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

[Bug 1628371] [NEW] OpenStack API文档 in Openstack-API-Documentation
by zhongtian 24 Oct '17

24 Oct '17

Public bug reported: 使用OpenStack API来启动服务器实力(应该是实例) ----------------------------------- Release: 0.1 on 2016-09-26 05:01 SHA: 3df6009c9272583e58ae90476aaf179b4dbfb21f 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/1628371 Title: OpenStack API文档 in Openstack-API-Documentation Status in openstack i18n: New Bug description: 使用OpenStack API来启动服务器实力(应该是实例) ----------------------------------- Release: 0.1 on 2016-09-26 05:01 SHA: 3df6009c9272583e58ae90476aaf179b4dbfb21f 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/1628371/+subscriptions

2 1

[Bug 1586041] [NEW] Incorrect PO-Revision-Date in some translation files for aodh project
by Alfredo Moralejo 03 Aug '17

03 Aug '17

Public bug reported: Following .po files have empty revision date, "PO-Revision-Date: \n": aodh/locale/it/LC_MESSAGES/aodh.po aodh/locale/pt_BR/LC_MESSAGES/aodh.po aodh/locale/zh_CN/LC_MESSAGES/aodh-log-info.po aodh/locale/zh_CN/LC_MESSAGES/aodh.po aodh/locale/zh_TW/LC_MESSAGES/aodh.po This makes compile_catalog to fail: $ python setup.py compile_catalog running compile_catalog compiling catalog aodh/locale/ja/LC_MESSAGES/aodh.po to aodh/locale/ja/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/ru/LC_MESSAGES/aodh.po to aodh/locale/ru/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/pt/LC_MESSAGES/aodh.po to aodh/locale/pt/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/en_GB/LC_MESSAGES/aodh.po to aodh/locale/en_GB/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/ko_KR/LC_MESSAGES/aodh.po to aodh/locale/ko_KR/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/de/LC_MESSAGES/aodh.po to aodh/locale/de/LC_MESSAGES/aodh.mo Traceback (most recent call last): File "setup.py", line 29, in <module> pbr=True) File "/usr/lib64/python2.7/distutils/core.py", line 151, in setup dist.run_commands() File "/usr/lib64/python2.7/distutils/dist.py", line 953, in run_commands self.run_command(cmd) File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command cmd_obj.run() File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/frontend.py", line 178, in run self._run_domain(domain) File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/frontend.py", line 218, in _run_domain catalog = read_po(infile, locale) File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/pofile.py", line 217, in read_po _add_message() File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/pofile.py", line 165, in _add_message catalog[msgid] = message File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/catalog.py", line 601, in __setitem__ self.mime_headers = _parse_header(message.string).items() File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/catalog.py", line 420, in _set_mime_headers self.revision_date = _parse_datetime_header(value) File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/catalog.py", line 46, in _parse_datetime_header tt = time.strptime(match.group('datetime'), '%Y-%m-%d %H:%M') File "/usr/lib64/python2.7/_strptime.py", line 467, in _strptime_time return _strptime(data_string, format)[0] File "/usr/lib64/python2.7/_strptime.py", line 325, in _strptime (data_string, format)) ValueError: time data u'' does not match format '%Y-%m-%d %H:%M' I've checked in https://translate.openstack.org that files are wrong there too, not only in github. ** 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/1586041 Title: Incorrect PO-Revision-Date in some translation files for aodh project Status in openstack i18n: New Bug description: Following .po files have empty revision date, "PO-Revision-Date: \n": aodh/locale/it/LC_MESSAGES/aodh.po aodh/locale/pt_BR/LC_MESSAGES/aodh.po aodh/locale/zh_CN/LC_MESSAGES/aodh-log-info.po aodh/locale/zh_CN/LC_MESSAGES/aodh.po aodh/locale/zh_TW/LC_MESSAGES/aodh.po This makes compile_catalog to fail: $ python setup.py compile_catalog running compile_catalog compiling catalog aodh/locale/ja/LC_MESSAGES/aodh.po to aodh/locale/ja/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/ru/LC_MESSAGES/aodh.po to aodh/locale/ru/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/pt/LC_MESSAGES/aodh.po to aodh/locale/pt/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/en_GB/LC_MESSAGES/aodh.po to aodh/locale/en_GB/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/ko_KR/LC_MESSAGES/aodh.po to aodh/locale/ko_KR/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/de/LC_MESSAGES/aodh.po to aodh/locale/de/LC_MESSAGES/aodh.mo Traceback (most recent call last): File "setup.py", line 29, in <module> pbr=True) File "/usr/lib64/python2.7/distutils/core.py", line 151, in setup dist.run_commands() File "/usr/lib64/python2.7/distutils/dist.py", line 953, in run_commands self.run_command(cmd) File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command cmd_obj.run() File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/frontend.py", line 178, in run self._run_domain(domain) File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/frontend.py", line 218, in _run_domain catalog = read_po(infile, locale) File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/pofile.py", line 217, in read_po _add_message() File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/pofile.py", line 165, in _add_message catalog[msgid] = message File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/catalog.py", line 601, in __setitem__ self.mime_headers = _parse_header(message.string).items() File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/catalog.py", line 420, in _set_mime_headers self.revision_date = _parse_datetime_header(value) File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/catalog.py", line 46, in _parse_datetime_header tt = time.strptime(match.group('datetime'), '%Y-%m-%d %H:%M') File "/usr/lib64/python2.7/_strptime.py", line 467, in _strptime_time return _strptime(data_string, format)[0] File "/usr/lib64/python2.7/_strptime.py", line 325, in _strptime (data_string, format)) ValueError: time data u'' does not match format '%Y-%m-%d %H:%M' I've checked in https://translate.openstack.org that files are wrong there too, not only in github. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1586041/+subscriptions

2 1

[Bug 1659349] [NEW] [French] Delete instance translated incorrectly
by Mateusz Kowalski 30 Jul '17

30 Jul '17

Public bug reported: In French version "Delete Instance" in Horizon interface is translated as "Supprimer le l'instance" for the singular form, whereas the correct one is "Supprimer l'instance". ** 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/1659349 Title: [French] Delete instance translated incorrectly Status in openstack i18n: New Bug description: In French version "Delete Instance" in Horizon interface is translated as "Supprimer le l'instance" for the singular form, whereas the correct one is "Supprimer l'instance". To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1659349/+subscriptions

2 1

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

15 Mar '17

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

3 9

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

11 Mar '17

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

6 18

Fwd: [OpenStack-docs] OpenStack Individual Board Member nomination
by Ian Y. Choi 14 Feb '17

14 Feb '17

Hello translators, I am forwarding one e-mail to share that 1) OpenStack Individual Board Member election will be held in Jan 9-13 2017 for 2017 Board Election. 2) Kato-san is seeking nominations :) Note that I am now on the candidate list because I wanted to check who nominated me, but I will not go for 2017 Board Election. I am now busy but so happy on serving I18n Ocata PTL :) With many thanks, /Ian -------- Original Message -------- Subject: [OpenStack-docs] OpenStack Individual Board Member nomination Date: Tue, 6 Dec 2016 15:41:59 +1000 From: Lana Brindley <openstack(a)lanabrindley.com> To: OpenStack Manuals <openstack-docs(a)lists.openstack.org> Hi everyone, One of our core team members, Tomoyuki KATO, is seeking election for the OpenStack board. In order to stand for candidacy, though, he needs 10 nominations. If you think Tomoyuki-san would be a good addition to the Board, then you can nominate him by going to http://www.openstack.org/community/members/ and searching for "Tomoyuki KATO". No supporting documentation required, just a click if you think he'd be a good candidate :) Voting for the accepted candidates happens in January. Lana -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

2 3

[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 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

[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

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