What happens to translations when upstream is brought in

[Og Maciel]

On 8/17/06, Enrique Matías Sánchez (Quique) <cronopios at gmail.com> wrote:
> A solution could be:
> a) use the strings translated upstream and lock them

+1

> b) give the upstream translator privileges in Rosetta to unlock the
> strings in the files he translates

+1.  If I could add more to this point, I'd say that maybe the
upstream translators could become part of the existing Rosetta team,
and together with the (Rosetta) existing members, lay down the rules
by which the translations would obey from now onward.

> c) when a rosetta translator has a *good* reason to modify a string
> already translated upstream, instead of modifying the po file, Rosetta
> should e-mail the upstream translator reporting him the issue and the
> new proposed translation

If what I said above (b) were to become true, then this would be taken
care by the teams themselves.

> d) the upstream translator could then use his unlocking privileges to
> approve (or reject) the proposal from the Rosetta translator, and
> modify that string both in Rosetta and upstream

Same as (c).

> e) in the event of an upstream translator not taking action, the
> Rosetta coordinator for that language would decide whether to approve
> or reject the proposed modification.

Same as (c).

> This way:
> - Ubuntu would promptly get any fixes the Rosetta translators propose.
 +1

> - Upstream could use the .po files generated in Rosetta to add the
> work done here over untranslated strings.

+1

> - No duplication of work and frustration feeling would happen.

+1

Actually, there wouldn't be an upstream anymore and every contribution
would go directly to the proper packages/teams.

Now, this all sounds too good so far... hehehe...  We need someone to pipe in...

Cheers,
-- 
Og B. Maciel

(Leader) Ubuntu Brazilian Portuguese Translators

ogmaciel at ubuntu.com
ogmaciel at ubuntubrasil.org
og.maciel at gmail.com

GPG Keys: D5CFC202

http://www.ogmaciel.com (en_US)
http://blog.ogmaciel.com (pt_BR)