- OpenStack-I18n - lists.openstack.org

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

22 Mar '16

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

1 0

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

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

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

18 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