Compatibility/Meetings/2018-06-work-week

From MozillaWiki
< Compatibility‎ | Meetings
Revision as of 21:29, 4 June 2018 by Karlcow (talk | contribs) (→‎Webcompat.com survival 101 (karl): adding things about webcompat.com 101 survival)
Jump to navigation Jump to search

This is the agenda and logistics page for Web Compatibility Team Work Week meeting in San Francisco (USA) from June 11 - June 15, 2018.

Logistics

Attendees

Hotel Attendee Arrival Departure
San Francisco Marriott Marquis Adam Stevenson Monday 19:00 Saturday 12:00
San Francisco Marriott Marquis Dennis Schubert Monday 12:55 Sunday 09:22
San Francisco Marriott Marquis Karl Dubost Monday 10:35 Sunday 12:20
San Francisco Marriott Marquis Mike Taylor Monday 15:42 Friday 23:59
San Francisco Marriott Marquis Oana Arbuzov Sunday 14:55 Saturday 13:45
San Francisco Marriott Marquis Ola Gasildo @@ @@
San Francisco Marriott Marquis Sergiu Logigan Sunday 14:55 Saturday 13:45
San Francisco Marriott Marquis Tom Wisniewski Monday 16:00 Saturday 22:45
San Francisco Marriott Marquis Kate Manning Monday 17:30 Saturday 11:00

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
  • 11:00am - 12:00: Web Compatibility Policy Discussion (Nob Hill B)
  • 1:00pm - 2:00pm
  • 2:00pm - 3:00pm
  • 2:30pm - 4:30pm Blipz meeting (for those involved or interested)
  • 3:00pm - 4:00pm
  • 4:00pm - 4:30pm
  • 4:30pm - 5:30pm

Friday 15

  • 9:00am - 9:50am
  • 10:00am - 12:00: Mozilla Developer Faire
  • 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

One Thousand Paper Cuts of Webcompat.com (karl)

The new redesign has been done, but there are some paper cuts that need to be fixed. Maybe we should create a new scope label: papercut

Webcompat To Bugzilla (karl)

(DEMO?) An accelerator to process issues. It is working well. Maintained by MDTsai. What should we do to evolve it? https://github.com/MDTsai/webcompat-to-bugzilla/

Etherpad at risk (karl)

What do we do with the information stored there? Do we back-it up on the wiki? Or let it rest for ever in the oblivion? Do we change platform for taking minutes too?

WebCompat.com next (karl)

Features we want to focus on in the next 6 months. We need to think impact for users and realistic time to create/manage them.


Lessons of Heroku as a hosting platform (karl)

I put this to quickly share what I learned and the Pros and Cons of moving to Heroku for hosting.

Dashboard check-in and coordination

Where are we at with our current efforts? Where do we want to be?

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."

SeeAlso GitHub/Microsoft… There are two different things:

See Also https://github.com/webcompat/webcompat.com/issues/2449

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.

Triage with Karl (Sergiu & Oana)

A new session for tips and tricks on how to improve Triage process (How to add breakpoints in WebIDE/How to open iframes in separate window/How to modify JS scripts in WebIDE/How to stop webpages refreshing).

Workshop with Mike and Ola (Sergiu & Oana)

A session on how to work with webcompat.com DEV (how to start local server, make changes, make pull requests) Notes: Any news how to start Webcompat server on Windows? #issue 2267 Unable to start the Local Server on Windows 10

Pre-triage Experiment with the crowd (Sergiu & Oana)

Discuss results and future plans (how are we scaling this?)

New Firefox for Android – Phoenix version (Sergiu & Oana)

Discuss how will we handle the testing process (will we restart testing locales on the new version?)

Webcompat Email bugs (adam_s)

This recently came up. How to handle webcompat issues that occur in Gmail using Firefox but not Chrome? How can someone report that to us?

WebCompat Team Dinner

Suggesting we all go out for a team dinner.

Retrieved from "https://dev.wikimo.nonprod.webservices.mozgcp.net/index.php?title=Compatibility/Meetings/2018-06-work-week&oldid=1195071"