[OpenStack-I18n] To language team coordinators: Let's speed up for Newton translation
Akihiro Motoki
amotoki at gmail.com
Mon Sep 26 06:24:16 UTC 2016
2016-09-26 15:21 GMT+09:00 Akihiro Motoki <amotoki at gmail.com>:
>
>
> 2016-09-26 13:05 GMT+09:00 Ian Y. Choi <ianyrchoi at gmail.com>:
>
>> Hello Akihiro-san,
>>
>> Thank you for this remainder :)
>>
>> I have one question.
>> For Mitaka release, we set the criteria for Horizon translation as 66% [1]
>>
>> For Newton, currently the following 14 languages satisfy the criteria
>> - cs, de, en-gb, en-au, es, fr, it, ja, ko, pt-br, ru, zh-cn, zh-tw + id
>>
>> Note that Indonesian was not included in Mitaka, but now the translation
>> progress is very good (76.12% for Horizon).
>>
>> Unfortunately, the two following languages are near the cutting edges
>> - pl-PL: 65.36%
>> - tr-TR: 63.19%
>>
>> I have checked the translation ratios for those two languages one week
>> ago, and now, the translation ratios are unfortunately the same.
>>
>> Should we remove those two languages in Horizon for Newton?
>>
>> I would like to discuss this issue with i18n members.
>> IMO since my kind announcement for Horizon translation was a little bit
>> late,
>> I think just including Indonesian and so total 16 languages for Newton
>> would be nice.
>>
>> And Akihiro-san, what would be the final due to include or exclude
>> language lists in Horizon?
>>
>
> AFAIK the horizon team has not decided the exact date for the final RC,
> but my guess is around the middle of the week.
> If there is a special reason, the horizon team can prepare RC3.
> I can propose the update of the language list appropriately and coordinate
> the date.
>
> My vote on the language list is to add languages with good progress
> aggresively
> and not to hurry to remove languages with non-good progress from the
> existing list.
> Thus, my suggestion is only to add Indonesian and remove nothing.
> How about apply the similar rule for translation import?
> For translation import, 75% for inclusion and 60% for exclusion.
>
The above numbers might be wrong.
>
>
> Akihiro
>
>
>>
>>
>> [1] http://lists.openstack.org/pipermail/openstack-i18n/2016-Mar
>> ch/002012.html
>>
>> With many thanks,
>>
>> /Ian
>>
>>
>> Akihiro Motoki wrote on 9/26/2016 12:53 PM:
>>
>> One thing to note on the final date.
>>
>> The week of Sep 26 (- Oct 1) is the final release candidate week.
>> The previous mail said Oct 1 is the deadline, but most OpenStack projects
>> will release the next RC in the middle of the week.
>>
>> I would suggest to finish translations by Sep 27 0600UTC if possible.
>> 0600UTC is the time of the daily translation import.
>>
>> Akihiro
>>
>> 2016-09-19 13:26 GMT+09:00 Ian Y. Choi <ianyrchoi at gmail.com>:
>>
>> >
>>
>> > Dear language coordinators and also translators,
>> >
>> > Although I think this telling is so late compared to Mitaka translation,
>> > I would like to kindly remind that we need to speed up for Newton
>> translation,
>> > since the cut-off date for final RCs (when translation results will be
>> finally imported) is *October 1st*.
>> >
>> > According to the dashboard on translate.openstack.org, our targeted
>> priorities are as the followings:
>> >
>> > - Dashboard - Horizon (High)
>> > - Dashboard Authorization Page (High)
>> > - Trove Dashboard (Medium)
>> > - Sahara Dashboard (Medium)
>> > - Murano Dashboard (Low)
>> > - Magnum UI (Low)
>> > - Designate Dashboard (Low)
>> >
>> > Note that recently, stable-newton version was created in translate.o.o.
>> > Please translate to *stable-newton* branch, not master branch
>> (exception: releasenotes should be translated on master branch).
>> >
>> > I tried to check whether there will be IBM translations or not,
>> > so I sent an e-mail to Douglas Fish (drfish at us.ibm.com), but
>> unfortunately, his e-mail address is not active.
>> >
>> > Since we do not have enough time, let's first focus on Horizon for
>> translation, and then translate Horizon related projects.
>> > (Surely, translation on server projects are also welcome!)
>> > Hope that we will have as much translation as we did previously,
>> > and I really hope that we will be able to keep on translation effort
>> for Ocata and further releases as one team.
>> >
>> > If you have any questions, feel free to send an e-mail to me or call
>> "ianychoi" nickname on Freenode #openstack-i18n channel.
>> > Sometimes my response can be slow, but I will respond :)
>> > Thank you very much.
>> >
>> >
>> > With many thanks,
>> >
>> > /Ian
>> >
>> > Ying Chun Guo wrote on 2/25/2016 5:53 PM:
>>
>> >>
>>
>> >>
>> >> Dear coordinators,
>> >>
>> >> Mitaka translation will be started at the beginning of March,
>> >> and probably ended in the week of March 28.
>> >> We need to get ourselves ready for Mitaka translation from now on.
>> >>
>> >> Because of the join of IBM professional translators, we will be able to
>> >> cover more projects in our translation plan of this release.
>> >> Generally, the jobs of existing community translators will not be
>> affected,
>> >> focus on Horizon, same as before.
>> >> IBM translators will focus on "other" projects.
>> >>
>> >> Before Mitaka translation starts, there are several things you can do:
>> >>
>> >> 1. Update glossary.
>> >>
>> >> If you don't have glossary translations in i18n repo[1], or you want
>> to update
>> >> glossary translations, you can send a patch with your translations or
>> your updates
>> >> to i18n repo directly.
>> >>
>> >> 2. Document your local team communication method in the team wiki
>> page[2].
>> >>
>> >> While Mitaka translation starts, it's good to open your local
>> communication channel to
>> >> all of your language translators. Good communication is quite
>> important for people from
>> >> different places to work well together.
>> >>
>> >> 3. Join IRC channel[3] #openstack-i18n with your zanata ID
>> >>
>> >> As a coordinator, you have the responsibility to coordinate your
>> language translations.
>> >> A good practise is to show up in IRC and have your people to get you
>> easily when they have troubles.
>> >>
>> >> If you have any questions, talk to me.
>> >> My IRC ID is "Daisy" in the channel of #openstack-i18n.
>> >> Thank you.
>> >>
>> >> Best regards
>> >> Ying Chun Guo (Daisy)
>> >>
>> >> [1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n/locale <
>> https://wiki.openstack.org/wiki/IRC>
>> >> [2] https://wiki.openstack.org/wiki/I18nTeam/team
>> >> [3] https://wiki.openstack.org/wiki/IRC
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> Openstack-i18n mailing list
>> >> Openstack-i18n at lists.openstack.org
>> <Openstack-i18n at lists.openstack.org>
>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n>
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > OpenStack-I18n mailing list
>> > OpenStack-I18n at lists.openstack.org <OpenStack-I18n at lists.openstack.org>
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-i18n/attachments/20160926/e0b8d2fd/attachment.html>
More information about the OpenStack-I18n
mailing list