Firefox/Go Faster: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Notes)
m (name fixup)
 
(21 intermediate revisions by 7 users not shown)
Line 1: Line 1:
= Overview =
= Overview =
Go Faster is a plan to change the way we ship Firefox for Desktop, and potentially other products. The end goal is to reduce the time it takes to deliver value to the user. This focuses on getting features and fixes to the user on a reduced cycle time, but includes reductions in time to download updates and new versions, and reductions in build and release time.
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==
==Team==
Line 9: Line 9:
| Laura Thomson || Product Owner
| Laura Thomson || Product Owner
|-
|-
| Cory Price || Program Management
| Rehan Dalal || Program Management
|-
| Robert Helmer || Technical Lead
|}
|}


==KPI's==
==KPI's==
* TODO
* Number of projects using the tools.
* All new features or improvements to existing features validated by go faster by the end 2016.


==Meetings==
==Meetings==
* [https://wiki.mozilla.org/Firefox/Go_Faster/Meetings Meeting Notes]
* [[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 25: Line 28:
* IRC: #gofaster
* IRC: #gofaster


= Current Status=
= Release Process and Mechanics =


<big>'''2016-04-12'''</big>
== Process ==
* [next week] Hello retrospective next week to discuss the first rollout of system add-on.
* [next week] SHIELD/Kinto/Switchboard teams are meeting this week.
* [next week] QA and Release Engineering are working through release mechanics, scheduling and testing discussions.
* [todo] Define program-level KPI's.
* [todo] Build a timeline.


([[Firefox/Go Faster/Status|past updates]])
Have something you want to ship through Go Faster?


= Projects =
Start here:
* [[Firefox/Go_Faster/System_Add-ons/Process]]
 
== 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]].


== I: Ship features as system add-ons ==
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 60: Line 61:
| Ben Hearsum || Tools
| Ben Hearsum || Tools
|-
|-
| Chris Lonnen || Tools
| Ritu Kothari || Tools
|-
| Lonnen || Tools
|-
|-
| Axel Hecht || l10n
| Axel Hecht || l10n
|}
|}


<big>'''16Q2 Goals'''</big>
= Projects =
* Clearly defined process for rollout out a system add-on.
* Process defined for handling multiple system add-ons.
* Metrics infrastructure.


<big>'''Resources'''</big>
These are the top-level projects defined for this program.
* [https://docs.google.com/document/d/1x27I7hAmWDWiqk3o3YC3fklhE3N59bdgHCQHF5p_lkU/edit#heading=h.x1jyf4e7lno7 Release & Relnotes plan]
* [[Firefox/Go_Faster/Releasing_an_add-on_mechanics|Releasing mechanics]]
 
== II: Switchboard ==
 
A service we use to segment users for A/B testing (and staged rollouts) on mobile.


<big>'''Team'''</big>
== Morgoth ==
{| class="wikitable"
|-
! Name !! Role
|-
| Margaret Leibovic || Owner
|-
| Sebastian Kaspari || Engineering
|}


<big>'''16Q2 Goals'''</big>
[[Firefox/Morgoth|Morgoth]]
* Mobile A/B Testing
* Downloadable content with Kinto


<big>'''Resources'''</big>
* Project Owner: Benson Wong [:mostlygeek]
* https://wiki.mozilla.org/Mobile/Fennec/Android/Switchboard
* https://mozilla.aha.io/products/FENN/feature_cards
* https://github.com/mozilla-services/switchboard-server
* https://github.com/mozilla-services/switchboard-experiments


== III: Kinto ==
== Kinto ==


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


<big>'''Team'''</big>
<big>'''Team'''</big>
Line 115: Line 95:
| 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 125: Line 100:
* Tool: http://kinto.readthedocs.org
* Tool: http://kinto.readthedocs.org


== IV: Recipe Server (SHIELD + Variants) ==
== 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.
A system that provides a fast and powerful way for Firefox to fix configuration problems, interact with users, and recommend features.


Line 139: Line 114:
| 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
* [[Firefox/Recipe_Server|Recipe Server]]


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


Line 165: Line 134:
| 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
* [[Test_Pilot|Test Pilot]]


= Shipping Pipeline =
= Shipping Pipeline =
[https://docs.google.com/spreadsheets/d/1yOgiOTU8q2I709VFhjCYCLATmoyQueV8RttPzciFIkQ/edit Shipping Pipeline Spreadsheet]


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 doc for a list of System Add-ons in flight.
 
Team:
 
== SHIELD ==
 
Team: Matt Grimes, Gregg Lind, Mike Kelly
 
== WebExtensions (tbd) ==
 
Team: Matt Grimes, Gregg Lind, Mike Kelly
 
== Hello ==
 
Team: Ian Bicking, Mark Banner
 
Shipped with 45 via system add-on.
 
== Pocket ==
 
Team: Shane Caraveo
 
Scheduled to ride the 46 release train.

Latest revision as of 22:26, 5 May 2023

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
Rehan Dalal Program Management
Robert Helmer Technical Lead

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:

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
Lonnen Tools
Axel Hecht l10n

Projects

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

Morgoth

Morgoth

  • Project Owner: Benson Wong [:mostlygeek]

Kinto

A JSON storage service with synchronisation and sharing ability - 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

Shipping Pipeline Spreadsheet

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 doc for a list of System Add-ons in flight.

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