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 26 Mar '16

26 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

[release][horizon][i18n] can we release django-openstack-auth of stable/mitaka for translations
by Akihiro Motoki 24 Mar '16

24 Mar '16

Hi release management team, Can we have a new release of django-openstack-auth from stable/mitaka branch for translations? What is happening? django-openstack-auth is a library project consumed by Horizon. The (soft) string freeze happens when the milestone-3 is cut. The milestone-3 is also the dependency freeze. This is a dilemma between dependency freeze and translation start, and there is no chance to import translations of django-openstack-auth for Mitaka. There are several updates of translations after 2.2.0 (mitaka) release [1]. As the i18n team, we would like to have a released version of django-openstack-auth with up-to-date translations. Which version? The current version of django-openstack-auth for Mitaka is 2.2.0. What version number is recommended, 2.2.1 or 2.3.0? When? Hopefully a new version is released soon around Mitaka is shipped. The current translation deadline is set to Mar 28 (the beginning of the release week). In my understanding we avoid releasing a new version of library before the Mitaka release. Distributors can choose which version is included in their distribution. Any suggestions would be appreciated. Thanks, Akihiro [1] https://review.openstack.org/#/q/topic:zanata/translations+project:openstac…

2 2

Re: [Openstack-i18n] Zanata Group for Mitaka dashboard translations
by Akihiro Motoki 23 Mar '16

23 Mar '16

Thanks Daisy! I am using this to check the progress of translations per language. The link like https://translate.openstack.org/version-group/view/mitaka-translation/langu… helps me. Akihiro 2016-03-18 16:04 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > It has been corrected, Akihiro. > Thank you for pointing out. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/18/2016 02:44:39 PM: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: "openstack-i18n(a)lists.openstack.org" > <Openstack-i18n(a)lists.openstack.org> >> Date: 03/18/2016 02:47 PM >> Subject: [Openstack-i18n] Zanata Group for Mitaka dashboard translations >> >> Hi Zanata admin, >> >> I noticed Zanata group "Mitaka dashboard translations" has strange > entries. >> > https://translate.openstack.org/version-group/view/mitaka-translation/proje… > >> >> - two versions for django_openstack_auth : master and stable-mitaka >> - read-only version for horizon : master-old-keepforstatistics >> >> Could you correct these versions to the appropriate ones? >> >> Thanks, >> Akihiro >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > >

2 3

Re: [Openstack-i18n] Criteria of Horizon language list for Mitakarelease
by Akihiro Motoki 22 Mar '16

22 Mar '16

2016-03-22 19:56 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > 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 re-read the old logs. My memory is not correct. We first import ~100% translated languages, and then relaxed the criteria to 90~95%. It seems I thought this is the criteria. After that, we discussed and agreed the criteria of >75% for addition and <66% for deleteion for each PO file. That's the history. > I thought the criteria was 66%. I got it. I just quoted the i18n team consensus several release ago and I didn't thought it has been updated as wrote above. Thanks. > 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. Totally agree. I just would like to clarify the criteria. Is it okay that I just update the language list with >66% progress? Everyone can see the progress at https://translate.openstack.org/iteration/view/horizon/stable-mitaka/langua… I will decide the progress based on this. Thanks, Akihiro > >> 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 >> >> >> > >> > >> > >

3 2

Re: [Openstack-i18n] Setting up stable-mitaka in Zanata
by Andreas Jaeger 22 Mar '16

22 Mar '16

On 2016-03-22 11:39, Ying Chun Guo wrote: > Hi, Andreas > > Can you kindly add job to support stable-mitaka for project > designate-dashboard ? We just found we missed it in the Mitaka translation > plan. Luckily, it has only a small po file with 68 words. We still have > time to add it back to the translation plan. Sorry for the trouble. Please > help. I'll setup the jobs. Do you add it to zanata? 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

2 2

Re: [Openstack-i18n] Criteria of Horizon language list for Mitakarelease
by Akihiro Motoki 22 Mar '16

22 Mar '16

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. 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 >> > >

5 4

Re: [Openstack-i18n] why is designate-dashboard excluded from the prioritized translation list?
by Akihiro Motoki 22 Mar '16

22 Mar '16

Thanks for your quick support! 2016-03-22 19:36 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Thank you, Kato. > stable-mitaka for designate-dashboard is created. The translation plan in > the front page is updated. Dashboard group is updated too. > > Best regards > Ying Chun Guo (Daisy) > > > "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> wrote on 03/22/2016 > 06:23:52 PM: > >> From: "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> >> To: Ying Chun Guo/China/IBM@IBMCN, Akihiro Motoki <amotoki(a)gmail.com> >> Cc: "openstack-i18n(a)lists.openstack.org" > <Openstack-i18n(a)lists.openstack.org> >> Date: 03/22/2016 06:25 PM >> Subject: RE: [Openstack-i18n] why is designate-dashboard excluded >> from the prioritized translation list? >> >> > hmm. >> > I don't know neither. >> > Maybe nobody proposed to add designate-dashboard in I18n mailing list. >> > And I don't think I see its liaison when I proposed plugin projects in > Feb >> > 29. >> > For whatever reasons, the reality is that we missed it in the plan. >> > >> > There are two possible solutions. >> > #1 we add it back to the plan. It has only 1 file with 68 words, > really a >> > very small workload. >> >> my +1 for #1 >> >> KATO Tomoyuki >> >> > #2 we told designate team that we missed it and we will include it in > next >> > release. >> > >> > I prefer the first one. >> > If you agree, I can make stable-mitaka version and we can ask Andreas > to >> > add the corresponding job. >> > >> > Best regards >> > Ying Chun Guo (Daisy) >> > >> > >> > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/22/2016 02:59:53 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 03:02 AM >> > > Subject: [Openstack-i18n] why is designate-dashboard excluded from >> > > the prioritized translation list? >> > > >> > > Does anyone describe why designate-dashboard is not listed in the >> > > prioritized list? >> > > I see designate has assigned a cross project liaison for i18n at > least >> > Mar 4 >> > > (according to the wiki history) and the project seem to be taking > care >> > > of translations well. >> > > >> > > I have no answer for >> > > >> > > http://lists.openstack.org/pipermail/openstack-dev/2016-March/090022.html >> > > ? >> > > Can we describe a reasonable reason for them? >> > > Daisy, could you follow up the mailing thread? >> > > >> > > stable-mitaka is not setup for designate-dashboard. >> > > As far as I know, they have setup translation support in the early >> > stage. >> > > >> > > If I remember correctly, we include murano-dashboard and magnum-ui >> > > because they responded in the -dev list. I am not sure we checked > the >> > > wiki at that time, >> > > and the nomination period is enough. >> > > >> > > Akihiro >> > > >> > > _______________________________________________ >> > > 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 >> > >

1 0

Re: [Openstack-i18n] Setting up stable-mitaka in Zanata
by Andreas Jaeger 22 Mar '16

22 Mar '16

I just added trove-dashboard for mitaka, 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 5

why is designate-dashboard excluded from the prioritized translation list?
by Akihiro Motoki 22 Mar '16

22 Mar '16

Does anyone describe why designate-dashboard is not listed in the prioritized list? I see designate has assigned a cross project liaison for i18n at least Mar 4 (according to the wiki history) and the project seem to be taking care of translations well. I have no answer for http://lists.openstack.org/pipermail/openstack-dev/2016-March/090022.html ? Can we describe a reasonable reason for them? Daisy, could you follow up the mailing thread? stable-mitaka is not setup for designate-dashboard. As far as I know, they have setup translation support in the early stage. If I remember correctly, we include murano-dashboard and magnum-ui because they responded in the -dev list. I am not sure we checked the wiki at that time, and the nomination period is enough. Akihiro

3 3

Re: [Openstack-i18n] why is designate-dashboard excluded from the prioritized translation list?
by Akihiro Motoki 22 Mar '16

22 Mar '16

Hi Daisy, Thanks for your reply to my rude mail forwarding _o_ > #1 we add it back to the plan. It has only 1 file with 68 words, really a > very small workload. My vote is #1. The following is just to record my memory. I think it was just a bad timing. We can improve the process in the future releases. * designate-dashboard is a candidate of the list, but we didn't see i18n liaison when the team meeting was held on Mar 3. This is the only reason. * In the mail to ask i18n liaison, we just asked to input his/her name to CPL wiki page if you are interested in i18n liaison, but we checked mail response only. * We decided the priority list just three days after the mail of i18n liaison request. Most teams are driven by weekly basis (IRC meeting or something), so three days is too short. Akihiro 2016-03-22 19:16 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > hmm. > I don't know neither. > Maybe nobody proposed to add designate-dashboard in I18n mailing list. > And I don't think I see its liaison when I proposed plugin projects in Feb > 29. > For whatever reasons, the reality is that we missed it in the plan. > > There are two possible solutions. > #1 we add it back to the plan. It has only 1 file with 68 words, really a > very small workload. > #2 we told designate team that we missed it and we will include it in next > release. > > I prefer the first one. > If you agree, I can make stable-mitaka version and we can ask Andreas to > add the corresponding job. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/22/2016 02:59:53 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 03:02 AM >> Subject: [Openstack-i18n] why is designate-dashboard excluded from >> the prioritized translation list? >> >> Does anyone describe why designate-dashboard is not listed in the >> prioritized list? >> I see designate has assigned a cross project liaison for i18n at least > Mar 4 >> (according to the wiki history) and the project seem to be taking care >> of translations well. >> >> I have no answer for >> > http://lists.openstack.org/pipermail/openstack-dev/2016-March/090022.html >> ? >> Can we describe a reasonable reason for them? >> Daisy, could you follow up the mailing thread? >> >> stable-mitaka is not setup for designate-dashboard. >> As far as I know, they have setup translation support in the early > stage. >> >> If I remember correctly, we include murano-dashboard and magnum-ui >> because they responded in the -dev list. I am not sure we checked the >> wiki at that time, >> and the nomination period is enough. >> >> Akihiro >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > >

1 0

Re: [Openstack-i18n] Will translation cleanup happen for Mitaka?
by Akihiro Motoki 22 Mar '16

22 Mar '16

Hi Daisy, 2016-03-22 19:01 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Hi, Akihiro > > I see [1] says the clean up patch will remove translations less than 66% ( > infra jobs will only delete translation files less than 20% ). > I remember [1] was an agreement made I18n team before. I was not aware of this agreement. Thanks. > I don't have strong opinion whether to clean up translations or not. > I respect any decisions made by you and Horizon team. I am really surprised. I have never been involved in the decision of translation cleanup. I don't know any decision around this by the Horizon team. Horizon team are always following the I18n team decision about i18n related topic. > If you are going to propose a clean up patch, I will suggest to follow the > same criteria in [1]. It is not a decision of Horizon team, so I am not going to do this. This is the reason I asked this. Thanks, Akihiro > > Best regards > Ying Chun Guo (Daisy) > > [1] > https://wiki.openstack.org/wiki/Translations/Infrastructure#Release_handling > > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/22/2016 01:11:08 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 01:13 AM >> Subject: [Openstack-i18n] Will translation cleanup happen for Mitaka? >> >> Hi, >> >> I saw translation cleanup which removed PO files of less translated >> language before Liberty release. >> Will the same thing happen for Mitaka release? >> Is anyone from the i18n project aware of it? >> >> I cannot find good information on this. >> The only information is [1] but it looks a proposal. >> I am not sure where it is discussed and who is the contact. >> >> I am writing another mail as Horizon liaison which asks how to update >> horizon language list >> before the release. If some cleanup happens for Mitaka, I hope the >> language list update happens >> at the same time or follow the same criteria. >> >> [1] https://wiki.openstack.org/wiki/Translations/ >> Infrastructure#Release_handling >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > >

1 0

Will translation cleanup happen for Mitaka?
by Akihiro Motoki 22 Mar '16

22 Mar '16

Hi, I saw translation cleanup which removed PO files of less translated language before Liberty release. Will the same thing happen for Mitaka release? Is anyone from the i18n project aware of it? I cannot find good information on this. The only information is [1] but it looks a proposal. I am not sure where it is discussed and who is the contact. I am writing another mail as Horizon liaison which asks how to update horizon language list before the release. If some cleanup happens for Mitaka, I hope the language list update happens at the same time or follow the same criteria. [1] https://wiki.openstack.org/wiki/Translations/Infrastructure#Release_handling

3 2

Criteria of Horizon language list for Mitaka release
by Akihiro Motoki 22 Mar '16

22 Mar '16

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]. 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 documented here [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? In future releases, I think we should automate this as a part of translation import jobs. I will reduce the work of horizon liaison. Akihiro [1] https://github.com/openstack/horizon/blob/master/openstack_dashboard/settin… [2] https://wiki.openstack.org/wiki/Translations/Infrastructure#Translation_per…

2 1

Translations for release notes in Mitaka? Perhaps NO
by Akihiro Motoki 22 Mar '16

22 Mar '16

The release management team has changed the process of generating releases notes for Mitaka. Release notes are generated from YAML files in individual repos by using reno. My understanding is that we don't have translation support for Mitaka release notes. Is it correct? After checking the meeting minutes, I found Kato has an action item to talk about it with the relmgt team. is there any feedback? Personally I am okay with it. I am always using English release notes :-) I am translating release notes only for reading them carefully and better understanding of the release. Thanks, Akihiro

4 7

Re: [Openstack-i18n] Looking for Translations for Nova Mitaka RC1
by Augustina Ragwitz 22 Mar '16

22 Mar '16

On Fri, Mar 18, 2016 at 12:34 AM, Ying Chun Guo <guoyingc(a)cn.ibm.com> wrote: > Ragwitz, > > I hope your team can cut RC2 on March 28, leaving a whole week for > translators to complete their work. > Please help to talk to nova team. > Thank you. > > Best regards > Ying Chun Guo (Daisy) > > > "Ragwitz, Augustina" <augustina.ragwitz(a)hpe.com> wrote on 03/18/2016 > 12:12:53 AM: > > > From: "Ragwitz, Augustina" <augustina.ragwitz(a)hpe.com> > > To: Openstack-i18n Openstack-i18n <openstack-i18n(a)lists.openstack.org> > > Date: 03/18/2016 12:14 AM > > Subject: Re: [Openstack-i18n] Looking for Translations for Nova Mitaka > RC1 > > > > > According the agreement about StringFreeze[1], cutting RC1 means > hard > > > freeze and translators can get extra 10 days to complete their > > > translations after hard freeze. So I don't think we can finish the > job > > > next week. The translation work is planned to be finished at > > the early of > > > the week after next. > > > > > > Can you figure out when is the last day to merge nova translations > ? > > > > I will follow up with the Nova team to find out our projected > > timeline for RC2. We have our team meeting today so I'll bring it up > > then. I assumed it would be end of next week based on the date in > > Launchpad for the OpenStack project [1], but this might not be accurate. > > > > [1] https://launchpad.net/openstack/+milestone/mitaka-rc2 > The Nova team will need to cut RC2 this week because we have some critical issues that need to be addressed before translations will be available. We will include whatever translations are available at that time. We will then cut RC3 the following week per your timeline to ensure all translations are included in the final release. If there is going to be any change to this, then I will follow up and let you all know. We recognize the value of the translations your team provides and will make sure they make it into the final release. --- Augustina Ragwitz Sr Systems Software Engineer, HPE Cloud Hewlett Packard Enterprise --- irc: auggy

1 0

My less activity in Newton (as i18n project) and some suggestions to the team
by Akihiro Motoki 22 Mar '16

22 Mar '16

Hi team, I am writing this mail to announce my less activity in Newton cycle (as I18n project) and will focus on translations and reviews of my focused and interested areas (i.e, dashboards and documentations). Translation is just my spare-time activity, so I need to choose how to spend my time. I have been involved in OpenStack translation activity before the I18n team is organized. The community is growing continuously and it is time for me to focus on translation itself again. I have made various activities including the following for the i18n team so far, but most of them are now over or can be shared by the community. * Coordinate the translation import timing for Horizon (now importing translation are done automatically) * Coordinate the final release timing of dashboards (now we have cross-project liaisons. it is no longer a personal role.) * Coordinate translation imports for stable updates (now imported automatically) * Provide translation check site for dashboards (we will have the official translation check site and I intentionally decided not to provide such site to encourage the effort in the i18n project.) * Continuously improve the upstream of Horizon and documentations for translation friendly. * Setup translation setup for horizon plugins in Mitaka (Completed) * Write various documentations around translation and I18n activities Finally, I would like to share several thoughts and suggestions for the i18n project before stepping down from the main activity of the i18n team. I hope the community is healthy enough and see much progress in Newton. I will help your efforts from individual project side. * Glossary management: It needs to be improved along with a new version of Zanata. The basic process itself on how to update glossary is not documented. In addition to this, contextual information support would be great. * Release notes translation * Documentation around i18n are spread: * We have i18n related documentations in several places. The infra manuals, horizon devref docs, i18n docs, and openstack wiki. We should have better guidance for readers considering their interests. Although appropriate place depends on a content, the i18n team should lead the effort. * Need more documentations for various processes. For example, how we decide prioritized projects for translations should be documented. In Mitaka translations, some dashboard plugin whose member responded in the ML is prioriptized and some plugin who added an entry to the cross project liaison wiki page are not. This is unfair. Another example is the criteria of the language list of Horizon translations. Maintaining the translation check site is another one. * Discussion process: I previously proposed several questions or improvements via MLs or gerrit. In many times, hey let's discuss in team meetings and that's all. No feedback or continued discussion on the original place where discussions happened. This is the point I feel frustrated and one of reason I am leaving. I understand IRC meeting is important, but that's not all. I am not a full-timer for translations and it leads most meeting times do not work. Translations are supported by not small number of volunteers, so I believe more async communications like ML or gerrit should be encouraged. * Better translation quality with technical knowledge: * Previously we try to increase the number of translators to encourage transltaions. I think it is now time to improve the quality of translations for languages translated well. To improve the translation quality, understanding OpenStack projects is inevitable. It is not enough to see strings in Zanata. * We need to explore a way how to improve the quality. In addition to involving technical contributors in translation reviews, I believe pure translators understand the basics of OpenStack projects and their concepts. As I mentioend in a recent IRC meeting (which I could luckily job), translation and reviews of documentations are one of ways to understand OpenStack projects. * For example, in Japanese translations, I played a role of technical reviewers so far, but I am not scalable, so I cannot play this role and have no more time to review server side projects which I am not interested in translations for. I believe other language teams have similar problems. Thanks for your all help so far. Note that I will continue my role as i18n liaison of horizon and neutron. I also continue to be a translator and a reviewer. Best Regards, Akihiro

1 0