[Localization] How do we manage translation effort in, > Release, process/roadmap?
gregsmitholpc at gmail.com
Wed Jul 16 09:29:33 EDT 2008
Hi Sayamindu and Localization Leads,
Thanks for following up on this.
I put "string freeze" for translation in the the Release Process at:
I don't know that the exact dates in the process will hold, but its a
start. There are a couple of other comments on translation in the Ice
Please update this page to fit your working assumptions. I included a
couple of questions I had (look for "?"). If you can address those it
will help. You may want to notify these lists if you make changes.
Add links to relevant pages you maintain too.
Let me know if you have any questions or need help with this.
> Date: Wed, 16 Jul 2008 11:13:21 +0530
> From: "Sayamindu Dasgupta" <sayamindu at gmail.com>
> Subject: Re: [Localization] How do we manage translation effort in
> Release, process/roadmap?
> To: greg at laptop.org
> Cc: devel at lists.laptop.org, localization at lists.laptop.org
> <a1314bfe0807152243m33da3c9fp2aa41160b0c2e17f at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
> Hi Greg,
> It looks like the current release schedule for SugarLabs worked out
> pretty fine for us.
> The time frame depends on the number of strings, as well as the number
> of strings which are being changed in a given release cycle. I would
> say a period of 30 days in enough.
> You may also find the schedule at
> http://live.gnome.org/TwoPointTwentythree to be interesting.
> On Fri, Jul 11, 2008 at 10:17 PM, Greg Smith <gregsmitholpc at gmail.com> wrote:
>> Hi Sayamindu,
>> Great work, thanks for taking up the gauntlet on this!
>> One question for you, how much lead time do you need to do the translations?
>> Assuming something like "final test" starts 15 days before the target
>> release date, when do we need to tell the developers to "freeze" all of
>> their strings?
>> Possible dates are 90 days before target release day and 60 days before
>> target release day.
>> Let me know which of those you prefer or if you think a different lead time
>> is warranted.
>> Greg S
>> Sayamindu Dasgupta wrote:
>>> Hello Korakurider,
>>> Thanks for your input. I have put up a basic document at
>>> http://wiki.laptop.org/go/Localization/Workflow Comments and brickbats
>>> are welcome :-).
>>> Regarding you questions - please see inline :-)
>>> On Fri, Jul 4, 2008 at 5:51 PM, Korakurider <korakurider at gmail.com> wrote:
>>>> On Thu, Jul 3, 2008 at 8:38 PM, Greg Smith <gregsmitholpc at gmail.com>
>>>> Now, my turn to ask :-) I don't know who is the right one to ask
>>>> (1) They say SugarLabs is upstream of Sugar software and OLPC is one of
>>>> Then, which POs are still "owned" by OLPC?
>>>> (Packaging/Pootle/Activation Server/OLPC Web site projects are obvious
>>>> For Sugar. will commit from Pootle go to upstream(SugarLab) or
>>>> Which will POT come from ?
>>> My personal opinion (I am open to suggestions) that all translations
>>> should go directly upstream as much as possible. Distro specific
>>> efforts for translations (unless you are talking about distro specific
>>> tools, etc) have been badly bitten in the past.
>>>> (2) SugarLabs have declared string freeze for 8.2. But I am not sure
>>>> specifically which POT/POs are governed by their declaration.
>>>> sugar.po/sugar-base.po/sugar-toolkit.po come to mind.
>>>> And I think other activities in XO-Core (that are also included in
>>>> their software stack as "Demo activities") aren't governed. right?
>>> I think I answered this.
>>> * sugar-base
>>> * sugar-toolkit
>>> * sugar
>>> * chat-activity
>>> * web-activity
>>> * read-activity
>>> * log-activity
>>> * write-activity
>>> * calculate-activity
>>> * terminal-activity
>>> * pippy-activity
>>> * etoys-activity
>>> I will probably try to arrange the projects in our Pootle server at
>>> some point to reflect this.
>>>> (3) OLPC have stopped to bundle activities with base software. Now
>>>> release cycle for them doesn't have to be aligned to XO software from
>>>> OLPC's point of view. But I think It would be still better to try to
>>>> let them aligned for refreshing translations.
>>>> Note that even if the package is enough mature, additional build would
>>>> be needed to pull new translations (new languages for instance).
>>>> Right now it is hard to know when my updated translations for some
>>>> activities will be pulled into the packages :-<
>>> For the sugar stuff - expect a following of the release cycles. For
>>> other stuff - there is really no way to know. However, I would like to
>>> request developers to announce releases a few days in advance in the
>>> localization list, so that translators can prioritize and/or commit
More information about the Devel