Add Galician (gl_ES) language to l.d.o

What's your relation to http://drupal.org/project/gl ?

http://drupal.org/project/gl is not active in traslations. Galician translators was working in a galician public source forge called "mancomun". This is the page to the project repository: https://forxa.mancomun.org/plugins/scmsvn/viewcvs.php/?root=drupal6-gal

You can see that this translation covers about 90% of Drupal core, and the translation of contrib modules was in progress.

Migrate this translation from "mancomun" to drupal localization is important because the new governement of Galiza wants to close "mancomun".

Fran Dieguez from http://drupal.org/project/gl is working in translation of mancomun

Sergio Caridad is set as maintainer to the existing http://drupal.org/project/gl Contacted him to reply here.

Hey all,
I wasn't aware of the new localizer server on d.o. Thanks Gábor for pointing this out to me.

The current drupal 6 translation may be found in this issue: http://drupal.org/node/291954 but after a conversation with Fran Dieguez, he told me he was going to rewrite it from scratch, and send it to me. I was waiting for that new translation to create the d6 branch in http://drupal.org/project/gl

So, right now, I understand that the latest code is the one in the forxa.mancomun repository, is that right? I can import it from there and commit the new 6.x branch with it to d.o.

About the l.d.o. project, I'll apply for an account so we can set up a team there. It's great to have a team working in forxa.mancomun, but we should keep the project updated here in d.o.

btw, is the code imported automatically from the d.o. cvs to l.d.o?

EDIT: This is the repo for the translation Fran was working on: http://github.com/frandieguez/Drupal-6-galician-translation
If any of you guys can tell me which one of these (or any other) to commit, I'll create the d6 branch.

@scb: Yes, all project releases are parsed from drupal.org on localize.drupal.org, so newly released code is automatically available.

@scb: if you prefer to work elsewhere on the translation, we are not going to set up a localize.drupal.org group. You are free to use macomun, but then we are not going to replicate the interface here. If we'd replicate it, people would have no idea where to contribute, whether their contributions are actually useful. So it's your decision.

Looks like requestor lost interest. Marking this postponed (vs closed) in the interest of someone else finding it later, and continuing our discussion.

I've just created a 6.x beta version with the contents from the forxa.mancomun repository. In order to keep the translation centralized, and available to all drupal users, we have to work with the drupal.org cvs repo, instead of working in external repositories. This way the translation will get updated in l.d.o. and will be available to everyone.

So, anyone who is working on (or wants to contribute to) the galician translation, please contact me for syncing efforts. Thanks.

@Gábor: Of course my interest is to keep the translation in l.d.o. If i get it right, once l.d.o. parses the release in drupal's cvs, it will show up in l.d.o, and everyone will be able to work there. After some time, I (or someone else in the translation team) should commit the latest translation to drupal.org cvs, so it's available for download. Is that right? I've searched for more info on this, but only found the http://localize.drupal.org/faq (which you might want to link from the main page, btw) so I dont know exactly how to proceed now... Is there somewhere else any documentation on this process? (I know it must be a pain to answer the same questions again and again...)
Thanks again for your time!

@scb: I'm afraid you are not getting the flow of the process on drupal.org. Localize.drupal.org is intended to be *the* source of the translation. Syncing between CVS back and forth is currently done on a case by case basis and we are working to eliminate the CVS side altogether. That you committed files to CVS will not open a group on localize.drupal.org or import those files either.

@Gábor: Well, then I'm confused... because you told me they did...

#5 (...) btw, is the code imported automatically from the d.o. cvs to l.d.o? (...)
#6 @scb: Yes, all project releases are parsed from drupal.org on localize.drupal.org, so newly released code is automatically available.

Well, anyway, I understand then that the source is going to be localize.drupal.org. Could you direct me on how to proceed now in order to import the contents to l.d.o (or point me to some docs), please? Thanks :)

@scb: Yes, module, theme and install profile projects are parsed and imported. Translation projects are not, because localize.drupal.org assumes it is the primary source of localization. Translation project hosting and packaging on drupal.org is on the way out.

To set up a team on l.d.o, we need a decision first that you are using l.d.o as the primary platform for translations, not github, not mancomun, etc. You can use other resources to distribute translations, but localize.drupal.org would be the primary source and hosting environment for your language team. Once we have a decision, then I can set up the team and you are expected to import the .po files from existing work to l.d.o. Our import processes work very quickly now, a full Drupal core .po file can be imported in a matter of seconds (in my testing last week at least).

Ok, thanks, Gábor, I'll post here as soon as we have a stable team ready.

So, everyone who wants to be a part of the galician translation team, please contact me asap. Thanks.

Looking forward to your updates.

Hi again Gábor,
Ok, we're ready! :)
I have a team of 5 people ready to work on l.d.o. and use it as the central repo for the Galician language, so please set up a team for us there.
Let me know if you need the members' names up front or any other info.

Thanks

Great, this should be fine then.

Great, I've created the team at http://localize.drupal.org/languages/gl and made scb the initial owner / admin.

Please expect that there might be bumps in the service. You are among the beta-tester of this live instance. Thanks for helping out and please report issues as you find them! Your team members can now join and help import existing translations and work on more translations.

Anybody can sign up for being a member of the team and they will be able to submit suggestions right away. The initial admin can change permissions of people signing up, widening their capabilities. See http://localize.drupal.org/node/616 for explanation on how. It is highly suggested to grant both moderation permissions to those who you also designate admins.

Welcome on board!