This is the agenda and logistics page for Web Compatibility Team Work Week meeting in Austin (USA) from December 11 - December 15, 2017.
- Previous Work Week: San Francisco, USA - June 2017.
- Next Work Week: (not known yet)
- 1 Logistics
- 2 Attendees
- 3 Agenda
- 4 Topics Bank
- 4.1 Keep good code quality in webcompat.com
- 4.2 Proper webcompat.com documentation for uwsgi and nginx
- 4.3 Makes Webcompat sprint better for everyone
- 4.4 Think and discuss about ideas on how to improve the bug quality
- 4.5 WebCompat Team Lightning Talks
- 4.6 WebCompat Team Dinner
- 4.7 Call for Help on Mozilla office screens
- 4.8 User Agent Detection
- 4.9 Working in Public
- Location: Austin, USA
- Hotel: JW Marriott Austin / Hilton Austin
|@@||Adam Stevenson||Friday 15:28||Saturday 16:10|
|JW Marriott Austin||Dennis Schubert||Monday 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|
First commit on webcompat.com 2013-12-13T21:44:40Z - 4 years ago 15:44 in Austin, Texas.
Use the following template in one of the section below:
==== Topic ==== Description with [http://example.com links] when necessary
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...).
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?