|Bugzilla L10n Watcher|
|Directly Responsible Individual||Axel Hecht|
|Product marketing lead||`|
Stage 1: Definition
1. Feature overview
There's a host of issues around l10n that'd be good to catch early, and pre-emtive. For those that can be automated, we should do that.
2. Users & use cases
The team of community members that help our development community in writing patches that are good to localize, as well as the development community itself.
The checks can contain changed strings, new modules, just l10n impact in general.
Pulse: Observing new patches in bugzilla is probably best done through pulse.
IT: The observer needs some hardware to run on.
Alert bugs with l10n impact, and run some checks:
- existing strings are changed (might be OK or not, needs human follow up)
- new top-level directories are created (might be OK or not, needs human follow up)
It'd be nice if this tool could just get away with commenting on bugs, and wouldn't need a web side itself.
Non-goals would be r+ or r- on patches.
Stage 2: Design
5. Functional specification
6. User experience design
Stage 3: Planning
7. Implementation plan
Quality Assurance review
Stage 4: Development
Stage 5: Release
10. Landing criteria
|Theme / Goal||`|
Team status notes