Please accept https://launchpad.net/~ubuntu-l10n-gv as the translation managing team for Manx

Asked by Reuben Potts

I have set up the team ubuntu-l10n-gv according to the checklist below:

(./) Check for an existing team. Make sure there isn't already an existing Ubuntu translations team for your language. If this is the case, you can skip all subsequent steps and ask to join the team instead.

     There wasn't an existing team

(./) Locale, keyboard and fonts. Make sure the language has a defined code, keyboard and fonts. You can skip this step if your language fulfills all requirements.

     My language fulfils all requirements.

(./) Launchpad team. Create a new Launchpad team for your language. The team's name must accord to the following rules:
ubuntu-l10n-<ISO 639 language code> - Where <ISO 639 language code> is a two-letter or a three-letter (if the two-letter one is not available) ISO 639 code.

     This was done; the team's name is ubuntu-l10n-gv

(./) Moderated subscription. Make the subscription policy of the new team Moderated or Restricted. Only this way you can ensure the quality of translations and make sure that upstream translations are not modified for no good reason.

This was done, the subscription poliy is moderated.

(./) Team information. Add some brief information on the team's page. This should include:
    * A welcome note with the purpose of the team
    * A note on how to join the team
    * Links to the team's existing communication channels (e.g. mailing list, forums, IRC channel, wiki, etc)

     All these are there.

(./) Team communication. The team should have a communication channel to coordinate the translation activities. This can be any of: a mailing list, IRC, forums, etc. This can be arranged after the team has been accepted, but it is a requirement.

This is already in place, a mailing list at <email address hidden>.

(./) Guidelines. The team should have a set of translation guidelines. This can be arranged after the team has been accepted, but it is a requirement.

     This is not yet in place, but is being worked on. In any case, there will probably be no other team members for some time.

(./) Upstream collaboration. The team should be aware of any upstream translation efforts (e.g. GNOME, KDE, Mozilla, OpenOffice.org, Debian, etc.), and coordinate with them if possible. You'll find more information about the different upstreams here.

     This is a tough one. I should explain that Manx is a REALLY minority language (but growing!!) and to put it shortly: there is no upstream. Hopefully this fact won't cause problems for me here, and I can say that if it became possible to contribute upstream I would definitely do it.

(./) Coordinator. The team should have a coordinator, who should subscribe to the ubuntu-translators mailing list and forward any relevant announcements or information to the team.

     I've done this.

(./) Application. Once all points have been addressed, simply file a support request and the Ubuntu Translations Coordinators will add the team to the Ubuntu Translators group.

    Right here. :)

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Translations Edit question
Assignee:
No assignee Edit question
Solved by:
David Planella
Solved:
Last query:
Last reply:
Revision history for this message
Best David Planella (dpm) said :
#1

Hi,

Having followed the procedure on starting a team and the requirements,
I'm happy to appoint the Ubuntu Manx translators team as responsible for
Manx translations in Ubuntu.

Please see the inline comments below:

El dv 16 de 04 de 2010 a les 22:38 +0000, en/na Reuben Potts va
escriure:
> New question #107634 on Ubuntu Translations:
> https://answers.edge.launchpad.net/ubuntu-translations/+question/107634
>
> I have set up the team ubuntu-l10n-gv according to the checklist below:
>
> (./) Check for an existing team. Make sure there isn't already an existing Ubuntu translations team for your language. If this is the case, you can skip all subsequent steps and ask to join the team instead.
>
> There wasn't an existing team
>
>
>
> (./) Locale, keyboard and fonts. Make sure the language has a defined code, keyboard and fonts. You can skip this step if your language fulfills all requirements.
>
> My language fulfils all requirements.
>
>
>
> (./) Launchpad team. Create a new Launchpad team for your language. The team's name must accord to the following rules:
> ubuntu-l10n-<ISO 639 language code> - Where <ISO 639 language code> is a two-letter or a three-letter (if the two-letter one is not available) ISO 639 code.
>
> This was done; the team's name is ubuntu-l10n-gv
>
>
>
> (./) Moderated subscription. Make the subscription policy of the new team Moderated or Restricted. Only this way you can ensure the quality of translations and make sure that upstream translations are not modified for no good reason.
>
> This was done, the subscription poliy is moderated.
>
>
>
> (./) Team information. Add some brief information on the team's page. This should include:
> * A welcome note with the purpose of the team
> * A note on how to join the team
> * Links to the team's existing communication channels (e.g. mailing list, forums, IRC channel, wiki, etc)
>
> All these are there.
>
>
>
> (./) Team communication. The team should have a communication channel to coordinate the translation activities. This can be any of: a mailing list, IRC, forums, etc. This can be arranged after the team has been accepted, but it is a requirement.
>
> This is already in place, a mailing list at <email address hidden>.
>
>
>
> (./) Guidelines. The team should have a set of translation guidelines. This can be arranged after the team has been accepted, but it is a requirement.
>
> This is not yet in place, but is being worked on. In any case, there will probably be no other team members for some time.
>

I would still encourage you to start working on the guidelines as soon
as possible. Even if there aren't any other new members for quite some
time, it will be helpful to have them to start translating consistently.

>
>
>
> (./) Upstream collaboration. The team should be aware of any upstream translation efforts (e.g. GNOME, KDE, Mozilla, OpenOffice.org, Debian, etc.), and coordinate with them if possible. You'll find more information about the different upstreams here.
>
> This is a tough one. I should explain that Manx is a REALLY minority language (but growing!!) and to put it shortly: there is no upstream. Hopefully this fact won't cause problems for me here, and I can say that if it became possible to contribute upstream I would definitely do it.
>

Launchpad offers you a unified online translation interface for all
translatable applications in Ubuntu, but it is still important to send
back contributions upstream, so that other distros can benefit from them
as well.

If there isn't an upstream team for a particular project, you might want
to create one. You can do this straight away or after having reached
some more translated content in Launchpad, which you could export
upstream.

You'll find more info here:
https://wiki.ubuntu.com/Translations/Upstream

>
>
> (./) Coordinator. The team should have a coordinator, who should subscribe to the ubuntu-translators mailing list and forward any relevant announcements or information to the team.
>
> I've done this.
>
>
>
> (./) Application. Once all points have been addressed, simply file a support request and the Ubuntu Translations Coordinators will add the team to the Ubuntu Translators group.
>
> Right here. :)
>

And as the final step, could you look into the points in the "After the
team has been accepted" section on
https://wiki.ubuntu.com/Translations/KnowledgeBase/StartingTeam?

Welcome to Ubuntu Translations!

Regards,
David.

--
David Planella
Ubuntu Translations Coordinator
david(dot)planella(at)ubuntu(dot)com
www.ubuntu.com

Revision history for this message
David Planella (dpm) said :
#2

Reuben,

This support request was actioned a while ago. I believe it is now solved, so if it is, could you please mark it as so on https://answers.launchpad.net/ubuntu-translations/+question/107634 by clicking on the answer that solved your question? Thanks!

Revision history for this message
Reuben Potts (reuben03) said :
#3

Thanks David Planella, that solved my question.