L10n:Goals/Q3 2017

Team Goals

Please ensure that individual goals (all or part) are contributing to our OKRs for this year. Citing the OKR that your Q3 goal contributes to in your goal section is preferred.

• 2017 OKRs for localization

Roundtable

Axel

Deliver cross-channel localization infrastructure

• [ ] Initial Repository for Fx, Fx Android, Thunderbird (w/ calendar), SeaMonkey
• [ ] Update logic to incrementally update the initial repository with new landings
• [ ] Test infrastructure on m-c to ensure all the constraints that x-channel brings
• [ ] Automated updates to upstream repository
• [ ] Support new config in elmo, add support for x-channel automation
• [ ] (releng) Deploy changes in automation to pick up x-channel l10n repos

Host l10n automation and l10n.m.o on the cloud

• TBD on the scope of the action, options are existing infra on AWS, or new automation infra on TC

Flod

Firefox Desktop

• [] Support localization for Firefox 57: Photon, Activity Stream and Firefox Screenshots integration in the browser.
• Support cross-channel repository initiative through:
  • [] (from Q2) Initial testing and support.
  • [] (from Q2) Creating documentation for new processes.
  • [] (from Q2) Adding support for cross-channel repository in Transvision.
  • [] (from Q2) Starting discussion with release management about shipping updates on release and ESR channels.
• [] (from Q2) Support DevTools move to an external GitHub repository.

Other products, tools, support for mozilla.org and mobile

• Documentation:
  • [] Complete Q3 tasks in documentation: How to drop a locale.
  • [] Complete Q3 tasks in localizer-documentation: How to use Pontoon, How to test Firefox desktop.
  • [] Clean up documentation (Pudelo).
• [] (ongoing) Support Test Pilot experiments and system add-ons (review, localization setup, infrastructure).
• [] Clean up tools (Pudelo).

Back-burner

• [] (from Q2, blocked by new project configurations) Get string tiers implemented in tools (Pootle, Pontoon).
• [] (ongoing) Identify inactive locales, reach out to them, try to find new contributors, remove them from builds if that fails (long term goal for 2017).

Gandalf

1. Run the 2nd round of feedback on Fluent (frameworks&platforms)
2. Develop an MVP version of Fluent Rust
3. Land Fluent Localization and FluentDOM in Gecko

Jeff

• Create and run pilots of new workshop formats for Asunción and Berlin.
• Gather team input and create plan for our 3-day work week in Berlin.
• Start cross-functional localization taskforce.
• Planning for 2018 budget and team strategy.

Stas

1. Add a solution for localizing DOM fragments to fluent-react. (3 weeks)

Related objective: Prepare Firefox desktop for implementation of next gen l10n framework & new i18n standard specifications after launch of Quantum.

 [ ] Review the solution currently implemented in fluent-dom.
 [ ] Research current solutions in other i18n libraries for React
 [ ] Research approaches to parsing HTML in translations
 [ ] Implement
 [ ] Write tests and documentation

2. Implement Fluent 0.3 resolver spec in fluent-rs (3 weeks)

Related objective: Prepare Firefox desktop for implementation of next gen l10n framework & new i18n standard specifications after launch of Quantum.

 [ ] Support ExternalArguments: only strings and numbers for now
 [ ] Support VariantExpression
 [ ] Support AttributeExpression
 [ ] Support SelectExpression
 [ ] Support Tags as selectors
 [ ] Support CallExpression

3. Create fluent-lint for linting FTL files and autofixing them (2 weeks)

Related objective: Prepare Firefox desktop for implementation of next gen l10n framework & new i18n standard specifications after launch of Quantum.

 [ ] Create a set of rules for formatting, whitespace and indentation, called Fluent Standard.
 [ ] Create a tool for reporting linting errors in FTL files.
 [ ] Add an option to autofix linting errors.

4. Create a v1 of the API endpoint supporting queries related to aggregate statistics per locale and per project (2 weeks)

Related objective: Optimize and streamline the string life cycle for throughput efficiency to maximize community localizer impact, output, and quality (i.e., continuous localization).

 [ ] Document research on REST and GraphQL
 [ ] Make an informed decision and choose one
 [ ] Implement the chosen solution
 [ ] Help build a simple dashboard (e.g. using processeer.io) to visualize the data described in bug 1302053

Kekoa

Asset Analysis

• [] Create general termbase for Mozilla.org and FireFox
• [] Migrate current style guides to Gitbook
• [] Make style guides accessible to and manageable by communities

Documentation

• [] Resources for Translation
• [] How to Localize in Pontoon

Pontoon

• [] Design and implement terminology management in Pontoon UI