- OpenStack-I18n - lists.openstack.org

[I18n] Translation platform may be unstable or down during 2/27 - 3/3 due to upgrade
by Ian Y. Choi 02 Mar '17

02 Mar '17

Hello all, As I shared I18n summary in my previous e-mail [1], there will be a major OpenStack translation platform upgrade during Feb 27 to Mar 3. It implies that: - Translation platform (https://translate.openstack.org) might be unstable or might not work for some time slots during the upgrade period. - “Imported Translation from Zanata” patch proposals [2] might not work. - Translation sync jobs [3, 4] may fail during some period. Infrastructure team kindly agreed to help a lot for the translation platform upgrade (I truly appreciate it!), and I18n team & Zanata [5] development team will have high attention on upgrade and changes. Note that the current Zanata version is 3.7.3, and the target upgrade version is 3.9.6. With many thanks, /Ian [1] http://lists.openstack.org/pipermail/openstack-dev/2017-February/112889.html [2] https://review.openstack.org/#/q/owner:%22OpenStack+Proposal+Bot%22+%22Impo… [3] http://status.openstack.org/openstack-health/#/g/build_queue/post?groupKey=… [4] http://status.openstack.org/openstack-health/#/g/build_queue/periodic?group… [5] http://zanata.org

4 5

[i18n] Translation for logs in keystone removed
by Alfredo Moralejo Alonso 01 Mar '17

01 Mar '17

Hi openstack-i18n, I've observed that all *-log-*.po files have been removed from keystone project in https://review.openstack.org/#/c/437811/ . This is making compile_catalog command to fail as it expects those files to exist in [1]. Is this expected?, will translation for all log files be removed from projects?, if so changes in setup.cfg should be coordinated when needed. Best regards, Alfredo [1] https://github.com/openstack/keystone/blob/master/setup.cfg#L54

3 4

Temporary glossary deletion
by Kato, Tomoyuki 26 Feb '17

26 Feb '17

Hi I18n team, As preparation for Zanata upgrade, I will remove the glossaries temporarily. The new Zanata has the feature, language specific glossary, but it cannot migrate the current glossary into the new one. However, I will upload the glossaries again just after upgrade. Sorry for your inconvenience. KATO Tomoyuki

3 2

Re: [OpenStack-I18n] [OpenStack-docs] FW: Team photo reminder :)
by Edgar Magana 24 Feb '17

24 Feb '17

A good looking team! I hate that I missed the PTG! Edgar From: Alexandra Settle <a.settle(a)outlook.com> Date: Wednesday, February 22, 2017 at 11:30 AM To: "openstack-docs(a)lists.openstack.org" <openstack-docs(a)lists.openstack.org>, "openstack-i18n(a)lists.openstack.org" <openstack-i18n(a)lists.openstack.org> Subject: [OpenStack-docs] FW: Team photo reminder :) Hi everyone! Attached are our team’s (docs and i18n) photos from the PTG :) Thanks, Alex From: Kendall Nelson <kennelson11(a)gmail.com> Date: Tuesday, February 21, 2017 at 4:07 PM To: "a.settle(a)outlook.com" <a.settle(a)outlook.com> Subject: Re: Team photo reminder :) Here are the photos! On Tue, Feb 21, 2017 at 9:24 AM Kendall Nelson <kennelson11(a)gmail.com<mailto:kennelson11@gmail.com>> wrote: 10:30 outside Grand ballroom A 3rd floor! -Kendall Nelson

5 4

[I18n] Pike PTG Summary
by Ian Y. Choi 24 Feb '17

24 Feb '17

Hello all, I18n team participated in PTG for horizontal discussions with the tight collaboration of Documentation team on Monday and Tuesday. Also, there were a few collaboration sessions with Infrastructure, Horizon, Release Management, and OpenStackAnsible team on Wednesday & Thursday in a reservable room. The following is the summary of what I18n team discussed with other project teams. More details for I18n issues are available at: https://etherpad.openstack.org/p/i18n-ptg-pike-topics 1. Documentation / I18n (Monday & Tuesday) The details of all discussions with Docs & I18n teams are written in: https://etherpad.openstack.org/p/docs-i18n-ptg-pike , and I would like to summarize mainly I18n issues (For Documentation topic summary, please see [1]). - For Horizon strings, Documentation team & I18n team identified : Documentation team wants to implement automated screenshot functionality for user-guide. Then, stable DevStack instance would be fine with adding the functionality. : On the other hand, I18n team wants to implement translation checksite which requires re-import of translated strings to review translated strings after around Soft & Hard StringFreezes. - Agreed that archiving & versioning [2] translated documents are also the target with consideration. - Defined url policy for translated project specific install guides : https://docs.openstack.org/<deliverable>/<projectname>/<lang>/ (e.g., https://docs.openstack.org/project-install-guide/baremetal/ja/newton/ ) - I18n team will implement to generate translated PDF documents after pdf implementation spec [3] is successfully landed. - I18n team discussed the approach for implementing translation checksite, I18n contributor guide translation, considering different release models, and solving Stackalytics integration issues. 2. Infrastructure + I18n (Wednesday) + OpenStackAnsible + Horizon (Thursday) - Translation platform ( https://translate.openstack.org ) is now ready for upgrade. - There will be upgrade during 2/27 - 3/3. Translation platform might not work due to upgrade progress. - openstackid-dev developer will test authentication with Zanata using https://translate-dev.o.o from next week - I18n team will automate to propose ATC status rather than current manual proposal work as extra-ATCs using upgraded translation platform. - Implementing translation checksite with OpenStackAnsible will be a feasible solution in OpenStack Infrastructure. I18n team will start to implement translation checksite using OpenStackAnsible from Pike cycle (spec [4] needs to be changed). - Discussed how to Improve algorithms to match Zanata ID with Launchpad & Gerrit ID in Stackalytics 3. Horizon I18n collaboration session w/ Release Management team - Shared current status of I18n team’s translation priority : I18n team sets the highest priority during Soft & Hard StringFreezes to include more qualified translated strings as much as possible for Horizon & Horizon plugin projects. - I18n team shared Ocata cycle experience: cycle-with-milestone, cycle-with-intermediary, and cycle-trailing release models for Horizon plugin projects are not matched with Soft & Hard StringFreeze periods. - Discussed & drawn a new proposal to consider translations for Horizon plugin projects : I18n team will consider Soft & Hard StringFreeze for the projects which follow cycle-with-milestone release model. : I18n team will also consider translation with releases for the projects which follow cycle-with-intermediary release model if they are fine following deadlines. : I18n team will propose a specification to tag (e.g., with “translate”) for projects which are the target of translations with managing stable branches in translation platform. : For cycle-trailing release models, I18n will consider translations with managing stable versions in translation platform if there is I18n cross-project liaison [5] for the project. : I18n team will higher priority for projects which have I18n cross-project liaison. - I18n team will ask to Zanata development team to automate to create new stable versions in Zanata, copying master translations over. I great appreciate all the help and support from especially Alex - Pike Docs PTL to help successfully land collaboration room with I18n team, and also many project team contributors to participate in the discussion and draw nice, and cool approach for better internationalization. With many thanks, /Ian [1] http://lists.openstack.org/pipermail/openstack-dev/2017-February/112885.html [2] http://specs.openstack.org/openstack/docs-specs/specs/pike/archiving.html [3] http://specs.openstack.org/openstack/docs-specs/specs/ocata/build-pdf-from-… [4] http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_ch… [5] https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n

1 0

[openstack-docs] [dev] What's up, Doc?
by Alexandra Settle 24 Feb '17

24 Feb '17

Team team team team team, Welcome to my second edition of What's up, Doc! We have had an extremely busy week in Atlanta for the PTG. We had a really enthusiastic attendance and I am truly impressed by how much we have managed to get done. This newsletter will be a short one and focus on a small PTG update! Our bug triager for the first 2 weeks of Pike is Darren Chan. Looking for more people to sign up and help out: https://wiki.openstack.org/wiki/Documentation/SpecialityTeams#Bug_Triage_Te… == Progress towards Pike == Thanks to our amazing release managers, Maria, Brian and Lana for all their amazing hard work on the Ocata release. Big thanks to Anne for stepping in at the last minute! * 44 days to go! https://www.timeanddate.com/countdown/newyear?p0=24&msg=Pike+release&ud=1&f… == The Road to the Summit in Boston == Voting is now open for topics. You can find the list of topics here: https://www.openstack.org/summit/boston-2017/vote-for-speakers#/ I was able to find some documentation related topics. If anyone has any more topics I am unaware of, please reply to this email thread and share your talks! Please vote for your fellow documenter below: 1. https://www.openstack.org/summit/boston-2017/vote-for-speakers#/17888 2. https://www.openstack.org/summit/boston-2017/vote-for-speakers#/18078 3. https://www.openstack.org/summit/boston-2017/vote-for-speakers#/17711 Event info is available here: http://www.openstack.org/ptg Purchase tickets here: https://pikeptg.eventbrite.com/ Tickets for the Boston summit: https://www.openstack.org/summit/boston-2017/ == PTG Update == We had a very successful PTG! Thanks to all those that were able to attend. Thanks to Ian Choi and the I18n team for being wonderful collaborators. We were able to get a lot done in our horizontal sessions. For anyone that is interested, here's our etherpad with all the notes from the sessions: https://etherpad.openstack.org/p/docs-i18n-ptg-pike Here are a few of the exciting things to look out for in Pike: 1. High Availability Guide improvements a. Adam Spiers and Ianeta Hutchinson will be leading the charge on the HA guide with a massive restructure and up-to-date new content. 2. Reno release notes for OpenStack manuals a. Adam Spiers has been working alongside John Davidge and the Infra team to work on implementing the reno release notes process for documentation. Including looking at implementing new reno templates to work specifically for documentation! 3. Networking Guide improvements and more collaboration with the neutron team. a. John Davidge has been working with the neutron team to develop the best way to ensure information flows into the guide. Discussions around the use of the DocImpact tag were successful. 4. Administrator Guide changes! Keep your eye out for exciting developments. a. Ildiko Vancsa and Joseph Robinson will be working together to come up with a new specification to implement in Queens for our Administration Guide. Development teams have been enthusiastic about implementing the project-install-guide and are looking for similar structures with the Admin Guide. Stay tuned for more news here! I had the opportunity to report back to meeting attendees yesterday afternoon, if anyone would like to know more, here are the meeting minutes: http://eavesdrop.openstack.org/meetings/docteam/2017/docteam.2017-02-23-20.… == Doc team meeting == Our next meeting will be on Thursday 9 March at 2100 UTC in #openstack-meeting-alt. Meeting chair will be me (Alexandra Settle - asettle)! \o/ For more meeting details, including minutes and the agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting -- Have a great weekend! Alex Lamp enthusiast and award winning marathon sleeper IRC: asettle Twitter: dewsday

2 2

Fwd: Greek language team.
by Ian Y. Choi 22 Feb '17

22 Feb '17

Oops.. I have forgot including with our important mailing list as a recipient. FYI With many thanks, /Ian ---------- Forwarded message ---------- From: Ian Y. Choi <ianyrchoi(a)gmail.com> Date: Wed, Feb 22, 2017 at 2:50 PM Subject: Re: [OpenStack-I18n] Greek language team. To: Dimosthenis Trichakis <dtrich0(a)gmail.com> Hello, I am attending now PTG and my response would be slow. But, I have just found that Greek team is already in Zanata and I have added your Zanata into Greek Language team. Currently, Efstathios Iosifidis is Greek language coordinator but unfortunately I have not discussed with the guy at least for one year. It would be great if you also discuss Greek translation with Efstathios and I welcome you to come to I18n IRC meeting to discuss more translation-side things if you would like to ask or discuss : https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting By the way, which projects are you interested in translations? (e.g., Horizon, Install-guide, and so on) With many thanks, /Ian On Wed, Feb 22, 2017 at 6:21 AM, Dimosthenis Trichakis <dtrich0(a)gmail.com> wrote: > Hi there, > > I'm a telecom engineer and I would like to learn about cloud technologies. > I'm a linux user for more than a decade and I like to contribute as much as > I can. From my point of view a good way to contribute and at the same time > to learn is translating projects. > I would like to request the creation of Greek Language team. > My user name in Zanata platform is dtrich0 and my Openstack member ID is > 83507. > > Regards, > > Dimosthenis Trichakis > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > >

1 0

glossary, translation changes order
by Robert Simai 22 Feb '17

22 Feb '17

Hi, while working in the "openstack-manuals master Documents (de) doc/common/source/locale/common" tree in Zanata I noticed, by translating the technical terms we're apparently changing the order. As an example, the term "Image" in German becomes "Abbild" and while it originally was under "I", now it should be under "A". But as far as I understand it won't since the order is given in the file "doc/common/ glossary.rst" which is the source of these strings. Am I right, and is this what happens? Or is there some "intelligence" that assembles the final documentation in the correct (alphabetical) order? -- Thanks, Robert

2 1

FW: Team photo reminder :)
by Alexandra Settle 22 Feb '17

22 Feb '17

Hi everyone! Attached are our team’s (docs and i18n) photos from the PTG :) Thanks, Alex From: Kendall Nelson <kennelson11(a)gmail.com> Date: Tuesday, February 21, 2017 at 4:07 PM To: "a.settle(a)outlook.com" <a.settle(a)outlook.com> Subject: Re: Team photo reminder :) Here are the photos! On Tue, Feb 21, 2017 at 9:24 AM Kendall Nelson <kennelson11(a)gmail.com<mailto:kennelson11@gmail.com>> wrote: 10:30 outside Grand ballroom A 3rd floor! -Kendall Nelson

1 0

Greek language team.
by Dimosthenis Trichakis 22 Feb '17

22 Feb '17

Hi there, I'm a telecom engineer and I would like to learn about cloud technologies. I'm a linux user for more than a decade and I like to contribute as much as I can. From my point of view a good way to contribute and at the same time to learn is translating projects. I would like to request the creation of Greek Language team. My user name in Zanata platform is dtrich0 and my Openstack member ID is 83507. Regards, Dimosthenis Trichakis

1 0