Creation of a translator group for the elementary project.

Asked by Eduard Gotwig


please create a whole translator team for the elementary project (see ).

The name should be 'elementary Translators' (please note that its a lower 'e', NOT an 'E').

For such a big software plattform, it's important to have its own launchpad translation team (IMHO).

I already created a German Translator group at :

Later on this group will be asigned to the elementary project. If you can do it, I would be pleased if you could do that, too.

Here is the log about the vote on that from the #elementary-dev IRC channel :

Thank you.

Question information

English Edit question
Launchpad itself Edit question
No assignee Edit question
Solved by:
Jeroen T. Vermeulen
Last query:
Last reply:
Revision history for this message
Milo Casagrande (milo) said :


@Eduard: I suggest you to create a team that will be the "coordinator" for the elementary translators group, like we do for the Ubuntu Translators and the Launchpad Translators groups ( and This team can be called "elementary-translations-coordinators, and will be the administrator of the elementary-translators group. In this way you can add people to help you out in managing the elementary Translators group.

@Launchpad admins: we need to create an elementary-translators group (elementary Translators), and add it to the overall translation groups in Launchpad.


Revision history for this message
Laura Czajkowski (czajkowski) said :

"You can always request the creation of a special translation group for Stoq (*),
but I'd recommend trying the Launchpad Translators group first, if you're not
happy with it, we'll create a new group for you. The reasons why we do not
directly encourage new groups is so that projects can start off with a trusted
and active set of translators and to not create fragmentation in the translations
community in Launchpad."

Revision history for this message
Eduard Gotwig (gotwig) said :

Ok, elementary Translators are now part of elementary core, and there are now sub teams created for many language regions as well:

Can you help us now?

Revision history for this message
Jeroen T. Vermeulen (jtv) said :

It may help to talk about terminology for a moment, because the terms we've always used can be a bit confusing. Maybe they ought to be changed at some point.

What we call a “translation group” is the organizational structure that assigns teams to manage translations per language. I believe that is what you are referring to when you say “whole translator team.” A translation group does not necessarily need to translate. Its primary purpose is to manage translations.

The team that manages translations for a particular language is called a “translation team.” This is a normal team like any other in Launchpad. In fact you could even just assign an individual if you wanted. Once you configure a more restrictive translation permissions model than the default, some editing privileges on translations will be preserved for members of the applicable translation team.

Revision history for this message
Eduard Gotwig (gotwig) said :

So that means we have to do for a every team , two sub teams? One for Reviewers, one for people that suggest translations?

Revision history for this message
Jeroen T. Vermeulen (jtv) said :

No, that shouldn't be necessary. Just one team for those who will review translations. Any logged-in user can suggest translations.

Revision history for this message
Eduard Gotwig (gotwig) said :

I tought that these special created teams ARE the reviewer teams.

Should there be one team that reviews them all or what :/?

Revision history for this message
Jeroen T. Vermeulen (jtv) said :

The “translation teams” are reviewer teams, yes. They manage the translations.

By “just one team” above I meant one team per language. The translation group defines which translation team is responsible for which language.

Revision history for this message
Eduard Gotwig (gotwig) said :

So we have the main translation team elementary Translators and we have reviewer teams, e.g elementary German Translators .

What is missing now?

If this topic continues to be so *big* and we don't understand each other, I recommend a chat, maybe via IRC? Please mail me, or I can mail you, too.

Revision history for this message
Best Jeroen T. Vermeulen (jtv) said :

As far as we're concerned, nothing is missing. Your new translation group is here:

I made you the owner, so you can appoint translation teams within the group. The project's owners can select it as the project's chosen translation group.

They'll also want to select a translation permissions model when they set the group for the project — typically either “Structured” or “Restricted.” In both models, any logged-in user can enter translations but if the language is covered by the translation group, only members of the translation team get to select which translations will actually be used.

The difference between these two models is what happens with languages that are not covered by the translation group. In the Structured model, any logged-in user gets full editing rights for these languages, which is good for attracting contributions. In Restricted, users aren't allowed to enter translations for these languages so this is better if you want tightly managed translations.

Revision history for this message
Eduard Gotwig (gotwig) said :

Thanks Jeroen T. Vermeulen, that solved my question.