L10n:Goals/H2-2018

Team Goals

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

• Fluent in Gecko - Zibi, Ax, F, S
• Multilingual Firefox - Flod, Z, J, Ax
• Fluent 1.0 - Stas, Z, Ax
• New brand translation policy - Peiying, Z, F, D
• compare-locales in Pontoon - Matjaz
• Pontoon translate view in React/Fluent - Adrian
• Android strings.xml - Axel, M, D

Roundtable

Axel

• Cross-channel for git and Android projects
  • Supporting Android strings.xml
  • Generate a single repository with all Android strings
    • Focus/Klar, Firefox for TV
    • Optional, TBC: Rocket
• Support for Strings.xml in compare-locales
  • Supporting Android strings.xml
  • tier0 and tier1, https://bugzilla.mozilla.org/buglist.cgi?bug_id=1472157%2C1473577%2C1465342%2C1472150%2C1466088%2C1465341%2C1465517%2C1466836%2C1472149%2C1465711
• Support for Android Components
  • Supporting Android strings.xml
  • Multiple strings.xml files against one cross-channel
  • Multiple reference files for one localized file support in compare-locales

Jeff

Workday goals

Internal terminology management workflow will be streamlined.

Corresponding OKR: Establish consistent practice of managing Mozilla terminology for all products and brand/product names.

This goal will be completed when:

• We define requirements for a terminology management solution.
• We evaluate at least 3 candidate solutions against our requirements.
• We make a selection and formulate/execute a migration plan for existing terminology data.
• We educate UX, SUMO, and others on using the solution and define an effective, streamlined pipeline for proposing, evaluating, and finalizing new terms.
• We create a product requirement document (PRD) for terminology management in Mozilla l10n toolchain to determine the investment and its return if we were to build our own solution.

L10n team is ready to scale localization for more mobile projects on faster timelines.

Corresponding OKR: Android products can be rapidly bootstrapped and continuously localized.

This goal will be completed when:

• Existing technical pain points in mobile l10n projects have been identified and scoped.
• We can predict scale challenges in human overhead and technical inefficiencies.
• We have a plan to account for scale challenges that is approved by leadership.

Matjaž

• Make localizer-critical data available in Pontoon
  • Implement support for errors and warnings in dashboards and filters
  • Implement file-level priorities
  • Implement file-level deadlines
• Improve path to first contribution to localization at Mozilla
  • Implement new Pontoon homepage (mentor a GSoC student)
  • Implement new main menu for the translate view
  • Implement the ability to request a new locale through Pontoon
• Organize a design sprint to design a translation feedback solution
• Become comfortable with using Translate.next technologies
• Add support for XML file format used in Android

Stas

• Release Fluent 1.0
  • Fluent Syntax 1.0 Spec is published.
    • The reference parser is used to validate the spec.
    • The Syntax Guide is up-to-date.
  • Implementations have been updated to Syntax 1.0.
    • The runtime fluent module.
    • The tooling fluent-syntax module.
    • The python-fluent module.
  • L20n is deprecated.

Adrian

• [Translate.Next] Rewrite Translate into a Single Page Application
  • Key Result: All of Pontoon’s translate view UI is re-written using React and is internationalized using fluent-react.
  • All features from current Translate application are ported to the new one
  • 100% of the code uses React and other efficient front-end technologies
  • All new code is fully localizable
  • All new code is unit tested and has decent code coverage (> 80%)

• [Translate.Next] Improve the review process
  • Key Result: Translators and managers can give translation feedback when testing and reviewing translations within Pontoon.
  • Design a better review process for translations
    • Design 2 ideas for an improved review process
    • Organize a local community meetup to test, improve, and choose the better option
    • Define scope for the implementation of the chosen option

• Non-Workday goals
  • Mentor a GSoC student
  • Implement the review process that has been chosen with the community
  • Organize testing of the new review process with the larger community