- OpenStack-I18n - lists.openstack.org

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 06 Apr '16

06 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 03 Apr '16

03 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 03 Apr '16

03 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 03 Apr '16

03 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 02 Apr '16

02 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 31 Mar '16

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

31 Mar '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 30 Mar '16

30 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 29 Mar '16

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

29 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

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

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

21 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

PTL non-candidacy
by Ying Chun Guo 21 Mar '16

21 Mar '16

Hi, team I'm writing to let team know I will not run for I18n PTL in Newton cycle. I18n team have a long history starting from July of 2013. I was there at the beginning. Almost 3 years passed, I see the team growth rapidly. Especially in the recently year, a lot of things happened. In Vancouver, we had the first I18n team meeting and we decided to go official. We made it in Liberty cycle. In Tokyo, tens of translators got their ATC codes because of translation contributions. We successfully moved to Zanata. We set up our own I18n repository. Translation contributions can be shown in stackalytics. Translation check website will be ready soon. Full time translators work together with us in Mitaka translation. There were 1 million words translations in Zanata after Liberty translation. I'm sure the number will grow a big amount in Mitaka. I'm so proud of the team and progresses we made. I appreciated the great support from coordinators. I appreciated the help of Elizabeth, Steve, Carlos and Alex, who helped to set up our own dedicated translation website. I appreciated Andreas's work on infra side. I appreciated Tom and Stefano who helped to set up the team. I'm so glad that I made a lot of friends there. I'm happy to see Kato announced his candidacy for the new PTL. I think he is well qualified. I will not leave. I will support the new PTL to make a smooth transition. I will continue as the coordinator of Simplified Chinese team and contributor of I18n team. I'm looking forward to see more achievements we make in the future. Thank you and best regards. Ying Chun Guo (Daisy)

11 10

Hard string freeze and version switch
by Ying Chun Guo 20 Mar '16

20 Mar '16

Hi, team Now there are 5 server side projects and 1 dashboard project which have met the hard string freeze and cut the RC1 ( release candidate 1 ). In their source code repositories, the stable/mitaka branch is created. In Zanata translation server, I created corresponding versions named as "stable-mitaka". The translation works need to be switched to "stable-mitaka" version from master version. I also changed the links in the front page of translation server. If you don't know which version you should work with, an easy way is to navigate to the correct version from the links in the front page. The 5 server side projects are: nova, glance, keystone, cinder, neutron, and heat. The 1 dashboard projects are: django_openstack_auth. The translations are planned to be imported in RC2. The server projects will have their source codes ready for RC2 next week. It's good if we can have the translations completed by the end of next week. Of course, the early, the better. The dashboard projects are slower than server projects. Horizon project will probably cut RC1 in the early of next week. Any questions, please let me know. Best regards Ying Chun Guo (Daisy)

1 1

Call for participation in evolving GILT in curriculum
by chandan kumar 18 Mar '16

18 Mar '16

Hi All, Most in FUEL community must have heard on the initiative to bring out a formal curriculum in GILT which can be taught either as short term or long term course. This was outcome of discussions at past FUEL-GILT events and FUEL meetings in Gnunify. Attached is presentation on how we intend to proceed. Have also created a draft document, link given below. We have been working on creating a draft curriculum, which becomes the starting point. https://docs.google.com/document/d/1M4KgUy4VOU8aIlo8XT-C7HW2no_B0B5ZhkM69TZ… Stage 1: Review draft & expand topic index. Owners for topics identified and available to work in Stage 2. This will be come the curriculum/syllabus. Target Date: 31st March 2016 Stage 2: On each identified topic, owners will collaboratively write a chapter of few pages (upto 10 should be good to start with). This would contain brief on the topic and sub topics, but not going into too much detail, external references can be given. In long term this content would evolve into one or more chapters of book on GILT which will be used as book in training/teaching GILT. Date: 1-2 months from completion of Stage 1. Welcome everyone to contribute to this. - Review the draft, give suggestions on what can be added. - Take ownership of topics, so can build topic index in chosen topic and write chapter on it. Link to document: https://docs.google.com/document/d/1M4KgUy4VOU8aIlo8XT-C7HW2no_B0B5ZhkM69TZ… If you wish to edit, please request someone who has edit permission to add you, or post comments/suggestions to start with. Thanks, Chandan Kumar

1 0

Zanata Group for Mitaka dashboard translations
by Akihiro Motoki 18 Mar '16

18 Mar '16

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

2 1

What's Up, Doc? 18 March 2016
by Lana Brindley 17 Mar '16

17 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, It is with great pleasure that I announce that I will be the PTL again for Newton, which will be my third release for openstack-manuals. I'm overwhelmed by the positive messages I've received since announcing my candidacy, and very excited to be leading such a dedicated and innovative group into the fray again. This week I spent some time on the Contributor Guide, working with Brian to get the docs tools documented, which is something we've been wanting to do for some time. Very soon I'll be calling for your ideas on Summit sessions, and beginning to do Design Summit planning. The Install Guide is now in the last push to have everything tested before release, but we can still use your help getting it all done! If you can help, please contact Matt Kassawara, or any docs core. == Progress towards Mitaka == 19 days to go! 515 bugs closed so far for this release. Docs Testing * Volunteers required! * https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting Release Tasks: * Release planning occurs in our etherpad here: https://etherpad.openstack.org/p/MitakaRelease * We're now freezing larger changes to the Install Guide, so cores will not be merging anything that changes the architecture of the guide, or significantly changes the technical content (except where that change is as a result of testing). This is to make the Install Guide testers work a little easier, by stopping the book from moving too much from under them. * We will be publishing release notes for our own projects to == Docs-tools == * Andreas and team have released a new version of the docs theme, which removes the versions information from the sidebar, and also removes the duplicated titles. This should make navigating the CI guides much easier, and reduce confusion over versions. == The Road to Austin == * PTL elections are now open for those projects that have more than one candidate. You should have received an email for elections in which you are eligible to vote. * I am pleased to announce that I am remaining as docs PTL for Newton (elected unopposed). I would also like to congratulate KATO Tomoyuki on becoming the new PTL for i18n, and to thank Daisy for her hard work in that group for many releases. * I have requested workrooms and fishbowls for the Austin Design Summit. I'll let you know when we get our allocation. I will send out a note next week to start gathering your ideas for sessions. == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' New for Mitaka release notes: Improved Pacemaker/Corosync cluster installation and configuration details http://docs.openstack.org/ha-guide/controller-ha-pacemaker.html (kudos Andrew Beekhof). Pacemaker Cluster Manager http://docs.openstack.org/ha-guide/intro-ha-arch-pacemaker.html and Keepalived http://docs.openstack.org/ha-guide/intro-ha-arch-keepalived.html architecture details and limitations (kudos Andrew Beekhof). Detailed Mariadb/Galera cluster installation, configuration and management guide http://docs.openstack.org/ha-guide/controller-ha-galera.html (kudos Kenneth Dyer). Improved RabbitMQ clustering guide http://docs.openstack.org/ha-guide/controller-ha-rabbitmq.html - HAProxy antipattern explained, new A/A option with Pacemaker resource agents (kudos KATO Tomoyuki, Andrew Beekhof). Many more, so read everything carefully ;-) '''User Guides - Joseph Robinson''' Larger patch for editing submitted this week, and working within the user guide team to reorganize the command line content in the admin user guide by moving common files into the cloud admin guide. '''API Docs - Anne Gentle''' Swagger files now built to developer.openstack.org. Project teams have templates for writing API guides within their project repository . == Doc team meeting == Next meetings: No meeting was held this week. Next meetings: APAC: Wednesday 23 March, 00:30 UTC US: Wednesday 30 March, 19:00 UTC 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#18_March_2016 - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJW642DAAoJELppzVb4+KUyfDcIAMpfegqx4dfyFCbK2LzhBzT0 Ky9CVUCzKJQGdZQVCGcfJZRJI3OtLXfWMKrkx5v5pE6lw0UJ1a8RfR8/46weUn1v wlC9k95RLeff64Wa16AE6YQc6oXEhsGWWciptgeTmg2aeWJfax7S1wx2F8UhF419 FM4iFr/PhvyrVs4BXeyx6l3LLRFfSWo/YiyEHDUOAPOQMJ0N/gZaOL5ir+fASEwl xSXbb9fzdVfhrJivnPOrxYoZBSivTSlIn4xWmGsMaoCUzV2xrQmwCWRV07TVneYp nthofj01Ij3kNWv2Gm3XrIkJFkHX7OG0+tlxPs3CUm2bguzQlpND45I/ILv8TbE= =GmrT -----END PGP SIGNATURE-----

1 0

Translation server is back !
by Ying Chun Guo 17 Mar '16

17 Mar '16

With the great support from infrastructure team, now we have our translation server back. You can login to http://translate.openstack.org to continue your work then. Sorry for the inconvenience. Best regards Ying Chun Guo (Daisy)

2 1

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

17 Mar '16

> 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 --- Augustina Ragwitz Sr System Software Engineer, HPE Cloud Hewlett Packard Enterprise --- irc: auggy

1 0

Glossary management
by Akihiro Motoki 17 Mar '16

17 Mar '16

# I changed the thread title to the appropriate one. 2016-03-01 17:23 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Thank you for the input, Akihiro and Kato. > > I'm not strict in local communication method and IRC ID. > If you have clearly documented them in your team wiki, that's fine. > > As to the glossary, I still think git repository is better than > wiki to store glossaries. Git repo has strict control, while wiki > has no controls at all. Wiki is used for frequently update purpose. > After it turns to mature, Git repo is good to store. I agree that it is better to use gerrit to manage glossaries, but all of my efforts disappointed me and discourage me to do more efforts. I already tried to maintain our glossary with context in our git repository. It used YAML file and converts it to PO files. It allowed us to keep contextual information. You said it will be discussed in the IRC meetings, but I got no feedback. I felt it was simply ignored (or rejected). (I could not join IRC meetings. If joining meetings is a requirement, I have to go away.) I clearly define what is required, but I don't see any counter solution provided and it forces me to use useless format (i.e., PO files). I believe I already have made enough proposal, but all of the results disappoints me and discourage me to try more efforts because it tends to waste my time. Finally, I tried to use another way to manage the glossary, then I was complained that it is not a standard way...... As a result, I had no way to satisfy requirements. Managing the glossary in two places is completely less-productive, maintain the master glossary with context information and then copy it into i18n repo (with losing the contextual information). > And, using pot/po file can make all translation teams to easily follow the > same glossary list. Do you mean even if the data format does not satisfy our requirements we should use it? Unified tools or formats are also important, but tools/format which do not satisfy requirements are useless. > As to the glossary, I still think git repository is better than > wiki to store glossaries. Git repo has strict control, while wiki > has no controls at all. Wiki is used for frequently update purpose. > After it turns to mature, Git repo is good to store. Regarding wiki usage, I don't think each language team page is not frequently updated. Does this mean a language team page does not fit into Wiki? I am not sure why we need to apply strict policy only for glossary. If the problem is that a wiki allows everyone to edit contents (i.e. glossary in this case), it is a problem of communication in a local language team. Final question. Gerrit is an easy way for translators or translation reviewers? If a language coordinator is forced to proxy maintaining glossaries, Perhaps, I am expecting too much and I may be better to be a translator. Akihiro > I understand Japanese glossaries are out of date and your team don't > like the current one in Zanata. If that's your team decision, I'm OK > to delete it from Zanata. > > Thoughts? > > Best regards > Ying Chun Guo (Daisy) > > > "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> wrote on 2016/02/27 > 17:08:46: > >> From: "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> >> To: "'Akihiro Motoki'" <amotoki(a)gmail.com>, Ying Chun Guo/China/IBM@IBMCN >> Cc: Openstack-i18n <openstack-i18n(a)lists.openstack.org> >> Date: 2016/02/27 17:40 >> Subject: RE: [Openstack-i18n] To language team coordinators: get >> ready for Mitaka translation >> > >> > Thanks Daisy for initiating this. >> > >> > 2016-02-25 17:53 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> > > 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. >> > >> > I would like to raise a question how the glossary work? Is it actually >> > working? >> > >> > As one of coordinators of Japanese team, the glossary list itself is >> > out-of-date. >> > In addition to update per-language glossary, can we update a list >> of glossary >> > itself? >> > >> > Beyond this, the current format of PO file for the glossary lacks an >> > essential feature as I described before. There is no way to describe the >> > context. >> > I wonder how the glossary help translations without the contextual >> > information. >> > As a result, Japanese team is forced to describe contextual information >> > in translated strings. >> > This is the reason we preferred to Wiki style glossary. >> > >> > From the above observation, does it sound a good option to clear the >> > whole >> > entry of Zanata glossary of a specific language? >> >> +1 to clear, as long as Japanese, as of now. >> >> > > 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. >> > >> > I missed the previous team meeting (it is not special to me due to >> the meeting >> > time). >> > I would like to make some follow-up comments on a local communication. >> > >> > I personally would like to continue to use Gitter (hosted by Github) as >> > a communication channel in Japanese team. From my past experience, it >> > has >> > various good merits. >> > I felt the first point is really useful in the crunch time of Liberty >> > translation reviews. >> > >> > * Pros: >> > * it has a notification mechanism. Unread messages will be notified >> > via >> > email. >> > * It can be used via browser (without any extra application) >> > * Unlimited archive as long as gitter room is open to everyone >> > * Cons >> > * it is not provided by OpenStack infra >> > >> > Kato-san and Japanese team members, feel free to comment it. >> > Your feedbacks would be really appreciated. >> >> I agree to using Gitter in Japanese team. >> >> In my understand, using IRC channel for local team is not mandatory, >> just an option. >> >> >> > > 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. >> > >> > "with Zanata ID"? It is just an option. It is not a requirement. >> > It is not a surprising thing someone uses an IRC nickname different from >> > Zanata ID. >> >> I'm using different IDs :) >> And, I'm not always join IRC because of my business reason and equipments. >> To coordinate my local language team, I'd like to use Gitter and >> local mailing list. >> >> >> Regards, >> KATO Tomoyuki >> >> > Note that it is important we need to know each other who you are but it >> > is not a requirement to use Zanata ID as IRC nickname if you already use >> > a different IRC nick. >> > >> > > If you have any questions, talk to me. >> > > My IRC ID is "Daisy" in the channel of #openstack-i18n. >> > >> > I can help you too. My nick is 'amotoki'. >> > I am usually online from 0200UTC to 1600UTC. >> > >> > # It will be easier to find me compared to finding Daisy on IRC :) # >> > Just >> > joking.. never mind Daisy! >> > >> > Akihiro >> > >> > > 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 >> >

3 2

Re: [Openstack-i18n] Cannot connect to Zanata
by Ilya Alekseyev 17 Mar '16

17 Mar '16

Dear Yumiko, Ian, Kato-san, same here, i can login to openstack.org and more i've checked in https://openstackid.org/accounts/user/profile that authentification is successfull: https://translate.openstack.org:443/openid.seam | LOGIN But unfortunatelly can't login to zanata. Kind regards, Ilya Alekseyev. 2016-03-17 10:28 GMT+03:00 Yumiko Ogawa <OGAWAYUM(a)jp.ibm.com>: > > Kato-san, > > Yes, I can login www.openstack.org without any problem, but not Zanata... > > Best regards, > > 小川優美子 Yumiko Ogawa, PMP® <ogawayum(a)jp.ibm.com> > Translation Services Center, IBM Japan > Tel: 03-3808-5007 > > > "Kato, Tomoyuki" ---2016/03/17 16:22:32---Hi, Can you login www.openstack.org? > > From: "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> > To: Yumiko Ogawa/Japan/IBM@IBMJP, Ilya Alekseyev <ilyaalekseyev(a)acm.org> > Cc: "openstack-i18n(a)lists.openstack.org" < openstack-i18n(a)lists.openstack.org> > Date: 2016/03/17 16:22 > Subject: RE: [Openstack-i18n] Cannot connect to Zanata > > > ________________________________ > > > > Hi, > > Can you login www.openstack.org? > # I can. But I can not login translate.openstack.org, too. > > I guess it seems to be a combination problem between > Zanata and OpenStack OpenID, or Zanata standalone problem... > > KATO Tomoyuki > > > -----Original Message----- > > Hi, > > > > We have the same problem in Japan. I understand that the OpenID authentication system is down. Our translators have been > > on standby all day today, so hopefully Zanata will be back soon. > > > > 小川優美子 Yumiko Ogawa, PMP® <ogawayum(a)jp.ibm.com> > > Translation Services Center, IBM Japan > > Tel: 03-3808-5007 > > > > > > Ilya Alekseyev ---2016/03/17 15:59:39---Dear colluegues, for some unknown reason i cannot connect to Zanata. > > > > From: Ilya Alekseyev <ilyaalekseyev(a)acm.org> > > To: "openstack-i18n(a)lists.openstack.org" < openstack-i18n(a)lists.openstack.org> > > Date: 2016/03/17 15:59 > > Subject: [Openstack-i18n] Cannot connect to Zanata > > > > ________________________________ > > > > > > > > > > Dear colluegues, > > > > for some unknown reason i cannot connect to Zanata. > > Tried different browsers and it just don't work. > > Wonder if somebody have the same problems? > > > > Kind regards, > > Ilya Alekseyev_______________________________________________ > > Openstack-i18n mailing list > > Openstack-i18n(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > > > > > > > >

1 0

Mitaka translation, go!
by Ying Chun Guo 17 Mar '16

17 Mar '16

Hi, team According to the release schedule, Mitaka translation starts from today. In the home page of translation website[1], you can find the detail information of Mitaka translation plan. The plan includes 6 web projects and 8 backend projects. Mitaka translation will last for above 3 weeks, from March 4th to March 28th. Here are some points for your attention during translation. 1. We start translations after soft string freeze. It means there will be string changes while you are translating. So don't be surprise when you notice the percentage of translation progress becomes smaller. 2. The hard string freeze will happen in the week of March 14-18. Different projects have different exact time of hard freeze. After hard freeze, our translation work will switch from master version to mitaka version. The links in the translation plan in the home page will be changed correspondingly. So continue your translation work from links in the home page is a good practise. Also, I will send notice to mailing list when the switch happens. 3. After hard string freeze and switch to mitaka version, there will be very few string changes. We can get 10(almost) more days after hard string freeze to finish up the translations. Let's work together to make a great success of mitaka translation. If you have any questions or get into troubles, there are several ways to ask help from: 1. Get help from your local team through the local communication method 2. Go to #openstack-i18n 3. Send mail to I18n mailing list There is a whole team who are willing to help. Enjoy translations! Best regards Ying Chun Guo (Daisy) [1] http://translate.openstack.org

4 8

Cannot connect to Zanata
by Ilya Alekseyev 17 Mar '16

17 Mar '16

Dear colluegues, for some unknown reason i cannot connect to Zanata. Tried different browsers and it just don't work. Wonder if somebody have the same problems? Kind regards, Ilya Alekseyev

4 4

IRC meeting today
by Ying Chun Guo 16 Mar '16

16 Mar '16

Hi, team We will have IRC meeting today at UTC 1300 in #openstack-meeting. The agenda in my mind are: * Mitaka translation updates * Open discussions If you have more topics, feel free to add. Best regards Ying Chun Guo (Daisy)

1 0

Re: [Openstack-i18n] Wrong plural formula for russian
by Ilya Alekseyev 16 Mar '16

16 Mar '16

Dear Daisy, Akihiro, Alex, thank you very much for your investigation and fix of this issue. Kind regards. Ilya Alekseyev 2016-03-15 10:14 GMT+03:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > I think you are right. > plural can be only set once. > After setting, it's not able to change. > > python-neutronclient is fixed. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/14/2016 07:21:10 PM: > > > From: Akihiro Motoki <amotoki(a)gmail.com> > > To: Ying Chun Guo/China/IBM@IBMCN > > Cc: Alex Eng <aeng(a)redhat.com>, Ilya Alekseyev > > <ilyaalekseyev(a)acm.org>, "openstack-i18n(a)lists.openstack.org" > > <openstack-i18n(a)lists.openstack.org> > > Date: 03/14/2016 07:22 PM > > Subject: Re: [Openstack-i18n] Wrong plural formula for russian > > > > Hi Daisy, > > > > 2016-03-14 17:33 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > > > Hi, Akihiro > > > > > > I tried to upload a new Russian translation file with the correct > plural > > > formula to django-openstack-auth. > > > And then I downloaded it. Yet the header is not changed at all. > > > I'm afraid uploading po files will not change the header. > > > > I made some tests with nplurals. > > My conclusion is that Zanata allows to update nplurals ONLY ONCE. > > I succeed to change nplural to 2 by putting japanese PO file, but once > > it was changed, > > even though I put Japanese PO file with nplural==1, nplural was not > changed. > > > > I tested it using neutronclient Japanese. > > As an unfortunate result, Japanese resource in neutronclient now have > > the wrong nplurals (2). > > Could you reset neutronclient in Japanese? > > (There is no translation in neutronclient, so we can do this more easily > :-) > > > > Thanks, > > Akihiro > > > > > > > > Best regards > > > Ying Chun Guo (Daisy) > > > > > > > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/12/2016 09:13:09 PM: > > > > > >> From: Akihiro Motoki <amotoki(a)gmail.com> > > >> To: Ying Chun Guo/China/IBM@IBMCN > > >> Cc: Alex Eng <aeng(a)redhat.com>, Ilya Alekseyev > > >> <ilyaalekseyev(a)acm.org>, "openstack-i18n(a)lists.openstack.org" > > >> <openstack-i18n(a)lists.openstack.org> > > >> Date: 03/12/2016 09:14 PM > > >> Subject: Re: [Openstack-i18n] Wrong plural formula for russian > > >> > > >> Hi Daisy, Alex, > > >> > > >> I think the steps Daisy describes is the last resort. > > >> Regarding translation statistics, I have nothing to say as I don't > > >> know any about stats. > > >> > > >> There are a couple of things I would like to note. > > >> > > >> * It is better to first try to upload Russian PO files with > nplurals=3 > > >> even though you failed it last time. > > >> * We need to check other Russian resources other than Horizon. > > >> I checked django-openstack-auth and nova and they have nplurals=4. > > >> There might be more. > > >> At now only Horizon and dashboard-related projects use plural > cases, > > >> so we see this issue only in Horizon now. > > >> > > >> Akihiro > > >> > > >> > > >> > > >> 2016-03-11 14:20 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > > >> > Thank you for the investigation, Akihiro and Alex. > > >> > > > >> > Below are the steps we previously used. > > >> > We can follow the same steps, just changing "stable" version to > > > "master" > > >> > version. > > >> > I think the statistic data will not be affected in step 1 to 5. > > >> > But, if we delete master-old, the contribution data in master-old > will > > > be > > >> > removed. > > >> > So my suggestion is to do the same steps, and keep master-old > version > > > (mark > > >> > it as readonly) > > >> > till 6 month or 12 month later when the contribution data is not > that > > >> > important. > > >> > > > >> >> 1. Create Russian translation files with only the correct header > and > > > the > > >> >> pluralities translation items. > > >> >> 2. Create a new version named as russian-fix > > >> >> 3. Upload the source files and the Russian translation files > created > > > in #1 > > >> >> to the version russian-fix > > >> >> 4. Merge the stable version with version russian-fix > > >> >> 5. Rename stable version to stable-old, and rename russian-fix to > > > stable. > > >> > > > >> > Alex and Akihiro, please confirm my proposal. > > >> > Then I can take actions. > > >> > > > >> > Best regards > > >> > Ying Chun Guo (Daisy) > > >> > > > >> > > > >> > Alex Eng <aeng(a)redhat.com> wrote on 2016/03/11 04:36:15: > > >> > > > >> >> From: Alex Eng <aeng(a)redhat.com> > > >> >> To: Ilya Alekseyev <ilyaalekseyev(a)acm.org> > > >> >> Cc: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun Guo/China/ > > >> >> IBM@IBMCN, "openstack-i18n(a)lists.openstack.org" <openstack- > > >> >> i18n(a)lists.openstack.org> > > >> >> Date: 2016/03/11 04:37 > > >> >> Subject: Re: [Openstack-i18n] Wrong plural formula for russian > > >> > > > >> > > > >> >> > > >> >> Hi, > > >> >> > > >> >> If we fix the plural forms in pot file and push to Zanata, that > > >> >> would not affect the statistics. > > >> >> > > >> >> But I remember last time when we trying to fix this, there are > some > > >> >> limitation of the pluralform wont update after the file is being > > >> >> uploaded once to Zanata. And we have to create a new version with > > >> >> fixed pot file and use "merge translation" feature to bring over > all > > >> >> the translations. > > >> >> > > >> >> We can do the same thing again and the statistics won't be > affected. > > >> >> (copied translation doesn't count in as contribution) > > >> >> > > >> >> I checked and Zanata has the correct form. > > >> >> > > >> >> nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 > && > > >> >> (n%100<10 || n%100>=20) ? 1 : 2) > > >> >> > > >> >> --------------------------------------------- > > >> >> > > >> >> Alex Eng > > >> >> Senior Software Engineer > > >> >> Globalisation Tools Engineering > > >> >> DID: +61 3514 8262 > > >> >> Mobile: +614 2335 3457 > > >> >> > > >> >> Red Hat, Asia-Pacific Pty Ltd > > >> >> Level 1, 193 North Quay > > >> >> Brisbane 4000 > > >> >> Office: +61 7 3514 8100 > > >> >> Fax: +61 7 3514 8199 > > >> >> Website: www.redhat.com > > >> >> > > >> >> On Fri, Mar 11, 2016 at 3:00 AM, Ilya Alekseyev > > > <ilyaalekseyev(a)acm.org> > > >> >> wrote: > > >> >> Daisy, > > >> >> > > >> >> i remember we fixed this for Liberty. But looks like somewhere > wrong > > >> >> config or error in script that creating master version. > > >> >> How ca we fix it? How i can help with this issue? > > >> >> > > >> >> Alex, is it possible to fix plural formula ofr version and keep > > >> >> statistics safe? > > >> >> > > >> >> We need to fix it as soon as possible, because 4 plural forms > making > > >> >> issues for russian translation (empty message, empty buttons, etc, > > >> >> as we can seee in Kilo release). > > >> >> > > >> >> Kind regards, > > >> >> Ilya Alekseyev. > > >> >> > > >> >> С уважением, > > >> >> Илья Алексеев > > >> >> > > >> >> Russian OpenStack Community > > >> >> > > >> >> 2016-03-10 19:37 GMT+03:00 Akihiro Motoki <amotoki(a)gmail.com>: > > >> >> Russian translations in the horizon repo is downloaded from > Zanata, > > >> >> OpenStack translation platform. > > >> >> It seems Zanata has wrong plural configuration. > > >> >> > > >> >> > Daisy, Alex, > > >> >> Could you check Russian configuration in Zanata is correct? > > >> >> > > >> >> 2016-03-10 22:42 GMT+09:00 Ilya Alekseyev <ilyaalekseyev(a)acm.org>: > > >> >> > Dear collegues, > > >> >> > > > >> >> > i've checked current russian translation in horizon repository > and > > > find > > >> >> > out > > >> >> > that we have wrong plural formula in upstream. > > >> >> > > > >> >> > https://github.com/openstack/horizon/blob/master/ > > >> >> openstack_dashboard/locale/ru/LC_MESSAGES/django.po#L35-L37 > > >> >> > > > >> >> > There is only 3 plural forms in Russian. > > >> >> > And correct formula should be > > >> >> > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && > n%10<=4 > > > && > > >> >> > (n%100<10 || n%100>=20) ? 1 : 2); > > >> >> > > > >> >> > Looks like some script is wrong. > > >> >> > Does anybody know how to fix it? > > >> >> > > > >> >> > Kind regards, > > >> >> > Ilya Alekseyev > > >> >> > > > >> >> > _______________________________________________ > > >> >> > 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] Wrong plural formula for russian
by Akihiro Motoki 15 Mar '16

15 Mar '16

Hi Daisy, 2016-03-14 17:33 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Hi, Akihiro > > I tried to upload a new Russian translation file with the correct plural > formula to django-openstack-auth. > And then I downloaded it. Yet the header is not changed at all. > I'm afraid uploading po files will not change the header. I made some tests with nplurals. My conclusion is that Zanata allows to update nplurals ONLY ONCE. I succeed to change nplural to 2 by putting japanese PO file, but once it was changed, even though I put Japanese PO file with nplural==1, nplural was not changed. I tested it using neutronclient Japanese. As an unfortunate result, Japanese resource in neutronclient now have the wrong nplurals (2). Could you reset neutronclient in Japanese? (There is no translation in neutronclient, so we can do this more easily :-) Thanks, Akihiro > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/12/2016 09:13:09 PM: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: Ying Chun Guo/China/IBM@IBMCN >> Cc: Alex Eng <aeng(a)redhat.com>, Ilya Alekseyev >> <ilyaalekseyev(a)acm.org>, "openstack-i18n(a)lists.openstack.org" >> <openstack-i18n(a)lists.openstack.org> >> Date: 03/12/2016 09:14 PM >> Subject: Re: [Openstack-i18n] Wrong plural formula for russian >> >> Hi Daisy, Alex, >> >> I think the steps Daisy describes is the last resort. >> Regarding translation statistics, I have nothing to say as I don't >> know any about stats. >> >> There are a couple of things I would like to note. >> >> * It is better to first try to upload Russian PO files with nplurals=3 >> even though you failed it last time. >> * We need to check other Russian resources other than Horizon. >> I checked django-openstack-auth and nova and they have nplurals=4. >> There might be more. >> At now only Horizon and dashboard-related projects use plural cases, >> so we see this issue only in Horizon now. >> >> Akihiro >> >> >> >> 2016-03-11 14:20 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> > Thank you for the investigation, Akihiro and Alex. >> > >> > Below are the steps we previously used. >> > We can follow the same steps, just changing "stable" version to > "master" >> > version. >> > I think the statistic data will not be affected in step 1 to 5. >> > But, if we delete master-old, the contribution data in master-old will > be >> > removed. >> > So my suggestion is to do the same steps, and keep master-old version > (mark >> > it as readonly) >> > till 6 month or 12 month later when the contribution data is not that >> > important. >> > >> >> 1. Create Russian translation files with only the correct header and > the >> >> pluralities translation items. >> >> 2. Create a new version named as russian-fix >> >> 3. Upload the source files and the Russian translation files created > in #1 >> >> to the version russian-fix >> >> 4. Merge the stable version with version russian-fix >> >> 5. Rename stable version to stable-old, and rename russian-fix to > stable. >> > >> > Alex and Akihiro, please confirm my proposal. >> > Then I can take actions. >> > >> > Best regards >> > Ying Chun Guo (Daisy) >> > >> > >> > Alex Eng <aeng(a)redhat.com> wrote on 2016/03/11 04:36:15: >> > >> >> From: Alex Eng <aeng(a)redhat.com> >> >> To: Ilya Alekseyev <ilyaalekseyev(a)acm.org> >> >> Cc: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun Guo/China/ >> >> IBM@IBMCN, "openstack-i18n(a)lists.openstack.org" <openstack- >> >> i18n(a)lists.openstack.org> >> >> Date: 2016/03/11 04:37 >> >> Subject: Re: [Openstack-i18n] Wrong plural formula for russian >> > >> > >> >> >> >> Hi, >> >> >> >> If we fix the plural forms in pot file and push to Zanata, that >> >> would not affect the statistics. >> >> >> >> But I remember last time when we trying to fix this, there are some >> >> limitation of the pluralform wont update after the file is being >> >> uploaded once to Zanata. And we have to create a new version with >> >> fixed pot file and use "merge translation" feature to bring over all >> >> the translations. >> >> >> >> We can do the same thing again and the statistics won't be affected. >> >> (copied translation doesn't count in as contribution) >> >> >> >> I checked and Zanata has the correct form. >> >> >> >> nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && >> >> (n%100<10 || n%100>=20) ? 1 : 2) >> >> >> >> --------------------------------------------- >> >> >> >> Alex Eng >> >> Senior Software Engineer >> >> Globalisation Tools Engineering >> >> DID: +61 3514 8262 >> >> Mobile: +614 2335 3457 >> >> >> >> Red Hat, Asia-Pacific Pty Ltd >> >> Level 1, 193 North Quay >> >> Brisbane 4000 >> >> Office: +61 7 3514 8100 >> >> Fax: +61 7 3514 8199 >> >> Website: www.redhat.com >> >> >> >> On Fri, Mar 11, 2016 at 3:00 AM, Ilya Alekseyev > <ilyaalekseyev(a)acm.org> >> >> wrote: >> >> Daisy, >> >> >> >> i remember we fixed this for Liberty. But looks like somewhere wrong >> >> config or error in script that creating master version. >> >> How ca we fix it? How i can help with this issue? >> >> >> >> Alex, is it possible to fix plural formula ofr version and keep >> >> statistics safe? >> >> >> >> We need to fix it as soon as possible, because 4 plural forms making >> >> issues for russian translation (empty message, empty buttons, etc, >> >> as we can seee in Kilo release). >> >> >> >> Kind regards, >> >> Ilya Alekseyev. >> >> >> >> С уважением, >> >> Илья Алексеев >> >> >> >> Russian OpenStack Community >> >> >> >> 2016-03-10 19:37 GMT+03:00 Akihiro Motoki <amotoki(a)gmail.com>: >> >> Russian translations in the horizon repo is downloaded from Zanata, >> >> OpenStack translation platform. >> >> It seems Zanata has wrong plural configuration. >> >> >> >> > Daisy, Alex, >> >> Could you check Russian configuration in Zanata is correct? >> >> >> >> 2016-03-10 22:42 GMT+09:00 Ilya Alekseyev <ilyaalekseyev(a)acm.org>: >> >> > Dear collegues, >> >> > >> >> > i've checked current russian translation in horizon repository and > find >> >> > out >> >> > that we have wrong plural formula in upstream. >> >> > >> >> > https://github.com/openstack/horizon/blob/master/ >> >> openstack_dashboard/locale/ru/LC_MESSAGES/django.po#L35-L37 >> >> > >> >> > There is only 3 plural forms in Russian. >> >> > And correct formula should be >> >> > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 > && >> >> > (n%100<10 || n%100>=20) ? 1 : 2); >> >> > >> >> > Looks like some script is wrong. >> >> > Does anybody know how to fix it? >> >> > >> >> > Kind regards, >> >> > Ilya Alekseyev >> >> > >> >> > _______________________________________________ >> >> > Openstack-i18n mailing list >> >> > Openstack-i18n(a)lists.openstack.org >> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >> > >> > >

2 1

GILT in Curriculum
by Rajesh Ranjan 14 Mar '16

14 Mar '16

Hi We, FUEL Community [1], are in discussion with SICSR [2] and some other institutes to introduce a formal curriculum on GILT (Globalization, Internationalization, Localization, Translation) technology which can be taught either as short term or long term course. This was outcome of discussions at past FUEL GILT Conference and FUEL meetings in Gnunify. Please refer the mail by Karunakar: https://lists.fedorahosted.org/archives/list/fuel-discuss@lists.fedorahoste… Please check the draft curriculum link: https://docs.google.com/document/d/1M4KgUy4VOU8aIlo8XT-C7HW2no_B0B5ZhkM69TZ… You are invited to contribution in the formation of the curriculum and take any chapter/sub chapter. Your suggestions are also welcome! Like all the content of FUEL Project, the content of the curriculum will be under open license. This is a unique activity and will help GILT technology. Thanks [1]. http://fuelproject.org/ [2]. http://sicsr.ac.in/ -- *Rajesh Ranjan* Open Source Community Manager Digital India, Govt. of India https://twitter.com/kajha

1 0

Re: [Openstack-i18n] Wrong plural formula for russian
by Akihiro Motoki 14 Mar '16

14 Mar '16

Hi Daisy, Alex, I think the steps Daisy describes is the last resort. Regarding translation statistics, I have nothing to say as I don't know any about stats. There are a couple of things I would like to note. * It is better to first try to upload Russian PO files with nplurals=3 even though you failed it last time. * We need to check other Russian resources other than Horizon. I checked django-openstack-auth and nova and they have nplurals=4. There might be more. At now only Horizon and dashboard-related projects use plural cases, so we see this issue only in Horizon now. Akihiro 2016-03-11 14:20 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Thank you for the investigation, Akihiro and Alex. > > Below are the steps we previously used. > We can follow the same steps, just changing "stable" version to "master" > version. > I think the statistic data will not be affected in step 1 to 5. > But, if we delete master-old, the contribution data in master-old will be > removed. > So my suggestion is to do the same steps, and keep master-old version (mark > it as readonly) > till 6 month or 12 month later when the contribution data is not that > important. > >> 1. Create Russian translation files with only the correct header and the >> pluralities translation items. >> 2. Create a new version named as russian-fix >> 3. Upload the source files and the Russian translation files created in #1 >> to the version russian-fix >> 4. Merge the stable version with version russian-fix >> 5. Rename stable version to stable-old, and rename russian-fix to stable. > > Alex and Akihiro, please confirm my proposal. > Then I can take actions. > > Best regards > Ying Chun Guo (Daisy) > > > Alex Eng <aeng(a)redhat.com> wrote on 2016/03/11 04:36:15: > >> From: Alex Eng <aeng(a)redhat.com> >> To: Ilya Alekseyev <ilyaalekseyev(a)acm.org> >> Cc: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun Guo/China/ >> IBM@IBMCN, "openstack-i18n(a)lists.openstack.org" <openstack- >> i18n(a)lists.openstack.org> >> Date: 2016/03/11 04:37 >> Subject: Re: [Openstack-i18n] Wrong plural formula for russian > > >> >> Hi, >> >> If we fix the plural forms in pot file and push to Zanata, that >> would not affect the statistics. >> >> But I remember last time when we trying to fix this, there are some >> limitation of the pluralform wont update after the file is being >> uploaded once to Zanata. And we have to create a new version with >> fixed pot file and use "merge translation" feature to bring over all >> the translations. >> >> We can do the same thing again and the statistics won't be affected. >> (copied translation doesn't count in as contribution) >> >> I checked and Zanata has the correct form. >> >> nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && >> (n%100<10 || n%100>=20) ? 1 : 2) >> >> --------------------------------------------- >> >> Alex Eng >> Senior Software Engineer >> Globalisation Tools Engineering >> DID: +61 3514 8262 >> Mobile: +614 2335 3457 >> >> Red Hat, Asia-Pacific Pty Ltd >> Level 1, 193 North Quay >> Brisbane 4000 >> Office: +61 7 3514 8100 >> Fax: +61 7 3514 8199 >> Website: www.redhat.com >> >> On Fri, Mar 11, 2016 at 3:00 AM, Ilya Alekseyev <ilyaalekseyev(a)acm.org> >> wrote: >> Daisy, >> >> i remember we fixed this for Liberty. But looks like somewhere wrong >> config or error in script that creating master version. >> How ca we fix it? How i can help with this issue? >> >> Alex, is it possible to fix plural formula ofr version and keep >> statistics safe? >> >> We need to fix it as soon as possible, because 4 plural forms making >> issues for russian translation (empty message, empty buttons, etc, >> as we can seee in Kilo release). >> >> Kind regards, >> Ilya Alekseyev. >> >> С уважением, >> Илья Алексеев >> >> Russian OpenStack Community >> >> 2016-03-10 19:37 GMT+03:00 Akihiro Motoki <amotoki(a)gmail.com>: >> Russian translations in the horizon repo is downloaded from Zanata, >> OpenStack translation platform. >> It seems Zanata has wrong plural configuration. >> >> > Daisy, Alex, >> Could you check Russian configuration in Zanata is correct? >> >> 2016-03-10 22:42 GMT+09:00 Ilya Alekseyev <ilyaalekseyev(a)acm.org>: >> > Dear collegues, >> > >> > i've checked current russian translation in horizon repository and find >> > out >> > that we have wrong plural formula in upstream. >> > >> > https://github.com/openstack/horizon/blob/master/ >> openstack_dashboard/locale/ru/LC_MESSAGES/django.po#L35-L37 >> > >> > There is only 3 plural forms in Russian. >> > And correct formula should be >> > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && >> > (n%100<10 || n%100>=20) ? 1 : 2); >> > >> > Looks like some script is wrong. >> > Does anybody know how to fix it? >> > >> > Kind regards, >> > Ilya Alekseyev >> > >> > _______________________________________________ >> > Openstack-i18n mailing list >> > Openstack-i18n(a)lists.openstack.org >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >

2 1

Wrong plural formula for russian
by Ilya Alekseyev 14 Mar '16

14 Mar '16

Dear collegues, i've checked current russian translation in horizon repository and find out that we have wrong plural formula in upstream. https://github.com/openstack/horizon/blob/master/openstack_dashboard/locale… There is only 3 plural forms in Russian. And correct formula should be nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2); Looks like some script is wrong. Does anybody know how to fix it? Kind regards, Ilya Alekseyev

4 10

[I18n] PTL Candidacy
by Kato, Tomoyuki 13 Mar '16

13 Mar '16

Hello everyone, I'd like to announce my candidacy for I18n PTL. I'm one of the most active translators since July 2013 when I18n team is a just working group, not an official project. Also, I'm one of Japanese coordinators. Japanese translation team is the most active team in I18n team. We sometimes share a few tips from our experience to I18n team. I18n team have spent a very great time for a long time. Especially, after we became an official project, we have became more collaborative in cross-language activity, such as building dashboard translation check site. I appreciate the current I18n PTL Daisy. She made our team become an official project. In the Newton cycle, I'd like to * support dashboard and its plug-ins tranlation into more languages, * facilitate documentation tranlation into more languages, * design and improve translation process, glossary management, translation bug triage process, and so on. Also, I'd like to feedback our experience to the translation system Zanata and cooperate with Zanata and Infra team to improve our translation efficiency. I think user facing contents translation is essential to improve user experience to the people having various language background. I believe I18n activity is necessary for OpenStack to become more and more universal. Best regards, KATO Tomoyuki (katomo)

1 0

[Docs] PTL Candidacy
by Lana Brindley 13 Mar '16

13 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, I am seeking re-election as Documentation PTL for Newton. I have now been the docs PTL for two releases (Liberty and Mitaka), and would love another term in the middle of the alphabet! We've achieved a lot this time around, including an almost complete conversion to RST, quite a few structural overhauls of popular books, and some fundamental toolchain improvements. There is still lots to be done, though, and I would love your support to achieve this in Newton. During Liberty we got the bulk of our books migrated away from Docbook XML and into RST. In Mitaka, we completed that work (with only the Ops Guide remaining to be converted in Newton). For the last couple of releases, we've also had a focus on improving the information architecture of our books, and have now successfully completed overhauls of our most popular books, with the Architecture Guide also well underway. All of these tasks will be carried over to Newton, with many of them finally coming to completion. In Newton, I would also like to address some of the larger issues around the organisation of our documentation suite, making it easier for developers to contribute quality code to our docs, and better welcoming and introducing new big tent projects to the documentation team. At the Mitaka summit in Tokyo, we decided to make a concerted effort to pay down a lot of our tech debt, and one of the main ways we chose to do that was to change the way we handled the DocImpact flag in our bugs. We merged those changes to DocImpact about a month ago now, and it is already having a significant impact on the amount of untriaged bugs outstanding. We're now much more able to keep on top of our bug queue, which is giving us a much greater ability to pay down tech debt. In this vein, we also have put a lot of effort into ensuring new contributors have a better onboarding experience to docs, with the creation of our new Contributor Guide which replaces a lot of old wiki-based content, a great 'get started with docs' campaign at the last Summit (which resulted in a hard copy article in the Summit edition of SuperUser, and Anne and I on SuperUser TV), and a general willingness to respond to questions on the mailing lists and help out new users wherever we find them. In the Liberty release cycle, we closed just over 600 bugs, and we're very close to matching that number for Mitaka, with 505 bugs closed as I write this. Again, we've managed to keep on top of the aging bugs as well, with all bugs older than a year now closed. In the Mitaka release, we managed to close 16 blueprints, which is a massive increase over Liberty's 7. I'm very excited about making the trek to Austin soon for the Newton summit, to catch up with old friends, and hopefully meet some of our newest contributors. Please be sure to stop for a chat if you see me around :) I'd love to have your support for the PTL role for Newton, and I'm looking forward to continuing to grow the documentation team. Thanks, Lana (@loquacities) - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJW5g++AAoJELppzVb4+KUy9LAH/RC5y/gM22qywGZaE2y4hWEc b+xdCxFUuh41l3WJhQ2iRJrnZUjm84doG2eCIcCpJW/OC5udo+2GiQYGmLUH278A uz8Rfglsu/SmDhWZbaIWtiKXo3WedmWzXUbBCV7/+aftphKLMdckD1KAharZZOWq Jqzg56SjWRqzbO++XiciCVwQ+zgoGuzJzYEQ1SsYsAdp/+wdtO2qPORZO1UuoOfz wFFS/OG8O4PsJa3e9KW/kHzDY3Emkz7bhqDcbE6w3HyszC6bEq8lDgmcXtg2SoNn FzjEpoiiAyalncUfo3p+v+7CV/3M/N4nCB2K+VhYO0hIAxPgUMxhrP3jzzq/gSI= =sboQ -----END PGP SIGNATURE-----

1 0

Re: [Openstack-i18n] Wrong plural formula for russian
by Alex Eng 13 Mar '16

13 Mar '16

+1 Daisy --------------------------------------------- Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com On Fri, Mar 11, 2016 at 3:20 PM, Ying Chun Guo <guoyingc(a)cn.ibm.com> wrote: > Thank you for the investigation, Akihiro and Alex. > > Below are the steps we previously used. > We can follow the same steps, just changing "stable" version to "master" > version. > I think the statistic data will not be affected in step 1 to 5. > But, if we delete master-old, the contribution data in master-old will be > removed. > So my suggestion is to do the same steps, and keep master-old version > (mark it as readonly) > till 6 month or 12 month later when the contribution data is not that > important. > > > 1. Create Russian translation files with only the correct header and the > > pluralities translation items. > > 2. Create a new version named as russian-fix > > 3. Upload the source files and the Russian translation files created in > #1 > > to the version russian-fix > > 4. Merge the stable version with version russian-fix > > 5. Rename stable version to stable-old, and rename russian-fix to stable. > > Alex and Akihiro, please confirm my proposal. > Then I can take actions. > > Best regards > Ying Chun Guo (Daisy) > > > Alex Eng <aeng(a)redhat.com> wrote on 2016/03/11 04:36:15: > > > From: Alex Eng <aeng(a)redhat.com> > > To: Ilya Alekseyev <ilyaalekseyev(a)acm.org> > > Cc: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun Guo/China/ > > IBM@IBMCN, "openstack-i18n(a)lists.openstack.org" <openstack- > > i18n(a)lists.openstack.org> > > Date: 2016/03/11 04:37 > > Subject: Re: [Openstack-i18n] Wrong plural formula for russian > > > > Hi, > > > > If we fix the plural forms in pot file and push to Zanata, that > > would not affect the statistics. > > > > But I remember last time when we trying to fix this, there are some > > limitation of the pluralform wont update after the file is being > > uploaded once to Zanata. And we have to create a new version with > > fixed pot file and use "merge translation" feature to bring over all > > the translations. > > > > We can do the same thing again and the statistics won't be affected. > > (copied translation doesn't count in as contribution) > > > > I checked and Zanata has the correct form. > > > > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && > > (n%100<10 || n%100>=20) ? 1 : 2) > > > > --------------------------------------------- > > > > Alex Eng > > Senior Software Engineer > > Globalisation Tools Engineering > > DID: +61 3514 8262 > > Mobile: +614 2335 3457 > > > > Red Hat, Asia-Pacific Pty Ltd > > Level 1, 193 North Quay > > Brisbane 4000 > > Office: +61 7 3514 8100 > > Fax: +61 7 3514 8199 > > Website: www.redhat.com > > > > On Fri, Mar 11, 2016 at 3:00 AM, Ilya Alekseyev <ilyaalekseyev(a)acm.org> > wrote: > > Daisy, > > > > i remember we fixed this for Liberty. But looks like somewhere wrong > > config or error in script that creating master version. > > How ca we fix it? How i can help with this issue? > > > > Alex, is it possible to fix plural formula ofr version and keep > > statistics safe? > > > > We need to fix it as soon as possible, because 4 plural forms making > > issues for russian translation (empty message, empty buttons, etc, > > as we can seee in Kilo release). > > > > Kind regards, > > Ilya Alekseyev. > > > > С уважением, > > Илья Алексеев > > > > Russian OpenStack Community > > > > 2016-03-10 19:37 GMT+03:00 Akihiro Motoki <amotoki(a)gmail.com>: > > Russian translations in the horizon repo is downloaded from Zanata, > > OpenStack translation platform. > > It seems Zanata has wrong plural configuration. > > > > > Daisy, Alex, > > Could you check Russian configuration in Zanata is correct? > > > > 2016-03-10 22:42 GMT+09:00 Ilya Alekseyev <ilyaalekseyev(a)acm.org>: > > > Dear collegues, > > > > > > i've checked current russian translation in horizon repository and > find out > > > that we have wrong plural formula in upstream. > > > > > > https://github.com/openstack/horizon/blob/master/ > > openstack_dashboard/locale/ru/LC_MESSAGES/django.po#L35-L37 > > > > > > There is only 3 plural forms in Russian. > > > And correct formula should be > > > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && > > > (n%100<10 || n%100>=20) ? 1 : 2); > > > > > > Looks like some script is wrong. > > > Does anybody know how to fix it? > > > > > > Kind regards, > > > Ilya Alekseyev > > > > > > _______________________________________________ > > > Openstack-i18n mailing list > > > Openstack-i18n(a)lists.openstack.org > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > >

1 0

Wow!
by Andreas Jaeger 13 Mar '16

13 Mar '16

Habe mir gerade mal Statistiken angesehen. Deutsche Übersetung bei Dashboard ist auf Platz 2 und bei Server auf dem 2. Platz! Klasse! Ein Kommentar noch zu den Prozenten: Wir importieren neu von zanata in die Projekte nur solche Dateien, die mindestens 75 % der Messages übersetzt haben. Angezeigt wird in Zanata per Default als Prozentsatz aber die Wörter, aber das kann man temporär umschalten. Die Logdatein würde ich übrigens nicht übersetzen, die sehen wirklich nur Admins und können zu Verwirrung führen. Die wurden ausgelagert, damit wir ihnen niedrigere Priorität geben können. Gruß 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

What's Up, Doc? 11 March 2016
by Lana Brindley 10 Mar '16

10 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, This week I've been smashing some older bugs from our queue, and can now confirm that as a team we've closed everything older than a year! What a great effort, and a fabulous way to go into our release period. We have less than a month now before release, so I've been briefing our new release managers Brian and Olga, and have also spent some time speaking to various people about what docs will be releasing for Mitaka. Install Guide testing is now well underway, but we can always use more hands, so please consider getting involved. If you need help getting started, please contact Matt Kassawara, or any docs core. == Progress towards Mitaka == 26 days to go! 500 bugs closed so far for this release, which means we're about on par with where we were this time last release. Keep squishing those bugs! Docs Testing * Volunteers required! * https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting Release Managers: We now have two release managers for Mitaka: Brian Moss, and Olga Gusarenko. They'll be making sure we stay on track as we hurtle towards 7 April, and will be backed up by Anne, Andreas, myself, and of course our lovely core team. == The Road to Austin == * Speaker acceptances have now gone out, and the schedule is available: https://www.openstack.org/summit/austin-2016/summit-schedule/#day=2016-04-24 * PTL nominations for Newton have now opened: https://wiki.openstack.org/wiki/PTL_Elections_March_2016. I'm very pleased to announce that I will be submitting my candidacy for docs. * I have requested workrooms and fishbowls for the Austin Design Summit. I'll let you know when we get our allocation. * You should be starting to think about booking travel and accommodation soon! If you need a visa to travel to the United States, there's more info here: https://www.openstack.org/summit/austin-2016/austin-and-travel/#visa == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' No update this week. '''Installation Guide - Matt Kassawara''' No update this week. '''Networking Guide - Edgar Magana''' Progress towards the missing features and new ones for Mitaka. DSCP for QoS section is in good shape: https://review.openstack.org/#/c/273638/ Last Networking Guide meeting: http://eavesdrop.openstack.org/meetings/networking_guide/2016/networking_gu… Still missing a lot of attendence to the IRC meeting but we are happy with more contributions to the guide. Matt provided a short overview on how to contribute during the Neutron mid-cycle sessions '''Security Guide - Nathaniel Dillon''' No update this week. '''User Guides - Joseph Robinson''' User Guide APAC and US meetings this week - discussed merging the CLI reorganization patch, which was merged following the meeting. Becuase of a meetbot error, the APAC meeting did not take place, but I am sending a summary out to the mailing list, which I am still working on. '''Ops and Arch Guides - Shilla Saebi''' No update this week. '''API Docs - Anne Gentle''' No update this week. Bug days: Work on api-site bugs: https://bugs.launchpad.net/openstack-api-site Work on these remaining WADL bugs which have patches: https://review.openstack.org/#/c/288315/ https://review.openstack.org/#/c/283114/ Continue to review and work on bootprint patch. Karin Bradshaw working on CSS updates. '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Pranav Salunke, Roger Luethi''' We merged support for snapshots in the KVM backend. Osbash works now on 32-bit i386 nodes which also makes nested virtualization (creating the whole VM cluster within a VM) possible. There is a new configuration file for users who only want an automated VM cluster setup, but no automated OpenStack installation. Finally, a new feature splits server log files according to cluster build phases, which makes it much easier to identify the origin of a specific log entry. '''Training Guides - Matjaz Pancur''' Enabled automatic bug status resolving at merge (https://review.openstack.org/#/c/283453/) WIP - Upstream training - add toolchain info for trainees (https://review.openstack.org/#/c/286941/) '''Hypervisor Tuning Guide - Joe Topjian''' I included a bunch of links related to NUMA and large memory pages. It'd be nice if the relevant information was pulled from the links and summarized. I also included some information about virtio-scsi. '''UX/UI Docs Guidelines - Linette Williams''' No update this week. == Doc team meeting == Next meetings: The APAC meeting was held this week. You can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-03-09 Next meetings: US: No meeting this week APAC: Wednesday 23 March, 00:30 UTC 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#11_March_2016 - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJW4kjpAAoJELppzVb4+KUyUSEH/iBWAOfRKZd8xEjUUh6roBPY XMeQh13RTBLBftyQoyzgIDenWfnaUeCrcDWlyNdY3jOVsDVQF9q0AkvuuzqXrfUu /LsnqcSHwJO0ervp6z7d0iJ0droUnJf0Qf3h1MMwutcwynRJtHVOsUYMVTLG9Dcw wALqlmxFwukD3GrbQfZ1M8MDGwVMopWU9/GsFNlHnBnbJ6DQFLBylWzGPEUQFR3e x/HAEC/ofNANZ5GqUTroqArNbv12bOTQanBGzIpcqEJ3hNG1c9tUMA3xH8ygLdCG cRoeDA4sCheYn8LWr1eNnw1jx4CAjUiO7d91Tf12c7Wp8XhMSquU18JzZ+g6Rkc= =lGay -----END PGP SIGNATURE-----

1 0

Re: [Openstack-i18n] Zanata Group for server project translations?
by Akihiro Motoki 08 Mar '16

08 Mar '16

2016-03-07 0:08 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Administrators can create groups. > > When you are talking about "server projects", > do you mean projects like nova, glance, keystone, and etc ? Yes. nova and others. We usually use this term in -dev list. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/05/2016 09:32:08 PM: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: "openstack-i18n(a)lists.openstack.org" > <Openstack-i18n(a)lists.openstack.org> >> Date: 03/05/2016 09:34 PM >> Subject: [Openstack-i18n] Zanata Group for server project translations? >> >> Hi Daisy, >> >> Can' t we have Zanata Group for server project translations as well? >> In my understanding, only you can create a Zanata group and I failed >> to catch you in IRC. >> >> Akihiro >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > >

4 4

Re: [Openstack-i18n] To language team coordinators: get ready for Mitaka translation
by Alex Eng 06 Mar '16

06 Mar '16

Daisy, If you're importing po files, the only field it will populate is the "description" field which extract from comment in message. There's no "pos" related field in po file. See the attached file. --------------------------------------------- Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com On Tue, Mar 1, 2016 at 6:05 PM, Ying Chun Guo <guoyingc(a)cn.ibm.com> wrote: > Thank you for the information, Alex. > I know Zanata allows to import glossaries from CSV and po files. > I can see a sample of CSV file, with "description" and "pos" field[1]. > Can you provide us a sample of po file, with "description" and "pos" field > for an entry ? > > Best regards > Ying Chun Guo (Daisy) > [1] > http://docs.zanata.org/en/release/user-guide/glossary/upload-glossaries/ > > > Alex Eng <aeng(a)redhat.com> wrote on 2016/02/29 05:58:23: > > > From: Alex Eng <aeng(a)redhat.com> > > To: "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> > > Cc: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun Guo/China/ > > IBM@IBMCN, Openstack-i18n <openstack-i18n(a)lists.openstack.org> > > Date: 2016/02/29 05:59 > > Subject: Re: [Openstack-i18n] To language team coordinators: get > > ready for Mitaka translation > > > > On Sat, Feb 27, 2016 at 7:08 PM, Kato, Tomoyuki < > kato.tomoyuki(a)jp.fujitsu.com > > > wrote: > > > Beyond this, the current format of PO file for the glossary lacks an > > > essential feature as I described before. There is no way to describe > the > > > context. > > > I wonder how the glossary help translations without the contextual > > > information. > > > As a result, Japanese team is forced to describe contextual information > > > in translated strings. > > > This is the reason we preferred to Wiki style glossary. > > > > > > From the above observation, does it sound a good option to clear the > whole > > > entry of Zanata glossary of a specific language? > > > > FYI, as of Zanata 3.8, we support same source string with unique > > "description" and "pos" field for each glossary entry. > > This will help translator with more context information and able to > > have similar string with different context. > > > > > > > > > --------------------------------------------- > > > > Alex Eng > > Senior Software Engineer > > Globalisation Tools Engineering > > DID: +61 3514 8262 > > Mobile: +614 2335 3457 > > > > Red Hat, Asia-Pacific Pty Ltd > > Level 1, 193 North Quay > > Brisbane 4000 > > Office: +61 7 3514 8100 > > Fax: +61 7 3514 8199 > > Website: www.redhat.com >

2 3

Zanata Group for server project translations?
by Akihiro Motoki 06 Mar '16

06 Mar '16

Hi Daisy, Can' t we have Zanata Group for server project translations as well? In my understanding, only you can create a Zanata group and I failed to catch you in IRC. Akihiro

3 2

Fwd: [openstack-tw] [Hackathon]Call for translator
by Tom Fifield 04 Mar '16

04 Mar '16

FYI - ZH_TW Team is making progress on the First App guide :) -------- Forwarded Message -------- Subject: [openstack-tw] [Hackathon]Call for translator Date: Thu, 3 Mar 2016 22:38:59 +0800 From: Rico Lin <rico.l(a)inwinstack.com> To: openstack-tw(a)lists.openstack.org Dear all we already have 59% of "Write your first app" doc complete thank for a group of hard working student from 臺中科技大學National Taichung University 大家覺的我們有機會在18號前將剩下的部份全部翻譯完畢嗎：） translate.openstack.org/webtrans/Application.seam?project=api-site&iteratio… <http://translate.openstack.org/webtrans/Application.seam?project=api-site&i…> -- Best regards, */Rico Lin/* <http://www.inwinstack.com> 迎棧科技股份有限公司 │ 886-963-612-021 <tel:886-963-612-021> │ rico.l(a)inwinstack.com <mailto:rico.l@inwinstack.com> │ 886-2-7738-6804 <tel:886-2-7738-6804> #7754 │ 新北市220板橋區遠東路3號5樓C室 Rm.C, 5F., No.3, Yuandong Rd., Banqiao Dist., New Taipei City 220, Taiwan (R.O.C)

2 1

What's Up, Doc? 4 March 2016
by Lana Brindley 03 Mar '16

03 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, This week I've been concentrating on getting ready for the release, and I'm very pleased to announce that we now have not one but two release managers for Mitaka. Please welcome Brian and Olga, thanks to you both for stepping up to the challenge! I'm looking forward to working with you both to get this out the door. We also completed the docs core team review, with no changes for this month. Install Guide testing is now well underway, but we can always use more hands, so please consider getting involved. If you need help getting started, please contact Matt Kassawara, or any docs core. == Progress towards Mitaka == 33 days to go! 465 bugs closed so far for this release. There is a global bug smash event next week to try and hit as many Mitaka bugs as possible. You can join an in-person group near you, or participate remotely. Details here: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka Docs Testing * Volunteers required! * https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting API Docs I'm very pleased to announce that Anne and the API docs team have managed to get HTML generation working directly from Swagger now. This is a massive leap forward for the API docs conversion. Well done to everyone involved! Release Managers: We now have two release managers for Mitaka: Brian Moss, and Olga Gusarenko. They'll be making sure we stay on track as we hurtle towards 7 April, and will be backed up by Anne, Andreas, myself, and of course our lovely core team. == The Road to Austin == * The final round of ATC passes have now gone out. * I have requested workrooms and fishbowls for the Austin Design Summit. I'll let you know when we get our allocation. * You should be starting to think about booking travel and accommodation soon! If you need a visa to travel to the United States, there's more info here: https://www.openstack.org/summit/austin-2016/austin-and-travel/#visa == Core Team reviews == I completed the core team review for March this week, and we decided to make no changes. We did, however, have some discussion about the stats we use to determine the core team membership. I currently use the 30 and 90 day russellbryant stats for determining review participation, and Stackalytics for commit participation, with emphasis being on the top 12 participants in each category. Feedback on the core team selection process is, as always, welcome. It is documented here: http://docs.openstack.org/contributor-guide/docs-review.html#achieving-a-co… == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' No update this week. '''Installation Guide - Matt Kassawara''' More patches and testing for Mitaka. '''Networking Guide - Edgar Magana''' No update this week. '''Security Guide - Nathaniel Dillon''' No update this week. '''User Guides - Joseph Robinson''' A patch for the reorganisation is under review - shifting the command line content in the admin user guide to the cloud admin guide. Following this patch merging, the next step is moving down the task list, and completing edits to the content in the Cloud Admin guide to improve the document. '''Ops and Arch Guides - Shilla Saebi''' The work items for the Architecture Design Guide converted to bugs: https://bugs.launchpad.net/openstack-manuals/+bugs?field.tag=arch-guide We still need people to confirm the bugs. Call for volunteers email went out to the ops and docs ML from Devon Boatwright. We are still looking for help, not getting many responses. Considering doing a swarm or work session at the summit in Austin for the Arch guide '''API Docs - Anne Gentle''' Patch fixing three of remaining 7 WADL bugs here: https://review.openstack.org/#/c/283114/ Patch that builds HTML from Swagger files here: https://review.openstack.org/#/c/286659/ This gets us over a big hurdle of making fairy-slipper "feature complete" while also ensuring the migration is complete. Great week, huge shoutout and thanks to Michael Krotscheck for the node/npm solution for building HTML. '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Pranav Salunke, Roger Luethi''' No update this week. '''Training Guides - Matjaz Pancur''' "Getting started" module for Training guides is published (http://docs.openstack.org/draft/training-guides/) Added "Local trainings" chapter to the Upstream training archive (http://docs.openstack.org/upstream-training/upstream-archives.html) cleanup patches (unused extensions, text redundancies and cleanup). Team meetings will be held on 1st and 3rd week in the month. '''Hypervisor Tuning Guide - Joe Topjian''' No update this week. '''UX/UI Docs Guidelines - Linette Williams''' Reviews continue for proposed UI panels in Invision == Doc team meeting == Next meetings: The US meeting was held this week, at the new time. You can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-03-02 Next meetings: APAC: Wednesday 9 March, 00:30 UTC US: Wednesday 16 March, 19:00 UTC ***Note the new time!*** 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#4_March_2016 - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJW2RKeAAoJELppzVb4+KUyiVEH/ROrKbQvJ3VEr1jVMNn5g16O aFu2aNjEd3cOJ50FHkzi0NdsHJoNslFq6NpSEcWdFQihKh5anZeaFA8flO8bKA/L xepUnQjTvcgvZgiREutcQGkowaIqZiUxkXr8YV36So+K8CQwyHOcBfBlcR8hSMRa r2k0o+BA2GjBZuAvjt4P6eIfCNrAA8N2oycXTU0F2j6IIwDoQ23A8uyTuKHrBArQ 8FYeUv31fabqA+jsRZRpYr2QinpyRW+m1xbeYsnh3cXq9QciwEqbdC44d/+MZsJq dOTI2MeUmCKz72Y7ftwPXGuyKcv84RNe/FSRoZWgCdIK3RSdChD/IVoiHtRbtUo= =+XXP -----END PGP SIGNATURE-----

1 0

French team mailing list and IRC channel
by JF Taltavull 03 Mar '16

03 Mar '16

Hello Daisy, The IRC channel #openstack-i18n-fr and the mailing list openstack-i18n-fr(a)lists.openstack.org are up and running :) Best regards, Jean-François Taltavull (jftalta) i18n french team coordinator

1 0

translation team communication, how to create mailing list
by Robert Simai 03 Mar '16

03 Mar '16

Hi, to get back on an older topic, e.g. see http://lists.openstack.org/pipermail/openstack-i18n/2015-September/001380.h… Zanata apparently doesn't have the capabilities to send messages to the translation team (the built in chat is not too helpful) and it doesn't seem realistic to expect such a feature in the near future. Since the German translator team is growing and to have some appropriate forum to discuss language specific issues and agree on standards, I thought about finally managing an email list, something like [Openstack-i18n-DE]. Would anyone know how to request/create an email list on lists.openstack.org? -- Thanks, Robert

3 5

Re: [Openstack-i18n] translation check site local.conf andconfiguraitons
by Akihiro Motoki 02 Mar '16

02 Mar '16

I am not sure the translation check site supports trove/sahara-dashboard for mitaka translation, so I decided not to push my current version of local.conf to the review of puppet-translation_checksite. You can freely pull my local.conf to the transaltion check site configuration! My latest version of local.conf is found at [1]. It supports trove-dashboard, sahara-dashboard and various neutron configurations. I also updated ansible-i18n-playbook [2] because it is referred to by the effort of the translation check site, but this repository will be deleted soon after the translation check site launches. [1] and [2] is used in my current developments. Akihiro [1] https://github.com/amotoki/ansible-playbook/tree/master/roles/devstack/temp… [2] https://github.com/amotoki/ansible-i18n-devstack/blob/master/roles/i18n-dev… 2016-02-24 16:55 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > I support to use puppet-translation_checksite to store a newest and latest > workable local.conf. > For various versions of local.conf, they mostly are used as references. > I think personal github is good to keep them. > > Thank you, Akihiro. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2016/02/24 00:32:42: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: SungJin Kang <gang.sungjin(a)gmail.com> >> Cc: "openstack-i18n(a)lists.openstack.org" >> <Openstack-i18n(a)lists.openstack.org> >> Date: 2016/02/24 00:34 >> Subject: Re: [Openstack-i18n] translation check site local.conf and >> configuraitons >> > >> I just remembered puppet-translation_checksite repo [1] is created to >> maintain the infra configuration for our translation check site. >> >> BTW, it sounds good to use i18n repo to share various contents >> including local.conf. >> We have various potential configuration options, so it is nice to have >> docs or files in our repo :-) >> >> [1] http://git.openstack.org/cgit/openstack-infra/puppet- >> translation_checksite/ >> >> 2016-02-24 1:22 GMT+09:00 SungJin Kang <gang.sungjin(a)gmail.com>: >> > HI, Akihiro. >> > >> > I things using i18n repo [1] >> > >> > Make directory /config? or /devstack/version? anythings. >> > >> > Thanks, >> > Sungjin >> > >> > [1]: http://git.openstack.org/cgit/openstack/i18n/ >> > >> > 2016-02-24 0:58 GMT+09:00 Akihiro Motoki <amotoki(a)gmail.com>: >> >> >> >> Hi, >> >> >> >> Thanks for working on translation check site as the upstream. >> >> >> >> Where is the configuration files maintained in OpenStack repositories? >> >> I can share my local.conf with GitHub gist or in other ways, but it is >> >> not the OpenStack way. >> >> We use gerrit to share everything. I would like to follow it. >> >> >> >> I promised to provide devstack local.conf which enables almost all >> >> features for the check site. >> >> I now have local.conf compatible with Liberty OpenStack dashboard >> >> ('compatible' means Trove and Sahara horizon plugins are supported). >> >> >> >> To support more horizon plugins beyond sahara/trove dashboard for >> >> translations, >> >> everyone can push a new version of local.conf once he/she finds and >> >> confirms >> >> a right configuration. There are many horizon plugins, so it is not >> >> reasonable to >> >> depend devstack configurations on a small group of peoples. >> >> >> >> Thanks, >> >> 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 >> >

2 3

IRC meeting tomorrow
by Ying Chun Guo 02 Mar '16

02 Mar '16

Hi, team We will have IRC meeting tomorrow at UTC 0600 in #openstack-meeting. The agenda in my mind are: * Kick off Mitaka translation * Open discussions If you have more topics, feel free to add. Thank you. Best regards Ying Chun Guo (Daisy)

3 3

Re: [Openstack-i18n] To language team coordinators: get ready for Mitaka translation
by Akihiro Motoki 02 Mar '16

02 Mar '16

Do you want we have out-of-date Japanese glossary in i18n repo? I am not a fan of this but am okay if you want. 2016-03-02 22:05 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > I hope you can agree to abandon it. > We can work on the improvement after the po format for new glossary > feature is clear. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/02/2016 09:01:12 PM: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: Ying Chun Guo/China/IBM@IBMCN >> Cc: Tomoyuki KATO <tomo(a)dream.daynight.jp>, "openstack- >> i18n(a)lists.openstack.org" <openstack-i18n(a)lists.openstack.org> >> Date: 03/02/2016 09:02 PM >> Subject: Re: [Openstack-i18n] To language team coordinators: get >> ready for Mitaka translation >> >> Daisy, >> >> What should I do for https://review.openstack.org/285725 ? >> Should abandon it? >> >> 2016-03-02 19:05 GMT+09:00 Akihiro Motoki <amotoki(a)gmail.com>: >> > Daisy and Tomo, >> > >> > Thanks for dropping Japanese glossaries (+ follow-up). >> > >> > We Japanese team are happy to re-join the standard way of I18n team >> > once we support contextual information. >> > It was not an easy choice, but from our discussion one-to-one mapping >> > from the source lang to Japanese does not work. >> > >> > Akihiro >> > >> > 2016-03-01 22:45 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> >> >> >> Hi, KATO >> >> >> >> I have deleted Japanese glossaries. >> >> You can check now. >> >> >> >> Best regards >> >> Ying Chun Guo (Daisy) >> >> >> >> >> >> >> >> ----- Original message ----- >> >> From: KATO Tomoyuki <tomo(a)dream.daynight.jp> >> >> To: Ying Chun Guo/China/IBM@IBMCN >> >> Cc: Openstack-i18n <openstack-i18n(a)lists.openstack.org> >> >> Subject: Re: [Openstack-i18n] To language team coordinators: get > ready for >> >> Mitaka translation >> >> Date: Tue, Mar 1, 2016 7:21 PM >> >> >> >> Hi Daisy, >> >> >> >>> Thank you for the input, Akihiro and Kato. >> >>> >> >>> I'm not strict in local communication method and IRC ID. >> >>> If you have clearly documented them in your team wiki, that's fine. >> >> >> >> Already enough clear in wiki, >> >> but only in Japanse :) because of local communication method. >> >> >> >>> As to the glossary, I still think git repository is better than >> >>> wiki to store glossaries. Git repo has strict control, while wiki >> >>> has no controls at all. Wiki is used for frequently update purpose. >> >>> After it turns to mature, Git repo is good to store. >> >>> And, using pot/po file can make all translation teams to easily > follow the >> >>> same glossary list. >> >> >> >> Yeah, I myself am generally agree to managing glossary on git > repository. >> >> But, as of now, it doesn't meet the requirements from Japanese team > fully. >> >> We need a little more work. >> >> >> >>> I understand Japanese glossaries are out of date and your team don't >> >>> like the current one in Zanata. If that's your team decision, I'm OK >> >>> to delete it from Zanata. >> >> >> >> I think so. It's Japanese team dicision at now. >> >> >> >> Thanks, >> >> KATO Tomoyuki >> >> >> >>> Thoughts? >> >>> >> >>> Best regards >> >>> Ying Chun Guo (Daisy) >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> 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] French team irc channel
by JF Taltavull 01 Mar '16

01 Mar '16

On 01/03/2016 14:46, Ying Chun Guo wrote: > I think #openstack-i18n-fr is good. So, let's go for it. > Do you need me to submit the patch to create this IRC channel ? Thanks Daisy,I will do it by myself. I'll let you know if something goes wrong. > Best regards > Ying Chun Guo (Daisy) > > ----- Original message ----- > From: JF Taltavull <jftalta(a)gmail.com> > To: Ying Chun Guo/China/IBM@IBMCN > Cc: Openstack-i18n Openstack-i18n > <openstack-i18n(a)lists.openstack.org>, Maxime Coquerel > <max.coquerel(a)gmail.com>, Safouen Benhadj <safouen.benhadj(a)gmail.com> > Subject: French team irc channel > Date: Tue, Mar 1, 2016 7:08 PM > Hi Daisy, > > In order to be more OpenStack compliant and more open, the i18n french > team would like to stop using Slack and start to communicate > through an > IRC channel. > > What would you think of creating a new channel like #openstack-i18n-fr > or #openstack-i18n-french-fr ? > > > Best regards > Jean-François Taltavull (jftalta) > >

1 0

French team irc channel
by JF Taltavull 01 Mar '16

01 Mar '16

Hi Daisy, In order to be more OpenStack compliant and more open, the i18n french team would like to stop using Slack and start to communicate through an IRC channel. What would you think of creating a new channel like #openstack-i18n-fr or #openstack-i18n-french-fr ? Best regards Jean-François Taltavull (jftalta)

2 1

Translation priority for Mitaka
by KATO Tomoyuki 01 Mar '16

01 Mar '16

Hi team, It's time to update our translation priority [1]. Here is my draft as high priority. Any comments are welcome. OpenStack Dashboard - Horizon - Authorization Page - Essential Plug-ins [TBD] Documentation [2] - Installation Guide - End User Guide - API Guide [1] https://translate.openstack.org/ [2] https://wiki.openstack.org/wiki/I18nTeam/docs-translation Thanks, KATO Tomoyuki

3 6

Closing Liberty translations?
by Andreas Jaeger 29 Feb '16

29 Feb '16

Since Mitaka translations start next week, I propose we close the Liberty translations now as discussed last autumn. How should we do this? Is there a need to keep the liberty branches for some time as read-only? Or should we delete them directly? 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

8 16

What's Up, Doc? 26 Feb 2016
by Lana Brindley 25 Feb '16

25 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, This week I've been working on code reviews and closing some of our oldest bugs from the bug queue. I've also updated the docs-specs core team list to reflect some recent changes to the Speciality Team leads, and doing some general prep work for the Mitaka release. We are now well and truly ready to start testing the Install Guide. If you need help getting started, please contact Matt Kassawara, or any of your friendly core team members :) == Progress towards Mitaka == 40 days to go! 445 bugs closed so far for this release. There is a global bug smash event coming up March 7-9 to try and hit as many Mitaka bugs as possible. You can join an in-person group near you, or participate remotely. There are still plenty of docs bugs that can be attended to. Details here: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka Docs Testing * Volunteers required! * https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting RST Conversions * All planned RST conversions are now complete! Reorganisations * Arch Guide: really needs a last minute push to get this complete before Mitaka. If you can help out, it would be greatly appreciated! ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * User Guides ** https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… ** Contact the User Guide Speciality team: https://wiki.openstack.org/wiki/User_Guides DocImpact * Is now complete == The Road to Austin == * The final round of ATC passes should be going out shortly. * I have now requested workrooms and fishbowls for the Austin Design Summit. I'll let you know when we get our allocation. * There is a plan to separate the Design Summit from the main conference after Barcelona. I strongly suggest you read the thread on the dev mailing list, if you haven't done so already: http://lists.openstack.org/pipermail/openstack-dev/2016-February/087161.html * You should be starting to think about booking travel and accommodation soon! If you need a visa to travel to the United States, there's more info here: https://www.openstack.org/summit/austin-2016/austin-and-travel/#visa == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' No update this week. '''Installation Guide - Matt Kassawara''' Continue updating the guide for Mitaka using primarily RDO milestone 3 packages. Review patch that adds manila to the guide. Review patch that adds magnum to the guide. '''Networking Guide - Edgar Magana''' No update this week. '''Security Guide - Nathaniel Dillon''' No update this week. '''User Guides - Joseph Robinson''' Team successfully moved across dashboard content from the Admin User Guide to the Cloud Admin guide. Team is preparing to move the command line content, and then continue to edit the Cloud Admin guide over the next week. '''Ops and Arch Guides - Shilla Saebi''' The work items for the Architecture Design Guide have been converted to bugs: https://bugs.launchpad.net/openstack-manuals/+bugs?field.tag=arch-guide We need people to confirm the bugs, so we can start working on them. Call for volunteers email went out to the ops and docs ML from Devon Boatwright. We are still looking for help, not getting many responses. Architecture guide reorganization is underway. We have a drafts repo in openstack-manuals, feel free to ping Shilla or Darren Chan if you are interested in helping out. Considering doing a swarm or work session at the summit in Austin for the Arch guide '''API Docs - Anne Gentle''' Check for API migration bugs: https://bugs.launchpad.net/openstack-api-site/+bugs?field.tag=migration There are five bugs remaining. Look at the infra spec if you're interested in how we'll build docs with Swagger files. https://review.openstack.org/#/c/276484/ I'm investigating using this tool so that we replace flat HTML files built from WADL with flat HTML files built from Swagger. https://github.com/nknapp/bootprint-openapi '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Pranav Salunke, Roger Luethi''' Continued fixes to KVM backend and the library functions. Working on creating a webpage for training-labs. https://review.openstack.org/#/c/281713/ https://review.openstack.org/#/c/281721/ https://review.openstack.org/#/c/281367/ Hosting an additional meeting to get our new member on-board and some general discussion. '''Training Guides - Matjaz Pancur''' No update this week. '''Hypervisor Tuning Guide - Joe Topjian''' No update this week. '''UX/UI Docs Guidelines - Linette Williams''' Reviews continue for proposed panels in Invision. Enhancement in UI content guidelines complete for text and icon formatting recommendations (http://docs.openstack.org/contributor-guide/ui-text-guidelines.html) == Doc team meeting == Next meetings: The APAC meeting attempted to be held this week, but failed to meet quorum. Next meetings: US: Wednesday 2 March, 19:00 UTC ***Note the new time!*** APAC: Wednesday 9 March, 00:30 UTC 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#26_February_2016 - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWz9fuAAoJELppzVb4+KUycvYIAJcS46IEaJ10izihei5rFTC3 Y90og8sCTOBTtD36L/la4EQEb33gEzozvOfJlN+nXBbyI1J85q5Bbaxhvmt6WgVy 8lS7hGS8RD74caYM2Hyfby8LHfNXlnXDO9NKGBy10RCqsLMw5sgcNcnA0r5IcwVx OrWOSMwcA/T0oJybSeKrgnaUDwXFwaPpZP4LGGblJrw2+WI7TamxgYEBYG5fumWo FVyAaswBdu1+zA+bCN6KwtbhfbM0VYpQeAuafE8GMYXqeiuVdvTu67z4S4bQUnR2 1JsADOBi77i7AyzP9OknvcGTjxuwXzWopvSi01si16mzQ1CAtdimDej4lyaSJ1Q= =DM9Z -----END PGP SIGNATURE-----

1 0

Planning I18n sessions in Austin summit
by Ying Chun Guo 25 Feb '16

25 Feb '16

Hello, team I'm planning I18n session in Austin summit now. I have planned two sessions: 1. A 40 minutes working session to discuss translation processes and tools. 2. A half-day contributors meetup If you have other topics to discussion and want to organize a specific i18n session, please reply this email. Thank you. Best regards Ying Chun Guo (Daisy)

2 1

Re: [Openstack-i18n] Closing Liberty translations?
by Andreas Jaeger 24 Feb '16

24 Feb '16

On 2016-02-24 09:29, Ying Chun Guo wrote: > If we delete them, translation memory and translators contribution > statistic data will be affected. Really? Interesting. Alex, can you explain what deletion of a branch will do to the stats and memory, please? > So I don't support deleting. > I think we mark them as read only. > > If no objections, we can do it by the end of this week. Fine by me, I can work on the infra change, Andreas > Best regards > Ying Chun Guo (Daisy) > > > Andreas Jaeger <aj(a)suse.com> wrote on 2016/02/24 16:16:37: > >> From: Andreas Jaeger <aj(a)suse.com> >> To: "openstack-i18n(a)lists.openstack.org" > <openstack-i18n(a)lists.openstack.org> >> Date: 2016/02/24 16:18 >> Subject: [Openstack-i18n] Closing Liberty translations? >> >> Since Mitaka translations start next week, I propose we close the >> Liberty translations now as discussed last autumn. >> >> How should we do this? >> >> Is there a need to keep the liberty branches for some time as read-only? >> Or should we delete them directly? >> >> 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 >> >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > -- 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

translation check site local.conf and configuraitons
by Akihiro Motoki 23 Feb '16

23 Feb '16

Hi, Thanks for working on translation check site as the upstream. Where is the configuration files maintained in OpenStack repositories? I can share my local.conf with GitHub gist or in other ways, but it is not the OpenStack way. We use gerrit to share everything. I would like to follow it. I promised to provide devstack local.conf which enables almost all features for the check site. I now have local.conf compatible with Liberty OpenStack dashboard ('compatible' means Trove and Sahara horizon plugins are supported). To support more horizon plugins beyond sahara/trove dashboard for translations, everyone can push a new version of local.conf once he/she finds and confirms a right configuration. There are many horizon plugins, so it is not reasonable to depend devstack configurations on a small group of peoples. Thanks, Akihiro

4 4

Document your language team communication method in the wiki
by Ying Chun Guo 22 Feb '16

22 Feb '16

Hello, team According to the Mitaka dev schedule[1], the community will reach "soft string freeze" in Feb 29-4. We will start Mitaka translation at that time. In order to well collaboration among translator team, lower the barrier to new translators, we need good communication within each language team in the local language. So I hope each language team can have a clear communication method and document the method in the team wiki page.[2] The communication method can be openstack-i18n, if the language team don't want to create a new one. It can be a separate IRC channel other than openstack-i18n, for example, openstack-i18n-zh-cn. It can be a local communication method. Whatever it is, I'd like coordinators clearly document in the team wiki page. We can work well together with good communications. Thank you. Best regards Ying Chun Guo (Daisy) [1] http://releases.openstack.org/mitaka/schedule.html [2] https://wiki.openstack.org/wiki/I18nTeam/team

1 0

Fwd: [openstack-dev] [Horizon][Trove][Sahara] Horizon-Trove/Sahara External Repository
by Akihiro Motoki 19 Feb '16

19 Feb '16

Hi team, Forwarded to i18n list. trove-dashaboard and sahara-dashboard are now ready for translation. Translations for horizon plugins are now working well I believe. If you have any troubles, let me know. One thing to note. If your language team made a lot of translations on Trove and Sahara dashboard in Liberty, you can upload it for Mitaka translations. I already did this for Japanese. Akihiro ---------- Forwarded message ---------- From: Akihiro Motoki <amotoki(a)gmail.com> Date: 2016-02-19 11:50 GMT+09:00 Subject: Re: [openstack-dev] [Horizon][Trove][Sahara] Horizon-Trove/Sahara External Repository To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev(a)lists.openstack.org> Cc: Vince Brunssen <brunssen(a)us.ibm.com> Hi, > Horizon still have some things we need to tidy up on our end to make sure we > have full support for testing and localization for external plugins. I am pleased to announce that translations of trove-dashboard and sahara-dashboard now work for the master branch. We have the parity to Liberty release :-) Thanks Andreas and folks involved in this effort. Akihiro 2015-12-04 6:44 GMT+09:00 Thai Q Tran <tqtran(a)us.ibm.com>: > Hello Trovers and Horizoneers, > > The intention of this email is to get everyone on the same page so we are > all aware of what is going on. As many of you are probably already aware, > Horizon is moving toward the plugin model for all of its dashboards > (including existing dashboards). This release cycle, we are aiming to move > Sahara and Trove into their own repository with joint ownership of the > respective project. I have spoken to interested parties, Craig, and David > about it and we are all in agreement. Ideally, this should help speed up the > review process for Trove, as you now own part of the code and ownership. > > Horizon still have some things we need to tidy up on our end to make sure we > have full support for testing and localization for external plugins. We > expect this to get resolve within the next few weeks. Work on excising the > Trove code will begin this week so expect a patch for that soon! It would be > ideal if we can merge existing Trove code before the excision happens. David > has agreed to let these patches merge with one core vote if we have enough > Trovers reviewing/reverifying them. So please help us help you. > > David and Craig, if I left anything else out, feel free add to this. > Otherwise, have a good xmas everyone. Looking to working with you all in the > coming weeks. > > Regard, > Thai (tqtran) > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >

2 1

What's Up, Doc? 19 Feb 2016
by Lana Brindley 18 Feb '16

18 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, This week I've been focusing on general housekeeping duties as we prepare to rush headlong into the release. I've cleaned up the blueprints list, and also been burning through the oldest bugs in our queue. I'm very pleased to report that the overall number of bugs has reduced dramatically in the past month or two, and the number of untriaged bugs is holding steady at a much lower rate than previously. I think this probably has a lot to do with the DocImpact changes we made at the beginning of the year, so it's very gratifying to see some solid improvement starting to filter through. In other news, thanks to all those people who helped us with locating pre-release packages for the Install Guide. Please feel free to begin testing! The more people we have testing, the better and more accurate our docs will be, which helps everyone. == Progress towards Mitaka == 47 days to go! 417 bugs closed so far for this release. There is a global bug smash event coming up March 7-9 to try and hit as many Mitaka bugs as possible. You can join an in-person group near you, or participate remotely. There are still plenty of docs bugs that can be attended to. Details here: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka Docs Testing * Volunteers required! * https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting RST Conversions * All planned RST conversions are now complete! Reorganisations * Arch Guide: really needs a last minute push to get this complete before Mitaka. If you can help out, it would be greatly appreciated! ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * User Guides ** https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… ** Contact the User Guide Speciality team: https://wiki.openstack.org/wiki/User_Guides DocImpact * Is now complete == The Road to Austin == * ATC passes are going out now, so keep an eye on your inbox for your discount code if you haven't received yours yet. * Talk voting is now closed * You should be starting to think about booking travel and accommodation soon! If you need a visa to travel to the United States, there's more info here: https://www.openstack.org/summit/austin-2016/austin-and-travel/#visa == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' No update this week. '''Installation Guide - Matt Kassawara''' Testing Mitaka milestone 3 using RDO packages and submitting patches for review. Lead of the install guide changed from Christian Berendt to Matt Kassawara. '''Networking Guide - Edgar Magana''' No update this week. '''Security Guide - Nathaniel Dillon''' No update this week. '''User Guides - Joseph Robinson''' The new User Guide team meetings are a success. We now have more contributors, and are discussing doc editing, new content, and Information Architecture of the User Guides. '''Ops and Arch Guides - Shilla Saebi''' Architecture guide reorganization is underway. We have a drafts repo in openstack-manuals, feel free to ping Shilla or Darren Chan if you are interested in helping out. Considering doing a swarm or work session at the summit in Austin for the Arch guide. Operations guide RST migration pending - conversations still happening to see which route we'll take. Still deciding if the ops guide should have another revision or edition, see ML e-mails. Call for volunteers email went out to the ops and docs ML from Devon Boatwright. We are looking for help! There is a global OpenStack bug smash scheduled for the Mitaka release in March. Details can be found here: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka We're looking for people to specifically help with the Architecture Guide, which is currently going through a reorganization. Here is the link for more details: https://wiki.openstack.org/wiki/Architecture_Design_Guide_work_items If you are interested in helping out, more detail s can be found about our team and our meetings here: https://wiki.openstack.org/wiki/Documentation/OpsGuide '''API Docs - Anne Gentle''' http://lists.openstack.org/pipermail/openstack-docs/2016-February/008286.ht… Swagger files now available at http://developer.openstack.org/draft/swagger/ '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Pranav Salunke, Roger Luethi''' Fixing various things in training-labs cluster for VirtualBox and KVM backends. Improving workflow, configuration and making the library scripts nicer. Adding training-labs landing page (WIP). Summit related work. Some minor improvements. '''Training Guides - Matjaz Pancur''' No update this week. '''Hypervisor Tuning Guide - Joe Topjian''' No update this week. '''UX/UI Docs Guidelines - Linette Williams''' Enhancement to UI content guidelines underway. Expect a new review shortly that covers icons and text formatting. If interested or have questions, contact Linette or Piet Kruithof. == 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-02-14 Next meetings: APAC: Wednesday 24 February, 00:30 UTC US: Wednesday 2 March, 14:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… Note that there is currently discussion about moving the US meeting to 20:00 UTC. A patch is open to change this, with ongoing discussion about finding a meeting room: https://review.openstack.org/#/c/271361/ - -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#19_February_2016 - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWxpUQAAoJELppzVb4+KUyM5IIAKXT4U1SDq8K1+3u41qchjRe tXx3DCHp+O70krBFP+b6xaYXsuIwd6G4iroUXtl0RodlNAxdBjFf82fnpTlt/sz9 tjlST4nt/Z93shaA5b0AkOzEKJhoHCyH0ucq2GCQ81P5mEM3ZkFOYsEjdQjckPhu fc8yvbgjo1Dvxjk6/bEV6c1hroEqLVrzhpd9jstefA/1ATTCg3hR/IWQ9cXscMn0 8qutBYibhFcXzcCVj4/aafjUH+1punMgGeb2KcjrmA0z345WcmS4+IWR4NZrCiMg WWEKbFT8MvGuLEU79KNs+cZBWA+TQnlD2d1fsuCHFKU/eqFeyPmc3P/tI9YM7Jo= =2AkG -----END PGP SIGNATURE-----

1 0

Re: [Openstack-i18n] [stable][i18n] What is the backport policy on i18n changes?
by Kato, Tomoyuki 18 Feb '16

18 Feb '16

> hmm, I think the policy should depends on projects. > For projects which don't have active translations, I think it's OK to backport. > For projects which have active translations, "Exception procedure" of StringFreeze could help. > Translators need to be notified for the changes. > > If you don't know whether the project has active translations or not, > "Exception procedure" can help, anyway. +1 KATO Tomoyuki > Best regards > Ying Chun Guo (Daisy) > > > Matt Riedemann <mriedem(a)linux.vnet.ibm.com> wrote on 2016/02/18 08:16:26: > > > From: Matt Riedemann <mriedem(a)linux.vnet.ibm.com> > > To: "OpenStack Development Mailing List (not for usage questions)" > > <openstack-dev(a)lists.openstack.org>, openstack-i18n(a)lists.openstack.org > > Date: 2016/02/18 08:18 > > Subject: [Openstack-i18n] [stable][i18n] What is the backport policy > > on i18n changes? > > > > I don't think we have an official policy for stable backports with > > respect to translatable string changes. > > > > I'm looking at a release request for ironic-inspector on stable/liberty > > [1] and one of the changes in that has translatable string changes to > > user-facing error messages [2]. > > > > mrunge brought up this issue in the stable team meeting this week also > > since Horizon has to be extra careful about backporting changes with > > translatable string changes. > > > > I think on the server side, if they are changes that just go in the > > logs, it's not a huge issue. But for user facing changes, should we > > treat those like StringFreeze [3]? Or only if the stable branches for > > the given project aren't getting translation updates? I know the server > > projects (at least nova) is still get translation updates on > > stable/liberty so if we do backport changes with translatable string > > updates, they aren't getting updated in stable. I don't see anything > > like that happening for ironic-inspector on stable/liberty though. > > > > Thoughts? > > > > [1] https://review.openstack.org/#/c/279515/ > > [2] https://review.openstack.org/#/c/279071/1/ironic_inspector/process.py > > [3] https://wiki.openstack.org/wiki/StringFreeze

1 0

[stable][i18n] What is the backport policy on i18n changes?
by Matt Riedemann 18 Feb '16

18 Feb '16

I don't think we have an official policy for stable backports with respect to translatable string changes. I'm looking at a release request for ironic-inspector on stable/liberty [1] and one of the changes in that has translatable string changes to user-facing error messages [2]. mrunge brought up this issue in the stable team meeting this week also since Horizon has to be extra careful about backporting changes with translatable string changes. I think on the server side, if they are changes that just go in the logs, it's not a huge issue. But for user facing changes, should we treat those like StringFreeze [3]? Or only if the stable branches for the given project aren't getting translation updates? I know the server projects (at least nova) is still get translation updates on stable/liberty so if we do backport changes with translatable string updates, they aren't getting updated in stable. I don't see anything like that happening for ironic-inspector on stable/liberty though. Thoughts? [1] https://review.openstack.org/#/c/279515/ [2] https://review.openstack.org/#/c/279071/1/ironic_inspector/process.py [3] https://wiki.openstack.org/wiki/StringFreeze -- Thanks, Matt Riedemann

3 2

IRC meeting today
by Ying Chun Guo 17 Feb '16

17 Feb '16

Hi, team We will have IRC meeting today at UTC 1300 in #openstack-meeting. The agenda in my mind are: * Follow up with translation check website * Get ready for Mitaka translation * Open discussions If you have more topics, feel free to add. Best regards Ying Chun Guo (Daisy)

1 0

Zanata 3.8 available
by Carlos Munoz 14 Feb '16

14 Feb '16

Hi All, Just a heads-up that Zanata 3.8.2 has been released and is ready for installation (See: https://github.com/zanata/zanata-server/releases) Please let us know if you want to do the upgrade and need any assistance. Regards, Carlos -- Carlos A. Muñoz Software Engineering Supervisor Globalization Red Hat

6 8

What's Up Doc? 12 Feb 2016
by Lana Brindley 11 Feb '16

11 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, This week has been all about the Install Guide. We're locating pre-release packages now so we can begin testing in about two weeks' time. Please consider being a tester for this release. Even if you've never done it before, it's a great way to improve your OpenStack knowledge, and the more people we have testing, the better and more accurate our docs will be, which helps everyone. We're also starting to see a little more action in the lead up to the Austin Summit. ATC passes are going out, and the talk sessions are now open for voting: https://www.openstack.org/summit/austin-2016/vote-for-speakers/ == Progress towards Mitaka == 54 days to go! 389 bugs closed so far for this release. Docs Testing * Volunteers required! * https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting RST Conversions * All planned RST conversions are now complete! Reorganisations * Arch Guide: really needs a last minute push to get this complete before Mitaka. If you can help out, it would be greatly appreciated! ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * User Guides ** https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… ** Contact the User Guide Speciality team: https://wiki.openstack.org/wiki/User_Guides DocImpact * Is now complete == The Road to Austin == * ATC passes are going out now, so keep an eye on your inbox for your discount code if you haven't received yours yet. * Don't forget to vote on your favourite talks: https://www.openstack.org/summit/austin-2016/vote-for-speakers/ == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' Minor updates to the corosync/pacemaker, rabbitmq clusters setup guides '''Installation Guide - Christian Berendt''' Mitaka Installation guide changes spec: https://review.openstack.org/#/c/274231/ Testing beginning, require packages: https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting '''Networking Guide - Edgar Magana''' Move the IRC meeting agenda to etherpad: https://etherpad.openstack.org/p/docnetworkingteam-agenda. Important Commits: DSCP addition to advanced qos guide: https://review.openstack.org/#/c/273638/ Add networking guide to Contributors Section: https://review.openstack.org/#/c/278330/ Last IRC Meeting Notes: http://eavesdrop.openstack.org/meetings/networking_guide/2016/networking_gu… '''Security Guide - Nathaniel Dillon''' Continuing bugfixes and beginning Networking review (thanks to all Neutron contributors!) '''User Guides - Joseph Robinson''' Held First US/EU Meeting, which was 1 and a 1/2 hours before the APAC meeting (Need to reserve the meeting time). Discussed Reorg- High Priority step - moving Dashboard content from the Admin Guide to the Cloud Admin Dashboard Chapter. '''Ops and Arch Guides - Shilla Saebi''' Architecture guide reorganization is underway. We have a drafts repo in openstack-manuals, feel free to ping Shilla or Darren Chan if you are interested in helping out. Considering doing a swarm or work session at the summit in Austin for the Arch guide. Operations guide RST migration pending - conversations still happening to see which route we'll take. Still deciding if the ops guide should have another revision or edition, see ML emails. '''API Docs - Anne Gentle''' No update this week. '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Pranav Salunke, Roger Luethi''' We reviewed and merged several patches: bug fixes, refactoring and some code to help with debugging. '''Training Guides - Matjaz Pancur''' No update this week. '''Hypervisor Tuning Guide - Joe Topjian''' No update this week. '''UX/UI Docs Guidelines - Linette Williams''' No update this week. == Doc team meeting == Next meetings: The APAC meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-02-10 Next meetings: US: Wednesday 17 February, 14:00 UTC APAC: Wednesday 24 February, 00:30 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… Note that there is currently discussion about moving the US meeting to 20:00 UTC. A patch is open to change this, with ongoing discussion about finding a meeting room: https://review.openstack.org/#/c/271361/ - -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#12_February_2016 - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWvWWOAAoJELppzVb4+KUyadwIAIzWAp7pJChEUmd6joi4GHig OLuvC3nsD6NnjW4qtK6OHdPklZQ6nN8JgNGhbnbBWhmO6/Pk4ulk4TUl5ENtYPxJ hCzQ3OKcgrj+Edb08mk7ck0uCXDQCnopDQfphNFVTObRWw6dpEBbWQBiy0zy0rsX rbp9P+TBOpbPHRgVoI/IvLps/lnlzYQM5QX+kBq0EdG6lG3jU1jDz6Lc3s8onZUV kim0xvw8Kq+l8ziJaf5UZ62ybKJeg/quhffvblVU0iU20m1sNpK6ockjR5miIJWt pSFgE1O4/AERn5/8lH72Nzm+2BuLYoxN749luRHU3agoewFxNdvpch0V7IdSv5c= =gytH -----END PGP SIGNATURE-----

1 0

French install guides for Liberty
by KATO Tomoyuki 10 Feb '16

10 Feb '16

Hi team, French team has good progress on install guides for Liberty translation. Nice work, French team! http://docs.openstack.org/liberty/fr/install-guide-obs/ http://docs.openstack.org/liberty/fr/install-guide-rdo/ http://docs.openstack.org/liberty/fr/install-guide-ubuntu/ Also, the guides will be linked from http://docs.openstack.org/draft/draft-index.html soon. At now, we have many translated docs as draft. If you think ready to publish, feel free to move them into public web pages. Regards, KATO Tomoyuki

1 0

bug squashing
by Kato, Tomoyuki 09 Feb '16

09 Feb '16

Hi team, We have 10 open bugs at now! 6 bugs looks like simplified-chinese traslation bugs. If you have time, please take a look at: https://bugs.launchpad.net/openstack-i18n/ Regards, KATO Tomoyuki

1 0

zh_CN Install Guide for Liberty broken
by Andreas Jaeger 07 Feb '16

07 Feb '16

Looking at today's import, I see for zh_CN lots of warnings - but none for other languages: http://logs.openstack.org/35/271735/1/check/gate-openstack-manuals-tox-chec… These warnings indicate a wrong breakage of the sphinx syntax. Could the zh_CN team look at these, please? 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

3 2

[Bug 1542487] extraneous spaces in some files in Glance translations
by Kato, Tomoyuki 07 Feb '16

07 Feb '16

Hi Italian team, Korean team Please take a look at the bug report. > -----Original Message----- > Public bug reported: > > Left comments in the files on this review: > https://review.openstack.org/#/c/276056/2 > > The two files affected are: > * glance/locale/it/LC_MESSAGES/glance.po > * glance/locale/ko_KR/LC_MESSAGES/glance.po > > ** Affects: openstack-i18n > Importance: Undecided > Status: New > > -- > Title: > extraneous spaces in some files in Glance translations > > Status in openstack i18n: > New > > Bug description: > Left comments in the files on this review: > https://review.openstack.org/#/c/276056/2 > > The two files affected are: > * glance/locale/it/LC_MESSAGES/glance.po > * glance/locale/ko_KR/LC_MESSAGES/glance.po

1 0

What's Up, Doc? 6 Feb 2016
by Lana Brindley 05 Feb '16

05 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, A busy week here in docs, with today marking only two months left until Mitaka goes out. I've been working on the DocImpact script, the core team review, and a whole lot of general chasing things up and tidying around the place. I also note that the Installation Guide team is busy ramping up for Mitaka, so watch this space for your opportunity to jump into testing for that very soon. Next week, I'll be cleaning up the blueprints, and also starting to get in touch with our packaging contacts to get ready for release. == Progress towards Mitaka == 60 days to go! 382 bugs closed so far for this release. RST Conversions * All planned RST conversions are now complete! Reorganisations * Arch Guide: really needs a last minute push to get this complete before Mitaka. If you can help out, it would be greatly appreciated! ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * User Guides ** https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… ** Contact the User Guide Speciality team: https://wiki.openstack.org/wiki/User_Guides DocImpact * The implementation plan for the DocImpact script changed after we received feedback from Infra and Nova. Now, *all* projects (including the five 'defcore' projects) default to opening DocImpact bugs in their own bug queues. This change was proposed in https://review.openstack.org/#/c/276065/ and merged yesterday, very quickly! Projects will now be able to determine for themselves how they would like to use the DocImpact script within their own groups, and hopefully the quality of bug reporting to docs will improve dramatically as a result of this. I'd like to thank all the PTLs, cross-project liaisons, project core team members, and especially the Infra and Nova teams for their assistance and patience while we worked through this knotty problem. I'm happy to be able to report that, as of today, this project is now complete. == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' No update this week. '''Installation Guide - Christian Berendt''' Mitaka Installation guide changes spec: https://review.openstack.org/#/c/274231/ '''Networking Guide - Edgar Magana''' No update this week. '''Security Guide - Nathaniel Dillon''' RST bug fixes and cleaning up of lingering migration issues. Looking for Neutron reviewers to see what is still accurate and what needs to be updated, please ping Nathaniel. Looking to setup PDF creation job. '''User Guides - Joseph Robinson''' An action item from last meeting was addressed this week - working with new User Guide team members to continue reorganisation edits. Plans for an earlier, US+EU meeting, which would roll into an APAC meeting on Wednesday/Thursday fortnightly meeting times are in place. '''Ops and Arch Guides - Shilla Saebi''' Architecture guide reorganization is underway. We have a drafts repo in openstack-manuals, feel free to ping Shilla or Darren Chan if you are interested in helping out. Considering doing a swarm or work session at the summit in Austin for the Arch guide. Operations guide RST migration pending - conversations still happening to see which route we'll take. Still deciding if the ops guide should have another revision or edition, see ML emails. '''API Docs - Anne Gentle''' Continuing to work on builds of Swagger plus RST. '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Pranav Salunke, Roger Luethi''' Liberty support has been merged. The new default for training-labs clusters is the Liberty release. '''Training Guides - Matjaz Pancur''' Removal of redundant Jenkins jobs (gate-training-guides-tox-slides) and tox targets. Upstream training archives (http://docs.openstack.org/upstream-training/upstream-archives.html) are now separated from the main landing page. '''Hypervisor Tuning Guide - Joe Topjian''' No update this week. '''UX/UI Docs Guidelines - Linette Williams''' Collaboration between the UX project and Doc project. The first UI text guidelines are live: http://docs.openstack.org/contributor-guide/ui-text-guidelines.html. Enhancements to guidelines in progress - specifically related to icons and text formatting. Text reviews are ongoing for new UI prototypes, as applicable. If interested in helping with UI panel reviews or with UI text guidelines, feel free to ping Linette or Piet Kruithof. == 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-01-20 Next meetings: APAC: Wednesday 10 February, 00:30 UTC US: Wednesday 17 February, 14:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… Note that there is currently discussion about moving the US meeting to 20:00 UTC. A patch is open to change this, with ongoing discussion about finding a meeting room: https://review.openstack.org/#/c/271361/ - -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#6_February_2016 - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWtXI/AAoJELppzVb4+KUy1j8IAJ+g5ZbNQuvDCJsznis2EgfX TDMxpovMVwULypjuQdqLT7K6C/uy/4dZbKSlG7vsENnE/dzJngn52P5DriFN3CV0 YjJQ+c7iTzOaiI4choz2sdoaKOYvLIdwDSg89FpS+AE3QF0e3FnjqCtLnRJJAZhN eBg1EaTIeQO9Hz4VWs6QBIMZPsYB7icONy9V08IKDu5HyRm5HFJy73g1Wp+Nrrlv cE5PyBnARBES4bBocxENBy1w7/Pl1exnZXS7M/gadAsJGXBt/k77Ec+6wgY4BmaL XWMyjYGb+LEkdebcKf+kEZ+88eEJlTteSZgvr4B8PdDoB2b3kNUVG3tAuW3/q3g= =fQ5W -----END PGP SIGNATURE-----

1 0

Translators' statistic data and ATC
by Ying Chun Guo 03 Feb '16

03 Feb '16

4 6

Re: [Openstack-i18n] Translators' statistic data and ATC
by KATO Tomoyuki 03 Feb '16

03 Feb '16

> I didn't say NO to both. > The first is yes, the second is no. Sorry, Daisy. I misread the discussion. > For list of contributors for a project version, the rest API will be > available in 3.8 release. Thanks, Alex. KATO Tomoyuki

1 0

IRC meeting tomorrow
by Ying Chun Guo 03 Feb '16

03 Feb '16

1 0

Disabling translation import of django-openstack-auth and designate-dashboard
by Akihiro Motoki 02 Feb '16

02 Feb '16

Hi team, We would like to disable automatic translation imports for __Liberty__ version of django-openstack-auth and designate-dashboard. The background and reasons are described below. I hope there is no objections :-) Thought? [Background] Andreas and I are now working on improvements of translation setup [1] and horizon plugin translation setups. The change made is incompatible with liberty version of these projects only. To keep the infra scripts simple, we would like to disable these. [Status] * designate-dashboard translation setup in Liberty is broken and translation does not work, so I believe there is no impact. * django-openstack-auth is well translated. We can stop translations. We can still propose translation fix by manual. Thanks, Akihiro [1] http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_se…

3 2

Re: [Openstack-i18n] Do we need a slot of i18n translation test meeting?
by Akihiro Motoki 01 Feb '16

01 Feb '16

I sent a patch to drop it. https://review.openstack.org/#/c/275045/ Akihiro 2016-02-02 15:01 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > OK. > Thank you for reminding. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2016/02/02 13:34:43: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: "openstack-i18n(a)lists.openstack.org" >> <Openstack-i18n(a)lists.openstack.org> >> Date: 2016/02/02 13:36 >> Subject: [Openstack-i18n] Do we need a slot of i18n translation test >> meeting? > >> >> Hi, >> >> Can we release the meeting slot reserved for i18n translation test >> meeting [1]? >> According to the meeting log [2], only one meeting was held and seems >> unnecessary. >> >> [1] http://eavesdrop.openstack.org/#I18N_Translation_test_meeting >> [2] >> http://eavesdrop.openstack.org/meetings/openstack_i18n_test_meeting/2015/ >> >> Thanks, >> Akihiro >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >

1 0

Do we need a slot of i18n translation test meeting?
by Akihiro Motoki 01 Feb '16

01 Feb '16

Hi, Can we release the meeting slot reserved for i18n translation test meeting [1]? According to the meeting log [2], only one meeting was held and seems unnecessary. [1] http://eavesdrop.openstack.org/#I18N_Translation_test_meeting [2] http://eavesdrop.openstack.org/meetings/openstack_i18n_test_meeting/2015/ Thanks, Akihiro

2 1

I18n midcycle virtual sprint
by Ying Chun Guo 01 Feb '16

01 Feb '16

Hello, team In the last IRC meeting, we decided to run a midcycle virtual sprint at UTC 1330 on January 29th. For more details please go to https://wiki.openstack.org/wiki/VirtualSprints. The sprint is planned in an weekend. We welcome any people who are interested to join. Best regards Ying Chun Guo (Daisy)

3 3

i18n repo: invalid pot files
by Andreas Jaeger 30 Jan '16

30 Jan '16

funning msgfmt --check-format on the i18n repo gives a couple of violations, please check these. Exact command used: find . -type f -regex '.*\.pot?' -print0 | xargs -0 -n 1 msgfmt --check-format -o /dev/null ./i18n/i18n/locale/it/LC_MESSAGES/i18n.po:309: duplicate message definition... ./i18n/i18n/locale/it/LC_MESSAGES/i18n.po:210: ...this is the location of the first definition msgfmt: found 1 fatal error ./i18n/i18n/locale/fr/LC_MESSAGES/i18n.po:309: duplicate message definition... ./i18n/i18n/locale/fr/LC_MESSAGES/i18n.po:210: ...this is the location of the first definition msgfmt: found 1 fatal error ./i18n/i18n/locale/de/LC_MESSAGES/i18n.po:311: duplicate message definition... ./i18n/i18n/locale/de/LC_MESSAGES/i18n.po:210: ...this is the location of the first definition msgfmt: found 1 fatal error ./i18n/i18n/locale/i18n.pot:13: duplicate message definition... ./i18n/i18n/locale/i18n.pot:2: ...this is the location of the first definition msgfmt: found 1 fatal error ./i18n/i18n/locale/zh_CN/LC_MESSAGES/i18n.po:309: duplicate message definition... ./i18n/i18n/locale/zh_CN/LC_MESSAGES/i18n.po:210: ...this is the location of the first definition msgfmt: found 1 fatal error ./i18n/i18n/locale/ko_KR/LC_MESSAGES/i18n.po:309: duplicate message definition... ./i18n/i18n/locale/ko_KR/LC_MESSAGES/i18n.po:210: ...this is the location of the first definition -- 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 1

What's Up, Doc? 29 January 2016
by Lana Brindley 28 Jan '16

28 Jan '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, An incredibly hot week here in the antipodes, coupled with Australia Day has meant that I haven't been particularly productive this week. Luckily, the rest of you have picked up the slack, and things have been ticking along nicely. Thanks everyone :) == Progress towards Mitaka == 68 days to go! 368 bugs closed so far for this release. RST Conversions * All planned RST conversions are now complete! Reorganisations * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * User Guides ** https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… ** Contact the User Guide Speciality team: https://wiki.openstack.org/wiki/User_Guides DocImpact * After some discussion on the dev list, we're adjusting our approach to this problem. Watch this space. == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' No update this week. '''Installation Guide - Christian Berendt''' AODH install instructions merged '''Networking Guide - Edgar Magana''' Networking guide versioning has been completed, we are publishing Liberty and Mitaka releases. Networking guide ToC has been updated and missing chapter have been assigned. Etherpad with the topic missing from the guide: https://etherpad.openstack.org/p/networking-guide '''Security Guide - Nathaniel Dillon''' No update this week. '''User Guides - Joseph Robinson''' Team meetings started again this week, and the large point was an IA reorg after content merging. Other discussion point included checking in with Docs liasons for Sahara, Trove, Murano, and Magneto plus checking in with interested volunteers for the User Guide Team. '''Ops and Arch Guides - Shilla Saebi''' Reorganization of the architecture guide is on-going. We have a full team of volunteers on our wiki <https://wiki.openstack.org/wiki/Documentation/OpsGuide>, but not much traction. We need more volunteers and we were looking to do a swarm in Manchester but not enough team members attending. Looking to maybe set one up for Austin. '''API Docs - Anne Gentle''' No update this week. '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Pranav Salunke, Roger Luethi''' Liberty support continues to make good progress. We can now launch an instance VM. Some clean up and reviewing still needs to be done. '''Training Guides - Matjaz Pancur''' Preparations for Austin Upstream training (https://review.openstack.org/#/c/271006/) New landing page for Training guides (http://docs.openstack.org/draft/training-guides/. '''Hypervisor Tuning Guide - Joe Topjian''' An update to to the Guide was posted back in December with a call for participation: http://lists.openstack.org/pipermail/openstack-operators/2015-December/0091… == Doc team meeting == Next meetings: US: Wednesday 3 February, 14:00 UTC APAC: Wednesday 10 February, 00:30 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… Note that there is currently discussion about moving the US meeting four hours later to 20:00 UTC. If you have a strong opinion on this matter, make sure you weigh in on the mailing list thread: http://lists.openstack.org/pipermail/openstack-docs/2016-January/008206.html - -- Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWquVYAAoJELppzVb4+KUyBTQH/0M+ixT7g/MIePoZpFms5aSU SvLV/rAJe1dKbB2tNfq5ozNcWS/uMHB+w4bzHGjP+xexOvTUZNoBrKGLcufADMSS ekOMITnr69PLlXh5e+/G55/02sZUFmmq4ZC2xmDrgGbwZLohbLUA/L1G3o+oJGYy 2/KrNAQCutkEKTNwAN4NkA+cbSj8jM8UyVWfFzfEbywSmpmrrQyetEhfmZPj3g9t 7cUnqrRegHI7mwPGeLyM3O2bIj3CLKsmWDFEfzOfoUGDGDCQ6yGj8iv8u4PuA6Zt Mw041/PII0LWDCSvovYnsRoZXMcRGVFfWdBvrOVZaGZfVhZLK/2BrZPIr+r6EzA= =eKF8 -----END PGP SIGNATURE-----

1 0

Re: [Openstack-i18n] IBM translations to contribute
by Akihiro Motoki 28 Jan '16

28 Jan '16

Hi Doug, First, I don't have any strong opinion on importing Mitaka translation contribution from IBM. Any decision is okay to me. The reason is described below. In addition, as an i18n active member, growing OpenStack translation folks is important but each language team should be a team. All comments below is as one of Japanese team reviewer who reviewed about 50% of strings (> 10000 messages) in Liberty release. I hope the same thing never happens in the Nxx release. Before going to the detail, I must apologize my following message is rude, but let me share my feeling as an active Japanese reviewer. 2016-01-13 0:02 GMT+09:00 Douglas Fish <drfish(a)us.ibm.com>: > Hi Akihiro, > > I understand your concern. These are translations that were completed > outside of Zanata, using our previous process. They were translated using > the same guidelines as the previous IBM contributions. While they are > professionally done and well tested, they have not been written to conform > to OpenStack community guidelines. It's likely any issues that existed in > the previous IBM translations will exist with these as well. Personally I was disappointed significantly with this. I am feeling that my effort to review Japanese IBM translations in Liberty cycle should not be done. I and some reviewers spent not small amount of time to review them because we believe our comments will be feedback-ed to Mitaka translations, but it turns out that it wasted the time. Regarding Japanese translations, the contributed translations did not have the enough quality that we could release them as-is from various points. * Not a small number of terminologies used were not natural to experienced OpenStack operators, * Strings were translated but it seems actual context where strings were used were not checked, especially substitutions (like %s, %(xxx)s), * There are many inconsistency with the existing team guidelines. (I have various experiences of translating Japanese certification exam for IT engineers and I believe I know what quality is ready for such purposes) We left many comments in Zanata but they are not referred at all.............. We, at least me, made these comments to share our guidelines..... In addition, Japanese translation team provides a lot of information including our glossary, contact points, discussion channels through OpenStack wiki page, but it does not work so far.... I will stop writing my feeling here. > I agree this is not a good long term way to complete translations. I'm not > sure if you are aware, but our Italian translation center has completed a > pilot of working directly in Zanata. Notice the high completion percentage > for Horizon Italian. I expect to have broader participation in this area > during the translation of Mitaka. It depends on the progress of translations of each language and I hope it works well. In addition, growing translation community is a good thing in the longer term. > We would like to contribute these translations to help with the OpenStack > translation effort. I understand that because they were not translated with > the same guidelines they may instead be burdensome to the translators. I > believe this is the purpose of creating the branch for offline translations: > so that language coordinators can evaluate if the translations are actually > beneficial to our OpenStack translation efforts, or if they are inconsistent > with the language's guidelines and more trouble than they are worth. I > certainly understand that creating and populating a branch does not mean > that these translations will actually be accepted. For Mitaka translation contribution, I don't have a strong opinion and either option is okay to me. If we talk about only Japanese translations of Mitaka release, server translations do not affect GUI translations (and CLI translation if any). According to our survey in Japan, most of all operators prefer to English messages. Considering these situations, I think Japanese translations of server projects can be shipped as-is without reviews. We can discuss the translation guidelines for Nxxx release translations to address inconsistencies and mismatches. > I'd like to have the branch created so that the review can take place. What > do you think? As mentioned above, I am okay with either decision. I am just concerned and disappointed with the fact that all translation efforts are being done completely separately and hope it never happens. Akihiro > > Doug > > > ----- Original message ----- > From: Akihiro Motoki <amotoki(a)gmail.com> > To: Douglas Fish/Rochester/IBM@IBMUS > Cc: "openstack-i18n(a)lists.openstack.org" > <openstack-i18n(a)lists.openstack.org> > Subject: Re: [Openstack-i18n] IBM translations to contribute > Date: Mon, Jan 11, 2016 11:09 PM > > Hi Doug, > > Thanks for continuing the effort. > > I have two questions. > > First, why do we need to use a branch again. > We already set up the translation platform and IBM team can translate > on Zanata directly > as we discussed in Liberty cycle. There is no reason to use a branch > and push translation bursty again. > > Second, is existing community translation guideline per language team > honored in the contributed translations? > When talking about Japanese, we saw a lot of different translation > guidelines on wording in the last IBM translation contributed in > Liberty. > As a reviewer, we don't want to comment the same thing again. > After we Japanese review team reviewed Liberty contribution from IBM, > we don't receive any feedback/response/discussion from IBM team, > so I am afraid we need to do the similar again. It need to be avoided. > Otherwise reviewers will lose their energy. > Could you comment on the situation? > > Thanks, > Akihiro > > > 2016-01-12 12:54 GMT+09:00 Douglas Fish <drfish(a)us.ibm.com>: >> We have translations to contribute for languages >> de es fr it ja ko_KR pt_BR ru zh_CN zh_TW >> for ceilometer, cinder, glance, keystone, neutron, and nova >> >> These are additional translations performed by the same teams that >> translated our previous contributions. They have been reviewed and tested. >> I >> estimate up to 35K messages will be contributed across the 10 languages >> and >> 6 components. >> >> Following the process outlined here >> >> http://lists.openstack.org/pipermail/openstack-i18n/2015-September/001388.h… >> I am requesting that a branch be created in Zanata to facilitate review of >> these translations by the language coordinators. >> >> Thanks >> >> Doug >> >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > > > >

6 7

Fwd: [openstack-dev] [all][i18n] Rework of translation setup
by Andreas Jaeger 28 Jan '16

28 Jan '16

FYI, I'll copy resources around for python-* and oslo.* projects, Andreas -------- Forwarded Message -------- Subject: [openstack-dev] [all][i18n] Rework of translation setup Date: Thu, 28 Jan 2016 13:13:50 +0100 From: Andreas Jaeger <aj(a)microfocus.com> Reply-To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> Organization: SUSE Linux GmbH, Nuernberg, GF: Felix Imendörffer, Jane Smithard, Graham Norton , HRB 21284 (AG Nuernberg) To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> Projects that want to setup translations for their repositories run into a few common problems and we're addressing these now to make the setup for everybody easier. The problems they run into came from limitations of the current infra scripts, so we rework the infra scripts. We want to have a simple and consistent setup for translations - with a sensible consistency. Right now it’s consistent for python projects but not sensible in some cases. See here for the full spec: http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_se… We're working basically on two major changes: a) The same setup for django projects. b) Locate files for python projects in a better place. b) only affects olso.* and python-*client projects: We need to update setup.cfg, your i18n file and move the files from $reponame/locale/$reponame.pot to $modulename/locale/modulename.pot - so placing it in your source directory and not besides it. While we move files around, we also stopped syncing of translations for olso* and python-client projects. So, please review these changes quickly and merge them. For a) we will review each django project and send patches for them as well. Also, we make our scripts more robust - and will document this properly. If you have any questions, please reach out to us. We hope that this will make translation setup for projects easier, Akihiro Motoki & Andreas Jaeger -- 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 __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- 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

Re: [Openstack-i18n] IRC meeting today
by Jeremy Stanley 22 Jan '16

22 Jan '16

On 2016-01-22 14:17:23 +0800 (+0800), Ying Chun Guo wrote: [...] > Zanata has API to query translators activities. [...] Oh, that's excellent news! Maybe the update I heard we were still needing was so that we could let non-administrators query that? > Adding them to "extra ATCs" is a way. > Are there any other options to grant them the election rights ? At the moment you'll need to continue updating the extra-atcs list. The tool which queries our contributors in Gerrit could be extended to also query Zanata, but I haven't even seen the API documentation for that yet so I can't gauge how long it would take me to integrate into what I have. Longer term, of course we want this data source automatically integrated with our contributor listing tools. For the curious, https://review.openstack.org/263971 is the current state of development on the new framework I'm using for determining electoral rolls and qualifiers for contributor summit codes. -- Jeremy Stanley

1 0

IRC meeting today
by Ying Chun Guo 21 Jan '16

21 Jan '16

Hello, team We will have our regular meeting today, at 1300UTC in #openstack-meeting. I'm going to cover following topics: * Discussion: Glossary management process * Discussion: IBM contributions * Status update: Installation guide translation * Status update: Translation check website * Status update: Stackalytics feature Feel free to propose other topics if you like. Best regards Ying Chun Guo (Daisy)

3 3

What's Up, Doc? 22 January 2016
by Lana Brindley 21 Jan '16

21 Jan '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, We seem to be more or less back into the swing of things here in docs land this week, with our meeting schedule back up and running, and now our very first full-length newsletter for 2016! We only have two and a half months until Mitaka goes out, but we're in great shape so far, with 345 bugs dealt with, and all the planned RST conversions complete. Most of the discussion this week has been around API documentation and Fairy Slipper, Docs Tools and some site theme changes, and a little back and forth on meeting times. == Progress towards Mitaka == 75 days to go! 345 bugs closed so far for this release. RST Conversions * All RST conversions are now complete! Well done to all the contributors and reviewers who made this happen so quickly this time around. We are now, with only a couple of exceptions, completely converted. Great job :) Reorganisations * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * User Guides ** https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… ** Contact the User Guide Speciality team: https://wiki.openstack.org/wiki/User_Guides DocImpact * After some discussion on the dev list, we're adjusting our approach to this problem. Watch this space. == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' Meeting moved http://lists.openstack.org/pipermail/openstack-docs/2016-January/008209.html. Kenneth finished his Galera patch https://review.openstack.org/#/c/263075/, there were also several patches from different contributors, so things are improving. '''Installation Guide - Christian Berendt''' AODH instructions near completion, EU/US meeting moved (Every two weeks (on even weeks) on Tuesday at 1600 UTC), APAC meeting will be dropped the next weeks if if not more participants join. '''Networking Guide - Edgar Magana''' No update this week. '''Security Guide - Nathaniel Dillon''' No update this week. '''User Guides - Joseph Robinson''' One patch combining Images and Instances content merged, and a patch on Shared File Systems is now available for review. User Guide team meetings are set to begin next Thursday, with guidelines for combining admin and cloud admin files a topic for discussion. '''Ops and Arch Guides - Shilla Saebi''' No update this week. '''API Docs - Anne Gentle''' Anne imported and triaged over 60 GitHub Issues into Launchpad bugs. Anne working on build jobs for making API docs with fairy-slipper: https://review.openstack.org/#/c/269809. Anne emailed over 25 individuals about the plans for API docs and answered follow-up questions. Karen worked on validated Swagger: https://review.openstack.org/#/c/266527/. Need to release fairy-slipper this week or next. '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Roger Luethi''' Liberty is making good progress, trying to get Liberty patches working. Early beginnings of Fedora support switched to CentOS. Copy-on-write disks for KVM. Bug fixing and refactoring, as usual. Early work on python port. Plan to host training labs on a web page. '''Training Guides - Matjaz Pancur''' German translation of the Upstream training (http://docs.openstack.org/de/upstream-training/) - this makes 3 full translations (en, de, ko_kr), ja is at 80%. A patch that enables direct bug reporting on the slides (https://review.openstack.org/#/c/259654/) several other patches. '''Hyperviser Tuning Guide - Joe Topjian''' No update this week. == Core Team Changes == The next core team review will occur on 1 February. In the meantime, it's probably a good time to go over what being a core means, and how the review system works. For more detail, see the Contributor Guide: http://docs.openstack.org/contributor-guide/docs-review.html Docs cores have the ability to +2 docs reviews, and they also have the ability to merge reviews. Reviews are merged by cores only once there's been *two* +2 votes, and at least one +1. There are very few exceptions to this rule, for changes that need to go through very quickly to resolve gate breakages or similar, but this rule holds in just about every situation. Cores are assigned based on merit, usually through the core review process that we do every month. During a core review, the PTL gathers statistics on reviews made, and patches created and merged, and uses that to determine who should be added to (or removed from) the core list. That then goes to a vote of the existing core team before being actioned and announced. Core team members also have the ability to nominate (and vote on) exceptional team members, where the statistics might not reflect the amount of effort they have put in. If you ever have any questions about becoming a docs core, or about getting your docs patch merged, you can contact the team on the usual docs mailing list, or ping any of us on IRC. == Doc team meeting == The US team meeting was held last week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-01-20 Next meetings: APAC: Wednesday 27 January, 00:30 UTC US: Wednesday 3 February, 14:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… Note that there is currently discussion about moving the US meeting four hours later to 20:00 UTC. If you have a strong opinion on this matter, make sure you weigh in on the mailing list thread: http://lists.openstack.org/pipermail/openstack-docs/2016-January/008206.html - -- Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWoafKAAoJELppzVb4+KUyFR8H/1so79V/BvFSAehklcbyDmZG JYkHQwrMUiTREN0y4l2ccegtgYWKeXEd01holKTMxxzR1KAcibi2eBMGjizNbIdt L8Add2BIPB8zwlqR0zrBAVKzecUth4EpvWLBTU4UDuHIHoF6cyOL3RZWKmkEg7/o GD7H/Yt264qFFPmQ8t8Flq5mUE892s2aReDVFkXPmmkNzBtIGDmzu13P6Y5zX4YX xzUSWJmBDTJPaz/0IsG8Sc46R3gs15hV7wtcCPwVtQXVZ18mKkYYz02zKQzpW518 Z8ysKgwHYkRhn+cxgsg10bV8/NePyxvgvHnknTLpbBZOV700kCmSTEmP3V3LUQw= =6VAi -----END PGP SIGNATURE-----

1 0

[OpenStack-i18n] Install guide finished translated Korean
by SungJin Kang 19 Jan '16

19 Jan '16

Hi, Install guide finished transtated ko_KR and review too. How to add draft site[1]? Thanks Sungjin. ps. not yet common-docs... [1]: http://docs.openstack.org/draft/draft-index.html

6 11

What's Up, Doc? 15 January
by Lana Brindley 14 Jan '16

14 Jan '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, Welcome to 2016! A short newsletter this week as I get my feet back under me after my vacation. I hope you all had a wonderful holiday period, and got some well-earned down time. I'm looking forward to working hard with you all over the next few months to get Mitaka out into the wild :) == Progress towards Mitaka == 82 days to go! 324 bugs closed so far for this release. RST Conversions * All RST conversions are now complete! Well done to all the contributors and reviewers who made this happen so quickly this time around. We are now, with only a couple of exceptions, completely converted. Great job :) Reorganisations * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * User Guides ** https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… ** Contact the User Guide Speciality team: https://wiki.openstack.org/wiki/User_Guides DocImpact * After some discussion on the dev list, we're adjusting our approach to this problem. Watch this space. == Speciality Teams == No updates this week, as I'm totally disorganised. Next week for sure! == Core Team Changes == I would like to offer a warm welcome to Atsushi Sakai as our newest core team member. Welcome to the team :) We will resume regular reviews in February 2016. == Doc team meeting == There's been some confusion over the meeting schedule, but as far as I can tell, these are the next meeting dates: Next meetings: US: Wednesday 20 January, 14:00 UTC APAC: Wednesday 27 January, 00:30 UTC 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 - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWmHLwAAoJELppzVb4+KUydocH/30zQwOcQ7kOPSeWIYvGPJ6u /WO2Tv9QkoOZe4O7WulkTRXTsVTlr9lP3esANYf9Vys8E1720Wl3pPNL6YYJ8XCe 1WWIxZpZNiIRB86dfgJn6/oLdhNjAS6W6SvNHNKtecQ5m/6Kv0uRfpVHxw89BRBV +f5QvPnDsydUlKEamQJAyRWzKc6BnpM/AbgS20BL3/luhZpZI3V1Z2bnxbGJCRlD 10uAwY3+z6Oo3SCQI7HVe3TfZQDa6BBYPUK2KSlY5Kr8VjclEgy4tuootRd/4rva WCS4Z61XPvR6DQdLPS6RVCmCrkRtHd1yYeBZt5fP9GBDrXm2CUZipl13grZMXY8= =XuVl -----END PGP SIGNATURE-----

1 0

FW: [Bug 1534418] [NEW] Wrong Chinese translation in OpenStack Liberty install doc
by Kato, Tomoyuki 14 Jan '16

14 Jan '16

Hi Chinese team, Please take a look at the bug: https://bugs.launchpad.net/bugs/1534418 I can't understand what is wrong from the bug report =) > Subject: [Bug 1534418] [NEW] Wrong Chinese translation in OpenStack Liberty install doc > > Public bug reported: > > The original link is http://docs.openstack.org/liberty/install-guide-rdo/environment-ntp-control… > The translation draft link is http://docs.openstack.org/liberty/zh_CN/install-guide-rdo/environment-ntp-c… > > ** Affects: openstack-i18n > Importance: Undecided > Status: New > > ** Attachment added: "01.png" > https://bugs.launchpad.net/bugs/1534418/+attachment/4550272/+files/01.png > > -- > > Title: > Wrong Chinese translation in OpenStack Liberty install doc > > Status in openstack i18n: > New > > Bug description: > The original link is http://docs.openstack.org/liberty/install-guide-rdo/environment-ntp-control… > The translation draft link is > http://docs.openstack.org/liberty/zh_CN/install-guide-rdo/environment-ntp-c…

2 1

Re: [Openstack-i18n] How do we manage glossary?
by Akihiro Motoki 14 Jan '16

14 Jan '16

2016-01-05 18:00 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Thank you for the patch, Akihiro. > I think it's easier to discuss in email. > So I copied your comments in your patch here. > >> Expected workflow: >> * add an entry to the master glossary: >> - Update glossary/master.yaml and review it on gerrit >> - Once approved, glossary-tool sync will update per-language glossary >> files and propose the update to gerrit (jenkins jos) > > In your design, when the changes to master.yaml is approved, how to trigger > the jenkins job ? using a tag ? > I think we could add one more action in this Jenkins job: automatically send > an email to i18n to notify that the glossary is changed. We can use 'post' pipeline to trigger some jobs when each change is merged. >> * update per-language glossary: >> - Each language team upload a proposed glossary to gerrit. A language team >> members review it and once they have a consensus i18n core reviewer merges >> it into the repository. >> - Once approved, a corresponding glossary PO file is generated and >> uploaded to Zanata. (glossary-tool write-po and jenkins job) > > In your design, translators will not use translation editor in Zanata to > translate glossary. > Translators will propose the glossary translation to gerrit. > I don't know if translators have enough training to commit a patch. > They may understand how to use Zanata more than how to use gerrit. > There is no commands to support uploading glossary to Zanata. > So the action to upload po files have to be executed manually. I think uploading glossary can be done by Jenkins job triggered by 'post' job as well. I agree that translators are familiar with Zanata rather than Gerrit to some extent. However, my question is still how to keep discussion contexts (or history/background). It seems Zanata history is associated with Zanata internal resource ID. I am afraid it can be easily lost and we cannot recover it :-( > How do you think if we change to: > - Update glossary/master.yaml and review it on gerrit. > - Once approved, glossary-tool sync will update per-language glossary files > and propose the update to gerrit (jenkins jos). > - The jenkins job will upload pot file in Zanata. > - The jenkins job will send email to i18n to notify the change. > - Translators log in to Zanata to translate. > - Jenkins job download po files to i18n repository. > - Zanata admin automatic update Zanata glossary. Again, how can we maintain discussion contexts? On the other hand, I might be thinking "context" too much. If we go to the above way you mentioned, I think we need to maintain discussion contexts in other places. If the team suggests to do so, I am okay. Japanese team actually maintains it in OpenStack wiki and it works mostly well except that we need to sync glossary manually, but it might be a small thing compared to keep "context". Keeping "context" will save time to explain why we choose THIS in our current glossary. If we do not have it, we need to explain same things to new contributors again and again, and this will increase the barrier to new contributors. >> * syntax when a review is proposed >>- 'glossary-tool' check verifies if YAML data is valid. It can be a part of >> pep8 target. > > Good to have syntax check. > > BTW, how do you think the advantage of YAML file, comparing with po and pot > files? > Because if we use po and pot files directly, we could put "note" as comments > in pot files. > Do you want "note" also be translated ? The only reason is YAML file is human-friendly and easy to edit by text editors. I don't think it is a good idea to edit PO file directly. The format is not human-friendly and we can easily make mistakes in editing PO files. "note" in a PO file will be overridden if the glossary is downloaded from Zanata. This means we need to manage PO files directly in our git repo. I don't think maintaining PO files is more difficult than maintaining YAML files. Finally, I would like to purge ancient glossary on Zanata as soon as possible. The current glossary harms translation and provides no value. Akihiro > > Regards > Daisy > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2016/01/05 07:05:51: > >> 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: 2016/01/05 07:07 >> Subject: Re: [Openstack-i18n] How do we manage glossary? > >> >> Hi Daisy and the team, >> >> 2015-12-17 19:35 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> > Hi, Akihiro >> > >> > Please let me know your comments to https://review.openstack.org/258924 >> >> I commented your above review. >> >> I proposed a counter proposal https://review.openstack.org/261767. >> This is just an idea. I am open to the input. >> >> Comments inline below. >> >> > Answers to your question: >> > >> > 1. Context >> > >> > The current solution in my patch could not satisfy this requirement >> > about >> > context. >> > If we want to put context to glossary, we need to develop our own >> > extension >> > of sphinx-build. >> > How do you think the priority to support context ? >> >> IMHO supporting contexts is important to make discussion on glossary >> productive. >> As you can see in Japanese glossary on OpenStack wiki [1], I believe >> that discussion contexts >> are important for further discussions and it also helps new >> contributors understand the background. >> >> In my proposal https://review.openstack.org/261767, >> we maintain all contexts in YAML glossary files. >> >> > 2. Process >> > >> > If people want to change the glossary, e.g. add, update, change the >> > comments, add coments >> > following process is designed. >> > >> > a> the requestor submits a patch to i18n repo >> > b> core team approve the patch >> > c> the auto uploading process is triggered. terminology.pot is uploaded >> > to >> > Zanata for translation >> > d> translators finish translation >> > e> Zanata admin manually patch terminology.pot and its translationpo >> > files, > >> > and upload to Zanata >> >> IMO the glossary needs to be reviewed more carefully compared to >> regular translations. >> In regular translations, all translated strings are imported, but for >> glossary it is better that >> only reviewed strings are imported. Another choice is to use gerrit >> for the glossary review. >> My proposal https://review.openstack.org/261767 implements the latter >> option. >> >> Thought? >> >> Thanks, >> Akihiro >> >> > >> > Best regards >> > Ying Chun Guo (Daisy) >> > >> > >> > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2015/12/02 02:29:44: >> > >> >> From: Akihiro Motoki <amotoki(a)gmail.com> >> >> To: "openstack-i18n(a)lists.openstack.org" >> >> <Openstack-i18n(a)lists.openstack.org> >> >> Date: 2015/12/02 02:32 >> >> Subject: [Openstack-i18n] How do we manage glossary? >> > >> >> >> >> Hi team, >> >> >> >> Recently we added the glossary to the i18n repo [1]. >> >> I wonder how we can manage the glossary and am sending this mail. >> >> The glossary can be referred to in Zanata, so it would be useful. >> >> >> >> Mainly I have two questions. >> >> >> >> The first point is what is the expected process to manage the glossary. >> >> How can we update the glossary? >> >> When is it uploaded to Zanata for translations? >> >> >> >> The second point is how we can have the context. >> >> I think the second point is also important. >> >> Each entry in our glossary has some background, for example >> >> why we reach the current consensus. >> >> This kind of context is important to discuss for further improvements. >> >> >> >> I updated the glossary for Japanese translation last week >> >> and I added various description about backgrounds of the glossary. >> >> I feel it is important to keep the context. >> >> How can we manage the context? >> >> >> >> I don't have a good idea now. >> >> I would like to raise these questions for broader discussion. >> >> >> >> Thanks, >> >> Akihiro >> >> >> >> [1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n >> >> >> >> _______________________________________________ >> >> Openstack-i18n mailing list >> >> Openstack-i18n(a)lists.openstack.org >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >> >> > >> >

4 5

IBM translations to contribute
by Douglas Fish 12 Jan '16

12 Jan '16

2 2

[all][i18n] Proposed change for consistent setup of translation - up for review
by Andreas Jaeger 11 Jan '16

11 Jan '16

Projects that want to have translations, need to setup their repository in very specific ways which lead to quite a few questions from some of you and also quite different solutions. Let's make this easier - and consistent. I've written a spec that aims to provide a consistent set up for the repositories and ask for your review and comments on it: https://review.openstack.org/#/c/262545/ 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

1 0

Re: [Openstack-i18n] How do we manage glossary - requirements priorities
by Akihiro Motoki 11 Jan '16

11 Jan '16

Thanks for initiating the effort. 2016-01-11 18:36 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Hello, team > > There are three possible solutions to manage glossaries and their > translations. > All of these solutions have their advantages and disadvantages. > I think we should prioritize the requirements firstly, then we make the > choice based on the requirements. > Here I list some requirements. > I would like to suggest to distinguish "master glossary" (in the source language) and "per-language glossary" in this discussion. Theoretically speaking, each language team can have its own glossary, but IIUC Zanata glossary does not allows it and we need to have a common glossary entries. As the assumption of this discussion, should we assume the current enabled feature in Zanata or can we assume to enhancing Zanata? I would suggest to distinguish 'requirements' and the current limitation of Zanata. 'requirement' should not have assumption based on 'the current limitation of Zanata'. Now, I am looking through the listed items. #0 each language team can manage their glossary without 'admin' role. At least, language coordinator and reviewers should be allowed to do it. To me, this is the top priority "must to have". > #1. Save glossaries in i18n repo "nice to have" "master" or "per-language"? Based on #2 below, it seems "master glossary". > #2. Translate and review with Zanata editor, and enable the auto sync > between Zanata editor and i18n repo. In #2, it seems two things are mixed. The first part "Translate and review with Zanata editor", yes it is a requirement. The second part is just a process. It is not a requirement, i.e., "nice to have". > #3. View comments while translating "Must to have" (as the second priority) I believe it is "Must to have" but it is not a top priority because the top priority to me is that each language is allowed to maintain their glossary without 'admin' privilege. > #4. Review the new added glossary by Gerrit "not necessary" I am not sure this needs to be done in Gerrit. If we have a way to add a new entry in Zanata, it is sufficient as well. I am not sure what assumption you have. > #5. View the list of glossaries and their comments in i18n documents. "not necessary" I don't think it is a requirement. I hope the list of glossary on Zanata instead as Transfix does. When we go to "Glossary" link at the top of Zanata UI https://translate.openstack.org/glossary/view.seam, we see a list of languages but when we click a language name, we will get a list of members of each language team. It is a confusing behavior and we expect a glossary in each language. > #6. Keep the history of glossary translations and discussions. "must to have" (as the second priority) Yes. this is important! > > Please let me know your thoughts to these requirements. > You can add comment "Must support", "good to have", and "not necessary" to > each requirement, > and order these requirements by the priority in your mind. > If you have other requirements, feel free to add. /FYI/ I abandoned my reviews to keep my review list small. Feel free to restore them if necessary even after this discussion have a consensus. Thanks, Akihiro > > For your reference, here are the three possible solutions: > > - Solution 1 Save glossaries in pot file and translations in po files. > The current solution in repo: openstack/i18n > Support requirement #1 , #2 and #4 > ( @Alex, please help to verify if #3 and #6 could be satisfied in this > solution.) > > - Solution 2 Save glossaries in rst file and translations in po files. > https://review.openstack.org/#/c/258924/ > Support requirement #1, #2, and #4, #5 > > - Solution 3 Save glossaries in YAML file and translations in YAML files. > https://review.openstack.org/#/c/261767/ > https://review.openstack.org/#/c/262710/ > Support requirement #1, #3 and #4, #6 > > Your input will help us to make a team decision. > Thank you. > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2016/01/05 19:09:09: > >> 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: 2016/01/05 19:10 >> Subject: Re: [Openstack-i18n] How do we manage glossary? >> >> 2016-01-05 18:00 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> > Thank you for the patch, Akihiro. >> > I think it's easier to discuss in email. >> > So I copied your comments in your patch here. >> > >> >> Expected workflow: >> >> * add an entry to the master glossary: >> >> - Update glossary/master.yaml and review it on gerrit >> >> - Once approved, glossary-tool sync will update per-language glossary >> >> files and propose the update to gerrit (jenkins jos) >> > >> > In your design, when the changes to master.yaml is approved, how to >> > trigger >> > the jenkins job ? using a tag ? >> > I think we could add one more action in this Jenkins job: automatically >> > send >> > an email to i18n to notify that the glossary is changed. >> >> We can use 'post' pipeline to trigger some jobs when each change is >> merged. >> >> >> * update per-language glossary: >> >> - Each language team upload a proposed glossary to gerrit. A language >> >> team >> >> members review it and once they have a consensus i18n core reviewer >> >> merges >> >> it into the repository. >> >> - Once approved, a corresponding glossary PO file is generated and >> >> uploaded to Zanata. (glossary-tool write-po and jenkins job) >> > >> > In your design, translators will not use translation editor in Zanata to >> > translate glossary. >> > Translators will propose the glossary translation to gerrit. >> > I don't know if translators have enough training to commit a patch. >> > They may understand how to use Zanata more than how to use gerrit. >> > There is no commands to support uploading glossary to Zanata. >> > So the action to upload po files have to be executed manually. >> >> I think uploading glossary can be done by Jenkins job triggered by >> 'post' job as well. >> I agree that translators are familiar with Zanata rather than Gerrit >> to some extent. >> >> However, my question is still how to keep discussion contexts (or >> history/background). >> It seems Zanata history is associated with Zanata internal resource ID. >> I am afraid it can be easily lost and we cannot recover it :-( >> >> > How do you think if we change to: >> > - Update glossary/master.yaml and review it on gerrit. >> > - Once approved, glossary-tool sync will update per-language glossary >> > files >> > and propose the update to gerrit (jenkins jos). >> > - The jenkins job will upload pot file in Zanata. >> > - The jenkins job will send email to i18n to notify the change. >> > - Translators log in to Zanata to translate. >> > - Jenkins job download po files to i18n repository. >> > - Zanata admin automatic update Zanata glossary. >> >> Again, how can we maintain discussion contexts? >> >> On the other hand, I might be thinking "context" too much. >> If we go to the above way you mentioned, >> I think we need to maintain discussion contexts in other places. >> If the team suggests to do so, I am okay. >> >> Japanese team actually maintains it in OpenStack wiki and it works mostly >> well >> except that we need to sync glossary manually, but it might be a small >> thing >> compared to keep "context". Keeping "context" will save time to explain >> why >> we choose THIS in our current glossary. If we do not have it, we need to >> explain same things to new contributors again and again, and this >> will increase >> the barrier to new contributors. >> >> >> * syntax when a review is proposed >> >>- 'glossary-tool' check verifies if YAML data is valid. It can be a part >> >> of >> >> pep8 target. >> > >> > Good to have syntax check. >> > >> > BTW, how do you think the advantage of YAML file, comparing with po and >> > pot >> > files? >> > Because if we use po and pot files directly, we could put "note" as >> > comments >> > in pot files. >> > Do you want "note" also be translated ? >> >> The only reason is YAML file is human-friendly and easy to edit by >> text editors. >> I don't think it is a good idea to edit PO file directly. >> The format is not human-friendly and we can easily make mistakes in >> editing PO files. >> >> "note" in a PO file will be overridden if the glossary is downloaded >> from Zanata. >> This means we need to manage PO files directly in our git repo. >> I don't think maintaining PO files is more difficult than maintaining >> YAML files. >> >> >> Finally, I would like to purge ancient glossary on Zanata as soon >> aspossible. >> The current glossary harms translation and provides no value. >> >> Akihiro >> >> >> > >> > Regards >> > Daisy >> > >> > >> > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2016/01/05 07:05:51: >> > >> >> 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: 2016/01/05 07:07 >> >> Subject: Re: [Openstack-i18n] How do we manage glossary? >> > >> >> >> >> Hi Daisy and the team, >> >> >> >> 2015-12-17 19:35 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> >> > Hi, Akihiro >> >> > >> >> > Please let me know your comments to >> >> > https://review.openstack.org/258924 >> >> >> >> I commented your above review. >> >> >> >> I proposed a counter proposal https://review.openstack.org/261767. >> >> This is just an idea. I am open to the input. >> >> >> >> Comments inline below. >> >> >> >> > Answers to your question: >> >> > >> >> > 1. Context >> >> > >> >> > The current solution in my patch could not satisfy this requirement >> >> > about >> >> > context. >> >> > If we want to put context to glossary, we need to develop our own >> >> > extension >> >> > of sphinx-build. >> >> > How do you think the priority to support context ? >> >> >> >> IMHO supporting contexts is important to make discussion on glossary >> >> productive. >> >> As you can see in Japanese glossary on OpenStack wiki [1], I believe >> >> that discussion contexts >> >> are important for further discussions and it also helps new >> >> contributors understand the background. >> >> >> >> In my proposal https://review.openstack.org/261767, >> >> we maintain all contexts in YAML glossary files. >> >> >> >> > 2. Process >> >> > >> >> > If people want to change the glossary, e.g. add, update, change the >> >> > comments, add coments >> >> > following process is designed. >> >> > >> >> > a> the requestor submits a patch to i18n repo >> >> > b> core team approve the patch >> >> > c> the auto uploading process is triggered. terminology.pot is >> >> > uploaded >> >> > to >> >> > Zanata for translation >> >> > d> translators finish translation >> >> > e> Zanata admin manually patch terminology.pot and its translationpo >> >> > files, >> > >> >> > and upload to Zanata >> >> >> >> IMO the glossary needs to be reviewed more carefully compared to >> >> regular translations. >> >> In regular translations, all translated strings are imported, but for >> >> glossary it is better that >> >> only reviewed strings are imported. Another choice is to use gerrit >> >> for the glossary review. >> >> My proposal https://review.openstack.org/261767 implements the latter >> >> option. >> >> >> >> Thought? >> >> >> >> Thanks, >> >> Akihiro >> >> >> >> > >> >> > Best regards >> >> > Ying Chun Guo (Daisy) >> >> > >> >> > >> >> > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2015/12/02 02:29:44: >> >> > >> >> >> From: Akihiro Motoki <amotoki(a)gmail.com> >> >> >> To: "openstack-i18n(a)lists.openstack.org" >> >> >> <Openstack-i18n(a)lists.openstack.org> >> >> >> Date: 2015/12/02 02:32 >> >> >> Subject: [Openstack-i18n] How do we manage glossary? >> >> > >> >> >> >> >> >> Hi team, >> >> >> >> >> >> Recently we added the glossary to the i18n repo [1]. >> >> >> I wonder how we can manage the glossary and am sending this mail. >> >> >> The glossary can be referred to in Zanata, so it would be useful. >> >> >> >> >> >> Mainly I have two questions. >> >> >> >> >> >> The first point is what is the expected process to manage the >> >> >> glossary. >> >> >> How can we update the glossary? >> >> >> When is it uploaded to Zanata for translations? >> >> >> >> >> >> The second point is how we can have the context. >> >> >> I think the second point is also important. >> >> >> Each entry in our glossary has some background, for example >> >> >> why we reach the current consensus. >> >> >> This kind of context is important to discuss for further >> >> >> improvements. >> >> >> >> >> >> I updated the glossary for Japanese translation last week >> >> >> and I added various description about backgrounds of the glossary. >> >> >> I feel it is important to keep the context. >> >> >> How can we manage the context? >> >> >> >> >> >> I don't have a good idea now. >> >> >> I would like to raise these questions for broader discussion. >> >> >> >> >> >> Thanks, >> >> >> Akihiro >> >> >> >> >> >> [1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n >> >> >> >> >> >> _______________________________________________ >> >> >> Openstack-i18n mailing list >> >> >> Openstack-i18n(a)lists.openstack.org >> >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >> >> >> >> > >> >> >> > >> >

1 0

Austin OpenStack Summit call-for-papers is open
by Ying Chun Guo 10 Jan '16

10 Jan '16

Hello, team The next OpenStack Summit will take place on April 25-29 in Austin, Texas, US. The Call for Papers is opened and will close on Feb 1st. You could find details on the tracks and process on the official page: https://www.openstack.org/summit/austin-2016/call-for-speakers/. I think following tracks are much related with our work. You are welcomed to submit speech proposals to these tracks. * Project Updates * How to Contribute * Upstream Development * Working Groups The track "Working Groups" is special. It is for collaborative working sessions rather than presentations. It will be in smaller rooms and video record will not be served. We can organize I18n/translations related working sessions in this track. If you have any speeches or discussion topics related with I18n/translations, you can contact with me. I'm happy to help review and schedule. BTW, the travel support program is opened at: https://www.openstack.org/summit/austin-2016/austin-and-travel/#travel-supp… . The deadline is Feb 9. Thank you. Best regards Ying Chun Guo (Daisy)

1 0

Re: [Openstack-i18n] Czech translation error
by Akihiro Motoki 07 Jan '16

07 Jan '16

I am not sure it is a bug of the source string. It works as the source language. The similar example is shown in the gettext documentation I quoted in the first mail. Apart from the warning you mentioned, after we change msgstr[0] to contain %s in a translation, the error disappears. IMHO, it is a bug of GNU gettext. On the other hand, I agree it is less confusing if the source string contains %s. Feel free to file a bug to horizon with a background. Akihiro 2016-01-07 18:19 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Hi, Akihiro > > It is a bug in the source code, isn't it ? > I don't see the translations are wrong. > > msgid is "Instance launched." > We cannot simply add %s to msgstr[0]. > Zanata will report a warning: Unexpected variable: %s > > I think the source string "Instance launched." should add %s firstly. > "Instance launched." should be changed to "Instance %s launched." > And then, the translation msgstr[0] should add %s correspondingly. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2016/01/07 01:44:42: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: "openstack-i18n(a)lists.openstack.org" >> <Openstack-i18n(a)lists.openstack.org> >> Date: 2016/01/07 01:46 >> Subject: [Openstack-i18n] Czech translation error > >> >> Hi Czech language team and i18n Zanata admin, >> >> Horizon translation import is broken due to Czech translation. >> This blocks all translation imports of horizon. >> Could you fix it? >> >> https://review.openstack.org/#/c/259677 >> >> The error is like this: >> http://logs.openstack.org/77/259677/15/check/gate-horizon-dsvm- >> integration/e5ed03e/logs/devstacklog.txt.gz#_2016-01-02_17_55_04_608 >> 2016-01-02 17:55:04.608 | CommandError: Execution of msgfmt failed: >> /opt/stack/new/horizon/openstack_dashboard/locale/cs/LC_MESSAGES/ >> djangojs.po:655: >> number of format specifications in 'msgid_plural' and 'msgstr[0]' does >> not match >> 2016-01-02 17:55:04.608 | msgfmt: found 1 fatal error >> >> The error point is: >> https://review.openstack.org/#/c/259677/15/openstack_dashboard/ >> locale/cs/LC_MESSAGES/djangojs.po >> >> I think we need to add %s to msgstr[0] to avoid msgfmt error. >> >> #, python-format >> msgid "Instance launched." >> msgid_plural "%s instances launched." >> msgstr[0] "Instance spuštěna. >> msgstr[1] "Spuštěny %s instance." >> msgstr[2] "Spuštěno %s instancí." >> >> >> BTW, I am not sure this is valid according to GNU gettext documentation >> [1], >> but msgfmt actually does not support this form. >> In the example of [1], msgid does not contain %s but all msgstr[n] contain >> %s. >> Although there is no explicit description, %s must be contained in all >> msgstr[n]. >> To avoid confusion, it is better to contain %s in 'msgid' (singular >> form) as well. >> >> [1] https://www.gnu.org/software/gettext/manual/html_node/ >> Translating-plural-forms.html >> >> >> Akihiro >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >

3 2

Czech translation error
by Akihiro Motoki 07 Jan '16

07 Jan '16

Hi Czech language team and i18n Zanata admin, Horizon translation import is broken due to Czech translation. This blocks all translation imports of horizon. Could you fix it? https://review.openstack.org/#/c/259677 The error is like this: http://logs.openstack.org/77/259677/15/check/gate-horizon-dsvm-integration/… 2016-01-02 17:55:04.608 | CommandError: Execution of msgfmt failed: /opt/stack/new/horizon/openstack_dashboard/locale/cs/LC_MESSAGES/djangojs.po:655: number of format specifications in 'msgid_plural' and 'msgstr[0]' does not match 2016-01-02 17:55:04.608 | msgfmt: found 1 fatal error The error point is: https://review.openstack.org/#/c/259677/15/openstack_dashboard/locale/cs/LC… I think we need to add %s to msgstr[0] to avoid msgfmt error. #, python-format msgid "Instance launched." msgid_plural "%s instances launched." msgstr[0] "Instance spuštěna. msgstr[1] "Spuštěny %s instance." msgstr[2] "Spuštěno %s instancí." BTW, I am not sure this is valid according to GNU gettext documentation [1], but msgfmt actually does not support this form. In the example of [1], msgid does not contain %s but all msgstr[n] contain %s. Although there is no explicit description, %s must be contained in all msgstr[n]. To avoid confusion, it is better to contain %s in 'msgid' (singular form) as well. [1] https://www.gnu.org/software/gettext/manual/html_node/Translating-plural-fo… Akihiro

4 4

IRC meeting today
by Ying Chun Guo 06 Jan '16

06 Jan '16

Hello, team I hope you had a good new year holiday. We will have our first IRC meeting in 2016 today, at 0600UTC in #openstack-meeting. I'm going to cover following topics: * Glossary management process discussion * Open discussions Feel free to propose other topics if you like. Best regards Ying Chun Guo (Daisy)

2 1

Re: [Openstack-i18n] How do we manage glossary?
by Kato, Tomoyuki 05 Jan '16

05 Jan '16

> >> Expected workflow: > >> * add an entry to the master glossary: > >> - Update glossary/master.yaml and review it on gerrit > >> - Once approved, glossary-tool sync will update per-language glossary > >> files and propose the update to gerrit (jenkins jos) > > > > In your design, when the changes to master.yaml is approved, how to trigger > > the jenkins job ? using a tag ? > > I think we could add one more action in this Jenkins job: automatically send > > an email to i18n to notify that the glossary is changed. > > We can use 'post' pipeline to trigger some jobs when each change is merged. I'm not fully contexted, but generally agree to 'post' pipeline idea. KATO Tomoyuki

1 0

Fw: [OpenStack-docs] Travel support for Summit, April 25-29, Austin, TX
by Ying Chun Guo 05 Jan '16

05 Jan '16

Hi, team If you need the travel support for Austin Summit, you could apply now. Best regards Ying Chun Guo (Daisy) ----- Forwarded by Ying Chun Guo/China/IBM on 2016/01/05 17:01 ----- Anne Gentle <annegentle(a)justwriteclick.com> wrote on 2016/01/05 01:43:00: > From: Anne Gentle <annegentle(a)justwriteclick.com> > To: "openstack-docs(a)lists.openstack.org" <openstack-docs(a)lists.openstack.org> > Date: 2016/01/05 01:45 > Subject: [OpenStack-docs] Travel support for Summit, April 25-29, Austin, TX > > Hi all, > Want to be sure that documentarians know about the travel support > program to get contributors to the Summit. Read all about it and apply here: > > https://www.openstack.org/summit/austin-2016/austin-and-travel/#travel-supp… > > Thanks, > Anne > > -- > Anne Gentle > Rackspace > Principal Engineer > www.justwriteclick.com_______________________________________________ > OpenStack-docs mailing list > OpenStack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

1 0

Re: [Openstack-i18n] How do we manage glossary?
by Akihiro Motoki 05 Jan '16

05 Jan '16

Hi Daisy and the team, 2015-12-17 19:35 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Hi, Akihiro > > Please let me know your comments to https://review.openstack.org/258924 I commented your above review. I proposed a counter proposal https://review.openstack.org/261767. This is just an idea. I am open to the input. Comments inline below. > Answers to your question: > > 1. Context > > The current solution in my patch could not satisfy this requirement about > context. > If we want to put context to glossary, we need to develop our own extension > of sphinx-build. > How do you think the priority to support context ? IMHO supporting contexts is important to make discussion on glossary productive. As you can see in Japanese glossary on OpenStack wiki [1], I believe that discussion contexts are important for further discussions and it also helps new contributors understand the background. In my proposal https://review.openstack.org/261767, we maintain all contexts in YAML glossary files. > 2. Process > > If people want to change the glossary, e.g. add, update, change the > comments, add coments > following process is designed. > > a> the requestor submits a patch to i18n repo > b> core team approve the patch > c> the auto uploading process is triggered. terminology.pot is uploaded to > Zanata for translation > d> translators finish translation > e> Zanata admin manually patch terminology.pot and its translation po files, > and upload to Zanata IMO the glossary needs to be reviewed more carefully compared to regular translations. In regular translations, all translated strings are imported, but for glossary it is better that only reviewed strings are imported. Another choice is to use gerrit for the glossary review. My proposal https://review.openstack.org/261767 implements the latter option. Thought? Thanks, Akihiro > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2015/12/02 02:29:44: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: "openstack-i18n(a)lists.openstack.org" >> <Openstack-i18n(a)lists.openstack.org> >> Date: 2015/12/02 02:32 >> Subject: [Openstack-i18n] How do we manage glossary? > >> >> Hi team, >> >> Recently we added the glossary to the i18n repo [1]. >> I wonder how we can manage the glossary and am sending this mail. >> The glossary can be referred to in Zanata, so it would be useful. >> >> Mainly I have two questions. >> >> The first point is what is the expected process to manage the glossary. >> How can we update the glossary? >> When is it uploaded to Zanata for translations? >> >> The second point is how we can have the context. >> I think the second point is also important. >> Each entry in our glossary has some background, for example >> why we reach the current consensus. >> This kind of context is important to discuss for further improvements. >> >> I updated the glossary for Japanese translation last week >> and I added various description about backgrounds of the glossary. >> I feel it is important to keep the context. >> How can we manage the context? >> >> I don't have a good idea now. >> I would like to raise these questions for broader discussion. >> >> Thanks, >> Akihiro >> >> [1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >

2 1

Re: [Openstack-i18n] Transifex
by Ian Y. Choi 22 Dec '15

22 Dec '15

Hello Daisy, Thank you so much for your kind explanation. I agree that all of translation data are successfully moved to Zanata, and I have no objection to remove current Transifex not to be confused for OpenStack translation contributor candidates. I just worried that some guys might want to see previous Transifex history: who contributed to OpenStack translations later, since, the author of translation results from Transifex to Zanata is "OpenStack Infra", not actual translators, as far as I know. However, I also think that it is very difficult to keep all the history to public. For my OpenStack translation stuff, I do not need Transifex any more. So if other translators also do not need to see to track previous translators in Transifex, then there is no more additional reason to remove Transifex except querying statistics. And one more idea: although some previous translators are not regarded as ATC, I think it would be much better to mention their Transifex ID (at least) to acknowledge their previous contribution or credit on somewhere, such as OpenStack wiki. Let's discuss on today IRC meeting :) With many thanks, /Ian Ying Chun Guo wrote on 12/17/2015 2:39 PM: > > Ian Y, > > I will not use the official i18n repo to store those materials. > I plan to store it in a personal repo in github, > just to keep the history. > > We have moved all data into Zanata while we migrated to Zanata in > September. > 4 months passed, we didn't get any complains about any missing data. > We could be sure that all data have been moved to the new tool. > So it's not that necessary to back up. > > The only reason to support to not delete OpenStack from Transifex is that: > it's easy to query the contribution data in any certain period through > the web UI of Transifex. > If we remove OpenStack from Transifex, we will lost the ability to query. > I could export the contribution data for a certain period, for > example, the last 3 years, from Transifex, > and store the export data somewhere. > But I will lost the ability to query any periods, for example, the > data from 2015.4-2015.10 will not be able to get. > > So we could discuss whether we need this ability in the meeting today. > If we don't need, Transifex is no use for us. We could delete it safely. > > Best regards > Ying Chun Guo (Daisy) > > > "Ian Y. Choi" <ianyrchoi(a)gmail.com> wrote on 2015/12/17 12:21:34: > > > From: "Ian Y. Choi" <ianyrchoi(a)gmail.com> > > To: Ying Chun Guo/China/IBM@IBMCN, Andreas Jaeger <aj(a)suse.com> > > Cc: Robert Simai <robert.simai(a)suse.com>, > openstack-i18n(a)lists.openstack.org > > Date: 2015/12/17 12:22 > > Subject: Re: [Openstack-i18n] Transifex > > > > Hello Andreas, > > > > I am copying & pasting from Andreas's comment to this thread: > > > > +++ > > "Sorry, let me clarify this again: > > * ATC is one year (voting rights for i18n) > > * Free passes for OpenStack conference is 6 months > > > > For ATC, you could take a one time snapshot as well now - going back > > to 1st of April, instead of saving it for later," > > > > > > => Thank you so much for your nice clarification on ATC status and > > summit free passes. > > > > We would vote this issue (removing on Transifex site) on today's IRC > > meeting, and yes. > > We need contribution statistics data from Transifex, and I agree that > > we can query and save Transifex statistics data (from April 1 2015 > > to now) and later > > we would merge this data with Zanata statistics data on next April. > > > > And I am not sure exactly, but we might use openstack/i18n repo to > > store Transfex related data > > into a specific branch, not a master branch. > > > > > > With many thanks, > > > > /Ian > > > > > > Ying Chun Guo wrote on 12/17/2015 1:21 AM: > > If we don't need the contribution data in Transifex, I think we > > could remove it. > > > > As to the back up, it's a personal habit. I just want to keep it as > > the history. > > I will use a repo in github to store the documents, including an > > Excel file with the contribution statistic data. > > > > Best regards > > Ying Chun Guo (Daisy) > > > > > > -----Andreas Jaeger <aj(a)suse.com> wrote: ----- > > > > >To: "Ian Y. Choi" <ianyrchoi(a)gmail.com>, Robert Simai > > ><robert.simai(a)suse.com> > > >From: Andreas Jaeger <aj(a)suse.com> > > >Date: 12/16/2015 09:59PM > > >Cc: openstack-i18n(a)lists.openstack.org > > >Subject: Re: [Openstack-i18n] Transifex > > > > > >On 2015-12-16 14:45, Andreas Jaeger wrote: > > >> On 2015-12-16 14:34, Ian Y. Choi wrote: > > >>> Hello Robert, > > >>> > > >>> As far as I remember, on the last i18n irc meeting (Dec 03 2015 +6 > > >UTC), > > >>> we discussed this issue. > > >>> > > >>> During the meeting, meeting attendees found that querying to > > >Transifex > > >>> statistics data > > >>> is needed to check ATC status for the next OpenStack release, > > >Mitaka. > > >> > > >> ATC status is handed out only for people active in the current > > >release, > > >> so for the next summit in Austin, only for people that were active > > >in > > >> Mitaka time frame. And since we used Zanata for all of Mitaka, > > >there's > > >> no need to query transifex IMO. > > >> > > >> Katamo is wrong with ATC status for one year, this has changed, > > > > > >See > > >https://ask.openstack.org/en/question/45531/atc-pass-for-the-openstac > > >k-summit/ > > >with information for Tokyo summit (1st of April was cut-off-date), > > > > > >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 > > > > > > > > >_______________________________________________ > > >Openstack-i18n mailing list > > >Openstack-i18n(a)lists.openstack.org > > >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > > > > >

5 5

How do we manage glossary?
by Akihiro Motoki 17 Dec '15

17 Dec '15

Hi team, Recently we added the glossary to the i18n repo [1]. I wonder how we can manage the glossary and am sending this mail. The glossary can be referred to in Zanata, so it would be useful. Mainly I have two questions. The first point is what is the expected process to manage the glossary. How can we update the glossary? When is it uploaded to Zanata for translations? The second point is how we can have the context. I think the second point is also important. Each entry in our glossary has some background, for example why we reach the current consensus. This kind of context is important to discuss for further improvements. I updated the glossary for Japanese translation last week and I added various description about backgrounds of the glossary. I feel it is important to keep the context. How can we manage the context? I don't have a good idea now. I would like to raise these questions for broader discussion. Thanks, Akihiro [1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n

2 1

Re: [Openstack-i18n] Transifex
by Ian Y. Choi 16 Dec '15

16 Dec '15

Hello Andreas, I am copying & pasting from Andreas's comment to this thread: +++ "Sorry, let me clarify this again: * ATC is one year (voting rights for i18n) * Free passes for OpenStack conference is 6 months For ATC, you could take a one time snapshot as well now - going back to 1st of April, instead of saving it for later," => Thank you so much for your nice clarification on ATC status and summit free passes. We would vote this issue (removing on Transifex site) on today's IRC meeting, and yes. We need contribution statistics data from Transifex, and I agree that we can query and save Transifex statistics data (from April 1 2015 to now) and later we would merge this data with Zanata statistics data on next April. And I am not sure exactly, but we might use openstack/i18n repo to store Transfex related data into a specific branch, not a master branch. With many thanks, /Ian Ying Chun Guo wrote on 12/17/2015 1:21 AM: > If we don't need the contribution data in Transifex, I think we could > remove it. > > As to the back up, it's a personal habit. I just want to keep it as > the history. > I will use a repo in github to store the documents, including an Excel > file with the contribution statistic data. > > Best regards > Ying Chun Guo (Daisy) > > > -----Andreas Jaeger <aj(a)suse.com <mailto:aj@suse.com>> wrote: ----- > > >To: "Ian Y. Choi" <ianyrchoi(a)gmail.com <mailto:ianyrchoi@gmail.com>>, > Robert Simai > ><robert.simai(a)suse.com <mailto:robert.simai@suse.com>> > >From: Andreas Jaeger <aj(a)suse.com <mailto:aj@suse.com>> > >Date: 12/16/2015 09:59PM > >Cc: openstack-i18n(a)lists.openstack.org > <mailto:openstack-i18n@lists.openstack.org> > >Subject: Re: [Openstack-i18n] Transifex > > > >On 2015-12-16 14:45, Andreas Jaeger wrote: > >> On 2015-12-16 14:34, Ian Y. Choi wrote: > >>> Hello Robert, > >>> > >>> As far as I remember, on the last i18n irc meeting (Dec 03 2015 +6 > >UTC), > >>> we discussed this issue. > >>> > >>> During the meeting, meeting attendees found that querying to > >Transifex > >>> statistics data > >>> is needed to check ATC status for the next OpenStack release, > >Mitaka. > >> > >> ATC status is handed out only for people active in the current > >release, > >> so for the next summit in Austin, only for people that were active > >in > >> Mitaka time frame. And since we used Zanata for all of Mitaka, > >there's > >> no need to query transifex IMO. > >> > >> Katamo is wrong with ATC status for one year, this has changed, > > > >See > >https://ask.openstack.org/en/question/45531/atc-pass-for-the-openstac > >k-summit/ > >with information for Tokyo summit (1st of April was cut-off-date), > > > >Andreas > >-- > > Andreas Jaeger aj(a){suse.com <mailto:aj@%7Bsuse.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 > > > > > >_______________________________________________ > >Openstack-i18n mailing list > >Openstack-i18n(a)lists.openstack.org > <mailto:Openstack-i18n@lists.openstack.org> > >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > >

2 1

IRC meeting today
by Ying Chun Guo 16 Dec '15

16 Dec '15

Hi, team We will have IRC meeting today, at 1300UTC in #openstack-meeting. I'm going to cover following topics. * Status update: Liberty installation guide translation * Discussion: Midcycle spring/virtual spring * Vote: delete OpenStack from Transifex * Open discussions Feel free to propose other topics if you like. Best regards Ying Chun Guo (Daisy)

1 0

Transifex
by Ying Chun Guo 16 Dec '15

16 Dec '15

Hello, team I have handled all the team join requests to OpenStack in Transifex, sending emails to inform the tool change and then rejecting them. I noticed there was no translations happened in Transifex after Oct. I think we could start to remove Openstack projects from Transifex. We may find a place to back up firstly, and then remove. Any objections to the remove ? Any suggestions about the back up ? Best regards Ying Chun Guo (Daisy)

4 6

How to set accept language tag to Dutch (nl) in OpenStack Tempest test framework?
by durga rao 15 Dec '15

15 Dec '15

I have latest tempest downloaded from GitHub.Here is my test requirement:We have a set of test scripts for compute, storage and network. For all the REST calls made by tempest test framework, I want to set the "Accept Language" tag to Dutch [nl] (Netherlands Dutch).It might just be one configuration file change. I want to know the configuration file that needs to be changed.Quick response is appreciated.Thank you

1 0

What's Up, Doc? Holiday Edition
by Lana Brindley 10 Dec '15

10 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, This is my final newsletter for the year, as I'm taking summer vacation over the next few weeks (yay for Southern Hemisphere weather!). Your regularly scheduled programming will resume in mid-January. I would like to take a moment to acknowledge the incredible work of the entire documentation team, especially the core team who have worked all year to keep on top of reviews, the speciality team leads who motivate and inspire their teams each and every day, and every single documentation contributor and reviewer: without you all doing your little bit, we wouldn't have had the success we have had. Thank you also to our crew of support people: from infra and release management, to our subject matter experts and the wonderful people on the TC and at Foundation. Thanks for helping us be the best we can be. I would also like to make special mention of Andreas Jaeger and Anne Gentle, who both continue to hold my hand daily and make sure I don't make too much of a fool of myself in public. Your support and encouragement have been invaluable. While we're on the goodwill wagon: if there's someone (or something!) you would like to call out for a special mention, you can do so using #success in our IRC channel. All successes get logged here: https://wiki.openstack.org/wiki/Successes and it's a great way to show your appreciation for your fellow community members. == Progress towards Mitaka == 117 days to go! 150 bugs closed so far for this release. RST Conversions * Arch Guide ** RST conversion is complete! Well done Shilla and team for getting this done so incredibly quickly :) * Config Ref ** Is underway: contact the Config Ref Speciality team: https://wiki.openstack.org/wiki/Documentation/ConfigRef * Virtual Machine Image Guide ** Is complete! Well done Tomoyuki-san :) Reorganisations * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Doc sprint planned for December 21-22. Contact the Ops Guide speciality team for more info or to get involved. ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * User Guides ** https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… ** Contact the User Guide Speciality team: https://wiki.openstack.org/wiki/User_Guides DocImpact * Waiting to merge the patch for the new Jenkins job: https://review.openstack.org/#/c/251301/ which for now will be against Nova only so we can make sure it's working correctly before we roll it out across the board. Document openstack-doc-tools and reorganise index page * Thanks to Brian and Christian for volunteering to take this on! Horizon UX work * Thanks to the people who offered to help out on this! If you're interested but haven't gotten in touch yet, contact Piet Kruithof of the UX team. There is now a blueprint + spec in draft: https://blueprints.launchpad.net/openstack-manuals/+spec/ui-content-guideli… and https://review.openstack.org/#/c/252668/ == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' The change to shift IRC meeting was not accepted. Going to create a new poll this time with correct options suggested by Tony Breeds. No more updates. '''Installation Guide - Christian Berendt''' We require Debian Install Guide testers. Please contact Christian if you're interested. '''Networking Guide - Edgar Magana''' The networking guide had its first official IRC meeting: https://wiki.openstack.org/wiki/Documentation/NetworkingGuideMeetings We are restructuring a little bit the wikis for better engagement with new contributors; Versioning spec for networking guide has been merged: https://review.openstack.org/#/c/253283/ Working of the remaining actions items from the meeting: http://eavesdrop.openstack.org/meetings/networking_guide/2015/networking_gu… We have proposed a time and date for an IRC meeting covering APAC time zone: https://review.openstack.org/#/c/254999/ '''Security Guide - Nathaniel Dillon''' Planning for a bug sprint and general triage/cleanup. '''User Guides - Joseph Robinson''' The User Guide Reorganization Spec merged this week, and the final User Guide meeting for 2016 has been rescheduled to next Thursday December 16 at 23:30 UTC, and the plan is to discuss work items. A patch for the User Guide Dashboard has begun using the blueprint implementation as a start to the reorg. '''Ops and Arch Guides - Shilla Saebi''' Regarding this spec - https://review.openstack.org/#/c/227660/, we decided we are going to hold off until the N-release; Architecture Guide Swarm - Asking for everyone who wants to help to please use the https://etherpad.openstack.org/p/arch-guide-reorg to document potential changes; The arch guide RST conversion is complete; For the swarm, everyone works in their timezone. They will then submit patches and allocate team members in the other timezones to review; The final dates for the arch guide virtual swarm is: 12/21-12/22. '''API Docs - Anne Gentle''' Trimming down what is output so that eventually we'll get working Swagger migrated from WADL. Repo still awaits being pulled into gerrit: https://github.com/russell/fairy-slipper to https://review.openstack.org/#/c/245352/ Nova API docs sprint 12/8 and 12/9 came up with good questions and answers and patches. Also, the Gabbi API test suite has a new release, see http://lists.openstack.org/pipermail/openstack-dev/2015-December/081891.html '''Config Ref - Gauvain Pocentek''' The configuration reference RST migration is almost done, only a few more Block Storage drivers docs to handle. Thanks to all the contributors! '''Training labs - Roger Luethi''' Training-labs merged a KVM provider patch which allows the training cluster to build on top of KVM. The IP address ranges now match the install guides. The Liberty training cluster is being worked on. '''Training Guides - Matjaz Pancur''' Through no fault of Matjaz', this report was erroneously left out of the last newsletter, sorry for the delay: A complete Korean translation of the Upstream training material is officially published at http://docs.openstack.org/ko_KR/upstream-training/ (big thanks to Ian Y. Choi and KATO Tomoyuki) '''Hyperviser Tuning Guide - Joe Topjian''' Finished the first pass of converting etherpad notes to the wiki. I sent an email <http://lists.openstack.org/pipermail/openstack-operators/2015-December/0091…> to the openstack-operators with a summary of the current state. Hopefully the guide will pick up two or three regular contributors to help things along. I'll continue to work on it 1-2 hours a week as I get time. == Core Team Changes == I would like to offer a warm welcome to Atsushi Sakai as our newest core team member. Welcome to the team :) We will resume regular reviews in February 2016. == Doc team meeting == We failed to hold the APAC docs meeting this week because I can't read a calendar, and clearly just need a holiday. My apologies! Next meetings: US: Wednesday 16 December, 14:00 UTC APAC: Will resume in the new year Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… - -- Happy holidays everyone, and remember to ... Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWaj4RAAoJELppzVb4+KUyFoAH/jVqenzze6Pl6xF68dKBwouT ij8j80wBMdbUzyn4zc4726uxQ1TMdzXgK+8Q8Ouk4fOewn6cV9rOZJelpSPSboOR Lv4mjm172UxqnrN1npy5f9tB9EnIC/R8N0KlZHJmD0YJ/EbiJ0Hv/wl4/6+f8L7D Ns6iIUylI62a/ycIs7Wz5RGASaMZpZaP1XEeQtUoXbpIHggTlxPcHgETayHVnBMl 5qIuG5B5fgIOdUKQAa41SuMRCttxyHStXCFM/lborpDd6vEbMR2S/UbJb+7zh0jK PIACfhsnnZCBiZqno9NFnxBehdqTXpDG3crG0I9Ajd2YnEdhmFro+jMQr56lkGE= =1Kk+ -----END PGP SIGNATURE-----

1 0

What's Up, Doc? 4 December 2015
by Lana Brindley 08 Dec '15

08 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, Slight delay in the newsletter this time around, it's been a busy week! I've been working on the DocImpact changes, reviewing the docs and docs-specs core teams, and catching up with blueprint management and reviews from while I was on leave. Since we're getting to the pointy end of the year, remember to call out successes using #success in our IRC channel. All successes get logged here: https://wiki.openstack.org/wiki/Successes and it's a great way to show your appreciation for your fellow community members. == Progress towards Mitaka == 121 days to go! 139 bugs closed so far for this release. RST Conversions * Arch Guide ** RST conversion is complete! Well done Shilla and team for getting this done so incredibly quickly :) * Config Ref ** Contact the Config Ref Speciality team: https://wiki.openstack.org/wiki/Documentation/ConfigRef * Virtual Machine Image Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/image-guide-rst and https://review.openstack.org/#/c/244598/ Reorganisations * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Doc sprint in planning for December 21-22. Contact the Ops Guide speciality team for more info or to get involved. ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * User Guides ** https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… ** Contact the User Guide Speciality team: https://wiki.openstack.org/wiki/User_Guides DocImpact * This is now well underway, with the first two patches merged. One changes the default bug queue for DocImpact back to the projects' own queue, and the other changes all current projects (with the exception of the six defcore projects) to their own bug queue. There has also been some discussion on the mailing lists about this process change. The next step is to merge the new Jenkins job (https://review.openstack.org/#/c/251301/) which for now will be against Nova only so we can make sure it's working correctly before we roll it out across the board. Thank you to Andreas, Josh Hesketh, and everyone else who has helped get us this far, and to the Nova team who are allowing us to use them as guinea pigs. Document openstack-doc-tools and reorganise index page * Thanks to Brian and Christian for volunteering to take this on! Horizon UX work * Thanks to the people who offered to help out on this! If you're interested but haven't gotten in touch yet, contact Piet Kruithof of the UX team. There is now a blueprint + spec in draft: https://blueprints.launchpad.net/openstack-manuals/+spec/ui-content-guideli… and https://review.openstack.org/#/c/252668/ == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' Finished IRC meeting schedule poll, finalised the Corosync/pacemaker patch (https://review.openstack.org/235893) participating and tracking progress with the HA for OpenStack instances research (https://etherpad.openstack.org/p/automatic-evacuation) to make it into the HA guide, eventually. '''Installation Guide - Christian Berendt''' Debian install guide nearly completed, testers needed; meeting time for the EU/US meeting will probably change from 13 UTC to 17 UTC; Aodh install instructions nearly finished, ongoing discussion because of missing SUSE packages; Japanese translation of the Liberty install guide published. '''Networking Guide - Edgar Magana''' We are having our first official IRC meeting tomorrow at 1600 UTC. The goal is to find out what we can to complete during the Liberty cycle and have specific tasks assigned. Relevant patches: Create tags for the Networking Guide - WIP (https://review.openstack.org/#/c/251979/) '''Security Guide - Nathaniel Dillon''' No update this week '''User Guides - Joseph Robinson''' The User guide meeting on IRC worked, however attendance was down; the reorganization spec is updated with information from Big Tent Project navigator to define the scope (http://www.openstack.org/software/project-navigator) and information from the published nova-network to neutron migration study. '''Ops and Arch Guides - Darren Chan''' The arch guide RST conversion is completed. We plan on doing a virtual swarm this December. The doodle link was sent out last week and the poll is now closed. The final date for the virtual swarm is: 12/21-12/22. '''API Docs - Anne Gentle''' Working on usage docs for migration, how to build, what gets migrated, how the docs are assembled: https://github.com/russell/fairy-slipper/blob/master/doc/source/usage.rst Responding to spec reviews: https://review.openstack.org/#/c/246660/ Revising patch to bring fairy-slipper into openstack org: https://review.openstack.org/#/c/245352/ '''Config Ref - Gauvain Pocentek''' The RST migration is still in progress. The Manila section has been greatly improved in the process, and the Zaqar documentation should land during this cycle as the spec has been approved. '''Training labs - Pranav Salunke''' KVM port is almost done. Planned to merge this by end of this week; Network configuration for the cluster is updated. Now it uses same network addresses as install guides; Welcome berndbausch into our team; Liberty port is in progress. Follow https://etherpad.openstack.org/p/training-labs-liberty for more details; Need to decide meeting time for weekly IRC meetings. '''Training Guides - Matjaz Pancur''' No update this week '''Hyperviser Tuning Guide - Joe Topjian''' Still on schedule. Halfway done with a first-pass cleanup. Should be ready for open contributions within 2 weeks. == Core Team Changes == During last week, I announced some changes to the docs-specs core team. Previously, this core team was a small subset of docs core team members, with an understanding that we would wait for speciality team leads to +1 a spec relevant to their team before approving. Now we have formalised that process by inviting each speciality team lead to the docs-specs core team, so that they can +2A their own specs. Speciality team leads are listed on the wiki here: https://wiki.openstack.org/wiki/Documentation/SpecialityTeams remember to engage them when you create a new spec for approval. We have also reviewed the current docs core team list for December, and the results of that will be announced shortly. We will not be reviewing the team in January because of the holiday period, and will resume regular reviews in February 2016. == Doc team meeting == We held the APAC docs meeting this week. Big thanks to Joseph for running that while I was away, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-11-25 Next meetings: US: Wednesday 9 December, 14:00 UTC APAC: Wednesday 16 December, 00:30:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… - -- Just a note that this will be my penultimate newsletter for 2015. Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWZPzNAAoJELppzVb4+KUyT+IH/0yFFN5+X1WG5mbq+SUK0DnP av+pdcVbIlVpSuVgI5rV69ri3TwnU9DmFyJfOcx7h3ZRib3ri3T09UQ7L4A/EvfL Ar+AzG0OLriSLz1WJEVhg8VYkVuxVugIfAUvrKyNPIQs9sbDHQfmnpYoyZ8LB/TK tXd6+R15yMt+2KOPfKT2UMj8NUhf+XYxEpuW8TCTNss3GWlQZBHy9USNFfat+rzY MaLpUGGG6dviKgWGStGOD4I2JUIswobqFRdOKJ0a3h7vDEPeJMkr+OHDG3wzNMx7 n2TL5jAf2teIoys0sLP7qVRBD/c4cQHIGi0C70iWlqSrbG80yq27Prc0cJrl/VA= =rNRL -----END PGP SIGNATURE-----

1 1

Chinese (zh_CN) translations are broken
by Andreas Jaeger 06 Dec '15

06 Dec '15

The import of openstack-manuals for zh_CN fails: On liberty for doc/common-rst/source/locale/common-rst On stable for install-guide In both cases, there's a Backspace character in there (0x08 Unicode). I'm removing all these backspaces now and ask the translators to be careful, 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 7

CLI Reference translations
by Andreas Jaeger 06 Dec '15

06 Dec '15

Hi The CLI reference is autogenerated from the output of our command line clients and currently has no translations, I suggest to not translate it at all and have proposed a change to do so. It currently is just a lot of noise in openstack-manuals with the source pot files whenever we do an update (see https://review.openstack.org/#/c/253794/) If there's interest later to translate the CLI reference, we can enable it again, Andreas Change: https://review.openstack.org/253803 -- 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

Re: [Openstack-i18n] Chinese (zh_CN) translations are broken
by Andreas Jaeger 04 Dec '15

04 Dec '15

On 2015-12-04 10:32, Ying Chun Guo wrote: > I have connected with the translator and he has found the problem. > He said it was caused by the input method. > He has solved the problem. > > Thank you Andreas for the information. Thanks, Daisy! Everything looks fine now, 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

Install Guide translation
by KATO Tomoyuki 03 Dec '15

03 Dec '15

Hi team, especially Czech member, Just a reminder. As mentioned a days ago, the translation resource of Install Guide for Liberty is "stable-liberty" version at Zanata. "master" version is a draft for Mitaka. Also, to be honest, the guide may be heavily rewrited for Mitaka. Regards, KATO Tomoyuki > On 2015-11-17 10:49, Ying Chun Guo wrote: > > Hi, Andreas > > > > I see stable/liberty is created in the repo of openstack-manuals, > > and stable-liberty version is created for openstack-manuals project in > > Zanata. > > Thank you for handling these. > > > > Is the installation guide in the master branch keeping open for Mitaka > > release? > > Yes. > > > So in order to translate Liberty installation guide, our translators should > > go to stable-liberty and work there. > > Correct. > > > I have changed the link of openstack manuals in the home page > > translation plan > > to stable-liberty version. > > Correct me if I'm wrong. > > Looks fine > > Andreas

1 0

Re: [Openstack-i18n] Chinese (zh_CN) translations are broken
by Andreas Jaeger 03 Dec '15

03 Dec '15

On 2015-12-03 09:43, Ying Chun Guo wrote: > Thank you, Andreas. > > Could you tell me what are source strings of the bad translations? > I will take a look and investigate the history. For liberty, it was all strings of the form "`Bugs: OpenStack Block Storage (cinder) <https://bugs.launchpad.net/cinder>`__" 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

3 2

Re: [Openstack-i18n] [OpenStack-docs] Usage of custom RST directives
by Lana Brindley 02 Dec '15

02 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 How will it impact translation? L On 02/12/15 23:21, Mariia Zlatkova wrote: >> >> At the moment I am not sure if I like it or not. But I think the usage of >> custom RST directives should be discussed on the list and if we decide to >> use custom RST directives they should be documented in the contributor >> guide. >> > > I think it makes sense to add this directive to the Contributor Guide (not > to copy and paste files to the repository and then update them manually). > > Maria > > On Wed, Dec 2, 2015 at 2:45 PM, Olena Logvinova <ologvinova(a)mirantis.com> > wrote: > >> At the moment I am not sure if I like it or not. But I think the >>> usage of custom RST directives should be discussed on the list and if >>> we decide to use custom RST directives they should be documented in >>> the contributor guide. >> >> >> I like the way a document looks like if we use this directive - it becomes >> smaller and, therefore, looks nicer. =) >> So I vote for adding this directive to the Contributor Guide conventions. >> >> Thanks >> Olena >> >> On Wed, Dec 2, 2015 at 1:17 PM, Gauvain Pocentek < >> gauvain.pocentek(a)objectif-libre.com> wrote: >> >>> Le 2015-12-02 11:31, Christian Berendt a écrit : >>> >>>> Hello everybody. >>>> >>>> While reviewing a review request for the new config-rst-guide I saw >>>> the usage of the RST directive "remote-code-block". I never saw this >>>> directive before and after searching for the definition I only found >>>> >>>> https://github.com/openstack/openstack-manuals/blob/master/doc/config-ref-r… >>>> . >>>> >>> >>> This particular directive tries to reproduce the docbook <xi:include> >>> behaviour, to avoid adding loads of sample file in our tree. I'm guilty of >>> adding it to the config-ref-rst folder. >>> >>> >>>> At the moment I am not sure if I like it or not. But I think the >>>> usage of custom RST directives should be discussed on the list and if >>>> we decide to use custom RST directives they should be documented in >>>> the contributor guide. >>>> >>> >>> Agreed. To be honnest I planned to write to the ML but it just slipped my >>> mind. >>> >>> >>> Gauvain Pocentek >>> >>> Objectif Libre - Infrastructure et Formations Linux >>> http://www.objectif-libre.com >>> >>> >>> _______________________________________________ >>> OpenStack-docs mailing list >>> OpenStack-docs(a)lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs >>> >> >> >> >> -- >> Best regards, >> Olena Logvinova, >> Technical Writer | Mirantis, Kharkiv | 38, Lenin av., Kharkiv >> ologvinova(a)mirantis.com | +380950903196 >> >> _______________________________________________ >> OpenStack-docs mailing list >> OpenStack-docs(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs >> >> > > > > > _______________________________________________ > OpenStack-docs mailing list > OpenStack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs > - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWX3PhAAoJELppzVb4+KUyD5IIAI78AYaDM00xzv1rmSyd7Pg1 3p0NrvZD2BtLPEiCq42B5DRWf2XNNnzbFGyqWvyT8ShD/94pr+5ASGceKv5t8P7H Rn0Gkc6idGKsv53ZKxWRHwizCm8mt+3VPiOQYZYhK4ghFII/mBY8kYNwnRQyyYHv rU5tdLNqOAlq36WqmVVbOUh0C3Rf3+YPs3BjcWNnnqVx11C/tPYJ5LR7oNHxW3jJ ZP0wZe9i/+6yOtH5dDxj0k4WnwXvdfXQPIAlHbpY1FvJUl8vsRMxrEe7s10AmpTS D2UybNqPg79PBdg7CUX6c72r+ASPw+LZTJeJm3vVpWY4izpmezZWt30drEUIgkU= =gnC5 -----END PGP SIGNATURE-----

2 1

IRC meeting tomorrow
by Ying Chun Guo 02 Dec '15

02 Dec '15

Hello, team We will have IRC meeting tomorrow at 0600 UTC in the IRC channel #openstack-meeting. I'm going to cover following topics tomorrow. * Discussion: Bug management process in Launchpad * Discussion: Glossary management process * Open discussions If you have more topics, please propose freely. Best regards Ying Chun Guo (Daisy)

1 0

Re: [Openstack-i18n] [OpenStack-docs] [openstack-dev] DocImpact Changes
by Lana Brindley 01 Dec '15

01 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 02/12/15 12:53, Armando M. wrote: > On 24 November 2015 at 13:11, Lana Brindley <openstack(a)lanabrindley.com> > wrote: > > Hi Akihiro, > > Judging by most of the bugs we see in the openstack-manuals queue, the > bugs that will be raised in projects' own queues will usually be against > their own developer documentation. > > >> I am a bit confused. The developer documentation coexists with the code >> that's being patched. Is this the documentation you're referring to? So for >> instance in Neutron we have [1] rendered into [2]. That's correct. > >> I always assumed that DocImpact was needed to flag configuration changes, >> and more generally user facing issues, and these are not captured in the >> developer doc [2] (afaik, *-aas services do have a developer documentation >> but no entry point in [4]), as developers are not the audience, but rather >> guide [3]. On the other hand, if patches do require dev doc changes (like >> design issues etc), reviewers tend to ask to take care of them in the >> context of the same patch, without the burden of going through an extra bug >> report. I agree, and that was the original intention, however it doesn't get used that way in the majority of cases we see. Feel free to use DocImpact (with a description), and then manually flip the bug to openstack-manuals in this case. > >> So the fact that Neutron's DocImpact changes raises a bug report in LP >> Neutron seems counterintuitive, and I am a bit at loss here. Can you >> elaborate on what was the rationale for making only certain projects target >> their own queues? I wouldn't want to have bug reports be reassigned to the >> right queue only to cause more burden that this initiative originally >> intended to relieve. We chose the five 'defcore' projects here, as they are the ones that are formally (and most extensively) documented in openstack-manuals. > >> Having said that, let's assume we are stricter about what gets flagged with >> DocImpact, would you be open to revisiting the doc group for Neutron as set >> in [5]? In the meantime, I'll go ahead and look at the outstanding patches >> and bug reports recently filed to sanitize with the best of my abilities. As we noted in the original spec, we appreciate that Neutron is on the cusp of being considered 'defcore', and we're happy to include it once that has happened formally. Thanks for your help. Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWXmDwAAoJELppzVb4+KUyezMH/3WuKrW+8Py9XU3o2vddCK4c ZovehU0Xq1mHzzpfh8Vfc71MfJVAtotr9Lt0Vd5b4jAnjSWz7QI4/W2CG3d+aM+L FYPDn9koTC/+EsXlz8ekzLQUz6PToa21jfdmcg6tSAPA09FV5j7SPWIPXD9bvzun q9NWhs3jjj4hVtgUhmFdeC7B0vDzT6EWU2kAuSWwUEf7z2c3S7ZnuteyOKLf6aLZ rRbZi59ras8/3jI9EY8h6Wk47gQ3fLwvYyL/tHU9c2jOGPPz47f7HKaXVO0MQ58p E4V3nhGEITt3NMQH8m0IEW7JLd3tRX1C7ERKK05+k5yl7dirxKsysq52xJh0EMo= =1mW1 -----END PGP SIGNATURE-----

1 0

Translation warnings (Re: [OpenStack-docs] Code block in RST and translation)
by Akihiro Motoki 01 Dec '15

01 Dec '15

2015-11-25 23:54 GMT+09:00 Andreas Jaeger <aj(a)suse.com>: > On 2015-11-25 15:48, KATO Tomoyuki wrote: >>> >>> >>>> On 25 Nov 2015, at 03:41, KATO Tomoyuki <tomo(a)dream.daynight.jp> wrote: >>>> >>>>> My idea at now is to use "code-block" directive as possible as we can, >>>> >>>> >>>> As far as I know, docs team guides mainly use "code-block". >>>> So, I'm okay to unify to "code-block" directive. >>>> >>>>> but I am not sure it is the right direction as "::" is widely used. >>>> >>>> >>>> In my understand, most of developers like “::”, which is simple RST >>>> format :) >>> >>> >>> Maybe we could add a gate check that looks for “::” in the end of the >>> strings (original and translated)? It would enable developers to use >>> whatever they are used to. >> >> >> Nice idea! Sounds good to me, as a non-vote job. >> >> Regards, >> KATO Tomoyuki > > > But who will monitor this and correct it? > > We already see warnings in translated code that everybody ignores, let's > find a good way to monitor and fix these problems first before we add > more tests... I think this kind tests are categorized into two: (a) to detect anti-patterns which are not good for translations. (b) to detect warnings when building translation documents. I have no good idea on who monitors it. (b) can be a periodic job and language translators need to check them. Related to (b) warnings in translation documents, I cleaned up warnings in Japanese translations last night. At now, Japanese documents have no warnings except https://bugs.launchpad.net/openstack-manuals/+bug/1521473. Most of them can be fixed by - adding an extra white space after closing RST markups such as `` or **, or - removing extra white spaces at beginning or end of strings wrapped by RST markups. Even with these warnings, translated documents are rendered properly. On the other hand, some warnings are actually due to translation mistakes to be fixed. This turns out that checking warnings is still important. Akihiro > > 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 > > > > _______________________________________________ > Openstack-i18n mailing list > Openstack-i18n(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

2 1

Upstream Training material publication
by KATO Tomoyuki 30 Nov '15

30 Nov '15

Hi team, Happily, we have new translation feature for Upstream Training material. Also, translation publication job is enabled at now. For ONLY this guide, the translated guide is published immediately. Amazingly, Korean team has almost finished translation. Congrats! http://docs.openstack.org/ko_KR/upstream-training/ Regards, KATO Tomoyuki

2 1

external reference in RST and translation
by Akihiro Motoki 27 Nov '15

27 Nov '15

Hi, It is about RST formatting and translation, again. I had a trouble in translating the following type of external references. The following style is used especially when the same reference is used multiple times. In this case, translators MUST keep an original label, in this case 'User guide' in English even if there is more appropriate string in each language. If translators translate such strings, we will get a broken external link. I don't have a good solution on this other than keep original strings at now. Any suggestions? (http://docs.openstack.org/contributor-guide/rst-conv/refs.html#external-ref…) ---- Here is an external web link separated from its definition: This paragraph contains the link to `User guide`_. ... .. format the link definition at the end of the file as follows: .. _`User guide`: http://docs.openstack.org/user-guide/ ---- Thanks, Akihiro

1 0

Code block in RST and translation
by Akihiro Motoki 27 Nov '15

27 Nov '15

Hi, According to [1], we use two types of code blocks in RST documentations. The one is to end a line with "::" [2] and the other is to use 'code-block'. During translation, I noticed the first style can be a wrong formatting in translated documents (it will be considered as "block quote" as far as I tested). It is not easy that translators understand "::" at end of line has a special meaning. To keep the format, translators MUST keep "::" at the end of line, but ":" is rarely used in some languages and I think they will forget "::" easily. In addition, it is hard to detect this kind of things during translation reviews. Note that other RST conventions are easier to be recognized as special because they are very different from usual strings. On the other hand, ending a line with "::" is a standard ReST convention and it is widely used in writing documents in ReST format. My idea at now is to use "code-block" directive as possible as we can, but I am not sure it is the right direction as "::" is widely used. Thought? Thanks, Akihiro [1] http://docs.openstack.org/contributor-guide/rst-conv/source-code.html [2] http://docs.openstack.org/contributor-guide/rst-conv/source-code.html#stand… [3] http://docs.openstack.org/contributor-guide/index.html#search-in-this-guide

4 6

Arch Design Guide RST conversion finished
by KATO Tomoyuki 27 Nov '15

27 Nov '15

Hi team, Docs team finished Arch Design Guide RST conversion. At now, new RST translation resource is uploaded to Zanata. openstack-manuals / arch-design (same name) Best Regards, KATO Tomoyuki

1 0

release notes translation
by KATO Tomoyuki 25 Nov '15

25 Nov '15

Hi team, Maybe, as you know, we have the new release notes tool "reno". As far as I know, reno doesn't have translation feature. I'm not sure whether it is planned or not. So, we need to contact and maybe work with reno team. Anyone, interested in taking a lead? Here is a rough blueprint: https://blueprints.launchpad.net/openstack-i18n/+spec/release-notes-transla… Best Regards, KATO Tomoyuki

2 2

DocImpact Changes
by Lana Brindley 25 Nov '15

25 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, The DocImpact flag was implemented back in Havana to make it easier for developers to notify the documentation team when a patch might cause a change in the docs. This has had an overwhelming response, resulting in a huge amount of technical debt for the docs team, so we've been working on a plan to change how DocImpact works. This way, instead of just creating a lot of noise, it will hopefully go back to being a useful tool. This is written in more detail in our spec[1], but this email attempts to hit the highlights for you. TL;DR: In the future, you will need to add a description whenever you add a DocImpact flag in your commit message. Right now, if you create a patch and include 'DocImpact' in the commit message, Infra raises a bug in either the openstack-manuals queue, or (for some projects) your own project queue. DocImpact is capable of handling a description field, but this is rarely used. Instead, docs writers are having to dig through your patch to determine what (if any) change is required. What we are now implementing has two main facets: * The DocImpact flag can only be used if it includes a description. A Jenkins job will test for this, and if you include DocImpact without a description, the job will fail. The description can be a short note about what needs changing in the docs, a link to a gist or etherpad with more information, or a note about the location of incorrect docs. There are specific examples in the spec[2]. * Only Nova, Swift, Glance, Keystone, and Cinder will have DocImpact bugs created in the openstack-manuals queue. All other projects will have DocImpact bugs raised in their own queue. This is handled in [3] and [4]. This will hopefully reduce the volume of DocImpact bugs being created in the openstack-manuals queue, and also improve the quality of the bugs that are created. I know there is a fair amount of confusion over DocImpact already, so I'm more than happy to field questions on this. Thanks, Lana 1: http://specs.openstack.org/openstack/docs-specs/specs/mitaka/review-docimpa… 2: http://specs.openstack.org/openstack/docs-specs/specs/mitaka/review-docimpa… 3: https://review.openstack.org/#/c/248515/ 4: https://review.openstack.org/#/c/248549/ - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWU5Q0AAoJELppzVb4+KUyYz4H/j+iAG5x2iRiNbJMBgxm5Qb5 tvxzlOePHZa6VQKj1gYrp8wnBFab0CsNDt/U03D8H9D6No2hqz5qvFgOuMDXIOkS DXG+2RDD8xKMRS42t70mNtJu2oPl+9BWIre+Qyvjd7heicGd+lN/mqAvmwVV3tKB fwJl3iLrlSpwwsyunzR3LxGxzVfHUroRdFv11iQGQZNJYbS9DfOLsz66e5JBTZPh ZoCK8VAlEionaL8ExppoMPQOwpU0oYMWSjM2HGxlc/RDrNEz7HWfXl36nxqfw/mO q8Op0p5cn5UW4fYv/9Ufbw6k0JRgwODCwzSEzJ73gmOJpBrcTEdZKocnGDSdtYA= =CCIn -----END PGP SIGNATURE-----

3 3

New guides published
by Andreas Jaeger 25 Nov '15

25 Nov '15

FYI, Japanese networking guide and Chinese (zh_CN) Install Guides have been added as drafts: http://docs.openstack.org/draft/draft-index.html 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

Virtual Machine Image Guide RST conversion finished
by KATO Tomoyuki 24 Nov '15

24 Nov '15

Hi team, Sorry for late announce. Virtual Machine Image Guide RST conversion has finished. You can look at new translation resource at Zanata: openstack-manuals/image-guide (same name) Unfortunatelly, we has droped the translations with XML markup, which is replaced with RST markup. However, we can easily translate them from Zanata translation memory. Tips: The strings ":guilabel:`xxxx`" is needed to keep this structure. :guilabel:`[yourlanguage]` This is a kind of RST markup. Best Regards, KATO Tomoyuki

1 0

translate.openstack.org upgraded to Zanata 3.7.3
by Elizabeth K. Joseph 19 Nov '15

19 Nov '15

Hi everyone, Thanks to work by Steve Kowalik and testing the upgrades on our translate-dev server, we have landed the upgrade of the production Zanata server from 3.7.1 to 3.7.3. This isn't a major upgrade, but if you're curious as to what has changed, release notes are as follows for the two versions we've upgraded through: 3.7.2: http://docs.zanata.org/en/latest/release-notes/#372 3.7.3: http://docs.zanata.org/en/latest/release-notes/#373 We'd like to involve Daisy and others as we do subsequent upgrades, particularly when we reach the major releases. Steve has written a script to query the API prior to upgrade and after the upgrade on the dev server so that we can be more confident that all of our scripts will continue to work in production, and I'll ask for volunteers from this team to look at translate-dev to confirm that the UI acts the way we expect it to after upgrading translate-dev and before upgrading the production translate server. I've logged in and walked through the UI post upgrade today, but please let us know if you have any trouble. -- Elizabeth Krumbach Joseph || Lyz || pleia2

3 3

What's Up Doc, 20 Nov 2015
by Lana Brindley 19 Nov '15

19 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, This week I've been working on catching up with some reviews and bug triage, I've been speaking to O'Reilly about the future of the Ops Guide, and also been working on a range of other things including docs-specs core team review, and the addition of Zaqar docs into the user guides. Just a quick heads up that there won't be a docs newsletter next week, though, as I'm taking a couple of days off (my Mum is coming to visit!), so I'll see you again around 4 December. For those of you in the United States, I hope you all have a lovely Thanksgiving :) == Progress towards Mitaka == 138 days to go! 119 bugs closed so far for this release. RST Conversions * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * Ops Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/ops-guide-rst ** Determining whether or not we want to do an updated version for O'Reilly in L * Config Ref ** Contact the Config Ref Speciality team: https://wiki.openstack.org/wiki/Documentation/ConfigRef * Virtual Machine Image Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/image-guide-rst and https://review.openstack.org/#/c/244598/ Reorganisations * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Doc sprint in planning for December. Contact the Ops Guide speciality team for more info or to get involved. ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * User Guides ** https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… ** Contact the User Guide Speciality team: https://wiki.openstack.org/wiki/User_Guides DocImpact * I've added some examples to the spec, and we're pretty much ready to go now: https://blueprints.launchpad.net/openstack-manuals/+spec/review-docimpact Document openstack-doc-tools and reorganise index page * Thanks to Brian and Christian for volunteering to take this on! Horizon UX work * Thanks to the people who offered to help out on this! If you're interested but haven't gotten in touch yet, contact Piet Kruithof of the UX team. == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' Two patches look ready for merge now: https://review.openstack.org/#/c/225418/ and https://review.openstack.org/235893 '''Installation Guide - Christian Berendt''' Business as usual. Nothing special to mention this week. '''Networking Guide - Edgar Magana''' Open Reviews: https://review.openstack.org/#/c/239361/ Merged: https://review.openstack.org/#/c/246671/ Very slow progress, hoping to speed up after the USA holidays. '''Security Guide - Nathaniel Dillon''' No update this week '''User Guides - Joseph Robinson''' After a specification update, there is a need to provide a more comprehensive scope: a list of Core features within scope, and include research on the nova-network/ neutron migration study. Contact from Zaqar, Trove, and Murano Liaisons on Admin guide tasks has been helpful, and given the reorganisation direction. A patch on fernet tokens (FAQ format) merged into the Cloud Admin Guide this week. '''Ops and Arch Guides - Darren Chan''' Arch guide migration is close to completion. We are currently planning to reorganize the guide over a two day virtual sprint in mid December. '''API Docs - Anne Gentle''' Review ready for the Mitaka specification of a vision for app dev docs: https://review.openstack.org/#/c/246660/ '''Config Ref - Gauvain Pocentek''' The tools are ready, the liberty branch is set up, the RST migration is on! Pick your file, run the tools, and let's review. '''Training labs - Pranav Salunke''' Training-labs has Kilo patch merged! We are currently updating the network configuration and trying to get things as per Matt's feedback/request. We plan to start adding Liberty very soon and also KVM port is on the way. '''Training Guides - Matjaz Pancur''' There is interest in translating Upstream training; we are waiting for https://review.openstack.org/#/c/245615/ to merge to enable it on the repo. '''Hyperviser Tuning Guide - Joe Topjian''' On schedule - working on changing bullet-point notes into rough draft sections. == Doc team meeting == We held the US docs meeting this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-11-18 Next meetings: APAC: Wednesday 25 November, 00:30:00 UTC US: Wednesday 2 December, 14:00 UTC 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 - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWTqEMAAoJELppzVb4+KUyx8AH/0AOs2kfvR8TwvMTO9FSuT2F UkfrQfzqPIPjU0d4prIkFxJJ3k9NlGDS4+h2lgZSsqYSDRfinoYMkzAOFGOBB0I/ P9KYx7dd+IRagmF2bOfIDBhl+qTxD4GrzaKdzpH9kAaizmf1xylk6VCXT2Yh0PRd wPRw7RAXg3XjvJhQIElm0pNoRijikAR1CfafzR+HnZMswXPI1S1NnwQSBJD3yYwK npdfEiICdIkzTcdNMODzN57PXkLBymb++EAW/UsWEnmlyyIGJTZqlJNbd8TAGjHz vpvILlZHsuJ8mavPASStZy0ZZad3svusNf6pbsZEdUcS3ibZKRSb3xpEOh31eC0= =7tXE -----END PGP SIGNATURE-----

1 0

IRC meeting tomorrow
by Ying Chun Guo 18 Nov '15

18 Nov '15

Hello, team We will have IRC meeting tomorrow at 1300 UTC in the IRC channel #openstack-meeting. I'm going to cover following topics tomorrow. If you have more topics, please propose freely. * Status update and issues collection of the work items * Discussion: how to manage I18n related bug reports ? * Open discussions Best regards Ying Chun Guo (Daisy)

1 0

Re: [Openstack-i18n] RFC: draft doc on how to report translation bugs
by Akihiro Motoki 17 Nov '15

17 Nov '15

BTW, The I18n team meeting wiki page says the next meeting is "Thursday, 5th December at 0600 UTC". Is this wrong information? 2015-11-18 11:59 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Thank you for initiating this. > Besides discussion in Gerrit, > let's create a topic to discuss it in the IRC meeting tomorrow. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2015/11/17 20:00:13: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: "openstack-i18n(a)lists.openstack.org" >> <Openstack-i18n(a)lists.openstack.org> >> Date: 2015/11/17 20:28 >> Subject: [Openstack-i18n] RFC: draft doc on how to report translation bugs > >> >> Hi team, >> >> I proposed a doc patch on how to report a translation/I18N bugs. >> >> https://review.openstack.org/#/c/246256/ >> >> It discusses which and where bugs should be filed. >> I know we don't have any consensus on how to manage >> language-specific translation bugs. >> My draft is just a start-line and I don't think it is best. >> Any discussion and input would be appreciated. >> >> Thanks, >> Akihiro >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >

1 0

RFC: draft doc on how to report translation bugs
by Akihiro Motoki 17 Nov '15

17 Nov '15

Hi team, I proposed a doc patch on how to report a translation/I18N bugs. https://review.openstack.org/#/c/246256/ It discusses which and where bugs should be filed. I know we don't have any consensus on how to manage language-specific translation bugs. My draft is just a start-line and I don't think it is best. Any discussion and input would be appreciated. Thanks, Akihiro

2 1

Re: [Openstack-i18n] stable-liberty version for openstack-manuals created in Zanata
by Andreas Jaeger 17 Nov '15

17 Nov '15

On 2015-11-17 10:49, Ying Chun Guo wrote: > Hi, Andreas > > I see stable/liberty is created in the repo of openstack-manuals, > and stable-liberty version is created for openstack-manuals project in > Zanata. > Thank you for handling these. > > Is the installation guide in the master branch keeping open for Mitaka > release? Yes. > So in order to translate Liberty installation guide, our translators should > go to stable-liberty and work there. Correct. > I have changed the link of openstack manuals in the home page > translation plan > to stable-liberty version. > Correct me if I'm wrong. Looks fine Andreas > Thank you. > Best regards > Ying Chun Guo (Daisy) > > ----- Forwarded by Ying Chun Guo/China/IBMon 2015/11/17 17:40----- > > Andreas Jaeger <aj(a)suse.com> wrote on 2015/11/16 23:44:58: > > > From: Andreas Jaeger <aj(a)suse.com> > > To: "openstack-docs(a)lists.openstack.org" > <openstack-docs(a)lists.openstack.org> > > Date: 2015/11/16 23:46 > > Subject: [OpenStack-docs] stable/liberty for openstack-manuals > > created - and frozen! > > > > Thanks to Spencer Krum (nibalicer) we now have a stable/liberty branch > > for openstack-manuals. > > > > I now need to setup the branch and ask for a freeze of stable/liberty > > until I have given the go ahead for the branch! I need to set it up and > > document all the steps ;) > > > > Merging of changes for master is fine but do not merge any for > liberty yet! > > > > Thanks > > 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 > > > > > > _______________________________________________ > > OpenStack-docs mailing list > > OpenStack-docs(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs > -- 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

1 0

stable-liberty version for openstack-manuals created in Zanata
by Ying Chun Guo 17 Nov '15

17 Nov '15

Hi, Andreas I see stable/liberty is created in the repo of openstack-manuals, and stable-liberty version is created for openstack-manuals project in Zanata. Thank you for handling these. Is the installation guide in the master branch keeping open for Mitaka release? So in order to translate Liberty installation guide, our translators should go to stable-liberty and work there. I have changed the link of openstack manuals in the home page translation plan to stable-liberty version. Correct me if I'm wrong. Thank you. Best regards Ying Chun Guo (Daisy) ----- Forwarded by Ying Chun Guo/China/IBM on 2015/11/17 17:40 ----- Andreas Jaeger <aj(a)suse.com> wrote on 2015/11/16 23:44:58: > From: Andreas Jaeger <aj(a)suse.com> > To: "openstack-docs(a)lists.openstack.org" <openstack-docs(a)lists.openstack.org> > Date: 2015/11/16 23:46 > Subject: [OpenStack-docs] stable/liberty for openstack-manuals > created - and frozen! > > Thanks to Spencer Krum (nibalicer) we now have a stable/liberty branch > for openstack-manuals. > > I now need to setup the branch and ask for a freeze of stable/liberty > until I have given the go ahead for the branch! I need to set it up and > document all the steps ;) > > Merging of changes for master is fine but do not merge any for liberty yet! > > Thanks > 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 > > > _______________________________________________ > OpenStack-docs mailing list > OpenStack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

1 0

Rename the language code of Punjabi
by Ying Chun Guo 16 Nov '15

16 Nov '15

Hello, According to previous discussion[1], it seems like pa-IN is meaningless. "Punjabi has two entirely different scripts i.e. Gurmukhi (ਪੈਂਤੀ) and Shahmukhi (اردو), while former is widely used in Indian side of Punjab aka Eastern Punjab the latter is used in Pakistani side of Punjab aka Western Punjab." The translations of pa-IN are mixing of two kinds of characters. So I think we should rename pa-IN to pa-Guru, in order to avoid confusing. I see Alam prefer to use "pa", not "pa-Guru". [2] But I think pa-Guru is more clear than pa. @Alam and Amandeep, correct me if I'm wrong. I have created a blueprint.[3] The work items include both the language team rename in Zanata and the folder rename in repo. Please review. Best regards Ying Chun Guo (Daisy) [1] http://lists.openstack.org/pipermail/openstack-i18n/2015-September/001358.h… [2] http://lists.openstack.org/pipermail/openstack-i18n/2015-September/001424.h… [3] https://blueprints.launchpad.net/openstack-i18n/+spec/rename-punjabi-code

2 2

Duplicated toctree of sidebar in translated install guides
by Akihiro Motoki 16 Nov '15

16 Nov '15

Hi, I noticed translated install guides have a toctree in the sidebar twice. The example is http://docs.openstack.org/draft/ja/install-guide-obs/ . I filed a bug at https://bugs.launchpad.net/openstack-manuals/+bug/1516079 . It is due to the change in https://review.openstack.org/#/c/237885/ and I think it is because index.rst has two toctree. We are doing a special handling in tools/build-install-guides-rst.sh when generating a non-translated install guide. Do we need a similar handling for translated install guides? The translated install guides are currently generated by doc-tools-check-languages and some infra jobs. I am not confident how they are involved. Any help would be appreciated. Thanks, Akihiro

3 2

How can i join Chinese (China) team？
by gaoxiao zhu 16 Nov '15

16 Nov '15

Hi all, I registered myself for the Chinese (China) translation project .I am looking forward to begin contributing for the project. What should I do? Best regards

2 1

Re: [Openstack-i18n] I18n wiki page is translatable
by Tom Fifield 14 Nov '15

14 Nov '15

On 13/11/15 14:00, Ying Chun Guo wrote: > Thank you, Akihiro. > It looks wonderful. > I think we could mark I18nTeam translatable now. > > Tom, please help. The page I18nTeam has been marked up for translation with 14 translation units. The page can now be translated. > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2015/11/12 23:06:14: > > > From: Akihiro Motoki <amotoki(a)gmail.com> > > To: Ying Chun Guo/China/IBM@IBMCN > > Cc: Tom Fifield <tom(a)openstack.org>, Openstack-i18n <openstack- > > i18n(a)lists.openstack.org> > > Date: 2015/11/12 23:06 > > Subject: Re: [Openstack-i18n] I18n wiki page is translatable > > > > Hi Daisy, > > > > I move all team wiki pages to I18nTeam/team/xxxxx. > > In addition, I created a page > https://wiki.openstack.org/wiki/I18nTeam/team > > which contains a list of language teams. > > > > Akihiro > > > > 2015-11-12 16:04 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > > > Thank you Tom. > > > Sorry for the trouble. > > > I will move all the team wiki pages to different links. > > > > > > Best regards > > > Ying Chun Guo (Daisy) > > > > > > > > > Tom Fifield <tom(a)openstack.org> wrote on 2015/11/12 07:43:39: > > > > > >> From: Tom Fifield <tom(a)openstack.org> > > >> To: Ying Chun Guo/China/IBM@IBMCN, Akihiro Motoki <amotoki(a)gmail.com> > > >> Cc: Openstack-i18n <openstack-i18n(a)lists.openstack.org> > > >> Date: 2015/11/12 07:43 > > > > > > > > >> Subject: Re: [Openstack-i18n] I18n wiki page is translatable > > >> > > >> Hi, > > >> > > >> Sorry, it took a while to work out how to disable the translations. > > >> That's been done now. > > >> > > >> > > >> Regards, > > >> > > >> > > >> Tom > > >> > > >> On 11/11/15 18:09, Ying Chun Guo wrote: > > >> > I think we need to disable the translation at first. > > >> > Then we could be able to move them. > > >> > I'm not able to move, same as you. > > >> > > > >> > Best regards > > >> > Ying Chun Guo (Daisy) > > >> > > > >> > > > >> > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2015/11/11 14:40:43: > > >> > > > >> > > From: Akihiro Motoki <amotoki(a)gmail.com> > > >> > > To: Ying Chun Guo/China/IBM@IBMCN > > >> > > Cc: "Ian Y. Choi" <ianyrchoi(a)gmail.com>, Openstack-i18n > <openstack- > > >> > > i18n(a)lists.openstack.org> > > >> > > Date: 2015/11/11 15:05 > > >> > > Subject: Re: [Openstack-i18n] I18n wiki page is translatable > > >> > > > > >> > > Daisy, > > >> > > > > >> > > It sounds good to me, but normal users like me cannot move pages. > > >> > > I got Permission Error. Could you handle all moving of pages? > > >> > > > > >> > > > > >> > > 2015-11-11 15:05 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > > >> > > > Thank you for the explain Ian. > > >> > > > I think we could move the wiki pages for language teams to > > >> > > > /I18nTeam/team/<language-code>, > > >> > > > and then keep /I18nTeam/<language-code> for the translation > page of > > >> > > > I18nTeam. > > >> > > > > > >> > > > How do you think about it, Akihiro? > > >> > > > > > >> > > > Best regards > > >> > > > Ying Chun Guo (Daisy) > > >> > > > > > >> > > > > > >> > > > "Ian Y. Choi" <ianyrchoi(a)gmail.com> wrote on 2015/11/11 > 00:55:07: > > >> > > > > > >> > > >> From: "Ian Y. Choi" <ianyrchoi(a)gmail.com> > > >> > > >> To: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun > > >> > Guo/China/IBM@IBMCN > > >> > > >> Cc: Openstack-i18n <openstack-i18n(a)lists.openstack.org> > > >> > > >> Date: 2015/11/11 00:55 > > >> > > >> Subject: Re: [Openstack-i18n] I18n wiki page is translatable > > >> > > > > > >> > > > > > >> > > >> > > >> > > >> Hello Akihiro, > > >> > > >> > > >> > > >> Actually I suggested a translatable I18nTeam wiki page [1] for > > >> > Korean > > >> > > >> during last Tokyo Design Summit. > > >> > > >> After saying it, I found that there might be a problem in > Japanese > > >> > local > > >> > > >> team > > >> > > >> because Japanese language team already used /ja page, as you > > >> > mentioned and > > >> > > >> which would make conflict with translation functionality in > > >> > OpenStack > > >> > > >> wiki. > > >> > > >> > > >> > > >> Let me first say why Korean translation page for I18nTeam is > > >> > needed and > > >> > > >> how Korean translation team wants to use two wiki pages > > >> > separately: > > >> > > >> > > >> > > >> 1) https://wiki.openstack.org/wiki/I18nTeam/ko > > >> > > >> : To provide Korean guys with official I18nTeam introduction > > >> > wiki page > > >> > > >> : I think "Local Translation Teams" section is needed > because > > >> > this > > >> > > >> information is > > >> > > >> beneficial with the knowledge of the various language team > > >> > activities. > > >> > > >> > > >> > > >> 2) https://wiki.openstack.org/wiki/I18nTeam/team/ko_KR > > >> > > >> (I found that Daisy moved from .../ko_KR to .../team/ko_KR. > > >> > Thank you!) > > >> > > >> : To introduce Korean translation team with details and our > > >> > specific > > >> > > >> translation rules > > >> > > >> : Providing links for OpenStack I18n official > introduction wiki > > >> > page & > > >> > > >> its translation > > >> > > >> > > >> > > >> I would like to respect I18nTeam official wiki page, and this > > >> > > >> information is written in English. > > >> > > >> In my opinion, translating this page would more clearly > advertise > > >> > > >> OpenStack I18n overall activities to more Korean. > > >> > > >> > > >> > > >> This requirement and need might be different from various > local > > >> > > >> translation teams, I think, > > >> > > >> and I also would like to respect the ways Japanese team > used more > > >> > than 1 > > >> > > >> year. > > >> > > >> > > >> > > >> So I would like to suggest not to include "<languages />" > tag on > > >> > [1] . > > >> > > >> As you know, OpenStack Release Note wiki pages such as [2] > > >> > > >> contain "<languages />" tag and displays different language > > >> > translated > > >> > > >> pages on the top part. > > >> > > >> > > >> > > >> I think this suggestion would satisfy different needs from > various > > >> > > >> language translation teams. > > >> > > >> However, if https://wiki.openstack.org/wiki/I18nTeam page > includes > > >> > > >> "<languages />" tag, > > >> > > >> then it would not fit to not only Japanese translation > team, but > > >> > also > > >> > > >> other teams such as French, Polish and so on. > > >> > > >> For Korean translation team, our official page contains the > > >> > translated > > >> > > >> I18nTeam link so it would be okay. > > >> > > >> > > >> > > >> I am not sure, but Daisy might already think so Daisy only > moved > > >> > from > > >> > > >> .../ko_KR to .../team/ko_KR, and > > >> > > >> did not include "<languages />" tag on [1] :) > > >> > > >> > > >> > > >> This is just my suggestion not to conflict with your team > and to > > >> > > >> accomplish our team requirement, > > >> > > >> and I would like to listen Daisy's opinion and other > language > > >> > teams' > > >> > > >> opinions. > > >> > > >> > > >> > > >> [1] https://wiki.openstack.org/wiki/I18nTeam > > >> > > >> [2] https://wiki.openstack.org/wiki/ReleaseNotes/Liberty > > >> > > >> > > >> > > >> > > >> > > >> With many thanks, > > >> > > >> > > >> > > >> /Ian > > >> > > >> > > >> > > >> Akihiro Motoki wrote on 11/10/2015 8:48 PM: > > >> > > >> > In addition, Japanese team maintains the original > contents which > > >> > > >> > are differ from the English version of I18nTeam page. > > >> > > >> > Before enabling translation for I18nTeam, I would like > to see a > > >> > solution > > >> > > >> > for language specific content. > > >> > > >> > > > >> > > >> > > > >> > > >> > 2015-11-10 20:45 GMT+09:00 Akihiro Motoki > <amotoki(a)gmail.com>: > > >> > > >> >> I noticed the existing language team page cannot be edited. > > >> > > >> >> For example, > https://wiki.openstack.org/wiki/I18nTeam/ja exists > > >> > from > > >> > > >> >> more than one year ago. > > >> > > >> >> After this change, we can no longer edit the original page. > > >> > > >> >> What should we do? > > >> > > >> >> > > >> > > >> >> In addition, I18nTeam wiki page contains contents which > is not > > >> > > >> >> appropriate for translation, > > >> > > >> >> for example, "Local Translation Teams" section. > > >> > > >> >> As a local team coordinator, I don't like to display this > > >> > section in a > > >> > > >> >> translated version. > > >> > > >> >> > > >> > > >> >> Thanks, > > >> > > >> >> Akihiro > > >> > > >> >> > > >> > > >> >> 2015-11-10 18:11 GMT+09:00 Ying Chun Guo > <guoyingc(a)cn.ibm.com>: > > >> > > >> >>> Hi, > > >> > > >> >>> > > >> > > >> >>> As requested by Korean team, the wiki page of I18nTeam is > > >> > > >> translatable now. > > >> > > >> >>> If you want to translate this page into your own language, > > >> > > >> please go ahead. > > >> > > >> >>> Thank you. > > >> > > >> >>> > > >> > > >> >>> Best regards > > >> > > >> >>> Ying Chun Guo (Daisy) > > >> > > >> >>> > > >> > > >> >>> > > >> > > >> >>> _______________________________________________ > > >> > > >> >>> 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 > > >> > > >> > > >> > > >> -- > > >> > > >> /Ian > > >> > > >> > > >> > > > > > >> > > > > >> > > > >> > > > >> > > > >> > _______________________________________________ > > >> > 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] I18n wiki page is translatable
by Akihiro Motoki 12 Nov '15

12 Nov '15

Hi Daisy, I move all team wiki pages to I18nTeam/team/xxxxx. In addition, I created a page https://wiki.openstack.org/wiki/I18nTeam/team which contains a list of language teams. Akihiro 2015-11-12 16:04 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Thank you Tom. > Sorry for the trouble. > I will move all the team wiki pages to different links. > > Best regards > Ying Chun Guo (Daisy) > > > Tom Fifield <tom(a)openstack.org> wrote on 2015/11/12 07:43:39: > >> From: Tom Fifield <tom(a)openstack.org> >> To: Ying Chun Guo/China/IBM@IBMCN, Akihiro Motoki <amotoki(a)gmail.com> >> Cc: Openstack-i18n <openstack-i18n(a)lists.openstack.org> >> Date: 2015/11/12 07:43 > > >> Subject: Re: [Openstack-i18n] I18n wiki page is translatable >> >> Hi, >> >> Sorry, it took a while to work out how to disable the translations. >> That's been done now. >> >> >> Regards, >> >> >> Tom >> >> On 11/11/15 18:09, Ying Chun Guo wrote: >> > I think we need to disable the translation at first. >> > Then we could be able to move them. >> > I'm not able to move, same as you. >> > >> > Best regards >> > Ying Chun Guo (Daisy) >> > >> > >> > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2015/11/11 14:40:43: >> > >> > > From: Akihiro Motoki <amotoki(a)gmail.com> >> > > To: Ying Chun Guo/China/IBM@IBMCN >> > > Cc: "Ian Y. Choi" <ianyrchoi(a)gmail.com>, Openstack-i18n <openstack- >> > > i18n(a)lists.openstack.org> >> > > Date: 2015/11/11 15:05 >> > > Subject: Re: [Openstack-i18n] I18n wiki page is translatable >> > > >> > > Daisy, >> > > >> > > It sounds good to me, but normal users like me cannot move pages. >> > > I got Permission Error. Could you handle all moving of pages? >> > > >> > > >> > > 2015-11-11 15:05 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> > > > Thank you for the explain Ian. >> > > > I think we could move the wiki pages for language teams to >> > > > /I18nTeam/team/<language-code>, >> > > > and then keep /I18nTeam/<language-code> for the translation page of >> > > > I18nTeam. >> > > > >> > > > How do you think about it, Akihiro? >> > > > >> > > > Best regards >> > > > Ying Chun Guo (Daisy) >> > > > >> > > > >> > > > "Ian Y. Choi" <ianyrchoi(a)gmail.com> wrote on 2015/11/11 00:55:07: >> > > > >> > > >> From: "Ian Y. Choi" <ianyrchoi(a)gmail.com> >> > > >> To: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun >> > Guo/China/IBM@IBMCN >> > > >> Cc: Openstack-i18n <openstack-i18n(a)lists.openstack.org> >> > > >> Date: 2015/11/11 00:55 >> > > >> Subject: Re: [Openstack-i18n] I18n wiki page is translatable >> > > > >> > > > >> > > >> >> > > >> Hello Akihiro, >> > > >> >> > > >> Actually I suggested a translatable I18nTeam wiki page [1] for >> > Korean >> > > >> during last Tokyo Design Summit. >> > > >> After saying it, I found that there might be a problem in Japanese >> > local >> > > >> team >> > > >> because Japanese language team already used /ja page, as you >> > mentioned and >> > > >> which would make conflict with translation functionality in >> > OpenStack >> > > >> wiki. >> > > >> >> > > >> Let me first say why Korean translation page for I18nTeam is >> > needed and >> > > >> how Korean translation team wants to use two wiki pages >> > separately: >> > > >> >> > > >> 1) https://wiki.openstack.org/wiki/I18nTeam/ko >> > > >> : To provide Korean guys with official I18nTeam introduction >> > wiki page >> > > >> : I think "Local Translation Teams" section is needed because >> > this >> > > >> information is >> > > >> beneficial with the knowledge of the various language team >> > activities. >> > > >> >> > > >> 2) https://wiki.openstack.org/wiki/I18nTeam/team/ko_KR >> > > >> (I found that Daisy moved from .../ko_KR to .../team/ko_KR. >> > Thank you!) >> > > >> : To introduce Korean translation team with details and our >> > specific >> > > >> translation rules >> > > >> : Providing links for OpenStack I18n official introduction wiki >> > page & >> > > >> its translation >> > > >> >> > > >> I would like to respect I18nTeam official wiki page, and this >> > > >> information is written in English. >> > > >> In my opinion, translating this page would more clearly advertise >> > > >> OpenStack I18n overall activities to more Korean. >> > > >> >> > > >> This requirement and need might be different from various local >> > > >> translation teams, I think, >> > > >> and I also would like to respect the ways Japanese team used more >> > than 1 >> > > >> year. >> > > >> >> > > >> So I would like to suggest not to include "<languages />" tag on >> > [1] . >> > > >> As you know, OpenStack Release Note wiki pages such as [2] >> > > >> contain "<languages />" tag and displays different language >> > translated >> > > >> pages on the top part. >> > > >> >> > > >> I think this suggestion would satisfy different needs from various >> > > >> language translation teams. >> > > >> However, if https://wiki.openstack.org/wiki/I18nTeam page includes >> > > >> "<languages />" tag, >> > > >> then it would not fit to not only Japanese translation team, but >> > also >> > > >> other teams such as French, Polish and so on. >> > > >> For Korean translation team, our official page contains the >> > translated >> > > >> I18nTeam link so it would be okay. >> > > >> >> > > >> I am not sure, but Daisy might already think so Daisy only moved >> > from >> > > >> .../ko_KR to .../team/ko_KR, and >> > > >> did not include "<languages />" tag on [1] :) >> > > >> >> > > >> This is just my suggestion not to conflict with your team and to >> > > >> accomplish our team requirement, >> > > >> and I would like to listen Daisy's opinion and other language >> > teams' >> > > >> opinions. >> > > >> >> > > >> [1] https://wiki.openstack.org/wiki/I18nTeam >> > > >> [2] https://wiki.openstack.org/wiki/ReleaseNotes/Liberty >> > > >> >> > > >> >> > > >> With many thanks, >> > > >> >> > > >> /Ian >> > > >> >> > > >> Akihiro Motoki wrote on 11/10/2015 8:48 PM: >> > > >> > In addition, Japanese team maintains the original contents which >> > > >> > are differ from the English version of I18nTeam page. >> > > >> > Before enabling translation for I18nTeam, I would like to see a >> > solution >> > > >> > for language specific content. >> > > >> > >> > > >> > >> > > >> > 2015-11-10 20:45 GMT+09:00 Akihiro Motoki <amotoki(a)gmail.com>: >> > > >> >> I noticed the existing language team page cannot be edited. >> > > >> >> For example, https://wiki.openstack.org/wiki/I18nTeam/ja exists >> > from >> > > >> >> more than one year ago. >> > > >> >> After this change, we can no longer edit the original page. >> > > >> >> What should we do? >> > > >> >> >> > > >> >> In addition, I18nTeam wiki page contains contents which is not >> > > >> >> appropriate for translation, >> > > >> >> for example, "Local Translation Teams" section. >> > > >> >> As a local team coordinator, I don't like to display this >> > section in a >> > > >> >> translated version. >> > > >> >> >> > > >> >> Thanks, >> > > >> >> Akihiro >> > > >> >> >> > > >> >> 2015-11-10 18:11 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> > > >> >>> Hi, >> > > >> >>> >> > > >> >>> As requested by Korean team, the wiki page of I18nTeam is >> > > >> translatable now. >> > > >> >>> If you want to translate this page into your own language, >> > > >> please go ahead. >> > > >> >>> Thank you. >> > > >> >>> >> > > >> >>> Best regards >> > > >> >>> Ying Chun Guo (Daisy) >> > > >> >>> >> > > >> >>> >> > > >> >>> _______________________________________________ >> > > >> >>> 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 >> > > >> >> > > >> -- >> > > >> /Ian >> > > >> >> > > > >> > > >> > >> > >> > >> > _______________________________________________ >> > Openstack-i18n mailing list >> > Openstack-i18n(a)lists.openstack.org >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > >> >

2 1

What's Up, Doc? 13 November 2015
by Lana Brindley 12 Nov '15

12 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, Well, things are starting to ramp up again after Summit. This week, I've spent some time catching up with other PTLs, and also worked on the DocImpact spec. I've also implemented my plan to get the Speciality Team leads to provide content on their projects individually, so many thanks to them for replying with so much great info! == Progress towards Mitaka == 145 days to go! 100 bugs closed so far for this release. DocImpact * I've updated the spec and made contact with Infra to nut out the finer technical details: https://blueprints.launchpad.net/openstack-manuals/+spec/review-docimpact RST Conversions * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * Ops Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/ops-guide-rst ** Lana will reach out to O'Reilly to discuss the printed book before this work begins * Config Ref ** Contact the Config Ref Speciality team: https://wiki.openstack.org/wiki/Documentation/ConfigRef * Virtual Machine Image Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/image-guide-rst and https://review.openstack.org/#/c/244598/ Reorganisations * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * User Guides ** https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… ** Contact the User Guide Speciality team: https://wiki.openstack.org/wiki/User_Guides Document openstack-doc-tools and reorganise index page * Thanks to Brian for volunteering to take this on! Horizon UX work * There's an interesting opportunity to improve the wording in Horizon, specifically around LBaaS, and also to develop a set of standards around the language used in the dashboard. If you're interested, let me know and I'll get you in contact with the right people. == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' Created a poll to shift HA guide IRC meeting time (http://lists.openstack.org/pipermail/openstack-docs/2015-November/007830.ht…) Submitted a status for HA guide testing (http://lists.openstack.org/pipermail/openstack-docs/2015-October/007718.html) hoping to see more participants in testing. Trying to push few patches, and initiated related discussion: https://review.openstack.org/#/c/225418/ and https://review.openstack.org/235893. Thinking on how to effectively collaborate with Adam Spiers and his Openstack HA initiative (http://lists.openstack.org/pipermail/openstack-dev/2015-November/079127.html) to benefit HA guide project as well. '''Installation Guide - Christian Berendt''' Moved the team meeting from Google Hangout to IRC (online at http://eavesdrop.openstack.org/#Documentation_Install_Team_Meeting) we had our first team meeting on the IRC (http://eavesdrop.openstack.org/meetings/docinstallteam/2015/docinstallteam.…) we discussed the inclusion of hypervisor specific appendixes, no consensus at the moment, really good progress on the Debian install guide, zigo is doing a good job. '''Networking Guide - Edgar Magana''' We have a new spec for OVN: https://review.openstack.org/#/c/244367/ I am going to start pulling people into specific patches. '''Security Guide - Nathaniel Dillon''' We have added a new chapter on Manila and have completed the reworking of the case studies. '''User Guides - Joseph Robinson''' Our meeting format has changed from hangouts to IRC meetings, with the appropriate changes made to the meetbot script thanks to Brian. The mitaka specification: the priority at the moment is checking in with project docs liaisons to confirm what services are in scope, and then add a short statement to the specification outlining this scope. Responding to Cloud Admin Guide patches. Thanks to Andreas for the link. '''Ops and Arch Guides - Shilla Saebi''' The operations guide RST migration is on hold until we find out if we are going to move forward with docbook or RST. In the meantime we are looking to add content and update it. The architecture guide RST conversion is underway. The progress on chapters and pages can be checked via the wiki page: https://wiki.openstack.org/wiki/Documentation/Migrate '''API Docs - Anne Gentle''' Russell Sim plans to revise the templates for developer.openstack.org landing page to better match docs.openstack.org. We'll also map out a plan for fairy-slipper and the WADL migration. Spec to be updated soon. '''Config Ref - Gauvain Pocentek''' The initial structure for the Config Reference RST migration is up, the automation tools are ready to handle RST tables generation, and a couple pages have already been converted. We're waiting for the liberty branching to start pushing more converted pages. '''Training labs - Pranav Salunke''' Added Kilo support, still under review but in final stages (https://review.openstack.org/#/c/237061/) Halfway through adding KVM support, will probably need more time. Other small things like fixing readmes etc. Still pending to decide IRC meeting time. '''Training Guides - Matjaz Pancur''' Two new core reviewers: Kato Tomoyuki and Tim Freund. We also added a new policy for cores: current lead of Upstream training session (held before each Summit) is now part of the core team by function. '''Hyperviser Tuning Guide - Joe Topjian''' All data from the past etherpads have been compiled onto the wiki (https://wiki.openstack.org/wiki/Documentation/HypervisorTuningGuide) My goal right now is to translate the raw notes into something more readable. Once the page starts to resemble a readable guide, I'll try to rally others to join in. == Doc team meeting == We held the APAC docs meeting this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-11-11 Next meetings: US: Wednesday 18 November, 14:00 UTC APAC: Wednesday 25 November, 00:30:00 UTC 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 - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWRWXhAAoJELppzVb4+KUyE5IH/AjYER1GXxR7IE0zz8uIsfqx rkgm7tJDz5uPZaJr5taXJFtZRiYomZKrZNQ+ijDSt770lUApunr5Q/gkQLrnIyBr GVZPmsmv8duj6vYYDgIlDNwfaE7BtsCE5Cqvcg+rE8+MpWwFp66I8/AcJ2g0Ez2I qQZ/mfsWfURAU2rZssBSh4sSl+t90C2TBRYPA2kH45zfyBXKxqXH5q1uFE9XFUwS BgiUUpFewnAZM+r+dR/efyN/brLUfmI0UkczrazAngq1HsytXBEhxgI7/LJ/xC29 ZA5R11eppGyS3y/6dUvBFVlVLrDm324DPNJD4ykU7eCRJbCUsd4rekD/08UXCeo= =K6gD -----END PGP SIGNATURE-----

1 0

I18n Guide publication
by KATO Tomoyuki 12 Nov '15

12 Nov '15

Hi team, We have published the I18n Guide [1]. The more contents are coming. Also, your contribution is very welcome, feel free to send a patch. For details, see the blueprint [2] and patch review requests [3]. [1] http://docs.openstack.org/developer/i18n/ [2] https://blueprints.launchpad.net/openstack-i18n/+spec/i18n-contributor-guide [3] https://review.openstack.org/#/q/status:open+project:openstack/i18n,n,z Thanks, KATO Tomoyuki

3 4

Terminologies in repo
by Ying Chun Guo 11 Nov '15

11 Nov '15

Hello, team I have submitted a patch to our repo for review, containing all the terminologies and translations we made. https://review.openstack.org/244031 I want to discuss about how to handle these assets we made. Currently, I use a google doc to store the terms and the translations. https://docs.google.com/spreadsheets/d/1BRizUNhDLl_6NtsGconFkxsKUqAmEEGum9I… I want to move these assets to our repo. My plan is to use pot and po files to store the terms and the translations. Then create a project named as "terminology" in Zanata, and create auto jobs to manage the synchronization between i18n repo and Zanata. So the process to update terms are: - If a people wants to add a new term to the terminology, submit a patch to i18n repo to change the original term.pot file. - If a people want to update a translation of a term, go to Zanata to update the translation. Let me know your thoughts to my design. Thank you. Best regards Ying Chun Guo (Daisy)

5 6

Re: [Openstack-i18n] I18n wiki page is translatable
by Akihiro Motoki 11 Nov '15

11 Nov '15

Daisy, It sounds good to me, but normal users like me cannot move pages. I got Permission Error. Could you handle all moving of pages? 2015-11-11 15:05 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Thank you for the explain Ian. > I think we could move the wiki pages for language teams to > /I18nTeam/team/<language-code>, > and then keep /I18nTeam/<language-code> for the translation page of > I18nTeam. > > How do you think about it, Akihiro? > > Best regards > Ying Chun Guo (Daisy) > > > "Ian Y. Choi" <ianyrchoi(a)gmail.com> wrote on 2015/11/11 00:55:07: > >> From: "Ian Y. Choi" <ianyrchoi(a)gmail.com> >> To: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun Guo/China/IBM@IBMCN >> Cc: Openstack-i18n <openstack-i18n(a)lists.openstack.org> >> Date: 2015/11/11 00:55 >> Subject: Re: [Openstack-i18n] I18n wiki page is translatable > > >> >> Hello Akihiro, >> >> Actually I suggested a translatable I18nTeam wiki page [1] for Korean >> during last Tokyo Design Summit. >> After saying it, I found that there might be a problem in Japanese local >> team >> because Japanese language team already used /ja page, as you mentioned and >> which would make conflict with translation functionality in OpenStack >> wiki. >> >> Let me first say why Korean translation page for I18nTeam is needed and >> how Korean translation team wants to use two wiki pages separately: >> >> 1) https://wiki.openstack.org/wiki/I18nTeam/ko >> : To provide Korean guys with official I18nTeam introduction wiki page >> : I think "Local Translation Teams" section is needed because this >> information is >> beneficial with the knowledge of the various language team activities. >> >> 2) https://wiki.openstack.org/wiki/I18nTeam/team/ko_KR >> (I found that Daisy moved from .../ko_KR to .../team/ko_KR. Thank you!) >> : To introduce Korean translation team with details and our specific >> translation rules >> : Providing links for OpenStack I18n official introduction wiki page & >> its translation >> >> I would like to respect I18nTeam official wiki page, and this >> information is written in English. >> In my opinion, translating this page would more clearly advertise >> OpenStack I18n overall activities to more Korean. >> >> This requirement and need might be different from various local >> translation teams, I think, >> and I also would like to respect the ways Japanese team used more than 1 >> year. >> >> So I would like to suggest not to include "<languages />" tag on [1] . >> As you know, OpenStack Release Note wiki pages such as [2] >> contain "<languages />" tag and displays different language translated >> pages on the top part. >> >> I think this suggestion would satisfy different needs from various >> language translation teams. >> However, if https://wiki.openstack.org/wiki/I18nTeam page includes >> "<languages />" tag, >> then it would not fit to not only Japanese translation team, but also >> other teams such as French, Polish and so on. >> For Korean translation team, our official page contains the translated >> I18nTeam link so it would be okay. >> >> I am not sure, but Daisy might already think so Daisy only moved from >> .../ko_KR to .../team/ko_KR, and >> did not include "<languages />" tag on [1] :) >> >> This is just my suggestion not to conflict with your team and to >> accomplish our team requirement, >> and I would like to listen Daisy's opinion and other language teams' >> opinions. >> >> [1] https://wiki.openstack.org/wiki/I18nTeam >> [2] https://wiki.openstack.org/wiki/ReleaseNotes/Liberty >> >> >> With many thanks, >> >> /Ian >> >> Akihiro Motoki wrote on 11/10/2015 8:48 PM: >> > In addition, Japanese team maintains the original contents which >> > are differ from the English version of I18nTeam page. >> > Before enabling translation for I18nTeam, I would like to see a solution >> > for language specific content. >> > >> > >> > 2015-11-10 20:45 GMT+09:00 Akihiro Motoki <amotoki(a)gmail.com>: >> >> I noticed the existing language team page cannot be edited. >> >> For example, https://wiki.openstack.org/wiki/I18nTeam/ja exists from >> >> more than one year ago. >> >> After this change, we can no longer edit the original page. >> >> What should we do? >> >> >> >> In addition, I18nTeam wiki page contains contents which is not >> >> appropriate for translation, >> >> for example, "Local Translation Teams" section. >> >> As a local team coordinator, I don't like to display this section in a >> >> translated version. >> >> >> >> Thanks, >> >> Akihiro >> >> >> >> 2015-11-10 18:11 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> >>> Hi, >> >>> >> >>> As requested by Korean team, the wiki page of I18nTeam is >> translatable now. >> >>> If you want to translate this page into your own language, >> please go ahead. >> >>> Thank you. >> >>> >> >>> Best regards >> >>> Ying Chun Guo (Daisy) >> >>> >> >>> >> >>> _______________________________________________ >> >>> 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 >> >> -- >> /Ian >> >

3 3

Re: [Openstack-i18n] I18n wiki page is translatable
by Ian Y. Choi 11 Nov '15

11 Nov '15

Thank you so much, Daisy and Akihiro! I also hope that everything runs so well. With many thanks, /Ian Ying Chun Guo wrote on 11/11/2015 4:09 PM: > > I think we need to disable the translation at first. > Then we could be able to move them. > I'm not able to move, same as you. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2015/11/11 14:40:43: > > > From: Akihiro Motoki <amotoki(a)gmail.com> > > To: Ying Chun Guo/China/IBM@IBMCN > > Cc: "Ian Y. Choi" <ianyrchoi(a)gmail.com>, Openstack-i18n <openstack- > > i18n(a)lists.openstack.org> > > Date: 2015/11/11 15:05 > > Subject: Re: [Openstack-i18n] I18n wiki page is translatable > > > > Daisy, > > > > It sounds good to me, but normal users like me cannot move pages. > > I got Permission Error. Could you handle all moving of pages? > > > > > > 2015-11-11 15:05 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > > > Thank you for the explain Ian. > > > I think we could move the wiki pages for language teams to > > > /I18nTeam/team/<language-code>, > > > and then keep /I18nTeam/<language-code> for the translation page of > > > I18nTeam. > > > > > > How do you think about it, Akihiro? > > > > > > Best regards > > > Ying Chun Guo (Daisy) > > > > > > > > > "Ian Y. Choi" <ianyrchoi(a)gmail.com> wrote on 2015/11/11 00:55:07: > > > > > >> From: "Ian Y. Choi" <ianyrchoi(a)gmail.com> > > >> To: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun Guo/China/IBM@IBMCN > > >> Cc: Openstack-i18n <openstack-i18n(a)lists.openstack.org> > > >> Date: 2015/11/11 00:55 > > >> Subject: Re: [Openstack-i18n] I18n wiki page is translatable > > > > > > > > >> > > >> Hello Akihiro, > > >> > > >> Actually I suggested a translatable I18nTeam wiki page [1] for Korean > > >> during last Tokyo Design Summit. > > >> After saying it, I found that there might be a problem in > Japanese local > > >> team > > >> because Japanese language team already used /ja page, as you > mentioned and > > >> which would make conflict with translation functionality in OpenStack > > >> wiki. > > >> > > >> Let me first say why Korean translation page for I18nTeam is > needed and > > >> how Korean translation team wants to use two wiki pages separately: > > >> > > >> 1) https://wiki.openstack.org/wiki/I18nTeam/ko > > >> : To provide Korean guys with official I18nTeam introduction > wiki page > > >> : I think "Local Translation Teams" section is needed because this > > >> information is > > >> beneficial with the knowledge of the various language team > activities. > > >> > > >> 2) https://wiki.openstack.org/wiki/I18nTeam/team/ko_KR > > >> (I found that Daisy moved from .../ko_KR to .../team/ko_KR. > Thank you!) > > >> : To introduce Korean translation team with details and our > specific > > >> translation rules > > >> : Providing links for OpenStack I18n official introduction wiki > page & > > >> its translation > > >> > > >> I would like to respect I18nTeam official wiki page, and this > > >> information is written in English. > > >> In my opinion, translating this page would more clearly advertise > > >> OpenStack I18n overall activities to more Korean. > > >> > > >> This requirement and need might be different from various local > > >> translation teams, I think, > > >> and I also would like to respect the ways Japanese team used more > than 1 > > >> year. > > >> > > >> So I would like to suggest not to include "<languages />" tag on > [1] . > > >> As you know, OpenStack Release Note wiki pages such as [2] > > >> contain "<languages />" tag and displays different language > translated > > >> pages on the top part. > > >> > > >> I think this suggestion would satisfy different needs from various > > >> language translation teams. > > >> However, if https://wiki.openstack.org/wiki/I18nTeam page includes > > >> "<languages />" tag, > > >> then it would not fit to not only Japanese translation team, but also > > >> other teams such as French, Polish and so on. > > >> For Korean translation team, our official page contains the > translated > > >> I18nTeam link so it would be okay. > > >> > > >> I am not sure, but Daisy might already think so Daisy only moved from > > >> .../ko_KR to .../team/ko_KR, and > > >> did not include "<languages />" tag on [1] :) > > >> > > >> This is just my suggestion not to conflict with your team and to > > >> accomplish our team requirement, > > >> and I would like to listen Daisy's opinion and other language > teams' > > >> opinions. > > >> > > >> [1] https://wiki.openstack.org/wiki/I18nTeam > > >> [2] https://wiki.openstack.org/wiki/ReleaseNotes/Liberty > > >> > > >> > > >> With many thanks, > > >> > > >> /Ian > > >> > > >> Akihiro Motoki wrote on 11/10/2015 8:48 PM: > > >> > In addition, Japanese team maintains the original contents which > > >> > are differ from the English version of I18nTeam page. > > >> > Before enabling translation for I18nTeam, I would like to see a > solution > > >> > for language specific content. > > >> > > > >> > > > >> > 2015-11-10 20:45 GMT+09:00 Akihiro Motoki <amotoki(a)gmail.com>: > > >> >> I noticed the existing language team page cannot be edited. > > >> >> For example, https://wiki.openstack.org/wiki/I18nTeam/ja > exists from > > >> >> more than one year ago. > > >> >> After this change, we can no longer edit the original page. > > >> >> What should we do? > > >> >> > > >> >> In addition, I18nTeam wiki page contains contents which is not > > >> >> appropriate for translation, > > >> >> for example, "Local Translation Teams" section. > > >> >> As a local team coordinator, I don't like to display this > section in a > > >> >> translated version. > > >> >> > > >> >> Thanks, > > >> >> Akihiro > > >> >> > > >> >> 2015-11-10 18:11 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > > >> >>> Hi, > > >> >>> > > >> >>> As requested by Korean team, the wiki page of I18nTeam is > > >> translatable now. > > >> >>> If you want to translate this page into your own language, > > >> please go ahead. > > >> >>> Thank you. > > >> >>> > > >> >>> Best regards > > >> >>> Ying Chun Guo (Daisy) > > >> >>> > > >> >>> > > >> >>> _______________________________________________ > > >> >>> 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 > > >> > > >> -- > > >> /Ian > > >> > > > > > >

1 0

I18n wiki page is translatable
by Ying Chun Guo 10 Nov '15

10 Nov '15

Hi, As requested by Korean team, the wiki page of I18nTeam is translatable now. If you want to translate this page into your own language, please go ahead. Thank you. Best regards Ying Chun Guo (Daisy)

3 6

Granting access for a new translator for the finnish (finland) translation project
by Jori Kuusinen 10 Nov '15

10 Nov '15

Hi all i18n mailing list members, I registered myself for the finnish (finland) translation project page and would like to have myself granted as a contributor. As a global project owner, I think "Daisy" is in charge for granting access if I'm not mistaken. Looking forward to begin contributing for the project. With kind regards, J o r i

1 0

FYI: [openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka
by KATO Tomoyuki 08 Nov '15

08 Nov '15

FYI. KATO Tomoyuki ---- As we discussed at the summit, the release management team is modifying our change management tracking tools and processes this cycle. This email is the official announcement of those changes, with more detail than we provided at the summit. In past cycles, we have used a combination of Launchpad milestone pages and our wiki to track changes in releases. We used to pull together release notes for stable point releases at the time of release. Most of that work fell to the stable maintenance and release teams. Similarly, the release managers worked with PTLs and release liaisons at each milestone checkpoint to update Launchpad to accurately reflect the work completed at each stage of development. It's a lot of work to fix up Launchpad and assemble the notes and make sure they are accurate, which has caused us to be a bottleneck for clear and complete communication at the time of the release. We have been looking for ways to reduce that effort for these tasks and eliminate the bottleneck for some time. This cycle, to address these problems for our ever-growing set of projects, the release management team is introducing a new tool for handling release notes as files in-tree, to allow us to simply and continuously build the release notes for stable branch point releases and milestones on the master branch. The idea is to use small YAML files, usually one per note or patch, to avoid merge conflicts on backports and then to compile those files in a deterministic way into a more readable document for readers. Files containing release notes can be including in patches directly, or you can create a separate patch with release notes if you want to document a feature than spans several patches. The tool is called Reno, and it currently supports ReStructuredText and Sphinx for converting note input files to HTML for publication. Reno is git branch-aware, so we can have separate release notes documents for each release series published together from the master build. The documentation for Reno, including design principles and basic usage instructions, is available at [1]. For now we are focusing on Sphinx integration so that release notes are published online. We will add setuptools integration in a future version of Reno so that the release notes can be built with the source distribution. As part of this rollout, I will also be updating the settings for the gerrit hook script so that when a patch with "Closes-Bug" in the commit message is merged the bug will be marked as "Fix Released" instead of "Fix Committeed" (since "Fix Committed" is not a closed state). When that work is done, I'll send another email to let PTLs know they can go through their existing bugs and change their status. We are ready to start rolling out Reno for use with Liberty stable branch releases and in master for the Mitaka release. We need the release liaisons to create and merge a few patches for each project between now and the Mitaka-1 milestone. 1. We need one patch to the master branch of the project to add the instructions for publishing the notes as part of the project sphinx documentation build. An example patch for Glance is in [2]. 2. We need another patch to the stable/liberty branch of the project to set up Reno and introduce the first release note for that series. An example patch for Glance is in [3]. 3. Each project needs to turn on the relevant jobs in project-config. An example patch using Glance is in [4]. New patches will need to be based on the change that adds the necessary template [5], until that lands. 4. Reno was not ready before the summit, so we started by using the wiki for release notes for the initial Liberty releases. We also need liaisons to convert those notes to reno YAML files in the stable/liberty branch of each project. Please use the topic "add-reno" for all patches so we can track adoption. Once those merge, project teams can stop using Launchpad for tracking completed work. We will still use Launchpad for bug reports, for now. If a team wants to continue using it for tracking blueprints, that's fine. If a team wants to use Launchpad for scheduling work to be done in the future, but not for release tracking, that is also fine. The release management team will no longer be reviewing or updating Launchpad as part of the release process. Thanks, Doug [1] http://docs.openstack.org/developer/reno/ [2] https://review.openstack.org/241323 [3] https://review.openstack.org/241322 [4] https://review.openstack.org/241344 [5] https://review.openstack.org/241343 __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

What's Up, Doc? 6 November 2015
by Lana Brindley 05 Nov '15

05 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, Wow! What a great Summit! And isn't Tokyo a truly beautiful and amazing city? Thank you so much to the Japanese Stackers who hosted us, and to everyone who came along to the docs sessions and helped us hammer out a great plan for Mitaka. I'm very excited about this release! This week, I've been catching up with everything that happened during Summit, and also working on outreach tasks. Today, I recorded an interview with Foundation about the project, and I've also published a blog post on the same topic, which will be published soon. You might also like to check out the Superuser interview Anne and I did about the docs while we were in Tokyo: http://superuser.openstack.org/articles/openstack-documentation-why-it-s-im… == Progress towards Mitaka == 152 days to go! 77 bugs closed so far for this release. API Docs * The API docs are will be switched to swagger: http://specs.openstack.org/openstack/docs-specs/specs/liberty/api-site.html DocImpact * I've removed the WIP from this blueprint, and will be working on this from next week: https://blueprints.launchpad.net/openstack-manuals/+spec/review-docimpact RST Conversions * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * Ops Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/ops-guide-rst ** Lana will reach out to O'Reilly to discuss the printed book before this work begins * Config Ref ** Thanks for all the offers of help on this one! Please contact the Config Ref Speciality team: https://wiki.openstack.org/wiki/Documentation/ConfigRef Reorganisations * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * User Guides ** https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… ** Contact the User Guide Speciality team: https://wiki.openstack.org/wiki/User_Guides Training * Labs ** https://blueprints.launchpad.net/openstack-manuals/+spec/training-labs * Guides ** Upstream University & 'core' component updates, EOL Upstream Wiki page. Document openstack-doc-tools * Need volunteers for this! Reorganise index page * The API docs have already moved off the front page * We need volunteers to look at the organisation of this page and to write one-sentence summaries of each book == Doc team meeting == Meetings will kick off again next week with the APAC meeting: APAC: Wednesday 11 November, 00:30:00 UTC US: Wednesday 18 November, 14:00 UTC 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 - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWPC4TAAoJELppzVb4+KUynpUH/30Y6pv7Zrse+YM1ki2pqLqi dp0f9RysJQkvXOA7OWy48kWLWXgMF0/hq1DIhrZ9AlsUCGOGC04/YVGNyaCAxMkx TTpyi6gJWl9Fiwbrc6k63MPx7OMFDcGu8KQow7tCBewH0jYngiJeP/mxIP6AnhBy SHVsZZ4OG99w/xZyUe8rVGkpXLFUfow8u0r4hCLlFGSUxLD3jz8ABp2HX7mf3ICi 0u1rgxD08lWSHPHRmhzUZ+kx7uW1ZY0UWiX1rsyTU690dsYbYeJSUcY+Saf2md52 eIGk7yevZaYczXvn9vo/rfwZCc4G5jyRFp55yR/BfD/2NVsjmt2vvguWTnDywEE= =Y0ik -----END PGP SIGNATURE-----

1 0

IRC meeting tomorrow
by Ying Chun Guo 04 Nov '15

04 Nov '15

1 0

mark as read-only policy
by KATO Tomoyuki 01 Nov '15

01 Nov '15

Hi Daisy, Today, I found some projects are translable at both master and stable-liberty branch. In my understand, only one branch should be translable. Just a example,I do not check all projects. * ironic * ceilometer Regards, KATO Tomoyuki

3 6

magnum-ui translation setup
by Andreas Jaeger 31 Oct '15

31 Oct '15

Steve and myself have been working on fixing the broken translation for magnum-ui. I didn't notice that it uses *two* pot files like horizon (one for python files, one for javascript) and uses as well a django and djangojs file and thus wrote these: https://review.openstack.org/#/c/240650/ https://review.openstack.org/#/c/240651/ Will these duplicated names - django in both horizon and magnum-ui - cause any problems in the running system? I doubt it since already horizon has *two* different django files but wanted to double check - and ask for review of the above. I think we need to use this setup for other dashboard related projects, so also for designate-dashboard. Reviews and comments are welcome, 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

1 0

I18n team meet up in Tokyo
by Ying Chun Guo 30 Oct '15

30 Oct '15

3 2

What's Up, Doc? 三鷹 Summit Edition
by Lana Brindley 29 Oct '15

29 Oct '15

Hi everyone, Welcome to the Summit edition of the docs newsletter! Docs have had a wonderfully productive week here in Tokyo, and we've now established a plan for Mitaka. This newsletter covers the more important announcements, and the main points we want to hit in the next release. Karin has kindly written up the summary of the Design Summit sessions here: https://etherpad.openstack.org/p/Mitaka-Docs-Meetup == Mitaka Goals == This is the list at the moment. There are more notes in the docs etherpads, and not everything has blueprints yet. * Switch API docs over to swagger http://specs.openstack.org/openstack/docs-specs/specs/liberty/api-site.html (???) * Implement new docimpact plan: https://blueprints.launchpad.net/openstack-manuals/+spec/review-docimpact * RST Conversions: ** Arch Guide: https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Ops Guide: https://blueprints.launchpad.net/openstack-manuals/+spec/ops-guide-rst (pending O'Reilly conversation) ** Config Ref * Reorganisations: ** Arch Guide: https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Ops Guide: https://blueprints.launchpad.net/openstack-manuals/+spec/improve-ops-guide ** User Guides: https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… * Training ** Labs: https://blueprints.launchpad.net/openstack-manuals/+spec/training-labs ** Guides: Upstream University & 'core' component updates, EOL Upstream Wiki page. * First App Guide: testing & improvements * Reorganise the index page * Document the openstack-doc-tools == Speciality Team Changes == More detail on the Speciality Team wiki page: https://wiki.openstack.org/wiki/Documentation/SpecialityTeams * Install Guide is now with Christian Berendt * HA Guide is now with Bogdan Dobrelya * Networking Guide is now with Edgar Magana * New Hypervisor Tuning Guide team with Joe Topjian あなたの東京ありがとう! Lana Lana Brindley Technical Writer Rackspace Cloud Builders Australia

1 0

dashboard translation check site
by KATO Tomoyuki 29 Oct '15

29 Oct '15

Hi, Elizabeth, Akihiro, Daisy Just a memorandum from the Summit session. We need share the operation process of Akihiro's personal dashboard translation check site before we prepare the our official check site. The check site is built with DevStack. Basic scripts for import and export tranlations are: https://github.com/amotoki/horizon-i18n-tools * need update from Transifex client to Zanata client Akihiro-san, please follow up and correct the details. Thanks, KATO Tomoyuki

2 1

Request to join local Translation in thai language.
by sawangpong muadphet 28 Oct '15

28 Oct '15

Dear Team My name is Sawangpong Muadphet from Thailand. I would like to join the Local Translation Teams for Thailand. I am contribute on Openstack promotion in Thailand for 2 yrs. I do training openstack also. But thai language is not in the openstack yet. I do hope that Thai people will have more opportunity in openstack my transfix account: sawangpongm Sincerely yours Sawangpong Muadphet CEO www.itbakery.net <http://www.itbakery.net/> Thailand

4 3

Call for Presentation Proposals for FUEL GILT Conference 2015!
by Rajesh Ranjan 24 Oct '15

24 Oct '15

FUEL GILT Conference is one of the largest events of FOSS language technology - Its challenges, solutions, best practices and its conventions. Due to some unavoidable reasons, we are a bit late in announcing CFP. We apologize for the same. We are late, but this time we have grand plan to celebrate the presence of our languages on new technology platform. Yes, we have a grand plan! Total three days for the event : 20,21 and 22 Nov 2015. So, save these dates on your calender! The host for the event and venue is - Tamil Virtual Academy (Erstwhile Tamil Virtual University), Anna University Campus, Gandhi Mandapam Road, Kottur, Chennai, Tamil Nadu. Thank you TVA. We are happy that, this time Mozilla Localisation Hackathon is being organised as a part of FUEL Gilt Conference 2015. We have FUEL Gilt Conference on 20th Nov and Mozilla l10n Hackthon on 21-22 Nov.However, the localization hackathon is open to the invited members only. If you are one of the localizers contributing to Mozilla, you may contact your locale leader to know more about it. This year Mozilla Corporation, Centre for Development of Advance Computing (C-DAC), Pune and Red Hat are the main organizers of the Conference. The event is being hosted at Tamil Virtual Academy and supported by Free Software Foundation Tamil Nadu. Thank you all for helping hand. Call for Presentation Proposal is open till Oct 31, 2015. Please send your proposal in required format mentioned on the page: http://fuelproject.org/gilt2015/index FUEL is growing only because of the support of volunteer communities world-wide and several well known organizations! The power of the event is the power of collaboration, the power of sharing, the power of volunteerism! Currently, More than 60 language communities are working with the FUEL Project. Since 2008, FUEL Project is consistently working with the different language communities to provide standard linguistic resources eg. Terminologies, style guides, assessment methods etc. to the world.Like last year, please collaborate and cooperate to make the event a huge success! For more details, please visit: http://fuelproject.org/gilt2015/index -- Rajesh Ranjan www.rajeshranjan.in @kajha <https://twitter.com/kajha> Developing a linguistic standard for language localization <http://www.livemint.com/Industry/zWJ1943VQmwABkZGmMTT2H/Developing-a-lingui…>

1 0

Horizon problem in pt
by Andreas Jaeger 22 Oct '15

22 Oct '15

Looking at todays bot run for Horizon on stable/liberty - see https://jenkins.openstack.org/job/horizon-propose-translation-update-libert… - I noticed a failure writing pt file for openstack_dashboard/locale/django: 2015-10-20 06:36:20.057 | [INFO] Writing translation file in locale pt for document openstack_dashboard/locale/django 2015-10-20 06:36:20.536 | [ERROR] Operation failed: javax.xml.bind.UnmarshalException 2015-10-20 06:36:20.536 | - with linked exception: 2015-10-20 06:36:20.536 | [org.xml.sax.SAXParseException; lineNumber: 4; columnNumber: 357; An invalid XML character (Unicode: 0x8) was found in the element content of the document.] 2015-10-20 06:36:20.536 | 2015-10-20 06:36:20.536 | To retry from the last document, please set the following option(s): 2015-10-20 06:36:20.536 | 2015-10-20 06:36:20.536 | --from-doc "openstack_dashboard/locale/django" 2015-10-20 06:36:20.537 | Is there anybody to fix this, please? 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 7

I18n contributors meetup in Tokyo
by Ying Chun Guo 21 Oct '15

21 Oct '15

1 0

I18n sessions plan in Tokyo summit
by Ying Chun Guo 21 Oct '15

21 Oct '15

Hello, team I plan to have two I18n working sessions and a half day I18n contributors meet up in Tokyo summit. Here are the descriptions of the two working sessions. Working session #1. Time: 4:40pm - 5:20pm on Oct. 27, Tuesday Title: Review of the tool support in Liberty translations Abstract: We just moved to the new translation tool in Liberty. In this session, we will review how Liberty translation went with Zanata. We will collect issues/problems we met in Liberty translation, talk about how to improve in the future, and figure out the next steps. The agenda will be tracked here: https://etherpad.openstack.org/p/tokyo-translation-tool-support Working session #2. Time: 5:30pm - 6:10pm on Oct. 27, Tuesday Title: How translation schedule fits the development schedule? Abstract: In Liberty, we redefined the string freeze, split into soft string freeze and hard string freeze. In this session, we will collect the feedback to translation schedule from both translators and developers, refine the definition of string freeze, and figure out a better translation schedule for next release. The agenda will be tracked here: https://etherpad.openstack.org/p/tokyo-translation-schedule The time of i18n meet up is not decided yet. It's a kind of round table, and doesn't have title and abstract. People could join and raise any discussions/questions related with i18n/l10n/translation there. We will use this page to track the agenda: https://etherpad.openstack.org/p/tokyo-i18n-meetup If you have any issues with these sessions, please let me know. Thank you. Best regards Ying Chun Guo (Daisy)

2 2

Stable translations?
by Andreas Jaeger 19 Oct '15

19 Oct '15

We had a few days ago some IRC discussion on how to translate stable branches and wrote up the following: https://wiki.openstack.org/wiki/Translations/Infrastructure#New_proposal Is that clear? Is it something we should try? Daisy, did you talk to the stable team yet? 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 2

How is openstack-manuals/common-rst updated?
by Akihiro Motoki 17 Oct '15

17 Oct '15

Hi team, During translation of common-rst in Zanata, I found a bit odd entries in openstack-manuals/doc/common-rst/source/locale/common-rst.pot. When and how is openstack-manuals/common-rst updated? For example, we see the following in common-rst.pot: --- #: ../common/app_support.rst:3 msgid "Community support" msgstr "" #: ../common/app_support.rst:5 msgid "Community Support" msgstr "" ---- However, we actually have only the first entry in common-rst/*.rst: --- $ grep -r 'Community Support' doc/common-rst/*.rst $ grep -r 'Community support' doc/common-rst/*.rst doc/common-rst/app_support.rst:Community support --- If you look at app_support.rst, we have only the first one. Where does the second one come from? In tools/generatepot-rst.sh, processing on 'common-rst' is skipped. I wonder which script we update common-rst.pot. Thanks, Akihiro

3 7

Re: [Openstack-i18n] [Openstack] OpenStack Kilo Release Note Translation
by Tom Fifield 17 Oct '15

17 Oct '15

Hi, I just clicked "Mark This Page for Translation", which should fix this, I think. """ The page ReleaseNotes/Kilo has been marked up for translation with 166 translation units. The page can now be translated. """ Regards, Tom On 01/05/15 10:40, Ray Sun wrote: > By the way, I found this in mediawiki translation plugin document: > > This page contains changes which are not marked for translation." if you > are not a translation administrator > > Best Regards > -- Ray > > On Fri, May 1, 2015 at 10:38 AM, Ray Sun <xiaoquqi(a)gmail.com > <mailto:xiaoquqi@gmail.com>> wrote: > > Stackers, > I try to translate OpenStack Kilo release note, but I don't think I > have permission to do that even if I added translation tag for it. > Any one who have that permission, please help. Thanks. > > Best Regards > -- Ray > > > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack(a)lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >

4 10

New translation plan is published
by Ying Chun Guo 15 Oct '15

15 Oct '15

Hello, team During the IRC meeting yesterday, the team decided to focus on "installation guide" translation in the next 3 months. The documents of "installation guide" is in the project "openstack-manuals". We will work with the master version, because the liberty version is not branched yet. When documentation team branches the stable-liberty, we will create the same version in Zanata and switch our translations there. The plan is published in the homepage of translate.openstack.org. BTW, I failed to set the hyperlink to doc "install-guide" directly. The hyperlink in the homepage will direct you to the project "openstack-manuals", not the doc. Then you have to select document "install-guide" from the list. Thank you. Best regards Ying Chun Guo (Daisy)

1 0

IRC meeting tomorrow
by Ying Chun Guo 14 Oct '15

14 Oct '15

Hi, team We will have our IRC meeting tomorrow in IRC channel #openstack-meeting at 1300 UTC on 15th October. I'm going to discuss following topics: Discussion: document translation plan Open discussions If you have topics, please propose here. Best regards Ying Chun Guo (Daisy)

2 1

Fwd: [Bug 1505870] [NEW] 安装配置控制节点服务器 in Red Hat Enterprise Linux 7, CentOS 7, and Fedora 20 的 OpenStack 安装手册 - Kilo
by Lana Brindley 14 Oct '15

14 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi i18n team, I noticed this bug in our queue today. Zhu Rong has been kind enough to help me with the translation. I understand that there's an issue in the Chinese version of the guide, which doesn't appear in the English version. Are you able to help? Thank you, Lana - -------- Forwarded Message -------- Subject: [Bug 1505870] [NEW] 安装配置控制节点服务器 in Red Hat Enterprise Linux 7, CentOS 7, and Fedora 20 的 OpenStack 安装手册 - Kilo Date: Wed, 14 Oct 2015 01:46:28 -0000 From: fangc <swjfc22(a)163.com> Reply-To: Bug 1505870 <1505870(a)bugs.launchpad.net> To: openstack(a)lanabrindley.com Public bug reported: 这个显示是kilo安装手册，但是在同步数据时参数仍然用的juno，这会在后续步骤中报错。 # su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf \ --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade juno" neutron juno应该改为kilo才可以，不然下一步就会出错，网络节点无法连接到控制节点。 - ----------------------------------- Built: 2015-03-30T21:27:48 08:00 git SHA: 3da25b5440ad6ef89618eb6ec20c8dc8f465d3c6 URL: http://docs.ocselected.org/openstack-manuals/kilo/install/rpm/content/neutr… source File: file:/media/develop/develop/openstack/openstack-manuals/generated/zh_CN/install-guide/section_neutron-controller-node.xml xml:id: neutron-controller-node ** Affects: openstack-manuals Importance: Undecided Status: New - -- You received this bug notification because you are subscribed to openstack-manuals. Matching subscriptions: Manuals Bugs, Openstack Manuals https://bugs.launchpad.net/bugs/1505870 Title: 安装配置控制节点服务器 in Red Hat Enterprise Linux 7, CentOS 7, and Fedora 20 的 OpenStack 安装手册 - Kilo Status in openstack-manuals: New Bug description: 这个显示是kilo安装手册，但是在同步数据时参数仍然用的juno，这会在后续步骤中报错。 # su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf \ --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade juno" neutron juno应该改为kilo才可以，不然下一步就会出错，网络节点无法连接到控制节点。 ----------------------------------- Built: 2015-03-30T21:27:48 08:00 git SHA: 3da25b5440ad6ef89618eb6ec20c8dc8f465d3c6 URL: http://docs.ocselected.org/openstack-manuals/kilo/install/rpm/content/neutr… source File: file:/media/develop/develop/openstack/openstack-manuals/generated/zh_CN/install-guide/section_neutron-controller-node.xml xml:id: neutron-controller-node To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1505870/+subscriptions -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWHcyeAAoJELppzVb4+KUyz9sH/2s20AHuYFX7IFoZJscAg1kS T9DTbrDdBay9LN7Z9QYgc/lSSnW6K7IzQSNOwlgHD1BvoAI2pW1AMuYrTuy69Yu4 h1Udn3f2j+e79U19qvqoOTpu/5QUiXwD+ySPHhUbVEkXg6jvrQmrYtwFyO8gSsb/ yWsBvuxVc1yqhsUnLm5/PG92Ijy/Jh5d5NxaR+LeUcDIGg8GL15CQczwEP2PZMAj zHvxYrhw10YMs+jhtHAfTPOTr1cv38KIuzpBeki7sQ9yz+Gb07/2Oy+Lm9/QzjKr oDvUr3XdERona8/Yq/fGPNb/ReKsC393vgtnxvYc+t9znoBMEYpLV8iDpq7Q5D4= =+JvA -----END PGP SIGNATURE-----

3 4

API Quick Start now RST
by Anne Gentle 13 Oct '15

13 Oct '15

Hi all, The API Quick Start migration change has landed and Andreas has been working on language builds for it: https://review.openstack.org/232937 https://review.openstack.org/232945 https://review.openstack.org/232950 It will build to developer.openstack.org/LANG/api-guide/quick-start. The goal is to also build developer.openstack.org/api-guide/compute -- one directory for each service, sourced from each project team's preferred location. I'm not sure that you need to prioritize the API Quick Start for translation, but wanted to let this list know. Thanks, Anne -- Anne Gentle Rackspace Principal Engineer www.justwriteclick.com

4 8

Approved & rejected translations after versions merging
by Ying Chun Guo 13 Oct '15

13 Oct '15

Hi, A translation could be approved or rejected. This action is called translation review. A version merging is to copy all matching translated/approved translations from the source version to the target version. If there is an existing translated/approved translation, the newer translation will be used. After liberty translations are closed, we will merge translations from stable-liberty version to master version, and then open both stable-liberty version and master version to accept translations. I investigated whether translation review would be copied after version merging. Here are the results: The review result - "approve" will be copied to the target version, while the review result - "reject" will not. Only "rejecting" existing translations will not have the same translations rejected in master version. But "approving" existing translations will have the same translations approved in the master version. That means, if there are "rejected" translations in stable-liberty, it's better to input the correct translations. The investigation result is OK with me. If you have different opinions, please propose here. If you want to understand more about version merging, please let me know. Best regards Ying Chun Guo (Daisy)

2 9

[openstack-i18n], [openstack-infra][project-config] Glance metadef JSON files need i18n support.
by Okuma, Wayne 09 Oct '15

09 Oct '15

Hi All, Not sure if this email got through the last time I sent it, so sending it again. Sorry if I've created a duplicate. I have a blueprint that I need feedback/approval for Mitaka. Please review it at: https://blueprints.launchpad.net/glance/+spec/metadefs-i18n-support https://review.openstack.org/#/c/229211/ Work for it is at: glance: https://review.openstack.org/#/c/229690/ python-glanceclient: https://review.openstack.org/#/c/231810/ project-config: https://review.openstack.org/#/c/232304/ Thanks and Regards, Wayne Okuma

1 0

[openstack-dev][glance]; [openstack-i18n]; [openstack-infra][project-config]; Glance metadefs JSON i18n support
by Okuma, Wayne 09 Oct '15

09 Oct '15

Hi All, I have a blueprint that I need feedback/approval for Mitaka. Please review it at: https://blueprints.launchpad.net/glance/+spec/metadefs-i18n-support https://review.openstack.org/#/c/229211/ Work for it is at: glance: https://review.openstack.org/#/c/229690/ python-glanceclient: https://review.openstack.org/#/c/231810/ project-config: https://review.openstack.org/#/c/232304/ Thanks and Regards, Wayne Okuma

1 0

Survey results of translated materials in Japanese community
by Akihiro Motoki 09 Oct '15

09 Oct '15

Hi I18N team, In the last moment in Liberty cycle, many translations of server side projects were incorporated. I think many language teams need to decide their priorities among various resources in the next release. I would like to share the survey result on translated materials we made in Japan. We, Japanese community, made a rough survey on the interest in translated materials in OpenStack 5th birthday event in Japan (in July). It was done in a lightning talk and we roughly count the number of raised hands. We have >300 folks in the hall. The question is very simple: Do you want or use translated version of the following or use English version? The results are as follows. The numbers are percentage of interested folks. - Horizon : 70~80% - Documentations : 40~50% (as long as they are kept up-to-date) - CLI : <5% (7~8 of >300) - Log messages : 0 (I could not find raised hands) The following is my impression on priories in Japanese translations. - Horizon and documentations: should be prioritized. horizon first. - CLI: low priorities - log messages: Lowest priorities. - User visible messages from server projects: low priorities (though our survey didn't cover it). Note that it need to be prioritized if Horizon use these strings directly. This is just my impression, and other languages must have different priorities. Thanks, Akihiro

2 2

What's Up, Doc? 9 Oct 2015
by Lana Brindley 08 Oct '15

08 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, We're hurtling head first to Liberty, with only about a week left to go. I've been working on Summit preparations, and making sure we're ready to go when the time hits. This week, I'm working on Release Notes, keeping an eye on the final Install Guide testing, and some other housekeeping tasks. This is my last docs newsletter before the Liberty release, although I'll endeavour to get a special Summit edition out as well. We will pick up regular meetings (and other tasks, like core team reviews) after the Summit. == Progress towards Liberty == 5 days to go! 601 bugs closed so far for this release. The main things that still need to be done before release: - - Testing, testing, testing: https://wiki.openstack.org/wiki/Documentation/LibertyDocTesting - - Reviews: https://review.openstack.org/#/q/status:open+project:openstack/openstack-ma… and https://review.openstack.org/#/q/status:open+project:openstack/api-site,n,z - - Bug triage: https://bugs.launchpad.net/openstack-manuals/+bugs?search=Search&field.stat… == Release Notes == Can all PTLs and Cross-Project Liaisons please check the Release Notes page, and ensure they've included all the new features for their project here: https://wiki.openstack.org/wiki/ReleaseNotes/Liberty The best way to do this (I'm told) is to go through the blueprints created for Liberty. I will be editing these during the next few days, so please ensure you're up to date ASAP. Please contact me directly if you have any questions or problems. == Mitaka Summit Prep == Thank you to everyone who provided suggestions for Design Summit sessions. I've now mangled them into a draft schedule, which is available on Sched: http://mitakadesignsummit.sched.org/type/Documentation == Doc team meeting == The US meeting was held this week. The minutes are here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-10-07 The next meetings will be the final meetings before the Liberty release: APAC: Wednesday 14 October, 00:30:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… - -- 東京でお会いしましょう Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJWF1vMAAoJELppzVb4+KUyjNAH/iWkObcXhsCagd/Ht6N5IjsY SRQ1+B9PDpRU1281VCmy0MfIRIGATCOOaSlpumEfpz8lIOnPmR/yXU/mKm6xJ55k gCRCXSdb0wGomn7b346b3kvfRD6AUanVfq/6LnQsP0c6XCH8graqPwB5LMT9ndVm 68n/bOm2KlHh1NHmlI40l7eKOUCL0J82VOgdyqrWup55kg4R96cc1wUFH7gbz0jf 5b7khgD/P6XTzD1dbJIigKMxy8cj49FMx4tsrxdZZxZds2NauoE5inteI7HOuZMH /iBf1SB1NbzFGSGH6upQVVZsxR0vKpq3WO/VwNTtlFZkjPrNDQXt0/n3wLv6REU= =aUM2 -----END PGP SIGNATURE-----

1 0

Re: [Openstack-i18n] Curious Strings
by Alex Eng 08 Oct '15

08 Oct '15

The first source string (all in single line) is from https://github.com/openstack/openstack-manuals/blob/master/doc/install-guid… . According to record in Zanata the second string (broken into 2 entries) is from /neutron-controller-install.rst:13, https://github.com/openstack/openstack-manuals/blob/master/doc/install-guid…, which is broken into 2 lines. Both pot files in github repo ( https://github.com/openstack/openstack-manuals/blob/master/doc/install-guid…) and the one uploaded to Zanata ( https://translate.openstack.org/iteration/view/openstack-manuals/master/doc…) is totally different. --------------------------------------------- Alex Eng Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com On Thu, Oct 8, 2015 at 3:41 AM, Douglas Fish <drfish(a)us.ibm.com> wrote: > Kato, Alex, > > This still seems like a bug to me. The POT file has this as a single > string that is written on two lines > > https://github.com/openstack/openstack-manuals/blob/master/doc/install-guid… > but Kato has shown that is it available in Zanata as two separate strings > to translate. > > In fact, it seems that it's also available as a proper string in Zanata. > This query shows 2 matches: > > https://translate.openstack.org/webtrans/translate?project=openstack-manual… > > > Use the database access client to connect to the database server as the ``root`` user: > > > - Resource ID: 6cfac5f7b0e6f238895e3dcc7ac03206 > - Message Context: > - Source Comment: > - Last Modified By: OpenStack Infra > - Last Modified Time: 09/09/15 11:55 > > which seems expected and proper, and > > Use the database access client to connect to the database server as the > > > - Resource ID: ca3fdc8a1c36bfac2c20fbad11897afb > - Message Context: > - Source Comment: > - Last Modified By: > - Last Modified Time: > > which is unexpected. I don't see anything in the POT file that corresponds > to the 2nd version. > Perhaps the bug is that items that used to be in the POT file but have > been removed remain in Zanata? > > Doug Fish > > > ----- Original message ----- > From: Alex Eng <aeng(a)redhat.com> > To: KATO Tomoyuki <tomo(a)dream.daynight.jp> > Cc: Openstack-i18n <openstack-i18n(a)lists.openstack.org> > Subject: Re: [Openstack-i18n] Curious Strings > Date: Tue, Oct 6, 2015 11:19 PM > > Hi Kato, > > According the source, the string is extracted from > https://github.com/openstack/openstack-manuals/blob/master/doc/install-guid…. > > > Its a markup syntax with the single quote. The source string has been in > this format since it first imported into Zanata. > > You can see the history for this file: > https://github.com/openstack/openstack-manuals/commits/master/doc/install-g… > > > https://github.com/openstack/openstack-manuals/commit/f22caf8bc349b6a6b97a7… > > > --------------------------------------------- > > Alex Eng > Globalisation Tools Engineering > DID: +61 3514 8262 <callto:+61+3514+8262> > Mobile: +614 2335 3457 <callto:+614+2335+3457> > > Red Hat, Asia-Pacific Pty Ltd > Level 1, 193 North Quay > Brisbane 4000 > Office: +61 7 3514 8100 <callto:+61+7+3514+8100> > Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> > Website: www.redhat.com > > On Wed, Oct 7, 2015 at 1:53 PM, KATO Tomoyuki <tomo(a)dream.daynight.jp> > wrote: > > Hi all, > > I encounter a curious situation. > The string [1] is separately displayed in Zanata [2]. > > #890 @Zanata > Use the database access client to connect to the database server as the > > #891 @Zanata > ``root`` user: > > This situation itself is very inconvinient for me to translate. > > Any thought? > Zanata bug???? > > [1] source message catalog: > > https://github.com/openstack/openstack-manuals/blob/master/doc/install-guid… > > [2] Zanata > openstack-manuals > install-guide > master > https://translate.openstack.org/iteration/view/openstack-manuals/master > > Thanks, > KATO Tomoyuki > > _______________________________________________ > 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 > > >

3 3

Re: [Openstack-i18n] Liberty translations are closing
by Ying Chun Guo 08 Oct '15

08 Oct '15

Hello, team We have finished Liberty translations. Look at the achievements we have made within 1 month: * Horizon translations 12 language teams finished Horizon translations 100%. 13 languages will be shipped together with Liberty. They are: Chinese (China), Chinese (Taiwan), Czech, English (Australia), French, German, Japanese, Korean (South Korea), Polish (Poland), Portuguese (Brazil), Russian, Spanish and Turkish (Turkey). * Nova message translations 3 language teams finished the translations of nova.po 100%. They are: Chinese (China), Czech, and German. 12 language translations of Nova messages are more than 75% and will be imported into Liberty branch. * In total, we have translated more than 1 million words in 1 month. (The exact number is 1037k.) It's an amazing number. Congratulations for those language teams, and many thanks to the hard work of translators, reviewers and coordinators. We will conclude liberty translation from today. According to Andreas suggestion, I leave stable-liberty in open status. You could continue the improvement of stable-liberty versions. All your improvements will be imported into liberty branches and shipped with the liberty stable releases. As to the master versions, I have set them writable and merged the translations of stable-liberty versions into master versions. Both stable-liberty and master versions are open to accept translations now. Thank you again for your hard work. Best regards Ying Chun Guo (Daisy) Ying Chun Guo/China/IBM wrote on 10/05/2015 10:53:37 PM: > From: Ying Chun Guo/China/IBM > To: Openstack-i18n <openstack-i18n(a)lists.openstack.org> > Date: 10/05/2015 10:53 PM > Subject: Liberty translations are closing > > Hello, team > > Liberty translations will be closed in 24 hours from now on. > After that, I will set stable-liberty "Read Only" for a few days, > in order to preserve time for development team to package them. > > I see zh-TW, fr, tr-TR have a very few words left in Horizon translations: > https://translate.openstack.org/iteration/view/horizon/stable-liberty. > Translation patches to Horizon and Heat still have unit test errors: > https://review.openstack.org/#/q/status:open+branch:stable/liberty > +topic:zanata/translations,n,z > > Translation teams have only 24 hours to clean up your work. > Please hurry up. > Thank you for the corporation. > > Best regards > Ying Chun Guo (Daisy)

5 16

Curious Strings
by KATO Tomoyuki 07 Oct '15

07 Oct '15

Hi all, I encounter a curious situation. The string [1] is separately displayed in Zanata [2]. #890 @Zanata Use the database access client to connect to the database server as the #891 @Zanata ``root`` user: This situation itself is very inconvinient for me to translate. Any thought? Zanata bug???? [1] source message catalog: https://github.com/openstack/openstack-manuals/blob/master/doc/install-guid… [2] Zanata > openstack-manuals > install-guide > master https://translate.openstack.org/iteration/view/openstack-manuals/master Thanks, KATO Tomoyuki

3 2

Fwd: [OpenStack-docs] Import failure - Japanese Install Guide
by Andreas Jaeger 07 Oct '15

07 Oct '15

Sorry, send to wrong list... Andreas -------- Forwarded Message -------- Subject: [OpenStack-docs] Import failure - Japanese Install Guide Date: Wed, 7 Oct 2015 08:51:24 +0200 From: Andreas Jaeger <aj(a)suse.com> To: openstack-docs(a)lists.openstack.org <openstack-docs(a)lists.openstack.org> Today's translation import of openstack-manuals fails the testing: 2015-10-07 06:49:00.393 | ++ msgfmt --statistics -o /dev/null doc/install-guide/source/locale/ja/LC_MESSAGES/install-guide.po 2015-10-07 06:49:00.431 | + trans='doc/install-guide/source/locale/ja/LC_MESSAGES/install-guide.po:6685: '\''msgid'\'' and '\''msgstr'\'' entries do not both begin with '\''\n'\'' Could somebody from Japanese team check and fix this, please? This is similar to what we discussed with horizon, let's mark this as error in Zanata. 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 _______________________________________________ OpenStack-docs mailing list OpenStack-docs(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

2 2

"Warning: none, Errors: 1" from the difference of number of lines
by Ian Y. Choi 06 Oct '15

06 Oct '15

Hello, Sorry if I am asking an already discussed issue. I am now reviewing horizon > stable-liberty > Documents (ko-KR) > openstack_dashboard/locale/django before our freezing deadline, as Daisy mentioned. But I have found that some Korean strings still have an error with the following message like: "Not enough lines in translation (expected 4, found 3)". The main reason I think is that in our previous translation platform Transifex, truncating the last empty line was recommended as far as I remember. (If not, Transifex generated an error.) My question is: should we fix those error translated strings with same number of lines and same spaces? I think it would be ignored because when I see Chinese translation, there were the same type of error message for almost translated strings. (Screenshot: https://www.dropbox.com/s/bvd098wsakpi192/Zanata_horizon_translation_exampl… ) And if this error would be negligible to us, are there some ways not to see this type of errors? I would like to copy an example sentence string in Zanata from Korean for my better explanation. <in English>(Translated from) === First, select which type of job that you want to run. This choice will determine which other steps are required === <in Korean>(Translated to) === 먼저, 실행하고자 하는 job 유형 을 선택합니다. 이 선택을 통해 필요로 하는 다른 과정들을 결정할 것입니다. === With many thanks, /Ian

7 13

Liberty translations are closing
by Ying Chun Guo 06 Oct '15

06 Oct '15

Hello, team Liberty translations will be closed in 24 hours from now on. After that, I will set stable-liberty "Read Only" for a few days, in order to preserve time for development team to package them. I see zh-TW, fr, tr-TR have a very few words left in Horizon translations: https://translate.openstack.org/iteration/view/horizon/stable-liberty. Translation patches to Horizon and Heat still have unit test errors: https://review.openstack.org/#/q/status:open+branch:stable/liberty+topic:za… Translation teams have only 24 hours to clean up your work. Please hurry up. Thank you for the corporation. Best regards Ying Chun Guo (Daisy)

3 2

API Quick Start
by Anne Gentle 05 Oct '15

05 Oct '15

Hi all, I've got a patch in progress to convert the "API Quick Start" from Docbook to RST: https://review.openstack.org/#/c/217467/ Since it has quite a few translations completed, I want to make sure that converting that document is okay with the translators. So, is it okay to convert and build using RST instead of Docbook? Is the tooling available for files in the api-site repository? Thanks, Anne -- Anne Gentle Rackspace Principal Engineer www.justwriteclick.com

3 3

What's Up, Doc? 2 October
by Lana Brindley 01 Oct '15

01 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, Welcome to October, which means: it's nearly release day! I've been brushing up on the release management tasks, and continued my housekeeping duties to make sure we're in shape. The next two weeks will be spent watching the Installation Guide pretty closely, and making sure we get it all tested and ready to ship. If you are looking for something to do this week, please treat Install Guide testing as your main priority from here until 15 October. Also, don't forget to vote in the TC election next week! == Progress towards Liberty == 12 days to go 534 bugs closed so far for this release. The main things that still need to be done as we hurtle towards release: * Testing, testing, testing: https://wiki.openstack.org/wiki/Documentation/LibertyDocTesting * Reviews: https://review.openstack.org/#/q/status:open+project:openstack/openstack - -manuals,n,z and https://review.openstack.org/#/q/status:open+project:openstack/api-site, n,z * Bug triage: https://bugs.launchpad.net/openstack-manuals/+bugs?search=Search&field.s tatus=New == Mitaka Summit Prep == Thank you to everyone who provided suggestions for Design Summit sessions. I've now mangled them into a draft schedule, which looks a little like this: Workrooms (Thursday AM): - - Docs toolchain/infra info session - - IA working session - Ops/Arch Guides & User Guides - - Doc Contributor Guide: new content addition - - API Docs Session Fishbowls (Thursday PM): - - The docs process, plus best practices - - Mitaka planning - deliverables for the next release Meetup (Friday AM): - - Contributors meetup. No agenda. We can assist with setting up devstack/working through the Install Guide during this session Once I have access to Cheddar and Sched, I'll get this allocated more accurately. In the meantime, feedback or questions are welcome. == Bug Triage Process == The core team have been noticing a lot of people trying to close bugs that haven't been triaged recently. It is very important that you have someone else confirm your bug before you go ahead and create a patch. Waiting just a little while for triage can save you (and our core team!) a lot of work, and makes sure we don't let wayward changes past the gate. If you're unsure about whether you need to wait or not, or if you're in a hurry to work on a bug, you can always ping one of the core team on IRC or on our mailing list. The core team members are listed here, and we're always happy to help you out with a bug or a patch: https://launchpad.net/~openstack-doc-core This is even more important than usual as we get closer to the Liberty release, so remember: If it's not triaged, don't fix it! == Doc team meeting == The APAC meeting was held this week. The minutes are here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-09-30 The next meetings will be the final meetings before the Liberty release: US: Wednesday 7 October, 14:00:00 UTC APAC: Wednesday 14 October, 00:30:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_ meeting - -- Remember, if you have content you would like to add to this newsletter, or you would like to be added to the distribution list, please email me directly at openstack(a)lanabrindley.com, or visit: https://wiki.openstack.org/w/index.php?title=Documentation/WhatsUpDoc Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJWDgItAAoJELppzVb4+KUyvy4H/3J5Dg5Z2Rv5yHImXU7ZhY4U chAQQ8ZUTysKcKtShIvqWqiejOWUql0Y2L9cV+28P9A8NFjJ/meWAckjC+LQgl1X WrqDimHjtStkLTft0kbmsVN3HYDpdH9QJhLh0ut3YHieWy5DeFaKZGbnP5MrTwFi 7WPjWCChECyCx0olrsr8AoYtLu9wUjtX0rDFJTC/4T3kZ1wauUnkWeRVT4S2e09c mjpGf7xgkciRqOyFgACzL0dGYXFlQhPxrRAnGMMRjpGERTIkWzlptk5v/oF9rx4v 84B/Ni3eTH2O+uqmVuXzjesvzV27Yzhoq4UvN14SeN7cHJ43mTfVsPi9kUZYPGM= =aCzp -----END PGP SIGNATURE-----

1 0

Re: [Openstack-i18n] Would like Zanata branch to correct 1494819
by Douglas Fish 01 Oct '15

01 Oct '15

1 0

Do your translations have English in them?
by Douglas Fish 01 Oct '15

01 Oct '15

1 0

Re: [Openstack-i18n] Would like Zanata branch to correct 1494819
by Ying Chun Guo 01 Oct '15

01 Oct '15

Hi, The new stable-liberty is created. The old stable-liberty was renamed to stable-libery-backup, and set as ReadOnly. Please verify if the bug is fixed. Thank you. Best regards Ying Chun Guo (Daisy) Douglas Fish/Rochester/IBM wrote on 10/01/2015 09:58:15 AM: > From: Douglas Fish/Rochester/IBM@IBMUS > To: aj(a)suse.com > Cc: guoyingc(a)cn.ibm.com, openstack-i18n(a)lists.openstack.org > Date: 10/01/2015 09:58 AM > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > I have examined the files in the russian-fix branch. They look > right. Also I've tested them and they appear to be working correctly > in Horizon. > > We'll need this in stable-liberty. It renders Horizon pretty broken > for Russian: https://bugs.launchpad.net/openstack-i18n/+bug/1494819 > > Doug Fish > > > > ----- Original message ----- > From: Andreas Jaeger <aj(a)suse.com> > To: Ying Chun Guo <guoyingc(a)cn.ibm.com>, Douglas Fish/Rochester/IBM@IBMUS > Cc: openstack-i18n(a)lists.openstack.org > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > Date: Wed, Sep 30, 2015 7:19 AM > > On 2015-09-30 13:21, Ying Chun Guo wrote: > > Hi, Doug > > > > After testing, I figured out a best way which has the lowest impact. > > 1. Create Russian translation files with only the correct header and the > > pluralitiestranslation items. > > 2. Create a new version named as russian-fix > > 3. Upload the source files and the Russian translation files created in > > #1 to the version russian-fix > > 4. Merge the stable version with version russian-fix > > 5. Rename stable version to stable-old, and rename russian-fix to stable. > > > > You could verify if the issues are fixed in russian-fix ? > > https://translate.openstack.org/iteration/view/horizon/russian-fix > > Do we need this fix for stable-liberty branch as well? > > Let's move forward quickly here for the release, please, > > 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 >

1 0

Re: [Openstack-i18n] IRC meeting tomorrow
by Ying Chun Guo 01 Oct '15

01 Oct '15

Sorry, guys. Today is my National Day. I had so a good time with my family that I forgot the meeting time. Thank you for take it over, Andreas. I will check how reviews merge when versions merge, and will response later. Many thanks for the attendees, and sorry again for my absence. Best regards Ying Chun Guo (Daisy) Andreas Jaeger <aj(a)suse.com> wrote on 10/01/2015 04:34:18 PM: > From: Andreas Jaeger <aj(a)suse.com> > To: Ying Chun Guo/China/IBM@IBMCN > Date: 10/01/2015 04:34 PM > Subject: Re: [Openstack-i18n] IRC meeting tomorrow > > On 2015-09-30 13:46, Ying Chun Guo wrote: > > Hello,team > > > > We will have the IRC meeting at UTC 0600 in the channel > > #openstack-meeting on October 1st. > > We could talk about the ongoing liberty translations: progress, > > importing, issues, and etc. > > If you have other topics, feel free to propose. > > > > Best regards > > Ying Chun Guo (Daisy) > > > > Hi Daisy, > > we missed you today. Hope everything is fine with! > > I took the liberty to run it today, there were a couple of questions > regarding merging back, could you review those, please? > > http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2015/ > openstack_i18n_meeting.2015-10-01-08.10.log.html > > 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 1

Re: [Openstack-i18n] Would like Zanata branch to correct 1494819
by Ying Chun Guo 30 Sep '15

30 Sep '15

Hi, Doug After testing, I figured out a best way which has the lowest impact. 1. Create Russian translation files with only the correct header and the pluralities translation items. 2. Create a new version named as russian-fix 3. Upload the source files and the Russian translation files created in #1 to the version russian-fix 4. Merge the stable version with version russian-fix 5. Rename stable version to stable-old, and rename russian-fix to stable. You could verify if the issues are fixed in russian-fix ? https://translate.openstack.org/iteration/view/horizon/russian-fix Best regards Ying Chun Guo (Daisy) Douglas Fish/Rochester/IBM wrote on 09/24/2015 02:41:16 AM: > From: Douglas Fish/Rochester/IBM@IBMUS > To: Ying Chun Guo/China/IBM@IBMCN > Cc: ilyaalekseyev(a)acm.org, openstack-i18n(a)lists.openstack.org > Date: 09/24/2015 02:41 AM > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > I don't think these kinds of structural edits are available through > the Zanata UI (I'm not expert and welcome any correction) > > I don't have a script to automatically do the updates but I did > outline my plan in the bug description. To repeat here: > cd openstack_dashboard/locale/ru/LC_MESSAGES > cp django.po django.po-tmp > grep -v msgstr.2. django.po-tmp > django.po > sed -i s/msgstr.3./msgstr[2]/ django.po > and edit the plurality function to be > "Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n" > "%10<=4 && (n%100<12 || n%100>14) ? 1 : 2);\n" > was my plan to fix the openstack_dashboard ... django.po file. This > is the only one that results in bad behavior in Horizon today. > > However, since this is such a difficult process I think we should > update all 4 Russian PO file while we are doing this: > openstack_dashboard/horizon and django.po/djangojs.po for each part. > > Daisy - I'm happy to help work through this, including testing out > our proposed files in Horizon. Do you want to schedule a time and > coordinate this through openstack-i18n or some meeting IRC channel? > > Doug > > ----- Original message ----- > From: Ying Chun Guo/China/IBM > To: Douglas Fish/Rochester/IBM@IBMUS@IBMAU > Cc: ilyaalekseyev(a)acm.org, openstack-i18n(a)lists.openstack.org > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > Date: Wed, Sep 23, 2015 11:25 AM > > Thank you for looking into it, Illya. > I think we need to fix it, although the manually process might be a > little complex. > > I'm going to: > 1. Create a new version in Zanata > 2. Mark master as read only > 2. Pull the source files and the translation files. > 3. Change the pluralities settings in Russian translation files. > 4. Upload the source files and translation files to the new version. > 5. Check if the all things are right, change master version name to > "master-old", > and then change the new version name to "master" > > How do you want to update these pluralities then? By program ? Or manually ? > Is it possible to make the changes through Zanata UI, other than > uploading po files ? > > Best regards > Ying Chun Guo (Daisy) > > > Douglas Fish/Rochester/IBM wrote on 09/23/2015 04:38:19 AM: > > > From: Douglas Fish/Rochester/IBM@IBMUS > > To: ilyaalekseyev(a)acm.org > > Cc: guoyingc(a)cn.ibm.com, openstack-i18n(a)lists.openstack.org > > Date: 09/23/2015 04:38 AM > > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > > > Hi Ilya, > > > > Thanks for looking at this! Unfortunately having 4 pluralities > > confuses Horizon. I've tested out stripping one of the pluralities > > and restoring the expected Plural-forms definition (just like the > > one you linked) and it works great. > > > > I had hoped to just repair the PO files in this way and upload the > > corrected translations to Zanata. > > > > Unfortunately, I understand from Daisy's research that once a > > language/project has been created in Zanata in this way we cannot > > just upload a PO file with corrected pluralities . More > > investigation will be needed to understand the process to fix this. > > > > Doug > > > > > > ----- Original message ----- > > From: Ilya Alekseyev <ilyaalekseyev(a)acm.org> > > Sent by: ilya(a)phpcoder.ru > > To: Douglas Fish/Rochester/IBM@IBMUS > > Cc: Ying Chun Guo <guoyingc(a)cn.ibm.com>, "openstack- > > i18n(a)lists.openstack.org" <openstack-i18n(a)lists.openstack.org> > > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > Date: Tue, Sep 22, 2015 2:39 PM > > > > Hi Doug and Daisy! > > > > Looks like we have wrong pluralities in current release: > > in https://github.com/openstack/horizon/blob/master/ > > openstack_dashboard/locale/ru/LC_MESSAGES/django.po > > > > we have: > > "Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n" > > "%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n% > 10<=9) || (n" > > "%100>=11 && n%100<=14)? 2 : 3);\n" > > > > but in previuos releses we have: > > "Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n% > > 10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" > > > > Last one is right for Russian. > > > > We can make translation in Zanata for 4 pluralities, but it can give > > in some cases bugs with wrong plural forms. > > > > Kind regards, > > Ilya Alekseyev. > > > > 2015-09-22 14:22 GMT+03:00 Douglas Fish <drfish(a)us.ibm.com>: > > Hi Daisy, > > > > I am certain this issue is caused by plural forms. The issue with > > missing menus is seen with the current 4 plural form translations; > > when I correct the PO file to have 3 forms Horizon properly > displaysthe menus. > > > > Doug > > > > > > ----- Original message ----- > > From: Ying Chun Guo/China/IBM > > To: Douglas Fish/Rochester/IBM@IBMUS@IBMAU > > Cc: openstack-i18n(a)lists.openstack.org > > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > Date: Tue, Sep 22, 2015 12:49 AM > > > > Hi, Doug > > > > We need to consider it carefully. > > > > After working with Zanata dev team, I got to understand: > > > > 1. Zanata has its own plural forms. If po file has its own plural > > form, Zanata will use that. > > Otherwise, Zanata will use its own plural form. Pluralforms in Zanata: > > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && > > (n%100<10 || n%100>=20) ? 1 : 2). > > So it looks like that OpenStack po files overrode the pluralforms in Zanata. > > > > 2. Zanata currently don't allow update of plural forms once the > > document has been uploaded to Zanata. > > Even with deletion of that source document and re-upload (in the > > same project-version, same doc name and same path), > > Zanata will still reuse the old pluralform. > > > > 3. If we want to update the pluralforms, we will need to do it in > > new project-version > > (don't use copy-from previous version function). > > > > I think we need to carefully design the steps to change pluralforms > > of Russian. > > At first, I want to confirm with you, are you sure this issue is > > caused by plural forms? > > > > Best regards > > Ying Chun Guo (Daisy) > > > > > > Douglas Fish/Rochester/IBM wrote on 2015/09/18 23:38:22: > > > > > From: Douglas Fish/Rochester/IBM@IBMUS > > > To: guoyingc(a)cn.ibm.com > > > Cc: openstack-i18n(a)lists.openstack.org > > > Date: 2015/09/18 23:38 > > > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > > > > > Hi Daisy, > > > > > > Yes, I understand - I don't think I can even propose my branch > > > unless I am added as a translator by the Russian team. > > > > > > My proposal would include removing one plural form for > > > 4 messages in horizon django.po > > > 1 message in horizon djangojs.po > > > 144 messages in openstack_dashboard django.po > > > 0 messages in openstack_dashboard djangojs.po > > > plus the pluralization specification would be updated in all 4 files. > > > > > > Doug > > > > > > ----- Original message ----- > > > From: Ying Chun Guo <guoyingc(a)cn.ibm.com> > > > To: Douglas Fish/Rochester/IBM@IBMUS > > > Cc: openstack-i18n(a)lists.openstack.org > > > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > > Date: Fri, Sep 18, 2015 3:25 AM > > > > > > Are there a lot of changes in your proposed po files ? > > > I'm still waiting for Russian team's response. > > > > > > Best regards > > > Ying Chun Guo (Daisy) > > > > > > > > > "Douglas Fish" <drfish(a)us.ibm.com> wrote on 09/18/2015 05:37:07 AM: > > > > > > > From: "Douglas Fish" <drfish(a)us.ibm.com> > > > > To: openstack-i18n(a)lists.openstack.org > > > > Date: 09/18/2015 05:38 AM > > > > Subject: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > > > > > > > Hi translation friends, > > > > > > > > I'd like to contribute 4 PO files for the Horizon Russian > > > > translation to correct the issue > > > > https://bugs.launchpad.net/openstack-i18n/+bug/1494819 > > > > > > > > These uploads won't contain any new translations, but instead will > > > > be an adjustment to the PO files so they have 3 pluralities, which > > > is standard > > > > http://localization-guide.readthedocs.org/en/latest/l10n/ > pluralforms.html > > > > > > > > Specifically, I plan to remove the msgstr[2] translation from the > > > > files (because msgstr[2] is blank for many cases), rename the msgstr > > > > [3] translation to msgstr[2] and adjust the plurality specification to > > > > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && > > > > (n%100<10 || n%100>=20) ? 1 : 2); > > > > > > > > As discussed in the team meeting http://eavesdrop.openstack.org/ > > > > meetings/openstack_i18n_meeting/2015/openstack_i18n_meeting. > > > > 2015-09-17-13.00.log.html > > > > please create a Zanata branch so I can propose these corrections > > for review. > > > > > > > > Thanks! > > > > > > > > Doug > > > > _______________________________________________ > > > > 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 3

IRC meeting tomorrow
by Ying Chun Guo 30 Sep '15

30 Sep '15

Hello,team We will have the IRC meeting at UTC 0600 in the channel #openstack-meeting on October 1st. We could talk about the ongoing liberty translations: progress, importing, issues, and etc. If you have other topics, feel free to propose. Best regards Ying Chun Guo (Daisy)

1 0

Handling of translations for Liberty
by Andreas Jaeger 29 Sep '15

29 Sep '15

We had some IRC discussion today about how to handle the "other" projects with importing and here's a proposal based on discussions with Clark, Lyz, Steve, Daisy and Thierry. I'd like to prepare everything for this tomorrow if possible, so please speak up if you have questions or concerns, Andreas Challenge: We have translations for some projects like keystone that are not on the liberty branch. Master is already open for Mitaka. Proposal: Handle all projects that have currently translations of main files (so, not only LOG files) and liberty branches the same - like we do with horizon and nova. Details: This means, the following projects will get liberty branches: List of projects that branch with translations: openstack/ceilometer openstack/cinder openstack/designate openstack/designate-dashboard openstack/django_openstack_auth openstack/glance openstack/horizon openstack/keystone openstack/neutron openstack/nova openstack/swift openstack/zaqar List of projects branching later: openstack/openstack-manuals - to translate Install Guide The following projects will not be translated: List of projects that branch without translations in git : openstack/aodh openstack/ironic-inspector openstack/magnum openstack/magnum-ui openstack/manila openstack/sahara openstack/searchlight List of projects that branch with only LOG translations in git: openstack/barbican openstack/glance_store openstack/heat openstack/ironic openstack/trove List of projects not branching: openstack/api-site openstack/ha-guide openstack/operations-guide openstack/oslo.cache openstack/oslo.concurrency openstack/oslo.db openstack/oslo.i18n openstack/oslo.log openstack/oslo.messaging openstack/oslo.middleware openstack/oslo.policy openstack/oslo.reports openstack/oslo.service openstack/oslo.utils openstack/oslo.versionedobjects openstack/oslo.vmware openstack/python-magnumclient openstack/python-openstackclient openstack/security-doc Process 1. Before RC1 is cut, translators work with master version. 2. When stable branch is cut, branches get created in Zanata as well. Syncing will get enabled for them. 3. Translators focus on translation of stable branch. 4. Once translators are finished with translations, a copy of new translations from stable branch to master is done in Zanata . 5. Open master version to accept translations. Note: Around RC1 time, a patch to cleanup "old" translations gets proposed to both stable and master to remove any translations in git that are less than 50 % translated (we normally only delete less than 20 % to avoid to frequent deletion). What do we want to see in Liberty release: * Updated translations of files that are sufficiently translate (> 75 %) * Updated po source file that reflect state of repository * No empty/mainly untranslated language files (< 50 %) 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

4 13

dashboard trans checksite
by KATO Tomoyuki 25 Sep '15

25 Sep '15

Hi team, A.I. from last IRC meeting. I updated translation check site spec. Any comments are welcome. https://review.openstack.org/#/c/184559/ Thanks, KATO Tomoyuki

2 2

horizon, django_openstack_auth and other stable/liberty created
by Andreas Jaeger 25 Sep '15

25 Sep '15

Hi, translation team, horizon, django_openstack_auth, and other projects as mentioned in my email have now stable/liberty branches created [1]. Daisy and myself have created the corresponding version for liberty in Zanata. The version name is stable-liberty. So from now on, all translations/review should be made in the stable-liberty version. The master version of horizon and django_openstack_auth is now set "Read Only" and will be open to accept translations after Liberty is done. Andreas [1] Horizon is currently get prepared for branch, the git repo is not yet updated but our version will be the branch point -- 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

1 2

Re: [Openstack-i18n] [openstack-dev] [nova][i18n] Is there any point in using _() inpython-novaclient?
by Matt Riedemann 25 Sep '15

25 Sep '15

On 9/6/2015 12:18 AM, Steve Martinelli wrote: > Isn't this just a matter of setting up novaclient for translation? IIRC > using _() is harmless if there's no translation bits set up for the project. > > Thanks, > > Steve Martinelli > OpenStack Keystone Core > > Inactive hide details for Matt Riedemann ---2015/09/04 01:50:54 PM---I > noticed this today: https://review.openstack.org/#/c/219Matt Riedemann > ---2015/09/04 01:50:54 PM---I noticed this today: > https://review.openstack.org/#/c/219768/ > > From: Matt Riedemann <mriedem(a)linux.vnet.ibm.com> > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev(a)lists.openstack.org>, openstack-i18n(a)lists.openstack.org > Date: 2015/09/04 01:50 PM > Subject: [openstack-dev] [nova][i18n] Is there any point in using _() in > python-novaclient? > > ------------------------------------------------------------------------ > > > > I noticed this today: > > https://review.openstack.org/#/c/219768/ > > And it got me thinking about something I've wondered before - why do we > even use _() in python-novaclient? It doesn't have any .po files for > babel message translation, it has no babel config, there is nothing in > setup.cfg about extracting messages and compiling them into .mo's, there > is nothing on Transifex for python-novaclient, etc. > > Is there a way to change your locale and get translated output in nova > CLIs? I didn't find anything in docs from a quick google search. > > Comparing to python-openstackclient, that does have a babel config and > some locale po files in tree, at least for de and zh_TW. > > So if this doesn't work in python-novaclient, do we need any of the i18n > code in there? It doesn't really hurt, but it seems pointless to push > changes for it or try to keep user-facing messages in mind in the code. > > -- > > Thanks, > > Matt Riedemann > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > Yeah, doffm is working on enabling i18n for python-novaclient via bug: https://bugs.launchpad.net/python-novaclient/+bug/1492444 -- Thanks, Matt Riedemann

5 6

Re: [Openstack-i18n] translating python clients
by Ying Chun Guo 24 Sep '15

24 Sep '15

Ying Chun Guo/China/IBM wrote on 2015/09/25 10:17:52: > From: Ying Chun Guo/China/IBM > To: Andreas Jaeger <aj(a)suse.com> > Cc: Matt Riedemann <mriedem(a)linux.vnet.ibm.com>, openstack- > i18n(a)lists.openstack.org > Date: 2015/09/25 10:17 > Subject: Re: [Openstack-i18n] translating python clients > > Andreas Jaeger <aj(a)suse.com> wrote on 2015/09/23 15:06:56: > > > From: Andreas Jaeger <aj(a)suse.com> > > To: Matt Riedemann <mriedem(a)linux.vnet.ibm.com>, Ying Chun Guo/ > China/IBM@IBMCN > > Cc: openstack-i18n(a)lists.openstack.org > > Date: 2015/09/23 15:07 > > Subject: Re: [Openstack-i18n] translating python clients > > > > On 2015-09-22 22:53, Matt Riedemann wrote: > > > > > > > > > On 9/21/2015 10:49 AM, Ying Chun Guo wrote: > > >> Andreas Jaeger <aj(a)suse.com> wrote on 09/21/2015 10:27:29 PM: > > >> > > >> > From: Andreas Jaeger <aj(a)suse.com> > > >> > To: Matt Riedemann <mriedem(a)linux.vnet.ibm.com>, openstack- > > >> > i18n(a)lists.openstack.org > > >> > Date: 09/21/2015 10:28 PM > > >> > Subject: Re: [Openstack-i18n] translating python clients > > >> > > > >> > On 2015-09-21 16:09, Matt Riedemann wrote: > > >> > > > > >> > > > > >> > > On 9/18/2015 10:54 AM, Akihiro Motoki wrote: > > >> > >> I have no comment on Liberty translation priority atm. > > >> > >> > > >> > >> I think a couple of different topics are discussed at the same > > >> here. > > >> > >> > > >> > >> * CLI translation priority > > >> > >> * Server side project translation priority > > >> > >> * (potential) usage of server side project translations in Horizon > > >> > >> > > >> > >> We need to have more contact with project teams in the next cycle > > >> > >> more deeply to decide translation priorties before starting > > >> translations. > > >> > >> In the past releases, i18n team tended to start discussions after > > >> > >> starting > > >> > >> translations and it is too late for the game in most cases. > > >> > >> > > >> > >> Regarding client projects, I know openstackclient is our future and > > >> > >> the keystone team encourage to use openstackclient for Keystone v3 > > >> API. > > >> > >> However, regarding other projects like nova or neutron, > > >> > >> the progress of openstackclient integration is not well enojgh > > >> > >> and a new feature is implemented in each client. > > >> > >> Thus we need to consider the priority in the next cycle. > > >> > > > > >> > > I agree with this. We are nowhere near, as far as I can tell > > >> anyway, of > > >> > > deprecating python-novaclient. The reason we pushed the changes to > > >> > > translate the project is because people are pushing changes into > > >> > > python-novaclient to mark strings for translation, but there was > > >> never > > >> > > any infrastructure in place to do those translations (the project > > >> wasn't > > >> > > even configured with babel until a couple of weeks ago). > > >> > > > > >> > > So the feeling was, why not translate it? It's easy to setup. I > > >> agree > > >> > > that python-openstackclient is higher priority for the CLI, but > > >> > > python-novaclient is not going away anytime soon, especially now > > >> that we > > >> > > have microversion support in it for the compute API, which I don't > > >> think > > >> > > python-openstackclient has. > > >> > > > >> > But just the setup will not give you translations for free. Even if we > > >> > set it up, I fear no one will translate it. Therefore I wonder whether > > >> > it makes sense at all to enable the infrastructure if no translator > > >> > looks at it. > > >> > > > >> > Or in other words: Does the translation team want to have every > > >> possible > > >> > project in Zanata? Or only those they want to translate? And then the > > >> > question is which ones to translate? > > >> > > >> In my mind, translation platform should not block any people who want to > > >> translate > > >> any resources if the resources are available in Openstack community. > > >> So if dev team want to put their resources, put them there. > > > > > > This is my thinking as well. If the infrastructure is not in place, > > > people are definitely not going to translate it. I understand that > > > people might not translate it anyway, but I don't see the harm in having > > > it available for translation if someone wants that. And as pointed out > > > somewhere else on this topic, python-openstackclient and Horizon both > > > use python-novaclient, so unless those are completely handling all > > > errors that come out of novaclient, we should probably have novaclient > > > available for translations - at least of errors. > > > > > >> Andreas is right, putting projects in Zanata will not bring free > > >> translations. > > >> Based on my observation, translators prefer to translate UI projects > > >> more than other projects. > > >> For example, even I include Nova in the Liberty translation plan, the > > >> nova translation progress > > >> is not that good. > > >> In translation community, translation team, coordinators and even > > >> individual translators > > >> have the autonomy. > > > > So, policy sounds like: > > > > A project that wants translations - and is part of the big tent - can > > set it up. The i18n PTL suggests a priority and ask for translation of > > specific projects but translators are not limited on what to translate. > > > > Correct? > > > > Yes. > > > So, do you want to enable python-keystoneclient, python-novaclient, and > > python-neutronclient? Or only the later two since keystoneclient is > > deprecated and even throws warnings when used: > > > > Pending deprecation: Command-line interface to the OpenStack Identity API. > > This CLI is pending deprecation in favor of python-openstackclient. For a > > Python library, continue using python-keystoneclient. > > > > keystoneclient is only used for Python binding and the CLI in is deprecated. > So if there is no objections from keystone dev team, we could remove > keystoneclient. > Please enable openstack-novaclient because we get the request that > it needs translation. > I don't see neutronclient is deprecating. So please enable it too. > Thank you. > Just got inputs from keystone dev team. They said "openstackclient still receives strings from keystoneclient, (it uses keystoneclient to perform the requests) also, keystoneclient can be used by customer applications so they might want translated strings." So let's include python-keystoneclient in the translation projects. > > 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 1