Compatibility/Meetings/2018-12-work-week

From MozillaWiki
< Compatibility‎ | Meetings
Revision as of 18:30, 28 November 2018 by Miketaylr (talk | contribs) (→‎Thursday 6: fleshing out thursday)
Jump to navigation Jump to search

This is the agenda and logistics page for Web Compatibility Team Work Week meeting in Orlando (USA) from December 3 - December 7, 2018.

Logistics

  • Location: Orlando, USA
  • Hotel: Dolphin and Swan Hotel, DisneyWorld

Attendees

Hotel Attendee Arrival Departure
Dolphin Hotel Adam Stevenson Monday, 19:33 Saturday, 07:00
Dolphin Hotel Dennis Schubert Monday, 17:55 Saturday, 20:20
Dolphin Hotel Guillaume Demesy Monday, 18:31 Saturday, 13:25
Dolphin Hotel Karl Dubost Monday, 21:39 Saturday, 06:45
Dolphin Hotel Kate Manning Monday, 17.55 Saturday, 20.20
Dolphin Hotel Mike Taylor Monday, early Saturday, early
Dolphin Hotel Tom Wisniewski Monday, 19:38 Saturday, 12:40
Dolphin Hotel Mariana Meireless Monday Saturday

Regrets

none.

Minutes

Scribed by Everyone!


Agenda

Monday 3

Arrival day

  • 09:00 - 17:00 People arriving all day long. Time to sleep, relax, walk around, meet if you wish. Tomorrow is the big day of work.
  • 18:00 - 21:00 Welcome Reception

Tuesday 4

  • 09:00 - 10:30 Mozlando Plenary
  • 11:00 - 12:00 Defining the agenda for the week using the topics bank. We vote on what we prefer/priorities.
  • 12:00 - 13:00 Outreachy lunch (for outreachy participants and mentors)
  • 13:00 - 15:00 Outreachy onboarding (for outreachy participants)
  • 13:00 - 15:00 H1 (Q1 & Q2) OKR Planning
  • 15:30 - 17:00 Engineering Lightning talks
  • 17:00 - 18:30 Down time / free time
  • 18:30 Hop on bus to Disney Springs for team dinner
  • 19:15 Team dinner at The Boathouse (click to see menu) Note: we have a reservation for 8 people, which is everyone on the immediate team.

Wednesday 5

  • 08:30 - 09:30 Compat/DevTools Diagnosis Party - Visuals Homeroom. (organized by Harald Kirschner)
    • Getting together to do some hands-on diagnosis for webcompat reports: https://webcompat.com/issues?stage=needsdiagnosis
    • Outcomes:
      • Successfully diagnose some issues, of course
      • Better shared understanding of web compat use cases, pain points and general experience; maybe commenting/filing some devtools issues
      • Quality DX team time
  • 09:30 - 12:00 Agenda Topics
  • 12:00 - 13:00 Lunch
  • 13:00 - 17:00 Agenda Topics (the "management" will be in a training...)
  • 17:00 - 18:30 Free time
  • 18:30 - 22:30 Evening: All company evening event at Kennedy Space Center

Thursday 6

  • 09:00 - 10:00 Platform and Web Compat Strategy
  • 10:15 - 11:15 Developer Experience All Hands
  • 11:30 - 12:00 Agenda Topics
  • 12:00 - 13:00 Lunch
  • 13:00 - 18:00 Agenda Topics

Friday 7

  • 09:00 - 16:00 Blah
  • 16:15 - 17:00 Exec Q&A for Runtime and Visuals teams
  • 19:00 - 24:00 Closing event at The Wizarding World of Harry Potter at Universal Studios

Topics Bank

Use the following template in one of the section below:

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

Measuring Compat in 2019

An overview and discussion of 2 proposed metrics for measuring progress in 2019.


2019 Vision and Alignment

Let's make sure we're working on the most important things for this year.

Hard to Diagnose bugs

Discussion around the collected Hard to Diagnose Bugs.

Work/Dev environment for webcompat-metrics

Karl, Guillaume and Kate need to work together on harmonizing the dev/local environment and probably document it, so we avoid issues.

Define OKRs for 2019Q1

To be sure to be ready to work on first day of 2019Q1, we need to have defined OKRs. We might want to predefine ideas of OKRs for 2019Q2.

Bot monitoring twitter for webcompat issues notifications

Users who are sending an anonymous report are often saying they submitted the issue on twitter. How do we track that? Should we make it visible in the bug? (privacy/opacity borderline by linking contexts).

FIXED IT

Core engineers are doing an awesome work at helping us and fixing the webcompat issues. We need to make this more visible. Probably a weekly/monthly blog post on the style of karl's lightning talk "FIXED IT".

Web Compatibility Improving Performance

Working with the outreachy candidate on the Performance project for webcompat. (Mike and Karl). Defining the steps. What should be kept for the project, what should be cut. So we don't have a too broad scope.

Review of Tinker-Tester

Dennis, Karl, Thomas will discuss about the current features and how to add/remove of them or anything related to the UX/design.

Improve the console.log reporting by the Reporter extension

Thomas. Karl (maybe Mike) See Discussions in issue 2659 Also https://bugzilla.mozilla.org/show_bug.cgi?id=1510073 So currently the reporter extension is sending JSON to the form which is then stored after being petrified as a string to be held into a hidden field. That's not very satisfying. A couple of silly ideas.

  • git commit (by webcompat-bot) a structured JSON of the console.logs into web-bugs repo.
  • upload the JSON the same way we do with images (create a link to the JSON file) which is added to the details.
  • Create a gist on webcompat bot account with the JSON.

SeeAlso https://bugzilla.mozilla.org/show_bug.cgi?id=1510067 and https://bugzilla.mozilla.org/show_bug.cgi?id=1510063

about:compat discussion

Discussion on the about:compat page, things that should be included, how we can implement and ship it, ...

Stalled needsdiagnosis from other vendors

We start to have a growing collections of issues not taken care of by other vendors.

  • We could in graph separate them. (issues with multiple labels). At least for Mozilla that would show a better reality of the work being done.
  • We could try to wake up the relationships. Another webcompat summit? With more maturity now. 3 years later.


Stalled needsdiagnosis for certain labels

Some of these are not being taken care of. This is useless if we do not do anything about them.

  • Marfeel
  • GWS
  • Reality browser VR


To diagnose while in USA


Check-our-current-needsinfo party

Everyone of us we are going through the current personal needsinfo and we make an assessment of what's the next step? When we can commit to an effort on it? Or if we just pass.