You are viewing a plain text version of this content. The canonical link for it is here.
Posted to l10n@openoffice.apache.org by janI <ja...@apache.org> on 2013/11/02 21:38:24 UTC

translate of "Apache OpenOffice genLang - EXPERIMENTAL, DON'T USE"

Hi.

I changed the title as suggested, but it seems not to be enough.

@eulena: the translations you have done on the Romanian language 1 november
12:20 will be lost during next week. Please do not translate in the project:

"Apache OpenOffice genLang - EXPERIMENTAL, DON'T
USE<https://translate.apache.org/projects/aooGenLang4/>"


When creating new users, it might be an idea, only to give access to the
active AOO translation projects.

rgds
jan I.

Re: translate of "Apache OpenOffice genLang - EXPERIMENTAL, DON'T USE"

Posted by Alexandro Colorado <jz...@oooes.org>.
On Sat, Nov 2, 2013 at 3:24 PM, Andrea Pescetti <pe...@apache.org> wrote:

> janI wrote:
>
>> When creating new users, it might be an idea, only to give access to the
>> active AOO translation projects.
>>
>
> This is what I am doing now. So, for example, euelena is a user in the
> global Pootle and a user in the Romanian aoo40 project. But we are not
> (yet) filtering out people: so a German translator can now edit Spanish
> translations too, and euelena can edit genlang translations too, simply
> because the default permissions are made this way.
>
> At a certain point we will restrict global privileges and "unusual"
> translation activities will require explicit whitelisting. But we are not
> there yet, even if all accounts created in the last several weeks are
> already configured properly.
>

​This is usually why leads or project managers used to be set in place and
projects were separated. Lead in Spanish had different roles than Lead in
German, etc. My belief is that eliminating roles is a free for all similar
to the way the wiki is structure, since everyone can read/write documents
on any NLC.

AFAIK there is a legitimate reason for leads as routers of information and
quickly know people responsible for modules or with specialized projects.
This is particularly useful in activities such as QA and bug reporting. ​




>
> Regards,
>   Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: l10n-help@openoffice.apache.org
>
>


-- 
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
882C 4389 3C27 E8DF 41B9  5C4C 1DB7 9D1C 7F4C 2614

Re: translate of "Apache OpenOffice genLang - EXPERIMENTAL, DON'T USE"

Posted by Andrea Pescetti <pe...@apache.org>.
janI wrote:
> When creating new users, it might be an idea, only to give access to the
> active AOO translation projects.

This is what I am doing now. So, for example, euelena is a user in the 
global Pootle and a user in the Romanian aoo40 project. But we are not 
(yet) filtering out people: so a German translator can now edit Spanish 
translations too, and euelena can edit genlang translations too, simply 
because the default permissions are made this way.

At a certain point we will restrict global privileges and "unusual" 
translation activities will require explicit whitelisting. But we are 
not there yet, even if all accounts created in the last several weeks 
are already configured properly.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
For additional commands, e-mail: l10n-help@openoffice.apache.org