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

Re: [OpenStack-I18n] [openstack-dev] A Summary of Atlanta PTG Summaries (!)
by Ian Y. Choi 15 Mar '17

15 Mar '17

Hello Hugh, Just I have found that there is a typo: I18n team is "I18n", not "I8n" :) (There are total 18 characters between 'I' and 'n' in "Internationalization" - too long.) Could you fix it? With many thanks, /Ian Hugh Blemings wrote on 3/13/2017 6:30 PM: > Hi Emilien, All, > > On 8/3/17 09:26, Emilien Macchi wrote: >> On Mon, Mar 6, 2017 at 10:45 PM, Hugh Blemings <hugh(a)blemings.org> >> wrote: >>> Hiya, >>> >>> As has been done for the last few Summits/PTGs in Lwood[1] I've pulled >>> together a list of the various posts to openstack-dev that summarise >>> things >>> at the PTG - projects, videos, anecdotes etc. >>> >>> The aggregated list is in this blog post; >>> >>> http://hugh.blemings.id.au/2017/03/07/openstack-ptg-atlanta-2017-summary-of… >>> >>> >>> Which should aggregate across to planet.openstack.org as well. >>> >>> I'll update this as further summaries appear, corrections/contributions >>> welcome. >> >> Thanks Hugh, that's awesome! > > Most welcome :) > >> Can you please remove the first link: TripleO: >> http://lists.openstack.org/pipermail/openstack-dev/2017-February/112893.html >> >> and only keep this one: >> http://lists.openstack.org/pipermail/openstack-dev/2017-February/112995.html >> > > Done, apologies for the delay, got behind in my email this week! > > Cheers, > Hugh > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

[I18n] Canceling IRC Meeting this week & asking for opinions
by Ian Y. Choi 15 Mar '17

15 Mar '17

Hello all, Due to my personal business this week, unfortunately I need to cancel the IRC meeting in this week. Instead, I would like to ask I18n team language coordinators and translators to share your opinions for the following topics: - Finalizing Pike translation goal & priorities : Discussion on Mar 02 was 1. Dashboard - Horizon [High] 2. Dashboard Authorization Page [High] 3. Magnum UI [Medium] 4. Trove Dashboard [Medium] 5. Sahara Dashboard [Medium] 6. neutron-lbaas-dashboard [Medium] 7. Murano Dashboard [Low] 8. Designate Dashboard [Low] 9. TripleO-UI [Low] - Thoughts on ATC criteria : Please see more details on https://review.openstack.org/#/c/437188/1/doc/source/official_translator.rst - Release note translation criteria : Please see and tell your thoughts on http://lists.openstack.org/pipermail/openstack-i18n/2017-March/002822.html - Translation checksite using OpenStackAnsible : Frank proposed one infra spec - https://review.openstack.org/#/c/440825/ - Log translation discussion : It would be so important for developers to change upstream codes. Please see & share your thoughts on "[openstack-dev] [i18n] [nova] understanding log domain change" thread in http://lists.openstack.org/pipermail/openstack-dev/2017-March/thread.html - Community Goals for Pike : Following http://lists.openstack.org/pipermail/openstack-dev/2017-March/113269.html is important. : Idea - py3 support is to run pep8 job with python3 (@amotoki) : python scripts (zanata_stats.py, zanata_users.py) running with Python3 would be optional? - Review requests on openstack/i18n & openstack/i18n-specs repository Please feel free tell your opinions (just replying with +1 and/or -1 with simple reasoning would be also fine), and I hope that we will have more ideas on such topics and more topics will be well discussed on the IRC meeting next week. With many thanks, /Ian

2 1

[I18n] IRC Meeting reminder: January 12th at 07:00 UTC
by Ian Y. Choi 15 Mar '17

15 Mar '17

Hello all, I18n team is having our next meeting on January 12th 2017 (Thursday) at 07:00 UTC in #openstack-meeting IRC channel. You can find meeting agenda here: https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting#Agenda_for_next_me… Anyone is welcome to add topics on Wiki. If you missed previous IRC meeting or want to refresh, please see last IRC meeting minutes and full logs: Minutes: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… Log: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… With many thanks, /Ian

3 9

Two I18n presentations on Boston Summit & preparation for Forum is needed: Let's brainstorming!
by Ian Y. Choi 13 Mar '17

13 Mar '17

Hello translators, I have three so delightful news to share with all translators regarding Boston Summit & Forum. First, I would like to happily announce that there will be two presentations with I18n & translation during Boston Summit! [Title: I18n-101: Introduction to translation and contributing qualified translation with useful tips] - Presenters: Zheng Xi Zhou (@zzxwill), Alex Eng (@aeng), Ian Y. Choi (@ianychoi) - Date & Time: Wednesday, May 10, 1:50pm-3:20pm - Track: Hands-on Workshops - More details: [1] [Title: Participating in translation makes you an internationalized OpenStacker & developer] - Presenters: Zheng Xi Zhou (@zzxwill), Jean-François Taltavull (@jftalta), Frank Kloeker (@eumel8) - Date & Time: Thursday, May 11, 1:30pm-2:10pm - Track: How to Contribute - More details: [2] @zzxwill (Chinese language team coordinator) suggested & actively submitted those two presentations and they have been finally accepted as two main presentations. Thanks a lot! Note that I have been notified that [3] was not accepted but approved as an Alternate Session for potential inclusion. If I receive a positive news on [3], then I will take appropriate actions to make the possible panel discussion successfully land on Boston Summit (e.g., more discussion with speakers, well-preparing panel questions, ...). Second, That's not all why it would be so nice and attractive for translators to come to Boston Summit. Forum is also important for I18n! There will be more Forum discussion(s) with I18n people - but not limited to I18n: Zanata dev. team, Infra people, developers and operators. I have created an Etherpad [4] to discuss ideas for nice topics during Boston Forum and included the Etherpad on [5]. We have sufficient time to well organize, prepare, and make successful Forum discussion(s) [6]. Please feel free to share your idea on [4] for fruitful discussions with I18n & translation. Third, recently, I have also heard that all ATCs received 300$ discount codes a few days ago. If you have translated >= 300 words from August 2016 to January 2017 but have not received such discount codes, please check your e-mail inbox with spam folder and if there is no such e-mail for discount codes, then please tell me. For such cases, I will take care of it by checking the exact statistics [7, 8] and asking to Foundation if needed. I hope that many translators will come to Boston, see the presentation sessions, and also discuss I18n & translation feedback + issues for Forum. Let's do brainstorming for Boston Summit & Forum for better I18n & translation world in OpenStack! With many thanks, /Ian [1] https://www.openstack.org/summit/boston-2017/summit-schedule/events/18387/i… [2] https://www.openstack.org/summit/boston-2017/summit-schedule/events/18315/p… [3] https://www.openstack.org/summit/boston-2017/vote-for-speakers#/17919 [4] https://etherpad.openstack.org/p/BOS-I18n-brainstorming [5] https://wiki.openstack.org/wiki/Forum/Boston2017 [6] http://lists.openstack.org/pipermail/openstack-dev/2017-March/113115.html [7] https://review.openstack.org/#/c/417569/ [8] http://git.openstack.org/cgit/openstack/i18n/tree/tools/zanata/zanata_stats…

3 4

[Bug 1671248] Re: liberty install guide is not available in english
by Andreas Jaeger 13 Mar '17

13 Mar '17

Liberty is not supported anymore by OpenStack, please install using a newer version. ** Changed in: openstack-i18n Status: New => Invalid ** Changed in: openstack-manuals Status: New => Invalid -- 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/1671248 Title: liberty install guide is not available in english Status in openstack i18n: Invalid Status in openstack-manuals: Invalid Bug description: I was trying to get to the liberty install guide in english but i was not able to access it. Mitaka and Newton are available To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1671248/+subscriptions

1 0

[Bug 1671248] Re: liberty install guide is not available in english
by Alexandra Settle 13 Mar '17

13 Mar '17

** Also affects: openstack-i18n Importance: Undecided Status: New -- 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/1671248 Title: liberty install guide is not available in english Status in openstack i18n: New Status in openstack-manuals: New Bug description: I was trying to get to the liberty install guide in english but i was not able to access it. Mitaka and Newton are available To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1671248/+subscriptions

1 0

translated release note: import criteria and publishing
by Akihiro Motoki 10 Mar '17

10 Mar '17

Hi i18n team, CC: Doug from the release team. We are now preparing translated version of release notes. I would like to discuss the import criteria of release notes translation. If there is a better way, it would be great. == Problem == Release notes translation is imported when 75% of a PO file is translated. 75% is calculated as a whole. If a language team wants to translate release notes of a specific release, the team needs to translate release notes of other releases. This comes from the fact that the translation percentage is calculated as a whole. The development teams started to use reno for translation at the beginning of Mitaka cycle and Liberty release notes are converted into reno-based release notes. This mean if we want to publish Newton release notes translation, we need to translate release notes for Liberty and Mitaka at the same time. == Proposal == I hope we can publish translated release notes per release. If Newton release notes translation completes, I want to publish Newton release notes. My proposal is to change the import criteria for release notes translation to 75% at least for a specific release. If translation progress of release notes are less than 40% for all releases, a corresponding PO file will be removed from the repo. I proposed an infra scirpt change to implement the above. https://review.openstack.org/#/c/383622/ Proposed threshold 75% and 40% might need to be revisited. == Open question == Do we publish translated release notes for a release with <75% progress? This is about publishing rendered release notes. For example, assume my lang team have translated release notes 90% for Newton, 10% for Mitaka and Liberty. In this case, which is better not to publish Mitaka and Liberty release notes translation or to publish all? My vote is not to publish less-translated version of release notes. == Note == Question from Ian on the gerrit review. By the way, is it possible to see only Newton release note strings in Zanata? Answer: The current Zanata version we use does not support filtering by an original filename. You need to check English release notes like [1] or [2] and search strings on Zanata. [1] https://releases.openstack.org/newton/index.html [2] http://docs.openstack.org/releasenotes/horizon/ Akihiro

6 18

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

10 Mar '17

Team team team team team, It's been a crazy few weeks since the PTG ramping up our goals for Pike! Big thanks to everyone who has really hit the ground running with our new set of objectives. This week I have been helping out Ianeta with the High Availability Guide ToC plan, (which you can review here: https://review.openstack.org/#/c/440890/ ) and Rob Clark with the Security Guide plan (https://etherpad.openstack.org/p/sec-guide-pike ). I have also been working alongside Brian and the nova team to unblock ourselves from a particularly nasty, critical, bug affecting the Install Guide. For more information: https://bugs.launchpad.net/openstack-manuals/+bug/1663485 Big thanks to Darren Chan who has been doing an awesome job for the last two weeks in keeping our bug list under control. We are down to an amazing 108 bugs in queue. Next week, we have Ianeta who 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 a few spots open for the rest of the cycle: https://wiki.openstack.org/wiki/Documentation/SpecialityTeams#Bug_Triage_Te… == Progress towards Pike == https://www.timeanddate.com/countdown/newyear?p0=24&msg=Pike+release&ud=1&f… Bugs closed in Pike: 32! You guys rock :) == The Road to the Summit in Boston == The summit schedule has been announced: https://www.openstack.org/summit/boston-2017/summit-schedule/#day=2017-05-08 I will be representing the docs team at the summit for the new 'Project Update' session. For more information: https://www.openstack.org/summit/boston-2017/summit-schedule/global-search?… Let me know if you had any doc talks accepted! == Speciality Team Reports == API - Anne Gentle: One prominent change is that the Block Storage API v2 is now exactly replicated with v3 and so is now marked Deprecated. The list of all OpenStack APIs is now also here: https://developer.openstack.org/#api and you can see them based on support level here: https://developer.openstack.org/api-guide/quick-start/ Configuration Reference and CLI Reference - Tomoyuki Kato: N/A High Availability Guide - Ianeta Hutchinson: So, we have this patch https://review.openstack.org/#/c/440890/13 to establish the new ToC for HA Guide. We are trying to move all content that is relevant in the current guide over to the new ToC. From there, we will be filing bugs to start collaboration with the OSIC DevOps team who have signed up to adopt-a-guide and will be helping to provide content as SME's. Hypervisor Tuning Guide - Blair Bethwaite: The Scientific-WG is considering proposing a hypervisor tuning + guide session for the Boston Forum though, so hopefully if that goes ahead it will create some renewed interest. Installation guides - Lana Brindley: Waiting to sort out the last couple of bugs before we branch, hopefully next week. Networking Guide - John Davidge: Huge number of patches this week on the RFC 5737 fix[1] - thanks to caoyuan! Continued progress on replacing neutronclient commands with OSC versions. Thank you to all contributors. A patch[2] changing a documented use of ’tenant’ to ‘project’ sparked a discussion in the neutron team about the mixture of terminology in neutron, with the conclusion that all remaining references to ’tenant’ in our config files and elsewhere are to be replaced with ‘project’ as soon as possible. Some of these will require deprecation cycles. Impact on the networking guide should be minimal. [1] https://launchpad.net/bugs/1656378 [2] https://review.openstack.org/#/c/43816 Operations and Architecture Design guides - Darren Chan: A patch to move the draft Arch Guide to docs.o.o has merged. The previous guide has been moved to a "to archive" directory until the archiving process is ready. The Arch Guide working group met this week to rearchitect and scope the design content. We're currently focussed on the storage content. Security Guide - Nathaniel Dillon: Rob Clark (PTL) and Alex are in the process of planning the ins and out of the overhaul of the guide. We're talking about dramatically reducing the scope, and introducing new, maintainable, content. Rob (hyakuhei) is also looking at getting a sprint in Austin at some point to get the security team all together and pump out some content. We also have the OSIC Security team pumping out some of the main, non-wishlist, bugs at preset. Training Guides - Matjaz Pancur: N/A Training labs - Pranav Salunke, Roger Luethi: We have pushed the current state of the Ocata training-labs changeset in case others find it useful. The scripts follow the install-guide and https://review.openstack.org/#/c/438328/ . The resulting cluster cannot launch instances because it fails to find a host (just like others following the install-guide have reported). Admin and User guides - Joseph Robinson: For the User and Admin Guides, I've been looping through the bug list - there are SDK bugs and the issue of moving the python SDK examples, which was discussed back in Newton. There are also two telemetry bugs, which I need to contact the liaisons for. The only other point, is reviewing the Admin Guide migration spec: https://review.openstack.org/#/c/439122/ == Doc team meeting == Our next meeting will be on Thursday, 23 March at 2100 UTC in #openstack-meeting-alt. For more meeting details, including minutes and the agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting I am unavailable to be the meeting chair this week :( is someone able to host? Ping or email if you are able to help out! -- Have a great weekend! Alex Fastest typer in the universe (2014) and expert cactus photographer IRC: asettle Twitter: dewsday

1 0

[Bug 1671367] Re: Losing a semicolon in overview page
by Rob Cresswell 09 Mar '17

09 Mar '17

** Also affects: openstack-i18n Importance: Undecided Status: New ** Changed in: horizon Status: In Progress => Invalid -- 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/1671367 Title: Losing a semicolon in overview page Status in OpenStack Dashboard (Horizon): Invalid Status in openstack i18n: New Bug description: Losing a semicolon Behind the "This Period's RAM-Hours". Semicolons should use Chinese, but using the English a semicolon. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1671367/+subscriptions

1 0

[Bug 1671690] [NEW] Use incorrect semicolon
by ZouHuiying 09 Mar '17

09 Mar '17

Public bug reported: Losing a semicolon Behind the "This Period's RAM-Hours". Semicolons should use Chinese, but using the English a semicolon. ** Affects: openstack-i18n Importance: Undecided Assignee: ZouHuiying (zhouhy) Status: New ** Changed in: openstack-i18n Assignee: (unassigned) => ZouHuiying (zhouhy) -- 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/1671690 Title: Use incorrect semicolon Status in openstack i18n: New Bug description: Losing a semicolon Behind the "This Period's RAM-Hours". Semicolons should use Chinese, but using the English a semicolon. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1671690/+subscriptions

1 0