- OpenStack-I18n - lists.openstack.org

Approval
by Remo Mattei 12 Apr '16

12 Apr '16

hello all, what is the process to approve a new translation? Thanks

2 1

today's horizon import puzzles me...
by Andreas Jaeger 11 Apr '16

11 Apr '16

Could somebody closely review today's horizon translation import, please? I'm surprised by the deletions but couldn't find an error with them either: https://review.openstack.org/#/c/303807/ 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

3 4

Fw: [openstack-announce] OpenStack Mitaka is officially released!
by KATO Tomoyuki 10 Apr '16

10 Apr '16

Hi team, OpenStack Mitaka was officially released. Congratulations! Also, it's time to take over the PTL role from Daisy to me. Again, I appreciate all your work, Daisy. Sincerely. KATO Tomoyuki ----------------------- Original Message ----------------------- Hello OpenStack community, I'm excited to announce the final releases for the components of OpenStack Mitaka, which conclude the 6-month Mitaka development cycle. You will find a complete list of all components, their latest versions, and links to individual project release notes documents listed on the new release site: http://releases.openstack.org/mitaka/ Congratulations to all of the teams who have contributed to this release! I also want to extend a big thank you to AJAeger and jhesketh for their help with build issues today, and to ttx and dims for their help with release work all this cycle and especially over the last couple of weeks. Thank you! Our next production cycle, Newton, has already started. We will meet in Austin April 25-29 at the Newton Design Summit to plan the work for the upcoming cycle. I hope to see you there! Doug

2 1

IRC meeting tomorrow
by Ying Chun Guo 07 Apr '16

07 Apr '16

Hi, team We will have IRC meeting tomorrow at UTC 0600 in #openstack-meeting. The agenda is - Summary of Mitaka translation - New translation priorities - Continued discussion about glossary management If you have more topics, feel free to add. Best regards Ying Chun Guo (Daisy)

3 2

Re: [OpenStack-I18n] Opening master again?
by Andreas Jaeger 04 Apr '16

04 Apr '16

Daisy, KATO, could either of you update the translate.openstack.org main page, please? The mitaka translation period is over according to it, 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 1

Re: [OpenStack-I18n] Opening master again?
by Andreas Jaeger 04 Apr '16

04 Apr '16

On 2016-04-04 03:28, Ying Chun Guo wrote: > Agree to open master again. > We will keep both master and stable open for a period, till string freeze > of next release. OK, I'll open up master now and merge content to master as well, 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

1 0

Opening master again?
by Andreas Jaeger 04 Apr '16

04 Apr '16

The translations have merged for mitaka, latest import was on Wednesday (30th) and for some even on Thursday - so some extra days after official end of the 28th. The last RC has been cut for all projects. I've seen an impressive amount of changes coming in, thanks! Any new translations will go into the first stable release unless a project needs an extra RC and takes in translations as well. Last time we made at this time the master branch writeable again and merged the stable branch translations to master - and left the stable branches open for further submissions. So, time to do this again now? That means translations on both master and stable can happen going forward, 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

3 2

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

Austin Design Summit track layout
by Kato, Tomoyuki 01 Apr '16

01 Apr '16

Hi team, Austin Design Summit track layout is announced. http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html I18n team has a contributor meetup at Friday. I'm looking forward to meet many people. Thank you to coodinate, Daisy. Thanks, KATO Tomoyuki

6 5

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

What's Up, Doc? Mitaka Release Edition
by Lana Brindley 01 Apr '16

01 Apr '16

Hi everyone, While it was very tempting to write something something shocking here for April Fools', I thought everyone might have already had their heart rate raised enough by the fact that Mitaka is only five days away! This will be my final docs newsletter before the release, and the docs are in great shape ready to go out. I would like to sincerely thank Andreas and our release managers Brian and Olga, not only for the hard work they've done so far, but also for holding down the fort over the next few days while I'm out of contact. Please remember to contact them directly if you have any last minute documentation fires that need putting out. I'd also like to mention the hard work that the Installation Guide testers have been putting in over the past couple of weeks. The testing matrix is looking very green (https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting) and I'm confident that we'll get the Mitaka guide out fully tested and on schedule. Don't forget you can check release progress on the etherpad here: https://etherpad.openstack.org/p/MitakaRelease == Progress towards Mitaka == 5 days to go! 558 bugs closed so far for this release. Docs Testing * https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting * Only a few items left to check off, at this stage we're good to publish the Ubuntu, RDO, and Suse guides on release day. Release Tasks: * Release planning occurs in our etherpad here: https://etherpad.openstack.org/p/MitakaRelease * All tasks that should be completed at this stage are done, and we're on track to start the release process in the 24-48 hours before the release drops. * Release notes for the docs project are in a "reno-style" directory in the openstack-manuals repo. This directory is not being managed by Reno, however, so please propose patches to it directly. == The Road to Austin == * First of all, thanks for the amazing feedback on what docs sessions you would like to see at the Austin Design Summit! We have filled our entire allocation (and then some), and the schedule so far is here: https://etherpad.openstack.org/p/Newton-DocsSessions * There's been a really robust and exciting conversation about the Install Guide on the dev list over the past week or so, which I have been following closely. If you're interested in overhauling our Install Guide (and it certainly seems like a lot of people are!), then please make sure you add our Install Guide Design Summit session to your agenda. It is on Wednesday at 11:50, so placed so that it can run over into lunchtime if required. * A note for those who noticed the Ops guide omission: this should take place in the Ops track, and I'll let you know when that session will be. == Doc team meeting == Next meetings: The US meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-03-30 Next meetings: APAC: No APAC meeting this week US: Wednesday 13 April, 19:00 UTC (This is after the Mitaka release) Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#1_April_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

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

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

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

23 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