[translations] who would be first to inhibit localize.drupal.org?

[Erik Stielstra]

Ok the Dutch team also joined the server. These were the first steps,  
lets continue...

I like to get a small group working on Dutch translation at l.d.o. We  
can work on existing translations, but will existing translations  
automatically be imported from CVS? And would it conflict if we would  
move some translations over already? When a project translation is  
completed is the (current) workflow to export it and commit it into  
CVS? Is my understanding correctly that translations will, in due  
time, be removed from CVS?

Regards,
Erik Stielstra



On 15 aug 2009, at 19:26, Gábor Hojtsy wrote:

> Hey,
>
> Localize.drupal.org (or localise.drupal.org) is becoming real! :) A
> central setup of the localization server project (which is already
> used by some of the translation teams) is alive on
> localize.drupal.org. It was running in a catch-up / testing mode this
> past weeks to parse up recent Drupal project releases. It currently
>
> - knows about 4886 projects
> - parsed up 5274 (0 in queue and parsing new releases as they are
> available on d.o)
> - 37943 files scanned
> - which results in 145646 strings to translate
>
> That is a huge amount of strings to translate but the UI allows you to
> focus on distinct projects even on distinct releases. Only projects
> with stable releases are parsed, but these 5274 projects include at
> least one stable release from the end of each branch of each project.
>
> The localize.drupal.org site works in a single-sign-on system with
> drupal.org, in which it is also pioneering new functionality on
> drupal.org. That was also tested in recent weeks, and we worked out
> solutions to some bugs, but there might be others lingering still.
> Good news it that you don't need to register on the site to use it,
> but will get redirected to drupal.org for login and get logged in on
> localize.drupal.org too.
>
> A wider announcement is expected later, but before getting a flood on
> us, it would be good to try and migrate a team or two to this platform
> and see how it works. We can either migrate teams from the drupal.org
> CVS based commit workflow or from another localization server. There
> should be no duplication in teams however, so unless there is
> dedication from the team to move to localize.drupal.org, we will not
> migrate a team. Advantages to be here include:
>
> - all releases of projects parsed, backups solved, so no need to
> manage all that within your team
> - central packaging and distribution will be implemented from here
> (not yet implemented), so sites will get translations from here easily
> - single sign-on with drupal.org
> - if you are still using the CVS workflow, this is far superior in  
> many ways
>
> If your team would like to be among the first to migrate, let me know.
>
> Gábor
> _______________________________________________
> translations mailing list
> translations at drupal.org
> http://lists.drupal.org/mailman/listinfo/translations