- OpenStack-I18n - lists.openstack.org

User survey translation status with translate checksite
by Ian Y. Choi 16 Jun '17

16 Jun '17

Hello! In Zanata, not only OpenStack official projects, but also user survey [1] is available to translate for better internationalized OpenStack from around the end of April this year :) Now I have found that some countries have nice progress on user survey translation, and I have heard that Foundation recently updated translation source strings to have more source strings in Zanata. Please revisit Zanata [1], also check user survey translate checksite, and review user survey translation for better quality of translated user survey. - User survey translate checksite : The site is available through https://devbranch.openstack.org/user-survey/ page. : Login is needed: The e-mail and password should be the same as your Zanata login. If you have trouble in your login, please tell me and I would like to guide you to resolve such situation. - How to reflect translation update to the translate checksite : You can edit translations through Zanata: https://translate.openstack. org/iteration/view/openstack-user-survey/openstack-user-survey . : Foundation manually updates po files from Zanata to translation checksite repository. : You can make a pull request to gettext/Locale folder in https://github.com/openstackweb/openstack-org/ github repisitory (Note: The repository is not in git.openstack.org and it is mainly managed from GitHub.) : If you are not familiar with Github pull request, please tell me then I will make a pull request. One example of pull request is: https://github.com/OpenStackweb/openstack-org/pull/78 With many thanks, /Ian [1] https://translate.openstack.org/iteration/view/openstack-user-survey/openst…

2 1

[I18n] Canceling IRC Meeting: April 27th at 13:00 UTC
by Ian Y. Choi 14 Jun '17

14 Jun '17

Hello all, Due to my international flight schedule, I cannot stay in IRC and discuss with some topics. Since other I18n IRC meeting chairs might be unavailable as far as I know, I would like to cancel the IRC meeting on April 27th at 13:00 UTC. Please see the previous meeting minutes at : http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/ . Also, I would like to mention those two things as a reminder: : More planning for Boston Summit for I18n - are you attending? - http://lists.openstack.org/pipermail/openstack-i18n/2017-April/002895.html : Let's also consider User survey translation: now available at Zanata! - http://lists.openstack.org/pipermail/openstack-i18n/2017-April/002896.html Now I am not pretty sure whether I can organize the next IRC meeting on May 4th, but I will try to do my best. With many thanks, /Ian

1 1

[I18n] Zanata webinar with IRC meeting (qna): June 8th at 13:00 UTC
by Ian Y. Choi 06 Jun '17

06 Jun '17

Hello, I am glad to announce that there will be a webinar from Zanata development team. - Title: The features since 3.9 in Zanata - Date & Time: June 8th at 13:00 UTC (presentation will be for 30-40 minutes) - Invited speaker: Patrick Huang (Senior Software Engineer in Red Hat) - Presentation description: Zanata [1] is an open source translation platform and OpenStack I18n team [2] uses it as a translation platform [3] running upon openstack-infra [4]. At the moment translate.openstack.org is running Zanata version 3.9.6. Here we will have a preview of the new features developed by Zanata team since 3.9.x. This will help us to decide when to upgrade to newer version as well as better utilize the tool once it's upgraded. - YouTube Live URL: https://www.youtube.com/watch?v=mVCSAfk4t54 During this webinar, I18n IRC meeting (#openstack-meeting freenode IRC channel) will be used for questions and answers on the webinar. Also, I have heard that YouTube Live access might be limited to some countries. For that, please tell me for me to prepare a channel with Skype for Business URL. Note that the attendees using Skype for Business might be muted. With many thanks, /Ian [1] http://zanata.org/ [2] https://wiki.openstack.org/wiki/I18nTeam [3] https://translate.openstack.org [4] http://git.openstack.org/cgit/openstack-infra/puppet-zanata

2 1

[Turkish] Asking for glossary review
by Ian Y. Choi 31 May '17

31 May '17

Hello Turkish translators, İşbaran Akçayır asked me to upload a glossary for Turkish. I would like Turkish translators to review https://review.openstack.org/#/c/467240/ and reply with +1 if it looks good. If you are not familiar with Gerrit (review.openstack.org) please see some documents and presentations in upstream institute [1]. I think [2] and [3] might be helpful, or please share your thoughts on Turkish glossary by replying to this e-mail copying with openstack-i18n(a)lists.openstack.org . With many thanks, /Ian [1] https://docs.openstack.org/upstream-training/ [2] https://docs.openstack.org/upstream-training/accounts.html#setup-gerrit-acc… [3] https://docs.openstack.org/upstream-training/workflow-reviewing.html#1

2 1

FW: [OpenStack-docs] [openstack-doc] [dev] What's up doc? Summit recap edition
by Alexandra Settle 25 May '17

25 May '17

Docs update below ☺ From: Alexandra Settle <a.settle(a)outlook.com> Date: Friday, May 19, 2017 at 12:12 PM To: "'openstack-docs(a)lists.openstack.org'" <openstack-docs(a)lists.openstack.org> Cc: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev(a)lists.openstack.org> Subject: [OpenStack-docs] [openstack-doc] [dev] What's up doc? Summit recap edition Hi everyone, The OpenStack manuals project had a really productive week at the OpenStack summit in Boston. You can find a list of all the etherpads and attendees here: https://etherpad.openstack.org/p/docs-summit As we all know, we are rapidly losing key contributors and core reviewers. We are not alone, this is happening across the board. It is making things harder, but not impossible. Since our inception in 2010, we’ve been climbing higher and higher trying to achieve the best documentation we could, and uphold our high standards. This is something to be incredibly proud of. However, we now need to take a step back and realise that the amount of work we are attempting to maintain is now out of reach for the team size that we have. At the moment we have 13 cores, of which none are full time contributors or reviewers. This includes myself. That being said! I have spent the last week at the summit talking to some of our leaders, including Doug Hellmann (cc’d), Jonathan Bryce and Mike Perez regarding the future of the project. Between myself and other community members, we have been drafting plans and coming up with a new direction that will hopefully be sustainable in the long-term. I am interested to hear your thoughts. I want to make sure that everyone feels that we’re headed in the right direction first and foremost. All of these action items are documented in this WIP etherpad: https://etherpad.openstack.org/p/doc-planning Some further highlights from the event… * The documentation team was represented by myself, Olga, and Alex Adamov for the Project Update: Documentation on the Monday. If you’d like to catch up with what we talked about, the video is available online now: https://www.youtube.com/watch?v=jcfbKxbpRvc The translation team PTL, Ian Choi, also had a session about getting more involved with the I18N team. You can view that video here: https://www.youtube.com/watch?v=ybFI4nez_Z8 * Ian and I also hosted the joint I18N and documentation onboarding session. We were visited by some friendly faces, and some new ones. Between Ian and myself, we discussed the documentation and translation workflows, and how to get involved (the mailing list, IRC channel, etc). Which was lots of fun :) we’d love to see more people there in the future, hopefully we’ll slowly get there! * This week I was focusing heavily on making the community aware that the documentation team was struggling to maintain contributors, but continuing with the same amount of work. This was a heavy conversation to be having, but it posed some really interesting questions to key leaders, and hopefully raised appropriate concerns. Ildiko and I hosted “OpenStack documentation: The future depends on all of us”. This was a really interesting session. I was able to pose to the group of attendees that the documentation team was struggling to maintain contributions. Major Hayden was kind enough to take notes during the session, you can find those here: https://etherpad.openstack.org/p/doc-future The project teams that came and represented their groups were interested in discussing the project-specific documentation (is living in the project’s repo tree the best place?) and voiced concerns I had otherwise not heard before. I recommend reading the notes to get a better idea :) * Kendall Nelson and Ildiko also hosted a session on the OpenStack Upstream Institute highlights. I recommend watching the video which is now live and available here: https://www.openstack.org/videos/boston-2017/openstack-upstream-institute-h… * One of the key takeaways from the summit was the session that I joint moderated with Melvin Hillsman regarding the Operations and Administration Guides. You can find the etherpad with notes here: https://etherpad.openstack.org/p/admin-ops-guides The session was really helpful – we were able to discuss with the operators present the current situation of the documentation team, and how they could help us maintain the two guides, aimed at the same audience. The operator’s present at the session agreed that the Administration Guide was important, and could be maintained upstream. However, they voted and agreed that the best course of action for the Operations Guide was for it to be pulled down and put into a wiki that the operators could manage themselves. We will be looking at actioning this item as soon as possible. These action items will free up the documentation team to become gate keepers and reviewers of documentation. Our key focus as a team will be on the tooling for the docs.openstack.org site (including the API docs). I’m really interested to hear everyone’s thoughts going forward – this is not set in stone. We need to change our strategy, and now is the time. If you’d rather reach out and discuss this personally, asettle on IRC is always the best place to find me. Thanks, Alex

2 1

[Bug 1691900] [NEW] Mistake in Newton Installation Guide
by Youhei Tooyama 23 May '17

23 May '17

Public bug reported: This Document are OpenStack Newton. But Document says to install Ocata. about CentOS yum install centos-release-openstack-ocata ↓ yum install centos-release-openstack-newton about RHEL yum install https://rdoproject.org/repos/rdo-release.rpm ↓ yum install https://repos.fedorapeople.org/repos/openstack/openstack-newton/rdo-release… This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [x] I have a fix to the document that I can paste below including example: input and output. ----------------------------------- Release: 15.0.0 on 2017-05-18 19:32 SHA: 27f002a754e77d621332f30353044a91e449dd79 Source: https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install… URL: https://docs.openstack.org/newton/ja/install-guide-rdo/environment-packages… ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide ** Description changed: This Doc are OpenStack Newton. - But Document says to install ocata. + But Document says to install Ocata. about CentOS yum install centos-release-openstack-ocata ↓ yum install centos-release-openstack-newton about RHEL yum install https://rdoproject.org/repos/rdo-release.rpm ↓ yum install https://repos.fedorapeople.org/repos/openstack/openstack-newton/rdo-release… This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - - [x] I have a fix to the document that I can paste below including example: input and output. + - [x] I have a fix to the document that I can paste below including example: input and output. ----------------------------------- Release: 15.0.0 on 2017-05-18 19:32 SHA: 27f002a754e77d621332f30353044a91e449dd79 Source: https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install… URL: https://docs.openstack.org/newton/ja/install-guide-rdo/environment-packages… ** Description changed: - This Doc are OpenStack Newton. + This Document are OpenStack Newton. But Document says to install Ocata. about CentOS yum install centos-release-openstack-ocata ↓ yum install centos-release-openstack-newton about RHEL yum install https://rdoproject.org/repos/rdo-release.rpm ↓ yum install https://repos.fedorapeople.org/repos/openstack/openstack-newton/rdo-release… This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [x] I have a fix to the document that I can paste below including example: input and output. ----------------------------------- Release: 15.0.0 on 2017-05-18 19:32 SHA: 27f002a754e77d621332f30353044a91e449dd79 Source: https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install… URL: https://docs.openstack.org/newton/ja/install-guide-rdo/environment-packages… -- 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/1691900 Title: Mistake in Newton Installation Guide Status in openstack i18n: New Bug description: This Document are OpenStack Newton. But Document says to install Ocata. about CentOS yum install centos-release-openstack-ocata ↓ yum install centos-release-openstack-newton about RHEL yum install https://rdoproject.org/repos/rdo-release.rpm ↓ yum install https://repos.fedorapeople.org/repos/openstack/openstack-newton/rdo-release… This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [x] I have a fix to the document that I can paste below including example: input and output. ----------------------------------- Release: 15.0.0 on 2017-05-18 19:32 SHA: 27f002a754e77d621332f30353044a91e449dd79 Source: https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install… URL: https://docs.openstack.org/newton/ja/install-guide-rdo/environment-packages… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1691900/+subscriptions

4 5

[Bug 1686339] [NEW] Wrong repository in Japanese install tutorials
by Tomonobu Niwa 22 May '17

22 May '17

Public bug reported: In Newton release, Japanese install manual describes to register Ocata repository when installing OpenStack packages, while that of English version explains to install Newton repository. Japanese tutorials: openSUSE: https://docs.openstack.org/newton/ja/install-guide-obs/environment-packages… CentOS: https://docs.openstack.org/newton/ja/install-guide-rdo/environment-packages… Ubuntu: https://docs.openstack.org/newton/ja/install-guide-ubuntu/environment-packa… ** 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/1686339 Title: Wrong repository in Japanese install tutorials Status in openstack i18n: New Bug description: In Newton release, Japanese install manual describes to register Ocata repository when installing OpenStack packages, while that of English version explains to install Newton repository. Japanese tutorials: openSUSE: https://docs.openstack.org/newton/ja/install-guide-obs/environment-packages… CentOS: https://docs.openstack.org/newton/ja/install-guide-rdo/environment-packages… Ubuntu: https://docs.openstack.org/newton/ja/install-guide-ubuntu/environment-packa… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1686339/+subscriptions

2 1

[Bug 1675298] Re: automatic generation of LANGUAGES list in settings.py
by OpenStack Infra 22 May '17

22 May '17

Reviewed: https://review.openstack.org/450126 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=a88092630014c53… Submitter: Jenkins Branch: master commit a88092630014c53c9e6fe4ee9265f8443eea96bd Author: Akihiro Motoki <amotoki(a)gmail.com> Date: Sun Mar 26 14:42:25 2017 +0000 Generate language list automatically Previously the available language list is maintained manually. This commit change horizon to check translation message catalog is available for each language and generate the language list automatically. settings.LANGUAGES is still used to determines the initial set of languages and now defaults to the list provided by django. Change-Id: I9d9c934beebd7a641e2feb0d5cdfa839e0efa3c3 Closes-Bug: #1675298 ** Changed in: horizon 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/1675298 Title: automatic generation of LANGUAGES list in settings.py Status in OpenStack Dashboard (Horizon): Fix Released Status in openstack i18n: New Bug description: At now, LANGUAGES list in openstack_dashboard/settings.py is updated manually. It is better to generate the language list automatically based on the existence of PO files. In horizon, there are four types of PO files ([horizon/locale, openstack_dashboard] * [django, djangojs]). It looks better to check whether all four types of PO files exist in the repo and list such languages. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1675298/+subscriptions

1 0

FYI: Statistics for docs.openstack.org by language & location
by Ian Y. Choi 18 May '17

18 May '17

Hello I18n team & Docs team! I would like to share Google Analytics statistics for https://docs.openstack.org . During Boston Summit, Alex showed such stats in [1] and me mentioned in [2]. I downloaded statistics data during Boston Summit for recent one year, and today I finally converted the data into text-based format to share through mailing lists. As far as I know, "Language" view in Google Analytics would be based on browser language settings, not sub-domain such as "docs.openstack.org/ja" or "docs.openstack.org/ko-kr", and "Location" might be where the web browser client actually requested. Feel free to share your thoughts: such as interpretation with such statistics, more meaningful metrics in Google Analytics to Docs & I18n team, and so on :) == Google Analytics: "Language" view for docs.openstack.org == (May 11, 2016 - May 10, 2017 / TOP 25) +----------+----------+----------------+ | Language | Sessions | % New Sessions | +----------+----------+----------------+ | en-us | 3374650 | 23.77% | +----------+----------+----------------+ | zh-cn | 1000346 | 18.03% | +----------+----------+----------------+ | en-gb | 295160 | 25.82% | +----------+----------+----------------+ | ja | 243452 | 19.06% | +----------+----------+----------------+ | fr | 159729 | 25.18% | +----------+----------+----------------+ | ko | 106003 | 17.17% | +----------+----------+----------------+ | ja-jp | 101114 | 28.62% | +----------+----------+----------------+ | zh-tw | 97826 | 19.32% | +----------+----------+----------------+ | de | 81475 | 32.40% | +----------+----------+----------------+ | ru | 68867 | 24.33% | +----------+----------+----------------+ | es | 63200 | 28.19% | +----------+----------+----------------+ | pt-br | 57748 | 30.93% | +----------+----------+----------------+ | ko-kr | 41212 | 25.11% | +----------+----------+----------------+ | pl | 33287 | 25.69% | +----------+----------+----------------+ | it | 31232 | 28.80% | +----------+----------+----------------+ | es-es | 30132 | 29.58% | +----------+----------+----------------+ | ru-ru | 26613 | 27.11% | +----------+----------+----------------+ | de-de | 22015 | 36.45% | +----------+----------+----------------+ | fr-fr | 19428 | 33.08% | +----------+----------+----------------+ | it-it | 18263 | 32.52% | +----------+----------+----------------+ | es-419 | 17672 | 28.48% | +----------+----------+----------------+ | en | 14706 | 27.52% | +----------+----------+----------------+ | nl | 13339 | 38.17% | +----------+----------+----------------+ | sv | 12805 | 23.17% | +----------+----------+----------------+ == Google Analytics: "Location" view for docs.openstack.org == (May 11, 2016 - May 10, 2017 / TOP 25) +----------------+----------+----------------+ | Country | Sessions | % New Sessions | +----------------+----------+----------------+ | United States | 1305483 | 24.73% | +----------------+----------+----------------+ | China | 906676 | 19.22% | +----------------+----------+----------------+ | India | 694034 | 23.82% | +----------------+----------+----------------+ | Japan | 428682 | 20.77% | +----------------+----------+----------------+ | France | 187056 | 25.39% | +----------------+----------+----------------+ | Germany | 180090 | 28.18% | +----------------+----------+----------------+ | South Korea | 168027 | 19.34% | +----------------+----------+----------------+ | United Kingdom | 167054 | 27.45% | +----------------+----------+----------------+ | Canada | 135999 | 24.74% | +----------------+----------+----------------+ | Russia | 125238 | 21.60% | +----------------+----------+----------------+ | Taiwan | 124119 | 18.55% | +----------------+----------+----------------+ | Brazil | 96044 | 28.07% | +----------------+----------+----------------+ | Spain | 95196 | 24.54% | +----------------+----------+----------------+ | Sweden | 73556 | 20.51% | +----------------+----------+----------------+ | Italy | 73003 | 27.99% | +----------------+----------+----------------+ | Vietnam | 66155 | 18.12% | +----------------+----------+----------------+ | Poland | 62403 | 24.73% | +----------------+----------+----------------+ | Australia | 62277 | 28.06% | +----------------+----------+----------------+ | Israel | 60821 | 19.37% | +----------------+----------+----------------+ | Hong Kong | 52224 | 22.83% | +----------------+----------+----------------+ | (not set) | 51330 | 18.09% | +----------------+----------+----------------+ | Finland | 51218 | 19.44% | +----------------+----------+----------------+ | Ukraine | 49667 | 21.54% | +----------------+----------+----------------+ | Netherlands | 49546 | 30.67% | +----------------+----------+----------------+ With many thanks, /Ian [1] https://www.openstack.org/summit/boston-2017/summit-schedule/events/18692/d… [2] https://www.openstack.org/summit/boston-2017/summit-schedule/events/18728/f…

1 0

Questions on new user registration failure in translate.openstack.org
by Ian Y. Choi 10 May '17

10 May '17

Hello Alex and Patrick, I am very thankful your your all and kind support on Zanata - translate.openstack.org :) Now I have a question on some authentication part in translate.openstack.org . As you might have already noticed, I18n team will have one important Hands-on Workshop session during Boston Summit on this Wednesday [1]. Yesterday, I met a Chinese OpenStack contributor and I asked her to also join in translate.openstack.org. However, she could not proceed to register in translate.openstack.org although she already had registered www.openstack.org account and signed ICLA. I was trying to find some log messages in Zanata but I did not know how to see some log messages. Would you investigate in this important authentication problem? It might imply that many participants on this Wednesday for Hands-on Workshop session will not able to register their accounts in Zanata, and now I am too much worried about this worst case. If we might need actual server logs in the production server, please tell me then I will ask this to infra team members. With many thanks, /Ian [1] https://www.openstack.org/summit/boston-2017/summit-schedule/events/18387/i…

3 3

[I18n] (Special) Summit hack-room & IRC meeting in this week with Skype
by Ian Y. Choi 09 May '17

09 May '17

Hello all, First of all, I really really feel that Boston Summit welcomes translators! Thanks to lots of kind support from upstream contributors, users, operators, and also Foundation staff, I think I18n team is able to have so many I18n sessions during this Summit. I have asked translators whether they would come to Boston Summit or not via i18n mailing list several times but it seems that a few active translators finally have come to Boston Summit [1]. Now, I would like to propose a hack-room for I18n team on on Thursday 9:00 AM - 10:30 AM at Hynes, MR 108 (I have signed into [2]). I think the time would be the best for I18n team since Thursday 9:00 AM - 10:00 AM is the same as I18n IRC meeting time slot [3]. So, for physical Summit attendees: - Please attend to I18n hack room on Thursday 9:00 AM - 10:30 AM at Hynes, MR 108. - If someone wants to more know I18n and translation or have questions on translation, please ping me via IRC. My IRC nickname is "ianychoi". And for I18n translators (+ Zanata development team members) who are unable to physically attend to the Summit: - Please come to IRC meeting [3]. - Also I strongly encourage to also join a voice meeting via Skype Business. I have made a link for the Meeting: https://meet.lync.com/ychoi/ianychoi/3HVZ0CY1 . Please join in the meeting if you would like to see I18n people in the Summit :) - Timezone information is also available at: [4] Also, I welcome upstream contributors, users, operators, and even Summit-101 members who would like to know how I18n team is dealing with translation. I am now proposing the following topics, but topics may be subject to change: - (Greeting) - Sharing how Summit is going with I18n - Report of recent Zanata production server error - User survey translation status - Discussion on I18n team PTG participation - Feedback from I18n contributors: PTG, Summit, Design Summit, Forum - Action items With many thanks, /Ian [1] https://etherpad.openstack.org/p/i18n-boston-summit-activities [2] https://ethercalc.openstack.org/Boston_Forum_Hacking_Rooms [3] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting#Agenda_for_next_me… [4] https://www.timeanddate.com/worldclock/meetingdetails.html?year=2017&month=…

3 2

[I18n] IRC Meeting reminder today: May 4th at 07:00 UTC and next week
by Ian Y. Choi 04 May '17

04 May '17

Hello all, I18n team is having our next meeting on May 4th 2017 (Thursday) at 07:00 UTC in #openstack-meeting IRC channel. Please refer to what I am suggesting for meeting agenda at : https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting#Agenda_for_next_me… and previous meeting logs are available at : https://wiki.openstack.org/wiki/I18N/MeetingLogs . Anyone is welcome to add topics on Wiki For next week IRC meeting (May 11st 2017 13:00 UTC), It conflicts with Boston Summit schedule, however, I would like to lead the next IRC meeting if there is remote attendee. Please reply from this message if you would like to attend to the IRC meeting on May 11st. If there are no replies, then I would like to skip the IRC meeting on May 11st 2017. FYI: Please also see the timezone at : https://www.timeanddate.com/worldclock/meetingdetails.html?year=2017&month=… With many thanks, /Ian

2 1

Let's also consider User survey translation: now available at Zanata!
by Ian Y. Choi 24 Apr '17

24 Apr '17

Hello, OpenStack User survey translation is now available at Zanata : https://translate.openstack.org/iteration/view/openstack-user-survey/openst… Thanks a lot especially Heidi Joy, Jimmy McArthur, and Sebastian Marcet who have supported, implemented user survey translation functionality, and integrated into Zanata with pot files. QA page for qualified translation and review would be available later if translation ratio is high. Foundation asks me that it would be so nice to have translations by around the early of June. There will be OpenStack Days in Asia region on July, and the translated user survey is anticipated to distribute to local users with translated questions. Note that the followings are when each country in Asia will have OpenStack Days (OSD): - July 13-14: OSD Korea - July 18-19: OSD Taiwan - July 20-21: OSD Japan - July 22-23: OSD India - July 24-25: OSD China In my opinion, considering user survey translation with OSD would strengthen the relationship with local translators and local user group members. Please also consider and translate user survey :) With many thanks, /Ian

1 0

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

24 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 24 Apr '17

24 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 10 Apr '17

10 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 07 Apr '17

07 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 06 Apr '17

06 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 04 Apr '17

04 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 03 Apr '17

03 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

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

27 Mar '17

Team team team team team, Well the last month has just FLOWN by since the PTG. We've got plenty going on in the doc team... This week I have been helping out the security team with the Security Guide. We've been working on some cursory edits, and removal of content. A few patches have already made it through - thanks to the OSIC security team for tackling some of the outstanding bugs. There'll be more edits coming from me in the next few weeks. To see our planning: https://etherpad.openstack.org/p/sec-guide-pike I am also in the process of drafting a governance tag for our install guides. Would be great for everyone to review and understand what the process will involve: https://review.openstack.org/#/c/445536/ Shoutout and big thanks to Brian Moss and the nova team who worked together tirelessly to document Nova v2 Cells and Placement API - which was a massive blocker for our Installation Guide. Also, thank you to our Ocata release managers, Maria Zlatkova and Brian Moss for cutting the branch! Pike is well and truly underway now. Ianeta Hutchinson has done an awesome job for the last two weeks in keeping our bug list under control. We are down to an amazing 104 bugs in queue, and 59 bugs closed this cycle already! Next week, we have Lana 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… == The Road to the Summit in Boston == * Schedule has been released: https://www.openstack.org/summit/boston-2017/summit-schedule/ * Docs and I18n have a project onboarding room at the summit, keep an eye out on the dev ML for more information. Kendall will inform us when the time comes. Anyone around to help me with that? http://lists.openstack.org/pipermail/openstack-dev/2017-March/114149.html * Docs project update will be delivered by me (asettle) on Mon 8, 3:40pm-4:20pm. https://www.openstack.org/summit/boston-2017/summit-schedule/global-search?… == Specialty Team Reports == * API - Anne Gentle: There's still a lot of discussion on https://review.openstack.org/#/c/421846/ which is about API change guidelines. Take a look and join in on the review. Also on the openstack-dev list, there's a thread about the future of the app catalog, which is relevant to the app developer audience so I include it here: http://lists.openstack.org/pipermail/openstack dev/2017-March/113362.html<http://lists.openstack.org/pipermail/openstack%20dev/2017-March/113362.html> Also related to the app dev audience is the wrapping up of the App Ecosystem working group: http://lists.openstack.org/pipermail/user-committee/2017-March/001825.html * Configuration Reference and CLI Reference - Tomoyuki Kato: N/A * High Availability Guide - Ianeta Hutchinson: At the Atlanta PTG, the documentation team outlined a new table of contents that is now upstream as a draft here: https://github.com/openstack/openstack-manuals/tree/master/doc/ha-guide-dra…. A blocker to progress in the past had been a lack of SME’s for the topic of high availability but that is no longer the case \o/. The OSIC DevOps team has an “adopt-a-guide” project in which they are collaborating with the OpenStack docs community and OSIC Docs team to apply the new ToC and validate all content for the guide. The progress of this collaboration is being tracked here https://docs.google.com/spreadsheets/d/1hw4axU2IbLlsjKpz9_EGlKQt0S6siViik7E… We are calling for more contributors both as SME's and tech writers. Ping iphutch if interested! * Hypervisor Tuning Guide - Blair Bethwaite: N/A * Installation guides - Lana Brindley: Cells bug is closer to being fixed, and we are closer to a complete test install https://wiki.openstack.org/wiki/Documentation/OcataDocTesting look at all that green!). We're planning to branch Ocata by the end of this week. * Networking Guide - John Davidge: N/A * Operations and Architecture Design guides - Darren Chan: Arch Design Guide: Minor IA and general cleanup of the storage, compute, and networking sections in the Design chapter. Currently updating gaps in storage design content. Ops Guide: Removed cloud architecture content (migrated to the Arch Design Guide). * Security Guide - Nathaniel Dillon: Edits from Alex going through, and patches from the OSIC DevOps team. See above for more info. * Training Guides - Matjaz Pancur: For Training guides, related topics: a new brand for activities around OpenStack Upstream University/Training. It is now known as OpenStack Upstream Institute (https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute) * Training labs - Roger Luethi: We are currently testing our automated version of the Ocata install-guide. We had a problem with Ubuntu's new ISO image (16.04.2 LTS) which is now resolved. * User guides - Joseph Robinson: Several other Legacy commands were converted to OS commands this week. Reviewed the Admin Guide spec. * Theme and Tools - Brian Moss: I'd like to do an openstackdocstheme release soon, as we've got some items (PDF styling, search page JS fix, image centering) that would be good to have in production. Any concerns or last minute items to merge please let me know. We've had some issues come up with the auto-generation scripts. Some have been fixed already (thanks Kato and Christian!), and we're investigating others. If you notice anything amiss or would like to help out, please let me know. 46 open bugs, 8 closed in Pike == Doc team meeting == Our next meeting will be on Thursday, 7 April at 2100 UTC in #openstack-meeting-alt. For more meeting details, including minutes and the agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting -- Have a great week :) Alex IRC: asettle Twitter: dewsday

1 0

Generate horizon language list automatically
by Akihiro Motoki 27 Mar '17

27 Mar '17

Hi I18n team, I just push my patch which changes horizon to generate the language list automatically [1] and the this topic is traced by the bug [2]. I would like to share my long-standing idea with the team. Does it sound reasonable? * The basic idea is to generate the language list based on message catalogs (PO files) availability. * Horizon now has four types of message catalogs (django, djangojs) in horizon and openstack_dashboard respectively. If all message catalogs are present, such languages are listed in the language list. There are some corner case logic. * Some languages share a same locale prefix. Good example is Spanish variants: es, es-ar, es-mx and es-ve. When horizon searches message catalogs for es-ar, a locale "es_AR" is first checked and then "es" (prefix) locale is checked. In this case, if "es-ar" has no corresponding translations ("es_AR") and "es" is already registered in the language list, "es-ar" will not be added in the language list. * For the source language (i.e., English), message catalog existence check is skipped. * The current setting LANGUAGES still has effect. Operators can use e used to limit the initial set of languages to exclude languages they want to show to their users. (Note that even when a language is specified in LANGUAGES setting, if not all message catalogs for the language exist the language will be skipped.) Thanks, Akihiro [1] https://review.openstack.org/#/c/450126/ [2] https://bugs.launchpad.net/horizon/+bug/1675298

1 0

Re: [OpenStack-I18n] [OpenStack-docs] stable/ocata created, publishing frozen for now
by Ian Y. Choi 25 Mar '17

25 Mar '17

Oh, great! Congrats for stable/ocata in openstack-manuals! To work translation sync job successfully with https://review.openstack.org/#/c/449385 <https://review.openstack.org/#/c/449385> , I18n team needs to create stable-ocata version for openstack-manuals in Zanata: https://translate.openstack.org. I checked that someone (maybe Kato-san or Andreas I think) already created stable-ocata version for openstack-manuals in Zanata. Thanks a lot! I have merged from openstack-manuals translations in stable-newton version to master and stable-ocata, and updated brief documentation translation plan for Pike cycle (aims to translate stable-ocata install-guide, common, network-guide, and some master documents). For more concrete plan, I18n team will discuss Documentation translation plan & priority on later IRC meeting. With many thanks, /Ian Mariia Zlatkova wrote on 3/25/2017 2:36 AM: > The changes have been merged. Kudos to Andreas for all his reviews and > fixes! > > So core-reviewers can go ahead and merge now. > > On Fri, Mar 24, 2017 at 1:42 PM, Andreas Jaeger <aj(a)suse.com > <mailto:aj@suse.com>> wrote: > > On 2017-03-24 11:24, Mariia Zlatkova wrote: > > Hi all, > > We have the stable/ocata branch created. Brian has prepared the > > following changes to master: > > > > https://review.openstack.org/#/c/449383 > <https://review.openstack.org/#/c/449383> > > <https://review.openstack.org/#/c/449383 > <https://review.openstack.org/#/c/449383>> > > https://review.openstack.org/#/c/449385 > <https://review.openstack.org/#/c/449385> > > <https://review.openstack.org/#/c/449385 > <https://review.openstack.org/#/c/449385>> > > > > I'm going to make the required changes to stable/ocata. So > please do not > > approve any changes until those are in. > > good idea, thanks! > > Note that since we tagged again, the release scripts added comments to > lots of closed bugs - you can ignore them... > > Andreas > -- > Andreas Jaeger aj(a){suse.com <http://suse.com>,opensuse.org > <http://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 > > > > > -- > *Mariia Zlatkova* > Technical Writer | Mirantis, Kharkiv > www.mirantis.com <http://www.mirantis.com> > > > > _______________________________________________ > OpenStack-docs mailing list > OpenStack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

1 0

Pike dashboard translation plan & priority are updated in Zanata Dashboard
by Ian Y. Choi 23 Mar '17

23 Mar '17

Hello all translators and language coordinators, Pike dashboard translation plan and priority are updated in Zanata Dashboard : https://translate.openstack.org . Some notes regarding this update are: - I have merged all dashboard translations for projects from stable-ocata to master in https://translate.openstack.org/version-group/view/ocata-dashboard-translat… . - For such merge purposes, translations in master version is being overwitten by translations in stable-ocata version, since I18n team prioritized primarily on Ocata version. - Pike dashboard translations group is available at : https://translate.openstack.org/version-group/view/pike-dashboard-translati… . Tripleo-ui has been added to Pike dashboard translations group. - I have checked that Docs team will create stable/ocata branch soon. I will follow to create stable-ocata version in Zanata, do merge stuffs later, and announce through I18n mailing list. With many thanks, /Ian

1 0