Create Translation Group

Hi,

I see you are currently using Launchpad Translators group.
What are the problems encountered while using Launchpad Translators group?

You can find more info about the group here.
https://help.launchpad.net/Translations/LaunchpadTranslators

Of course we can create a translation group for Xiphos, but from my point of view, splitting translators community in hundreds of groups will not get to much benefit both for translators and project maintainers.

We want to make Launchpad Translators group, suitable for any project hosted in Launchpad, so any feedback is much appreciated.

Kindest regards,
Adi

Well I totally understand your point. That's why I do like Launchpad & Ubuntu community a lot. I'm Ubuntu/Debian maintainer of Xiphos but also got svn commit access on sourceforge. They use sourceforge as primary user/developer group (although it might not look like it due to my activity on lp)

I guess translation group "feature" is viewed as a "bug". Here is the email to developer list from Xiphos project leader:

2009/12/13 Peter von Kaehne <email address hidden>:
> Peter von Kaehne wrote:
>> But I absolutely do resist any idea of having the farsi translation open
>> for drive-by shooters. Any submissions needs to get checked and
>> essentially i will want to ignore people who I do not know (personally
>> and face-to-face).
>>
>> Can we please have some more fine grained control over who is allowed to
>> make changes to what?
>
> Ok, I think the solution for Launchpad is to change the project overall
> to "structured" and then name a maintainer for those languages the
> maintainer wants to have control over what goes in.
>
> This will restrict access to those languages which shall not get
> "messed" about with, wile leaving wide open the rest.
>
> Best of all worlds I guess.
>
> Peter

I guess I can simply ignore fa translations and not commit them back to svn.

But from rosetta point of view it would be nice to have a feature to give per language control over translations. Eg. yes translate all, but we do have existing outside lp maintainers for so and so and he will review these translations.

I'll browse through rosetta bugs and to see something similar.

Hi,

Thank you very much for you feedback!

In this case you would like to set translation policy to Restricted.

This should solve your problem as any language without a managing team will be closed for "drive-by shooters".

Right now we are building the teams and trying to find trusted translators for languages that don't already have a managing team.

You should see Launchpad Translators Group just like you own Xiphos group. If you need new teams added please let us know and we will add them. If some teams are submitting bad translations , also please let us know and we will take care of that.

-------
Will Restricted translation policy suit your needs?

Kindest regards,
Adi

Sounds good.

We will stick to structured policy.

Please set team ~farsi-translators as maintainer for Persian. I'll add
our other 2 Persian translators to it.

Sounds good.

We will stick to structured policy.

Please set team ~farsi-translators as maintainer for Persian. I'll add our other 2 Persian translators to it.

Hi,

Can you please set up the lp-l10n-fa team ?
We use this naming convention for all other Launchpad Translation teams and we would like to have a consistent naming convention.

As soon as the team is created, I will appoint it to Launchpad Translations Group for Persian.

Kindest regards,
Adi

done cheers

https://edge.launchpad.net/~lp-l10n-fa

Thanks Adi Roiban, that solved my question.

LinkedIn
------------

I'd like to add you to my professional network on LinkedIn.

- Dmitrijs Ledkovs

Confirm that you know Dmitrijs Ledkovs
https://www.linkedin.com/e/isd/1067433077/V-qpG26-/

------
(c) 2010, LinkedIn Corporation