- OpenStack-I18n - lists.openstack.org

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 07 Aug '17

07 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 05 Aug '17

05 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 03 Aug '17

03 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 03 Aug '17

03 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