L10n:Goals/2011Q1/L10n Data
For quarterly releases, we'll need early and targeted outreach to our localization community, and address the messaging to where they are.
There are some lessons we learned about our data on localizations for Firefox 4. In particular, there are shortcomings in what data proved to be valuable to guide outreach. Firstly, how do we find locales that have better content to ship that currently signed off? That implies keeping statistics on the status of the currently signed-off changeset.
Remark: Sign-offs still play an important role in ensuring technical quality, like preferences, search setup, protocol handlers. Our source-based checks are improving, but they're not perfect.
- Project Lead: Axel
Status
Gathering data requirements based on Fx4 experience.
Goals
The data needed for targeted outreach to the l10n community, as well as a proper status display for product.
- Define the data set
- Implement the automation to get the dataset
- Run the automation to actually gather the data, also for past releases
- Be more robust in terms of infrastructure security, we're not shipping with this beast down.
- In great shape to easily tear up and down project branches, if needed
Non Goals
Ride-alongs
There are some opportunistic features to take while we're at it:
- update buildbot (requires at least stable scheduler api)
- separate the different infrastructure pieces,
- adding parallel slaves for better response times
- separating web front end from back bone
- stop polling hg and listen to pushes on hg
Timeline / Milestones
The numbered items are consecutive, the bullet items can be done in parallel.
- definition phase
- data design
- system design (with security input)
- implementation phase
- actual buildbot infrastructure code and updates to elmo for new data structures
- aquire IT resources, aka hardware (VM or not TBD)
- data
- run new infra to gather historical data
- merge shipping information, in particular sign-offs
- replace current system with new one
These are the bugs of interest:
| Bug | Owner | Status |
|---|
Requirements
- Guidance on infrastructure security
- Hardware/VM resources (IT)
Dependencies
None of the dependencies are hard blockers for the actual data piece, but have a deep impact on in particular ride-alongs, and the public facing web pages.
- Guidance on infrastructure security
- Move from pollers to pulse requires that to be stable on all repos
- stable interfaces and tests on upstream buildbot 0.8.x
- Integration of the new data models and their display with Elmo
