How do we manage translation effort in Release process/roadmap?

[Kim Quirk]

This is a good point and I hope Michael will be able to address it. If
there are any questions about how to get translations into pootle or
into a build, please post them so we can get them resolved quickly.

In order to help focus which translations are high priority for this
release, I have listed the languages we are shipping to today and
expect to ship to in the next 4-6 months. They are in size order:

Spanish (Peru, Uruguay, Mexico), 200k
Mongolia, 20k (10k now, 10k by end of year)
French (Rwanda), 10k (5k now, 5k in late fall)
Kreyol (Haiti), 13k (6k now, 7k later)
Amharic (Ethiopia), 5000
Khmer (Cambodia), 1000
Dari (Afghanistan), 3000 (1k now, 2k later)
Thai, 500
Devanagari, 500
Portuguese (Brazil), 200
Arabic, ~500

Receiving laptops in the next 3-6 months:
Oceania, 500
Italy, 600
Turkey, 15k
Senegal (French), 1000
Argentina, Equitorial Guinea, Panama (Spanish)

Not included:
Birmingham, South Carolina, NY (because they are English) and
deployments that got US/Eng keyboards that weren't big enough to
designate the shipping location.

-Kim

On Wed, Jul 2, 2008 at 12:20 AM, Korakurider <korakurider at gmail.com> wrote:
> Hi, all.
> I have read though Greg's release process draft of OLPC
> (http://wiki.laptop.org/go/Release_Process_Home)
> and ReleaseTeam/Roadmap of SugarLabs
> (http://wiki.sugarlabs.org/go/ReleaseTeam/Roadmap).
> But both draft documents haven't explained translation of software
> (including activity) and others.
>
> Until midst of update.1 development, development of activities and
> translation had been aligned to the road map
> of XO software.  it was straightforward; we were notified when window
> for translation of whole project was opened/closed.
>
> Now our collaboration has become complex, because of SugarLabs's split.
> Translators are still working with one unified portal (i.e Pootle),
> but I can't understand how and when each PO will be pulled to build.
> Without those knowledge it would be difficult for translation
> community to manage their schedule.
> Could you please explain about this?
>
> For instance, scheduled build of Terminal activity with pulling newer
> translation was announced recently.
> (http://lists.laptop.org/pipermail/localization/2008-June/001138.html)
>  So we could easily manage the effort.
> But could we expect similar announcement for every activities, or will
> the window for translation of activity aligned to
> development road map of sugarlab or OLPC?
>
> Maybe I missed important thing, though...
>
> Thanks in advance
> /Korakurider
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>