How do I join a translation team?

Asked by Peggy WiserEarth

I've been trying to find the "Join" button for the Launchpad Translation Group, so that I can review and approve the translations for my WiserEarth project. But I don't see any such links on the translation group page ->

https://translations.launchpad.net/+groups/launchpad-translators

Nor do I see any information on who to contact to let me into the group. What should I be doing or where should I be going to join the group?

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Jeroen T. Vermeulen (jtv) said :
#1

Two misconceptions here.

First, a translation group is a very different thing from a translation team. A translation team manages translations to a given language. A translation group is a group of translation teams that work together on the same set of projects, each for its own language of course.

Second, translation groups do not review and approve translations for projects. Three entities do that:

1. The auto-approver. This is an automated job that regularly (several times an hour, normally) tries to match uploaded templates and translations to known templates and languages, and where it finds matches, approves them.

To get this to work for you, make sure that each of your templates is in its own directory; that the filenames are all in lower-case; that each translation file is in exactly the same directory as its template; and that each translation file has a name consisting of exactly the language code plus filename extension, e.g. "es.po" for Spanish and "de.po" for German and so on. (You can also get around the approval process to some extent by uploading each individual file from the translation pages for its particular template and language, instead of from the central upload link).

2. The branch auto-approver. This is another automated job that runs within a similar timeframe, but for translations and templates that are automatically imported from bzr branches. It's a bit more aggressive than the normal auto-approver because it sees more complete information. Still, make sure you use the right naming scheme as with the regular auto-approver.

3. Us developers. We check that uploads satisfy our policies and do not cause certain types of problems that otherwise you might not notice until later.

We come in when a new template is first uploaded for a new release series—or if a template is uploaded with a different path/filename than before, which to the system looks exactly like a new template. It can take us several days to get to your upload, so try to avoid this where possible.

In your case, I don't see anything waiting for approval on the import queue so I guess the auto-approvers have already taken care of it.

Jeroen

Can you help with this problem?

Provide an answer of your own, or ask Peggy WiserEarth for more information if necessary.

To post a message you must log in.