L10n:Goals/H1-2019: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 21: Line 21:
=== Jeff ===
=== Jeff ===
Publish new service level agreements for localization team.
Publish new service level agreements for localization team.
    *Creating a new draft of the Localization Mana page around the team's purpose, processes, and SLAs.
*Creating a new draft of the Localization Mana page around the team's purpose, processes, and SLAs.
    *Create official project request intake pipeline through standard Mozilla channels.
*Create official project request intake pipeline through standard Mozilla channels.
    *Managing feedback rounds with l10n team, eng ops leadership, executive leadership, and internal clients.
*Managing feedback rounds with l10n team, eng ops leadership, executive leadership, and internal clients.
    *Refining Mana doc with each feedback round.
*Refining Mana doc with each feedback round.
    *Creating comms strategy for the update.
*Creating comms strategy for the update.
    *Publishing doc and executing on comms strategy.
*Publishing doc and executing on comms strategy.


=== Matjaž ===
=== Matjaž ===

Revision as of 12:27, 15 March 2019

Team Goals

Roundtable

Axel

Delphine

Flod

Reduce the amount of work required by Fluent reviews for mozilla-central:

  • [] Identify tasks that can be automated via linting and tests.
  • [] Create documentation for reviewers describing common problems and expectations.
  • [] Drop the mandatory review for FTL files by end of H1.

Ensure team’s productivity and success in Q2 while standing in as a manager.:

  • [] Ensure that at least 70% of the team OKR defined for Q2 are completed.
  • [] (Personal growth) Use feedback and experience to identify areas where I need to invest for personal growth, evaluate becoming a manager as a potential career path, and use this information to define an Individual Development Plan in H2.

Jeff

Publish new service level agreements for localization team.

  • Creating a new draft of the Localization Mana page around the team's purpose, processes, and SLAs.
  • Create official project request intake pipeline through standard Mozilla channels.
  • Managing feedback rounds with l10n team, eng ops leadership, executive leadership, and internal clients.
  • Refining Mana doc with each feedback round.
  • Creating comms strategy for the update.
  • Publishing doc and executing on comms strategy.

Matjaž

Peiying

Stas

Adrian

Theo (optional)