Adding a new group for LimeWire translations

Asked by Jarret on 2009-11-03

Per recent emails with Danilo & Mark, this is a formal inquiry regarding a new group for the LimeWire translations. We would like to be able to change the permissions on the group & appoint moderators for key languages and ensure the quality of the translations.

In the past, using the main open Launchpad group has led to some mistranslated strings or complaints that once-correct strings are being overwritten.

If starting our own group with more restricted permissions on how translations are suggested / submitted is the best way to solve these prior issues than please set up such a group. If there is another suggestion, please let me know what you have in mind!

Initially our concern about a new group was having to 'migrate' the users that have been helping us in the main Launchpad Translators group. Would we need to 'recruit' or redirect those users to our new one?

Apologies for the long question - the more detail I can get about this situation the better! Many thanks to your team for the prompt, polite and very helpful communication so far.

Let me know if I can provide further details. Thanks & regards, Jarret B. @ LimeWire

Question information

English Edit question
Launchpad itself Edit question
No assignee Edit question
Solved by:
Last query:
Last reply:
Henning Eggers (henninge) said : #1

Thank you for your request.

A translation group is used to *appoint* translators (a person or a team) to specific languages for a project, so that only these can accept or reject translations for this language while everybody else can only make suggestions. All languages without an appointed translator are either open to translations by all ("structured" permissions) or completely closed to translatoins ("restricted" permissions).

"Migration" would happen by either appointing a translator to a language (if a single person) or by creating a translation team (e.g. "LimeWire French Translators") which is appointed to the language and add the translators to that team. Appointment happens on the page of the translation group.

If you are happy with that procedure, I can create a translation group for you right away.

Btw, running your own translation group only makes sense if you already have translators and just need to organize the work. If you still need to find translators, using the existing "Launchpad Translation Gruop" might be a better choice for you.

Jarret (jbattisti) said : #3

Henning, my thanks for your prompt reply and help with my questions.

Given our translation situation perhaps it's best to keep the Launchpad Translator group as the main pool for our needs. If we keep the structure that way, is it possible to then change our permissions from "Open" to "Structured" so that submissions are not automatically accepted into the existing strings?

Does that then require the Launchpad Translators to moderate all of our translations (more so than they do now)?

I'm not opposed to creating one group for all the Limewire translations and then multiple moderators for the languages, but I really want to avoid alienating the people that are helping us, or making more work for the current moderators...

Thanks again, Jarret.

Adi Roiban (adiroiban) said : #4


With Open permission anyone can translate and the Launchpad Translators group has no effective role.

Changing to „Structured” will mean anyone can add suggestions but only members of Launchpad Translations team / per langauge can approve those translations are valid. In this case the Launchpad Translators will act as quality assurance teams.

Using structured, it's like in software development, anyone can submit a patch, but only the development team can review and approve them.

Open permission is like Wikis. Anyone can submit a change and that change is automaticaly accepted.

The maintainer of a project can choose the translation policy:

On that page you should see some tips about assigning a translation group and choosing the policy.

Jeroen T. Vermeulen (jtv) said : #5

You may wonder about the difference between Structured and Restricted. The difference is what happens when the translation group does not cover a given language. Under Structured, such "untended" translations behave like Open. Under Restricted, the untended translations behave like Closed.

Jarret (jbattisti) said : #6

Jeroen, Adi - thanks for your continued support with my inquiry, I'll change our project settings to "Structured" so that the main group or Launchpad Translators can act as a QC team on the languages with teams assigned to them.

Regards, Jarret