MozillaWiki

Firefox/Go Faster: Difference between revisions

< Firefox
(→‎Documentation: Add existing docs to the list.)
m (name fixup)
 
(29 intermediate revisions by 7 users not shown)
Line 1: Line 1:
= Go Faster =
= 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.  


==Meetings, Status Reports, Communications==
==Team==
* [https://wiki.mozilla.org/Firefox/Go_Faster/Meetings Meetings]
{| class="wikitable"
* [https://wiki.mozilla.org/Firefox/Go_Faster/Status Status Reports]
|-
* Bi-Weekly Team Meeting: Tuesdays at 11:30 San Francisco, CA, USA local time ([https://www.timeanddate.com/worldclock/converted.html?iso=20151124T0930&p1=224&p2=250&p3=0&p4=195 conversions]) in the "Program Management" Vidyo Room.
! 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==
* [[Firefox/Go_Faster/Meetings|Meeting Notes]]
* Bi-Weekly Team Meeting
** 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)
 
==Communications==
* [https://mail.mozilla.org/listinfo/gofaster Mailing List] (open to all, primarily used for sharing status)
* [https://mail.mozilla.org/listinfo/gofaster 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:
* [[Firefox/Go_Faster/System_Add-ons/Process]]
== Mechanics ==
This page details the technological pieces involved in shipping system add-ons.
[[Firefox/Go_Faster/Releasing_an_add-on_mechanics|Releasing mechanics]].
The initial authors of this process are


=Development=
{| class="wikitable"
<p> </p>
|-
==Schedule==
! Name !! Role
* [https://wiki.mozilla.org/Release_Management/TeamWiki Firefox main release schedule] is the master location for the dates when each Firefox version goes to Aurora, Beta, & Release.
|-
* System add-ons:
| needs:owner || Owner
** Hello (45) and Pocket (46) are shipping as system add-ons.
|-
** We shipped our first (signed, no-op) update to the beta channel on Friday, February 26 2016.
| Mark Banner || Hello/docs
* Data updates:
|-
** Finalizing signing now.
| Ian Bicking || Hello/docs
** OneCRL is shipping in 47
|-
** AMO blocklist is shipping via Go Faster (Kinto) in 49
| Rob Helmer || Client
* DLC
|-
** Fennec  fonts is shipping in 48
| Dave Townsend || Client
* Test Pilot is scheduled [real soon now]
|-
| Ben Hearsum || Tools
|-
| Ritu Kothari || Tools
|-
| Lonnen || Tools
|-
| Axel Hecht || l10n
|}


= Projects =


<p> </p>
These are the top-level projects defined for this program.


== Morgoth ==


== Goals ==
[[Firefox/Morgoth|Morgoth]]
* 2016 H1 strategic initiatives:
* System add-ons
** System add-ons infrastructure complete: Documented, simple, easy to ship/update, easy to localize. (Q2)
** Staged rollout of a system addon: With a/b testing (Q2)
** Measurement infrastructure in place: Telemetry for go-faster addons (Q2)
** String delivery and updates are decoupled from trains (May tweak the wording here slightly, but essentially l10n work to support Go Faster) (Q2)
* Test Pilot
** Test Pilot launch: Release opt-in platform that allows us to perform controlled tests of new high-visibility product concepts in the general release channel of Firefox (Q2)
** Test Pilot metrics dashboard: Metrics dashboard to aid experiment authors in making decisions (Q2)


* Q1 goals:
* Project Owner: Benson Wong [:mostlygeek]
** Ship Hello as a system add-on and update it
** OneCRL via Kinto into production
** Fennec fonts installed on demand (DLC) via Kinto
** Scope and prototypes for rollout and telemetry systems
** Test Pilot locale expansion - Nick/Wil
** Test Pilot launch - Nick/Wil


== Kinto ==


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


== Project 1: Ship features as system add-ons ==
<big>'''Team'''</big>
=== Client ===
{| class="wikitable"
* Owner: Dave Townsend, Robert Helmer
|-
! Name !! Role
|-
| Tarek Ziade || Owner
|-
| Mark Goodwin || OneCRL client, PKI work for the signing
|-
| Sebastian  || Fennec Client
|-
| Jorge || our customer for the AMO blocklist
|}


=== Tools/Metrics ===
<big>'''Resources'''</big>
[https://wiki.mozilla.org/Firefox/Go_Faster/Release_Pipeline Release Pipeline]
* Tracking document: https://docs.google.com/document/d/1MHQNqJ--GAmNxXl2PODJ-YGU459l6vvDRmf9oEIRTms/edit
* Owner: Chris Lonnen (Tools and Systems)
* Tool: http://kinto.readthedocs.org


=== Hello as add-on ===
== Recipe Server (SHIELD + Variants) ==
* Owner: Mark Banner, Ian Bicking (Hello)
A system that provides a fast and powerful way for Firefox to fix configuration problems, interact with users, and recommend features.


=== Pocket as add-on ===
<big>'''Team'''</big>
* Owner: Shane Caraveo (BD&L)
{| class="wikitable"
|-
! Name !! Role
|-
| Gregg Lind || Owner
|-
| Matt Grimes || Product Manager
|-
| Mike Kelly  || Engineering Manager
|}


== Project 2: Ship experimental features as add-ons from Test Pilot ==
<big>'''Resources'''</big>
* Product Owner: Nick Chapman
* [[Firefox/Recipe_Server|Recipe Server]]
* Engineering Team: Wil Clouser (manager), Jared Hirsch (dev), Dave Justice (dev), John Gruen (UX), Les Orchard (dev)
* Tasks:
    * Implement Universal Search as an experimental add-on (this can be served/updated from AMO or similar) (Jared/Les)
    * Implement first iteration of Test Pilot website (Nick Chapman/John Gruen)
    * Design and implement process for Test Pilot
* Dependencies:
    * None.
* Resources
    * Planning Doc: https://docs.google.com/document/d/1bew13QgnGriiMEEZMnI7XP6P2ieq6KiE0t4tDzrqcxQ/edit
    * Primary Wireframes: https://www.dropbox.com/s/n7dz7be1zm372mu/idea-town-WIRES.pdf?dl=0
    * Flows: https://www.lucidchart.com/documents/view/5efea80e-6240-4c24-801f-fd56c1ca9c3d
    * Github Repo: https://github.com/mozilla/idea-town


== Project 3: Data Updates ==
== Test Pilot ==
* Owner: Tarek Ziade + Cloud Storage team
A system that provides a fast and powerful way for Firefox to fix configuration problems, interact with users, and recommend features.


== Project 4: decouple l10n from product ==
<big>'''Team'''</big>
* On hold
{| class="wikitable"
|-
! Name !! Role
|-
| Javaun Moradi || Owner
|-
| Cory Price  || Program Management
|-
| Wil Clouser || Engineering Manager
|-
| John Gruen  || UX Lead
|}


==Roles and Responsibilities==
<big>'''Resources'''</big>
The [https://wiki.mozilla.org/Firefox/Contacts Contacts Page] has the Roles and Responsibilities for Firefox teams, partner teams, and external partners.
* [[Test_Pilot|Test Pilot]]


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


Place for us to keep documentation for now. Will put something better together later.
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.


* [https://docs.google.com/document/d/1x27I7hAmWDWiqk3o3YC3fklhE3N59bdgHCQHF5p_lkU/edit#heading=h.x1jyf4e7lno7 Release & Relnotes plan]
View the doc for a list of System Add-ons in flight.
* [[Firefox/Go_Faster/Releasing_an_add-on_mechanics|Releasing mechanics]]

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.allizom.org/index.php?title=Firefox/Go_Faster&oldid=1246425"