(→Fedora L10N Steering Committee: update, no agenda) |
(→Commits list: Update to FAS2) |
||
Line 45: | Line 45: | ||
* We've setup the group 'l10n-commits' for those who would like to receive emails for commits in the <code>/cvs/l10n/</code> repo and various other emails. | * We've setup the group 'l10n-commits' for those who would like to receive emails for commits in the <code>/cvs/l10n/</code> repo and various other emails. | ||
* To subscribe, go to [https://admin.fedoraproject.org/accounts/ | * To subscribe, go to the [https://admin.fedoraproject.org/accounts/ Fedora Accounts System] and add yourself to [https://admin.fedoraproject.org/accounts/group/view/l10n-commits l10n-commits]. Unfortunately the system needs approval, so someone should jump in to approve you, which should happen quickly. | ||
=== IRC channel === | === IRC channel === |
Revision as of 07:15, 28 May 2008
The Fedora Localization Project
The goal of the Fedora Localization Project (FLP) is to bring everything around Fedora (the Software, Documentation, Websites and culture) closer to local communities (countries, languages and in general cultural groups). Usually this involves doing translations via PO files but is certainly not limited to that.
Language list
Refer to http://translate.fedoraproject.org/languages for an overview of how many languages are available and have substantial translation of our essential software.
Joining the Fedora Localization Project
To learn how to join Fedora Localization Project, please refer to the Join page.
New Translator | Old Translators (from i18n.redhat.com) |
other ways to help |
- Translation Quick Start Guide - TQSG (updated, see v0.4.1) - Repository Access - CVS Basics - FAQ - Website Translation - KDE Translation HOWTO - GNOME L10n Resources - GNU gettext Manual |
- Repository Access - TQSG (updated, see v0.4.1) - FAQ - GUI page |
- Bug Reporting - Become a Maintainer - Project Maintenance |
- More info can be found on the Documentation Translation page, which is specific to the Docs Project.
- Statistics for most software translations can be found at http://translate.fedoraproject.org.
Some more links:
Teams
- Teams are currently listed/managed at the translate.fp.o teams page .
Communication
Mailing list
There are some mailing lists that interest members of the FLP.
- The main list is fedora-trans-list (archive ), which holds discussions about translations, team coordination, etc.
- Technical issues are discussed at fedora-i18n-list . If you are interested in more than translations, like eg. our websites, bugzilla, the mailing list, etc, you would want to join this as well.
Commits list
- We've setup the group 'l10n-commits' for those who would like to receive emails for commits in the
/cvs/l10n/
repo and various other emails. - To subscribe, go to the Fedora Accounts System and add yourself to l10n-commits. Unfortunately the system needs approval, so someone should jump in to approve you, which should happen quickly.
IRC channel
#fedora-l10n
on freenode
Meetings
- See L10N/Meetings
Schedule
Both of these schedules include translation freeze dates, which are dates that translations are picked up for adding them into the product.
Tasks
Take a look at the L10N/Tasks page and add your name next to an item you are interested in helping out.
Fedora L10N Steering Committee
The Fedora Localization Steering Committee (FLSCo) leads the Fedora Localization Project (FLP). Its mission is to provide the Fedora translators with necessary guidance, and support their efforts to localize the Fedora Project to multiple languages and cultures.
If you have a question, need clarifications or have problems, please contact Fedora L10N Steering Committee.
For more information: Fedora L10N Steering Committee
Bug Reporting, Testing, and Quality Assurance
Before you file a bug, please read through the list of current and previous bugs for the cooresponding software package to determine if your bug has already been filed. If your bug does not exists, enter a bug report using the Bugzilla bug entry page. If your bug exists and has not been fixed, add additional information to the existing bug. If your bug exists and has been fixed, upgrade to the version in the bug report to determine if the bug was properly fixed. If it was not, reopen the bug.
Useful Bugzilla pages:
Some other interesting Bugzilla queries:
- All open translation bugs (searches for "translation" keyword)
- All font-related bugs (searches for "font" in Summary)
- All i18n bugs (searches for "i18n" keyword)