From Fedora Project Wiki

< L10N‎ | Guide

Revision as of 23:49, 12 June 2009 by Raven (talk | contribs)

The Fedora Localization Project - Maintainer

This page contains useful information for all language maintainers (coordinators).

The maintainer is the contact point for the group. Each language group should have a maintainer, so that other people can reach the group easily and new members can request for help directly from a person in the team. For this reason, a maintainer should already be familiarized with our tools and processes.

Become a language maintainer

Take a look at our existing teams. If your language group does not already have a maintainer, step up to be one by following the steps below.

1. Go through L10N/Join and follow all steps. Maintainers should have a good understanding of our tools and resources.

1. Write to fedora-trans-list and tell the group that you want to be the maintainer/coordinator.

1. Update L10N/Teams to add your team info there. See L10N/FAQ#new-team for more info.

1. Update the owners.list file in the CVS and add your Bugzilla information. Alternatively, use the same bug report of previous step and put in it a line from the above file specific to your language. Someone can help you on IRC for this.

1. If your team doesn't have a mailing list of its own, create one: each team with over 2-3 members should have its own mailing list.

  • To request a new mailing list, please open a ticket at Fedora Infrastructure. If you are to discuss only translations, a name like fedora-trans-XX is appropriate (eg. fedora-trans-de). If you have bigger plans and would like at some point to address also end-users, a name like fedora-XX-list could be considered.
  • Make sure your team gets to know you by sending a self-introduction to the your local mailing list.
  • As the maintainer of the language, you could be one of the admins of the list.

1. Subscribe to the l10n-commits list to receive notifications by email when a file in CVS related to translations has changed. This will help you monitor the commits for new modules, POT file changes and commits from the members of your team.

1. Organize your team, build it up, help your team members... Take all the leader actions to make your team a strong and successful community inside the Fedora Localization Project. But don't forget to have fun! :)

Becoming a 'cvsl10n' group Sponsor of FAS

To approve up-coming new translator in your team, it is needed to become a 'cvsl10n' group Sponsor of FAS.

  • Post a request mail into fedora-trans-list with your FAS username.
  • Edit L10N/GroupSponsors page by adding you as 'Sponsor'.
  • 'Administrator' will upgrade you from 'User' to 'Sponsor'.

Approving new translator

Please remember that all other 'Sponsors' are expecting you to approve all new translators for your language team. For example if you are 'Sponsor' from Danish team, then generally you should approve all new Danish translators, but not other languages except the language with no sponsor. Do not approve any unknown user(s) appeared in the section who has not made proper self-intro.

  • When you find a self-intro of your language on fedora-trans-list, check if he/she has also sent in self-intro to your local ml. If he/she has not sent in then kindly ask for it.
  • Go to FAS and login.

3. In "Your Fedora Account" page, there are the list of groups which you have joined. Find the group name "Translation CVS Commit Group (Sponsor)" and click it. You will be moved to that group page.

  • In "Translation CVS Commit Group (cvsl10n)" page, scroll down to the section of "Sponsorship Queue".
  • Find the target username and click "Sponsor" in "Action" column located far right.
  • Now this user is approved and be able to submit his/her translation via Transifex.


In order to create Bugzilla components for languages, we have an owners.list file. You can find it in the L10n CVS, at /cvs/l10n/owners/. Each organized language group should have an entry there.

If you are the maintainer of a language, put your Bugzilla e-mail and your language's mailing list, just like the other lines.

If you want your mailing list to receive automatic emails for each new bug report opened to your language: 1. Create a new bugzilla account for your mailing list. 1. Visit the admin mailman page of the list, for example: 1. The admin of the list is shown at the bottom. If you are not the one, contact the person and ask him to configure the list appropriately: At the "Privacy" -> "Sender filter" section, add bugzilla (at) redhat (dot) com in the accept_these_nonmembers box.

Fedora Translation Announcement mailing list

The Fedora Localization Project has an announcement mailing list, where all project-wide announcements will be sent. This list only works if all language mailing list get these announcements.

To setup your mailing list to allow these announcements to pass:

1. Visit and subscribe your mailing list (e-mail address would for example be: An admin will verify your subscription (this is to make sure that normal users don't register for this list, they get these mails through the various other translation mailing lists)

2. Visit the admin mailman page of your own list, for example:

3. The admin of the list is shown at the bottom. If you are not the one, contact the person and ask him to configure the list appropriately: At the "Privacy" -> "Sender filter" section, add fedora-trans-announce (at) redhat (dot) com in the accept_these_nonmembers box.