1109
Comment:
|
3238
|
Deletions are marked like this. | Additions are marked like this. |
Line 2: | Line 2: |
The development or this group is discussed here: https://blueprints.edge.launchpad.net/rosetta/+spec/launchpad-translators-group | |
Line 9: | Line 10: |
= Goal = | * [[https://translations.launchpad.net/+groups/launchpad-translators/ | 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. |
Line 15: | Line 26: |
* 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 |
|
Line 19: | Line 33: |
* follow the rules for your team | * follow the rules of your team * when translating downstream alwasy check with the upstream project and summit changes |
Line 23: | Line 38: |
* when to create a team | |
Line 28: | Line 42: |
== Procedure for creating a team == | === Relation with other translations team === 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 === Assuring quality === How a team can work and comunitate in order to assure quality. === Common practice === A set of common practices for running ateam * common practice 1 * common practice 2 == Creating a team == When to create a team Steps to follow for creating a team and appointing to a language. |
Line 30: | Line 61: |
* 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 * create a lp-l10n-CC team and ask admins to appoint a language to this team * TODO: |
* 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 1. If you karma is over 5000 go to step X 1. If you are already a coordinator of a translation team, let us know about this, and go to step X 1. 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 1. '''Step X''' create a lp-l10n-CC team and ask launchpad-translation-leaders to appoint a language to this team |
!!!! 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
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
Relation with other translations team
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
Assuring quality
How a team can work and comunitate in order to assure quality.
Common practice
A set of common practices for running ateam
- common practice 1
- common practice 2
Creating a team
When to create a team
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 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
Step X create a lp-l10n-CC team and ask launchpad-translation-leaders to appoint a language to this team