Coordinating a Translation Team
[
English
]
Table of Contents
This page is a short description of the role played by the GNU Translation Team Coordinator.
The following is a list of the tasks a coordinator of a traslation team should perform:
- 1. Contact constantly, at least once a month, the Web Translations Manager <[email protected]> to let hir (her or him) know
about the development of the team. Important information to provide the web-translators is : Number of old and new volunteers and number of pages
translated since the last contact.
- 2. Provide first help to newcoming volunteers willing to join the team. Ask them to read the general translation directives, and inform hir about the role to be played inside
the team, as well of any internal rules.
- 3. Keep a record of the in-progress translations on the team. This can be done in any way the coordinator find easier: Either
writing a web page and uploading it to the web server, or a local record on hir machine.
- 4. Make sure that every page is reviewed at least by two volunteers not involved in the original translation, when possible.
- 5. Upload the pages to the web server using CVS.
- 6. Monitor the changes on the server to keep the translations current.
Start easy. The first pages to translate should be those with few paragraphs. Do this until you get more
fluent with the translation process.
Do not translate the GNU Flashes. This section of the GNU Home page changes too often to keep it current. Include the GNU Flashes
only if your team is big enough to keep pace of this changes
(> 15 volunteers).
Do not translate the boilerplate or any other page which is intended to be read primarily by the GNU
volunteers, like the general translation directives or this page. It's useless.
https://savannah.gnu.org/cvs/?group_id=23
We are very serious about the privacy. The coordinator of a translation team may choose to include either (or
none) of these data into the /server/standards/README.translations.html
file.
- Coordinator complete name or an alternative alias.
- Email email address (either at GNU.org or a private address).
- Group email address. [email protected].
- Group web URL, when available. This address should be preferably at the GNU.org web site. Remember not to link
any site where propietary software is announced, advertised or promoted.
Note : Do not translate this page.
[
English
]
Return to GNU's home page.
Please send FSF & GNU inquiries & questions to
[email protected].
There are also other ways to
contact the FSF.
Please send comments on these web pages to
[email protected],
send other questions to
[email protected].
Copyright (C) 2001 Free Software Foundation, Inc.,
51 Franklin St, Fifth Floor, Boston, MA 02110, USA
Verbatim copying and distribution of this entire article is
permitted in any medium, provided this notice is preserved.
Updated:
$Date: 2005/06/09 17:35:36 $ $Author: alex_muntada $