Confirmed users
613
edits
Firefox/Go Faster: Difference between revisions
adding projects
(removed weekly meeting section as we dont have one yet) |
(adding projects) |
||
| Line 27: | Line 27: | ||
*'''Ship data separately from code:''' Pull data out and make it a separate download (transparent to the user) via the installer or updater. | *'''Ship data separately from code:''' Pull data out and make it a separate download (transparent to the user) via the installer or updater. | ||
<p></p> | <p> | ||
== Project 1: Ship features as system add-ons == | |||
Component: Addons manager in Firefox | |||
Owner: Addons team (under Dave Camp, new team being formed - check with Dave for who) | |||
Tasks: | |||
Make Firefox understand what a system add-on is | |||
How to install one | |||
How it should be signed | |||
Where it should be updated from | |||
That it can't be uninstalled, only disabled | |||
That it should be available across all profiles | |||
Work with add-on updater team to figure out where to install these from. | |||
Component: Updater in Firefox | |||
Owner: Rob Strong? / Addons team? Check with dcamp for who | |||
Tasks: Change the updater: | |||
Update system add-ons | |||
Check compatibility/dependencies | |||
Check signed appropriately | |||
Update data files | |||
Separate the updater from the Firefox binary | |||
Component: Services system add-on updater | |||
Owner: ? - Potentially Les Orchard or Selena Deckelmann | |||
Tasks: | |||
Figure out if we want to serve system addons from AMO, from Balrog, or from somewhere else | |||
Build that. | |||
Component: Build, release, QA pipeline | |||
Team: Selena Deckelmann for releng, Krupa Raj and Matt Brandt from WebQA, someone from desktop QA | |||
Tasks: | |||
Design a build and release pipeline for system add-ons (using existing tools) (Selena) | |||
Decide/design the role of QA in CD for Firefox (QA teams) | |||
Component: l10n for systems addons | |||
Team: Pascal Chevrel? (haven't talked to him yet), Michael Kelly | |||
Tasks: | |||
Design and build a process for localizing system add-ons | |||
Component: Hello as add-on | |||
Owner: Adam Roach (WebRTC) + Mark Banner (Client Hello team) | |||
Tasks: | |||
Implement Hello as a system add-on | |||
Create a migration path from Hello in product to Hello as system add-on | |||
Dependencies: | |||
Updater changes, build pipeline? | |||
== Project 1a: Ship experiment features as add-ons from IdeaLab == | |||
Component: Universal Search as IdeaLab add-on | |||
Owner: Jared Hirsch/Nick Chapman | |||
Tasks: | |||
Implement Universal Search as an experimental add-on (this can be served/updated from AMO or similar) (Jared/Les) | |||
Implement first iteration of Firefox IdeaLab website (Nick Chapman/John Gruen) | |||
Design and implement process for IdeaLab experiments | |||
Dependencies: | |||
None. | |||
== Project 2: Pull data out of products and serve and update it separately == | |||
Tech lead/architect: Tarek Ziade | |||
Component: Services data updater | |||
Owner: French team (Tarek) | |||
Tasks: | |||
Serve updates to security policy | |||
Serve datafiles for Fennec (dictionaries and fonts) | |||
Dependencies: | |||
Client updater changes (in project 1, above) | |||
== Project 3: decouple l10n from product == | |||
I'm suggesting we do the other two things first, and plan on picking this up in q4 for resource contention reasons, but I may be persuaded otherwise. | |||
Component: Build process | |||
Owner: Chris AtLee / RelEng / RelMan | |||
Tasks: | |||
Remove l10n repacks from the release critical path | |||
Work out how to add additional strings to locale packs | |||
Automate uploading locale packs to AMO | |||
Dependencies: | |||
Installer/updater changes | |||
Component: Installer/updater | |||
Owner: Rob Strong or Add-ons team | |||
Tasks: | |||
Build stub installers for Windows and Linux | |||
Change installer to pull locale pack from AMO as a separate download | |||
Figure out how locale updates need to work | |||
</p> | |||
Things we want to do - but not starting until higher priorities are done: | Things we want to do - but not starting until higher priorities are done: | ||
*TBD - add as things come up | *TBD - add as things come up | ||