Add the ability to lock translations managed by upstream teams
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
We have a recurrent issue in the Ubuntu French Translator group: newcomers tend to make suggestions to a lot of different packages whose translations are present on Launchpad, but not *managed* by Launchpad.
Go for instance on the translation page for the Metacity package for Karmic:
https:/
You can modify everything and if you scroll to the bottom of the page, you'll see a nice
" This translation is managed by Ubuntu French Translators, assigned by Ubuntu Translators. You have full access to this translation. " (well, for the French, at least).
But we don't want to allow anyone to modify this upstream translation, do we?
We maintain a list of "translatable" package on the wiki (http://
We think it could be very profitable to have a way to lock translations for packages that didn't explicitly use Rosetta for their translations.
tags: | added: upstream |
tags: | added: translation |
At the moment, we don't want to allow locking of translations (until we spend more time figuring out the right privilege model for doing translations).
For instance, that metacity template you linked to might actually have modifications specific to Ubuntu: if we allow locking it, some teams might decide to do it without understanding the consequences and it would result in incomplete translations. Thus, we can't properly introduce locking without first figuring out which bits are Ubuntu specific and which are not.
Work-around for the problem you are currently facing is to limit access to ubuntu-l10n-fr team to only established reviewers, and to make sure that communication happens between team members (so they understand what they can or cannot do).