Archive:L10N/FedoraModulesMove

From FedoraProject

Revision as of 18:27, 25 June 2009 by Raven (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Cog.png
It has been requested that this page be deleted.
Outdated content

Contents

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.

Idea.png
A more detailed rationale can be found at the Move coordination page, together with a full list of all modules being moved.

Overview

Idea.png
All elvis users need to create new Fedora accounts to continue working on Fedora translations.

Here's a quick list of what a translator needs to do to migrate to the new systems.

The most useful docs to help you understand the new processes are the Quick Start Guide and the L10n FAQ .

What should I do to continue contributing translations?

Here are some detailed information about migrating to the new systems.

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.

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 Warning.png exclamation mark saying there is no Maintainer for the team, please step up as one to help coordinate the activities for that team!

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

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/


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.

Useful resources

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.