|
1 | | -# Roles within Mozilla l10n communities |
| 1 | +# Roles and guidelines in the localization community |
2 | 2 |
|
3 | | -Within Mozilla l10n communities, each individual is organized into one of three roles: Locale manager, Translator, Contributor. These roles reflect the community structure within Pontoon as well. Each l10n community has its own unique implementation of these roles, but there is a baseline set of responsibilities and expectations that Mozilla places on those contributing to localization. |
| 3 | +Volunteer communities are the backbone of the localization (l10n) efforts at Mozilla. They are designed to be self-regulating and self-managing with minimal intervention from staff. For example, the responsibility of reviewing suggestions falls on the Translators and Managers within the community; they not only ensure quality and consistency but also keep an eye out for potential new volunteers to promote. And when Managers plan to step down, it’s crucial they develop succession plans to maintain continuity. |
4 | 4 |
|
5 | | -This document defines the roles within each l10n community, as well as the responsibilities and expectations of each. We also define what the l10n-driver responsibilities and expectations are with regard to the community as a whole. Here we define responsibilities as what each individual commits to by accepting their role in the community. We define expectations as how you carry yourself in the role. |
| 5 | +The role of staff is to intervene only when necessary. The main reasons for staff to be involved is when self-regulation fails or there are violations of the [Community Participation Guidelines](https://www.mozilla.org/about/governance/policies/participation/) (CPG). The goal is to empower the communities to thrive independently while maintaining the high standards that Mozilla is known for. |
6 | 6 |
|
7 | | -## L10n-drivers (Mozilla staff) |
| 7 | +The localization team can occasionally take a more hands-on approach, proactively engaging with locales that are facing challenges. For example, it can happen when a member (or members) of a locale reaches out directly to localization staff to express concerns about their community. Other times, the team may receive product requests for specific locales, which prompts initiatives to ensure that these communities are capable of supporting the product expansion. |
8 | 8 |
|
9 | | -L10n-driver responsibilities and expectations are multifaceted, being that in addition to being accountable to the community, we’re accountable to Mozilla leadership as well as the many teams throughout Mozilla that we support with localization. This section describes how the l10n-drivers are accountable to the community. |
| 9 | +In the following sections, we’ll review the current roles and expectations and suggest guidelines for when role criteria are not met — and how the localization staff can get involved and help in these different scenarios. |
10 | 10 |
|
11 | | -### Responsibilities |
| 11 | +## Roles: responsibilities and expectations |
12 | 12 |
|
13 | | -* Mentor new l10n communities through the process of launching a new localized Mozilla product. |
14 | | -* Communicate project updates and participation invitations in primary communications channels, like the dev-l10n mailing list and IRC. |
15 | | -* Respond to reports of CPG violations within the community. |
16 | | -* Create and guarantee a safe, collaborative space for all communities. |
17 | | -* Work with l10n communities to increase the user base for their localizations. |
18 | | -* Perform technical validation of contributions from the community to determine whether to ship contributions. |
19 | | -* Create and maintain tooling that promotes a healthy and simple localization workflow for the community. |
20 | | -* Recognize outstanding contributions made by the community. |
21 | | -* Promote translation and localization best practices within the project. |
| 13 | +### Managers |
22 | 14 |
|
23 | | -### Expectations |
| 15 | +#### Responsibilities |
24 | 16 |
|
25 | | -* Promote the growth and health of each l10n community. |
26 | | -* Represent and advocate for the needs of the l10n community to the Mozilla organization. |
27 | | -* Respond positively to ideas for l10n improvements from the community. |
28 | | -* Utilize open communication channels at every opportunity. |
29 | | - |
30 | | -## Locale manager |
31 | | - |
32 | | -### Responsibilities |
| 17 | +On top of the responsibilities associated with the Translator role: |
33 | 18 |
|
34 | 19 | * Establish mentorship practices for new localizers that foster growth and lead to impactful participation. |
35 | 20 | * Identify and train community mentors in their role. |
36 | 21 | * Coordinate translation and l10n testing of projects within the l10n community. |
37 | | -* With input and consultation with Translators, evaluate candidates for advanced roles within the community. |
| 22 | +* Provide input and consultation with localizers, evaluate candidates for advanced roles within the community. |
38 | 23 | * Coordinate and facilitate internal community discussions. |
39 | 24 | * Create and maintain language resources for the community (e.g., terminology, style guides, etc.). |
40 | 25 |
|
41 | | -### Expectations |
| 26 | +#### Expectations |
42 | 27 |
|
43 | 28 | * Open and frequent communication (liaison between l10n-drivers and l10n community) concerning new projects, new deadlines, and community issues. |
44 | 29 | * Create and secure a safe space for people to participate in l10n in an impactful way. |
45 | 30 | * Recruit and mentor new localizers. |
46 | 31 | * Give timely feedback to community mentors and translators. |
47 | 32 |
|
48 | | -## Translator |
| 33 | +### Translators |
49 | 34 |
|
50 | | -### Responsibilities |
| 35 | +#### Responsibilities |
51 | 36 |
|
52 | | -* Submit translations for new source language content. |
| 37 | +* Submit translations for new content. |
53 | 38 | * Review pending translation suggestions from contributors and provide them with timely feedback that focuses on developing skills. |
54 | | -* In-context l10n testing of all submitted translations. |
55 | | -* Work with managers to create and maintain language resources for the community. |
| 39 | +* Testing of all submitted translations in product. |
| 40 | +* Work with Managers to create and maintain language resources for the community. |
56 | 41 | * Report issues concerning source language content issues. |
57 | 42 |
|
58 | | -### Expectations |
| 43 | +#### Expectations |
59 | 44 |
|
60 | 45 | * Ensure consistent quality of the project they’re localizing. |
61 | 46 | * Give detailed feedback to contributors in a timely manner. |
62 | 47 | * Translate new content regularly. |
63 | 48 | * Ensure that community style guidelines are being followed in translations that make it to the repositories. |
64 | 49 | * Keep pending translation suggestion queue to a low number. |
65 | | -* Gracefully accept feedback on their translations from other translators and managers. |
| 50 | +* Gracefully accept feedback on their translations from other Translators and Managers. |
66 | 51 |
|
67 | | -## Contributor |
| 52 | +### Contributors |
68 | 53 |
|
69 | | -### Responsibilities |
| 54 | +#### Responsibilities |
70 | 55 |
|
71 | 56 | * Submit translation suggestions to Pontoon projects for the target language. |
72 | 57 | * Request and accept feedback from Translators and Managers in the community. |
73 | 58 | * In-context review (l10n testing) of translation suggestions that have been approved by Translators and Managers. |
74 | 59 |
|
75 | | -### Expectations |
| 60 | +#### Expectations |
76 | 61 |
|
77 | 62 | * Gracefully accept feedback on their translations from Translators and Managers. |
78 | | -* Avoid using machine translation. |
| 63 | +* Avoid relying exclusively on machine translation, especially when unsure about the source string or the language. |
79 | 64 | * Proactively request feedback from Translators and Managers. |
80 | | -* Don’t take shortcuts to increasing leaderboard standings. |
81 | 65 | * Network and form relationships with others in the community. |
82 | 66 |
|
83 | | -## Implementation |
| 67 | +## Guidelines |
| 68 | + |
| 69 | +### Promotions |
| 70 | + |
| 71 | +Promotions apply to Translators and Contributors. Managers and localization staff can directly [promote/demote users](../tools/pontoon/users.md#managing-permissions) to Translator or Manager roles. |
| 72 | + |
| 73 | +#### Efforts to revive an inactive community |
| 74 | + |
| 75 | +A community is considered inactive when there are no other active Translators or Managers, which can make it difficult for Contributors to participate effectively. If a Contributor has attempted to reach out to the Managers or Translators but has not received a satisfactory response (or any response) within a few weeks, it’s advisable to [contact the localization staff](#how-can-i-contact-the-localization-staff) for assistance. Each situation is unique, and staff can help investigate further, for example reviewing a localizer’s contribution history across external localization projects outside of Mozilla. The localization team will also reach out to former Managers and Translators for their input. If there is still no response, the localization team will consider promoting active localizers who have expressed interest in taking on an active role. |
| 76 | + |
| 77 | +#### Community engagement |
| 78 | + |
| 79 | +Localizers who actively participate in community discussions, provide feedback and reviews, mentor new members, and engage in localization events and workshops should be recognized and promoted for their dedication and leadership within the community. They often transition from direct translation work to more managerial roles, focusing on building and enabling the locale community. |
| 80 | + |
| 81 | +How do you recognize and promote them? Existing locale Managers are typically in charge of updating the permissions on Pontoon. Staff will step in if there are reasons preventing a person from reaching the next role (for example, if there are no active Managers, or if there is [gatekeeping](#gatekeeping)). |
| 82 | + |
| 83 | +In the case there is no existing community, a localizer requesting a new locale will be appointed to the Manager role. |
| 84 | + |
| 85 | +#### High-quality contributions |
| 86 | + |
| 87 | +A localizer who consistently provides high-quality translations that meet the community’s standards should be considered for promotion. This includes accuracy, adherence to style guides, and timely contributions and reviews. Contribution data on Pontoon can be used to help guide these decisions. |
| 88 | + |
| 89 | +### Demotions |
| 90 | + |
| 91 | +Demotions should come as a last resort when a localizer’s actions significantly impact the project’s quality, collaboration, or community. In practice demotions are extremely rare and historically have occurred when a Manager or Translator voluntarily expresses a desire to step back from their roles and expectations. |
| 92 | + |
| 93 | +Here are some examples of reasons for demotion. |
| 94 | + |
| 95 | +#### A localizer wants to take a step back |
| 96 | + |
| 97 | +As explained, a request for demotion can come from localizers themselves, when they want to delegate certain responsibilities. This is a straightforward scenario, in which a localizer typically will reach out to the manager — or localization staff — to express their desire to step down. Managers have the permissions to do so themselves, but localization staff can also assist. |
| 98 | + |
| 99 | +#### A localizer is failing to meet role expectations |
| 100 | + |
| 101 | +A localizer might notice that a Manager or Translator is abusing their role, especially in ways that may be considered [gatekeeping](#gatekeeping). After the community has tried to get in touch with the Managers or Translators, but has not received a satisfactory response (or any response) after a few weeks, [reaching out to the localization staff](#how-can-i-contact-the-localization-staff) is a good first step for the team to help investigate and find solutions, as each situation is unique. Note that the localization team rarely demotes anyone unless it’s a grave situation, but they can help promote or unblock users. |
| 102 | + |
| 103 | +#### Prolonged inactivity |
| 104 | + |
| 105 | +Typically there isn’t a need to demote a Manager or Translator due to inactivity, unless [gatekeeping](#gatekeeping) or retaliation disrupt the work of others. |
| 106 | + |
| 107 | +### Community guidelines enforcement |
| 108 | + |
| 109 | +#### CPG violation |
| 110 | + |
| 111 | +A CPG violation is taken very seriously and will be addressed immediately. The process for reporting a violation is detailed under the “Reporting” section of the [CPG](https://www.mozilla.org/about/governance/policies/participation/). |
| 112 | + |
| 113 | +#### Gatekeeping |
| 114 | + |
| 115 | +Gatekeeping can show up in different ways in localization communities/localizers: |
| 116 | + |
| 117 | +* Not reviewing new Contributors’ work, which prevents them from joining and contributing. |
| 118 | +* Self-reviewing their own work and ignoring the work done by others — or constantly rejecting others’ contributions as not good enough to maintain control over the locale. |
| 119 | +* Creating unnecessary barriers to participation, like setting very strict standards without offering guidance or feedback, holding onto knowledge or resources instead of sharing with the community, and resisting changes or improvements suggested by others without explanation. |
| 120 | +* Being inactive for a long period of time, but nonetheless never wanting to give permissions to others actively participating. |
| 121 | +These actions limit the growth and diversity of the community, making it less welcoming and inclusive. |
| 122 | + |
| 123 | +How does the localization team know someone is gatekeeping? This can happen through direct feedback, or through the localization team’s own investigations. |
| 124 | + |
| 125 | +If a localizer has attempted to reach out to Managers or Translators but has not received a satisfactory response (or any response) within 2 weeks, it’s advisable to contact the localization staff for assistance. |
| 126 | + |
| 127 | +## Common issues and references |
| 128 | + |
| 129 | +### How can I contact the localization staff? |
| 130 | + |
| 131 | +If you have contacted members of your team and received no responses, have questions about these guidelines or want to suggest improvements, don’t hesitate to get in touch with the localization staff: |
| 132 | + |
| 133 | +1. You can use [email](mailto:pontoon-team@mozilla.com) and [Matrix](https://matrix.to/#/#l10n-community:mozilla.org) to reach out to the entire team. |
| 134 | +2. You can also find the member of staff in charge of each project [directly in Pontoon](../tools/pontoon/teams_projects.md#project-page). |
| 135 | + |
| 136 | +### I am a Translator and want to become a Manager, what do I do? |
| 137 | + |
| 138 | +Try to get in touch with the current Managers and Translators from your locale, to surface your request (you can find them under the Contributor view in your [team page](../tools/pontoon/teams_projects.md#teams-page) on Pontoon). Check also the [Promotions](#promotions) section. You can also [reach out to the localization team](#how-can-i-contact-the-localization-staff) directly. |
| 139 | + |
| 140 | +### No one is reviewing my suggestions, what do I do? |
| 141 | + |
| 142 | +Try to get in touch with the current Managers and Translators from your locale, to surface your request (you can find them under the Contributor view in your team page on Pontoon). You can also [reach out to the localization team](#how-can-i-contact-the-localization-staff) directly. |
| 143 | + |
| 144 | +### I’m a new Contributor and am interested in becoming a Translator for only one project. |
84 | 145 |
|
85 | | -Each community implements these roles according to their own cultural and unique situations, in accordance with the [Mozilla Community Participation Guidelines](https://www.mozilla.org/en-US/about/governance/policies/participation/) and Mozilla Leadership Agreements. For example, in some smaller communities, everyone may be Managers and the responsibilities for the role are shared among them. In other communities, there may be one Manager, several Translators, and many Contributors. We respect each community’s rights to implement these roles as best works for them, within the constraints mentioned above. |
| 146 | +Get in touch with the locale Managers first, to ask them to appoint you to only one project. If there is no response within a few weeks, [reach out to the localization team](#how-can-i-contact-the-localization-staff). |
86 | 147 |
|
87 | | -Evaluating whether someone should move into a more advanced role should be done by consulting with other experienced localizers within the community, not in a vacuum. Typically, a localizer is ready for a role change member when they have proven themselves to satisfy the responsibilities and expectations of their current role and even go above and beyond what’s expected. When considering someone for a role change, consider the responsibilities of the new role and how the candidate localizer will perform in that role. For example, when considering moving a Translator to a Manager, consider if they have mastered the responsibilities and expectations of a Translator first and whether they have the skills to successfully master the responsibilities and expectations of a Manager. Translating fluently and in a timely manner may be applicable to evaluating them as a Translator, but not as relevant to evaluating them as a Manager. |
| 148 | +### How can I delete my Pontoon account? |
88 | 149 |
|
89 | | -These evaluations should be done regularly and mentored feedback should be given to teach community member regularly. |
| 150 | +Currently users cannot remove their account directly from Pontoon. [Reach out to the localization team](#how-can-i-contact-the-localization-staff). |
0 commit comments