Contribute/L10n/Team Health Evaluations

Below you will find goals and criteria for performing l10n team health evaluations. Because of the self-governing nature of our l10n teams and various tool sets they use to execute their l10n efforts, it is very difficult to get a "bird's eye" look of any given l10n team's overall health and status. We hope to resolve that by periodically checking in with each team, evaluating their status based on the criteria below, and recording these evaluations in a high-level dashboard and on each team's wiki page. The criteria and goals are not set in stone and can be adjusted according to the needs of round of evaluations.

Q4 2012 Goals

• Accurately evaluate and record health of each l10n team.
• Get all teams to update their wiki pages.
• Get all l10n contributors into mozillians phonebook under L10N and L10N:[locale-code] groups.
• Identify those with potential to gain hg/SVN commit access and make plans to help them.

Recording health assessments

• Consolidate table on https://wiki.mozilla.org/L10n/Community
  • Columns:
    • Locale code with link to ELMO dashboard
    • Lang name with wiki page link & state color
    • State of health
    • Region (EU, Asia, LATAM, Africa/Mid-east)
    • Hg/SVN access (Y/N & #) (?+-)
    • Links to online tools used
    • Offline tools used
    • Link to onboarding process
    • Links to l10n assets
    • Remo
    • Needs
• Legal or community issues (e.g., Tamil and Balkans)
• Track names of people who have attended MozCamp.
• Use as bird's eye view of l10n health based on determined criteria.
• Recorded assessment for each team on their individual team wiki page.

States of health

Dead (red)

• Outdated contact info on team wiki page.
• No logged activity in 1+ years based on view of:
  • Bugzilla
  • Push logs
  • Dashboards from online tools (e.g., Narro, Verbatim, locamotion Pootle, Webdashboard)
• No team member responds to attempts to contact
• No onboarding process for new contributors.
• No l10n assets.

Innactive (red-orange)

• Team wiki page does not have new template applied to it.
• Very limited activity in >6 months based on view of:
  • Bugzilla
  • Push logs
  • Dashboards from online tools (e.g., Narro, Verbatim, locamotion Pootle, Webdashboard)
• No team member responds to attempts to contact.
• No onboarding process for new contributors.
• Some l10n assets.

Moderately active (yellow)

• Team wiki page does not have new template applied to it, but no content updates.
• Very limited activity in >3 months based on view of:
  • Bugzilla
  • Push logs
  • Dashboards from online tools (e.g., Narro, Verbatim, locamotion Pootle, Webdashboard)
• Team members respond to attempts to contact via email, but unwilling to speak in call.
• No onboarding process for new contributors.
• Some l10n assets.

Active (green)

• Team wiki page has new template applied and content updates within the last 3 months.
• Visible activity based on view of:
  • Bugzilla
  • Push logs
  • Dashboards from online tools (e.g., Narro, Verbatim, locamotion Pootle, Webdashboard)
• At least 1 person has hg & SVN commit access.
• Regularly shipping all projects which they have currently undertaken on time.
• Occassional recruiting done for new localizers, but without solidified onboarding process or desired skill sets for new localizers.
• Maintains l10n assets like:
  • TM
  • Bilingual glossary of terms

Peak (blue)

• Team wiki page has new template applied and updates content regularly to include new localizers.
• More than 2 people have hg & SVN commit access.
• Regularly shipping all projects which they have currently undertaken on time with willingness to take more.
• Regular recruiting done for new localizers which is based on solidified onboarding process and desired skill sets for new localizers.
• Maintains l10n assets like:
  • TM
  • Bilingual glossary of terms and/or termbase
  • Locale style guide
• Mentors other l10n teams.

Identify the key/active contributors of each team

• All info must be as outlined in wiki team page template. Names, numbers for each team, designations (e.g., localizer in training, team leader, etc.).
• All contributors need to be signed up in mozillians phonebook under L10N and L10N:[locale-code] groups.

Keep track of people with commit access

• Commit Access Sample bug: https://bugzilla.mozilla.org/show_bug.cgi?id=741305
• Identify teams that need commit access.

Assignments for Q4 2012

• Jeff & Arky to talk to all Indian teams and Asian locales in person at MozCamp Asia.
• Jeff = all LATAM teams.
• Jeff = Western European teams
• Arky = Eastern European teams
• Arky = Middle Eastern teams
• Jeff = African teams