- OpenStack-I18n - lists.openstack.org

技术因素 in OpenStack 架构设计指南 - 当前最新
by KATO Tomoyuki 15 Apr '16

15 Apr '16

Hi Chinese team, Please take a look at: https://bugs.launchpad.net/openstack-i18n/+bug/1571100 Kato

1 0

Renaming of resources
by Andreas Jaeger 12 Apr '16

12 Apr '16

I propose to change the setting of the locale source dir from "$module/locale" to "." for all projects to have this consistent. This will change the names of all resources since those are relative to the locale source dir. This will enable us to translate release notes using Zanata for the python projects. This is only relevant for python projects - not for documentation ones or for Django based projects since those already use "." as source directory. This implies a scripting change as well as a manual copying translation files around. I'm willing to do both later this week. My proposal would be to only do this for *master* but not for stable/mitaka, I don't want to risk anything on that branch. Everybody ok with this? Or has anybody concerns and suggestions? 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

4 6

Re: [OpenStack-I18n] Renaming of resources
by Andreas Jaeger 12 Apr '16

12 Apr '16

On 2016-04-12 12:03, Ying Chun Guo wrote: > Hi, Andreas > > Just release Horizon project have two pairs of resources with same name: > django and djangojs. And that will not change, they will stay the same. > Will they have both the same name and same location after changing ? Yes, as the new setup is exactly the setup that horizon has. > Is there a way to separate them from the web UI after changing? > See: > https://translate.openstack.org/iteration/view/horizon/master/documents I think that is clear, it gives name and path 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

Re: [OpenStack-I18n] Renaming of resources
by Andreas Jaeger 12 Apr '16

12 Apr '16

On 2016-04-12 11:08, Ying Chun Guo wrote: > Hi, Andreas > > Do you mean to move the *.pot files from "$module/locale" to the root > folder of module ( or the root folder of project ) ? Will you move > translation files in language folders ? Only the name in Zanata is changed, see "Translation script challenges" as well. The files will stay the same in the repositories. But the parameter we give zanata is different and thus the files in Zanata are renamed. > The purpose of this change is to support release notes translation, right > ? Yes. Also, it avoids problems like we had with keystone (see above referenced email for full details), Andreas > Best regards > Ying Chun Guo (Daisy) > > > Andreas Jaeger <aj(a)suse.com> wrote on 04/12/2016 02:56:34 PM: > >> From: Andreas Jaeger <aj(a)suse.com> >> To: "openstack-i18n(a)lists.openstack.org" > <openstack-i18n(a)lists.openstack.org> >> Date: 04/12/2016 02:58 PM >> Subject: [OpenStack-I18n] Renaming of resources >> >> I propose to change the setting of the locale source dir from >> "$module/locale" to "." for all projects to have this consistent. This >> will change the names of all resources since those are relative to the >> locale source dir. This will enable us to translate release notes using >> Zanata for the python projects. >> >> This is only relevant for python projects - not for documentation ones >> or for Django based projects since those already use "." as source >> directory. >> >> This implies a scripting change as well as a manual copying translation >> files around. I'm willing to do both later this week. >> >> My proposal would be to only do this for *master* but not for >> stable/mitaka, I don't want to risk anything on that branch. >> >> Everybody ok with this? Or has anybody concerns and suggestions? >> >> 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

3 2

Translation script challenges
by Andreas Jaeger 11 Apr '16

11 Apr '16

I think this is mainly of interest to KATO-san, Akihiro-san, Alex, and infra folks but wanted to send it here to have it recorded. This is about the scripting we use in project-config to push content to zanata. I just did two changes to fix problems I noticed with release notes translation and with python projects that use more than one module (keystone): https://review.openstack.org/303727 https://review.openstack.org/303722 But now I see have another problem: Since keystone went from one to two modules, the srcdir setting changed and thus it's not anymore keystone but keystone/locale/keystone as resource name. Compare: https://translate.openstack.org/iteration/view/keystone/master/documents https://translate.openstack.org/iteration/view/keystone/stable-mitaka/docum… The rename deleted the old content and created new files ;( We can fix this with downloading the translation of mitaka files and pushing them to master. But this will hit us every time a project moves from one to multiple modules. Now, checking releasenotes push for python projects: It still does not work due to the ../.. zanata-cli does not see files outside of the srcdir. For reference: We need to push nova/locale/nova.pot and releasenotes/locale/releasenotes.pot zanata.xml contains: <rules> <rule pattern="**/*.pot">{locale_with_underscore}/LC_MESSAGES/{filename}.po</rule> <rule pattern="../../releasenotes/source/locale/releasenotes.pot">../../releasenotes/source/locale/{locale_with_underscore}/LC_MESSAGES/releasenotes.po</rule> </rules> So, I'm proposing to set sourcedir and transdir *everywhere* to "." instead of "$module/locale" - like done for multiple modules: <rules> <rule pattern="**/*.pot">{path}/{locale_with_underscore}/LC_MESSAGES/{filename}.po</rule> <rule pattern="releasenotes/source/locale/releasenotes.pot">releasenotes/source/locale/{locale_with_underscore}/LC_MESSAGES/releasenotes.po</rule> </rules> Does anybody have a better idea on how to fix these two problems? Or a better way to write the rules above for this? Alex, is there a way to not lose the content when this change is done since it will rename the translation files? 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 5

RFC: Zanata enhancement
by Kato, Tomoyuki 11 Apr '16

11 Apr '16

Hi team, I'd like to collect Zanata enhancement requests. I believe Zanata enhancement improve your work effciency, as translator, coordinator, or infra engineer... Please feel free to write your requests. https://etherpad.openstack.org/p/I18n-Zanata-enhancement I have a chance to talk with Alex, Zanata dev team, at Austin Summit. Unfortunately, we don't have enough official session slot, but we will talk at somewhere. Also, everyone is welcome to join us. Exact date and location are to be determined. I'll email details around summit. Thanks, KATO Tomoyuki

1 0

Approval
by Remo Mattei 11 Apr '16

11 Apr '16

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

2 1

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

10 Apr '16

Could somebody closely review today's horizon translation import, please? I'm surprised by the deletions but couldn't find an error with them either: https://review.openstack.org/#/c/303807/ Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 4

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

10 Apr '16

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

2 1

IRC meeting tomorrow
by Ying Chun Guo 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