- OpenStack-I18n - lists.openstack.org

Ocata dashboard translation: 100% and a feature request for Zanata
by Will Zhou 13 Feb '17

13 Feb '17

Hi Ian and Daisy, With the contribution of Simplified Chinese translators, *vuuv, liujunpeng, sunanchen, zhugaoxiao *and* xiangbinbin*, Ocata dashboard translation reaches 100%! Great thanks for their dedication:) As you are working with Zanata team for bug fix and feature implementation, here is a tiny feature request for the team from vuuv (Thank vuuv for bring out this request). We need to have Zanata tool to validate symbols ```` and its completion. For example, ``templateName`` from the string <https://translate.openstack.org/webtrans/translate?project=murano-dashboard…> as below: - ``ref(templateName [, parameterName] [, idOnly])`` YAQL function was added to UI definition DSL. This function evaluates template ``templateName`` and fixes the result in parameters under ``parameterName`` key (or ``templateName`` if the second parameter was omitted). Then it generates object ID and places it into ``?/id`` field. On the first use of ``parameterName`` or if ``idOnly`` is ``false`` the function will return the whole object structure. On subsequent calls or if ``idOnly`` is ``true`` it will return the ID that was generated upon the first call. Thus the function brings ability to reference single object several times. We need to tool to check the translation ``templateName`` and make sure it consists two symbols '``'. If there is no '`' or only one '``', like *templateNam* or *``templateNam*, the tool will prompt errors. Thanks and have a nice weekend:) -- --------------------------------------------- 周正喜 Mobile: 13701280947 WeChat: 472174291

2 1

Korean translation broken for training-guides
by Andreas Jaeger 13 Feb '17

13 Feb '17

Could somebody fix Korean translations, please? http://logs.openstack.org/periodic/training-guides-propose-translation-upda… contains: ++ msgfmt --statistics -o /dev/null doc/upstream-training/source/locale/ko_KR/LC_MESSAGES/upstream-training.po 2017-02-12 08:31:46.980964 | + trans='doc/upstream-training/source/locale/ko_KR/LC_MESSAGES/upstream-training.po:4871: '\''msgid'\'' and '\''msgstr'\'' entries do not both end with '\''\n'\'' 2017-02-12 08:31:46.981085 | msgfmt: found 1 fatal error thanks, 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 1

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

10 Feb '17

Team team team team team, Welcome to my first edition of What's up, Doc? Firstly, I just want to thank everyone who supported me when I announced I would like to run for manuals PTL. Although I ran the election uncontested (like the beginning of all good dictatorships), it was wonderful to receive messages of support from everyone. I’ve slowly been ramping up and getting used to the mass influx of emails. Turns out I’m really good at sending out emails with the incorrect time and/or date. Big thanks to Andreas for informing me the next 9th of January will be in 2020. Without further ado, let's get down to business! We have a very short window now between Ocata and the start of Pike, and we still have quite a number of things left to achieve. - If anyone has time to dedicate to Install Guide testing - please sign up (links below). Thanks to those who have already volunteered to help Lana out! - As per my email yesterday, I'd love to see some people out there smashing bugs! (links also below, and more info in the meeting minutes from yesterday). == Progress towards Ocata == * 12 days to go! * Closed 256 bugs so far. We have 128 open bugs left: https://bugs.launchpad.net/openstack-manuals/+bugs * Release tasks are being tracked here: https://wiki.openstack.org/wiki/Documentation/OcataDeliverables * Install Guide testing is being tracked here: https://wiki.openstack.org/wiki/Documentation/OcataDocTesting == The Road to PTG in Atlanta == Docs is a horizontal project, so our sessions will run across the Monday and Tuesday of the event. We will be combining the docs event with i18n, so translators and docs people will all be in the room together. Everyone welcome! Conversation topics for Docs and i18n here: https://etherpad.openstack.org/p/docs-i18n-ptg-pike 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/ == Specialty Team Reports == API - Anne Gentle: The trove API docs are incomplete after migration, and a user reported the bug to the ML. Anne to log the missing clustering API info. Alex and Anne to meet with the app dev community manager at the Foundation to talk about goals for developer.openstack.org. The NFV Orchestration (tacker) team landed their API ref this week. Configuration Reference and CLI Reference - Tomoyuki Kato: CLI Reference: Updated some CLI references. Added aodhclient. Config Reference: Start working on Ocata updates. High Availability Guide - Ianeta Hutchinson: Sent a message to the ML looking for people interested in helping out on the HA guide for Pike. Planning for the PTG as I can’t attend. Hypervisor Tuning Guide - Blair Bethwaite: No report this week Installation guides - Lana Brindley: Landing page review: https://review.openstack.org/#/c/425821/12. Install guide testing is well underway. Networking Guide - John Davidge: Working on organising a Networking Guide working group with the neutron team at the PTG. Also been smashing bugs. Operations and Architecture Design guides - Darren Chan: Darren and Ben are working on an action plan for the Arch Guide to be worked on during Pike to get the current draft guide published. Security Guide - Nathaniel Dillon: Moved the sec-guide bugs to the sec team Launchpad. Sec and doc team to coordinate and come up with action plan for the future of the sec guide at the PTG. Training Guides - Matjaz Pancur: No report this week Training labs - Pranav Salunke, Roger Luethi: Training-labs has a rough, but working Ocata patch. Issues we found are noted on the Etherpad as you requested. We should be able to release within a week or two after Ocata is official. User guides - Joseph Robinson: The legacy command changes have gone through well this release, and the next steps is to check with the nova, neutron, cinder, and glance teams on the status of some specific project commands == Doc team meeting == Our next meeting will be on Thursday 23 February at 2100 UTC in #openstack-meeting-alt. We will not be skipping the meeting in favor for the PTG as the docs sessions are on the Mon-Tues and I would love the opportunity to immediately report back to people who cannot attend. 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 All round badass and supernaturally good potato peeler IRC: asettle Twitter: dewsday

1 0

[StringFreeze] *stable-ocata* has been created in Zanata
by Ilya Alekseyev 10 Feb '17

10 Feb '17

Hello language coordinators & translators! On the last week, I18n team checked feature freeze status and also created a stable version: *stable-ocata* in Zanata. Now 1-2 weeks are left to Ocata release [1], and I would like to inform that ideally I18n team needs to focus to review translated strings in stable-ocata versions. According to the dashboard on translate.openstack.org, our targeted priorities are as the followings: - Dashboard - Horizon (High) - Dashboard Authorization Page (High) - neutron-lbaas-dashboard (High) - Trove Dashboard (Medium) - Sahara Dashboard (Medium) - Murano Dashboard (Low) - Magnum UI (Low) - Designate Dashboard (Low) If you have questions, feel free to ask through openstack-i18n(a)lists.openstack.org mailing list or find many I18n members on Freenode #openstack-i18n channel. Thank you all! [1] https://releases.openstack.org/ocata/schedule.html Ilya Alekseyev (IRC: adiantum), StringFreeze Manager in Ocata cycle Ian Y. Choi (IRC: ianychoi), I18n Ocata PTL

3 2

[Bug 1661454] Re: Inadequate Japanese translation for "Browse" on App Catalog tab
by Eddie Ramirez 08 Feb '17

08 Feb '17

Invalidating this bug. ** Changed in: horizon 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/1661454 Title: Inadequate Japanese translation for "Browse" on App Catalog tab Status in OpenStack Dashboard (Horizon): Invalid Status in openstack i18n: New Bug description: Japanese translation for "Browse" is not adequate for this context. It is currently translated into 探索, but it should be 参照 or ブラウズ, but unable to locate the string from Zanata To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1661454/+subscriptions

1 0

[Bug 1631350] [NEW] manila-ui project translations into runnian are very confusing
by Valeriy Ponomaryov 06 Feb '17

06 Feb '17

Public bug reported: Translation of texts in "manila-ui" project into russian has lots of confusing places. Details can be found here: https://review.openstack.org/#/c/379994/5/manila_ui/locale/ru/LC_MESSAGES/d… ** Affects: openstack-i18n Importance: Undecided Status: New ** Description changed: - Translation of text in "manila-ui" project into russian has lots of + Translation of texts in "manila-ui" project into russian has lots of confusing places. Details can be found here: https://review.openstack.org/#/c/379994/5/manila_ui/locale/ru/LC_MESSAGES/d… -- 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/1631350 Title: manila-ui project translations into runnian are very confusing Status in openstack i18n: New Bug description: Translation of texts in "manila-ui" project into russian has lots of confusing places. Details can be found here: https://review.openstack.org/#/c/379994/5/manila_ui/locale/ru/LC_MESSAGES/d… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1631350/+subscriptions

2 1

[Bug 1556887] Re: Themes setting is not translated
by Ian Y. Choi 06 Feb '17

06 Feb '17

Thanks a lot for the comment with Chinese details, Alex! ** Changed in: openstack-i18n Status: Fix Committed => 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/1556887 Title: Themes setting is not translated Status in OpenStack Dashboard (Horizon): Invalid Status in openstack i18n: Invalid Bug description: The theme string should be translated. The screen shot is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1556887/+subscriptions

1 0

[Bug 1633376] [NEW] 安装和配置 in Installation Guide
by johnson 06 Feb '17

06 Feb '17

Public bug reported: http://docs.openstack.org/liberty/zh_CN/install-guide-rdo/keystone-install.… “安全并配置组件” 应该是 “安装并配置组件” ----------------------------------- Release: 0.1 on 2016-10-02 17:09 SHA: 620d348d56f41b8f87fb48a1195f9228df451ae0 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/liberty/zh_CN/install-guide-rdo/keystone-install.… ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- 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/1633376 Title: 安装和配置 in Installation Guide Status in openstack i18n: New Bug description: http://docs.openstack.org/liberty/zh_CN/install-guide-rdo/keystone-install.… “安全并配置组件” 应该是 “安装并配置组件” ----------------------------------- Release: 0.1 on 2016-10-02 17:09 SHA: 620d348d56f41b8f87fb48a1195f9228df451ae0 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/liberty/zh_CN/install-guide-rdo/keystone-install.… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1633376/+subscriptions

2 1

[Bug 1649188] [NEW] 网络（neutron）概念 in Installation Guide
by xiaohan 06 Feb '17

06 Feb '17

Public bug reported: The Chinese should be "不像其他的网络那样，外部网络不仅仅是一个定义的虚拟网络" instead of "不想其他的网络那样，外部网络不仅仅是一个定义的虚拟网络" ----------------------------------- Release: 0.1 on 2016-12-09 09:29 SHA: 0a21733bd348d21d7eddb0fcab97b09cfac30afa Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/neutron-concepts.h… ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- 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/1649188 Title: 网络（neutron）概念 in Installation Guide Status in openstack i18n: New Bug description: The Chinese should be "不像其他的网络那样，外部网络不仅仅是一个定义的虚拟网络" instead of "不想其他的网络那样，外部网络不仅仅是一个定义的虚拟网络" ----------------------------------- Release: 0.1 on 2016-12-09 09:29 SHA: 0a21733bd348d21d7eddb0fcab97b09cfac30afa Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/neutron-concepts.h… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1649188/+subscriptions

2 1

[Bug 1642120] [NEW] OpenStack API文档 in Openstack-API-Documentation
by yindesheng 06 Feb '17

06 Feb '17

Public bug reported: 计算服务 API v1 应该是: 计算服务 API (微版本) ----------------------------------- Release: 0.1 on 2016-11-15 16:49 SHA: bbf08d36d73d2c17487859c0f32ac283cf355e78 Source: http://git.openstack.org/cgit/openstack/api-site/tree/api-quick-start/sourc… URL: http://developer.openstack.org/zh_CN/api-guide/quick-start/ ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: api-site -- 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/1642120 Title: OpenStack API文档 in Openstack-API-Documentation Status in openstack i18n: New Bug description: 计算服务 API v1 应该是: 计算服务 API (微版本) ----------------------------------- Release: 0.1 on 2016-11-15 16:49 SHA: bbf08d36d73d2c17487859c0f32ac283cf355e78 Source: http://git.openstack.org/cgit/openstack/api-site/tree/api-quick-start/sourc… URL: http://developer.openstack.org/zh_CN/api-guide/quick-start/ To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1642120/+subscriptions

2 1

[Bug 1652235] [NEW] 计算服务概览 in Installation Guide
by zhang-qinghuai 06 Feb '17

06 Feb '17

Public bug reported: in the following url,there have a translation bug, can you check and correction it, Thank you very much. http://docs.openstack.org/mitaka/zh_CN/install-guide- rdo/common/get_started_compute.html ``nova-conductor``模块媒介作用于``nova-compute``服务与数据库之间。它排除了由``nova-compute``服务对云数据库的直接访问。nova-conductor模块可以水平扩展。但是，不要将它部署在运行``nova-conductor``服务的主机节点上。参考Configuration Reference Guide <http://docs.openstack.org/mitaka/config-reference/compute/conductor.html>`__。 ==> ``nova-conductor``模块媒介作用于``nova-compute``服务与数据库之间。它排除了由``nova-compute``服务对云数据库的直接访问。nova-conductor模块可以水平扩展。但是，不要将它部署在运行``nova-compute``服务的主机节点上。参考Configuration Reference Guide <http://docs.openstack.org/mitaka/config-reference/compute/conductor.html>`__。 ----------------------------------- Release: 0.1 on 2016-12-22 09:41 SHA: 50603e48e497eef2e34741d8e41f4a99cc336b98 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/common/get_started… ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- 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/1652235 Title: 计算服务概览 in Installation Guide Status in openstack i18n: New Bug description: in the following url,there have a translation bug, can you check and correction it, Thank you very much. http://docs.openstack.org/mitaka/zh_CN/install-guide- rdo/common/get_started_compute.html ``nova-conductor``模块媒介作用于``nova-compute``服务与数据库之间。它排除了由``nova-compute``服务对云数据库的直接访问。nova-conductor模块可以水平扩展。但是，不要将它部署在运行``nova-conductor``服务的主机节点上。参考Configuration Reference Guide <http://docs.openstack.org/mitaka/config-reference/compute/conductor.html>`__。 ==> ``nova-conductor``模块媒介作用于``nova-compute``服务与数据库之间。它排除了由``nova-compute``服务对云数据库的直接访问。nova-conductor模块可以水平扩展。但是，不要将它部署在运行``nova-compute``服务的主机节点上。参考Configuration Reference Guide <http://docs.openstack.org/mitaka/config-reference/compute/conductor.html>`__。 ----------------------------------- Release: 0.1 on 2016-12-22 09:41 SHA: 50603e48e497eef2e34741d8e41f4a99cc336b98 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/common/get_started… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1652235/+subscriptions

2 1

[Bug 1655540] [NEW] 网络选项2：私有网络 in Installation Guide
by Jimmy Li 06 Feb '17

06 Feb '17

Public bug reported: 原文为: Therefore, replace OVERLAY_INTERFACE_IP_ADDRESS with the management IP address of the controller node. 翻译为: 因此，将``OVERLAY_INTERFACE_IP_ADDRESS``替换为计算节点的管理网络的IP地址错误为: 计算节点应该为: 控制节点 ----------------------------------- Release: 0.1 on 2016-12-22 09:41 SHA: 50603e48e497eef2e34741d8e41f4a99cc336b98 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/neutron-controller… ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- 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/1655540 Title: 网络选项2：私有网络 in Installation Guide Status in openstack i18n: New Bug description: 原文为: Therefore, replace OVERLAY_INTERFACE_IP_ADDRESS with the management IP address of the controller node. 翻译为: 因此，将``OVERLAY_INTERFACE_IP_ADDRESS``替换为计算节点的管理网络的IP地址错误为: 计算节点应该为: 控制节点 ----------------------------------- Release: 0.1 on 2016-12-22 09:41 SHA: 50603e48e497eef2e34741d8e41f4a99cc336b98 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/neutron-controller… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1655540/+subscriptions

2 1

[Bug 1645743] [NEW] unlocalized string in horizon
by Sai Kiran 06 Feb '17

06 Feb '17

Public bug reported: In simplified Chinese locale "Flavors" string is not localized in horizon. Admin >> System >> Flavors Openstack Stable/Mitaka version ** Affects: openstack-i18n Importance: Undecided Assignee: Sai Kiran (saikiran) Status: New ** Tags: horizon ** Attachment added: "Flavor_horizon.jpg" https://bugs.launchpad.net/bugs/1645743/+attachment/4784711/+files/Flavor_h… ** Changed in: openstack-i18n Assignee: (unassigned) => Sai Kiran (saikiran) -- 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/1645743 Title: unlocalized string in horizon Status in openstack i18n: New Bug description: In simplified Chinese locale "Flavors" string is not localized in horizon. Admin >> System >> Flavors Openstack Stable/Mitaka version To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1645743/+subscriptions

2 1

Related translation documents
by Alex Eng 05 Feb '17

05 Feb '17

Hi, Any knows the related file/document in Zanata with issue reported in https://bugs.launchpad.net/openstack-i18n/+bug/1645743 ? -- Alex Eng

1 0

Invalid Horizon PO fzh_CN file
by Andreas Jaeger 03 Feb '17

03 Feb '17

From: http://logs.openstack.org/periodic/horizon-propose-translation-update/ec054… : 2017-02-02 08:01:29.323053 | + msgfmt --check-format -o /dev/null openstack_dashboard/locale/zh_CN/LC_MESSAGES/django.po 2017-02-02 08:01:29.349022 | openstack_dashboard/locale/zh_CN/LC_MESSAGES/django.po:7094: a format specification for argument 'req' doesn't exist in 'msgstr[0]' 2017-02-02 08:01:29.349109 | msgfmt: found 1 fatal error Could somebody from the Chinese team investigate and fix, please? 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 2

[Bug 1661454] Re: Inadequate Japanese translation for "Browse" on App Catalog tab
by Ian Y. Choi 03 Feb '17

03 Feb '17

** Tags added: i18n ** 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/1661454 Title: Inadequate Japanese translation for "Browse" on App Catalog tab Status in OpenStack Dashboard (Horizon): New Status in openstack i18n: New Bug description: Japanese translation for "Browse" is not adequate for this context. It is currently translated into 探索, but it should be 参照 or ブラウズ, but unable to locate the string from Zanata To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1661454/+subscriptions

1 0

[I18n] IRC Meeting remainder: December 22nd at 13:00 UTC
by Ian Y. Choi 02 Feb '17

02 Feb '17

Hello all, I18n team is having our next meeting on December 22nd (Thursday) at 13: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 :) Note that it will be the last I18n IRC meeting in this year. Hope to see more participants on the meeting and let's wrap up I18n activities in this year. With many thanks, /Ian

3 6

German Mitaka Installation Guides
by Kato, Tomoyuki 02 Feb '17

02 Feb '17

Hi German team, Could you check the Mitaka Installation Guides? https://review.openstack.org/#/c/427596/1 Thanks, KATO Tomoyuki

3 4

Re: [OpenStack-I18n] [openstack-dev] Supporting our global community
by Ian Y. Choi 31 Jan '17

31 Jan '17

Hello, Thanks a lot for this important message. As an I18n team contributor and an non-US citizen, I quite agree with the note. FYI: ujuc - I18n Korean language coordinator translated the message into Korean language => https://ujuc.kr/openstack-%EB%B2%88%EC%97%AD-supporting-our-global-communit… With many thanks, /Ian Jonathan Bryce wrote on 1/30/2017 3:34 AM: > OpenStack is a global open source community. The OpenStack Foundation serves members in 180 countries focused on advancing the capabilities and accessibility of open infrastructure everywhere. We fundamentally believe diversity and collaboration are a powerful force for innovation, and it has been amazing to see the product of tens of thousands of people around the world over the last 6+ years. > > Lauren, Mark and I disagree with the executive order issued by President Trump that targets individuals from 7 countries. The order restricts the travel and movement of people in a discriminatory way that results in a restriction on access to talent and ideas. It is still unclear how the policies will play out and be enforced, but we will be watching, advocating for and supporting our community members to the best of our ability. > > This executive order will not impact the governance of the Foundation or the way the community operates globally. We will continue to support user groups and community members that are active in the seven countries named by the executive order, alongside our 120+ user groups around the world. However, we have two scheduled events in the United States within the next six months that will attract a global audience: the PTG (Project Teams Gathering) in Atlanta, Feb 20-24, a smaller event that will bring together hundreds of upstream contributors, and the OpenStack Summit in Boston, May 8-11, our larger event that happens every six months. > > This executive order could impact some community members' ability to travel to Atlanta and Boston, but unfortunately it is too late at this point to change the location of these events. The following three OpenStack Summits, however, are now scheduled to occur outside of the United States. The next Summit will be in November 2017 in Sydney, Australia and we are working to finalize the details so we can announce the following two Summit locations soon. > > We’ve already heard from one community member, Mohammed Naser, who is concerned that his plans to travel from Canada to Atlanta to attend the PTG may be restricted, simply because he a dual citizen of Canada and Iraq. Mohammed has been contributing code to OpenStack since 2011 and is the CEO and Founder of Vexxhost. Blocking his travel would serve no purpose and rob the community of a valuable contributor during an important event. If you are concerned about the impact or have any questions, please don't hesitate to reach out to me at jonathan(a)openstack.org. > > Political actions like this highlight the importance of our collective values. The Four Opens, the founding principles of our community, exist to ensure the free flow of talent and ideas, across geographic, national, organizational or other lines that might divide us. We believe in humanity. We believe in opportunity. We believe in the power of collaboration across borders, and we will continue to carry forward our mission. > > We also posted this online: https://www.openstack.org/blog/2017/01/supporting-our-global-community/ > > Jonathan Bryce > Mark Collier > Lauren Sell > > > > __________________________________________________________________________ > 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

[openstack-doc] [i18n] PTG planning
by Alexandra Settle 31 Jan '17

31 Jan '17

Hi everyone, I would just like to remind everyone of our docs and i18n planning etherpad for Pike: https://etherpad.openstack.org/p/docs-i18n-ptg-pike The PTG is now less than a month away, and it would be great for everyone to propose their topics. Do not forget that we will be including remote attendees if you would like to speak on a particular topic, or get involved in a particular conversation ☺ Do not hesitate to contact me or Ian if you have any questions. Thanks, Alex

2 1

[I18n] PTL Candidacy for Pike
by Ian Y. Choi 30 Jan '17

30 Jan '17

Hello, I am writing to announce my candidacy for I18n Pike PTL. To retrospect my activities in Ocata cycle, my overall feeling is that Ocata cycle is really short. In fact, I acknowledge that most of the action items I wrote in [1] are still on-going or have not completed yet. Nevertheless, the followings are some memorable activities which I have involved with and also would like to continue during upcoming Pike cycle: * Well summarized action items from Ocata Design Summit [2] * IRC meeting time change accordingly with two bi-weekly schedules * Publicizing IRC meeting announcement and logs [3] * On-going effort on Zanata upgrade with Xenial with infra team * Clearer communication on translation imports and criteria [4, 5] * Landing page updates for translated documents * Co-participation in Pike PTG with Documentation team [6] I am seeing that there are many upstream translations, and many I18n team members participate with great and kind help. I really appreciate their contributions and also the help from especially Infrastructure team, Documentation team, and Zanata development team members. I believe that I am able to continue my effort to finish what I wrote in [1] and make for better I18n. Please support and encourage me again. With many thanks, /Ian [1] https://git.openstack.org/cgit/openstack/election/plain/candidates/ocata/I1… [2] https://etherpad.openstack.org/p/barcelona-i18n-meetup [3] https://wiki.openstack.org/wiki/I18N/MeetingLogs [4] http://docs.openstack.org/developer/i18n/reviewing-translation-import.html [5] http://docs.openstack.org/developer/i18n/infra.html [6] https://www.openstack.org/ptg

3 2

2nd UNOFFICIAL Horizon translation checksite
by Ian Y. Choi 29 Jan '17

29 Jan '17

Hello translators, Although I initially set Horizon translation checksite higher priority during Ocata cycle, it seems that official Horizon translation checksite implementation requires more effort to realize appropriate procedures and implementation details. I think I can start to investigate on this again after Zanata upgrade is successfully finished. Nevertheless, I acknowledge that many translators want Horizon translation checksite. After the discussion on the last IRC meeting with Frank, he kindly prepared a temporary translation checksite for Ocata cycle. (Let's express appreciation by replying to this message :) Thanks a lot, Frank!) This implementation is based on what I18n team did a midcycle virtual spring about one year ago [1] and also what Akihiro-san kindly shared with details [2, 3]. Please read what Frank shared with details below, feel free to test it, and share your feedback through this mailing list or via IRC. Note that since is unofficial, it might not work for maintenance or some technical issues, and also it might not work after Ocata is released. With many thanks, /Ian [1] http://lists.openstack.org/pipermail/openstack-i18n/2016-February/001790.ht… [2] http://lists.openstack.org/pipermail/openstack-i18n/2016-September/002420.h… [3] http://docs.openstack.org/developer/i18n/check_translation.html#openstack-d… -------- Original Message -------- Subject: temp translation checksite Date: Thu, 26 Jan 2017 23:24:41 +0100 From: Frank Kloeker <eumel(a)arcor.de> To: Ian Y. Choi <ianyrchoi(a)gmail.com> Hi Ian, translation checksite is temporaty online: [1] accounts: admin/password demo/password Unfortunately Neutron Lbaas module has a bug and automatically DevStack installation will fail [2] I disabled the plugin manually and it works for the moment. But it's no way for an automatic bootstrapping in OpenStack Infra. Also some Javascripts are broken. Don't know why, it's fetched from current master branch. I installed also the puppet things [3], so translation files will sync every 30 minutes from Zanata. Due the recompiling of the files, the dashboard is a little bit slow on the first resquest. I tried some caching [4] but this could delay the refresh of the new translated side. Will see. kind regards Frank [1] http://i18n.ref.app.telekomcloud.com [2] https://bugs.launchpad.net/devstack/+bug/1540328 [3] https://github.com/eumel8/translation_checksite/tree/dev/0.3 [4] http://docs.openstack.org/admin-guide/dashboard-sessions.html

4 3

Re: [OpenStack-I18n] [OpenStack-docs] [openstack-docs] Archiving documentation
by Ian Y. Choi 27 Jan '17

27 Jan '17

Hello, Andreas Jaeger wrote on 1/25/2017 4:33 PM: > On 2017-01-25 05:39, Tom Fifield wrote: >> I'd suggest that anyone on the infrastructure team would be happy to >> perform this copy (and have the access necessary to do so. Just drop a >> mail to openstack-infra(a)lists.openstack.org (or in #openstack-infra) and >> ask to copy the icehouse dir from 'docs-archived' to 'docs.o.o'. > I can coordinate that copying - but before I do, I'd like to see a plan. > > Btw. copying the complete icehouse dir is wrong, I don't want to copy > the Install Guide as you said as well. So, what should be copied exactly? > > Moving to docs-archived just a single directory right now is the wrong > way: It still breaks existing URLs, why not use /icehouse? Then, which > other directories to copy over? How do you want to make these archived > versions available - there's no /icehouse or /docs-archived index page. > What are we doing about translations of the documents? I would like to kindly ask doc team members to also consider archiving translated documents. IMHO, translated documents may have their values although the documents are EOL, since - Translation contributions for documents starts after the documents are released. - Due to a kind of nature for I18n team, some translated documents might not be released (e.g., one translated install-guide for Liberty - but no Mitaka nor Newton translated install-guide for the same language). Recently, one bug has been reported to openstack-i18n launchpad but I have just forwarded to openstack-manuals: https://bugs.launchpad.net/openstack-manuals/+bug/1659167 , since the actual tox run is accomplished in openstack-manuals repository. Would not we fix this issue since Liberty is EOL? Or we need to fix although it is EOL but for translated documents? Now I am a little bit inclined to fix the bug, but I am open to follow Doc team's opinion :) With many thanks, /Ian > > Andreas

3 3

What's Up, Doc? Farewell edition
by Lana Brindley 27 Jan '17

27 Jan '17

Hi everyone, I must confess, I'm feeling a little sad. This is my very last What's Up, Doc. Next week, I'll be handling the Docs PTL mantle to Alexandra Settle. I've worked with Alex in varying capacities over many years, and I have no doubt that she will be a fabulous PTL. I'm really looking forward to working with her, and seeing what new directions she's able to take this team. I want to take this opportunity to thank each and every one of you for your continued support and encouragement over the last two years (and almost-four releases!). I have had an absolute ball doing this job, and it's all because of the amazing people I get to work with every day. Of course, I'm not going anywhere just yet. I will stay on as a core contributor, and continue to help out as much as I can. In the meantime, we have a release to get out the door! We now only have 26 days until Ocata is released, please keep an eye on the docs mailing list for updates, and consider getting your hands dirty with some Install Guide testing: https://wiki.openstack.org/wiki/Documentation/OcataDocTesting == Progress towards Ocata == 26 days to go! Closed 211 bugs so far. Release tasks are being tracked here: https://wiki.openstack.org/wiki/Documentation/OcataDeliverables Install Guide testing is being tracked here: https://wiki.openstack.org/wiki/Documentation/OcataDocTesting == The Road to PTG in Atlanta == Event info is available here: http://www.openstack.org/ptg Purchase tickets here: https://pikeptg.eventbrite.com/ Docs is a horizontal project, so our sessions will run across the Monday and Tuesday of the event. We will be combining the docs event with i18n, so translators and docs people will all be in the room together. Conversation topics for Docs and i18n here: https://etherpad.openstack.org/p/docs-i18n-ptg-pike Also, a quick note that the CFP and ticket sales for *Boston in May* are now open: https://www.openstack.org/summit/boston-2017/call-for-presentations/ == Speciality Team Reports == No speciality team reports this week, as we didn't have quorum for the docs meeting. == Doc team meeting == Our next meeting will be on Thursday 9 February at 2100 UTC in #openstack-meeting-alt Meeting chair will be Alexandra Settle. For more meeting details, including minutes and the agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#27_January_2017 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

3 3

[Bug 1659726] [NEW] Fix wrong verb
by EunSeop Shin 27 Jan '17

27 Jan '17

Public bug reported: At http://docs.openstack.org/developer/i18n/release_management.html worng verb used second note section ** Affects: openstack-i18n Importance: Undecided Assignee: EunSeop Shin (vi01et03) Status: In Progress ** Changed in: openstack-i18n Assignee: (unassigned) => EunSeop Shin (vi01et03) ** Changed in: openstack-i18n Status: New => In Progress -- 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/1659726 Title: Fix wrong verb Status in openstack i18n: In Progress Bug description: At http://docs.openstack.org/developer/i18n/release_management.html worng verb used second note section To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1659726/+subscriptions

2 1

[Bug 1659167] [NEW] OpenStack Installation Guide for Ubuntu in Installation Guide
by Ngoc-Tu Chau 27 Jan '17

27 Jan '17

Public bug reported: Problem: - Duplicate menu on Korea language: Normal Openstack install guild + Defcon menu (Korean - Liberty version only, this does not occur on English - Liberty verion). - Also, the Next button on 메시지 큐 (message queue) page redirects user to debconf page. ----------------------------------- Release: 0.1 on 2016-11-24 07:53 SHA: cc8b39934de4de69e5235ca8e5c4d4b567d0f418 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/liberty/ko_KR/install-guide-ubuntu/index.html ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- 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/1659167 Title: OpenStack Installation Guide for Ubuntu in Installation Guide Status in openstack i18n: New Bug description: Problem: - Duplicate menu on Korea language: Normal Openstack install guild + Defcon menu (Korean - Liberty version only, this does not occur on English - Liberty verion). - Also, the Next button on 메시지 큐 (message queue) page redirects user to debconf page. ----------------------------------- Release: 0.1 on 2016-11-24 07:53 SHA: cc8b39934de4de69e5235ca8e5c4d4b567d0f418 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/liberty/ko_KR/install-guide-ubuntu/index.html To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1659167/+subscriptions

2 1

networking-guide in master.
by Cloud Suhartono 27 Jan '17

27 Jan '17

One networking-guide document is in the stable-newton directory. Our team have translated it into Bahasa Indonesia reaching 100%. Now,our team are going to proceed the similar document but in the master directory, while this document having reached up 6% translated. How to made it done effectively and efficiently ? Thank you for your guides, /Suhartono & Indonesian Team.

2 2

[Bug 1659478] [NEW] i18n/doc/source/about.rst typo report
by koain 26 Jan '17

26 Jan '17

Public bug reported: It seems that the word "convenstions" is a typo. ** Affects: openstack-i18n Importance: Undecided Assignee: koain (koain) Status: In Progress ** Changed in: openstack-i18n Assignee: (unassigned) => koain (koain) -- 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/1659478 Title: i18n/doc/source/about.rst typo report Status in openstack i18n: In Progress Bug description: It seems that the word "convenstions" is a typo. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1659478/+subscriptions

2 1

[StringFreeze] Soft StringFreeze starts!
by Ilya Alekseyev 25 Jan '17

25 Jan '17

Dear language coordinators & translators! Only four weeks left before Ocata release [1] and I would like to inform you that Soft StringFreeze period has come. Language teams need to focus on Horizon and Horizon-related projects before all translated strings will be packaged for upcoming release. According to the dashboard on https://translate.openstack.org, our targeted priorities look as follows: - Dashboard - Horizon (High) - Dashboard Authorization Page (High) - neutron-lbaas-dashboard (High) - Trove Dashboard (Medium) - Sahara Dashboard (Medium) - Murano Dashboard (Low) - Magnum UI (Low) - Designate Dashboard (Low) All of those and more additional target projects grouped in [2] in *master* branch and PTL (@ianychoi) will check feature freeze status on projects listed above. He will create a stable version: *stable-ocata* in Zanata for the target projects this week. Although the stable version has not been created yet, but it is highly encouraged to translate those projects from now, since StringFreeze periods are relatively short during Ocata cycle. If you have questions, feel free to ask through openstack-i18n(a)lists.openstack.org mailing list or ask I18n members on Freenode #openstack-i18n channel. Thank you all for your contribution! [1] https://releases.openstack.org/ocata/schedule.html [2] https://translate.openstack.org/version-group/view/ocata-dashboard-translat… Ilya Alekseyev (IRC: adiantum), StringFreeze Manager in Ocata cycle Ian Y. Choi (IRC: ianychoi), I18n Ocata PTL

3 3

[openstack-docs][i18n] PTG etherpad
by Alexandra Settle 23 Jan '17

23 Jan '17

Hi everyone, Just a quick reminder that we have our etherpad up for our joint PTG planning efforts: https://etherpad.openstack.org/p/docs-i18n-ptg-pike If you are UNABLE to attend the PTG, but would still like to discuss an idea or concern with the team, I have included a third heading for those that would remotely like to attend a session to talk. Please include your name and topic (if applicable) to the list. We would like to include as many participants as we can, and will endeavor to accommodate all if possible. At the moment we are just gathering interest. Planning to include those that are remote can commence after the PTL elections and closer to the date of the PTG. If you have any questions, do not hesitate to reach out to me. Thank you, Alex

1 0

[OpenStack-docs] [Docs] PTL Candidacy for Pike
by Alexandra Settle 20 Jan '17

20 Jan '17

Hi everyone, I am announcing my candidacy for the OpenStack manuals PTL position. Some of you may know me from the 2014 Paris summit where I cooed like a pigeon [1] in a panel discussion, but I hope that most of you will know me from my documentation work across OpenStack, specifically the OpenStack manuals project and OpenStack-Ansible contributions. I have been an active contributor to OpenStack manuals since the beginning of 2014, and have been a core member since early 2015. Over these last 3 years, I was privileged to be a part of the sprint team that authored the first edition of the OpenStack Architecture Design Guide [2] (and the subsequent swarm team that fixed it up), the team that converted the manuals from XML to RST, the specialty team that worked on the creation and curation of the Contributor Guide, and the release management team for Ocata. I also worked with the OpenStack Infra team to create the new Deployment Guides section [3] at docs.openstack.org. I regularly work in different OpenStack projects. For example, I assisted the Swift team to curate the Swift Ops Runbook [4], and have been helping the OpenStack-Ansible team rework their documentation [5]. I am passionate about our documentation, our community, and our team’s involvement across OpenStack. OpenStack manuals was never organised and facilitated by a single person. Behind the scenes there are a great number of individuals who work hard to ensure our ship stays afloat. As PTL, I would like to continue this trend by: 1. Improving cross-project documentation liaison relationships a. Over the course of the Pike release, I plan to focus on developing better relationships with the cross-project liaisons and PTL’s of individual projects. I would like to promote and encourage developers and operators to get more involved in the development of OpenStack manuals content. OpenStack manuals takes on the responsibility of documenting and maintaining guides that represent the projects and tools developers and operators are working so hard to build and maintain. This written representation of their work is equally as important as the output. 2. Continuing with Lana’s bug-depletion legacy a. I plan to achieve this by reporting on completed bugs on a weekly basis and encouraging other contributors to report and fix one bug per week. When Lana first became PTL, she vowed to attack our enormous (and continuously growing) bug list. I'd like to continue this work, and will strive to find innovative ways to reduce our technical debt. If you would like to know more about how I will work to improve our community and the manuals, I’d love to chat with you more on IRC or via email. Coo coo, Alexandra Settle IRC: asettle Twitter: dewsday Email: a.settle(a)outlook.com [1] https://youtu.be/PtomtKeJ0tc?t=1783 [2] http://docs.openstack.org/arch-design/introduction-how-this-book-was-writte… [3] http://docs.openstack.org/project-deploy-guide/newton/ [4] http://docs.openstack.org/developer/swift/ops_runbook/index.html [5] https://blueprints.launchpad.net/openstack-ansible/+spec/osa-install-guide-…

1 0

Re: [OpenStack-I18n] [OpenStack-Infra] [I18n] Regarding Zanata upgrade plan to 3.9.6 with Xenial: Help is needed
by Ian Y. Choi 19 Jan '17

19 Jan '17

Hello, I would like to summarize the status for Zanata (translation platform) upgrade here from various but a little bit scattered results, and also ask some questions to infra team. - I18n team completed tests with current Zanata (3.7.3) with Xenial [1], but found one error mentioned in [2]. It seems that more memory size allocation for Zanata with Java 8 is needed. Could you upgrade the memory size for translate-dev server first to test again? - I remember that newer version of openstackid needs to be tested with translate-dev. So I have just uploaded this patch: https://review.openstack.org/#/c/419667/ . I18n team needs more tests, but I think it is a good time to change to openstackid-dev for such testing. Please ping me after openstackid-dev test with translate-dev is completed with no error :) - On last I18n team meeting, I18n team recognized that the backup would be so important. Is there more disks for such backup on translate-dev and translate.o.o server? And the approach implementing like [3] looks quite a good idea I think. Thanks, Frank! - Can I have root access to translate-dev and translate server? I really appreciate kind and continuous help for such Zanata upgrade, but sometimes I feel that considering priority like in [5] would be also a good idea. (Or somewhere on i18n-specs, which is not yet revised with items [6]). Since O cycle is rather short and also StringFreeze period is important for I18n team with translations, it seems that applying new Zanata version into production (I mean, translate.openstack.org) would be difficult. But, I really want to upgrade Zanata 3.9.6 with Xenial in translate-dev.openstack.org during O cycle and hope that all tests will be fine. Then I would like to have some discussions during PTG event including this topic :) [1] https://etherpad.openstack.org/p/i18n-zanata-test-for-translate-dev [2] http://lists.openstack.org/pipermail/openstack-i18n/2017-January/002643.html [3] https://review.openstack.org/#/c/419389/ [4] http://git.openstack.org/cgit/openstack-infra/system-config/tree/manifests/… [5] http://specs.openstack.org/openstack-infra/infra-specs/#priority-efforts [6] http://specs.openstack.org/openstack/i18n-specs/ With many thanks, /Ian Clark Boylan wrote on 12/8/2016 7:56 AM: > On Wed, Dec 7, 2016, at 01:08 AM, Frank Kloeker wrote: >> ----- Original Nachricht ---- >> Von: Clark Boylan <cboylan(a)sapwetik.org> >> An: "Ian Y. Choi" <ianyrchoi(a)gmail.com>, OpenStack Infra >> <openstack-infra(a)lists.openstack.org> >> Datum: 03.12.2016 00:37 >> Betreff: Re: [OpenStack-Infra] [I18n] Regarding Zanata upgrade plan to >> 3.9.6 >> with Xenial: Help is needed >> >>> On Tue, Nov 22, 2016, at 03:56 PM, Clark Boylan wrote: >>>> On Wed, Nov 9, 2016, at 09:49 AM, Ian Y. Choi wrote: >>>>> Hello, >>>>> >>>>> I18n team currently uses Zanata in translate.openstack.org so frequently >>>>> as an OpenStack translation platform. >>>>> I really appreciate great help from all contributors, especially infra >>>>> team members and Zanata development team >>>>> : >>>>> >>> http://specs.openstack.org/openstack-infra/infra-specs/specs/migrate_to_zana >>> ta.html >>>>> . >>>>> >>>>> Thanks to [1], the current deployed Zanata version is 3.7.3. >>>>> During about one year, there were some discussions for Zanata >>>>> enhancements in many i18n IRC meetings, >>>>> and especially Austin & Barcelona summits [2]. >>>>> Zanata development team members kindly listen to such enhancements, and >>>>> they are actively upgrading Zanata >>>>> with fixing bugs and incorporating cool features, which are very helpful >>>>> for translators. >>>>> >>>>> One main obstacle for upgrading Zanata (as far as I know) was that newer >>>>> versions of Zanata requires Java 8, >>>>> but it is not default on Trusty. To upgrade Zanata, upgrading from >>>>> Trusty to Xenial for translate.openstack.org is needed >>>>> since default-jre-headless on Trusty is Java 7 and Xenial is Java 8. >>>>> >>>>> Recently [3] has been merged, so I really hope that i18n team will see >>>>> newer version of Zanata soon :) >>>>> >>>>> I18n team discussed Zanata upgrade with pleia2 and clarkb during i18n >>>>> Barcelona meetup (See number 4 in [4]), >>>>> and the following is my thoughts on appropriate procedures to support >>>>> Zanata latest version >>>>> (Currently 3.9.6 - [5]): >>>>> >>>>> 1. Xenial OS test for translate-dev.openstack.org >>>>> : IMO after tests from infra team, [6] will be changed from "# Node-OS: >>>>> trusty" to "# Node-OS: xenial" >>>>> >>>>> 2. Using openstackid instead of openstackid-dev for translators to test >>>>> translate-dev.o.o >>>>> : I uploaded a patch [7]. >>>>> >>>>> 3. Uploading a patch on openstack-infra/puppet-zanata for Zanata 3.9.6 >>>>> : [8] is a reference for previous upgrade from Zanata 3.7.2 to 3.7.3 >>>>> >>>>> 4. translate-dev.o.o with Zanata 3.9.6 will be ready => I18n translators >>>>> will test it :) >>>>> >>>>> 5. If there will be no error for Zanata 3.9,6, then node upgrade from >>>>> Trusty to Xenial and Zanata upgrade to 3.9.6 >>>>> is needed for translate.openstack.org >>>>> : changing [9] line and also proposing a patch similar to [10] will be >>>>> needed later. >>>>> >>>>> >>>>> Since newer version of Zanata is what translators are expecting a lot >>> :) >>>>> , >>>>> I would like to kindly ask infra team members for the help of reviewing >>>>> and accomplishing such steps with higher priority. >>>>> >>>>> @clarkb, would the proposed procedures cover all the things regarding >>>>> Zanata upgrade? >>>>> If yes, would you share a sort of scheduled plans? >>>>> IMO Zanata development team will kindly help following schedules if >>>>> there will be some issues which are dependent to Zanata itself. >>>>> >>>>> >>>>> [1] https://review.openstack.org/#/c/240383/ >>>>> [2] https://etherpad.openstack.org/p/I18n-Zanata-enhancement >>>>> [3] https://review.openstack.org/#/c/384239/ >>>>> [4] https://etherpad.openstack.org/p/barcelona-i18n-meetup >>>>> [5] https://github.com/zanata/zanata-platform/releases >>>>> [6] >>>>> >>> http://git.openstack.org/cgit/openstack-infra/system-config/tree/manifests/s >>> ite.pp#n1282 >>>>> [7] https://review.openstack.org/#/c/393405/ >>>>> [8] https://review.openstack.org/#/c/239617/1/manifests/init.pp >>>>> [9] >>>>> >>> http://git.openstack.org/cgit/openstack-infra/system-config/tree/manifests/s >>> ite.pp#n1257 >>>>> [10] https://review.openstack.org/#/c/232313/ >>>> Just a quick status update on this. I have updated puppet things so that >>>> we can deploy translate-dev01.openstack.org on Xenial then CNAME >>>> translate-dev.openstack.org to it. (This is part of how we are trying to >>>> deploy services in the future to avoid being tied to a single instance >>>> in our puppetry). This includes running the noop puppet apply test >>>> against Xenial for these nodes on puppet changes as well. >>>> >>>> All of that has gone relatively well and I just tried to deploy on >>>> Xenial and have run into a few problems. The puppet output [11] shows >>>> that the service isn't installed properly on Ubuntu Xenial. Looking at >>>> the puppet-wildfly module [12] it doesn't appear to support systemd on >>>> debuntu yet. Due to the upcoming thanksgiving holiday I doubt I will get >>>> around to updating and testing that this week, so would be great if >>>> someone else is able to work with the puppet-wildfly upstream to fix >>>> this. >>>> >>>> One other thing that came up is do we need to copy any files from the >>>> old server to the new server? Specifically it looks like portions of >>>> `/home/wildfly/zanata` may need to be preserved. Or is everything >>>> important in the database? >>>> >>>> In any case once the wildfly puppetry is working I think the next step >>>> is to upgrade zanata to 3.9.6, change the openid server, and have the >>>> team test it. Once that looks good its on to the production server. >>>> >>>> [11] http://paste.openstack.org/show/590149/ >>>> [12] >>>> >>> https://github.com/biemond/biemond-wildfly/blob/master/manifests/service.pp# >>> L35-L46 >>> >>> Time for an update, and this time it is good news. I managed to hack >>> around the systemd issue by adding a puppet exec between installing the >>> init script and starting the service that runs a systemctl daemon-reload >>> [13]. This is necessary to make systemd see the init script allowing it >>> to be used to start the service. >>> >>> With that sorted I have created a new server called >>> translate-dev01.openstack.org and updated DNS to have >>> translate-dev.openstack.org point to it. This server is running on >>> Ubuntu Xenial with Java 8 and using the old version of Zanata (3.7.3). >>> Now would be a good time to test that this works so that we don't have >>> to do the entire upgrade migration in one go when we do production. Once >>> we are happy with Zanata 3.7.3 on Ubuntu Xenial and Java 8 we can >>> upgrade translate-dev.openstack.org to the version of Zanata we want, >>> then test again. And once that is done we can redeploy and upgrade the >>> production server on Xenial as well. >>> >>> Let me know how your testing goes and we can take it from there. >>> >>> [13] https://review.openstack.org/#/c/401363/ >> >> Hi Clark, >> >> thanks for the work. Regarding the systemd issue just to ensure: you are >> using Wildfly 10 with wildfly puppet module v1.0.0? It seems the systemd >> stuff is already implemented there and to use with: >> >> class { '::wildfly': >> ... >> init_system => 'systemd', >> } > This actually looks brand new. I will have to look at it more closely. I > ended up hacking around it locally though. The shipped sys v init script > works fine with systemd you just have to inject a daemon-reload since > puppet doesn't know how to do that when dealing with systemd. > > Clark

5 15

Importing Glossaries from i18n repo into Zanata has been done
by Ian Y. Choi 17 Jan '17

17 Jan '17

Hello translators, Zanata has glossary support as seen number 11 in [1]. I18n team maintains glossaries from language teams in [2], but I have just recognized that updating glossaries into Zanata is also my important role. Sorry for that, and now I confirm that Zanata (translate.openstack.org) now has the same glossary set in [2]. If there is some need to change glossary words or some language teams want to upload glossary, patch submissions like [3] and/or [4] are welcome :) (Usually, the approval from corresponding language coordinators is needed to merge such patch.) [1] http://docs.zanata.org/en/release/user-guide/editor/editor-view/ [2] http://git.openstack.org/cgit/openstack/i18n/tree/i18n/locale [3] https://review.openstack.org/#/c/418351/ [4] https://review.openstack.org/#/c/351783/ With many thanks, /Ian

1 0

Proposal on new "StringFreeze" manager + I18n reports
by Ian Y. Choi 16 Jan '17

16 Jan '17

Hello i18n team members! When I decided to start my PTL role for Ocata cycle, I wanted to do a lot with many I18n team members. However, lots of real condition (short Ocata cycle, my busy daily work, and so on..) makes me difficult to accomplish what I originally wanted during Ocata. (Before I would like to tell, please also review i18n-specs repository : https://review.openstack.org/#/q/project:openstack/i18n-specs . I originally wanted to share what I would like to change through i18n-specs, but now I think it is good to share using e-mail now.) The followings are mainly based on what I18n team discussed on the last IRC meeting [2-4]: 1) "StringFreeze Manager" - roles : sending an e-mail for notifications for soft / hard stringfreeze : sharing statistics how much strings are being translated : activity period would be the period affecting soft and hard stringfreeze : weekly checking for e-mail notifications and sharing statistics would be needed. - concrete example (Ocata) >> just before R-5: notification for "translation is important because stringfreeze period is too short. Please start" >> just before R-4: "This week is for Soft Freeze. Almost all strings in Horizon and related projects are being freezed" (we might need to search it.. I will also search for freezed projects) >> just before R-3: Horizon projects will be hard-freezed and packaged. If there is translation bugs, please change it before hard freeze >> R-2 and R-1: sharing translation stats with freezed project list on horizon and related projects mentioned in https://translate.openstack.org/ => Ilya Alekseyev (irc:adiantum) kindly accepted my proposal. So I would like to become a driver for such StringFreeze manager role with Ilya. 2) A periodic report based on IRC meeting and activities reported by language coordinators - Period: Let's start "monthly" first, and then try to pursue bi-weekly, if the report will be useful to all. - Language coordinators need to report translation progress and stats in their language : IRC meeting presence is preferred. : Reporting by e-mail and also wiki form [5] is also welcome. - PTL will gather information and publish reports like [1]. - Recipient: openstack-i18n, openstack-docs We have I18n liaisons and I would like to think how StringFreeze manager(s) and liaisons would cooperate each other later (not now, since I have no concrete idea - but feel free to share us!). Also, I18n report needs more interaction with language coordinators and core reviewers. I will think more on it :) [1] http://lists.openstack.org/pipermail/openstack-docs/2017-January/009471.html [2] http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… [3] http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… [4] http://eavesdrop.openstack.org/irclogs/%23openstack-i18n/%23openstack-i18n.… [5] https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Apologies_for_absen… With many thanks, /Ian

1 0

Updating paragraphs in the landing page.
by Cloud Suhartono 16 Jan '17

16 Jan '17

Thanks you for resolving [www-id] adds more translated page links, and finally the page http://docs.openstack.org/id/ having new links. Now, please give me another help to update 2 paragraphs in the page http://docs.openstack.org/id/. I want the updated paragraphs in the new version patch set look like these: 15 16 Apa OpenStack? OpenStack adalah sistem operasi cloud yang mengontrol kolam besar sumber daya komputasi, penyimpanan, dan jaringan di seluruh pusat data, dimana semuanya dikelola melalui dashboard yang memberikan administrator untuk mengontrol dan sekaligus memberdayakan penggunanya dalam pemanfaatan sumber daya melalui antarmuka web. 17 86 Pengantar menggunakan OpenStack API Best regards /Suhartono

2 1

Re: [OpenStack-I18n] [OpenStack-Infra] translate-dev wildfly/zanata/trove issues
by Ian Y. Choi 16 Jan '17

16 Jan '17

Thanks a lot for such sharing Ian! - not me :) I am copying to i18n mailing list and Zanata dev team for FYI purpose (as what Kato-san kindly RST markups for option on another mail thread). Note that this issue is re-generatable: I am able recreate the issue on translate-dev : When I create a new version from openstack-manuals from master branch [1] - 20107950 words, there is no further web responses from translate-dev.o.o around after 3/4 of total words were processed like [2-4]. It was completely fine for a version creation with 2610150 words. If someone has a good idea to further investigate on it, please share to us :) [1] https://translate-dev.openstack.org/iteration/view/openstack-manuals/master [2] https://translate-dev.openstack.org/iteration/view/openstack-manuals/stable… [3] https://translate-dev.openstack.org/iteration/view/openstack-manuals/test-v… [4] https://translate-dev.openstack.org/iteration/view/openstack-manuals/test-v… With many thanks, /Ian Ian Wienand wrote on 1/16/2017 12:03 PM: > Hi, > > I was alerted to translate-dev performance issues today. Indeed, it > seemed that things were going crazy with the java wildfly process > sucking up all CPU. > > At first there didn't seem to be anything in the logs. Java was > clearly going mad however, with the following threads going flat-out. > > --- gone crazy processes --- > 14807 wildfly 20 0 9.892g 4.729g 34232 R 93.7 60.7 26:56.73 java > 14804 wildfly 20 0 9.892g 4.729g 34232 R 92.4 60.7 26:51.91 java > 14806 wildfly 20 0 9.892g 4.729g 34232 R 92.4 60.7 26:53.92 java > 14808 wildfly 20 0 9.892g 4.729g 34232 R 92.4 60.7 26:53.97 java > 14810 wildfly 20 0 9.892g 4.729g 34232 R 92.4 60.7 26:56.28 java > 14809 wildfly 20 0 9.892g 4.729g 34232 R 92.1 60.7 26:57.74 java > 14803 wildfly 20 0 9.892g 4.729g 34232 R 91.1 60.7 26:54.90 java > 14805 wildfly 20 0 9.892g 4.729g 34232 R 90.4 60.7 26:52.44 java > --- > > Hoping to find a easy smoking-gun, I made the java process dump it's > threads to see what these are doing > > --- thread dump --- > > 14807 14804 14806 14808 14810 14809 14803, 14805 > 0x39d7 0x39d4 0x39d6 0x39d8 0x39da 0x39d9 0x39d3 0x39d5 > > "GC task thread#4 (ParallelGC)" os_prio=0 tid=0x00007fb2a8026000 nid=0x39d7 runnable > "GC task thread#4 (ParallelGC)" os_prio=0 tid=0x00007fb2a8026000 nid=0x39d7 runnable > "GC task thread#4 (ParallelGC)" os_prio=0 tid=0x00007fb2a8026000 nid=0x39d7 runnable > "GC task thread#4 (ParallelGC)" os_prio=0 tid=0x00007fb2a8026000 nid=0x39d7 runnable > > "GC task thread#1 (ParallelGC)" os_prio=0 tid=0x00007fb2a8021000 nid=0x39d4 runnable > "GC task thread#1 (ParallelGC)" os_prio=0 tid=0x00007fb2a8021000 nid=0x39d4 runnable > "GC task thread#1 (ParallelGC)" os_prio=0 tid=0x00007fb2a8021000 nid=0x39d4 runnable > "GC task thread#1 (ParallelGC)" os_prio=0 tid=0x00007fb2a8021000 nid=0x39d4 runnable > > "GC task thread#3 (ParallelGC)" os_prio=0 tid=0x00007fb2a8024800 nid=0x39d6 runnable > "GC task thread#3 (ParallelGC)" os_prio=0 tid=0x00007fb2a8024800 nid=0x39d6 runnable > "GC task thread#3 (ParallelGC)" os_prio=0 tid=0x00007fb2a8024800 nid=0x39d6 runnable > "GC task thread#3 (ParallelGC)" os_prio=0 tid=0x00007fb2a8024800 nid=0x39d6 runnable > > "GC task thread#5 (ParallelGC)" os_prio=0 tid=0x00007fb2a8028000 nid=0x39d8 runnable > "GC task thread#5 (ParallelGC)" os_prio=0 tid=0x00007fb2a8028000 nid=0x39d8 runnable > "GC task thread#5 (ParallelGC)" os_prio=0 tid=0x00007fb2a8028000 nid=0x39d8 runnable > "GC task thread#5 (ParallelGC)" os_prio=0 tid=0x00007fb2a8028000 nid=0x39d8 runnable > > "GC task thread#7 (ParallelGC)" os_prio=0 tid=0x00007fb2a802b800 nid=0x39da runnable > "GC task thread#7 (ParallelGC)" os_prio=0 tid=0x00007fb2a802b800 nid=0x39da runnable > "GC task thread#7 (ParallelGC)" os_prio=0 tid=0x00007fb2a802b800 nid=0x39da runnable > "GC task thread#7 (ParallelGC)" os_prio=0 tid=0x00007fb2a802b800 nid=0x39da runnable > > "GC task thread#6 (ParallelGC)" os_prio=0 tid=0x00007fb2a8029800 nid=0x39d9 runnable > "GC task thread#6 (ParallelGC)" os_prio=0 tid=0x00007fb2a8029800 nid=0x39d9 runnable > "GC task thread#6 (ParallelGC)" os_prio=0 tid=0x00007fb2a8029800 nid=0x39d9 runnable > "GC task thread#6 (ParallelGC)" os_prio=0 tid=0x00007fb2a8029800 nid=0x39d9 runnable > > "GC task thread#0 (ParallelGC)" os_prio=0 tid=0x00007fb2a801f000 nid=0x39d3 runnable > "GC task thread#0 (ParallelGC)" os_prio=0 tid=0x00007fb2a801f000 nid=0x39d3 runnable > "GC task thread#0 (ParallelGC)" os_prio=0 tid=0x00007fb2a801f000 nid=0x39d3 runnable > "GC task thread#0 (ParallelGC)" os_prio=0 tid=0x00007fb2a801f000 nid=0x39d3 runnable > --- > > Unfortunately, these all appear to be GC threads so there's nothing > really obvious there. > > However, eventually in the log you start getting stuff like > > --- > 2017-01-16T01:58:00,844Z SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (default task-43) Error Rendering View[/project/project.xhtml]: javax.el.ELException: /WEB-INF/layout/project/settings-tab-languages.xhtml @117,88 rendered="#{not projectHome.hasLocaleAlias(locale)}": javax.persistence.PersistenceException: org.hibernate.HibernateException: Transaction was rolled back in a different thread! > ... > 2017-01-16T01:08:48,805Z WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (pool-5-thread-1) SQL Error: 0, SQLState: null > 2017-01-16T01:08:48,806Z ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (pool-5-thread-1) javax.resource.ResourceException: IJ000460: Error checking for a transaction > 2017-01-16T01:08:48,813Z ERROR [org.hibernate.AssertionFailure] (pool-5-thread-1) HHH000099: an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session): org.hibernate.exception.GenericJDBCException: Could not open connection > 2017-01-16T01:08:48,813Z WARN [com.arjuna.ats.jta] (pool-5-thread-1) ARJUNA016029: SynchronizationImple.afterCompletion - failed for org.hibernate.engine.transaction.synchronization.internal.RegisteredSynchronization@3fc123aa with exception: org.hibernate.AssertionFailure: Exception releasing cache locks > --- > > There's literally hundreds of lines of traceback across various > exceptions, but at the bottom this really seems to point to mysql > being at the root of all this? > > In this case, mysql is running in RAX's cloud db service. I logged > into the RAX control-panel and everything for the DB was green. I > used the same credentials as zanata to authenticate and I can connect > to the db via translate-dev.o.o and do a few basic things. > > --- > MySQL [(none)]> USE zanata; > Reading table information for completion of table and column names > You can turn off this feature to get a quicker startup with -A > > Database changed > MySQL [zanata]> show tables; > +----------------------------------+ > | Tables_in_zanata | > +----------------------------------+ > | Activity | > | DATABASECHANGELOG | > ... > --- > > So it's not as simple as "db not working" :( I have copied the console > log to [1] in case that makes any sense to zanata people. > > If this persists, and isn't a known Zanata issue, I think we might > have to enable root access for the db via the API which might allow us > to do some thing like debug long-queries. Otherwise, there might be > something in the mysql logs available to RAX support people that would > otherwise help identify the issue. OTOH, maybe it's as simple as > upping java heaps or something. > > In the mean time, I have restarted wildfly which seems to get things > going for a while. > > -i > > [1] http://people.redhat.com/~iwienand/console.log.translate-dev-2017-01-16.log… > > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

2 1

FYI: RST markups for option
by Kato, Tomoyuki 15 Jan '17

15 Jan '17

Hi I18n team, Docs team changed convention about RST markup for options[1]. The newer version of Sphinx warns about :option:` ` usage without .. option:: description. Since we do not use .. option:: to describe parameter, remove :option:` `. Please keep in mind using :option:` ` breaks build in traslating. [1] http://docs.openstack.org/contributor-guide/rst-conv/inline-markups.html#op… Regards, KATO Tomoyuki

1 0

Re: [OpenStack-I18n] [openstack-dev] [release][ptl] not planning to serve as release PTL for Pike
by Ian Y. Choi 15 Jan '17

15 Jan '17

Thank a lot for your great work on release management team. Also, I would like to express my appreciation to Doug especially for communications with I18n team. I remember that Doug kindly came to I18n room at Austin Design Summit, and we discussed some release management issues for I18n team. Moreover, releasenotes translation support would not be possible without your kind assistance. With many thanks, Doug Hellmann wrote on 1/14/2017 5:00 AM: > I announced this at the release team meeting on 6 Jan, but thought > I should also post to the list as well: I do not plan to serve as > the Release Management team PTL for the Pike release cycle. > > It has been my pleasure to serve as PTL, and we've almost finished > the automation work that I envisioned when I joined the team. Now > I would like to shift my focus to some other projects within the > community. I will still be an active member of the Release Management > team, helping with new initiatives and reviews for releases. > > Doug > > __________________________________________________________________________ > 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

PTG planning etherpad
by Alexandra Settle 14 Jan '17

14 Jan '17

Hi everyone, I have created an etherpad for i18n and docs to collaborate on: https://etherpad.openstack.org/p/docs-i18n-ptg-pike I have added this etherpad to the wiki page: https://wiki.openstack.org/wiki/PTG/Pike/Etherpads#Monday_-.3E_Tuesday Please allocate if you are able to attend in the ‘attendees’ section. If you have any topics you wish to discuss during the PTG (for docs or i18n) please list them in the etherpad ☺ Thanks, Alex

3 2

What's Up, Doc? 13 January
by Lana Brindley 13 Jan '17

13 Jan '17

Hi everyone, Welcome to 2017. I hope you all had a chance to rest up a little before we hurtle straight into another release, as Ocata is now only 40 days away! I'll be in contact with our lovely release managers Brian and Mariia over the next week or so to kick off release management tasks. We will need people to test the Installation Guide again, too, so if you're interested in helping out there, please let me know. As many of you already know, I'm not planning on running for Pike PTL. PTL nominations open in the week of 23 January, and I'll be working with Alex and Kato-san who have both expressed interest in taking on this role. If you're interested in running for PTL (for Pike or any future release), and would like a crash course in PTLing, please let me know and I can share whatever meagre wisdom I've gleaned. == Progress towards Ocata == 40 days to go! Closed 149 bugs so far. Deliverables are being tracked here: https://wiki.openstack.org/wiki/Documentation/OcataDeliverables == The Road to PTG in Atlanta == Event info is available here: http://www.openstack.org/ptg Purchase tickets here: https://pikeptg.eventbrite.com/ Docs is a horizontal project, so our sessions will run across the Monday and Tuesday of the event. We will be combining the docs event with i18n, so translators and docs people will all be in the room together. The incoming PTL will be responsible for planning and running sessions at the Atlanta PTG. Also, a quick note that the CFP and ticket sales for *Boston* in May are now open: https://www.openstack.org/summit/boston-2017/call-for-presentations/ == Speciality Team Reports == * API: Anne Gentle Fairy-slipper is being retired. It was a good tool, served its purpose, and can now traipse into the sunset, thanks to AJaeger and stevemar for the help with the patches. Be sure to follow the service catalog naming conventions work going on in the API WG. And there's also a new EC2 API reference: http://developer.openstack.org/api-ref/ec2-api/ * Configuration Reference and CLI Reference: Tomoyuki Kato Config Reference: Updated a few plug-ins. CLI reference: Updated a few command references and removed unsupported Block Storage API v1 and Image API v1. * High Availability Guide: Andrew Beekhof No report this week * Hypervisor Tuning Guide: Joe Topjian No report this week * Installation guides: Lana Brindley Testing for Ocata will be opening soon. Also, we need a web dev for the landing page, if you know of anyone, please get me in touch. * Networking Guide: John Davidge No update this week. * Operations and Architecture Design guides: Darren Chan Ben Silverman has spent some time refining the Compute content in the Arch Guide draft. Thanks Ben! We are also looking for more SMEs to help with the Arch Guide. So if you're interested, contact asettle or me. * Security Guide: Nathaniel Dillon No update this week. * Training Guides: Matjaz Pancur No update this week. * Training labs: Pranav Salunke, Roger Luethi No update this week. * User guides: Joseph Robinson The command conversions have happened at a good pace, the User Guide appears to be mostly complete, with the condition that the trove and manila teams do not have OpenStack commands yet. I have started checking through the Admin Guide files. I suspect there is more to convert, but it should be ready for Ocata. == Doc team meeting == Our next meeting will be on Thursday 27 January at 2100 UTC in #openstack-meeting-alt For more meeting details, including minutes and the agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#13_January_2017 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Discussion: How to test Zanata well for translate-dev.openstack.org?
by Ian Y. Choi 13 Jan '17

13 Jan '17

Hello, First of all, I am really sorry for raising this issue late. (I have thought that I already shared it through openstack-i18n mailing list, but it was actually in my draft mailbox..) Previously, when I18n team migrated translation platform from Transifex to Zanata, http://translate-dev.openstack.org was used to test Zanata. Current Zanata version we use is 3.7.3, and now I18n wants to have newer Zanata version (e.g., 3.9.6: https://github.com/zanata/zanata-platform/releases/tag/server-3.9.6 - current latest) with a few bug fixes and newer functionalities. Infra team is now helping to upgrade Zanata with server operating system upgrade (Current translate.openstack.org uses Trusty - Ubuntu 14.04 but newer Zanata version needs Xenial - Ubuntu 16.04), and now http://translate-dev.openstack.org is running with current Zanata 3.7.3 version and *Xenial*! For the first step, I18n team needs to test translate-dev.openstack.org - whether Zanata 3.7.3 works with Xenial operating system or not. Please see possible test items on Etherpad: https://etherpad.openstack.org/p/i18n-zanata-test-for-translate-dev Actually, since I did not involve too much on previously migration from Transifex to Zanata, I am not sure whether current test items on Etherpad is sufficient for Zanata test or not. So, please review test items for such testing purposes and add or modify items if needed. Also, involving translate-dev test activities and updating test result with 'O' mark in Etherpad will be really appreciated. If our test result is fine, then the next step would be to test Zanata latest version with Xenial on translate-dev.openstack.org . With many thanks, /Ian

5 6

Re: [OpenStack-I18n] [I18n] Sharing Documentation translation stats
by C. Verheyde 12 Jan '17

12 Jan '17

Hi, Thank you for the sharing of the stats Ian ! That's great to see it progressing. I noticed a "bug" in identity in stackalytics. My nickname/logname is Corin, but it seems I'm refered in stackalytics as "Corin Royal Drummond<http://stackalytics.com/?metric=translations&release=all&user_id=corin>". I don't know at all where this "Royal Drummond" suffix comes from ??? http://stackalytics.com/?metric=translations&release=ocata) Regards, Corinne

3 4

[I18n] Sharing Documentation translation stats during Ocata cycle
by Ian Y. Choi 12 Jan '17

12 Jan '17

Hello! When I went to last Barcelona Summit, I told that I would share updates from I18n to Docs mailing list monthly. But, in reality, my daily and usual stuffs prevented me from writing a good and nice article as Lana does so well. Furthermore, time is really going too fast (Half of Ocata cycle is already passed!). Now I would like to share Documentation translation statistics from translators for last couple of months in Ocata cycle to Docs and I18n team. Note that my sharing might not be perfect. I have not quantitatively measured how many words are in OpenStack documents and also how translation qualities are improved by review activities, but I welcome your feedback from my first sharing. I would like to keep sharing such updates with Docs team :) == Documentation translation plan during Ocata cycle == - By the last December 2016, I18n team set higher priority for the following document translation: : (stable-newton) openstack-manuals: install-guide : (stable-newton) openstack-manuals: common : (stable-newton) openstack-manuals: networking-guide : (master) openstack-manuals: user-guide : (master) training-guides: upstream-training == Statistics data for documentation translations == - By now, there were total 158,414 translated words in openstack-manuals for Ocata cycle. Many translators from different countries have participated in such translation. I really appreciate such kind translation contribution! - Also, there were 23,552 translated words in training-guides (upstream-training) and 1,159 words for api-site (api-quick-start) for OpenStack documents. - For more information on statistics, please see translation metrics in Stackalytics (URL: http://stackalytics.com/?metric=translations&release=ocata) == Completed documentation translation == The following documents have significant progress during Ocata cycle. I have checked the percentage of translations by documents on late November 2016 and just today from Zanata, OpenStack translation platform: https://translate.openstack.org/ . - openstack-manuals in stable/newton : common => 100% translated for Indonesian, Korean, and Russian! : install-guide => Now French, Indonesian, and Korean documents are fully translated. => Also, there have been lots of translations contributed from German translators. - openstack-manuals in master : Japanese translators have constantly contributed their translations. Now the following documents are fully translated into Japanese => ha-guide, image-guide, and user-guide : Also, Indonesian user-guide is 100% translated. - training-guides : Indonesian upstream-training is now fully translated. : Nice progress for German (45.04% -> 74.33%) More detail translation progress with published pages is available at : https://etherpad.openstack.org/p/i18n-translation-status-documentation . == Published translated documents and Language landing pages == It is important for language landing pages to have up-to-date links for published translated documents. During Ocata cycle, - French landing page now includes Mitaka install-guide (Note: It was fully translated before Ocata cycle, but translation reviews by French translators have been accomplished during Ocata cycle). - Korean landing page now includes Newton install-guide. For language landing pages, the following modifications will be accomplished soon hopefully. Note that it will depend on specific translation and review plan from different languages. : Indonesian landing page will include more published translated documents. : Japanese landing page will include ha-guide, which is now 100% translated. : French landing page will be refined with a new theme (the one now docs.openstack.org uses). That's what I wanted to share with Docs and I18n team for documentation translation statistics. Now Ocata Dashboard translation including Horizon is getting more important for I18n team, since StringFreeze periods are relatively short in Ocata cycle. However, that does not mean that documentation translation for I18n team has been finished in Ocata cycle. Although translators would be busy for translation activities, I would like to encourage to also spend time on translation reviews to make translated documents with higher qualities. With many thanks, /Ian

3 2

Re: [OpenStack-I18n] Puzzled with Japanese ha-guide
by Kato, Tomoyuki 06 Jan '17

06 Jan '17

Hi Andreas, Good finding. I submitted a patch: https://review.openstack.org/#/c/417336/ Regards, KATO Tomoyuki > https://review.openstack.org/#/c/417318/ imports the Japanese ha-guide > and trying to build it, sphinx fails with: > > Exception occurred: > File > "/home/aj/Software/vcs/OpenStack/openstack/openstack-manuals/.tox/venv/lib/python2.7/site-packages/docutils/nodes.py", > line 1367, in set_duplicate_name_id > old_node = self.ids[old_id] > KeyError: 'install-rabbitmq' > > > I'm not sure what's going on here ;( > > we have in shared-messaging-rst: > - :ref:`Install RabbitMQ<rabbitmq-install>` > > And later the headline "Install RabbitMQ" with the label above. > > If I remove this entry from the po file, it still fails building: > > msgid ":ref:`Install RabbitMQ<rabbitmq-install>`" > msgstr ":ref:`RabbitMQ のインストール<rabbitmq-install>`" > > Could somebody investigate and fix this, please? [snip]

2 1

Puzzled with Japanese ha-guide
by Andreas Jaeger 06 Jan '17

06 Jan '17

https://review.openstack.org/#/c/417318/ imports the Japanese ha-guide and trying to build it, sphinx fails with: Exception occurred: File "/home/aj/Software/vcs/OpenStack/openstack/openstack-manuals/.tox/venv/lib/python2.7/site-packages/docutils/nodes.py", line 1367, in set_duplicate_name_id old_node = self.ids[old_id] KeyError: 'install-rabbitmq' I'm not sure what's going on here ;( we have in shared-messaging-rst: - :ref:`Install RabbitMQ<rabbitmq-install>` And later the headline "Install RabbitMQ" with the label above. If I remove this entry from the po file, it still fails building: msgid ":ref:`Install RabbitMQ<rabbitmq-install>`" msgstr ":ref:`RabbitMQ のインストール<rabbitmq-install>`" Could somebody investigate and fix this, please? Note for building, I did: diff --git a/doc-tools-check-languages.conf b/doc-tools-check-languages.conf index d562f83..ddb0047 100644 --- a/doc-tools-check-languages.conf +++ b/doc-tools-check-languages.conf @@ -8,7 +8,8 @@ declare -A BOOKS=( ["de"]="install-guide" ["fr"]="install-guide" ["id"]="install-guide user-guide" - ["ja"]="image-guide install-guide networking-guide ops-guide user-guide" +# ["ja"]="ha-guide image-guide install-guide networking-guide ops-guide user-guide" + ["ja"]="ha-guide" ["ko_KR"]="install-guide" ["zh_CN"]="install-guide user-guide" ) @@ -19,7 +20,7 @@ declare -A DRAFTS=( ["de"]="install-guide" ["fr"]="install-guide" ["id"]="install-guide" - ["ja"]="install-guide networking-guide ops-guide" + ["ja"]="ha-guide install-guide networking-guide ops-guide" ["ko_KR"]="install-guide" ["zh_CN"]="install-guide" And then run locally "tox -e buildlang -- ja". Note that it gives a success message despites failing (the next openstack-doc-tools update will fail this), 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

1 0

[Bug 1651917] [NEW] Storage 노드 설치와 구성 in Installation Guide
by junghyunchoi 05 Jan '17

05 Jan '17

Public bug reported: There is a typo. The following sentences should be changed 스토리지 노드를 설치dhk -> 스토리지 노드를 설치와 ----------------------------------- Release: 0.1 on 2016-12-21 10:47 SHA: 8868f91f9b758e1f98a2fac0c50b703e6ae1b6d3 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/ko_KR/install-guide-ubuntu/swift-storage-i… ** Affects: openstack-i18n Importance: Undecided Assignee: junghyunchoi (choipro14) Status: In Progress ** Tags: install-guide ** Changed in: openstack-i18n Assignee: (unassigned) => junghyunchoi (choipro14) ** Changed in: openstack-i18n Status: New => In Progress -- 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/1651917 Title: Storage 노드 설치와 구성 in Installation Guide Status in openstack i18n: In Progress Bug description: There is a typo. The following sentences should be changed 스토리지 노드를 설치dhk -> 스토리지 노드를 설치와 ----------------------------------- Release: 0.1 on 2016-12-21 10:47 SHA: 8868f91f9b758e1f98a2fac0c50b703e6ae1b6d3 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/ko_KR/install-guide-ubuntu/swift-storage-i… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1651917/+subscriptions

2 1

Re: [OpenStack-I18n] [openstack-dev] Fwd: [Openstack] The Forum: in more detail
by Ian Y. Choi 05 Jan '17

05 Jan '17

Hello, What a good article for the background of Forum and PTG with details! By the way, I have one question regarding to discount of translators for the Forum. Due to the nature (large number of members, geographically-dispersed, coming from all over our community, ops, devs, users) of I18n team [1], me and previous I18n PTLs (Daisy and Kato-san) have encouraged translators to participate in Forum to meet each other offline and discuss many translation and integration issues rather than attending to PTG. For translators, it seems that few translators will physically attend to PTG because of such nature, which implies that many translators who previously received discount codes for the Summit with the recognition of ATCs will not receive discount codes for the Forum. Then, is there less possibility for them to receive discount codes? I have been so expecting that more translators and I18n members will participate in the Forum and discuss how more translation activities will be vitalized with user community activities. Please give me some direction for successful participation and making fruits from I18n team on the Forum. (Of course, PTG is also an important event for I18n team although few I18n members will go there. I would like to bring some topics to discuss horizontally with many teams in near future, not too late or long.) [1] http://www.openstack.org/ptg#tab_faq [2] http://lists.openstack.org/pipermail/openstack-docs/2016-November/009294.ht… With many thanks, /Ian Tom Fifield wrote on 1/5/2017 1:19 PM: > Hi *dev, > > Post over on the general ML you might be interested in - please send > replies there to avoid cross-posting pain ;) > > > Regards, > > > Tom > > > -------- Forwarded Message -------- > Subject: [Openstack] The Forum: in more detail > Date: Thu, 5 Jan 2017 11:42:53 +0800 > From: Tom Fifield <tom(a)openstack.org> > To: openstack(a)lists.openstack.org > > Hi all, > > working with colleagues, I've just put up a post cobbling together > some more detail on the Forum. Sorry it took so long! > > http://superuser.openstack.org/articles/openstack-forum/ > > > There's now also a wiki page to be the reference for us to follow when > preparing or participating: > > https://wiki.openstack.org/wiki/Forum > > > Please check them out and reply with any thoughts, ideas or angry rants! > > > Regards, > > > Tom > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack(a)lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > __________________________________________________________________________ > > 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

[Bug 1651329] [NEW] Storage 노드 설치와 구성 in Installation Guide
by Jaeki Hong 22 Dec '16

22 Dec '16

Public bug reported: there are typos The following sentences should be changed [pipeline:mail] 섹션 -> [pipeline:main] 섹션 ----------------------------------- Release: 0.1 on 2016-12-12 10:29 SHA: 703d0574be515e76315ab505d6b2ea25a8450dc7 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/ko_KR/install-guide-ubuntu/swift-storage-i… ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- 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/1651329 Title: Storage 노드 설치와 구성 in Installation Guide Status in openstack i18n: New Bug description: there are typos The following sentences should be changed [pipeline:mail] 섹션 -> [pipeline:main] 섹션 ----------------------------------- Release: 0.1 on 2016-12-12 10:29 SHA: 703d0574be515e76315ab505d6b2ea25a8450dc7 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/ko_KR/install-guide-ubuntu/swift-storage-i… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1651329/+subscriptions

2 1

Merry Christmas and Happy New Year
by Alex Eng 22 Dec '16

22 Dec '16

Hi all, Zanata core team will be on holiday from 23 Dec to 2 Jan. We will be back on 3rd Jan 2017. I'm reachable via mobile and my personal email: loones1595(a)gmail.com Wishing you all Merry Christmas and Happy New Year! Regards, --------------------------------------------- Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com

1 0

[I18n] Today (Dec 15th) IRC meeting is canceled
by Ian Y. Choi 15 Dec '16

15 Dec '16

Hello, Unfortunately, I am unable to participate in today I18n IRC meeting due to my personal schedule. I am sorry for that. Note that the next IRC meeting will be on December 22nd 13:00 UTC in #openstack-meeting IRC channel. It will be the last meeting in this year (December 29th is during Christmas holiday). I hope to see many I18n members on the next meeting to wrap up what happened this year and also celebrate Christmas :) With many thanks, /Ian

1 0

formatted source text
by Robert Simai 08 Dec '16

08 Dec '16

Hi, I guess everyone translating has seen this, sometimes there's source text formatted by line breaks and even spaces at the beginning of lines which finally forces the translator to keep this format, else Zanata wouldn't allow to save it. For an example, see above :-) I think this formatting is rather bad and shouldn't happen. Text should be either continuous or it needs to be split to go into multiple strings. Are there any reasons where as such formatted text is justified, translator should leave it as it is? Or shall we rather rather flag this through a bug, or even create patches to change it? Opinions? -- Thanks, Robert

3 6

[I18n] IRC Meeting remainder: November 10th at 13:00 UTC
by Ian Y. Choi 08 Dec '16

08 Dec '16

Hello all, I18n team is having our next meeting on November 10th (Thursday) at 13: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/2016/opensta… Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Log: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Note that I will be moving from one place to another during meeting time. I will bring my laptop with smartphone tethering, but it would be much better if someone (IRC meeting chair or any volunteer) starts meeting. See you tomorrow! With many thanks, /Ian

2 4

[Bug 1647116] [NEW] [i18n-guide] link errors
by Ian Y. Choi 05 Dec '16

05 Dec '16

Public bug reported: In http://docs.openstack.org/developer/i18n/infra.html , http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/j… from include-build-releasenotes.sh and http://docs.zanata.org/projects/zanata-client/en/latest/ from zanata-cli are not working. ** Affects: openstack-i18n Importance: Undecided Assignee: Ian Y. Choi (ianychoi) Status: In Progress ** Changed in: openstack-i18n Assignee: (unassigned) => Ian Y. Choi (ianychoi) -- 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/1647116 Title: [i18n-guide] link errors Status in openstack i18n: In Progress Bug description: In http://docs.openstack.org/developer/i18n/infra.html , http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/j… from include-build-releasenotes.sh and http://docs.zanata.org/projects/zanata-client/en/latest/ from zanata-cli are not working. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1647116/+subscriptions

2 1

What's Up, Doc? Holiday Edition!
by Lana Brindley 02 Dec '16

02 Dec '16

Hi everyone, The end of the year is nearly upon us already, and this will be my last newsletter for 2016, before I disappear for the holidays on the 16th. I've had yet another wonderful year with all you lovely OpenStack people, and I wish all of you and your families a happy and safe holiday, wherever and however you celebrate it. Here in Australia, the temperature is starting to soar, so I'm off on another cruise, followed by a few lazy days by the pool with family and friends. I'll be back in the office early in the new year, and ready to kick Ocata out of the door! As many of you already know, I'm not planning on running for Pike PTL. If you're interested in running for PTL (for Pike or any future release), and would like a crash course in PTLing, please let me know and I can share whatever meagre wisdom I've gleaned before self nominations open in mid-January. == Progress towards Ocata == 82 days to go! Closed 106 bugs so far. Release tasks are being tracked here: https://wiki.openstack.org/wiki/Documentation/OcataDeliverables == The Road to PTG in Atlanta == Event info is available here: http://www.openstack.org/ptg Purchase tickets here: https://pikeptg.eventbrite.com/ Docs is a horizontal project, so our sessions will run across the Monday and Tuesday of the event. The incoming PTL will be responsible for planning and running sessions at the Atlanta PTG. == Speciality Team Reports == * API: Anne Gentle The App Dev Support WG is working on a survey to determine which content areas to invest in for content on http://www.openstack.org/appdev (http://lists.openstack.org/pipermail/user-committee/2016-November/001469.ht…) * Configuration Reference and CLI Reference: Tomoyuki Kato We try to recreating the single page view for the "openstack" command. I'd like to generate the reference from source code automatically. However, python-openstackclient has many plug-ins. It is difficulty, but worth to tackle it. We need your help! * High Availability Guide: Andrew Beekhof No formal report, but Alex Settle has been doing a lot of work on this guide recently, cleaning up, and raising bugs for some of the TODO items. We need to consider if the HA guide is an ongoing concern. Ben Silverman is wondering if we can fold the content into the Ops/Arch Guides. This will be raised on the mailing list for more conversation. * Hypervisor Tuning Guide: Joe Topjian No report this week * Installation guides: Lana Brindley We've heard back from Foundation on design resources, I'm going to reply to that email today and hopefully start drafting the new design next week. I've also got Piet from the UX team on board to help. Anyone who wants to be involved with that, please contact me. * Networking Guide: John Davidge No update this week. * Operations and Architecture Design guides: Darren Chan For the Arch guide, patches for networking and compute content were merged, thanks to Ben and Shaun. For the Ops Guide, there is patch up to update the upgrades chapter and include links to the project upgrade notes: https://review.openstack.org/#/c/404528/ * Security Guide: Nathaniel Dillon No update this week. * Training Guides: Matjaz Pancur BCN Upstream training article in the Superuser magazine: http://superuser.openstack.org/articles/openstack-upstream-training-revamp/ - actively looking for contributors to join the Upstream training, please see http://lists.openstack.org/pipermail/openstack-docs/2016-November/009382.ht… - cleaned test entries in the Launchpad bug queue and the Sandbox repository (left from the Barcelona Upstream training) - updated Training guides README.rst * Training labs: Pranav Salunke, Roger Luethi No update this week. * User guides: Joseph Robinson The legacy command conversion continues at a good pace. I have some more updates to patch today. The only obstacle I have run into is generating new output to match the OpenStack command client. Otherwise, contributors have been adding to the table, and there's been steady patching completed. Just a reminder to update the table if making a change: https://wiki.openstack.org/wiki/Documentation/ReorganizeUserGuides == Doc team meeting == Our next meeting will be on Thursday 16 December at 2100 UTC in #openstack-meeting-alt For more meeting details, including minutes and the agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#1_December_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Re: [OpenStack-I18n] Adding Romanian Language Team
by Ian Y. Choi 02 Dec '16

02 Dec '16

Hello Cristian, Sorry for my late reply. I am copying with openstack-i18n(a)lists.openstack.org to keep track of your request. (Note: I always try to read all of my e-mails but since I receive too much e-mails in my account these days, I usually check http://lists.openstack.org/pipermail/openstack-i18n/ for faster responses from openstack-i18n(a)lists.openstack.org.) Cristian Cira wrote on 11/17/2016 11:34 PM: > Hello Ian, > > Nice to meet you too! > > * I have registered to the mailing list > * It is not clear to me what is the difference between the two > encoding. I searched the net for some documentation but failed to > find one that points out the difference -maybe you could point me > to a better source. If my understanding is correct (namely that > the second one includes "somehow" a geographical component in the > characters encoding ) then I would opt for "ro" to keep it as > general as possible since there are few differences in the > Romanian dialects from various regions > Personally, I have been to Romania about 10 years ago shortly (about less than 4 weeks in Bucharest), but I do not have enough knowledge to judge between ro vs. ro-RO. Now I want to follow your decision: "ro". Thanks. > > * I will accept to be a coordinator with some hesitation. This > coordinator position must come with some extra responsibility > which is totally fine with. My concern regards the time I have to > dedicate to this activity. So, as long as I do not have to > officially commit a certain amount of hours to it, I am more then > happy to help translate. Also, I feel confident that I can find > some extra contributors, maybe even better suited for this > position then me. > That's fine. At least, I am not a full-time translator for OpenStack :) > * Also, could you please point me to a place where I can as question > related to how should I approach this task. Surely there are some > more important parts of the documentation that would need to be > tackled first. > Would you read first http://docs.openstack.org/developer/i18n/ ? Then please let me know which points you would like to know or ask. I will follow Romanian language support in Zanata after I18n IRC meeting on this Thursday 13:00 UTC ( http://eavesdrop.openstack.org/#I18N_Team_Meeting ). If you attend to this meeting, I think it will be very nice to talk each other. With many thanks, /Ian > > * > > > Thank you for your time. Have a lovely day, > ~cira > > On Thu, Nov 17, 2016 at 4:53 AM Ian Y. Choi <ianyrchoi(a)gmail.com > <mailto:ianyrchoi@gmail.com>> wrote: > > Hello Cristian, > > I am Ian. Nice to meet you! > > I think adding the support for Romanian language is possible in > Zanata :) > > Before going further, I want to ask you: > > - Please subscribe openstack-i18n(a)lists.openstack.org > <mailto:openstack-i18n@lists.openstack.org> mailing list through > : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > - For Romanian language, I want to ask you which ISO language code > is preferred > : "ro" vs. "ro-RO". > > - Are you willing to be a Romanian language coordinator in i18n team? > Since there is no Romanian translator currently, I want to > assign you as Romanian language coordinator. > As a language coordinator, it would be much better if you will > encourage more Romanian translations > to others, tell PTL (currently, me) for any updates, and share > or ask anything regarding i18n related things > through I18n IRC meeting > http://eavesdrop.openstack.org/#I18N_Team_Meeting or this mailing > list. > > > With many thanks, > > /Ian > > > Cristian Cira (KTH-PDC) wrote on 11/16/2016 4:26 AM: >> Dear all, >> >> I have recently decided to contribute to the translation of the >> OpenStack documentation to Romanian in my limited free time. >> >> I am a native Romanian currently working in Sweden at a HPC >> center. My English is proficient having studied and worked in USA >> for 5 years prior to moving here. Here is my LinkedIn >> <https://se.linkedin.com/in/cristian-cira-246b0933> account for >> some more details. >> >> My username on Zanata is *cira* >> * >> *Please let me know what are the next steps I have to take. >> >> Thank you, >> C >> >> *Cristian Cira,*PhD >> Application Expert in Code Optimization >> *PDC Center for High Performance Computing* >> KTH Royal Institute of Technology >> SE-100 44 Stockholm, Sweden >> *http://www.pdc.kth.se >> * >> Tel : +46 8 790 6309 <tel:08-790%2063%2009> >> Mob : +46 737 65 22 98 >> >> >> _______________________________________________ >> OpenStack-I18n mailing list >> OpenStack-I18n(a)lists.openstack.org >> <mailto:OpenStack-I18n@lists.openstack.org> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > -- > *Cristian Cira,* PhD > Application Expert in Code Optimization > *PDC Center for High Performance Computing* > KTH Royal Institute of Technology > SE-100 44 Stockholm, Sweden > *http://www.pdc.kth.se > * > Tel : +46 8 790 6309 > Mob : +46 737 65 22 98

2 2

[I18n] IRC Meeting remainder: November 3rd at 07:00 UTC
by Ian Y. Choi 30 Nov '16

30 Nov '16

Hello all, I18n team is having our next meeting on November 3rd (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 i18n Barcelona contributor meetup summary on Etherpad (URL: https://etherpad.openstack.org/p/barcelona-i18n-meetup ), last IRC meeting minutes and full logs: Minutes: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Log: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… With many thanks, /Ian

2 4

searchlight-ui: Broken cs translation / neutron-lbaas-dashboard: broken ja translation
by Andreas Jaeger 24 Nov '16

24 Nov '16

Could somebody check and fix these, please? http://logs.openstack.org/periodic/searchlight-ui-propose-translation-updat… searchlight_ui/locale/cs/LC_MESSAGES/djangojs.po:789: number of format specifications in 'msgid_plural' and 'msgstr[2]' does not match http://logs.openstack.org/periodic/neutron-lbaas-dashboard-propose-translat… neutron_lbaas_dashboard/locale/ja/LC_MESSAGES/djangojs.po:1092: '\''msgid'\'' and '\''msgstr'\'' entries do not both end with '\''\n'\'' 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 1

[Bug 1641785] [NEW] 环境 in Installation Guide 镜像服务写成了径向服务
by jeck 21 Nov '16

21 Nov '16

Public bug reported: 拼写错误 ----------------------------------- Release: 0.1 on 2016-11-13 23:16 SHA: 5a9c47b83b0209892f887697bb9e8bb871eee8a3 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-ubuntu/environment.html ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- 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/1641785 Title: 环境 in Installation Guide 镜像服务写成了径向服务 Status in openstack i18n: New Bug description: 拼写错误 ----------------------------------- Release: 0.1 on 2016-11-13 23:16 SHA: 5a9c47b83b0209892f887697bb9e8bb871eee8a3 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-ubuntu/environment.html To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1641785/+subscriptions

1 1

[Bug 1489311] Re: Chinese words in translations are incorrect
by Ian Y. Choi 20 Nov '16

20 Nov '16

I have found that Zanata now has a fixed string for this bug report: http://git.openstack.org/cgit/openstack/openstack- manuals/tree/doc/common/source/locale/zh_CN/LC_MESSAGES/common.po#n1145 ** Changed in: openstack-i18n Status: Confirmed => 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/1489311 Title: Chinese words in translations are incorrect Status in openstack i18n: Fix Released Bug description: I found there are mistakes of Chinese words in translations. Details: In source file: https://github.com/openstack/openstack-manuals/blob/master/doc/common/local… there are two places as follow: 1: L413 "<emphasis>用户不可以想传统的硬盘那样使用OpenStack对象存储。</emphasis>对象存" "用户不可以想传统的硬盘" should be "用户不可以像传统的硬盘". 2: L736 msgid "Access associated with a VM" L737 msgstr "访问和VM想关联" "访问和VM想关联" should be "访问和VM相关联". To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1489311/+subscriptions

1 0

[Bug 1612201] [NEW] Some strings which needn't translation appear in Zanata
by zzxwill 20 Nov '16

20 Nov '16

Public bug reported: In Zanata, document 'doc/admin-guide/source/locale/admin-guide' of openstack-manuals, some strings like 'vm2', 'doc/admin- guide/source/locale/admin-guide', 'd693db9e-a7cf-45ef-a7c9-b3ecb5f22645' are waiting for translation, while, which don't need to be translated. I think there should be a way to stop them from being shown in Zanata. Thanks. ** 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/1612201 Title: Some strings which needn't translation appear in Zanata Status in openstack i18n: New Bug description: In Zanata, document 'doc/admin-guide/source/locale/admin-guide' of openstack-manuals, some strings like 'vm2', 'doc/admin- guide/source/locale/admin-guide', 'd693db9e-a7cf-45ef- a7c9-b3ecb5f22645' are waiting for translation, while, which don't need to be translated. I think there should be a way to stop them from being shown in Zanata. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1612201/+subscriptions

2 1

[Bug 1612878] Re: 安装和配置 in Installation Guide
by Ian Y. Choi 20 Nov '16

20 Nov '16

"controller" vs. "10.0.0.11" is not the target of I18n team. ** Changed in: openstack-i18n Status: New => Invalid ** Tags added: simplified-chinese -- 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/1612878 Title: 安装和配置 in Installation Guide Status in openstack i18n: Invalid Bug description: ----------------------------------- Release: 0.1 on 2016-08-12 08:52 SHA: 739d8d9e6cb81a10aca0068e5ba1b76541b0398d Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-ubuntu/horizon-install… 在memcached里，/etc/memcached.conf 如果-l是controller -l controller 那么在/etc/openstack-dashboard/local_settings.py这个里面也应该是controller CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache', 'LOCATION': 'controller:11211', } } 否则在登录dashboard的时候，能出现登录的页面，登录不成功。如果都写IP地址，也是可以成功。在memcached里，/etc/memcached.conf 如果-l是10.0.0.11 -l 10.0.0.11 那么在/etc/openstack-dashboard/local_settings.py这个里面也应该是10.0.0.11 CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache', 'LOCATION': '10.0.0.11:11211', } } 这样才能成功。 To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1612878/+subscriptions

1 0

[Bug 1637920] [NEW] 网络选项2：私有网络配置Linuxbridge代理中[linux_bridge]部分应为 physical_interface_mappings = provider:PUBLIC_INTERFACE_NAME
by gavin 20 Nov '16

20 Nov '16

Public bug reported: section of PUBLIC_INTERFACE_NAME ----------------------------------- Release: 0.1 on 2016-10-30 16:22 SHA: 0aec93ae3cabb0ba77ca4a0a2498b5dcaf454984 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/neutron-controller… ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- 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/1637920 Title: 网络选项2：私有网络配置Linuxbridge代理中[linux_bridge]部分应为 physical_interface_mappings = provider:PUBLIC_INTERFACE_NAME Status in openstack i18n: New Bug description: section of PUBLIC_INTERFACE_NAME ----------------------------------- Release: 0.1 on 2016-10-30 16:22 SHA: 0aec93ae3cabb0ba77ca4a0a2498b5dcaf454984 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/neutron-controller… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1637920/+subscriptions

2 1

Re: [OpenStack-I18n] [OpenStack-docs] stable/newton created, publishing frozen for now
by Ian Y. Choi 20 Nov '16

20 Nov '16

Hello, Andreas Jaeger wrote on 11/13/2016 3:52 AM: > On 11/12/2016 07:18 PM, Andreas Jaeger wrote: >> Clark just created a stable/newton branch. >> >> I'll create the changes now for both master and stable so that >> publishing is correct. >> >> Please do not approve any changes until those are in. >> >> I'll sent in a few minutes an email with links to those changes for >> review, > > The changes that need to merge are: > > https://review.openstack.org/396874 > https://review.openstack.org/396875 > > In addition: > * stable-newton needs to be created on zanata (i18n team) Zanata now has a stable-newton version for openstack-manuals, and this version can be seen in https://translate.openstack.org/project/view/openstack-manuals and https://translate.openstack.org/iteration/view/openstack-manuals/stable-new… . i18n team will translate backported guides (common, install-guide, networking-guide) in stable-newton instead of master for translation plan and priority during Ocata cycle. Thank you all kind help and communication, especially Andreas and Olena! With many thanks, /Ian > * import of newton translations: https://review.openstack.org/396876 > * Documentation for the above: https://review.openstack.org/396877 > > Please review everything and help updating these if I missed anything, > I really like to have this properly documented so that the release > managers can do it next time, > > Andreas

1 1

What's Up, Doc? 18 November
by Lana Brindley 18 Nov '16

18 Nov '16

Hi everyone, Welcome to Ocata! It was great to catch up with many of you in Barcelona, and always refreshing to see the energy around our little project and catch that enthusiasm all over again :) Of course, Ocata is a *very* short cycle, so we've deliberately cut down our deliverables list to ensure we can squeeze it all in. We have two main priorities this release: tidying up the new Install Guides index page, and a little bit of navel gazing in terms of social structures and procedures. More on that in this newsletter! == Progress towards Ocata == 96 days to go! Closed 77 bugs so far. Release tasks are being tracked here: https://wiki.openstack.org/wiki/Documentation/OcataDeliverables == The Road to PTG in Atlanta == Event info is available here: http://www.openstack.org/ptg Purchase tickets here: https://pikeptg.eventbrite.com/ Docs is a horizontal project, so our sessions will run across the Monday and Tuesday of the event. == Specs on review == * Ops/Arch Guides: https://review.openstack.org/#/c/392372/ [arch-design] Revise the Architecture Design Guide https://review.openstack.org/#/c/394261/ [ops-guide] Add project upgrade notes https://review.openstack.org/#/c/391786/ Proposed use case form * Training Labs: https://review.openstack.org/#/c/391548/ training-labs: Rewrite training-labs in python == Speciality Team Reports == We've made some structural changes to how Speciality Teams and our regular docs meeting work. Speciality teams will now meet no more than once monthly (most on an 'as needed' basis), and participants are instead encouraged to attend the main docs meeting to discuss work and report on progress. This is aiming to keep all the information about the work we're doing a little more centralised, and give newcomers a way to find out where they can best help. It also gives us a chance to find out where we can help each other, without going to a dozen meetings! * API: Anne Gentle Karen Bradshaw has been working on updates to the openstackdocstheme that would fix this bug: https://launchpad.net/bugs/1583623. The review is up at https://review.openstack.org/#/c/393890/ and getting input from the affected teams who have recognized the need because of errors building when you have multiple API versions with very similar calls, so you end up with identical headings. Launchpad bug 1583623 in openstack-doc-tools "os-api-ref: duplicate labels for selectors" [Low,In progress] - Assigned to Karen Bradshaw (kbhawkey) I've had a couple of inquiries on IRC about "where did the draft/swagger files go?" but to meet their stated end goals, those particular files wouldn't have worked any way due to inaccuracies in the content and incomplete content. See the 100 api-ref doc patches up for review at: https://review.openstack.org/#/q/status:open+file:api-ref. * Configuration Reference and CLI Reference: Tomoyuki Kato No report this week * High Availability Guide: Andrew Beekhof No report this week * Hypervisor Tuning Guide: Joe Topjian No report this week * Installation guides: Lana Brindley No major updates to the guides themselves, but we are planning updates to the landing page. We're also working on getting our first deployment guide landed there, with OpenStack Ansible. I've requested design resources from foundation, but haven't heard back yet, so if you have ideas/suggestions (or design skillz!) then please let me know. * Networking Guide: John Davidge A couple of new articles are close to merging: https://review.openstack.org/#/c/361776/ - VLAN Trunking and https://review.openstack.org/#/c/356013/ - Routed Provider Networks. Need to decide how best to track the work that's going on for https://blueprints.launchpad.net/openstack-manuals/+spec/use-openstack-comm…. Probably a google spreadsheet or etherpad with a list of all the network guide pages to be converted, and the person working on it would be best. That way we can hopefully avoid duplicating efforts. * Operations and Architecture Design guides: Darren Chan We're slowly making progress with the arch guide, and have cloudnull onboard to help. So the focus is completing the design chapter and migrating stuff from the ops guide. * Security Guide: Nathaniel Dillon No update this week. * Training Guides: Matjaz Pancur We changed our IRC meeting to every two weeks (on even weeks) on Tuesday at 1300 UTC in #openstack-meeting-3. There will be an article published about BCN Upstream training in OpenStack's Superuser magazine. BCN Upstream training retrospective https://etherpad.openstack.org/p/upstream-training-barcelona-retrospective * Training labs: Pranav Salunke, Roger Luethi We have the python port already under review, the spec is not done yet, but we hope to get them merged soonish and in the right order :) User guides: Joseph Robinson * This the current work on converting the legacy commands to OS commands: https://wiki.openstack.org/wiki/Documentation/ReorganizeUserGuides#Ocata_Ta…. Thanks to csatari and visnyei and allen, there's progress happening. I need to finish adding the files affected to the checklist, and then also start making changes. Apart from that, keeping track of any admin or user guide bugs is also a task. == Doc team meeting == We have re-started the docs team meetings, with a new cadence. Our first meeting was held today, with much success. Thank you to everyone who participated, either directly in IRC, or by making sure you sent me your updates ahead of schedule. Our next meeting will be on Thursday 1 December at 2100 UTC in #openstack-meeting-alt For more meeting details, including minutes and the agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#18_November_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Adding Romanian Language Team
by Cristian Cira (KTH-PDC) 17 Nov '16

17 Nov '16

Dear all, I have recently decided to contribute to the translation of the OpenStack documentation to Romanian in my limited free time. I am a native Romanian currently working in Sweden at a HPC center. My English is proficient having studied and worked in USA for 5 years prior to moving here. Here is my LinkedIn <https://se.linkedin.com/in/cristian-cira-246b0933> account for some more details. My username on Zanata is *cira* Please let me know what are the next steps I have to take. Thank you, C *Cristian Cira,* PhD Application Expert in Code Optimization *PDC Center for High Performance Computing* KTH Royal Institute of Technology SE-100 44 Stockholm, Sweden *http://www.pdc.kth.se <http://www.pdc.kth.se>* Tel : +46 8 790 6309 Mob : +46 737 65 22 98

2 1

Re: [OpenStack-I18n] [openstack-dev] [i18n] [glance] ESL question 'shared' vs 'shareable'
by Ian Y. Choi 17 Nov '16

17 Nov '16

Hello devs, As a Korean translator, I also quite agree with the idea. Some images with "shared" state but actually not shared yet would be awkward, and "shareable" word would cover such context : those images can be shard but may not be shared yet (although the addition of "image members"is needed) or already shared. Hello translators, I am copying openstack-i18n(a)lists.openstack.org on this. Would you pleased think about this and share your thoughts? (Or please attend to the next i18n IRC meeting about in 9-10 hours and tell me.) With many thanks, /Ian Sean McGinnis wrote on 11/17/2016 1:44 AM: > On Wed, Nov 16, 2016 at 04:04:52PM +0000, Brian Rosmaita wrote: >> Hello Translators, >> >> We're having a discussion about a new image "visibility" value for Glance, >> and before we go too far, it would be helpful to know whether what we're >> worried about is going to matter for ESL people. >> >> Here's the situation: Since the Diablo release, Glance end users have had >> the ability to share images with other cloud users by adding "members" to >> the image. We call those "shared images". Previously, we haven't had a >> special "visibility" keyword for these, but we are introducing one now >> [0]. Here's the problem introduced by that change: >> >> (1) Members can only be added to an image if its current visibility value >> allows for it. We're going to make this an explicit visibility state that >> we ware proposing to call 'shared'. >> >> (2) An image with visibility == 'shared', however, isn't actually >> accessible to other users unless they are added as "image members". So >> it's going to be possible for a user to have some images with visibility >> == 'shared', but they aren't *really* shared with anyone yet. >> >> (3) For reasons outlined on [0], we're proposing to make this new >> visibility the default value in Glance. This will enable the current >> sharing workflow to work in a backward-compatible way. But some people >> are worried that users will panic when they see that their new images have >> visibility == 'shared' (even though no other users have access to such >> images until "image members" are added). >> >> (4) To address this, we're thinking that maybe the identifier for this >> kind of image visibility should be 'shareable'. >> >> Finally, here's my question. For an ESL person looking at these two >> identifiers (which, as identifiers, won't be translated): >> * shared >> * shareable >> >> Are the above so similar that the nuances of the discussion above would be >> lost anyway? In other words, are we just bikeshedding here, or is there a >> clear distinction? What I mean is, is the panic described above likely or >> unlikely to happen for an ESL person? >> >> thanks, >> brian > Good question. I think technically it would be shareable, which would > mean that it then able to be shared. > > Realistically though, in my opinion, calling it shared to denote that it > _can be_ shared is probably intuitive enough that there wouldn't be any > confusion about the naming. > > My 2 cents. > >> [0] https://review.openstack.org/#/c/396919/ >> >> >> __________________________________________________________________________ >> 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 > __________________________________________________________________________ > 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

Creating i18n-specs for I18n specifications
by Ian Y. Choi 09 Nov '16

09 Nov '16

Hello, Official OpenStack project teams can have specification repositories, and the specifications are published on: http://specs.openstack.org/ . As we decided on last Barcelona i18n contributor meetup (Please see number 2 part in Etherpad for more details: https://etherpad.openstack.org/p/barcelona-i18n-meetup ), I have just requested to create i18n-specs repository using the following patchsets - https://review.openstack.org/#/c/394680/ - https://review.openstack.org/#/c/394681/ Hope that more i18n activities will be documented with details and shared using this i18n-specs repo. I will notice again after i18n-specs repo will be landed successfully :) With many thanks, /Ian

3 3

Feedback is needed for I18n draft logo!
by Ian Y. Choi 09 Nov '16

09 Nov '16

Hello, On last July, i18n team decided *parrot* as i18n project mascot. OpenStack Foundation has a plan for all the official OpenStack teams to have logos based on mascots. Logos will be ready by the 1st Project Team Gathering on next February. Please see the attached figure for draft logo. The attached is a draft logo for i18n team to target Barcelona Summit for project teams to more discuss on logos. If you are interested in how illustrators worked, please refer a video: https://youtu.be/JmMTCWyY8Y4 . I18n team needs to return a feedback from the draft logo by Nov 11 (Fri) with a feedback form: http://tinyurl.com/OSmascot . Direct feedback to the URL is also fine, but please share feedback through i18n mailing list! (e.g., color, style, design, form, ...) The following is what I was received what we can expect through the logo: * A horizontal version of the logo, including your mascot, project name and the words "An OpenStack Community project" * A square(ish) version of the logo, including all of the above * A mascot-only version of the logo * Stickers for all project teams distributed at the PTG * One piece of swag that incorporates all project mascots, such as a deck of playing cards, distributed at the PTG * All digital files will be available through the website With many thanks, /Ian

5 6

I18n in BCN: I18n contributor meetup wrap up
by Ian Y. Choi 02 Nov '16

02 Nov '16

Hello! There were around total 20 participants for last I18n contributor meetup @Barcelona, including Daisy, Zanata team, Infrastructure team, Docs team, and Stackalytics team members! Thank you very much for such all kind and so active participation! Although there have been sort of time conflicts for some active translators and main contributors on other projects but who are helping i18n team a lot, we have met each other and discussed for better i18n. I think i18n team members have dealt various topics with so long time. If there was no time limit: 6pm, i18n members might have discussed much longer :) I am now transferring to go home and my final flight has been delayed about 3 hours, but thanks to such delay, I have briefly summarized now what have been discussed and what are results from I18n contributor meetup. Please see Etherpad: https://etherpad.openstack.org/p/barcelona-i18n-meetup , and "Discussed Topics and Results" (2nd) section. - Andreas Jaeger shortly visited due to his return flight and we agreed with translation job import and export criteria. I have briefly summarized in number *(1)*. - Ilya Shakhat, who is a Stackalytics core developer and maintainer, kindly participated in the meetup. If anyone is interested in Stackalytics with i18n statistics, please refer to number *(3)* for the details. - Although there is another infrastructure team meeting on the same time, Elizabeth K. Joseph and Clark Boylan came to I18n contributor meetup (thank you so much again!). Zanata upgrade *(4)* is what i18n team is really waiting for. Alex Eng and Patrick Huang from Zanata team gave some beneficial feedback (e.g., current Zanata version number and new version release plan) through IRC in real time. Moreover, I hope that some discussion of translation checksite *(5)* will yield more positive progress, although it seems that more discussion is needed. - Also, Lana from Docs team PTL visited to i18n contributor meetup, although she was leading Docs contributor meetup on the same time. Lana and me both agreed that more communication between two teams will make nice fruit *(6)*. - For i18n activities, we have differentiated and clarified the usage of web pages : Zanata dashboard, Wiki, i18n contributor guide, and so on *(2)*, and also finalizing Ocata translation plans is very important during Ocata Design Summit *(7)*! I will update Zanata dashboard according to the finalization. Because of some time restriction, some topics has not been discussed yet or just briefly mentioned. Let's also consider those topics gradually such as on the next IRC meeting. Some meetup participants took photos. Frank shared photos to Etherpad! I hope that other participants will share photos soon. Hope all to have a return flight safely. Again, thank you very much all! With many thanks, /Ian

4 5

Fwd: Feedback is needed for I18n draft logo!
by Cloud Suhartono 02 Nov '16

02 Nov '16

Hello, I just gave the OpenStack Project Mascot Feedback. Overall, our logo is good, even though, skill of parrots just follows what people say, and is not smart enough to present it. For notes, our project should presents clearly the documentation. /suh 2016-11-02 1:13 GMT+07:00 JF Taltavull <jftalta(a)gmail.com>: > Hello Ian, hello teammates, > > The draft logo looks good for me, though the black lines are a little bit > too bold, maybe... > > -JF > > On 30/10/2016 03:05, Ian Y. Choi wrote: > > Hello, > > On last July, i18n team decided *parrot* as i18n project mascot. > OpenStack Foundation has a plan for all the official OpenStack teams to > have logos > based on mascots. Logos will be ready by the 1st Project Team Gathering on > next February. > > Please see the attached figure for draft logo. > > The attached is a draft logo for i18n team to target Barcelona Summit for > project teams > to more discuss on logos. > If you are interested in how illustrators worked, please refer a video: > https://youtu.be/JmMTCWyY8Y4 . > > I18n team needs to return a feedback from the draft logo by Nov 11 (Fri) > with a feedback form: http://tinyurl.com/OSmascot . > > Direct feedback to the URL is also fine, but please share feedback through > i18n mailing list! > (e.g., color, style, design, form, ...) > > The following is what I was received what we can expect through the logo: > > * A horizontal version of the logo, including your mascot, project name > and the words "An OpenStack Community project" > * A square(ish) version of the logo, including all of the above > * A mascot-only version of the logo > * Stickers for all project teams distributed at the PTG > * One piece of swag that incorporates all project mascots, such as > a deck of playing cards, distributed at the PTG > * All digital files will be available through the website > > > > With many thanks, > > /Ian > > > _______________________________________________ > OpenStack-I18n mailing listOpenStack-I18n@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > >

2 1

Re: [OpenStack-I18n] Feedback is needed for I18n draft logo!
by Kato, Tomoyuki 02 Nov '16

02 Nov '16

Hi Ian, I do like this mascot logo. KATO Tomoyuki > Hello, > > On last July, i18n team decided *parrot* as i18n project mascot. > OpenStack Foundation has a plan for all the official OpenStack teams to > have logos > based on mascots. Logos will be ready by the 1st Project Team Gathering > on next February. > > Please see the attached figure for draft logo. > > The attached is a draft logo for i18n team to target Barcelona Summit > for project teams > to more discuss on logos. > If you are interested in how illustrators worked, please refer a video: > https://youtu.be/JmMTCWyY8Y4 . > > I18n team needs to return a feedback from the draft logo by Nov 11 (Fri) > with a feedback form: http://tinyurl.com/OSmascot . > > Direct feedback to the URL is also fine, but please share feedback > through i18n mailing list! > (e.g., color, style, design, form, ...) > > The following is what I was received what we can expect through the logo: > > * A horizontal version of the logo, including your mascot, project > name and the words "An OpenStack Community project" > * A square(ish) version of the logo, including all of the above > * A mascot-only version of the logo > * Stickers for all project teams distributed at the PTG > * One piece of swag that incorporates all project mascots, such as > a deck of playing cards, distributed at the PTG > * All digital files will be available through the website > > > > With many thanks, > > /Ian

1 0

[Bug 1637900] [NEW] 创建域、项目、用户和角色 in Installation Guide
by woolenhy 31 Oct '16

31 Oct '16

Public bug reported: ----------------------------------- Release: 0.1 on 2016-10-30 16:22 SHA: 0aec93ae3cabb0ba77ca4a0a2498b5dcaf454984 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/keystone-users.html The following are a problem? 创建域``default``： $ openstack domain create --description "Default Domain" default openstack: 'domain' is not an openstack command. See 'openstack --help'. Did you mean one of these? command list container create container delete container list container save container set container show container unset ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- 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/1637900 Title: 创建域、项目、用户和角色 in Installation Guide Status in openstack i18n: New Bug description: ----------------------------------- Release: 0.1 on 2016-10-30 16:22 SHA: 0aec93ae3cabb0ba77ca4a0a2498b5dcaf454984 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/keystone-users.html The following are a problem? 创建域``default``： $ openstack domain create --description "Default Domain" default openstack: 'domain' is not an openstack command. See 'openstack --help'. Did you mean one of these? command list container create container delete container list container save container set container show container unset To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1637900/+subscriptions

1 1

[I18n] No IRC Meeting but inviting virtual i18n contributor meetup through IRC
by Ian Y. Choi 27 Oct '16

27 Oct '16

Hello all, I18n team will not have IRC meeting in #openstack-meeting IRC channel this week, since Barcelona Summit is now on-going! :) But there will be virtual meeting time during Barcelona I18n contributor meetup. The time will be 13:00-14:00 UTC on tomorrow (Friday) (See a few different timezones: https://www.timeanddate.com/worldclock/converted.html?iso=20161028T15&p1=31… ) on *#openstack-i18n# channel, not #openstack-meeting channel. For Barcelona I18n contributor meetup and virtual meeting, please see https://etherpad.openstack.org/p/barcelona-i18n-meetup for more details. With many thanks, /Ian

1 0

Planning Barcelona Design Summit session - contributors meetup
by Ian Y. Choi 20 Oct '16

20 Oct '16

Hello, I have started to plan I18n Barcelona Design Summit session. We will have one contributors meetup on October28th (Friday) 2-6pm at Barcelona. Please see Etherpad: https://etherpad.openstack.org/p/barcelona-i18n-meetup , and write your availability on Barcelona I18n contributors meetup and/or possible discussion topics. And for contributors who could not come to Barcelona, I am planning to have 'virtual meeting time' for one hour during contributors meetup. If someone is unable to come to Barcelona but would like to participate in virtual meeting time, please write your name and time preference on survey: http://doodle.com/poll/zny89dgs53n28y56 . With many thanks, /Ian

7 21

[I18n] IRC Meeting remainder: October 20th at 07:00 UTC
by Ian Y. Choi 19 Oct '16

19 Oct '16

Hello all, I18n team is having our next meeting on October 20th (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/2016/opensta… Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Log: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Note: There will be no IRC meeting on October 27th (Thursday) at 13:00 UTC, since the next week is reserved for Barcelona Summit. Instead hope to see on October 28th (Friday) at 06:00-07:00 UTC during Barcelona I18n contributor meetup. (I will announce it later.) With many thanks, /Ian

1 0

Ocata translation group (Re: Planning Barcelona Design Summit session - contributors meetup)
by Akihiro Motoki 18 Oct '16

18 Oct '16

# The subject has been changed accordingly. 2016-10-17 21:52 GMT+09:00 Ian Y. Choi <ianyrchoi(a)gmail.com>: > Robert Simai wrote on 10/17/2016 9:28 PM: > >> On Monday 17 October 2016, 20:41:18 Ian Y. Choi <ianyrchoi(a)gmail.com> >> wrote: >> >> [...] >> >> By the way, I briefly modified the Zanata front page: >>> https://translate.openstack.org/ >>> (Also it would be great that front page visibility will be enhanced, as >>> I wrote in https://etherpad.openstack.org/p/I18n-Zanata-enhancement ) >>> If you have better idea on front page design and content, please tell me >>> :) >>> >> I see all the user facing projects are aggregated under the link >> >> "Dashboard translation (Required)" >> https://translate.openstack.org/version-group/view/newton-da >> shboard-translation >> >> for all languages. Is that the change you made? >> > Actually at that time I did not create such group. Kato-san created this > on last July I think. > > I have updated a few more on the front page, since now translating mainly > on master branch > rather than stable-newton version will be nice. > For user facing projects of Ocata translation, please see: > https://translate.openstack.org/version-group/view/ocata-das > hboard-translation/ > (I have just created such group.) I would like to see neutron-lbaas-dashboard in the Ocata dashboard translation list. In Ocata cycle, Horizon will drop LBaaS v1 from the code and neutron-lbaas-dashboard plugin supports LBaaS v2 operation. > > > > >> This is _very_ helpful as it now allows to quickly see the status. Thanks >> a >> lot! >> > Hope that the new group "Ocata dashboard translation" will be also useful > to all. :) > > > With many thanks, > > /Ian > >> >> > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >

2 1

Again Invalid openstack_dashboard/locale/id/LC_MESSAGES/django.po
by Andreas Jaeger 15 Oct '16

15 Oct '16

For stable/newton and master: http://logs.openstack.org/periodic/horizon-propose-translation-update-newto… http://logs.openstack.org/periodic/horizon-propose-translation-update/61420… It's openstack_dashboard/locale/id/LC_MESSAGES/django.po in both cases. Anybody from id team around to fix it? 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 1

[I18n] IRC Meeting remainder: October 13th at 13:00 UTC
by Ian Y. Choi 14 Oct '16

14 Oct '16

Hello all, I18n team is having our next meeting on October 13th (Thursday) at 13: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/2016/opensta… Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Log: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Note: Since I need to participate in one local event at that time, would someone (IRC meeting chair or any volunteer) start meeting? I will see the channel and tell my idea using my phone, but it is difficult to run IRC meeting using my phone.. With many thanks, /Ian

3 4

[OpenStack-I18n] openstack_dashboard/locale/id/LC_MESSAGES/django.po is invalid
by Andreas Jaeger 14 Oct '16

14 Oct '16

Could somebody check this, please? http://logs.openstack.org/periodic/horizon-propose-translation-update-newto… Thanks, 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

3 2

ironic/locale/fr/LC_MESSAGES/ironic-log-info.po is invalid
by Andreas Jaeger 14 Oct '16

14 Oct '16

Could somebody investigate this as well, please? http://logs.openstack.org/periodic/ironic-propose-translation-update/67d02f… thanks, 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 2

language specific view in Zanata
by Robert Simai 12 Oct '16

12 Oct '16

Hi, as a translator for a specific language I'm mostly interested to make sure that all relevant projects and files for my language are complete. Unfortunately in Zanata I need to access my files through Project -> Version ->-> Languages ->->-> Documents to finally see how we're doing. I'd clearly prefer to start with my language and have a more plain view of all projects (or better documents) and their status. Does anyone know if that's achievable in Zanata or would that be an enhancement request? To not consequently stringfreeze is annoying but this would at least mitigate the situation and not require clicking through each and every project, even they were known to been at 100% translated before ... -- Thanks, Robert

3 3

Next generation translation checksite
by Frank Kloeker 11 Oct '16

11 Oct '16

Dear all, maybe as you know we tried this year to bring the translation checksite on the stage. This wasn't sucessful because the developed puppet module which called DevStack rans out of time and the installation was very often broken. Not practical. Not usable. I have had a deeper look in the last days and I found out openstack-ansible could help us in this situation. There is also an All-In-One installation of OpenStack which puts all parts like Horizon separated into container. It's easy to catch the Horizon container, install the Zanata stuff and fetch the translation files periodically to show the changes of translation on the dashboard. Prototyp is running on https://i18n2.ref.app.telekomcloud.com/ I have summarized all my thoughts on the etherpad: https://etherpad.openstack.org/p/openstack-ansible-os_translation-checksite Pleass take a look and let me know if we should work in the next release cycle on this topic? kind regards Frank

4 6

No document string freeze on stable branch?
by Akihiro Motoki 11 Oct '16

11 Oct '16

Does the openstack-manuals project allow a big refactoring in **stable** branches? I saw a big refactoring on the networking guide was merged in the master branch and it was backported into stable/mitaka branch. As a result of the backport, 25% of Japanese Mitaka Networking Guide translation. I was really shocked that such thing happened in a stable branch. If the project allows such backport, translators will easily lose their translation and it implicitly means the project suggests not to translate it. I would like to know the policy of the docs stable branch maintenance. Akihiro

4 7

First translated releasenotes up
by Andreas Jaeger 11 Oct '16

11 Oct '16

FYI, Aodh is the first repo to publish translated release notes: http://docs.openstack.org/releasenotes/aodh/index.html (British English only) 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 2

What's Up, Doc? Newton Edition!
by Lana Brindley 07 Oct '16

07 Oct '16

Hi everyone, First of all, Newton docs are live on http://docs.openstack.org/ \o/ Thank you to our release managers, Olena and Alex, who have put in the hard yards over the past few weeks to get us in good shape. Thanks also to Andreas and Kato-san, for everything that they do, and to our speciality team leads and cross project liaisons. And thanks to Christian and Matt for the last minute assistance. Of course, every release belongs to all of you who have written, tested, reviewed, updated, triaged, and edited over the last six months. Well done on another successful release :) Don't forget that you can still use "#success" before a message in any OpenStack IRC channel to call out wins, they are gathered here: https://wiki.openstack.org/wiki/Successes == Progress towards Newton == Newton has been released unto the world. We fixed 479 bugs this cycle, and completed 15 blueprints. We'll begin planning for Ocata over the next couple of weeks, culminating in the Barcelona Summit 25-28 October, where we'll develop our Ocata deliverables list. Stay tuned! == The Road to Barcelona == Our docs schedule is now available here: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-sear… We are also hoping to have a docs session in the Ops track. I'll get back to you with more information on that as soon as I have it. I've requested a docs track at the PTG in Atlanta next February, which will be used for Ocata review and Pike planning. Please let me know if you intend to participate. == Core Team Reviews == Just a quick note that we won't be holding a core team review in November, as it conflicts with Summit. We'll resume these in December for the Ocata cycle. == Doc team meeting == We will take a short break and resume the normal meeting schedule after Summit. In the meantime, you can catch most of us in #openstack-doc in a variety of timezones, so feel free to drop in and ask questions any time. -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#7_October_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Re: [OpenStack-I18n] Problems with quotes in Zanata
by Alex Eng 06 Oct '16

06 Oct '16

Hi, The warning displayed on the screen is actually a validator for Java type project (.properties file) and all validator is enabled by default (that is why it is a warning). With openstack project mainly on Python, either we can disable the "Java variables validator" option for all project or translators can simply ignore the warning. Having said that, there is a small bug in the Java validator itself which discovered in this issue :) --------------------------------------------- Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com

6 7

RFC: publishing translated release notes
by Andreas Jaeger 06 Oct '16

06 Oct '16

I've done a proof of concept on how we could publish translated release notes: https://review.openstack.org/372167 I've added two open questions to the review - please look at it and give me your suggestions. If anybody comes up with a better solution, this would be more than welcome, Note that currently only 19 repos have translations for release notes - out of 197 repos that have release notes, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: 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

4 6

Announcing new I18n IRC meeting time and reminder for Oct 6 07:00 UTC
by Ian Y. Choi 06 Oct '16

06 Oct '16

Hello all, Today, I would like to announce new I18n IRC meeting time and explain detail backgrounds on new meeting time schedule. First of all, our new I18n IRC meeting time will be - odd weeks: 1 hour from 13:00 UTC (Oct 13, Oct 27, Nov 10, Nov 24, Dec 8, ...) - even weeks: 1 hour from 07:00 UTC (Oct 6, Oct 20, Nov 3, Nov 17, Dec 1, ...) Note that it is different from current schedule: 1st and 3rd week in a month, and the next I18n IRC meeting will be at *07:00 UTC on October 6th 2016* in #openstack-meeting IRC channel. We started discussions on such kind of new IRC meeting schedule from May ([1] as subsequent) but finalization was not so easy. On last I18n meeting [2], me and Kato-san discussed and agreed that changing I18n meeting time is worth. After then, since I have became Ocata PTL for six months, I needed to consider again and more. The followings are my ideas on new I18n IRC meeting time: - My participation is indeed needed. However, from October to December this year, I am not available neither or 06:00 UTC and 08:00 UTC on every Thursday. 07:00 UTC is the only available time slot for me. I really sorry for that. - Encouragement with standardization is usually the most nice way. Previous schedule (1st and 3rd week in every month) does not fit with official eavesdrop.o.o schedule [3], which may prevent more participation from contributors. In my honest opinion, following standards, documenting the logistics according to the standards, and meeting reminders to the team will be relevant steps for better I18n team. So I proposed new meeting time slots [4], revised I18n meeting information [5] with previous meeting logs [6], and now writing this e-mail. - Actually I am also busy as other translators and contributors. As you see [6], I have observed that Kato-san participated in I18n teem meeting the most, and JF Taltavull also participated in meetings. So I would like to nominate them as I18n meeting chairs, and asked the availability on both time. (07:00 UTC is fine for Kato-san and 13:00 UTC is fine for JF Taltavull.) Note that every I18n team members can start I18n meeting by using "#startmeeting OpenStack I18n Meeting" command (documented in [7]). And I would like to more focus on communications and updating related documents [5] [6] and taking actions. So from now, we will have more I18n meetings every week and it might be more number of meetings compared to current status. But I would like to see more members in meetings, and occasional participation is also fine :) If this new meeting time schedule might not fit to all, I will reconsider to revise meeting time schedule. Please feel free to tell me or here: openstack-i18n(a)lists.openstack.org . And finally, for our next meeting on UTC 07:00 October 6, the following topics are currently I think: - Newton translation result summary - Translation change criteria on Hard String freeze period - Planning I18n contributor's meetup on Ocata Design Summit - Open discussions [1] http://lists.openstack.org/pipermail/openstack-i18n/2016-June/002220.html [2] http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… [3] http://eavesdrop.openstack.org/#I18N_Team_Meeting [4] https://review.openstack.org/#/c/380998/ [5] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting [6] https://wiki.openstack.org/wiki/I18N/MeetingLogs [7] https://etherpad.openstack.org/p/i18n-meeting With many thanks, /Ian

4 4

[OpenStack-I18n] openstack_dashboard/locale/id/LC_MESSAGES/django.po broken
by Andreas Jaeger 05 Oct '16

05 Oct '16

Could somebody fix the newton file, please? For details, see http://logs.openstack.org/periodic/horizon-propose-translation-update-newto… thanks, 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 1

[I18n] PTL Candidacy
by Ian Y. Choi 04 Oct '16

04 Oct '16

Hello, I am writing to announce my candidacy for I18n Ocata PTL. I have participated in OpenStack translations into Korean since October 2014. At the first time, I was just a Korean translator and used Transifex, the previous translation platform. As I got involved more and more, I have experienced and learned a lot through the kind help from I18n members and also with many I18n activities. I went to previous two Summits and it was so happy to meet many I18n members, Zanata members, and Infra team members offline. I have committed small patches into Infra, openstack-manuals, and Stackalytics repositories for better integration with I18n. Now I am an active translator in Korean team, and also an I18n core reviewer. I am currently ranked as the third top contributor in Translations [1], and I try to leave review comments with details in openstack/i18n repository [2]. I18n team has become an official project since June last year [3]. Indeed, internationalizing OpenStack makes OpenStack ubiquitous accessible to much more members all over the world. To accomplish our team goal, we have done a lot of things including translation platform and infrastructure with the collaboration of OpenStack teams. On the other hand, it seems that currently there are still more things to do with many translators, language coordinators, and also developers. In my opinion, we need to find ways to more focus on translation qualities, and keep better track of the change in evolving OpenStack. I think I18n team is special because team members have different language backgrounds and experiences. I like this diversity. I truly believe that we can make good synergy with the diversity. In the Ocata cycle, I would like to work with I18n members for: * Translations are our first important aspect in I18n team. For better translations, more conversations and discussions with various I18n members are needed. Let's consider the ways to better communicate with language translators and coordinators. I would like to kindly discuss and cooperate with many members to share our good practices and improve OpenStack I18n Guide [4]. Also, translation support in OpenStack I18n Guide will make our significant guide internationally accessible. * Stablizing our on-going work is also important. For example, Stackalytics now shows Translations metric. However, more tunings are needed such as applying language filter, and showing translations on contribution report. Also, we need to apply appropriate ways for translators to regard as ATCs with an automated manner rather than registering as extra ATCs. * Let's facilitate I18n and Inter-Project Cross-Project Liaisons [5]. Lots of members from different project teams helped a lot. Since we have such nice Liaisons relationship with other project teams, facilitating Liaisons will be able to go for positive progress. For example, I really hope that Infrastructure/I18n Liaisons will help successfully land several on-going issues including translations check site and Zanata upgrade. I would like to appreciate previous and current great help from I18n and also many of different team members. Let's continue our effort for OpenStack to become more universal! One more thing to mention is that I am not fully familiar with all of aspects in I18n team. I need help from many members even if I will be nominated for I18n Ocata PTL. Please support and encourage me for better I18n project. [1] http://stackalytics.com/?metric=translations [2] http://stackalytics.com/report/contribution/i18n/90 [3] http://lists.openstack.org/pipermail/openstack-i18n/2015-June/001112.html [4] http://docs.openstack.org/developer/i18n/ [5] https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n With many thanks, /Ian

4 3

Newton Horizon translation (Re: Horizon: Newton RC2 tagged)
by Akihiro Motoki 03 Oct '16

03 Oct '16

Hi all translators, Some updates on horizon newton translations. * Horizon RC3 was released to include more translations. RC3 will be the Newton release. RC3 imported translations as of Sep 30 0600 UTC. * Horizon team plans to release the Newton stable update (10.0.1) soon after Newton release. Horizon translations are continuously imported into the horizon repo, so if you would like to update translations feel free to update them on Zanata. Don't worry even if you missed some translations in the Newton initial release. Akihiro 2016-09-28 17:22 GMT+09:00 Ian Y. Choi <ianyrchoi(a)gmail.com>: > Hello all translators, > > I have just found that Horizon Newton RC2 tagging was under review on > : https://review.openstack.org/#/c/378344/ and it has been just merged. > > As Akihiro-san previously mentioned, > it is unlikely for Horizon team to propose RC3 unless any further > important changes will happen. > > Thank you very much for all translators especially for this so-busy > translation period :) > > > With many thanks, > > /Ian > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >

1 0

Problems with quotes in Zanata
by Frank Kloeker 02 Oct '16

02 Oct '16

Hello, I had this week some trouble with some strings in murano-dashboard. After translation different messages Zanata sends a warning "Variables not quoted". But there is no quoting in the original message. I made a screenshot for better understanding: https://1drv.ms/f/s!AlAahwYfjwW6-T3RwIFjIPequQ7l I think it's caused by the apostroph which is not necassary in German in context with this brackets {} As workaround we set the brackets in quotes as advised but I'm not shure if this will work later in the dashboard. Maybe someone has experienced the same and can give some hints. thx Frank

3 2

What's Up, Doc? 30 September
by Lana Brindley 30 Sep '16

30 Sep '16

Hi everyone, We're on the final countdown to Newton now! The release managers Olena and Alex are busy getting the release patches ready, the Install Guide testing team are madly working through the last few sections, and Andreas and I have our fingers hovering over the big red GO button! Don't forget that you can contact any of us (or just send mail to the docs mailing list) if you have any questions about the Newton docs release. Please be aware that the core team will not be merging non-critical patches until after we've branched for Newton, particularly for the Installation Guide. We usually cut the branch about a week after Summit concludes, so you might be asked to wait until then. If that happens, a core will -2 your patch until after we've branched. == Progress towards Newton == 5 days to go! Bugs closed so far: 466 Release managers: Olena Logvinova and Alexandra Settle Release tasks are being tracked here: https://etherpad.openstack.org/p/NewtonRelease Install Guide testing is being tracked here: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting == The Road to Barcelona == I have a draft schedule up, which you can see here: https://etherpad.openstack.org/p/Ocata-DocsSessions I'll put this into Sched once the tool becomes available, and your early feedback is welcome. Additionally, if you're interested in moderating a session in Barcelona, please let me know. == Core Team Reviews == Just a quick note that we won't be holding a core team review in October, as it conflicts with release, or in November, as it conflicts with Summit. We'll resume these in December for the Newton cycle. == Doc team meeting == Next meetings: The US meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-09-28 Next meetings: APAC: Wednesday 5 October, 00:30 UTC (This will be the final meeting before release day!) US: Wednesday 12 October, 19:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#30_September_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

To language team coordinators: get ready for Mitaka translation
by Ying Chun Guo 28 Sep '16

28 Sep '16

Dear coordinators, Mitaka translation will be started at the beginning of March, and probably ended in the week of March 28. We need to get ourselves ready for Mitaka translation from now on. Because of the join of IBM professional translators, we will be able to cover more projects in our translation plan of this release. Generally, the jobs of existing community translators will not be affected, focus on Horizon, same as before. IBM translators will focus on "other" projects. Before Mitaka translation starts, there are several things you can do: 1. Update glossary. If you don't have glossary translations in i18n repo[1], or you want to update glossary translations, you can send a patch with your translations or your updates to i18n repo directly. 2. Document your local team communication method in the team wiki page[2]. While Mitaka translation starts, it's good to open your local communication channel to all of your language translators. Good communication is quite important for people from different places to work well together. 3. Join IRC channel[3] #openstack-i18n with your zanata ID As a coordinator, you have the responsibility to coordinate your language translations. A good practise is to show up in IRC and have your people to get you easily when they have troubles. If you have any questions, talk to me. My IRC ID is "Daisy" in the channel of #openstack-i18n. Thank you. Best regards Ying Chun Guo (Daisy) [1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n/locale [2] https://wiki.openstack.org/wiki/I18nTeam/team [3] https://wiki.openstack.org/wiki/IRC

9 27

Horizon: Newton RC2 tagged
by Ian Y. Choi 28 Sep '16

28 Sep '16

Hello all translators, I have just found that Horizon Newton RC2 tagging was under review on : https://review.openstack.org/#/c/378344/ and it has been just merged. As Akihiro-san previously mentioned, it is unlikely for Horizon team to propose RC3 unless any further important changes will happen. Thank you very much for all translators especially for this so-busy translation period :) With many thanks, /Ian

1 0

Lao Localization
by Saikeo Kavhanxay 26 Sep '16

26 Sep '16

Hi localization team, I am interested to localize OpenStack into my language. Currently Lao localization team is not available on OpenStack yet. I want to open it and start translate. Please suggest me how to localize OpenStack. Thank you. Best regards, Saikeo Network and System Engineer IT Dept., APB Laos [ccna_routerswitching_sm][jn_certified_associate_rgb]

4 10

Re: [OpenStack-I18n] [openstack-community] Chinese Ask OpenStack
by Ian Y. Choi 24 Sep '16

24 Sep '16

Hello Stefano! First of all, sorry for my late reply from your kind comment. (Recently I have been thinking a lot inside my brain, but most ideas are still in my head..) Thank you very much for sharing with much details. Although it has been less than 2 years since I participated in as a OpenStack Korean group organizer, I have seen lots of kind and enormous efforts and communications from you and Tom during my community activities. I really appreciate such great help and support, especially for non-English members from you and Tom, and also so many community members. I agree that ask.o.o is also an open source, and in my opinion, we, as community organizers and leaders, can encourage local developers and operators to more participate in building and maintaining ask.o.o for their languages. I really hope that more local communities will be vitalized through lots of interesting activities : not only local meetups, but also grouped development activities and more participation in OpenStack contribution including infra-side management. My actions for building Korean ask.o.o may be slow, since recently I applied to I18n Ocata PTL. but I would happily like to keep on investigating my time for building Korean ask.o.o steadily. And for I18n team, the cross-relationship with other official project teams is important, but encouraging more local language translator participation is also another significant aspect to make OpenStack ubiquitously accessible. I really want to find nice approaches how local translators will get more involved in translation with local community activities. If someone has a good idea on such perspective, feel free to kindly share opinions :) (So for this reason and FYI, I am copying my mail thread to openstack-i18n(a)lists.openstack.org) With many thanks, /Ian Stefano Maffulli wrote on 9/14/2016 3:48 PM: > On 09/11/2016 12:09 AM, Ian Y. Choi wrote: >> I am one of OpenStack Korea user group organizers. >> >> On the other hand, I really wanted to open ask.o.o for Korean >> (e.g., ask.openstack.org/ko/questions ) but I am not familiar how I can >> create or request this site. > I can elaborate on this topic, since I have followed the initial steps > of Ask OpenStack when it launched. That site exists partially because > StackExchange denied OpenStack to create something like ask.ubuntu.com > for us, and partially because I really wanted to have ask.openstack.org > in multiple languages. > > During my tenure as community manager, the Foundation sponsored the > improvement of the support for non-latin alphabets, with Chinese, > Japanese and Korean as first targets. > > But once we launched the site in Chinese, we realized that the way we > managed the site, we couldn't add more languages without increasing > dramatically the risk of breaking everything. The resources to fix the > situation were never enough to make a dramatic impact and therefore the > site has been making slow progress over the years, focusing on > stability, operational solidity and spam-prevention/fix. > > Despite having an extremely high ranking on search engines for common > openstack issues in English, ask.openstack.org never had enough > development resources to grow to the other languages. > >> So my general idea is to support more languages on ask.o.o, and >> encourage more OpenStack members to use ask.o.o globally. > I think this is still a very fair request but the answer can only be in > the Foundation or volunteers in the community, since the whole software > and infrastructure behind ask.openstack.org is open source. Languages > can be added and tested on the staging site quite easily... in theory at > least (the documentation is a bit sparse, with > http://askbot.org/doc/multilingual.html#multilingual and > http://askbot.org/doc/text-search.html#text-search being a starting > point)... but once you activate Korean language, then you'll have a > whole new site to manage... and I'm not sure what resources will be > available to fix bugs that inevitably will pop up. > > /stef > > _______________________________________________ > Community mailing list > Community(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/community

1 0

What's Up, Doc? 23 September
by Lana Brindley 23 Sep '16

23 Sep '16

Hi everyone, Newton goes out in just two weeks, and the release team and I have been busy working through release tasks in preparation. Don't forget that you can contact any of us (or just send mail to the docs mailing list) if you have any questions about the Newton docs release. I'm also pleased to announce that I have been returned as the documentation PTL for Ocata, which will be my fourth term. Thanks for all the support! == Progress towards Newton == 12 days to go! Bugs closed so far: 455 Release managers: Olena Logvinova and Alexandra Settle Release tasks are being tracked here: https://etherpad.openstack.org/p/NewtonRelease Install Guide testing is being tracked here: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting == The Road to Barcelona == * I have a draft schedule starting to take shape, which you can see here: https://etherpad.openstack.org/p/Ocata-DocsSessions I'll put this into Sched once the tool becomes available, and your early feedback is welcome. Additionally, if you're interested in moderating a session in Barcelona, please let me know. * By now, you should be well on the way to having your travel and accommodation booked for Barcelona. In case you're still working on it, though, there's travel information available on the Summit site here: https://www.openstack.org/summit/barcelona-2016/travel/ * Looking a little further forward, Foundation have now announced that the first Project Team Gathering (PTG) will be held in Atlanta, US, on Feb 20-24: http://www.openstack.org/ptg == Doc team meeting == Next meetings: The APAC meeting was skipped this week. Next meetings: US: Wednesday 28 September, 19:00 UTC APAC: Wednesday 5 October, 00:30 UTC These two meetings will be the final meetings before release day. Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#23_September_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

UNOFFICIAL horizon check site
by Akihiro Motoki 23 Sep '16

23 Sep '16

Hi, The official translation check site is not planned for Newton, so I set up an unofficial horizon translation check site for Japanese team. There is no reason not to share it to the community. URL: http://v157-7-133-23.myvps.jp/dashboard Username: 'demo' or 'admin' Password: b2949da771d1 * The site is updated manually and occasionally when I want to. * Only core services (+ Heat) are covered. No additional services are covered. * The site will be closed or switched to Ocata sometime after Newton release is shipped. No announcement is planned. * The site is sometimes used for development purpose. * This is a voluntary site. Do not ask me to update :) Akihiro

5 7

[Bug 1587221] [NEW] openstack-manuals stable-mitaka releasenotes on Zanata looks unnecessary
by Akihiro Motoki 20 Sep '16

20 Sep '16

Public bug reported: As we discussed at Austin, only the master version is required for release notes translation on Zanata. Zanata currently has openstack- manuals stable-mitaka releasenotes resource. It looks unnecessary. ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: infra -- 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/1587221 Title: openstack-manuals stable-mitaka releasenotes on Zanata looks unnecessary Status in openstack i18n: New Bug description: As we discussed at Austin, only the master version is required for release notes translation on Zanata. Zanata currently has openstack- manuals stable-mitaka releasenotes resource. It looks unnecessary. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1587221/+subscriptions

2 1