launchpad help|
Size: 7711
Comment:
|
← Revision 47 as of 2010-12-23 13:33:10 ⇥
Size: 9166
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| !!!! DRAFT !!!! The development or this group is discussed here: https://blueprints.edge.launchpad.net/rosetta/+spec/launchpad-translators-group ~-[[FrontPage|Launchpad Help]] > [[Translations]] > "Launchpad Translators" translation group -~ |
~-[[FrontPage|Launchpad Help]] > [[Translations]] > Translators and Translation Teams in Launchpad -~ |
| Line 10: | Line 7: |
| * Link to [[https://translations.launchpad.net/+groups/launchpad-translators/ | Launchpad Translators Group in Rosetta]] * Link to a list of translation guides for all languages * Link to a page describing upstream translation projects and how we should work togheter |
The [[https://translations.launchpad.net/+groups/launchpad-translators/ | Launchpad Translators group]] is a set of teams and individuals working on translating software hosted in Launchpad. It is a confederation of translation teams, it is not yet another translation project. |
| Line 14: | Line 9: |
| = Goal and Purpose = | We believe that people translating software in the same language should work in the same team, even thought they are working at different software. |
| Line 16: | Line 11: |
| ''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'' | There is one Launchpad localization team appointed for each language. |
| Line 18: | Line 13: |
| 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. | We encourage Ubuntu, Debian, Fedora, GNOME, KDE, Mozilla, !OpenOffice.org and all other translators dedicated to a specific project to join the localization team appointed for their language. |
| Line 20: | Line 15: |
| 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 | We also encourage project maintainers to appoint the '''Launchpad Translators''' group as the translation group for their project. |
| Line 22: | Line 17: |
| Project maintainers should be able to trust Launchpad Translators Group and appoint it to manage translations for their projects. | = Project Maintainers = |
| Line 24: | Line 19: |
| = Working with Launchpad Translators = == Project maintainers == * first learn how to use Launchpad Translations to make translation available for your project. For more information [[https://help.launchpad.net/Translations | check the Launchpad Translations help pages]] * chose a translation model and appoint Launchpad Translators Group for doing the translation * 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 |
Every project needs high quality translation that convey with the cultural background and the already established guidelines of each language. |
| Line 30: | Line 21: |
| * TODO: see how we can use Bugs and Answers to interact with project maintainers | The '''Launchpad Translators''' group stands for those goals. Here you can find a list of steps to follow in order to use Launchpad Translations as the translation tool for you project and have it translated into many languages. |
| Line 32: | Line 23: |
| == Translators == * First learn how to use Launchpad for translating projects/operating systems. For more information [[https://help.launchpad.net/Translations | check the Launchpad Translations help pages]] * Follow the procedure for joining a team for your language. Before joining a team you might be asked to do some translation in order to check your translation skills. * Follow the rules of your team * When translating downstream always check with the upstream project and commit your changes |
* Before proceeding, please take a moment and see how you can use Launchpad and what you should do in order to have your project translated. You can find these information at [[https://help.launchpad.net/Translations/YourProject | Translating your project help pages]]. |
| Line 38: | Line 25: |
| = Teams = ''Describe purpose of a Launchpad translation team'' |
* Choose a translation permissions policy and appoint the "Launchpad Translators" group for doing the translation. Follow this link to find more info about [[https://help.launchpad.net/Translations/YourProject/PermissionPolicies | Choosing permissions policy]]. We recommend using the ''Structured'' policy, as a measure to assure translation quality. |
| Line 41: | Line 27: |
| * The direct link to your project permissions policy is: [[https://translations.launchpad.net/<YOUR-PROJECT-NAME>/+settings]]. | |
| Line 42: | Line 29: |
| = Managing a team = | * You can contact the [[https://launchpad.net/~launchpad-translators | Launchpad Translators Team]] for announcing things that affect all languages (ex. approaching release, major string changes, string freeze... etc.) or a [[https://translations.launchpad.net/+groups/launchpad-translators/ | specific language team]] for things affecting only one language. |
| Line 44: | Line 31: |
| ''General information about managing a team and a translation team'' | * You can also send an initial message to the [[https://launchpad.net/~launchpad-translators | Launchpad Translators Team]] and let them know about your project. |
| Line 46: | Line 33: |
| == Relation with other translation teams == | * When you are due to release a new version of your project, contact the team and let them know when you would like to release: in this way translators can better organize their work. It is good to advise them at least two weeks before a release. |
| Line 48: | Line 35: |
| ''How each team can work and colaborate with upstream or other translation project for the same language.'' | * If there are any translations errors or bug in your project please assign them to the [[https://launchpad.net/~launchpad-translators | Launchpad Translators team]]. We will look at the problems and assign them to the proper team or person. |
| Line 50: | Line 37: |
| ''How each team can share best practice with the other Launchpad translators team'' | * For your project Answers section, if people ask about specific translations or localization matters, you can assign those questions to the [[https://translations.launchpad.net/+groups/launchpad-translators/ | Launchpad Translators Team]]. We will try to analyze it and have a knowledgable person take care or it. |
| Line 52: | Line 39: |
| == Quality assurence == ''How a team can work and comunitate in order to assure quality.'' |
= Translators = |
| Line 56: | Line 41: |
| == Common/best practice == | All members of a Launchpad localization teams should be knowledgable in translating software into their own language, be aware about the work of other localization teams and about other translation projects. |
| Line 58: | Line 43: |
| Below you will find a set of common practices for running a team | Below is a list of steps you might follow in order to start using Launchpad Translations for translating your favorite project or distributions. |
| Line 60: | Line 45: |
| * Don't forget about other translators or translations groups. In many cases you or your are not the only one doing translation in the free software ecosystem. Always keep in touch with that other teams are doing and make sure the translation teams for your language are translating free software using the same "language". Try to create or join a communication channel channel common to all transaltion teams for your language and use it for talking about important aspect that affect all translations. | * Before doing any translation work please take a moment and learn how to use Launchpad as your translation tool. For more information [[https://help.launchpad.net/Translations/StartingToTranslate | check the Launchpad Translations help pages]]. |
| Line 62: | Line 47: |
| * Define a procedure for accepting new team members. * The acceptance level may vary according to the percentage of already finnised translations. For languages with few translators and translations already done team acceptance could be lower than in the case of a language with many translators, tramslations made and the presence of GTP, OpenOffice , etc upstream translation projects. * Before accepting a member you may ask him/her to provide some translation. If the translations are great you may accept the new member. Otherwise giving feedback about why the translation are not good is a great help. Try to use a forum, mailinglist or IRC channel for giving feedback to potential new members. |
* Consult the [[https://translations.launchpad.net/+groups/launchpad-translators/ | list of translations teams]] and check the team assigned to your language. If there is no team assigned for your language, please follow the required step to create a new one. Below you will find more information on how to create a new team. |
| Line 66: | Line 49: |
| * Create a webpage/wikipage for the translations guide. This guide should contain: * First rule: "If a translation does not make sense for you / your grandmother, definetly it is wrong!". * Second rule: "Make your translation useful and adapt to the context. Don't follow always the original text". Like for example "Tile children" may sound funny in many languages so try "Arrange windows as tilea". The original text is not always the correct one. * a common terminolgy or a link to a common terminalogy dictionary or glossary. Don't forget about [[http://open-tran.eu | open-tran.eu ]] . You can also install [[http://www.i18n.ro/glosar | the glossary used by Romanian teams]] ([[ http://diacritice.svn.sourceforge.net/viewvc/diacritice/trunk/ | here is the code]]) * information about what should be translated and what not * specific rules for translating into your language * a list of frequent errors. * explaining the plurar form for your language and how to use them * how you should translate menu accelerators / shortcuts * inform the translators about other translation project and how we should cooperate and work togheter * 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. |
* Follow the procedure for joining the team for your language. Before joining a team you might be asked to do some translation in order to test your translation skills. |
| Line 79: | Line 51: |
| * add your best practice 1 * add your best practice 2 |
* Follow the rules of your team, communicate and keep in touch with the team. |
| Line 82: | Line 53: |
| * You may want to join the [[https://launchpad.net/~launchpad-translators | Launchpad Translators mailing list]] and get in touch with other translators and teams. | |
| Line 83: | Line 55: |
| = 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. |
= Launchpad Localization Teams = |
| Line 86: | Line 57: |
| 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. | Launchpad localization teams are the driving force behind the Launchpad translation process. Each localization team will translate and check translations on behalf of the language appointed to it. |
| Line 88: | Line 59: |
| To check the current status you can consult the [[https://translations.launchpad.net/+groups/launchpad-translators/ | Launchpad Translators Group in Rosetta]]. | Launchpad Translators Group will only have one team appointed to each language. |
| Line 90: | Line 61: |
| 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. | To check the current status of Launchpad Translators Group, please consult the [[https://translations.launchpad.net/+groups/launchpad-translators/ | list of Launchpad localization teams]]: * If your language does not appear in the list, please consider starting a new team for your language. * If your language is in the list, please consider joining that team (or request that your current team to be added as a subteam). |
| Line 92: | Line 65: |
| Steps to follow for creating a team and appointing to a language. * join the launchpad translators discussions/announcemnts list - ADD LINK TO THIS LIST * create a wiki page or a web page explaining how translators should work in your team . you can follow the example from our best practices -ADD LINK - and adapt them to your language/team |
If the Launchpad localization team appointed to your language is no longer active, or in case you encounter problems joining or working with the team, please let us know by [[https://launchpad.net/%7Elaunchpad-translators-leaders/+contactuser | contacting the Launchpad Translation Coordinators]]. |
| Line 96: | Line 67: |
| 1. If you translation 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. 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. 1. '''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. |
<<Anchor(StartingTeam)>> == How to start a new team and join Launchpad Translators == Here's how you can create a new team for your language and join the Launchpad Translators group: * '''Create the team'''. [[https://launchpad.net/people/+newteam |Create a new Launchpad localization team]]. When giving a name to the team in Launchpad, please follow the convention '''lp-l10n-CC''', where CC is your '''language''' code . We use iso-639 two letters code and if not available we fallback to three letters code. For instance '''lp-l10n-de''' would be the name for the German team (language code ''de'') * '''Moderated subscription'''. Make the [[Teams/CreatingAndRunning#Subscription%20policies|subscription policy]] of the new team '''Moderated''' or '''Restricted'''. Only this way you can ensure the quality of translations. * '''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) * '''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. * '''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. * You can use the [[Translations/Guide | general Launchpad localization guidelines]] or adapt them for your language/team. * [[Translations/Guidelines | Let Launchpad know about your translation guidelines]]. * '''Coordinator'''. The team should have a coordinator with a stable contact e-mail address visible to logged-in Launchpad users. The coordinator should subscribe to the launchpad-translators mailing list and forward any relevant announcements or information to the team. As the coordinator, you are the primary contact person for the team and the person who make things happen. * As the coordinator of a Launchpad localization team, it is higly recommended to join the [[https://launchpad.net/~launchpad-translators | Launchpad Translators mailing list]]. * '''Apply'''. [[https://answers.launchpad.net/rosetta/+addquestion|Send a support request]] for the Launchpad Translations Coordinators to appoint your team in the Launchpad Translators group. Please include a link to your team and a short note explaining how you have addressed the points above. Except for creating the guidelines and setting up a communication channel, this process should not take more than a few minutes to complete. If you need any help or you've got any questions in any of the steps, feel free to [[https://answers.launchpad.net/rosetta/+addquestion|ask]], and we'll be happy to give a hand. ||<tablestyle="width: 100%;"> ~-[[Translations/TranslationGroups|< Translations Groups]] -~ ||<style="text-align: right;"> ~- [[Translations| Translations help page >]] -~ || |
Launchpad Help > Translations > Translators and Translation Teams in Launchpad
Overview
The Launchpad Translators group is a set of teams and individuals working on translating software hosted in Launchpad. It is a confederation of translation teams, it is not yet another translation project.
We believe that people translating software in the same language should work in the same team, even thought they are working at different software.
There is one Launchpad localization team appointed for each language.
We encourage Ubuntu, Debian, Fedora, GNOME, KDE, Mozilla, OpenOffice.org and all other translators dedicated to a specific project to join the localization team appointed for their language.
We also encourage project maintainers to appoint the Launchpad Translators group as the translation group for their project.
Project Maintainers
Every project needs high quality translation that convey with the cultural background and the already established guidelines of each language.
The Launchpad Translators group stands for those goals. Here you can find a list of steps to follow in order to use Launchpad Translations as the translation tool for you project and have it translated into many languages.
Before proceeding, please take a moment and see how you can use Launchpad and what you should do in order to have your project translated. You can find these information at Translating your project help pages.
Choose a translation permissions policy and appoint the "Launchpad Translators" group for doing the translation. Follow this link to find more info about Choosing permissions policy. We recommend using the Structured policy, as a measure to assure translation quality.
The direct link to your project permissions policy is: https://translations.launchpad.net/<YOUR-PROJECT-NAME>/+settings.
You can contact the Launchpad Translators Team for announcing things that affect all languages (ex. approaching release, major string changes, string freeze... etc.) or a specific language team for things affecting only one language.
You can also send an initial message to the Launchpad Translators Team and let them know about your project.
- When you are due to release a new version of your project, contact the team and let them know when you would like to release: in this way translators can better organize their work. It is good to advise them at least two weeks before a release.
If there are any translations errors or bug in your project please assign them to the Launchpad Translators team. We will look at the problems and assign them to the proper team or person.
For your project Answers section, if people ask about specific translations or localization matters, you can assign those questions to the Launchpad Translators Team. We will try to analyze it and have a knowledgable person take care or it.
Translators
All members of a Launchpad localization teams should be knowledgable in translating software into their own language, be aware about the work of other localization teams and about other translation projects.
Below is a list of steps you might follow in order to start using Launchpad Translations for translating your favorite project or distributions.
Before doing any translation work please take a moment and learn how to use Launchpad as your translation tool. For more information check the Launchpad Translations help pages.
Consult the list of translations teams and check the team assigned to your language. If there is no team assigned for your language, please follow the required step to create a new one. Below you will find more information on how to create a new team.
- Follow the procedure for joining the team for your language. Before joining a team you might be asked to do some translation in order to test your translation skills.
- Follow the rules of your team, communicate and keep in touch with the team.
You may want to join the Launchpad Translators mailing list and get in touch with other translators and teams.
Launchpad Localization Teams
Launchpad localization teams are the driving force behind the Launchpad translation process. Each localization team will translate and check translations on behalf of the language appointed to it.
Launchpad Translators Group will only have one team appointed to each language.
To check the current status of Launchpad Translators Group, please consult the list of Launchpad localization teams:
- If your language does not appear in the list, please consider starting a new team for your language.
- If your language is in the list, please consider joining that team (or request that your current team to be added as a subteam).
If the Launchpad localization team appointed to your language is no longer active, or in case you encounter problems joining or working with the team, please let us know by contacting the Launchpad Translation Coordinators.
How to start a new team and join Launchpad Translators
Here's how you can create a new team for your language and join the Launchpad Translators group:
Create the team. Create a new Launchpad localization team. When giving a name to the team in Launchpad, please follow the convention lp-l10n-CC, where CC is your language code . We use iso-639 two letters code and if not available we fallback to three letters code. For instance lp-l10n-de would be the name for the German team (language code de)
Moderated subscription. Make the subscription policy of the new team Moderated or Restricted. Only this way you can ensure the quality of translations.
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)
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.
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.
You can use the general Launchpad localization guidelines or adapt them for your language/team.
Coordinator. The team should have a coordinator with a stable contact e-mail address visible to logged-in Launchpad users. The coordinator should subscribe to the launchpad-translators mailing list and forward any relevant announcements or information to the team. As the coordinator, you are the primary contact person for the team and the person who make things happen.
As the coordinator of a Launchpad localization team, it is higly recommended to join the Launchpad Translators mailing list.
Apply. Send a support request for the Launchpad Translations Coordinators to appoint your team in the Launchpad Translators group. Please include a link to your team and a short note explaining how you have addressed the points above.
Except for creating the guidelines and setting up a communication channel, this process should not take more than a few minutes to complete. If you need any help or you've got any questions in any of the steps, feel free to ask, and we'll be happy to give a hand.
