- OpenStack-I18n - lists.openstack.org

[StringFreeze] Horizon RC1 tagged and has stable-pike version in Zanata
by Ian Y. Choi 11 Aug '17

11 Aug '17

Hello translators, As Rob Cresswell (Horizon team Pike PTL) announced, Horizon RC1 was tagged : http://lists.openstack.org/pipermail/openstack-dev/2017-August/121038.html , which implies that it is a good timing for translators to do translations and translation review activities to reflect better quality of translations into Pike release. If you see "Pike Dashboard Translation Group" : https://translate.openstack.org/version-group/view/pike-dashboard-translati… , some projects are "stable-pike" versions, not master versions. Please do more translation and translation review contributions on "stable-pike" versions if exist. Horizon team said that it is worth to have RC2. Please take more care of stable versions :) Also, thanks to the kind advice from Andreas Jaeger, I have emphasize "Translation merge" activities to developers : http://lists.openstack.org/pipermail/openstack-dev/2017-August/121072.html . With many thanks, /Ian

1 0

Welcome a new i18n-core and explanation on extra ATCs
by Ian Y. Choi 07 Aug '17

07 Aug '17

Hello, I would like to happily announce a new i18n core: Robert Simai. The following is the analysis from current i18n core reviewer(s): - Robert Simai is now active, an ATC (translation count) [1], has made commits on openstack-manuals regarding i18n [2], and also has been serving as a German I18n language coordinator for years. Actually, I suggested to propose more i18n core reviewers, but it seems that more agreement or recommendation is needed. If you have a good suggestion for i18n core reviewers, please do not hesitate to share your thoughts to I18n PTL or current i18n core reviewers. The list of current i18n core reviewers is available at [3]. For extra ATCs, I submitted as seen in [4] for active translators and/or reviewers and the result was accepted by Technical Committee. To become an extra ATC (of course, I18n team hopes to automate the process of proposing as extra ATCs for active translators and/or reviewers), a member needs to be a "Foundation Member". More details are explained in [5] - thanks a lot, @fungi! With many thanks, /Ian [1] https://git.openstack.org/cgit/openstack/governance/tree/reference/projects… [2] https://review.openstack.org/#/q/owner:%22Robert+Simai+%253Crobert.simai%25… [3] https://review.openstack.org/#/admin/groups/1132,members (login to Gerrit is needed to see) [4] https://wiki.openstack.org/wiki/I18nTeam/ATC_statistics#Pike_cycle_.282017-… [5] http://lists.openstack.org/pipermail/openstack-i18n/2017-August/003000.html

4 3

[openstack-dev][Docs][Elections] PTL candidacy for Queens
by Chason 06 Aug '17

06 Aug '17

Hello everyone, I would like to announce my candidacy for Documentation PTL (Queens). First of all, I wish to introduce myself briefly. I have been working on the bugs of openstack-manuals project since the Liberty release. And the most I fixed is the bugs of the Install Guide. In my opinion, Openstack is not very friendly with new hand. If they install their first openstack environment according to our Install Guide which may not be very accurate, she or he would be in a mess. I will continue to focus on document bugs whether as a reviewer or PTL. In this cycle, Alex( asettle) has coordinated the doc migration work [1]. I wish to take this opportunity to thank all members of the OpenStack community who partcipated in this work. We cannot achieve such seriously bug stuff without your cooperation. :) As you can see, we removed several guides from openstack-manuals project. There are still many things [2] we have not yet to accomplished after the doc migration. Some of these problems we already have solutions. But the others need to be discussed. We are welcome everyone to join in our discussion[3]. It would be wonderful if you can give us some ideas! If I am elected PTL of the Documentation project, my focuses for the coming release are to grow the Documentation team, keep the accuracy of documents, and work closely with other projects to help them imporve documents. Thanks for your consideration, and I am looking forward to work together with all of you on getting the OpenStack documents to the next stage. Cheers, Chason Email: chason.chan(a)foxmail.com IRC: chason Launchpad: chen-xing [1] https://etherpad.openstack.org/p/doc-migration-tracking [2] https://etherpad.openstack.org/p/doc-future-problems [3] https://etherpad.openstack.org/p/denver-doc-PTG

1 0

VPNaaS dashboard (Re: [StringFreeze] Soft period was over - Plz contribute translation for the release!)
by Akihiro Motoki 06 Aug '17

06 Aug '17

> Note that VPNaaS panel in horizon was split out into a horizon plugin, > but it is not an official project, so we cannot use the translation platform, > so we will lose existing translations in Pike. If someone has > interests in translating VPNaaS dashboard, > feel free to contact me (I am a maintainer of VPNaaS dashboard) and I > can consider including some > translations manually. I am thinking it for Japanese at the moment. neutron-vpnaas-dashboard cannot use Zanata for translation (from the reason above), so we need to maintain translation manually if actually needed. I extracted translated strings from Ocata horizon translations and you can find it at [1]. The status is like this [2] and almost all fuzzy strings are caused by the addition of ' =' to existing strings, so the fix would be small. I am not sure how many folks are interested in keeping VPNaaS dashboard, but if you are interested to update translations feel free to update the review [1] or send me an updated version of your translation. For Japanese translation I reviewed the new version and it has been merged into the repository [2]. If you find some bugs or improvements, feel free to propose a fix or let me know. Thanks, Akihiro [1] https://review.openstack.org/#/c/491201/ [2] http://paste.openstack.org/show/617600/ [3] https://review.openstack.org/#/c/491200/ 2017-08-02 19:57 GMT+09:00 Akihiro Motoki <amotoki(a)gmail.com>: > 2017-08-01 3:30 GMT+09:00 Ian Y. Choi <ianyrchoi(a)gmail.com>: >> Dear language coordinators & translators! >> >> Only a few weeks left before official Pike release [1] and I would like to >> inform >> you that the last week was the Soft StringFreeze period. >> >> 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) >> - Magnum UI (Medium) >> - Trove Dashboard (Medium) >> - Sahara Dashboard (Medium) >> - neutron-lbaas-dashboard (Medium) >> - Murano Dashboard (Low) >> - Designate Dashboard (Low) >> - TripleO UI (Low) > > Could you add neutron-fwaas-dashboard to the above list? > FWaaS panel in horizon in the past releases has been split out to a > separate horizon plugin in Pike. > I think it is worth translating neutron-fwaas-dashboard in Pike and > existing users can see the same level of translations. > Translation would be easy enough so I think we have translation memory. > > Regarding the priority, I am not sure what Medium priority means. > High and Low might be enough, but I have no strong opinions. > > Note that VPNaaS panel in horizon was split out into a horizon plugin, > but it is not an official project, so we cannot use the translation platform, > so we will lose existing translations in Pike. If someone has > interests in translating VPNaaS dashboard, > feel free to contact me (I am a maintainer of VPNaaS dashboard) and I > can consider including some > translations manually. I am thinking it for Japanese at the moment. > > Thanks, > Akihiro > > >> >> >> All of those and more additional target projects grouped in [2] in *master* >> branch >> and current & next PTL will check feature freeze status on projects listed >> above. >> He will create a stable version: *stable-pike* in Zanata for the target >> projects after the project have stable/pike branch. >> >> 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 (about 2 weeks of RC1, then >> HardStringFreeze). >> >> For more details on how I18n team is doing with releases (especially Horizon >> & plugin projects), please see [3]. >> >> If you have questions, feel free to ask through >> openstack-i18n at 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/pike/schedule.html >> [2] >> https://translate.openstack.org/version-group/view/pike-dashboard-translati… >> [3] https://docs.openstack.org/i18n/latest/release_management.html >> >> >> 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

Re: [OpenStack-I18n] [openstack-dev] [Cinder] string freeze exception for VMAX driver
by Ian Y. Choi 04 Aug '17

04 Aug '17

Hello Helen, Thanks a lot for sharing a string freeze exception request to openstack-dev mailing list. With @amotoki's comment [1] and the discussion on the last IRC meeting yesterday [2], I18n team is fine and there will be no problem to accept the requests from I18n team's perspective. Note that String Freeze has been important for Docs & I18n team to acknowledge string freeze status and take appropriate actions of what needs to be changed to documentation and translation activities if needed. Since I18n team now more focuses on dashboard translations [1] and documents are being migrated [3], I think the importance of string freeze for server projects (e.g., cinder, nova, keystone, neutron) might be less important than previous cycle(s), but sharing the status to all the teams including release management team is a good idea to stay on the same page as much as possible :) With many thanks, /Ian, I18n team Ocata PTL. [1] http://lists.openstack.org/pipermail/openstack-i18n/2017-August/002999.html [2] http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… [3] http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migra… Walsh, Helen wrote on 8/3/2017 5:21 PM: > > *To whom it may concern,* > > I would like to request a string freeze exception for 2 patches that > are on the merge queue for Pike. > > 1.VMAX driver - align VMAX QOS settings with front end (CI Passed) > > https://review.openstack.org/#/c/484885/7/cinder/volume/drivers/dell_emc/vm… > line 800 (removal of exception message) > > Although it’s primary aim is to align QoS with front end setting it > indirectly fixes a lazy loading error we were seeing around QoS which > occasionally > > Broke CI on previous patches. > > 2.VMAX driver - seamless upgrade from SMI-S to REST (CI Pending) > > https://review.openstack.org/#/c/482138/19/cinder/volume/drivers/dell_emc/v… > line 1400 ,1455 (message changes) > > This is vital for as reuse of volumes from Ocata to Pike. In Ocata we > used SMIS to interface with the VMAX, in Pike we are using REST. A > few changes needed to be made to make this transition as seamless as > possible. > > Thank you, > > Helen > > > > __________________________________________________________________________ > 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

2 3

[docs][ptl] Candidacy for Docs
by Petr Kovar 04 Aug '17

04 Aug '17

Hi all, I'd like to announce my candidacy for PTL of the docs project for Queens. I've been active in various open source documentation and translation projects since 2007 and started contributing to OpenStack docs during the Mitaka cycle, both upstream and in the RDO Project. The docs project has recently seen a significant decrease in both the number of submitted updates and contributors, but thanks to a group of dedicated people in the community, we've managed to come up with a clear plan to migrate docs over to individual projects, restructure them and reduce the scope to keep them maintainable. This is now well underway and I'd like to help the team and the community drive and continue with this work. In docs, we generally like to keep it rather short and simple, so let me summarize the main three points as follows: Support and help drive the remaining tasks in restructuring and/or moving content from the core docs suite. Help establish the docs team as content editors for individual project docs when needed or requested. Stay open and friendly to new contributors, no matter if they are prospective core members or drive-by docs contributors, with the understanding that docs are a great way to get involved in the project for both the non- and developers. Thank you, pk -- Petr Kovar Sr. Technical Writer | Customer Content Services Red Hat Czech, Brno

1 0

Translation bugs on Chinese China
by Akihiro Motoki 04 Aug '17

04 Aug '17

Hi Chinese language coordinator and translators, We received several number of bug reports on Chinese China translations, but unlike other languages they have not been triaged and fixed. 9 of 13 open bugs looks related to Chinese China. Can anyone from Chinese China handle these bugs? Check bugs on https://bugs.launchpad.net/openstack-i18n Unless we have good volunteers, we cannot handle translated bugs. Thanks, amotoki

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

Re: [OpenStack-I18n] IMPORTANT upcoming change to technical elections
by Jeremy Stanley 02 Aug '17

02 Aug '17

I just posted an announcement to openstack-dev which is also relevant to some subscribers of this ML who may not see it there: http://lists.openstack.org/pipermail/openstack-dev/2017-July/119786.html If possible, please follow up there with any questions. -- Jeremy Stanley

1 1

Re: [OpenStack-I18n] [openstack-dev] string freeze exception for VMAX driver
by Akihiro Motoki 02 Aug '17

02 Aug '17

I am not sure who is responsible to respond to string freeze exception, but I will comment it as my hat of the i18n team. Looking at "cinder" translation status [1], the best progress is ~73% and 718 of 2932 message are remaining. In other languages the progress is lower. Adding two new messages does not matter. Removing messages has no problem. I see no blocking issue in this request. In addition, I think the i18n team focuses on dashboard translations and server projects are less focused for translations. IIRC the I18n team discussed an idea to announce the i18n team focus on translation to let server projects be free from string freeze around the beginning of the Pike cycle but I am not sure it is announced or not. Thanks, Akihiro [1] https://translate.openstack.org/iteration/view/cinder/master/documents?docI… 2017-08-03 3:14 GMT+09:00 Walsh, Helen <Helen.Walsh(a)dell.com>: > > > > > To whom it may concern, > > > > I would like to request a string freeze exception for 2 patches that are on > the merge queue for Pike. > > > > 1. VMAX driver - align VMAX QOS settings with front end (CI Passed) > > https://review.openstack.org/#/c/484885/7/cinder/volume/drivers/dell_emc/vm… > line 800 (removal of exception message) > > > > Although it’s primary aim is to align QoS with front end setting it > indirectly fixes a lazy loading error we were seeing around QoS which > occasionally > > Broke CI on previous patches. > > > > > > 2. VMAX driver - seamless upgrade from SMI-S to REST (CI Pending) > > https://review.openstack.org/#/c/482138/19/cinder/volume/drivers/dell_emc/v… > line 1400 ,1455 (message changes) > > > > This is vital for as reuse of volumes from Ocata to Pike. In Ocata we used > SMIS to interface with the VMAX, in Pike we are using REST. A few changes > needed to be made to make this transition as seamless as possible. > > > > Thank you, > > Helen > > > > > > > __________________________________________________________________________ > 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

Re: [OpenStack-I18n] [OpenStack-docs] Summary of how I18n affects with doc-migration
by Doug Hellmann 02 Aug '17

02 Aug '17

[resending to the lists] > On Aug 1, 2017, at 10:55 AM, Doug Hellmann <doug(a)doughellmann.com> wrote: > > Excerpts from Andreas Jaeger's message of 2017-08-01 08:57:09 +0200: >> On 2017-07-31 22:46, Doug Hellmann wrote: >>> Excerpts from Ian Y. Choi's message of 2017-08-01 03:16:09 +0900: >>>> [...] >>>> 2. Draft index page for translated documents was also removed >>>> >>>> Previously, Docs team maintained draft documents for the master branch >>>> (which will be the stable branch >>>> after the official release and the document stables) on >>>> https://docs.openstack.org/draft/draft-index.html page. >>>> It also contained translated draft documents and I18n team accessed the >>>> page to see whether translated documents >>>> render well or not, and also review translated strings. >>>> >>>> I did not notice when I saw the spec [1], but recently, I noticed that >>>> the the draft-index.html page was deprecated >>>> by [next-release-name]/index.haml (e.g., >>>> https://docs.openstack.org/pike/index.html ) [4]. >>>> >>>> Since I18n team encourages translation review for the better quality of >>>> translations, it is a good idea to see >>>> draft documents before language landing pages have the link to fully >>>> translated and reviewed documents. >>> >>> Is it possible to see the draft of a translation by reviewing the >>> output of the job that proposes the patch containing the translated >>> text? >> >> Currently not, it needs publishing to docs-draft and a way to access the >> multiple documents. Note this needs handling for both openstack-manuals >> and project repos like neutron (networking-guide). > > Could we make it work that way? I understand why we need a separate > review step for the translations, but not why we need a separate > copy of the docs published outside of the context of a job in order > to perform that review. (This is probably just me not understanding > how a tool works.) > >> >>>> Motoki-san proposed an idea of translation status support using an yaml >>>> file in openstack-manuals [5], >>>> and I would like to discuss with I18n team how we deal with the change >>>> of draft index page. >>> >>> How would that flag or information be used? >>> >> >> WE could just have the link to it added - dependent on the flag - to either: >> * language index >> * draft index > > It seems like we want a list of languages for which there are > translations for a given set of docs. We could use that to populate > templates in a few different ways (link from the English version > to the other languages, link from a $language landing page to all > of the guides in that language, etc.). > > I can advise someone on how to add those features, if we have a > volunteer. > > Doug

3 4

[StringFreeze] Soft period was over - Plz contribute translation for the release!
by Ian Y. Choi 02 Aug '17

02 Aug '17

Dear language coordinators & translators! Only a few weeks left before official Pike release [1] and I would like to inform you that the last week was the Soft StringFreeze period. 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) - Magnum UI (Medium) - Trove Dashboard (Medium) - Sahara Dashboard (Medium) - neutron-lbaas-dashboard (Medium) - Murano Dashboard (Low) - Designate Dashboard (Low) - TripleO UI (Low) All of those and more additional target projects grouped in [2] in *master* branch and current & next PTL will check feature freeze status on projects listed above. He will create a stable version: *stable-pike* in Zanata for the target projects after the project have stable/pike branch. 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 (about 2 weeks of RC1, then HardStringFreeze). For more details on how I18n team is doing with releases (especially Horizon & plugin projects), please see [3]. If you have questions, feel free to ask through openstack-i18n at 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/pike/schedule.html [2] https://translate.openstack.org/version-group/view/pike-dashboard-translati… [3] https://docs.openstack.org/i18n/latest/release_management.html With many thanks, /Ian

4 3

French member with no role
by Akihiro Motoki 02 Aug '17

02 Aug '17

Hi French team coordinators, I see one member in French language team has no role. What does this mean? Is he considered as a translator? This is just a question and to clarify the situation. I see a warning every time I run a script to sync Zanata users list into the i18n repo. Thanks, Akihiro

2 3

[Elections] Candidacy for I18n PTL (Queens)
by Frank Kloeker 01 Aug '17

01 Aug '17

Good morning! Today I would like to announce my candidacy as I18n PTL in Queens cycle. I've been in the OpenStack Community since 2015, active as a translator in the German team. I participated in my first OpenStack Summit in Tokyo and met the I18n team for the first time at the Design Summit. It was an exciting moment to meet people from all over the world working on the same thing. It is not just translations, but working with different cultures, views and ... time zones. These are the magical dimensions and challenges. After Tokyo we had virtual midcycle sprint to develop the translation check site, one of the tools to help translators in their work. I met more people during Barcelona Summit and sank deeper and deeper into the work of OpenStack and I18n. In Boston we had our own session to show the work of the I18n team. We prepared a workshop also which was not so successful, but the preparation was great and we can repeat it at any time. At this point I would like to thank Ianychoi for his excellent work in the past as PTL. He is tireless, full of energy, and brought I18n far forward. He was for me in the last weeks a kind of mentor to learn all the things related to I18n and PTL. Nevertheless, I still need support from the entire team to successfully manage this task. What goals have I set for myself for Queens: 1. Completion of the translation check site. I have been involved in this project since 2015 and now it has to be finished :-) 2. Automate all the things. We have some manual work in I18n and our tools that are to automate to make the work easier. 3. Aquire more people to the team. We have great teams that do a lot. But we also get more work through translate new OpenStack projects or the User Survey. I hope I have given a good overview. Contact me directly if you have any questions or requests. On good cooperation in a new cycle of OpenStack! kind regards Frank Email: eumel(a)arcor.de IRC: eumel8 Twitter: eumel_8 OpenStack Profile: https://www.openstack.org/community/members/profile/45058/frank-kloeker

2 1

Re: [OpenStack-I18n] [OpenStack-docs] Summary of how I18n affects with doc-migration
by Andreas Jaeger 01 Aug '17

01 Aug '17

On 2017-07-31 22:46, Doug Hellmann wrote: > [...] > This is good to know. I am going to need someone who knows how the > translation jobs work to help set those up. I can assist, but I do not > know how they work so I cannot lead that effort. Doug, I'm happy to have a discussion with you - and anybody else - on these. We can do a special IRC session or some kind of videochat. Who else wants to join? Once I know participants, let's set up something... 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

Re: [OpenStack-I18n] [OpenStack-docs] Summary of how I18n affects with doc-migration
by Andreas Jaeger 31 Jul '17

31 Jul '17

On 2017-07-31 22:46, Doug Hellmann wrote: > Excerpts from Ian Y. Choi's message of 2017-08-01 03:16:09 +0900: >> [...] >> 2. Draft index page for translated documents was also removed >> >> Previously, Docs team maintained draft documents for the master branch >> (which will be the stable branch >> after the official release and the document stables) on >> https://docs.openstack.org/draft/draft-index.html page. >> It also contained translated draft documents and I18n team accessed the >> page to see whether translated documents >> render well or not, and also review translated strings. >> >> I did not notice when I saw the spec [1], but recently, I noticed that >> the the draft-index.html page was deprecated >> by [next-release-name]/index.haml (e.g., >> https://docs.openstack.org/pike/index.html ) [4]. >> >> Since I18n team encourages translation review for the better quality of >> translations, it is a good idea to see >> draft documents before language landing pages have the link to fully >> translated and reviewed documents. > > Is it possible to see the draft of a translation by reviewing the > output of the job that proposes the patch containing the translated > text? Currently not, it needs publishing to docs-draft and a way to access the multiple documents. Note this needs handling for both openstack-manuals and project repos like neutron (networking-guide). >> Motoki-san proposed an idea of translation status support using an yaml >> file in openstack-manuals [5], >> and I would like to discuss with I18n team how we deal with the change >> of draft index page. > > How would that flag or information be used? > WE could just have the link to it added - dependent on the flag - to either: * language index * draft index 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

Summary of how I18n affects with doc-migration
by Ian Y. Choi 31 Jul '17

31 Jul '17

Hello translators, The OpenStack manuals project migration [1] has been going well, and I would like to share what I have found which things influence on I18n activities from the perspective of translators, since some translators asked me about missing some openstack-manuals documents in Zanata. 1. Removal of documents in openstack-manuals project in Zanata In [2], the following documents are not currently visible : admin-guide, arch-design, networking-guide, ops-guide, user-guide . For several release cycles, there have been less amount contribution on admin-guide (migrating to each project tree) and arch-design (deprecated). For networking-guide, translating in stable-ocata will be preserved, but master version was removed and the content will be migrated into neutron repository. User-guide will be migrated and divided between the horizon repository and python-openstackclient repository. If the strings for the migrated projects (admin-guide, networking-guide, and user-guide) would be the same as the removed strings in openstack-manuals, I18n team expects that translation memory merge functionality in Zanata would be able to fill out translations for the migrated projects. Note that the translation support work of migrated documents will be started after the migration completes and I18n team need volunteers for the work. 2. Draft index page for translated documents was also removed Previously, Docs team maintained draft documents for the master branch (which will be the stable branch after the official release and the document stables) on https://docs.openstack.org/draft/draft-index.html page. It also contained translated draft documents and I18n team accessed the page to see whether translated documents render well or not, and also review translated strings. I did not notice when I saw the spec [1], but recently, I noticed that the the draft-index.html page was deprecated by [next-release-name]/index.haml (e.g., https://docs.openstack.org/pike/index.html ) [4]. Since I18n team encourages translation review for the better quality of translations, it is a good idea to see draft documents before language landing pages have the link to fully translated and reviewed documents. Motoki-san proposed an idea of translation status support using an yaml file in openstack-manuals [5], and I would like to discuss with I18n team how we deal with the change of draft index page. 3. Archiving translated documents is also needed Liberty translated documents (e.g., [6]) and translated documents which were migrated (e.g., [7], [8]) are still accessible through docs.o.o. In my opinion, those translated documents are also the target of archiving documents [9]. For translated documents, I think just publishing htmls as read-only (e.g., github pages?) would be fine, and the work needs volunteers. With many thanks, /Ian [1] http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migra… [2] https://translate.openstack.org/iteration/view/openstack-manuals/master/doc… [3] https://translate.openstack.org/iteration/view/openstack-manuals/stable-oca… [4] https://docs.openstack.org/pike/index.html [5] http://git.openstack.org/cgit/openstack/openstack-manuals/tree/www/project-… [6] https://docs.openstack.org/liberty/ko_KR/install-guide-ubuntu/ [7] https://docs.openstack.org/ja/user-guide/ [8] https://docs.openstack.org/ja/ops-guide/ [9] http://specs.openstack.org/openstack/docs-specs/specs/pike/archiving.html [10] https://etherpad.openstack.org/p/denver-doc-PTG

2 1

[I18n] Denver PTG Planning
by Ian Y. Choi 31 Jul '17

31 Jul '17

Hello, PTG (Project Team Gathering) is also important for I18n team to meet upstream project developers in person to discuss priorities for the upcoming cycle, iterate quickly on solutions for complex issues, and make fast progress on critical items with many horizontal projects, and also better internationalize to vertical projects with discussion. I have created an Etherpad for I18n team planning on next Denver PTG. Please share your idea on the Etherpad: https://etherpad.openstack.org/p/denver-i18n-PTG . I really wanted to go to Denver PTG to discuss more I18n issues with many cross project teams including Docs, Infra, Release Mgmt., and also find how more projects would be able to better internationalized with the discussion of many project team members. However, due to my busy life with my new job, I unfortunately am not able to attend to the next PTG. Hope that I18n people will go to the PTG, and meet upstream project developers with interesting topics. Note that the due of PTG travel support application is by August 6th. With many thanks, /Ian

1 0

[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

[Bug 1671367] Re: Losing a semicolon in overview page
by Akihiro Motoki 30 Jul '17

30 Jul '17

** No longer affects: horizon ** 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/1671367 Title: Losing a semicolon in overview page Status in openstack i18n: New Bug description: Losing a semicolon Behind the "This Period's RAM-Hours". Semicolons should use Chinese, but using the English a semicolon. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1671367/+subscriptions

1 0

[Bug 1661454] Re: Inadequate Japanese translation for "Browse" on App Catalog tab
by Akihiro Motoki 30 Jul '17

30 Jul '17

As the report said, this is not a bug. ** Changed in: openstack-i18n 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: Invalid 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 1700907] [NEW] Miss translation in Get Image document
by Tomonobu Niwa 30 Jul '17

30 Jul '17

Public bug reported: In https://docs.openstack.org/ja/image-guide/obtain-images.html, the explanations for other images (CentOS, Ubuntu, etc.) are correct but that of cirros is wrong as bellow. The original version: In a CirrOS image, the login account is cirros. The Japanese version: CirrOS イメージでは、ログインアカウントは「cirros「です。 It should be CirrOS イメージでは、ログインアカウントは cirros です。 as same as other images. ** 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/1700907 Title: Miss translation in Get Image document Status in openstack i18n: New Bug description: In https://docs.openstack.org/ja/image-guide/obtain-images.html, the explanations for other images (CentOS, Ubuntu, etc.) are correct but that of cirros is wrong as bellow. The original version: In a CirrOS image, the login account is cirros. The Japanese version: CirrOS イメージでは、ログインアカウントは「cirros「です。 It should be CirrOS イメージでは、ログインアカウントは cirros です。 as same as other images. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1700907/+subscriptions

2 1

[Bug 1536226] Re: Not all .po files compiled
by Akihiro Motoki 30 Jul '17

30 Jul '17

we decided to drop translation support for log strings, so we no longer need to move this forward. As an umbrella bug in openstack-i18n, this bug should be marked as Won't Fix. ** Changed in: openstack-i18n Status: New => Won't Fix -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1536226 Title: Not all .po files compiled Status in Cinder: Fix Released Status in Glance: In Progress Status in heat: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in openstack i18n: Won't Fix Bug description: python setup.py compile_catalog only compiles one <domain>.po file per language to a <domain>.mo file. By default <domain> is the project name, that is nova.po. This means all other nova-log-*.po files are never compiled. The only way to get setup.py compile the other files is calling it several times with different domains set, like for instance `python setup.py --domain nova-log-info` and so on. Since this is not usual, it can be assumed that the usual packages don't contain all the .mo files. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1536226/+subscriptions

1 0

[Bug 1675298] Re: automatic generation of LANGUAGES list in settings.py
by Akihiro Motoki 30 Jul '17

30 Jul '17

horizon patch will be released as part of Pike. This can be closed in openstack-i18n now. ** Changed in: openstack-i18n Status: New => Fix Released -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1675298 Title: automatic generation of LANGUAGES list in settings.py Status in OpenStack Dashboard (Horizon): Fix Released Status in openstack i18n: Fix Released Bug description: At now, LANGUAGES list in openstack_dashboard/settings.py is updated manually. It is better to generate the language list automatically based on the existence of PO files. In horizon, there are four types of PO files ([horizon/locale, openstack_dashboard] * [django, djangojs]). It looks better to check whether all four types of PO files exist in the repo and list such languages. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1675298/+subscriptions

1 0

[Bug 1706270] [NEW] Need redirect URL on FWaaS in Networking Guide
by Youhei Tooyama 25 Jul '17

25 Jul '17

Public bug reported: This URL are 404. http://docs.openstack.org/admin-guide-cloud/networking_introduction.html#fi… Need redirect URL. /admin-guide-cloud to New pages. http://docs.openstack.org/admin-guide-cloud/ ----------------------------------- Release: 0.9 on 2016-11-24 07:57 SHA: cc8b39934de4de69e5235ca8e5c4d4b567d0f418 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/networki… URL: https://docs.openstack.org/liberty/ja/networking-guide/adv-config-fwaas.html ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: networking-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/1706270 Title: Need redirect URL on FWaaS in Networking Guide Status in openstack i18n: New Bug description: This URL are 404. http://docs.openstack.org/admin-guide-cloud/networking_introduction.html#fi… Need redirect URL. /admin-guide-cloud to New pages. http://docs.openstack.org/admin-guide-cloud/ ----------------------------------- Release: 0.9 on 2016-11-24 07:57 SHA: cc8b39934de4de69e5235ca8e5c4d4b567d0f418 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/networki… URL: https://docs.openstack.org/liberty/ja/networking-guide/adv-config-fwaas.html To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1706270/+subscriptions

2 1

Fwd: Re: Translations-test site
by Ian Y. Choi 18 Jul '17

18 Jul '17

Hello infra team (copying: openstack-i18n mailing list), I18n team initially proposed a spec for translation checksite about two years ago [1], and the specification was revised [2] by making use of OpenStackAnsible with the help of Horizon team [3]. Three teams have been communicating a lot and now we think that it is time to deploy translate checksite using OpenStackAnsible into openstack-infra side. Would you help us to successfully deploy translate checksite into openstack-infra? It would be much nice if such deployment is accomplished by around R-5 [4], since Soft and Hard StringFreezes are important for translators, but it we do not have enough time to prepare by then, it would be also nice to prepare translate checksite for the next cycle. I am copying & pasting a recent message from Frank to share up-to-date status on translate checksite implementation status. =========== We are nearly done with the developement of translation check site. At the moment I'm doing some test with the work from Andy but basicly it's realized as described in [5] Now it's time to think about the installation on openstack-infra site. I think we need a new server with Ubuntu Xenial, clone the git repo [6] and run the script on [7]. Finaly with need a cron job to sync the translation files periodically. The question is what you need for the installation. Is it a puppet manifest like [8] or you prefer a new format? The installation of the site takes up to 50-60 min. This was a problem in the past for running puppet. But we need the time only for a fresh installation. Later we can refresh code with git pull as ansible task or manually. kind regards Frank =========== With many thanks, /Ian [1] https://review.openstack.org/#/c/184559/ [2] https://review.openstack.org/#/c/440825/ [3] http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_ch… [4] https://releases.openstack.org/pike/schedule.html [5] http://git.openstack.org/cgit/openstack-infra/infra-specs/tr ee/specs/translation_check_site.rst [6] http://git.openstack.org/cgit/openstack/openstack-ansible/tree/ [7] http://git.openstack.org/cgit/openstack/openstack-ansible/tr ee/scripts/gate-check-commit.sh [8] https://review.openstack.org/#/c/276466/

3 2

Fwd: [tripleo] I18n-themed Deep Dive - July 6th
by Julie Pichon 16 Jul '17

16 Jul '17

Hi, During the IRC meeting this morning [1], Ian mentioned a talk I'm planning to do for the TripleO team about I18n in tripleo-ui, and also a bit about the processes. If you're interested in attending, you're welcome to! It's right after the IRC meeting next week. Regards, Julie [1] http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… ---------- Forwarded message ---------- From: Julie Pichon <jpichon(a)redhat.com> Date: 29 June 2017 at 16:22 Subject: [tripleo] I18n-themed Deep Dive - July 6th To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev(a)lists.openstack.org> Hi folks, As I mentioned during the weekly meeting on Tuesday, I'd like to do a short i18n-themed deep dive during next week's slot (Thu July 6th, 14:00 UTC). I'll use my BlueJeans at [1] and updated the deep dives etherpad [2] with that information. There should be two broad topics: - Life and journey of a string - From when it gets introduced in tripleo-ui, goes through infra, up to Zanata, and then back - I'd also like to share some debugging tips, and how the infra jobs work - Working with the I18n team - The role of the I18n cross-project liaison - How we interact with the team in general, how to make their work easier - Governance, release schedule & string freezes, particularly as a cycle-trailing project I mentioned this presentation at the I18n meeting this morning and several people expressed an interest in attending, it could be a nice opportunity for both devs & translators to see another side of the work. If there's something in particular you'd like me to touch on, feel free to bring it up. The talk will be recorded and I'll post a transcript as well. Regards, Julie [1] https://bluejeans.com/4050564424/ [2] https://etherpad.openstack.org/p/tripleo-deep-dive-topics

3 6

[I18n] IRC Meeting reminder: July 6th at 13:00 UTC
by Ian Y. Choi 06 Jul '17

06 Jul '17

Hello all, I18n team is having our next meeting on July 6th 2017 (Thursday) at 13:00 UTC in #openstack-meeting IRC channel. I have not updated the topics yet but previous meeting logs are available at : http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/ . With many thanks, /Ian

1 1

[Bug 1682010] [NEW] the configuration file /etc/mongodb.conf should be /etc/mongod.conf
by zenglulu 01 Jul '17

01 Jul '17

Public bug reported: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [x] I have a fix to the document that I can paste below including example: input and output. /etc/mongod.conf If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode ----------------------------------- Release: 0.1 on 2017-03-20 12:49 SHA: abc274532d229d2083df0d95d707393521e3d162 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/mitaka/zh_CN/install-guide-ubuntu/environment-no… ** Affects: openstack-i18n Importance: Undecided Assignee: zenglulu (zengluul) Status: New ** Tags: install-guide ** Changed in: openstack-i18n Assignee: (unassigned) => zenglulu (zengluul) -- 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/1682010 Title: the configuration file /etc/mongodb.conf should be /etc/mongod.conf Status in openstack i18n: New Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [x] I have a fix to the document that I can paste below including example: input and output. /etc/mongod.conf If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode ----------------------------------- Release: 0.1 on 2017-03-20 12:49 SHA: abc274532d229d2083df0d95d707393521e3d162 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/mitaka/zh_CN/install-guide-ubuntu/environment-no… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1682010/+subscriptions

2 1

[I18n] IRC Meeting reminder: March 30th at 13:00 UTC
by Ian Y. Choi 28 Jun '17

28 Jun '17

Hello all, I18n team is having our next meeting on March 30th 2017 (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/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

2 10

[Bug 1700321] [NEW] 네트워킹 (neutron) 개념 in Installation Guide
by fisache 24 Jun '17

24 Jun '17

Private bug reported: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode ----------------------------------- Release: 0.1 on 2017-06-12 11:12 SHA: 1865f28305fdb1eb6b5e1a434ac7e292c3421513 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/mitaka/ko_KR/install-guide-rdo/neutron-concepts.… ** Affects: openstack-i18n Importance: Undecided Status: Invalid ** 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/1700321 Title: 네트워킹 (neutron) 개념 in Installation Guide Status in openstack i18n: Invalid Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode ----------------------------------- Release: 0.1 on 2017-06-12 11:12 SHA: 1865f28305fdb1eb6b5e1a434ac7e292c3421513 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/mitaka/ko_KR/install-guide-rdo/neutron-concepts.… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1700321/+subscriptions

1 1

tr_TR is broken for sahara_dashboard
by Andreas Jaeger 19 Jun '17

19 Jun '17

From http://logs.openstack.org/periodic/sahara-dashboard-propose-translation-upd… 2017-06-19 06:39:00.785324 | + trans='sahara_dashboard/locale/tr_TR/LC_MESSAGES/django.po:1375: '\''msgid'\'' and '\''msgstr'\'' entries do not both end with '\''\n'\'' 2017-06-19 06:39:00.785416 | sahara_dashboard/locale/tr_TR/LC_MESSAGES/django.po:2747: '\''msgid'\'' and '\''msgstr'\'' entries do not both end with '\''\n'\'' 2017-06-19 06:39:00.785437 | msgfmt: found 2 fatal errors 2017-06-19 06:39:00.785456 | 551 translated messages.' Could anybody fix the string, please? 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

horizon/dashboard Translation sync broken?
by Andreas Jaeger 19 Jun '17

19 Jun '17

Looking at http://status.openstack.org/openstack-health/#/g/build_queue/periodic?group… I see lots of failures for horizon related projects. Is there anybody that can look into this, 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

3 4

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

16 Jun '17

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

2 1

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

14 Jun '17

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

1 1

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

06 Jun '17

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

2 1

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

31 May '17

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

2 1

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

25 May '17

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

2 1

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

23 May '17

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

4 5

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

22 May '17

Public bug reported: In Newton release, Japanese install manual describes to register Ocata repository when installing OpenStack packages, while that of English version explains to install Newton repository. Japanese tutorials: openSUSE: https://docs.openstack.org/newton/ja/install-guide-obs/environment-packages… CentOS: https://docs.openstack.org/newton/ja/install-guide-rdo/environment-packages… Ubuntu: https://docs.openstack.org/newton/ja/install-guide-ubuntu/environment-packa… ** Affects: openstack-i18n Importance: Undecided Status: New -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1686339 Title: Wrong repository in Japanese install tutorials Status in openstack i18n: New Bug description: In Newton release, Japanese install manual describes to register Ocata repository when installing OpenStack packages, while that of English version explains to install Newton repository. Japanese tutorials: openSUSE: https://docs.openstack.org/newton/ja/install-guide-obs/environment-packages… CentOS: https://docs.openstack.org/newton/ja/install-guide-rdo/environment-packages… Ubuntu: https://docs.openstack.org/newton/ja/install-guide-ubuntu/environment-packa… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1686339/+subscriptions

2 1

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

22 May '17

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

1 0

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

18 May '17

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

1 0

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

10 May '17

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

3 3

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

09 May '17

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

3 2

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

04 May '17

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

2 1

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

24 Apr '17

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

1 0

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

24 Apr '17

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

1 0

Survey for Zanata platform
by Alex Eng 24 Apr '17

24 Apr '17

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

6 6

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

10 Apr '17

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

2 1

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

07 Apr '17

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

1 0