Compatibility/Meetings/2017-12-work-week: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎Attendees: Update Hotel - Sergiu)
(Added Hotel)
Line 24: Line 24:
| JW Marriott Austin || Mike Taylor || local  || local
| JW Marriott Austin || Mike Taylor || local  || local
|-
|-
| @@ || Oana Arbuzov ||  Sunday 20:04  || Saturday 13:10
| Hilton Austin || Oana Arbuzov ||  Sunday 20:04  || Saturday 13:10
|-
|-
| @@ || Ola Gasildo || --  || --
| @@ || Ola Gasildo || --  || --

Revision as of 07:41, 31 October 2017

This is the agenda and logistics page for Web Compatibility Team Work Week meeting in Austin (USA) from December 11 - December 15, 2017.

Logistics

  • Location: Austin, USA
  • Hotel: JW Marriott Austin / Hilton Austin

Attendees

Hotel Attendee Arrival Departure
@@ Adam Stevenson Friday 15:28 Saturday 16:10
@@ Dennis Schubert Monday 21:03 Sunday 17:00
@@ Eric Tsai @@ @@
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
@@ Ola Gasildo -- --
Hilton Austin Sergiu Logigan Sunday 20:04 Saturday 13:10
@@ Tom Wisniewski @@ @@

Regrets

Agenda

Topics Bank

Use the following template in one of the section below:

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

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

Time to time, there are bugs where we do not have credentials. One of the most likely outcome is that we close it being incomplete. Maybe we can harness the power of office screens to call for help.

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.