- OpenStack-I18n - lists.openstack.org

[Bug 1710787] [NEW] CSV data is not the target for translation
by Ian Y. Choi 17 Aug '17

17 Aug '17

Public bug reported: CSV data in https://docs.openstack.org/i18n/latest/atc-stats/pike.html is not the target for translation. The strings in CSV data needs to be excluded in *.pot and *.po files. ** Affects: openstack-i18n Importance: Undecided Assignee: minwook shin (minwook-shin) Status: New ** Summary changed: - Old "translation tools" link in I18n contributor guide + CSV data is not the target for translation ** Description changed: - In https://docs.openstack.org/i18n/latest/contributing.html , - "translation tools" link page is https://wiki.openstack.org/wiki/I18n/Tools , but - it guides users to go to https://docs.openstack.org/i18n/latest/tools.html . - - So "translation tools" link page needs to be changed to - https://docs.openstack.org/i18n/latest/tools.html . + CSV data in https://docs.openstack.org/i18n/latest/atc-stats/pike.html is not the target for translation. + The strings in CSV data needs to be excluded in *.pot and *.po files. ** Changed in: openstack-i18n Assignee: (unassigned) => minwook shin (minwook-shin) -- 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/1710787 Title: CSV data is not the target for translation Status in openstack i18n: New Bug description: CSV data in https://docs.openstack.org/i18n/latest/atc-stats/pike.html is not the target for translation. The strings in CSV data needs to be excluded in *.pot and *.po files. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1710787/+subscriptions

2 1

[Bug 1710785] [NEW] Old I18n contributor guide link in /ocata, /newton, ...
by Ian Y. Choi 16 Aug '17

16 Aug '17

Public bug reported: In https://docs.openstack.org/ocata/ , I18n contributor guide link is https://docs.openstack.org/developer/i18n/ . This document is not maintained anymore and need to be redirected into https://docs.openstack.org/i18n/latest/ ** Affects: openstack-i18n Importance: Undecided Assignee: LEE SEUNGWOO (jaeseung172) Status: New ** Changed in: openstack-i18n Assignee: (unassigned) => LEE SEUNGWOO (jaeseung172) -- 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/1710785 Title: Old I18n contributor guide link in /ocata, /newton, ... Status in openstack i18n: New Bug description: In https://docs.openstack.org/ocata/ , I18n contributor guide link is https://docs.openstack.org/developer/i18n/ . This document is not maintained anymore and need to be redirected into https://docs.openstack.org/i18n/latest/ To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1710785/+subscriptions

1 1

[Bug 1710788] [NEW] Old "translation tools" link in I18n contributor guide
by Ian Y. Choi 15 Aug '17

15 Aug '17

Public bug reported: In https://docs.openstack.org/i18n/latest/contributing.html , "translation tools" link page is https://wiki.openstack.org/wiki/I18n/Tools , but it guides users to go to https://docs.openstack.org/i18n/latest/tools.html . So "translation tools" link page needs to be changed to https://docs.openstack.org/i18n/latest/tools.html . ** Affects: openstack-i18n Importance: Undecided Assignee: ChJR (chjr) Status: New ** Changed in: openstack-i18n Assignee: (unassigned) => ChJR (chjr) -- 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/1710788 Title: Old "translation tools" link in I18n contributor guide Status in openstack i18n: New Bug description: In https://docs.openstack.org/i18n/latest/contributing.html , "translation tools" link page is https://wiki.openstack.org/wiki/I18n/Tools , but it guides users to go to https://docs.openstack.org/i18n/latest/tools.html . So "translation tools" link page needs to be changed to https://docs.openstack.org/i18n/latest/tools.html . To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1710788/+subscriptions

2 1

[I18n] Announcing a virtual sprint
by Ian Y. Choi 14 Aug '17

14 Aug '17

Hello team, I would like to open a virtual sprint with @ujuc on August 15 01:00-09:00 UTC to see I18n issues with development knowledge. For more details, please see https://wiki.openstack.org/wiki/VirtualSprints#I18n_Team_Virtual_Sprint_wit… Note that the event will be co-held with a sprint in Pycon Korea 2017 : https://www.pycon.kr/2017/program/sprint/9 . The brief summary is: "The sprint aims to understand various types of contributions (translation, documentation, translation tool maintenance, bug fixes) in I18n team. Participants in this sprint are highly encouraged to choose one part among various types of contributions, and submit a Gerrit patch in openstack/i18n repository." With many thanks, /Ian

1 0

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