L10n:Features/Web/Locale Repository
Status
| Locale Repository | |
| Stage | Draft |
| Status | ` |
| Release target | ` |
| Health | OK |
| Status note | ` |
{{#set:Feature name=Locale Repository
|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 is a host of data around locales like language names, region names, plural rules etc that are used all around in Mozilla, in all of our languages.
This is supposed to be the central repository for those, unifying what's currently in product-details and in toolkit, extending it to the full range of data.
The data is supposed to be what our l10n community says it should be.
2. Users & use cases
Toolkit features that need to list language and region names like dictionaries, accept-language header UI etc. as well as websites that need to display region and language names.
3. Dependencies
`
4. Requirements
API: Expose a set of language names and region names for a set of languages.
Repository: Store as many of those, editable by our locale leaders.
Not necessarily in the initial phase: Expose known conflicts so that mozillians are aware that there are conflicts, and that a particular decision has been made knowing about it.
Non-goals
World Peace. Literally. All the data in here is confrontational and it's good to have a repository where we have those conflicts dealt with. That's not resolved, just dealt with.
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 is a host of data around locales like language names, region names, plural rules etc that are used all around in Mozilla, in all of our languages.
This is supposed to be the central repository for those, unifying what's currently in product-details and in toolkit, extending it to the full range of data.
The data is supposed to be what our l10n community says it should be. |Feature users and use cases=Toolkit features that need to list language and region names like dictionaries, accept-language header UI etc. as well as websites that need to display region and language names. |Feature dependencies=` |Feature requirements=API: Expose a set of language names and region names for a set of languages.
Repository: Store as many of those, editable by our locale leaders.
Not necessarily in the initial phase: Expose known conflicts so that mozillians are aware that there are conflicts, and that a particular decision has been made knowing about it. |Feature non-goals=World Peace. Literally. All the data in here is confrontational and it's good to have a repository where we have those conflicts dealt with. That's not resolved, just dealt with. |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=` }}