Coordination of l10n teams


The program that listens to debian-l10n-* lists understands pseudo-URLs in the subject header. The pseudo-URLs need to have the following form.

[<state>] <type>://<package>/<file>

The state must be one of the following: TAF, MAJ, ITT, RFR, LCFC, BTS#<bug number>, DONE, or HOLD.

TAF (Travail À Faire)
Sent by a coordinator (not by a random list member) to indicate that there is a document that needs to be worked on.
MAJ (Mise À Jour)
Sent by a coordinator (not by a random list member) to indicate that there is a document that needs to be updated and that the work is reserved for the previous translator.
ITT (Intent To Translate)
Sent to indicate that you plan to work on the translation; used to avoid double work.
If you send an [ITT] message and somebody else send another [ITT] for the same file, please send a new message immediately on the mailing list to remind him you have the priority. The goal is to avoid useless work.
RFR (Request For Review)
An initial draft translation is attached. Others on the list are requested to check it for errors and send a reply (possibly off-list if they found no flaws).
Further RFRs may follow if substantial changes have been made.
ITR (Intent To Review)
Used to avoid LCFCs being sent when there are reviews pending.
Mainly used when you expect your review not to be ready for several days (because the translation is big, or you don't have any time before the weekend, etc.)
The mail body should contain an indication of when to expect the review.
Note that ITR pseudo-URLs are ignored by the spider.
LCFC (Last Chance For Comment)
Indicates that translation is finished, with changes from the review process incorporated, and that it will be sent to the appropriate place.
Can be sent when there are no ITRs, and discussion following the last RFR has ended for a few days.
Should not be sent before there has been at least one review.
BTS#<bug number> (Bug Tracking System)
Used to register a bug number once you have submitted the translation to the BTS.
The spider will regularly check if an open bug report has been fixed or closed.
Used to close a thread once the translation has been dealt with; useful if it has not been sent to the BTS.
Used to put a translation on hold, for example when more changes are due (if there is errors about translation in the package or the translation is available somewhere else).
The goal of this status is to avoid unuseful work.

The type can be anything indicating the type of the document, such as po-debconf, po, po4a, or wml.

package is the name of the package that the document comes from. Please use or nothing for the WML files of the Debian web site.

file is the filename of the document; it can contain other information to uniquely identify the document, such as the path to the file. It's usually a name like lc.po where lc is the language code (e.g.: de for German, or pt_BR for Brazilian Portuguese).

The structure of file depends on the chosen type, and of course the language. In principle it's just an identifier, but since it's used on these web pages to track the status of translations, it's strongly recommended to follow the scheme given below.

The BTS state is somewhat special; it registers a bug number so the l10n-bot can track the status of the translation once submitted to the BTS by checking whether any of the open bug reports have been closed. Thus for instance the debian-l10n-spanish list might use:

[BTS#123456] po-debconf://cups/es.po

If you intend to translate a lot of packages, you can ITT them all at once. An example (for the debian-l10n-danish list):

[ITT] po-debconf://{cups,courier,apache2}/da.po

So put the packages between braces and separate them with commas. No extra spaces!