A few weeks ago we conducted a pilot survey with a diverse set of localizers in various roles to know more about the expectations around localization roles. At the same time the l10n-drivers staff also did a similar internal exercise to share their perception of the responsibilities and expectations unique to each of these roles.
Once we received data from both community and l10n-drivers, we created a perceived priority point system. Items voted as top priority received 2 points, medium priority received 1 point, and low priority received 0 points. Points were weighed equally between community opinion and l10n-drivers opinion, meaning that items could receive a maximum of 4 points (2 from community, 2 from l10n-drivers) and a minimum of 0. The result of all this work is a merged opinion about localization roles responsibilities and expectations.
Important: This is just a proposal for discussion and we know the initial survey doesn’t represent all localizers, we wanted to have a first take to be able to present an initial draft and start a conversation about it.
Note Responsibilities are defined as what you commit to by accepting the role and expectations are defined as how you carry yourself in the role.
- Establish mentorship practices for new localizers that foster growth and lead to impactful participation.
- Identify and train community mentors in their role.
- Coordinate translation and l10n testing of projects within the l10n community.
- Evaluate candidates for increased roles within the community.
- Coordinate and facilitate internal community discussions.
- Create and maintain language resources for the community (e.g., terminology, style guides, etc.)
- Open and frequent communication (liaison between l10n-drivers and l10n community) concerning new projects, new deadlines, and community issues.
- Create and secure a safe space for people to participate in l10n in an impactful way.
- Recruit and mentor new localizers.
- Give timely feedback to community mentors and translators.
- Submit translations for new source language content.
- Review pending translation suggestions from contributors and provide them with timely feedback that focuses on developing skills.
- In-context l10n testing of all submitted translations.
- Work with managers to create and maintain language resources for the community.
- File bugs concerning source language content issues.
- Ensure consistent quality of the project they’re localizing.
- Give detailed feedback to contributors in a timely manner.
- Translate new content regularly.
- Ensure that community style guidelines are being kept in translations that make it to the repositories.
- Keep pending translation suggestion queue to a low number.
- Gracefully accept feedback on their translations from other translators and managers.
- Submit translation suggestions to Pontoon projects for the target language.
- Request and accept feedback from Translators and Managers in the community.
- In-context review (l10n testing) of translation suggestions that have been approved by Translators and Managers.
- Gracefully accept feedback on their translations from Translators and Managers.
- Avoid using machine translation.
- Proactively request feedback from Translators and Managers.
- Doesn’t take shortcuts to increasing leaderboard standings.
- Network and form relationships with others in the community.
Please, share with us here:
How do you feel about this proposal?
Which points do you feel more important?
Are we missing anything?
We will keep this conversation open until 4 May, after that we will gather all feedback and include it in a final version.
Thanks for your opinion!