As far as I know, l10n_server is almost done to work as centralized translation server and should certainlly be able to host all the current translation servers published in this module frontpage.
I have previously seen some comments about the server but is there roadmap? something for let the community collaborate?
and the domain. Is it going to be l10n.drupal.org? drupal.org/l10n?
Sorry for the mess of questions...
Blessings!

Comments

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

The central localizations server will run on its own Drupal instance on a subdomain on drupal.org. It might be t.drupal.org, translate.drupal.org, l10n.drupal.org, etc. There are three angles where work is to be done to set up the central server:

1. Performance:

- #375826: Fill in empty initial translations to use INNER JOIN
- #375817: Performance: denormalize releases, files and lines with project/release info Assigned to: gábor hojtsy
- #375821: Split archived and live data

2. Userbase. Since the new Drupal instance will have its own userbase, and we would not like to set up another subsite with a userbase on its own, settings up an OpenID server on the main site and then relying on those OpenID login for our users is the goal. See #353425: Allow other sites to use drupal.org user identities for login (in D7 infrastructure, without shared secrets) and more broadly http://drupal.org/project/issues-term/819

3. Packaging. The setup of the central l10n_server will obsolete using CVS for translations. We need to make up our new rules and ways for packaging translations. Imagine you translate pathauto. It has many releases, and we translate it to 40 languages. Should we package all translations into one package per release? What if one of those translations improves? Repackage the whole stuff? Should we package translations per releases (40 packages per release)?

pvasili’s picture

pvasili commented

I think ill have a central Localization server ..
Drupal.org must have only finished translation (work) (XML-RCP, file,... or in other ways).

1) Translators easier to solve any problems in their native language
2) Translations help make people who do not speak English (a teacher, linguist, ...)
3) The issues of assistance and solved quickly (especially in his native language)

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

FYI: Existing issue in the d.org webmasters queue: #341865: Translation server for projects for the redesign.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Active » Fixed

What happened recently is that (2) was solved with http://drupal.org/project/bakery which is not OpenID based but instead Drupal specific. (3) is not at all solved yet, but that we will be able to solve on the go. Also, only some of (1) was solved, but Gerhard was pushy to get this running, since that might eventually help people work on (1), so there you go. Localize.drupal.org is now running in an invitation based beta mode.

So even though subissues are not solved here, they are all open separately so will be fixed independently.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.