L10n:Features/Automation/Bugzilla Watcher
Status
| Bugzilla L10n Watcher | |
| Stage | Draft | 
| Status | ` | 
| Release target | ` | 
| Health | OK | 
| Status note | ` | 
{{#set:Feature name=Bugzilla L10n Watcher
|Feature stage=Draft |Feature status=` |Feature version=` |Feature health=OK |Feature status note=` }}
Team
| Product manager | ` | 
| Directly Responsible Individual | Axel Hecht | 
| Lead engineer | ` | 
| Security lead | ` | 
| Privacy lead | ` | 
| Localization lead | ` | 
| Accessibility lead | ` | 
| QA lead | ` | 
| UX lead | ` | 
| Product marketing lead | ` | 
| Operations lead | ` | 
| Additional members | ` | 
{{#set:Feature product manager=`
|Feature feature manager=Axel Hecht |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
Open issues/risks
`
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.
3. Dependencies
Pulse: Observing new patches in bugzilla is probably best done through pulse.
IT: The observer needs some hardware to run on.
4. Requirements
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
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
`
8. Reviews
Security review
`
Privacy review
`
Localization review
`
Accessibility
`
Quality Assurance review
`
Operations review
`
Stage 4: Development
9. Implementation
`
Stage 5: Release
10. Landing criteria
` {{#set:Feature open issues and risks=` |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. |Feature users and 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. |Feature dependencies=Pulse: Observing new patches in bugzilla is probably best done through pulse.
IT: The observer needs some hardware to run on. |Feature requirements=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. |Feature non-goals=Non-goals would be r+ or r- on patches. |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}
Feature details
| Priority | Unprioritized | 
| Rank | 999 | 
| Theme / Goal | ` | 
| Roadmap | ` | 
| Secondary roadmap | ` | 
| Feature list | ` | 
| Project | ` | 
| Engineering team | ` | 
{{#set:Feature priority=Unprioritized
|Feature rank=999 |Feature theme=` |Feature roadmap=` |Feature secondary roadmap=` |Feature list=` |Feature project=` |Feature engineering team=` }}
Team status notes
| status | notes | |
| Products | ` | ` | 
| Engineering | ` | ` | 
| Security | ` | ` | 
| Privacy | ` | ` | 
| Localization | ` | ` | 
| Accessibility | ` | ` | 
| Quality assurance | ` | ` | 
| User experience | ` | ` | 
| Product marketing | ` | ` | 
| Operations | ` | ` | 
{{#set:Feature products status=`
|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}