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

adding link to the next meeting.
(→‎Topics Bank: Add topic of data analysis)
(adding link to the next meeting.)
 
(34 intermediate revisions by 5 users not shown)
Line 2: Line 2:


* Previous Work Week: [[Compatibility/Meetings/2017-06-work-week|San Francisco, USA - June 2017]].
* Previous Work Week: [[Compatibility/Meetings/2017-06-work-week|San Francisco, USA - June 2017]].
* Next Work Week: (not known yet)
* Next Work Week: [[Compatibility/Meetings/2018-06-work-week|San Francisco, USA - June 2018]]


== Logistics ==
== Logistics ==
Line 16: Line 16:
| @@ || Adam Stevenson || Friday 15:28  || Saturday 16:10
| @@ || Adam Stevenson || Friday 15:28  || Saturday 16:10
|-
|-
| JW Marriott Austin || Dennis Schubert || Monday 21:03 || Sunday 17:00
| 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 || Eric Tsai || Monday 11:00  || Saturday 17:00
Line 36: Line 36:


== Agenda ==
== Agenda ==
Unless otherwise specified, we will meet in Firefox Visuals homeroom (maybe moving elsewhere together).
=== Monday 11 ===
=== Monday 11 ===
* Travel day. Be safe.
* 6pm - 9pm: (optional) [https://austinyallhands2017.sched.com/event/CweZ/welcome-to-austin-reception Opening reception].
=== Tuesday 12 ===
=== Tuesday 12 ===
Note: Dennis' flight was cancelled. We might try to restructure some things to accommodate.
[[Compatibility/Meetings/2017-12-12|Minutes]]
* 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
=== Wednesday 13 ===
=== Wednesday 13 ===
First commit on webcompat.com 2013-12-13T21:44:40Z - 4 years ago 15:44 in Austin, Texas.
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 [[Compatibility/Meetings/2017-12-13|Electives or project hacking]] (Minutes for today)
* 6:30pm - 9:30pm Dinner at Stubb's BBQ


=== Thursday 14 ===
=== Thursday 14 ===
* 9:00am - 12:00am Some kind of team thing, weather permitting. [https://docs.google.com/document/d/1fBjgUxUwNGZ4QRlMx9pE-kuevgb5_VaF-POgg5HjPd0/edit 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


=== Friday 15 ===
=== Friday 15 ===
[[Compatibility/Meetings/2017-12-15|Minutes]]
* 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] [https://public.etherpad-mozilla.org/p/webcompat.com more details]
* 3:00pm - 4:00pm Direction of webcompat.com [Ola] [https://public.etherpad-mozilla.org/p/webcompat.com more details]
* 4:00pm - 4:30pm "Triage with Mike"
* 4:30pm - 5:30pm Agenda items
* 6:30pm - late. Closing party.


== Topics Bank ==
== Topics Bank ==
Line 53: Line 92:
  Description with [http://example.com links] when necessary
  Description with [http://example.com links] when necessary
</pre>
</pre>
==== 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 ====
==== 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...).
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 ====
==== Proper webcompat.com documentation for uwsgi and nginx ====
Line 77: Line 126:
Let's all introduce a topic about something.
Let's all introduce a topic about something.


* [QA] Triage and how to<br />
* [QA] Triage and how to
* [QA] Bugzilla History (Webcompat related issues)
* [QA] Bugzilla History (Webcompat related issues)


Line 94: Line 143:


==== Data analysis of issues ====
==== Data analysis of issues ====
We have some side projects like Karl's triage dashboard, Eric's issue dependency graph. Let's discuss anything we are interested in and can do in the future.
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 ====
[https://stripe.com/blog/scaling-email-transparency 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?
 
==== Webcompat newsletter ====
Followup. The [https://public.etherpad-mozilla.org/p/webcompat-news idea didn't work]. We had good goals but nobody contributing.
 
==== Minutes Generator (20 minutes) ====
Showing how [https://github.com/karlcow/shoki shoki], the minutes generator is working. Issues, features.
 
==== Needs Diagnosis ====
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?


[[Category:Web Compatibility]]
[[Category:Web Compatibility]]
Confirmed users
1,567

edits