Compatibility/Meetings/2019-06-work-week

This is the agenda and logistics page for Web Compatibility Team Work Week meeting in Whistler (Canada) from June 17 to June 22, 2018.

• Previous Work Week: Orlando, USA - December 2018.
• Next Work Week: Berlin, Germany - January 2020 (27 to Feb 1)

Logistics

• Location: Whistler, Canada
• Hotel: Multiple

Attendees

Hotel	Attendee	Arrival	Departure
Aava Whistler	Abdul Rauf	Monday, 14:25	Saturday, 8:00
hotel_name	Adam Stevenson	Monday	Saturday
Fairmont Chateau Whistler	Dennis Schubert	Monday, 15:55	Saturday, 17:45
Aava Whistler	Guillaume Démesy	Monday, 14:00	Saturday, 14:10
Fairmont Chateau Whistler	Karl Dubost	Monday, 14:50	Tuesday 25, 16:25
Aava Whistler	Kate Manning	Monday, 18:55	Saturday, 20:55
Westin Whistler	Ksenia Berezina	Monday, 12:59	Saturday, 16:45
Fairmont Chateau Whistler	Mike Taylor	Saturday, 21:26	Saturday 06:15
Fairmont Chateau Whistler	Tom Wisniewski	Monday, 16:42	Saturday, 00:05

Regrets

none.

Minutes

Scribed by Everyone!

Agenda

Monday 17

Arrival day

• 09:00 - 17:00 Blah

Tuesday 18

• 09:00 - 17:00 Blah
• 18:30 - 20:30 Team Dinner: BG Urban Grill. Reservation confirmed.

Wednesday 19

• 09:00 - 17:00 Blah

Thursday 20

• 09:00 - 17:00 Blah

Friday 21

• 09:00 - 14:00 Blah
• 14:00 - 15:00 WebCompat Metrics (see sched)
• 15:00 - 16:00 Blah
• 16:00 - 19:00 Chill out time
• 19:00 - ???? Friday Night Closing Event

Topics Bank

Use the following template in one of the section below:

 ==== Topic ====
 Description with [http://example.com links] when necessary

Assigning bugs and priority conventions

Let's come up with something consistent for Bugzilla work.

TSCI discussion

Now that we have a Top Site Compatibility Index, what does it mean for how we prioritize our work? I'd like us to discuss prioritizing efforts on top sites (the whole pipeline, not just diagnosis) and critical bugs going forward.

webcompat.com roadmap discussion

What's next?

A / B testing of webcompat.com bug form

(In theory we might have something useful to discuss? Will depend on Open Innovation getting the work done in time).

webcompat SAO workflow

Do we stay on GitHub? Move entirely to m-c? Let's discuss the pros and cons.

Unifying diagnosis workstream

See https://bugzilla.mozilla.org/show_bug.cgi?id=1553597. Mike would like to move all diagnosis work from Bugzilla to GitHub. Let's discuss the implications.

Outreach

There are a lot of bugs that need outreach, and no longer dedicated headcount to do this work. How do we split up the work?

Sharing diagnosis knowledge

We've tried weekly reports. What's next? Thomas had a proposal for a summary of the interesting issue. We probably need something which is easy to carry on.

Define 2019H2 OKRs

The goal is to come up with a set of objectives that we can reasonably achieve in the next 6 months.

Define 2019Q3 OKRs

The goal is to come up with a set of objectives that we can reasonably achieve in the next 3 months. This list is more tailored, matured. (note: Q3 OKRs already exist in a draft state, so let's dig in and see if we need to adapt)

[SV] Retest Bing top sites Should we consider having a new OKR task for Bing top sites after Bugzilla issue #1555035 is fixed?

Orlando 2018 All Hands Post Mortem

Let's check the project we started in Orlando and how much did we fare and fail. What we need to pursue or abandon?

Review WebCompat.com milestones/projects

There are a couple of unfinished tasks in current we need to review, trim, clean, close, move forward.

• webcompat.com projects.
• webcompat.com milestones
• metrics server projects

And let's create mini-projects that someone can take ownerships in a way which is not overwhelming.

Bug Work Process Check-in

How do we do our bug work (from new bug to closed bug)? Is it effective? Can it be improved? What are the bottlenecks?

Needsinfo co-hacking

Let's pair up and work on clearing out old and complicated needinfo requests.

Team walk

We can walk around and talk about bugs... by the trees. 🌲🌲🌳🐝🐛🐜🦟🦗🌿☘️🚶🏽‍♂️🚶🏼‍♀️🚶🏽‍♂️🚶🏽‍♂️🌳🚶🏼‍♀️🚶🏽‍♂️🚶🏼‍♀️……🌳……🏃🏽‍♂️🌳🌲🌳🌳

Tooling improvements discussion

Let's discuss how we could improve tools like Tinker Tester Developer Spy to lower the amount of time we have to do triage and diagnosis. Any specific papercuts, or things we do over and over? Perhaps we could finally make that addon to report common webcompat issues noticed on a given site?

• What is the status of the UI proposal made by Dennis in Florida work week (December 2018)?

Ask us anything for Ksenia

Probably Ksenia should collect all the questions she may have about the work and take the opportunity to fill up what is missing.

Use GoFaster as a platform to ship shims/polyfills?

Out of some discussions between Tom and Dennis around a WebSQL breakage, the idea of shipping polyfills via GoFaster came up. Let's have a discussion around that idea.

Reporter addon and Fennec/Fenix for mobile frameworks

How to get the new detection features in Fenix at least, and Maybe fennec (stucked on 68)?

[SV] Weekly task - Twitter issues investigation

Should we consider having a weekly task regarding investigation of issues reported by users on Twitter, which are gathered in this document and slack “Webcompat-in-the-wild” channel?

[SV] Monthly task - Verify “about:compat” bugs

Should we consider having a monthly task to verify that all the sites in “about:compat” on Desktop and Mobile still need the overrides or interventions (in Nightly)?

[SV] Webcompat new site design testing

Since the webcompat.com site is being redesigned should we consider having a task to test the new design?

[SV] Machine Learning for auto-triage (Nemo)

Are there any news about Nemo’s progress on this? Can we further help him in any way?