Compatibility/Meetings/2018-06-work-week
This is the agenda and logistics page for Web Compatibility Team Work Week meeting in San Francisco (USA) from June 11 - June 15, 2018.
- Previous Work Week: Austin, USA - December 2017.
- Next Work Week: Orlando, USA - December 2018
Logistics
- Location: San Francisco, USA
- Hotel: Marriott Marquis
Attendees
| Hotel | Attendee | Arrival | Departure |
|---|---|---|---|
| @@ | Adam Stevenson | Monday 16:00 | Saturday 12:00 |
| @@ | Dennis Schubert | Monday 12:55 | Sunday 09:22 |
| @@ | Karl Dubost | Monday 10:35 | Sunday 12:20 |
| @@ | Mike Taylor | Monday 15:42 | Friday 23:59 |
| @@ | Oana Arbuzov | Sunday 14:55 | Saturday 13:45 |
| @@ | Ola Gasildo | @@ | @@ |
| @@ | Sergiu Logigan | Sunday 14:55 | Saturday 13:45 |
| @@ | Tom Wisniewski | Monday 16:00 | Saturday 22:45 |
Regrets
Agenda
Monday 11
Arrival day
- 9:00am - 10:30am
- 10:45am - 12:00
- 1:00pm - 2:00pm
- 2:00pm - 3:00pm
- 3:00pm - 4:00pm
- 4:00pm - 4:30pm
- 4:30pm - 5:30pm
Tuesday 12
- 9:00am - 10:30am
- 10:45am - 12:00
- 1:00pm - 2:00pm
- 2:00pm - 3:00pm
- 3:00pm - 4:00pm
- 4:00pm - 4:30pm
- 4:30pm - 5:30pm
Wednesday 13
- 9:00am - 10:30am
- 10:45am - 12:00
- 1:00pm - 2:00pm
- 2:00pm - 3:00pm
- 3:00pm - 4:00pm
- 4:00pm - 4:30pm
- 4:30pm - 5:30pm
Thursday 14
- 9:00am - 10:30am
- 10:45am - 12:00
- 1:00pm - 2:00pm
- 2:00pm - 3:00pm
- 3:00pm - 4:00pm
- 4:00pm - 4:30pm
- 4:30pm - 5:30pm
Friday 15
- 9:00am - 10:30am
- 10:45am - 12:00
- 1:00pm - 2:00pm
- 2:00pm - 3:00pm
- 3:00pm - 4:00pm
- 4:00pm - 4:30pm
- 4:30pm - 5:30pm
Bye Bye Event.
Topics Bank
Use the following template in one of the section below:
==== Topic ==== Description with [http://example.com links] when necessary
Module for WebCompat?
Does a Mozilla-style module ownership model make sense for the WebCompat project and its sub-projects (webcompat.com, addons, report site issue, go faster..)?
https://www.mozilla.org/en-US/about/governance/policies/module-ownership/
Let's come to a decision together.
IRL OKR Check-in (mike)
Just like it says.
Webcompat.com survival 101 (karl)
Mapzen closed its doors. Here an interesting take on the way they developed their project. What can we learn and do from this?
"Early on at Mapzen, we were planning some new project. I asked a question that kind of scared me: “How would this survive the death of the company?” We weren’t close to death, and it scared me because who wants to hear that from the CEO? But it captured what we were doing in this special point in time and inspired our work. We had the chance to build everything to survive, and we did it. And we planned it all along the way to survive past our own existence."
Team Mission Statement (mike)
Review and finalize a team mission statement, including norms around communication to eachother and the outside world.
What is Webcompat? (karl)
Tied to the Team Mission Statement proposed by mike, but more on the side of defining what is webcompat for each of us in 3 minutes. This should help clarify and understands our own boundaries and see how we can do a better mission statement.
Experimental Diagnosis Add-on (tom)
A dive into how to use the current version of the add-on, as well as collecting feedback and brainstorming desired improvements. The basic aim is to help reduce the time we spend diagnosing issues by enabling more powerful diagnosis features.