April 2017 - OpenStack-I18n - lists.openstack.org

More planning for Boston Summit for I18n - are you attending?
by Ian Y. Choi 25 Apr '17

25 Apr '17

Hello, It is the time to more concisely plan Boston Summit with I18n :) I have create an Etherpad : https://etherpad.openstack.org/p/i18n-boston-summit-activities Please put your name if you will attend to Boston Summit with available dates. Moreover, if you are unable to attend but want to discuss via IRC, please also mention your name with available time. There are many I18n sessions during Boston Summit - once every Summit day! (although Wednesday Hands on Workshop needs to be more planned with details) For meetup, I would like decide best time slot considering number of attendees from I18n. With many thanks, /Ian

1 0

Survey for Zanata platform
by Alex Eng 25 Apr '17

25 Apr '17

Hi guys, As part of our plan to improve Zanata translation platform, it is important for us to constantly collect feedback from users to understand problems and needs. It would be appreciated if you guys can spent few minutes to complete the survey https://drive.google.com/open?id=1lcbmbJ1snljrd5t_ nRyGgDTH7SRWpp6PBKJaq7UiQkM PS. The survey will be closed on 6/MAY. <https://drive.google.com/open?id=1lcbmbJ1snljrd5t_nRyGgDTH7SRWpp6PBKJaq7UiQ…> Regards, -- ALEX ENG SENIOR SOFTWARE ENGINEER, TEam lead Red Hat Asia-Pacific Pty Ltd <https://www.redhat.com/> Level 1, 193 North Quay Brisbane 4000 aeng(a)redhat.com M: +61423353457 IM: aeng <https://red.ht/sig>

6 6

Fwd: [User-committee] Boston Forum Schedule
by Ian Y. Choi 11 Apr '17

11 Apr '17

Hello translators, I would like to happily forward one announcement: I18n feedback collection has been finally selected as one of Forum topics! More details are at http://forumtopics.openstack.org/cfp/details/116 , and the time slot is 11:15 - 11:55 AM on Tuesday (May 9th) according to Boston local time. Note that the brainstorming for I18n team Forum and Summit presentations & workshops are still on-going : https://etherpad.openstack.org/p/BOS-I18n-brainstorming . Please do not hesitate to share your idea on Etherpad, here (mailing list), IRC, or anything else. Your feedback is important and I appreciate all :) With many thanks, /Ian -------- Original Message -------- Subject: [User-committee] Boston Forum Schedule Date: Mon, 10 Apr 2017 17:35:46 +0800 From: Tom Fifield <tom(a)openstack.org> To: user-committee(a)lists.openstack.org <user-committee(a)lists.openstack.org> Hi everyone, Thank you for the many excellent topics submitted for our first Forum. We have updated the topic submission site with the status of each - please check yours. Please also find attached in PDF the proposed schedule for the Forum in Boston. Let us know if you see major issues with it. As Thierry said in design summits past; "It's difficult to make too many changes at this stage as they quickly cascade into breaking all sorts of constraints, but we may still be able to accommodate some." :) Eagle-eyed readers will see that there are a number of slots in gray (on Thursday afternoon). These are being deliberately kept aside for the usual few critical topics that come up in the next few weeks and also for the discoveries we make in the first 3 days of the summit. We'll soon publish the Forum sessions on the main schedule, using the title, abstracts and moderators you submitted, but look forward to your feedback in the mean-time! Thank you all very much for making our first Forum a success. Regards, Doug, Emilien, Melvin, Mike, Shamail & Tom Forum Scheduling Committee

2 1

[openstack-docs] [dev] What's up, doc?
by Alexandra Settle 08 Apr '17

08 Apr '17

Team, This week I have still been working on drafting a governance tag for our guides called "docs:follows-policy". I have been working with Doug Hellmann (dhellmann) in the last week to change to draft dramatically, so it would be good for doc people and doc liaisons to review. We are trying to make this a broader tag, so it can be applied for other guides too. To review: https://review.openstack.org/#/c/445536/ I am also in the process of documenting guidelines in our Contribution Guide - which would also benefit from doc reviews: https://review.openstack.org/#/c/453642/ Would like to call out and thank John Davidge for his awesome work with the Networking Guide and neutron-related patches. He's been providing valuable guidance, and reviews, and it has been greatly appreciated by myself and the team. Lana Brindley has done an awesome job for the last two weeks in keeping our bug list under control. We are down to an amazing 102 bugs in queue, and 82 bugs closed this cycle already! Next week, I will be looking after the bug triage liaison role! If you're sitting there thinking "bugs are for me, I really love triaging bugs!" well, you're in luck! We have one spot open for the rest of the cycle (14 Aug - 28 Aug): https://wiki.openstack.org/wiki/Documentation/SpecialityTeams#Bug_Triage_Te… == The Road to the Summit in Boston == Keep an eye out for the docs and I18n have a project onboarding room at the summit. Melvin Hillsman (mrhillsman) of the User Committee submitted a forum topic for the Ops Guide to get operator feedback. David Flanders from the Foundation has also proposed a forum topic for developer.openstack.org (which currently houses our API, SDK, and other dev stuff). We'll be discussing major changes to that and would like to see some feedback from people here. Any questions on that, shoot it my way. My main objective for this forum topic is to reduce our current technical debt that lives on this site. For more information on forum topics: https://wiki.openstack.org/wiki/Forum Schedule has been released: https://www.openstack.org/summit/boston-2017/summit-schedul == Specialty Team Reports == * API - Anne Gentle: API versioning in relation to release versioning is currently manually compiled for the 40-ish API services, so ideas on how to automate and surface that info welcomed. More info: http://lists.openstack.org/pipermail/openstack-dev/2017-March/114690.html * Configuration Reference and CLI Reference - Tomoyuki Kato: N/A * High Availability Guide - Ianeta Hutchinson: We are continuing to collaborate with OS DevOps team. See the tag ha-guide-draft for bugs opened to fill content for the new guide. * Hypervisor Tuning Guide - Blair Bethwaite: N/A * Installation guides - Lana Brindley: We have now branched, so please remember to backport if you have edits to the Ocata guide now. Big thanks to all the testers who have been working hard over the past month or two (that Nova cells bug was *tough*!), and to Brian and Mariia for doing the heavy lifting. Noticed a bunch links to draft versions of the guide in Newton/Ocata branches, backports for that have been merged, and the Contributor Guide updated so we don't miss it in the future (https://docs.openstack.org/contributor guide/release/taskdetail.html#update-links-in-all-books). * Networking Guide - John Davidge: More patches landed in the last couple of weeks dealing with the move to OSC, and more are still in flight. Progress also continues on RFC 5737 compliance. Thanks to all contributors for their work. * Operations and Architecture Design guides - Darren Chan: Arch Guide: edited architecture considerations content and cleaned up the index page structure which was applied across OS manuals. Some ops-related content was moved to the Ops Guide. Our current focus is improving the storage design content and networking design content. * Training Guides - Matjaz Pancur: N/A * Training labs - Roger Luethi: We released the Ocata version of training-labs this week. * User guides - Joseph Robinson: For the user guides - the spec on migrating the Admin Guide content this week moved closer to merging. I started preparing the work items for action on the User Guides tasks wiki page. * Theme and Tools - Brian Moss: Anne has a spec up for theme consolidation, please check it out: https://review.openstack.org/#/c/454346/, Brian has fixed up the sitemap tool tests, reviews welcome: https://review.openstack.org/#/c/453976/. 41 open bugs, 13 closed in Pike == Doc team meeting == Our next meeting will be on Thursday, 20 April at 2100 UTC in #openstack-meeting-alt. For more meeting details, including minutes and the agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting The meeting chair will be me! Big thanks to Joseph for stepping up in the last 2 meetings and hosting in my absence! Really appreciated it :) -- Have a great weekend :) Alex IRC: asettle Twitter: dewsday

1 0

Babel 2.4 and ko_KR
by Andreas Jaeger 07 Apr '17

07 Apr '17

I see in: http://logs.openstack.org/8d/8d993d3bbd17ce22288b9ea9caa6d93618522f46/post/… "ValueError: expected only letters, got u'ko-kr'" Is there anybody that can investigate whether Babel is broken and needs blacklisting - or what else needs to change? This is using BAbel 2.4.0, Thanks for any help, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 7

[openstack-doc] Docs team meeting
by Alexandra Settle 06 Apr '17

06 Apr '17

Hey everyone, The docs meeting will continue today in #openstack-meeting-alt as scheduled (Thursday at 21:00 UTC). For more details, and the agenda, see the meeting page: - https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… The meeting with be hosted by Joseph Robinson, as I have some personal business to attend to this evening. Specialty team leads – if you are unable to attend the meeting, please send me your team reports to include in the doc newsletter. Thanks, Alex

1 0

[Bug 1536226] Re: Not all .po files compiled
by OpenStack Infra 05 Apr '17

05 Apr '17

Reviewed: https://review.openstack.org/319353 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=cf42abc85e385ea… Submitter: Jenkins Branch: master commit cf42abc85e385eac12123ccac63a7dd3eb4f83ce Author: Sven Anderson <sven(a)redhat.com> Date: Fri May 20 18:35:52 2016 +0200 Let setup.py compile_catalog process all language files Two years ago the translation files have been split into several files, separating the log messages of different log levels from each other, like X.pot, X-log-warning.pot, X-log-info.pot, and so on. However, the setup.py command `compile_catalogs`, that comes from the babel package and compiles the corresponding .po files into .mo files, only supported one file per python package. This means that during packaging `compile_catalogs` never compiled the X-log-*.po files, so the corresponding translations were always missing. Since babel 2.3 the domain can be set to a space separated list of domains. This change adds the the additional log level files to the domain list. Change-Id: I436072d03f401240df6d7b8348616bc7c4731c4a Closes-Bug: #1536226 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1536226 Title: Not all .po files compiled Status in Cinder: Fix Released Status in Glance: In Progress Status in heat: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in openstack i18n: New Bug description: python setup.py compile_catalog only compiles one <domain>.po file per language to a <domain>.mo file. By default <domain> is the project name, that is nova.po. This means all other nova-log-*.po files are never compiled. The only way to get setup.py compile the other files is calling it several times with different domains set, like for instance `python setup.py --domain nova-log-info` and so on. Since this is not usual, it can be assumed that the usual packages don't contain all the .mo files. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1536226/+subscriptions

1 0

request for help from ESL readers
by Brian Rosmaita 04 Apr '17

04 Apr '17

Hello i18n team, There's a section of Glance documentation that's written in a colloquial american english style, but some contributors have expressed concern that this attempt to make a concept clear to non-technical american english readers may actually make it more difficult for ESL readers to understand. It would be awesome if a few ESL people would take a look and let us know what you think: http://specs.openstack.org/openstack/glance-specs/specs/api/v2/sharing-imag… thanks, brian

3 3