This is the agenda and logistics page for Web Compatibility Team Work Week meeting in Austin (USA) from December 11 - December 15, 2017.
- 1 Logistics
- 2 Attendees
- 3 Agenda
- 4 Topics Bank
- 4.1 Google Tier 1 Search Summary and next steps
- 4.2 Keep good code quality in webcompat.com
- 4.3 Direction of webcompat.com
- 4.4 Proper webcompat.com documentation for uwsgi and nginx
- 4.5 Makes Webcompat sprint better for everyone
- 4.6 Think and discuss about ideas on how to improve the bug quality
- 4.7 WebCompat Team Lightning Talks
- 4.8 WebCompat Team Dinner
- 4.9 Call for Help on Mozilla office screens
- 4.10 User Agent Detection
- 4.11 Working in Public
- 4.12 Data analysis of issues
- 4.13 Emails Good Practice
- 4.14 Webcompat newsletter
- 4.15 Minutes Generator (20 minutes)
- 4.16 Needs Diagnosis
- 4.17 ContactReady to SiteWait
- 4.18 Mozilla Wiki (2 minutes)
- Location: Austin, USA
- Hotel: JW Marriott Austin / Hilton Austin
|@@||Adam Stevenson||Friday 15:28||Saturday 16:10|
|JW Marriott Austin||Dennis Schubert||Tuesday 21:03 🌨⛄️||Sunday 17:00|
|JW Marriott Austin||Eric Tsai||Monday 11:00||Saturday 17:00|
|JW Marriott Austin||Karl Dubost||Monday 11:00||Saturday 18:43|
|JW Marriott Austin||Mike Taylor||local||local|
|Hilton Austin||Oana Arbuzov||Sunday 20:04||Saturday 13:10|
|N/A||Ola Gasildo||Attending remotely||Attending remotely|
|Hilton Austin||Sergiu Logigan||Sunday 20:04||Saturday 13:10|
Unless otherwise specified, we will meet in Firefox Visuals homeroom (maybe moving elsewhere together).
- Travel day. Be safe.
- 6pm - 9pm: (optional) Opening reception.
Note: Dennis' flight was cancelled. We might try to restructure some things to accommodate.
- 9:30am - 1:00pm All Hands plenary, photo, lunch
- 1:00pm - 3:00pm Agenda Topics (Mike might be a little late, like 1:30pm. Ola might be late, depending on the kid).
- 3:00pm - 5:00pm 2018 Planning (+2017 projects retrospective, come prepared to give status updates).
- 5:00pm - 5:15pm Planning for rest of week (which topics and when)
- 5:15pm: Dinner/Free time
First commit on webcompat.com 2013-12-13T21:44:40Z - 4 years ago 15:44 in Austin, Texas.
- 9:00 - 12:00 Team time / agenda items
- 1:00pm - 5:30pm Electives or project hacking (Minutes for today)
- 6:30pm - 9:30pm Dinner at Stubb's BBQ
- 9:00am - 12:00am Some kind of team thing, weather permitting. Waiver required.
- 1:00pm - 2:30pm Research lightning talks (for those interested).
- (2:00pm - 3:00pm Mike meeting with Rosana from Open Innovation to talk about crowdsourcing, others welcome to join)
- 3:00pm - 5:00pm Firefox Engineering lightning talks (for those interested). karl presenting.
- 5:00pm - 7:30pm Team Dinner at Mike's
- 9:00am - 10:30am Agenda items
- 10:45am - 12:00 (noon) Runtime Visuals & WebCompat
- 1:00pm - 2:00pm Agenda items
- 2:00pm - 3:00pm Keep good code quality in webcompat.com [Ola] more details
- 3:00pm - 4:00pm Direction of webcompat.com [Ola] more details
- 4:00pm - 4:30pm "Triage with Mike"
- 4:30pm - 5:30pm Agenda items
- 6:30pm - late. Closing party.
Use the following template in one of the section below:
==== Topic ==== Description with [http://example.com links] when necessary
Google Tier 1 Search Summary and next steps
Let's talk about what we've diagnosed so far, and try to summarize what our recommendations are for a final report.
Keep good code quality in webcompat.com
As webcompat.com is growing more and more, and we get more contributors in, I'd love to discuss ways to keep up our code quality and structuring the project bit more (processes for new features, test coverage, documentation...).
Direction of webcompat.com
With the discussions we had around new features and the form as well as the refactor, it seems we should talk about the direction of webcompat.com.
- What purpose(s) shall it serve?
- Which features do we need in the future to help reporters, the community and the team?
- What is the audience?
Proper webcompat.com documentation for uwsgi and nginx
We ran into an issue recently not happening on localhost. We should probably, create a better documentation on how to configure a similar (optional) environment for testing the server. The Current documentation explains broadly the configuration but doesn't really gives a step by step to replicate.
Makes Webcompat sprint better for everyone
For the release of Firefox 57 (Quantum) a firefox sprint was organized across the world, it created a huge amount of issues which were mostly invalid. This has an impact on our team productivity/mood. We need to create better circumstances for this type of events.
- Participation Guide (for creating such an event) ex: What is a Web Compat issue
- Coordination with Participation team in advance.
- Special form/parameters for this type of event
Think and discuss about ideas on how to improve the bug quality
As this is an ongoing point, let's find time for discussions about how we could improve the quality of incoming reports. This could include design changes, UX changes, adding new possibilities for reporters to provide some contact information, or whatever we may come up with.
Let's sit together and write some initial ideas, so we can discuss them in further detail in future meetings!
- About the sprint event. In Tokyo, the event didn't generate that many issues nor invalid bugs. The organization was key. The way it was handled with introduction to the topic and explanation of things which were wrong, individual as resource to evaluate, no contest in between participants—just the will to help, a Google sheet on who's working on what, …
WebCompat Team Lightning Talks
Let's all introduce a topic about something.
- [QA] Triage and how to
- [QA] Bugzilla History (Webcompat related issues)
WebCompat Team Dinner
Mike knowing probably Austin better than us, let's challenge him to find the right place.
Call for Help on Mozilla office screens
User Agent Detection
We had a discussion on the mailing-list about user agent sniffing. Let's draft something to make the MDN page up to date.
Working in Public
We need to define and reassess what it means to work in public. How do we share a common set of values for doing so?
Data analysis of issues
We have some side projects like Adam's issue metrics, Karl/Guillaume's triage dashboard, Eric's issue dependency graph. Let's discuss anything we are interested in and can do in the future.
Emails Good Practice
Re-Reading "Scaling email transparency" is a good thing. With things like: "Email transparency is fairly simple: make your emails transparent by CCing a list, and make it easy for others to be transparent by observing the responsibilities below."
- Should we stop "digest mode" of compatibility mailing-list?
- Do you require better headers, keywords in the email for filtering?
Followup. The idea didn't work. We had good goals but nobody contributing.
Minutes Generator (20 minutes)
Showing how shoki, the minutes generator is working. Issues, features.
The pile is growing how can we improve this by dealing with issues. Some ideas: Better tagging of issues class, dashboard, etc.
ContactReady to SiteWait
Should we create a non-public mailing-list that we can Bcc and which is archiving our requests for contacts (when there is no real mailing-list)? Just food for thoughts.
- Pro: Share the knowledge
- Con: Privacy issue with some contacts
- Con: More manual work for archiving responses. Need to Bounce message each time (not forward) to keep thread.
Mozilla Wiki (2 minutes)
Did you know you could subscribe to feed for page modifications?