!!!! DRAFT !!!! The development or this group is discussed here: https://blueprints.edge.launchpad.net/rosetta/+spec/launchpad-translators-group

Launchpad Help > Translations > "Launchpad Translators" translation group

Overview

• Launchpad Translators Group in Rosetta

Goal and Purpose

Describe the goal and purpose of Launchpad Translators group and it's relations with the other translations groups, including Ubuntu, GTP , Mozilla, OpenOffice.org, The Translation Project

We want to build the Launchpad Translators Group as a confederation of translation teams each team working at translating project hosted by Launchpad in it's language.

All members of Launchad Translators should be experts in translating software and be aware about the work of other teams from Launchpad or not. Launchpad translators will do translations work

Project maintainers should be able to trust Launchpad Translators Group and appoint it to manage translations for their projects.

Working with Launchpad Translator

Project owners

• first learn how to use Launchpad to make translation available for your project
• chose a translation model and assing Launchpad Translators
• use the announcemnt list for things that affect all languages (ex. new release, major string changes, string freeze... etc) or each team for things affecting only one language
• TODO: see how we can use Bugs and Answers

Translators

• first learn how to use Launchpad for translating projects/operating systems
• join a team for your language
• follow the rules of your team
• when translating downstream alwasy check with the upstream project and summit changes

Teams

• purpose of the team

Managing a team

General information about managing a team and a translation team

Relation with other translation teams

How each team can work and colaborate with upstream or other translation project for the same language. How each team can share best practice with the other Launchpad translators team

Quality assurence

How a team can work and comunitate in order to assure quality.

Common/best practice

A set of common practices for running ateam

• common practice 1
• common practice 2
• Make sure you have a solid communication channel for all members of the team or subteam. Try to reach all communication types: maillinglist, forum, IRC channel.

Creating a team

Launchpad Translators Group will appoint one team for each language. To add more teams for a specific language you will need to add them as a subteam of the initial team.

Thus creating a new Launchpad team for a specific language and asking for it's appointment is only required if there is no team already appointed for the specific language.

To check the current status you can consult the Launchpad Translators Group in Rosetta.

If there is already a team appointed for a language you can still create your own translation team but in order to translate software in your language you will need to become a subteam of the already appointed team for your language.

Steps to follow for creating a team and appointing to a language.

• join the launchpad translators announcemnts list
• create a wiki page or a web page explaining how translators should work in your team . you can follow our best practices and addapt them to your language/team
• If you translation karma is over 5000 go to step X
• If you are already a coordinator of a translation team, let us know about this, and go to step X

• If there is already a GNOME, KDE, OpenOffice.org, Mozilla, etc. upstream project from your language point us some translation you have made for those projects then go to step X

• If there is no upstream project already set for your language please consider following the required steps in creating one for your language. There is no problem if in the same time you are the coordinator for multiple translation projects.

• Step X create a lp-l10n-CC team and ask launchpad-translation-leaders to appoint a language to this team. We use iso-639 two letters code and if not available we fallback to three letters code.