Polyglots Team Badges

You can find the current profile badge criteria for Polyglots TeamPolyglots Team Polyglots 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/. contribution on this meta team handbook page.

Dear Polyglots,

We’ve discussed Polyglots badges for a while now during weekly chats. As we want to move things forward, we need to make some decisions.


The current suggestion is that Translation Contributors (translators) and Translation EditorsTranslation Editor Translation 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 (validators) get a separate badge.

In the weeks and months to come with the expectation for more and more projects in Translate.WordPress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins., we will need to find mechanisms to onboard new Translation Contributors faster and integrate them better into the existing teams.

If badges help this process along, I believe we should try to keep the barrier for getting a translation badge low.

At the same time Translation Editors are dedicating a lot of time and effort to keep translations consistent, they’re actively involved in the Polyglots team and put a lot more time into validating translation suggestions and generally taking care of a localeLocale Locale = 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/.

This is the reason behind the two separate badges for Translation Contributors and Translation Editors.

Things to consider

1. We need a simple automated principle for rewarding a contributor with a badge, manually adding badges will require resources the team doesn’t have. A lot of teams are doing badges manually now for a lack of a better option, but we have a way to reward automatically and it would be great if we could take advantage of that.

2. Current badges don’t have an expiration date for any of the existing teams.

What we need to decide

1. How many approved stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. should a contributor have to receive the Translation ContributorTranslation Contributor Translation Contributors (formerly known as Translators) are volunteers that focus on translating projects into their language. They contribute to improving their language either in a small way, like fixing a typo, or a large way, likes translating entire projects. badge?

2. Do contributor badges need to expire and what would the principle be

Please fill out this two question poll and help us make a decision.

Earlier today Sergey suggested we only have one badge for Polyglots for Translation Editors. If any of you is strongly in favour of this suggestion, please comment below.