Firefox/Go Faster: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Add docs)
(Update board.)
Line 19: Line 19:
* [https://wiki.mozilla.org/Firefox/Go_Faster/Meetings Meeting Notes]
* [https://wiki.mozilla.org/Firefox/Go_Faster/Meetings Meeting Notes]
* Bi-Weekly Team Meeting
* Bi-Weekly Team Meeting
** Tuesdays at 11:30 AM PST ([https://www.timeanddate.com/worldclock/converted.html?iso=20151124T0930&p1=224&p2=250&p3=0&p4=195 conversions])
** Every other Tuesday at 11:30 AM PST ([https://www.timeanddate.com/worldclock/converted.html?iso=20151124T0930&p1=224&p2=250&p3=0&p4=195 conversions])
** "GoFaster" Vidyo Room (extension 8557)
** "GoFaster" Vidyo Room (extension 8557)


Line 26: Line 26:
* IRC: #gofaster
* IRC: #gofaster


= Current Status=
= Release Process and Mechanics =


<big>'''2016-06-07'''</big>
== Process ==
* Project Morgoth is kicking off this month.
* Pipeline is moved to Trello: https://trello.com/b/moJCpVCD/go-faster-system-add-on-pipeline
* Finalizing release process documentation.


([[Firefox/Go Faster/Status|past updates]])
Have something you want to ship through Go Faster? Start here:
https://wiki.mozilla.org/Firefox/Go_Faster/Process


= Projects =
== Mechanics ==
 
This page details the technological pieces involved in shipping system add-ons.


These are the top-level projects defined for this program.
[[Firefox/Go_Faster/Releasing_an_add-on_mechanics|Releasing mechanics]].


== Improve existing system add-on mechanics ==
The initial authors of this process are
Developing the mechanisms and processes required to ship system add-ons.


<big>'''Team'''</big>
{| class="wikitable"
{| class="wikitable"
|-
|-
Line 66: Line 64:
|}
|}


<big>'''16Q2 Goals'''</big>
= Projects =
* Clearly defined process for rollout out a system add-on.
 
* Process defined for handling multiple system add-ons.
These are the top-level projects defined for this program.
* Metrics infrastructure.
 
== Morgoth ==
 
https://wiki.mozilla.org/Firefox/Morgoth


<big>'''Resources'''</big>
* Project Owner: Michael Kelly [:Osmose]
* [https://docs.google.com/document/d/1x27I7hAmWDWiqk3o3YC3fklhE3N59bdgHCQHF5p_lkU/edit#heading=h.x1jyf4e7lno7 Release & Relnotes plan]
* Development: Rehan Dalal [:rdalal], Web Engineering - Systems
* [[Firefox/Go_Faster/Releasing_an_add-on_mechanics|Releasing mechanics]].
* Status: Planning / Implementation
* [https://docs.google.com/document/d/1zc1fK37gVWFzaPdNHGsUtPXufrrUo5AGxIRfF1v5uic/edit Firefox System Add-on Update Protocol]
* Scheduled for: 2016 late q2 / q3


== Kinto ==
== Kinto ==
Line 93: Line 94:
| Jorge || our customer for the AMO blocklist
| Jorge || our customer for the AMO blocklist
|}
|}
<big>'''16Q2 Goals'''</big>
* OneCRL
* AMO Blocklist and ADI
* Fennec downloadable content


<big>'''Resources'''</big>
<big>'''Resources'''</big>
Line 117: Line 113:
| Mike Kelly  || Engineering Manager
| Mike Kelly  || Engineering Manager
|}
|}
<big>'''16Q2 Goals'''</big>
* A/B testing with Shield Studies
* Feature recommendation
* Self-repair
* Generalizable feedback


<big>'''Resources'''</big>
<big>'''Resources'''</big>
* https://wiki.mozilla.org/Firefox/Recipe_Server
* https://wiki.mozilla.org/Firefox/Recipe_Server
== Morgoth ==
https://wiki.mozilla.org/Firefox/Morgoth
* Project Owner: Michael Kelly [:Osmose]
* Development: Rehan Dalal [:rdalal], Web Engineering - Systems
* Status: Planning / Implementation
* Scheduled for: 2016 late q2 / q3


== Test Pilot ==
== Test Pilot ==
Line 152: Line 133:
| John Gruen  || UX Lead
| John Gruen  || UX Lead
|}
|}
<big>'''16Q2 Goals'''</big>
* Launch Test Pilot with 3 experiments enabled.


<big>'''Resources'''</big>
<big>'''Resources'''</big>
* https://wiki.mozilla.org/Test_Pilot
* https://wiki.mozilla.org/Test_Pilot
== Switchboard ==
2016-06-07: This is no longer part of Go Faster updates. More information can be found in their [[Mobile/Fennec/Android/Switchboard|docs]].


= Shipping Pipeline ( https://trello.com/b/moJCpVCD/go-faster-system-add-on-pipeline ) =
= Shipping Pipeline ( https://trello.com/b/moJCpVCD/go-faster-system-add-on-pipeline ) =
Line 167: Line 141:
The `how` for Go Faster are the top-level projects outlined above. The other important things to track are the individual features and fixes that are going to be launching ''through'' Go Faster.
The `how` for Go Faster are the top-level projects outlined above. The other important things to track are the individual features and fixes that are going to be launching ''through'' Go Faster.


== e10s ==
View the Trello board for a list of System Add-ons in flight.
 
Team: Chris Peterson, Felipe
 
== SHIELD ==
 
Team: Matt Grimes, Gregg Lind, Mike Kelly
 
== WebExtensions ==
 
Team: Andy McKay
 
== Hot Fixes ==
 
Team: Andy McKay
 
== Hello ==
 
Team: Ian Bicking, Mark Banner
 
Shipped with 45 via system add-on.
 
== Pocket ==
 
Team: Shane Caraveo
 
Scheduled to ride the 46 release train.

Revision as of 17:56, 19 July 2016

Overview

We believe that building out tools and processes for shipping Go Faster add-ons will enable Mozilla's engineers to get features and fixes to a larger audience sooner. We will know this is true when we see widespread adoption of system add-ons as a mechanism for moving faster and updating faster than the standard trains.

Team

Name Role
Laura Thomson Product Owner
Cory Price Program Management

KPI's

  • Number of projects using the tools.
  • All new features or improvements to existing features validated by go faster by the end 2016.

Meetings

  • Meeting Notes
  • Bi-Weekly Team Meeting
    • Every other Tuesday at 11:30 AM PST (conversions)
    • "GoFaster" Vidyo Room (extension 8557)

Communications

  • Mailing List (open to all, primarily used for sharing status)
  • IRC: #gofaster

Release Process and Mechanics

Process

Have something you want to ship through Go Faster? Start here: https://wiki.mozilla.org/Firefox/Go_Faster/Process

Mechanics

This page details the technological pieces involved in shipping system add-ons.

Releasing mechanics.

The initial authors of this process are

Name Role
needs:owner Owner
Mark Banner Hello/docs
Ian Bicking Hello/docs
Rob Helmer Client
Dave Townsend Client
Ben Hearsum Tools
Ritu Kothari Tools
Chris Lonnen Tools
Axel Hecht l10n

Projects

These are the top-level projects defined for this program.

Morgoth

https://wiki.mozilla.org/Firefox/Morgoth

  • Project Owner: Michael Kelly [:Osmose]
  • Development: Rehan Dalal [:rdalal], Web Engineering - Systems
  • Status: Planning / Implementation
  • Scheduled for: 2016 late q2 / q3

Kinto

A JSON storage service with synchronisation and sharing abilitie - allows the smart client to retrieve signed data from a dumb server.

Team

Name Role
Tarek Ziade Owner
Mark Goodwin OneCRL client, PKI work for the signing
Sebastian Fennec Client
Jorge our customer for the AMO blocklist

Resources

Recipe Server (SHIELD + Variants)

A system that provides a fast and powerful way for Firefox to fix configuration problems, interact with users, and recommend features.

Team

Name Role
Gregg Lind Owner
Matt Grimes Product Manager
Mike Kelly Engineering Manager

Resources

Test Pilot

A system that provides a fast and powerful way for Firefox to fix configuration problems, interact with users, and recommend features.

Team

Name Role
Javaun Moradi Owner
Cory Price Program Management
Wil Clouser Engineering Manager
John Gruen UX Lead

Resources

Shipping Pipeline ( https://trello.com/b/moJCpVCD/go-faster-system-add-on-pipeline )

The `how` for Go Faster are the top-level projects outlined above. The other important things to track are the individual features and fixes that are going to be launching through Go Faster.

View the Trello board for a list of System Add-ons in flight.

Retrieved from "https://wiki.allizom.org/index.php?title=Firefox/Go_Faster&oldid=1140352"