March 2016 - OpenStack-I18n - lists.openstack.org

To language team coordinators: get ready for Mitaka translation
by Ying Chun Guo 28 Sep '16

28 Sep '16

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 [2] https://wiki.openstack.org/wiki/I18nTeam/team [3] https://wiki.openstack.org/wiki/IRC

9 27

stable/liberty version fo Zanata networking-guide
by Akihiro Motoki 03 Apr '16

03 Apr '16

Hi, networking-guide in openstack-manuals is now versioned. Can we have a stable-liberty version for networking-guide on Zanata? Akihiro

4 4

Strange projects on translate.openstack.org
by Andreas Jaeger 01 Apr '16

01 Apr '16

Hi, does anybody know what these are? https://translate.openstack.org/project/view/swift-italian/ https://translate.openstack.org/project/view/tempest https://translate.openstack.org/project/view/test-json-md IMHO we should not add new projects that are manually translated - instead let's integrate them in the usual toolchain. Also, why do these have some projects separate maintainers? We don't need them IMHO at all. I propose to delete them. Going forward, I suggest that any new projects outside of the usual process get discussed on the openstack-i18n mailing list, so that we know what's going on. Can we also document the reason for them somewhere? Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

5 6

Starting translations for libraries (like djnago-openstack-auth) earlier in Newton?
by Akihiro Motoki 31 Mar '16

31 Mar '16

During the Mitaka RC phase, I released django-openstack-auth only for translation. At that time, I was asked from Doug Hellmann, the release manamgement PTL, whether the i18n team can start translations for libraries earlier, i.e., sooner before the freeze date of libraries. [1] Can we do this in Newton or later? If we accept this, please keep it in mind when planning translation schedule and make sure to announce it to the team. I am just sharing information and won't lead this discussion. I have been coordinating this kind of things for long and now am tired to do it. I hope someone else takes the role. Background: django-openstack-auth is a library used by horizon. In the OpenStack release process, all libraries are frozen when the milestone-3 is cut. [1] http://lists.openstack.org/pipermail/openstack-dev/2016-March/090112.html

2 1

Re: [OpenStack-I18n] Criteria of Horizon language list forMitakarelease
by Kato, Tomoyuki 30 Mar '16

30 Mar '16

> As of now, 15 languages satisfy the criteria. > https://translate.openstack.org/version-group/view/mitaka-translation/ > projects/horizon/stable-mitaka > and > http://git.openstack.org/cgit/openstack/horizon/tree/openstack_dashboa > rd/settings.py?h=stable/mitaka#n198 > match, > so there is no need to update. Thanks, Akihiro. And, congrats, 15 languages coordinators! Mitaka is really coming soon. KATO Tomoyuki > This is the final check from my side. > If your language satisfies this criteria after this mail, feel free to > propose a patch to update the language list in Horizon by yourself. > > I believe various projects will release RC including translations this week. > > Akihiro

1 0

Re: [Openstack-i18n] Criteria of Horizon language list forMitakarelease
by Akihiro Motoki 30 Mar '16

30 Mar '16

Hi Doug and all, I needed to spend some time to look for the history. Roughly speaking our history can be broken donw into three categories: [1] Liberty Horizon [2] documentation translation from 2014. [3] up to Kilo Horizon I think following the history clarified what happened. --- [1] Liberty Horizon In Liberty, we migrated the translation platform to Zanata and all imports were done by Jenkins jobs (thanks to Andreas). [2] documentation translation from 2014 In parallel, there was the ongoing efforts to automate documentation translations. The thread is [2] and we discussed the threshold for translation addition (75%) and removal (60%). It is documented very well at https://wiki.openstack.org/wiki/Translations/Infrastructure. [3] up to Kilo Horizon The following are my translation import patch for Horizon up to Kilo: * KIlo : https://github.com/openstack/horizon/commit/56d5683c8c49558ae22200bc01ec87e… (The commit message was wrong not Juno but Kilo :p) * Juno : https://github.com/openstack/horizon/commit/9b0ba951c07af13aa4c386b19876474… * Icehouse : https://github.com/openstack/horizon/commit/a9cf547d20065b2bd49e101364b46cf… * Havana : https://github.com/openstack/horizon/commit/4910222356fbd2aeb0dab1b3cebe003… All of these commit messages said "Import ~100% completed translaitons". It seems we used almost all are translated. I could not find the meeting log where we discussed this criteria first for Havana or Icehouse. According to [1] it seems we had the criteria of 95% for Juno. --- commit 56d5683c8c49558ae22200bc01ec87ea83144003 Author: Akihiro Motoki <motoki(a)da.jp.nec.com> Date: Thu Apr 23 06:58:49 2015 +0900 Import translations from Transifex for Juno * Import ~100% completed translations (translations available for 12 languages) * Delete incomplete languages * Update language list in openstack_dashboard settings.py --- That's all what I succeeded to gather. Akihiro [1] http://lists.openstack.org/pipermail/openstack-i18n/2014-October/000806.html [2] http://lists.openstack.org/pipermail/openstack-i18n/2014-October/thread.htm… 2016-03-22 22:32 GMT+09:00 Douglas Fish <drfish(a)us.ibm.com>: > Akihiro, > > I've been trying to find where we documented the 90% cutoff used by Horizon > in past releases. I can't find it (and I'm afraid I'm the one who documented > it). Were you able to find that reference? > > I think it's reasonable to manage the Horizon language list to match the > same set of languages for which we have PO files included in the project. > The 66% cutoff would apply in both cases then. It should be easy for a > consumer or distro to provide a shorter list than what we've defaulted by > changing the value of the LANGUAGES setting in local_settings.py or a > local_settings.d file. > > Doug Fish > > > > "Ying Chun Guo" <guoyingc(a)cn.ibm.com> wrote on 03/22/2016 05:56:45 AM: > >> From: "Ying Chun Guo" <guoyingc(a)cn.ibm.com> >> To: Akihiro Motoki <amotoki(a)gmail.com> >> Cc: "openstack-i18n(a)lists.openstack.org" >> <openstack-i18n(a)lists.openstack.org> >> Date: 03/22/2016 05:59 AM >> Subject: Re: [Openstack-i18n] Criteria of Horizon language list for >> Mitakarelease >> >> Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/22/2016 06:43:33 PM: >> >> > From: Akihiro Motoki <amotoki(a)gmail.com> >> > To: Ying Chun Guo/China/IBM@IBMCN >> > Cc: "openstack-i18n(a)lists.openstack.org" >> <openstack-i18n(a)lists.openstack.org> >> > Date: 03/22/2016 06:45 PM >> > Subject: Re: [Openstack-i18n] Criteria of Horizon language list for > >> > Mitakarelease >> > >> > 2016-03-22 18:00 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/22/2016 02:27:21 AM: >> > > >> > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> > >> To: "openstack-i18n(a)lists.openstack.org" >> > > <Openstack-i18n(a)lists.openstack.org> >> > >> Date: 03/22/2016 02:29 AM >> > >> Subject: [Openstack-i18n] Criteria of Horizon language list for >> Mitaka >> > > release >> > >> >> > >> Hi i18n team, >> > >> >> > >> As Horizon liaison, I would like to ask you all about the criteria of >> > >> Horizon language list for Mitaka release. >> > >> >> > >> The same topic was discussed several releases ago and the consensus >> at >> > >> that time were: >> > >> * remove all translations with less than 90% progress >> > >> * update the language list accordingly. >> > >> >> > >> Translations were imported manually at that time and the situation >> may >> > >> be changed now. >> > >> I don't have an opinion and will just follow the i18n project >> decision. >> > >> If no response or well-defined criteria, I will just keep the current >> > >> language list [1]. >> > > >> > > Thank you for taking care of that, Akihiro. >> > > I don't see any requests to change the language list. >> > > >> > >> >> > >> The following is just information: >> > >> We have four PO files (django/djangojs for horizon and >> > > openstack_dashboard). >> > >> The current translation import policy for each PO file is >> documentedhere >> > > [2]. >> > >> Each PO file is imported once the translation percentage becomes over >> > > 75% >> > >> and it will be removed when the translation percentage becomes less >> than >> > > 20%. >> > >> What is our criteria? >> > > >> > > My opinion is to follow the previous guidelines. >> > >> > Do you mean we should remove <90% translations and update the lang >> > list accordingly? >> > >> > I made a quick survey. The result is not so happy, but I will just >> > follow the team decision. >> > >> > We have four PO files per language for horizon. >> > My understanding is 90% means 90% translations for all these PO files. >> > Unfortunately, as of today, only four languages satisfy this criteria >> > (90%): de, fr, ja, ko >> > If we change the criteria to 66%, we will have three more languages: >> > pt-br, ru, zh-cn. >> > >> > It is too sad statistics. openstack_dashboard/djangojs is the >> > bottleneck of the progress. >> > >> > On the other hand, the current language list contains 15 translated >> languages: >> > cs, de, en-gb, en-au, es, fr, it, ja, ko, pl, pt-br, ru, tr, zh-cn, >> zh-tw. >> > >> >> No, I didn't mean to remove <90% translations. >> Did we do that before ? >> I thought the criteria was 66%. >> >> I just realized the difference situation we met in this release. >> We have included plugin projects. >> Before mitaka, we only focus on Horizon translation. >> If we only take a look at the completion rate of Horizon[1], I think most >> active translation team have achieved >66%. So it means, we don't need to >> remove any languages from the list. >> If we consider the overall completion rate of plugin projects together >> with Horizon projects, some languages are less than 66%. >> My suggestion is to only consider the progress of Horizon project. >> 90% is too strict, I think. 66% is better. >> >> > Akihiro >> > >> > > >> > > >> > >> >> > >> In future releases, I think we should automate this as a part of >> > >> translation import jobs. >> > >> I will reduce the work of horizon liaison. >> > >> >> > > >> > > I agree. >> > > >> > > >> > >> Akihiro >> > >> >> > >> [1] https://github.com/openstack/horizon/blob/master/ >> > >> openstack_dashboard/settings.py#L198-L215 >> > >> [2] https://wiki.openstack.org/wiki/Translations/ >> > >> Infrastructure#Translation_percentage_changes >> > >> >> > >> _______________________________________________ >> > >> Openstack-i18n mailing list >> > >> Openstack-i18n(a)lists.openstack.org >> > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > >> >> > > >> > > >> > >> >> >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >

4 5

unable to login to Zanata
by Nikita Burtsev 29 Mar '16

29 Mar '16

Hello, When I try to login to production Zanata I get forwarded to openstackID first then to Zanata profile creation page. This page tells me that my username/email are already in use. I've never used production Zanata before but I did use 'dev' version. I guess my profile was migrated from dev but never associated with openstackID (or something like that) Could someone help me out with this please? Thank you. -- BR Nikita

7 15

Setting up stable-mitaka in Zanata
by Andreas Jaeger 25 Mar '16

25 Mar '16

Team, the release manager have setup stable/mitaka for these projects: https://review.openstack.org/#/q/topic:create-mitaka We should create stable-mitaka again in zanata and freeze master. Daisy, will you do this? I'm taking care of the infra side now, change is https://translate.openstack.org/ Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 4

designate-dashboard missing template strings
by Akihiro Motoki 24 Mar '16

24 Mar '16

Hi, Strings in templates of designate-dashboard are not extracted now. https://bugs.launchpad.net/designate/+bug/1561203 and I proposed a fix at https://review.openstack.org/#/c/296807/ Questions for the team is whether we should have this in mitaka? We are in the hard string freeze after RC1 phase. This change violates the string freeze. However this change only add new strings and allows translators to translate strings which cannot be translated now. This add 18 fuzzy translations, 8 untranslated messages. I think it is acceptable from i18n view. Thought? Akihiro

2 1

Do you need a temporary translation check site?
by Akihiro Motoki 24 Mar '16

24 Mar '16

Unfortunately the official translation check site is not announced yet. If you need an alternative one, try the following. Horizon is now available at http://157.7.133.23:13580/dashboard The default users are: admin and demo The password: UW3D9n6TqdGn Note that it is temporary and I am using this site for development and testing. The enabled panel may sometimes be changed. Do not ask me :)

2 2