L10N/Guide/Coordinator: Difference between revisions

Latest revision as of 10:15, 7 April 2020

In other languages: English (en) português do Brasil (pt-br) [edit]

The Fedora Localization Project - Language Coordinator

The coordinator is the contact point for the group. Each language group should have a coordinator, 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 coordinator should already be familiarized with our tools and processes.

You could define 2 coordinators in order to be safe and always have someone responsive.

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

Approving New Translators

Each new contributor has to follow these steps: L10N/Guide#Creating_a_Fedora_Account

You role as a coordinator is to make sure the process is respected, and to validate each necessary steps (usually FAS group and Weblate, sometimes mailing list subscription).

Do not approve any unknown user(s) who has not made proper self-intro on your mailing list if you have one, or on the general one.

One of our core values is "Friend". Better to know at least a little each other, we are a community.

Becoming a Language Coordinator

Take a look at our existing teams. If your language group does not already have a coordinator, step up to be one by following the steps below. You need to have a FAS account and a Bugzilla account.

If there is a current coordinator and you will be taking over the role with some reason, the current coordinator must agree and post an announcement of this hand-over to the trans mailing list. In case the current coordinator is totally unresponsive, first please contact the administrator.

Write to the trans mailing list and tell the group that you want to be the coordinator. Subscribe to this mailing list if not done yet. This is the one that you'll use to gain L10N support.
- Is it an handover from old/new coordinator? We would really like to see the precedent coordinator sending an e-mail to make it official, so we limit eventual conflicts and can welcome the new coordinator.

Update L10N Teams to add your team info there. See L10N FAQ for more info.

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-g11n^[?]).

Make sure your team gets to know you by sending a self-introduction to the your local mailing list.

Language Mailing List

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 trans-XX is appropriate (e.g. 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 here).

If you have bigger plans and would like at some point to address also end-users, a name like XX-users could be considered.

Weblate Languages

Subscribe to our translating platform, Fedora Weblate, then ask to create a new team.

FAS: Becoming the cvsl10n Group Sponsor

Post a request e-mail to trans mailing list with your FAS username, letting the Administrator know. If it is take-over, then the current coordinator's announcement post can trigger the Administrator's action.

Edit L10N Teams page by adding you as a Sponsor.

According to FAS vocable: the Administrator will upgrade you from a User to a Sponsor.

Bugzilla

In order to create a Bugzilla component for a language, please file a ticket at fedora-infrastructure

@@ Line 1: / Line 1: @@
-= The Fedora Localization Project - Maintainer =
+{{autolang|base=yes}}
+[[Image:L10n-images-coordinator.png|right]]
-This page contains useful information for all language maintainers (coordinators).
+== The Fedora Localization Project - Language Coordinator ==
-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 coordinator is the contact point for the group. Each language group should have a coordinator, 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 coordinator should already be familiarized with our tools and processes.
-== Become a language maintainer ==
+You could define 2 coordinators in order to be safe and always have someone responsive.
-Take a look at our [[L10N/Teams| existing teams]]. If your language group does not already have a maintainer, step up to be one by following the steps below.
+Your role is to organize your team, build it up, help your team members... Take all the actions to make your team a strong and successful community inside the Fedora Localization Project. But don't forget to have fun! :)
-. Go through [[L10N/Join]] and follow all steps. Maintainers should have a good understanding of our tools and resources.
+== Approving New Translators ==
-. Write to <code>fedora-trans-list</code> and tell the group that you want to be the maintainer/coordinator.
+Each new contributor has to follow these steps: [[L10N/Guide#Creating_a_Fedora_Account]]
-. Update [[L10N/Teams]] to add your team info there. See [[L10N/FAQ#new-team| L10N/FAQ#new-team]] for more info.
+You role as a coordinator is to make sure the process is respected, and to validate each necessary steps (usually FAS group and Weblate, sometimes mailing list subscription).
-. 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.
+Do not approve any unknown user(s) who has not made proper self-intro on your mailing list if you have one, or on the [https://lists.fedoraproject.org/admin/lists/trans.lists.fedoraproject.org/ general] one.
-. 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.
+One of our core values is "Friend". Better to know at least a little each other, we are a community.
-* 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.
+== Becoming a Language Coordinator ==
-* Make sure your team gets to know you by sending a [[L10N/Join/SelfIntroduction| self-introduction]] to the your local mailing list.
+Take a look at our [[L10N_Teams| existing teams]]. If your language group does not already have a coordinator, 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].
-* As the maintainer of the language, you could be one of the admins of the list.
+If there is a current coordinator and you will be taking over the role with some reason, the current coordinator must agree and post an announcement of this hand-over to the {{fplist||trans}} mailing list. In case the current coordinator is totally unresponsive, first please contact the administrator.
-. 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.
+* Write to the {{fplist|trans}} mailing list and tell the group that you want to be the coordinator. Subscribe to this mailing list if not done yet. This is the one that you'll use to gain L10N support.
+** Is it an handover from old/new coordinator? We would really like to see the precedent coordinator sending an e-mail to make it official, so we limit eventual conflicts and can welcome the new coordinator.
-. 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! :)
+* Update [[L10N_Teams| L10N Teams]] to add your team info there. See [[L10N_FAQ#new-team| L10N FAQ]] for more info.
-== Becoming a 'cvsl10n' group Sponsor of FAS ==
+* Ask on the {{fplist|trans}} 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 ({{fpchat|#fedora-g11n}}).
-To approve up-coming new translator in your team, it is needed to become a 'cvsl10n' group Sponsor of FAS.
+* Make sure your team gets to know you by sending a [[L10N_Self_introduction| self-introduction]] to the your local mailing list.
-* 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'.
-=== Approving new translator ===
+== Language Mailing List ==
-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.
-. 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.
-== Bugzilla ==
+* 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.
-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.
+* To request a new mailing list, please [https://pagure.io/fedora-infrastructure/issues open a ticket at Fedora Infrastructure]. If you are to discuss only translations, a name like <code>trans-XX</code> is appropriate (''e.g.'' trans-de). You can log in with your FAS credentials. Don't forget to link to your request/presentation on the {{fplist|trans}} mailing list (the archives are [https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org/ here]).
+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.
-If you are the maintainer of a language, put your '''Bugzilla''' e-mail and your language's mailing list, just like the other lines.
+== Weblate Languages ==
-If you want your mailing list to receive automatic emails for each new bug report opened to your language:
+* Subscribe to our translating platform, [https://translate.fedoraproject.org/ Fedora Weblate], then ask to create a new team.
-. Create a new bugzilla account for your mailing list.
-. Visit the admin mailman page of the list, for example: https://www.redhat.com/mailman/admin/fedora-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 ==
+== FAS: Becoming the cvsl10n Group Sponsor ==
-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.
+* Post a request e-mail to trans mailing list with your FAS username, letting the Administrator know. If it is take-over, then the current coordinator's announcement post can trigger the Administrator's action.
-To setup your mailing list to allow these announcements to pass:
+* Edit [[L10N_Teams| L10N Teams]] page by adding you as a ''Sponsor''.
-. 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)
+* According to FAS vocable: the ''Administrator'' will upgrade you from a ''User'' to a ''Sponsor''.
-. Visit the admin mailman page of your own list, for example: https://www.redhat.com/mailman/admin/fedora-trans-fr
+== Bugzilla ==
-. 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.
+In order to create a Bugzilla component for a language, please file a ticket at [https://pagure.io/fedora-infrastructure/issues fedora-infrastructure]
 [[Category:Localization]]

Search