Compatibility/Meetings/2017-06-work-week

This is the agenda and logistics page for Web Compatibility Team Work Week meeting in San Francisco (USA) from June 26 - June 30, 2017.

• Previous Work Week: Berlin, Germany - April 2017.
• Next Work Week: (not known yet)

Logistics

• Location: San Francisco, USA
• Hotel: Hilton Hotel

Attendees

• [Parc55] Adam Stevenson
• [Union] Dennis Schubert (Arrival: Monday 6:15pm, Departure: Sunday, 2:05pm)
• [Union] Eric Tsai (Arrival: Monday 2:25pm, Departure: Sunday 1:40am)
• [Union] Guillaume Demesy (Arrival: Monday 12:30pm, Departure: Saturday 03:10pm)
• [Parc55] Karl Dubost (Arrival: Monday 10:30am, Departure: Saturday 11:25am)
• Mike Taylor
• [Union] Ola Gasildo
• [Parc55] Tom Wisniewski (Arrival: Monday 7:03pm, Departure: Saturday 7:55pm)

Topics Bank

Use the following template in one of the section below:

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

webcompat.com dev - committing on your repo

It seems there are two styles of coding for branches. Some people will commit on webcompat.com repo a branch, and some will do it on their personal fork. We pushed people to do it on their own repo in the past to avoid any kerfuffles on webcompat.com.

Communications channels and openess

There is a trend that we need to stop and fix. We have a tendency to use non-open communication channels for things which are not Mozilla-secret sensitive. Each time we share something on a private channel, each time we lower the sense of the community. Mundane stuff, simple links to geeky stuff, etc. All of that is useful for the community even if there are just peeping.

Triage Consistency

(Adam, Eric, Karl) When doing triage we need to define some consistent strategy. Examples: when do we close as incomplete? When do we move to non-compat and with which status? When it's a bug report for another browser, do we automatically move it to needsdiagnosis? Etc.

This Week Minutes

Let's make sure that we minute everything or have summaries for everything we discussed. Hawaii was a good work week but poorly minuted. We are usually good on the first day and then slowly with fatigue let things slip.

• Use the etherpad for minutes taking with the usual format.
• Minutes on the wiki by the end of each day. Karl will generate them.
• If working in smaller groups, write the minutes for your group on the etherpad at the usual place.
• Record clear Action items which can be understood out of context.
  • WHO to do WHAT in WHICH CONTEXT by THIS DATE
  • Example: Karl to do review peace in the world policy framework in webcompat-dev issue 6969 by 2020-03-16
• Send the minutes to the mailing-list. Karl will do it.

Webcompat.com Responsibilities Overview

How the responsibilities worked out since Berlin Meeting? Do we need to readjust the path? tweak? Do we sail as-is?

Webcompat.com San Francisco Milestone

We have a San Francisco Milestone for Webcompat.com. Let's try to tackle it before the work week.

Half-day or evening team building

Let's do something not work related together. The bigger the team the harder it becomes but we will probably find out something. If you have ideas, propose them here.