L10n:Goals/Q3 2016

Roundtable

Delphine

• Become more competitive with localization coverage on Android
  • Deliverable: Revive 2 in-active/low-activity locales to 100% completion on Fennec localizations

• More locale coverage on iOS
  • Deliverable: Add at least 2 new locales to iOS

• Gain autonomy in Fennec workflow
  • Deliverables:
    • Adding new locales on both Fennecs
    • Managing both App Stores in an autonomous manner
    • Adding new fennec projects for locales to Pontoon

gandalf

Switch one Firefox feature to use L20n

With a new contractor on board, and 3rd edition released, the focus is now on 4th edition where Mozilla is pushing for a bunch of new APIs. For this quarter, I'd like to get `formatToParts` included in the spec, with tests, and advance PluralRules and ListFormat.

Progress ECMA 402 specificiation

By the end of this quarter we will have at least one Firefox feature switched from the old l10n infrastructure to l20n.

This requires:

* Landing L10nRegistry
* Landing MessageContext
* Landing html/xul/xbl bindings

For all of those items we will have to:

* write tests
* prove performance (on par or better)
* develop QA strategy for collecting data back from users (telemetry)

Matjaž

* Development
 * [ ] Redesign dashboards with all data from elmo & webdashboard
 * [ ] Implement UI for advanced FTL (L20N) features
 * [ ] Replace Persona with Firefox Accounts
 * [ ] Add terminology support using Microsoft Terminology as source
 * [ ] Implement in-app notifications informing user about new strings
 * [ ] Read translation authors from commit authors
* Engagement
 * [ ] Announce 3 new features on l10n blog (what's up next, how to get invovled)

Pei

• More tightly integrated within product teams: Establish a routine with the cadence cycle, communicate when there are issues, understanding the technical aspect of each localization request.
• Localization process: Have a clear definition on how to make contribution to localization (both new localization and new localizers) and an instructional pathway to being successful contributing to localization.
• Mozilla Foundation support: Mentor adoption of standard l10n tool support and process.

Pike

• elmo
  • update to stable django
  • automation off of buildbot
• l20n
  • get l20n landed in gecko
  • mostly automation and elmo work

Stas

Port and land one UI feature of Firefox Desktop to L20n

This is The Deliverable. Many dependencies need to be coordinated to land even a smallest UI feature of Firefox: translation syntax, support in authoring tools, support in l10n dashboards, support in build infrastructure, the runtime library, resource loading, language negotiation, and—finally—porting the code of the chosen UI feature.

The current candidates include the About window or the about:support page.

Measure the performance impact of L20n on Firefox's startup

We need to produce performance numbers on how L20n affects the startup of Firefox. We are going to create a branch and transition a feature of Firefox which is on the perf-critical startup path (tpaint test in Talos). See bug 1280677.