Compatibility/Meetings/2019-06-work-week

From MozillaWiki
Jump to: navigation, search

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

Logistics

  • Location: Whistler, Canada
  • Hotel: Multiple

Attendees

Hotel Attendee Arrival Departure
Aava Whistler Abdul Rauf Monday, 11:00 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
hotel_name *** (new hire) Monday, Saturday,
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 - 17:00 Blah

Topics Bank

Use the following template in one of the section below:

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

Unifying diagnosis workstream

See https://bugzilla.mozilla.org/show_bug.cgi?id=1553597. I'd 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 next?

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)

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.

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)?