L10N Maintainer

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Fedora Translation Announcement mailing list)
m (Bugzilla: cvs is gone)
 
(21 intermediate revisions by 7 users not shown)
Line 1: Line 1:
= The Fedora Localization Project - Maintainer =
+
{{autolang|base=yes}}
 +
{{admon/important|In progress|This page is being updated. Ask your questions to the trans mailing list if things are still unclear.}}
  
This page contains useful information for all language maintainers (coordinators).
+
= The Fedora Localization Project - Language Maintainer =
  
 
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.
 
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 ==
+
A "maintainer" is called a "coordinator" on our localization plateform, Transifex. You could define 2 coordinators in order to be safe and always have someone responsive.
  
Take a look at our [http://translate.fedoraproject.org/teams existing teams]. If your language group does not already have a maintainer, step up to be one by following the steps below.
+
== Become a Language Maintainer ==
  
{{ /code/| on Freenode.
+
Take a look at our [[L10N_Teams| existing teams]]. Check also that there is no pending request on [https://fedora.transifex.com/ transifex.com], if so, get in touch with them. If your language group does not already have a maintainer, step up to be one by following the steps below. You need to have a [https://admin.fedoraproject.org/accounts/ FAS account] and a [https://bugzilla.redhat.com/ Bugzilla account].
}}
+
  
1. Go through [[L10N/Join| ]] and follow all steps. Maintainers should have a good understanding of our tools and resources.
+
* Write to the [https://lists.fedoraproject.org/mailman/listinfo/trans trans] mailing list and tell the group that you want to be the maintainer/coordinator. Subscribe to this mailing list if not done yet. This is the one that you'll use to gain L10n support.
  
1. Write to <code>fedora-trans-list</code> and tell the group that you want to be the maintainer/coordinator.
+
* Update [[L10N_Teams| L10N Teams]] to add your team info there. See [[L10N_FAQ#new-team| L10N FAQ]] for more info.
  
1. Update [http://translate.fedoraproject.org/ translate.fpo] to add your team info there. See [[L10N/FAQ#new-team| L10N/FAQ#new-team]]  for more info.
+
* Ask on the <code>trans</code> mailing list (or best: open a bugzilla ticket for this request) and ask to update the [http://git.fedorahosted.org/git/?p=l10n/owners.git;a=blob_plain;f=owners.list;hb=master owners.list file] with your Bugzilla information. Someone can help you on IRC for this (#fedora-trans on freenode).
  
1. Update the [http://cvs.fedora.redhat.com/viewcvs/owners/owners.list?root=l10n&view=markup 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.
+
* 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.
  
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.
+
{{admon/note|Creating a New Mailing List| To request a new mailing list, please [https://fedorahosted.org/fedora-infrastructure open a ticket at Fedora Infrastructure]. If you are to discuss only translations, a name like <code>trans-XX</code> is appropriate (eg. trans-de). You can log in with your FAS credentials. Don't forget to link to your request/presentation on the <code>trans</code> mailing list (the archives are [http://lists.fedoraproject.org/pipermail/trans/ there].
 +
If you have bigger plans and would like at some point to address also end-users, a name like <code>XX-users</code> could be considered.}}
  
* To request a new mailing list, please [https://fedorahosted.org/fedora-infrastructure open a ticket at Fedora Infrastructure]. If you are to discuss only translations, a name like <code>fedora-trans-XX</code> 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 <code>fedora-XX-list</code> could be considered.
+
* Make sure your team gets to know you by sending a [[L10N_Self_introduction| self-introduction]] to the your local mailing list.
  
* Make sure your team gets to know you by sending a [[L10N/Join/SelfIntroduction| self-introduction]] to the your local mailing list.
+
* Subscribe to our translating platform, [https://fedora.transifex.com/ transifex.com] then ask to create a new team.  
  
* As the maintainer of the language, you could be one of the admins of the list.
+
* 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! :)
  
1. Subscribe to the [[L10N/Tools#commits-list| 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.
+
== Joining the 'cvsl10n' Group Sponsor of FAS ==
  
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! :)
+
Translator could ask to join the 'cvsl10n' group of FAS to gain access of several sweeties like the [[EmailAliases|Fedora aliases]] or the [[Infrastructure/fedorapeople.org|fedora people repo]].
  
== Becoming a 'cvsl10n' group Sponsor of FAS ==
+
There should be enough cvsl10n sponsors but in case you need to become one, do the following steps:
 +
 
 +
* Post a request e-mail to trans mailing list with your FAS username, letting 'Administrator' know.
 +
 
 +
* Edit [[L10N_Teams| L10N Teams]] page by adding you as 'Sponsor'.
  
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 [http://fedoraproject.org/wiki/L10N/GroupSponsors L10N/GroupSponsors] page by adding you as 'Sponsor'.
 
 
* 'Administrator' will upgrade you from 'User' to 'Sponsor'.   
 
* 'Administrator' will upgrade you from 'User' to 'Sponsor'.   
  
=== Approving new translator ===
+
=== Approving New Translators ===
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.
+
This is done through our translating plateform, [https://transifex.com Transifex].
* Go to FAS and login.
+
Do not approve any unknown user(s) who has not made proper self-intro on your mailing list if you've one, or on the general <code>trans</code> one.
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.
+
One of our core values is "Friend". Better to know at least a little each other, we are a community.
* 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.
+
* When you find a self-introduction of your language on trans mailing list, check if he/she has also sent in self-introduction to your local mailing list. If he/she has not sent in then kindly ask for it.
* Now this user is approved and be able to submit his/her translation via Transifex.
+
 
  
 
== Bugzilla ==
 
== Bugzilla ==
  
In order to create bugzilla components for languages, we have an <code>owners.list</code> file. You can find it in the L10n CVS, at [http://cvs.fedoraproject.org/viewcvs/owners/?root=l10n /cvs/l10n/owners/]. Each organized language group should have an entry there.
+
In order to create Bugzilla components for languages, we have an <code>owners.list</code> file. You can find it in the L10n git repository, at [http://git.fedorahosted.org/git/?p=l10n/owners.git;a=blob_plain;f=owners.list;hb=master 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 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:
 
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: https://www.redhat.com/mailman/admin/fedora-trans-fr
+
* Create a new Bugzilla account for your mailing list.
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 <code>bugzilla (at) redhat (dot) com</code> in the accept_these_nonmembers box.
+
 
 +
* Visit the admin mailman page of the list, for example: [https://admin.fedoraproject.org/mailman/listinfo/trans-fr]
 +
 
 +
* 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 <code>bugzilla (at) redhat (dot) com</code> in the accept_these_nonmembers box.
  
 
== Fedora Translation Announcement mailing list ==
 
== Fedora Translation Announcement mailing list ==
 +
{{admon/important|Dead|We don't use this list anymore. Kept here by the time that this mailing list is removed.}}
  
 
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.
 
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.
Line 65: Line 71:
 
To setup your mailing list to allow these announcements to pass:
 
To setup your mailing list to allow these announcements to pass:
  
1. Visit https://www.redhat.com/mailman/listinfo/fedora-trans-announce and subscribe your mailing list (e-mail address would for example be: fedora-trans-fr@redhat.com). 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)
+
* Visit [https://admin.fedoraproject.org/mailman/listinfo/trans-announce] and subscribe your mailing list (e-mail address would for example be: trans-fr@lists.fedoraproject.org). 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: https://www.redhat.com/mailman/admin/fedora-trans-fr
+
* Visit the admin mailman page of your own list, for example: [https://admin.fedoraproject.org/mailman/listinfo/trans-fr]
  
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 <code>fedora-trans-announce (at) redhat (dot) com</code> in the accept_these_nonmembers box.
+
* 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 <code>trans-announce@lists.fedoraproject.org</code> in the accept_these_nonmembers box.
  
 
[[Category:Localization]]
 
[[Category:Localization]]

Latest revision as of 11:03, 15 April 2013

Important.png
In progress
This page is being updated. Ask your questions to the trans mailing list if things are still unclear.

Contents

[edit] The Fedora Localization Project - Language Maintainer

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.

A "maintainer" is called a "coordinator" on our localization plateform, Transifex. You could define 2 coordinators in order to be safe and always have someone responsive.

[edit] Become a Language Maintainer

Take a look at our existing teams. Check also that there is no pending request on transifex.com, if so, get in touch with them. If your language group does not already have a maintainer, step up to be one by following the steps below. You need to have a FAS account and a Bugzilla account.

  • Write to the trans mailing list and tell the group that you want to be the maintainer/coordinator. Subscribe to this mailing list if not done yet. This is the one that you'll use to gain L10n support.
  • Ask on the trans mailing list (or best: open a bugzilla ticket for this request) and ask to update the owners.list file with your Bugzilla information. Someone can help you on IRC for this (#fedora-trans on freenode).
  • 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.
Note.png
Creating a New 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 trans-XX is appropriate (eg. trans-de). You can log in with your FAS credentials. Don't forget to link to your request/presentation on the trans mailing list (the archives are there. If you have bigger plans and would like at some point to address also end-users, a name like XX-users could be considered.
  • Make sure your team gets to know you by sending a self-introduction to the your local mailing list.
  • Subscribe to our translating platform, transifex.com then ask to create a new team.
  • 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! :)

[edit] Joining the 'cvsl10n' Group Sponsor of FAS

Translator could ask to join the 'cvsl10n' group of FAS to gain access of several sweeties like the Fedora aliases or the fedora people repo.

There should be enough cvsl10n sponsors but in case you need to become one, do the following steps:

  • Post a request e-mail to trans mailing list with your FAS username, letting 'Administrator' know.
  • 'Administrator' will upgrade you from 'User' to 'Sponsor'.

[edit] Approving New Translators

This is done through our translating plateform, Transifex. Do not approve any unknown user(s) who has not made proper self-intro on your mailing list if you've one, or on the general trans one. One of our core values is "Friend". Better to know at least a little each other, we are a community.

  • When you find a self-introduction of your language on trans mailing list, check if he/she has also sent in self-introduction to your local mailing list. If he/she has not sent in then kindly ask for it.


[edit] Bugzilla

In order to create Bugzilla components for languages, we have an owners.list file. You can find it in the L10n git repository, at 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:

  • Create a new Bugzilla account for your mailing list.
  • 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.

[edit] Fedora Translation Announcement mailing list

Important.png
Dead
We don't use this list anymore. Kept here by the time that this mailing list is removed.

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:

  • Visit [2] and subscribe your mailing list (e-mail address would for example be: trans-fr@lists.fedoraproject.org). 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).
  • 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 trans-announce@lists.fedoraproject.org in the accept_these_nonmembers box.