Archive:L10N/FedoraModulesMove
From FedoraProject
m (→Overview: Fixed template) |
(To deletion) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Delete|Outdated content}} | ||
= Mass move of Fedora modules = | = Mass move of Fedora modules = | ||
| − | {{ Template:floatright/| [[Image:L10N_FedoraModulesMove_ElvisPresleyAlohafromHawaii.jpg]] | + | {{ Template:floatright/| [[Image:L10N_FedoraModulesMove_ElvisPresleyAlohafromHawaii.jpg]]}} |
| − | }} | + | |
On '''February 18, 2008''' the Fedora Project is moving all translatable Fedora projects from the [http://i18n.redhat.com/cgi-bin/i18n-status i18n.redhat.com] (also known as elvis) over to Fedora servers ([[L10N/FedoraModulesMove/Announcement| original announcement]] ) | On '''February 18, 2008''' the Fedora Project is moving all translatable Fedora projects from the [http://i18n.redhat.com/cgi-bin/i18n-status i18n.redhat.com] (also known as elvis) over to Fedora servers ([[L10N/FedoraModulesMove/Announcement| original announcement]] ) | ||
| Line 8: | Line 8: | ||
The move of all Fedora-related modules from elvis to [[Infrastructure| Fedora servers]] allows us to better maintain them, hook them up with the Fedora Account System, and increase their interoperability with the rest of our infrastructure. This move is part of our effort to grow our community and open up our processes and will help us increase the number of Fedora languages and their quality, and also lower the barrier of entry for new translators. | The move of all Fedora-related modules from elvis to [[Infrastructure| Fedora servers]] allows us to better maintain them, hook them up with the Fedora Account System, and increase their interoperability with the rest of our infrastructure. This move is part of our effort to grow our community and open up our processes and will help us increase the number of Fedora languages and their quality, and also lower the barrier of entry for new translators. | ||
| − | {{ | + | {{Admon/tip | [[Infrastructure/RFR/FinalElvisMove#why-migrate| A more detailed rationale]] can be found at the |
| − | Move coordination page, together with a [[Infrastructure/RFR/FinalElvisMove#projects| full list of all modules being moved]] . | + | Move coordination page, together with a [[Infrastructure/RFR/FinalElvisMove#projects| full list of all modules being moved]].}} |
== Overview == | == Overview == | ||
| Line 39: | Line 39: | ||
One of the most important aspects of the Translation project is that we work in language teams. This way, we get to discuss with people in our own languages, peer review our contributions, and allow users to send suggestions for our translations directly to us. Furthermore, some local groups meet together to work on issues they like in real life. That's why the Join procedure has a step to help you [http://translate.fedoraproject.org/teams/ join your language's team] and introduce yourself to it. | One of the most important aspects of the Translation project is that we work in language teams. This way, we get to discuss with people in our own languages, peer review our contributions, and allow users to send suggestions for our translations directly to us. Furthermore, some local groups meet together to work on issues they like in real life. That's why the Join procedure has a step to help you [http://translate.fedoraproject.org/teams/ join your language's team] and introduce yourself to it. | ||
| − | If the team list page doesn't have your team or has an {{Template:Caution}} exclamation mark saying there is no Maintainer for the team, please [[L10N/Maintainer step up as one]] to help coordinate the activities for that team! | + | If the team list page doesn't have your team or has an {{Template:Caution}} exclamation mark saying there is no Maintainer for the team, please [[L10N/Maintainer |step up as one]] to help coordinate the activities for that team! |
==== Getting the translation files ==== | ==== Getting the translation files ==== | ||
| Line 51: | Line 51: | ||
</pre> | </pre> | ||
| − | {{ | + | {{Admon/tip | More info | [[L10N/FAQ#get-files| L10N/FAQ#get-files]]}} |
==== Submitting the files ==== | ==== Submitting the files ==== | ||
| Line 59: | Line 59: | ||
'''https://translate.fedoraproject.org/submit/''' | '''https://translate.fedoraproject.org/submit/''' | ||
| − | {{ | + | {{Admon/tip | More info | [http://docs.fedoraproject.org/translation-quick-start-guide/en_US/sn_translating_software.html#sn-commit-modules TQSG commit modules] , [[L10N/FAQ#submit| Submit FAQ]]}} |
| Line 79: | Line 79: | ||
If you have any questions regarding your migration process, drop by IRC on Freenode, channel #fedora-l10n. Alternatively, send an email to fedora-trans-list, the mailing list for your language team, or directly to the maintainer of it. | If you have any questions regarding your migration process, drop by IRC on Freenode, channel #fedora-l10n. Alternatively, send an email to fedora-trans-list, the mailing list for your language team, or directly to the maintainer of it. | ||
| − | {{ | + | {{Admon/tip | See also | [[Communicate/IRCHowTo| IRC HowTo]] , [[Communicate#ML| Mailing lists help]]}} |
| − | |||
[[Category:Localization]] | [[Category:Localization]] | ||
Latest revision as of 18:27, 25 June 2009
Contents |
[edit] Mass move of Fedora modules
On February 18, 2008 the Fedora Project is moving all translatable Fedora projects from the i18n.redhat.com (also known as elvis) over to Fedora servers ( original announcement )
The move of all Fedora-related modules from elvis to Fedora servers allows us to better maintain them, hook them up with the Fedora Account System, and increase their interoperability with the rest of our infrastructure. This move is part of our effort to grow our community and open up our processes and will help us increase the number of Fedora languages and their quality, and also lower the barrier of entry for new translators.
[edit] Overview
Here's a quick list of what a translator needs to do to migrate to the new systems.
- Become a member of the Fedora Localization Project. To learn how to create a Fedora account and join the 'cvsl10n' group, read the Fedora Translation Quick Start Guide .
- Visit the Project's homepage with translation statistics and other information at http://translate.fedoraproject.org/.
- If no team is associated with your language, create one .
- Download your PO files for Fedora 9 or other resources .
- Submit them through Transifex , or in the case of modules hosted on cvs.fedoraproject.org, also using the command line.
The most useful docs to help you understand the new processes are the Quick Start Guide and the L10n FAQ .
[edit] What should I do to continue contributing translations?
Here are some detailed information about migrating to the new systems.
[edit] Join the translation team
The first thing you need to do to migrate to our new architecture, is to create a Fedora Account, if you haven't done so already. With a Fedora account you will have access to Transifex, our new tool to submit translations, and especially for cvs.fedoraproject.org, you'll have access to contribute from the command line as well. To learn how to create an account, take a look at the Translation Quick Start Guide, chapter 'accounts' .
Since you probably already have an SSH key you used on elvis, you don't need to create a new one. Skip step 2.3 in the guide, and use that one when creating your Fedora account. To find out the GPG key for an existing key of yours, you can use the command gpg -K.
[edit] Language teams
One of the most important aspects of the Translation project is that we work in language teams. This way, we get to discuss with people in our own languages, peer review our contributions, and allow users to send suggestions for our translations directly to us. Furthermore, some local groups meet together to work on issues they like in real life. That's why the Join procedure has a step to help you join your language's team and introduce yourself to it.
If the team list page doesn't have your team or has an
exclamation mark saying there is no Maintainer for the team, please step up as one to help coordinate the activities for that team!
[edit] Getting the translation files
Our new L10n architecture allows developers to host their projects anywhere they want. Take a look at the modules list page on the Fedora Localization website: projects are hosted on a variety of repositories.
This means that the old way of accessing everything from one, centralized server will no longer work. There are several ways of getting the translation files listed at the get-files FAQ , the last one being probably the easiest:
export MYLANG=<lang-code> wget -q -r -N -l 1 --accept *$MYLANG.po -nd -nH -P pofiles http://translate.fedoraproject.org/languages/$MYLANG/fedora-9
[edit] Submitting the files
Since projects can be hosted on any server, how are you supposed to submit files to them? We've simplified the commit procedure in an easy to use web interface called 'Transifex'. Once you have a Fedora account and become a member of 'cvsl10n', you can use it to submit translations to any Fedora related project:
https://translate.fedoraproject.org/submit/
[edit] Then what?
Well, if you followed all the steps for joining the projects, you're now subscribed to fedora-trans-list, where we discuss the project's major topics, and arrange our IRC meetings. You're probably also a member of a language team, often with its own mailing list, to meet peers and discuss things around contributions in your language. If you sent a short introduction about yourself to -trans-list, probably some people will contact you to work on stuff both of you are interested.
Finally, if you've stepped up as a language maintainer, you'll often get contacted for information about joining your team or maybe mistakes in your language's translations from time to time.
[edit] Useful resources
- The Fedora Translation Quick Start guide
- Frequently Asked Questions about L10n
- How to create a new team or become a language maintainer
- Original announcement to fedora-devel-announce
[edit] Getting help
If you have any questions regarding your migration process, drop by IRC on Freenode, channel #fedora-l10n. Alternatively, send an email to fedora-trans-list, the mailing list for your language team, or directly to the maintainer of it.