We're structuring the roadmap by the lifecycle of a localization project.
- no downtime on project changes
- single source of truth of current and past projects
- a group maintains the set-up, no single source-of-failure
We strongly recommend to use L20n for all projects.
mozilla.org uses .lang files.
Other projects should use XLIFF, or even .po (gettext).
- just ONE SINGLE dashboard
- response times should be quick
- support variety of file formats directly
- ftl (l20n)
- XLIFF
- .po
- DTD
- .properties
- .lang
- all projects should be available in at least one translation tool
These are the projects we're working on right now, in addition to general bug fixes.
- land in gecko, used in Firefox and Firefox for Android.
- elmo-pontoon merger
- cross-channel firefox l10n