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

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

18 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