Welcome to the official blog of the translator team for the WordPress open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project. This is where we discuss all things related to translating WordPress. Follow our progress for general updates, status reports, and debates.
We’d love for you to help out!
You can help translate WordPress to your language by logging in to the translation platform with your WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ account and suggesting translations (more details).
We have meetings every week on SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. in polyglots (the schedule is on the sidebarSidebarA sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. of this page). You are also welcome to ask questions on the same channel at any time!
Expectations for translators and translation editorsTranslation EditorTranslation editors can approve translations for projects. The GTE (General Translation Editor) and LM (Locale Manager) roles can add new users with the "Project Translation Editor" role that can approve translations for specific projects. There are two different Translation Editor roles:
General Translation Editor and Project Translation Editor were a common piece of feedback I received in the Polyglots outreach effort. Most, if not all, teams wanted to set clearer expectations for new translators; other teams struggled with translation editors who were no longer available to help grow the team.
This reminded me of my previous exercise with the Make/Training team to define a contributor ladder. While the Polyglots teamPolyglots TeamPolyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. has clear roles—particularly because most roles are tied to permissions—I’m unsure of when expectations related to these roles were last discussed.
As a result of this feedback, I’d like to present my understanding of what a contributor’s progression may look like on the Polyglots team. In presenting this resource, I hope it can define current expectations for Polyglots contributors and potentially identify any gaps that may exist.
Communicates with local translation editors for feedback
Project Translation EditorProject Translation EditorA Project Translation Editor (often referred to as PTE) is a person, who has access to validate strings on a specific project (for example BuddyPress, WooCommerce or Twenty Fourteen) for one specific locale. A project translation editor can approve strings that are added by translation contributors. Per project translation, editors are appointed by a general translation editor after a request by the project author or by the contributors themselves. (Understanding/Engaging)
Responsible for maintaining specific translation projects in translate.wordpress.orgtranslate.wordpress.orgThe platform for contributing to the translation of WordPress core, themes and plugins., including translation review and feedback
General Translation EditorGeneral Translation EditorA General Translation Editor (often referred to as GTE) is a person, who has global access to validate strings on all projects for a specific locale. (Leading)
Sets priorities for their individual localeLocaleLocale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ team
Mentors and provides feedback to new translators
Maintains translation consistency, quality, and related resources (Glossary, Style Guide)
Locale Manager (Leading)
Manages the locale’s RosettaRosettaThe code name of the theme for the local WordPress sites (eg. bg.wordpress.org is a “Rosetta” site). All locale specific WordPress sites are referred to as “Rosetta sites.” The name was inspired from the ancient Rosetta Stone, which contained more or less the same text in three different languages. site, including adding or promoting users
Often performs many of the same activities listed under General Translation Editors
Global Mentor (Leading)
Helps set priorities for the global team
Provides mentorship for any/all locale teams and translation editors
Responsible for technical maintenance, e.g. new locale requests, communicating WordPress release schedule
In brainstorming the Polyglots team structure, two things stood out to me:
Some of the steps between roles are pretty large.
There’s a lot of responsibility for some roles.
With that in mind, I made a slightly revised map of the Polyglots team.
Revised Polyglots Roles
Contributors, especially translation editors, can ideally use many different skills at once to manage translations, maintain translation quality, highlight priorities, and still build the translation community. It’s a lot, especially with a small team!
Currently, the Polyglots Global Mentors have two sub-roles: a Global Mentor and a Tech Lead. Similarly, I’d like to propose distinct sub-roles for General Translation Editors:
Translation Quality → Review translations and proactively provide feedback to translators.
Community → Recruit and mentor translators.
Documentation → Maintain team documentation, such as the Glossary or local Handbooks.
Marketing → Coordinate local marketing efforts, such as translating /news posts.
Exploring ways to highlight expectations for Project Translation Editors in each locale may also be interesting. When approving a PTEProject Translation EditorA Project Translation Editor (often referred to as PTE) is a person, who has access to validate strings on a specific project (for example BuddyPress, WooCommerce or Twenty Fourteen) for one specific locale. A project translation editor can approve strings that are added by translation contributors. Per project translation, editors are appointed by a general translation editor after a request by the project author or by the contributors themselves., would it be helpful to share if they’re also expected to review and provide feedback on suggested translations for your locale? What might those expectations look like?
The benefits of outlining these specialties are that they highlight the many different roles translation editors play. Clearly outlining these tasks may make it easier for teams to decide if and how to divide these responsibilities.
Feedback and improvements
While I recognize that more documentation won’t immediately help resolve the challenges that inspired this post, I believe it’s useful to agree on a definition and expectations for these roles. For the locale teams that are specifically struggling to add new GTEs when others are inactive, it’s particularly important to ensure everyone is clear on the expectations of their role. Things change, and stepping back from a position or inviting others to help is okay.
With that in mind, I would appreciate any feedback you have. In particular, I would like to know:
Am I missing any roles in these diagrams?
Does this match your experience with contributing to Polyglots?
Does this match your team’s structure?
Would you add any roles? Has your locale team added any roles?
What do you think of creating “sub-roles” for translation editors?
How could this resource be useful to you?
I would love to use this to enhance existing documentation in the Polyglots Handbook, especially the Roles and Capabilities page. Your feedback on this post is welcome, either in the comments or in SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. for any additional discussion. Ideally, I would like to collect as much feedback as possible within the next two weeks by Monday, May 8th, 2023.