Request to create Esperanto team

[Tim Morley]

On 31 Mar 2006, at 20:12, Jordi Mallach wrote:

>> One other request -- restrict who has the right to edit
>> translations directly, who can suggest changes to be confirmed, etc.
>
> Ok, I think you got this a bit wrong. With the current codebase, when
> you add someone to your team, you'll give him full access to any
> translation owned by the Ubuntu translations. To avoid people editing
> translations, you need to "disable" them from the team.

OK, that's better than a wide open system, but could you explain in  
that case what's been happening so far? I started translating  
immediately after creating my own account on LaunchPad, and nobody's  
ever objected. The half-dozen other people also did exactly the same  
-- started working on the Esperanto translation, and were never  
questioned. All this was before the Ubuntu Esperanto Team even existed.

If we were all allowed to just pitch in without any authorisation,  
will it be any different in future for the next contributor?

> I wish there will be more fine grained control within teams, but for
> now, this is not possible.

Well, allow me to quote:

> From: Mark Shuttleworth <mark at canonical.com>
> Date: 17 March 2006 11:02:11 GMT
> To: Tim Morley <t_morley at ARGONET.CO.UK>
> Cc: rosetta-users at lists.ubuntu.com
> Subject: Re: Translation groups
>
> <...>
> Permissions are fun. You can set permissions on:
>
>  - a distribution ("ubuntu")
>  - a product (an upstream application like "firefox")
>  - a project (a group of upstream applications, like "mozilla")
>
> And your permissions can be (from memory):
>
>  - Open.
>    Anybody (official translator or not) can change the translations  
> in any language for this product/project/distro.
>
>  - Structured/Reviewed.
>    For languages where there is a translation team in the relevant  
> translation group, ONLY the members of that team can change a  
> translation. Other people can make suggestions which the official  
> translators will see. For other languages, where there is no  
> official translation team, anybody can edit the translation.
>
>  - Closed.
>    Translations are locked and ONLY the official members of  
> translation teams can edit the translations. Other people can make  
> suggestions only. If there is no official translation team, then  
> suggestions will not become translations.
>
> I wrote much of that code so I'll take the bullets if there are  
> bugs. We really need better Launchpad documentation so folks know  
> how to take advantage of this sort of feature!

Your description makes it sound like only the "Open" and "Closed"  
options that Mark lists actually exist. Is Mark's memory failing  
him?  ;-)

The "Structured/Reviewed" option definitely sounds like the most  
useful (but also obviously the hardest to implement), but it would  
allow newcomers to contribute usefully and immediately, but also  
allow the established team the chance to competence-check new people  
before giving out full permissions.

If you could let me know about the above permissions stuff, it'd be  
much appreciated.

Cheers.


Tim