- OpenStack-I18n - lists.openstack.org

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

20 Nov '16

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

1 0

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

20 Nov '16

Public bug reported: In Zanata, document 'doc/admin-guide/source/locale/admin-guide' of openstack-manuals, some strings like 'vm2', 'doc/admin- guide/source/locale/admin-guide', 'd693db9e-a7cf-45ef-a7c9-b3ecb5f22645' are waiting for translation, while, which don't need to be translated. I think there should be a way to stop them from being shown in Zanata. Thanks. ** Affects: openstack-i18n Importance: Undecided Status: New -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1612201 Title: Some strings which needn't translation appear in Zanata Status in openstack i18n: New Bug description: In Zanata, document 'doc/admin-guide/source/locale/admin-guide' of openstack-manuals, some strings like 'vm2', 'doc/admin- guide/source/locale/admin-guide', 'd693db9e-a7cf-45ef- a7c9-b3ecb5f22645' are waiting for translation, while, which don't need to be translated. I think there should be a way to stop them from being shown in Zanata. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1612201/+subscriptions

2 1

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

20 Nov '16

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

1 0

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

20 Nov '16

Public bug reported: section of PUBLIC_INTERFACE_NAME ----------------------------------- Release: 0.1 on 2016-10-30 16:22 SHA: 0aec93ae3cabb0ba77ca4a0a2498b5dcaf454984 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/neutron-controller… ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1637920 Title: 网络选项2：私有网络配置Linuxbridge代理中[linux_bridge]部分应为 physical_interface_mappings = provider:PUBLIC_INTERFACE_NAME Status in openstack i18n: New Bug description: section of PUBLIC_INTERFACE_NAME ----------------------------------- Release: 0.1 on 2016-10-30 16:22 SHA: 0aec93ae3cabb0ba77ca4a0a2498b5dcaf454984 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/neutron-controller… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1637920/+subscriptions

2 1

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

20 Nov '16

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

1 1

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

18 Nov '16

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

1 0

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

17 Nov '16

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

2 1

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

17 Nov '16

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

1 0

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

09 Nov '16

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

3 3

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

09 Nov '16

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

5 6

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

03 Nov '16

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

4 5

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

02 Nov '16

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

2 1

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

02 Nov '16

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

1 0

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

31 Oct '16

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

1 1

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

27 Oct '16

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

1 0

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

20 Oct '16

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

7 21

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

19 Oct '16

Hello all, I18n team is having our next meeting on October 20th (Thursday) at 07:00 UTC in #openstack-meeting IRC channel. You can find meeting agenda here: https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting#Agenda_for_next_me… Anyone is welcome to add topics on Wiki If you missed previous IRC meeting or want to refresh, please see last IRC meeting minutes and full logs: Minutes: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Log: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Note: There will be no IRC meeting on October 27th (Thursday) at 13:00 UTC, since the next week is reserved for Barcelona Summit. Instead hope to see on October 28th (Friday) at 06:00-07:00 UTC during Barcelona I18n contributor meetup. (I will announce it later.) With many thanks, /Ian

1 0

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

18 Oct '16

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

2 1

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

15 Oct '16

For stable/newton and master: http://logs.openstack.org/periodic/horizon-propose-translation-update-newto… http://logs.openstack.org/periodic/horizon-propose-translation-update/61420… It's openstack_dashboard/locale/id/LC_MESSAGES/django.po in both cases. Anybody from id team around to fix it? Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 1

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

14 Oct '16

Hello all, I18n team is having our next meeting on October 13th (Thursday) at 13:00 UTC in #openstack-meeting IRC channel. You can find meeting agenda here: https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting#Agenda_for_next_me… Anyone is welcome to add topics on Wiki :) If you missed previous IRC meeting or want to refresh, please see last IRC meeting minutes and full logs: Minutes: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Log: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Note: Since I need to participate in one local event at that time, would someone (IRC meeting chair or any volunteer) start meeting? I will see the channel and tell my idea using my phone, but it is difficult to run IRC meeting using my phone.. With many thanks, /Ian

3 4

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

14 Oct '16

Could somebody check this, please? http://logs.openstack.org/periodic/horizon-propose-translation-update-newto… Thanks, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 2

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

14 Oct '16

Could somebody investigate this as well, please? http://logs.openstack.org/periodic/ironic-propose-translation-update/67d02f… thanks, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 2

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

12 Oct '16

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

3 3

Next generation translation checksite
by Frank Kloeker 12 Oct '16

12 Oct '16

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

4 6

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

12 Oct '16

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

4 7

First translated releasenotes up
by Andreas Jaeger 11 Oct '16

11 Oct '16

FYI, Aodh is the first repo to publish translated release notes: http://docs.openstack.org/releasenotes/aodh/index.html (British English only) Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 2

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

07 Oct '16

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

1 0

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

07 Oct '16

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

6 7

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

07 Oct '16

I've done a proof of concept on how we could publish translated release notes: https://review.openstack.org/372167 I've added two open questions to the review - please look at it and give me your suggestions. If anybody comes up with a better solution, this would be more than welcome, Note that currently only 19 repos have translations for release notes - out of 197 repos that have release notes, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

4 6

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

06 Oct '16

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

4 4

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

05 Oct '16

Could somebody fix the newton file, please? For details, see http://logs.openstack.org/periodic/horizon-propose-translation-update-newto… thanks, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 1

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

04 Oct '16

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

4 3

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

03 Oct '16

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

1 0

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

03 Oct '16

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

3 2

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

30 Sep '16

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

1 0

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

28 Sep '16

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

9 27

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

28 Sep '16

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

1 0

Lao Localization
by Saikeo Kavhanxay 26 Sep '16

26 Sep '16

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

4 10

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

24 Sep '16

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

1 0

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

23 Sep '16

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

1 0

UNOFFICIAL horizon check site
by Akihiro Motoki 23 Sep '16

23 Sep '16

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

5 7

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

21 Sep '16

Public bug reported: As we discussed at Austin, only the master version is required for release notes translation on Zanata. Zanata currently has openstack- manuals stable-mitaka releasenotes resource. It looks unnecessary. ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: infra -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1587221 Title: openstack-manuals stable-mitaka releasenotes on Zanata looks unnecessary Status in openstack i18n: New Bug description: As we discussed at Austin, only the master version is required for release notes translation on Zanata. Zanata currently has openstack- manuals stable-mitaka releasenotes resource. It looks unnecessary. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1587221/+subscriptions

2 1

[Bug 1571100] Re: 技术因素 in OpenStack 架构设计指南 - 当前最新
by Ian Y. Choi 21 Sep '16

21 Sep '16

Hmm.. I cannot check "Won't fix". Instead, I will triage as "Opinion". ** Changed in: openstack-i18n Status: Confirmed => Opinion -- 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/1571100 Title: 技术因素 in OpenStack 架构设计指南 - 当前最新 Status in openstack i18n: Opinion Bug description: Error "Redia"是一个key-value存储系统 Redis是一个key-value存储系统 ----------------------------------- Built: 2015-11-24T07:19:53 00:00 git SHA: ed0b07948cdc10b7fb962ec8aba3c3cb299fe053 URL: http://docs.openstack.org/zh_CN/arch-design/content/technical-consideration… source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishlang/generated/zh_CN/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml xml:id: technical-considerations-general-purpose To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1571100/+subscriptions

1 0

[Bug 1535172] Re: Wrong typesetting in Chinese OpenStack Mitaka and master install doc
by Ian Y. Choi 21 Sep '16

21 Sep '16

Thanks a lot for your comment, Shengjing! ** Summary changed: - Wrong typesetting in Chinese OpenStack Liberty install doc + Wrong typesetting in Chinese OpenStack Mitaka and master install doc ** Changed in: openstack-i18n Status: Confirmed => Fix Released -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1535172 Title: Wrong typesetting in Chinese OpenStack Mitaka and master install doc Status in openstack i18n: Fix Released Bug description: Extra underline in the doc. The translated link is http://docs.openstack.org/liberty/zh_CN/install-guide-rdo/glance-install.ht… The original doc link is http://docs.openstack.org/liberty/install-guide-rdo/glance-install.html The picture is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1535172/+subscriptions

1 0

[Bug 1608992] [NEW] [api-quick-start] Some old translated pages are still being seen
by Ian Y. Choi 21 Sep '16

21 Sep '16

Public bug reported: Previously, API quick start documentation was xml-based format (with maven build). Since all the API quick start content is written as RST format now, docs.openstack.org/api/quick-start/ url is redirected to current API quick start URL like http://developer.openstack.org/api-guide/quick-start/index.html . I have found some of current problems which can be interpreted as bugs: - Not all translated RST documentation is visible : Although current translation is ~100% in Chinese (zh_CN), http://docs.openstack.org/zh_CN/api/quick-start/content/index.html (xml based) is okay, but http://developer.openstack.org/zh_CN/api-guide/quick-start/ url is not working. - No redirection to rst based documentation : For example, when users enter the previous Japanese API quick-start using docs.openstack.org/ja/api/quick-start/ , the old page is still being seen. On the other hand, English docs.openstack.org/api/quick-start url is redirected to current API quick start URL like http://developer.openstack.org/api-guide/quick-start/index.html . - Even though translation progress seems to be good, there is no rst- based generated documentation for zh_CN (Chinese) and id (Indonesia) So, currently, my approach to address this bug is: 1) Identify which languages have good progress on api-quick-start translation 2) Include that those languages need to build 3) After checking the documentation result on public web pages, we need to add url redirection. ** Affects: openstack-api-site Importance: Undecided Assignee: Ian Y. Choi (ianychoi) Status: In Progress ** Affects: openstack-i18n Importance: Undecided Assignee: Ian Y. Choi (ianychoi) Status: New ** Also affects: openstack-api-site Importance: Undecided Status: New ** Changed in: openstack-api-site Assignee: (unassigned) => Ian Y. Choi (ianychoi) ** Changed in: openstack-i18n Assignee: (unassigned) => Ian Y. Choi (ianychoi) -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1608992 Title: [api-quick-start] Some old translated pages are still being seen Status in openstack-api-site: In Progress Status in openstack i18n: New Bug description: Previously, API quick start documentation was xml-based format (with maven build). Since all the API quick start content is written as RST format now, docs.openstack.org/api/quick-start/ url is redirected to current API quick start URL like http://developer.openstack.org/api-guide/quick-start/index.html . I have found some of current problems which can be interpreted as bugs: - Not all translated RST documentation is visible : Although current translation is ~100% in Chinese (zh_CN), http://docs.openstack.org/zh_CN/api/quick-start/content/index.html (xml based) is okay, but http://developer.openstack.org/zh_CN/api-guide/quick-start/ url is not working. - No redirection to rst based documentation : For example, when users enter the previous Japanese API quick-start using docs.openstack.org/ja/api/quick-start/ , the old page is still being seen. On the other hand, English docs.openstack.org/api/quick-start url is redirected to current API quick start URL like http://developer.openstack.org/api-guide/quick-start/index.html . - Even though translation progress seems to be good, there is no rst- based generated documentation for zh_CN (Chinese) and id (Indonesia) So, currently, my approach to address this bug is: 1) Identify which languages have good progress on api-quick-start translation 2) Include that those languages need to build 3) After checking the documentation result on public web pages, we need to add url redirection. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-api-site/+bug/1608992/+subscriptions

1 3

What happens in openstack-manual on Zanata?
by Akihiro Motoki 20 Sep '16

20 Sep '16

Hi, I see many many 'common' in openstack-manual project on Zanata? https://translate.openstack.org/iteration/view/openstack-manuals/master/doc… 'common' in openstack-manuals are linked into individual guides and they are uploaded by accident. Is there any change around upstream_translation_update.sh ? Akihiro

4 3

First stable/newton branches created
by Andreas Jaeger 20 Sep '16

20 Sep '16

Could somebody please set up stable-newton branches for those projects that should get translations of them, please? With RC1 today, projects are creating stable/newton branches now, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

4 14

[horizon] Question on a singular/plural string use in openstack_dashboard
by Ian Y. Choi 19 Sep '16

19 Sep '16

Hello, Recently, thanks to the help from Andreas, I am investigating on a broken job for the translation import of Horizon project [1]. The actual error message is : openstack_dashboard/locale/ko_KR/LC_MESSAGES/django.po:8273: a format specification for argument 'req' doesn't exist in 'msgstr[0]' And then I have found that this error was from a string in horizon - openstack_dashboard [2] error_message = ungettext_lazy( 'The requested instance cannot be launched as you only ' 'have %(avail)i of your quota available. ', 'The requested %(req)i instances cannot be launched as you ' 'only have %(avail)i of your quota available.', count) params = {'req': count, 'avail': available_count} In i18n translation infrastructure, only one of two (for singular and plural) strings should be selected, translated, saved, and finally imported back to Horizon project as [1]. However, the first string only used "%(avail)i" string variable, and the second string used both "%(req)i" and "%(avail)i" string variables. Since one Korean translator selected the first string, there will be no "%(req)i" in Korean po file, which generates such an error. So my suggestion is to use the same string variables for both two strings when we use ungettext_lazy function. Is it a bug from Horizon? Would it be other issues when we change like : from 'The requested instance cannot be launched as you only ' to 'The requested %(req)i instance cannot be launched as you only '? [1] http://logs.openstack.org/periodic/horizon-propose-translation-update/c038a… [2] http://git.openstack.org/cgit/openstack/horizon/tree/openstack_dashboard/da… With many thanks, /Ian

4 8

Re: [OpenStack-I18n] [openstack-dev] [stable] [all] Regarding string freeze and back ports involving translatable strings
by Ian Y. Choi 18 Sep '16

18 Sep '16

Hello, First of all, a little bit sorry for following this thread late. I am a Korean translator. Translation is also one of important and vital parts within OpenStack "Big Tent". Although the hard string freeze period before final release date is only for 3 weeks, many I18n language teams focus on translations during that period intensively. For example, Horizon translation results on lots of languages have been already included since several past releases. For nova and many other projects, the translation focus depends on different language teams. Luigi Toscano wrote on 9/12/2016 9:04 PM: > On Friday, 9 September 2016 14:12:51 CEST Matt Riedemann wrote: >> On 9/9/2016 1:58 PM, Ben Swartzlander wrote: >>> On 09/08/2016 08:37 PM, Matt Riedemann wrote: >>>> On 9/8/2016 7:05 PM, Ravi, Goutham wrote: >>>>> Hi, >>>>> >>>>> >>>>> >>>>> I was looking for some clarity around backports of bug fixes that >>>>> qualify the stable branch policy [1]. >>>>> <http://docs.openstack.org/project-team-guide/stable-branches.html#appro >>>>> priate-fixes> >>>>> >>>>> >>>>> What is the policy if the fix introduces a new translatable string or >>>>> modifies an existing one? >>>>> >>>>> The guidelines in Release management [2] >>>>> <http://docs.openstack.org/project-team-guide/release-management.html> >>>>> regarding string freeze do not specifically call this scenario out. I >>>>> see that while translatable strings are mostly avoided, some projects >>>>> have been merging changes to stable branches with introduction of new >>>>> translatable strings. >>>>> >>>>> >>>>> >>>>> The question is reminiscent of one posed in the ML a few releases ago >>>>> [3]; >>>>> <http://lists.openstack.org/pipermail/openstack-dev/2015-September/07394 >>>>> 2.html> >>>>> >>>>> >>>>> but applies to stable branches. Should we allow changes to translatable >>>>> strings for bug fixes that matter, or is it better to always deny them >>>>> for the sake of translation accuracy? >>>> The former IMO, a high severity bug fix trumps a translation. Note that >>>> some projects are translated on the stable branches too, I know this is >>>> the case for Nova. >>>> >>>> If it's a user-facing change, like an error message in the API, then it >>>> might require a bit more careful consideration, but if it's just a log >>>> message marked for translation that an end user of the API wouldn't see >>>> anyway, then I think it's fine to backport it. >>> So this stance makes sense to me, but I can't reconcile it with the >>> "hard string freeze" rules. Is the theory that after we release, the >>> string freeze ends for the stable branch, and that the hard string >>> freeze only exists for that 3 week period between RC1 and final release, >>> or is the theory that hard string freeze is always subject to exceptions >>> for "critical" bug fixes? >>> >> I treat it as the former. > Interesting: I'm not a translator in the OpenStack project, but I contribute > as translator to other Free Software communities and I would thought as the > latter as more appropriate. Stable is stable and string changes should be > approved on a case-by-case, otherwise translator's life can be more > complicated especially when the next release is translated. > > But as I said I'm not a translator here. > Currently my suggestion is the latter, not former, and if some exception is needed, then writing and sharing such as http://lists.openstack.org/pipermail/openstack-i18n/2016-September/002402.h… would be nice. However, it seems that there are some more things to be elaborated such as: - Need to identify how many projects are interested in translation especially for hard string freeze in different language teams - Although strings are hard-freezed, some strings will not appropriate to be translatable. It can be from misuse of ungettext() and ungettext_lazy() functions. - Or translators may find source string typos. Should they be included into stable branch? - Notification to exceptional cases to I18n team is needed. - ... I would like to copy this thread to openstack-i18n mailing list, and also discuss those things with many translators to find great solutions. If there is some better idea, please share it :) With many thanks, /Ian

1 0

Stop
by Sonny TADJER 18 Sep '16

18 Sep '16

Stop Sent from my iPad > On 17 Sep 2016, at 13:00, openstack-i18n-request(a)lists.openstack.org wrote: > > Send OpenStack-I18n mailing list submissions to > openstack-i18n(a)lists.openstack.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > or, via email, send a message with subject or body 'help' to > openstack-i18n-request(a)lists.openstack.org > > You can reach the person managing the list at > openstack-i18n-owner(a)lists.openstack.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OpenStack-I18n digest..." > > > Today's Topics: > > 1. Re: First stable/newton branches created (Akihiro Motoki) > 2. Re: First stable/newton branches created (Andreas Jaeger) > 3. [String freeze exception] Horizon > https://review.openstack.org/#/c/371907/ (Akihiro Motoki) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 16 Sep 2016 23:42:32 +0900 > From: Akihiro Motoki <amotoki(a)gmail.com> > To: "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> > Cc: Andreas Jaeger <aj(a)suse.com>, "openstack-i18n(a)lists.openstack.org" > <openstack-i18n(a)lists.openstack.org> > Subject: Re: [OpenStack-I18n] First stable/newton branches created > Message-ID: > <CALhU9tk1OnDZ7H+HTqrFG=CJh4EZ2_nvX5iadEMgzQWpzbJ+5A(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > 2016?9?16?????Kato, Tomoyuki<kato.tomoyuki(a)jp.fujitsu.com>????????: > >>> Thanks Andreas for the info. >>> >>> Kato-san, could you take care of it? >>> You can do it yourself or delegate it to someone else, >>> but it is better to do it soon. Otherwise master and stable-newton >>> will be diverged. >> >> Sorry for late response. I wiil work on it from now. > > > No problem. I can help additional prpject branching. > We were just discussing what we can, > Thanks formyour help. > > >> KATO Tomoyuki >> >> >>> >>>> Syncing to Zanata works automatically if there is a stable-newton (note >>>> the "-", Zanata does not allow "/"!) branch. >>> >>> That's what was unclear to me. Thanks. >>> So, the question now is who creates stable-newton version in Zanata. >>> I think only the limited folks can do that. Perhaps Daisy, Kato-san, >> Andreas? >>> In addition to the permission, the tips on creating a Zanata version >>> has not been shared. >>> >>> Akihiro >>> >>> 2016-09-16 14:32 GMT+09:00 Andreas Jaeger <aj(a)suse.com <javascript:;>>: >>>>> On 09/16/2016 04:30 AM, Akihiro Motoki wrote: >>>>> Hi Ian, >>>>> >>>>> 2016-09-16 9:54 GMT+09:00 Ian Y. Choi <ianyrchoi(a)gmail.com >> <javascript:;>>: >>>>>> Hello Andreas and i18n team members, >>>>>> >>>>>> Yesterday (according to UTC), Kato-san and me discussed this topic >> in IRC >>>>>> meeting [1], >>>>>> but we are not sure when we will have stable-newton branch. >>>>>> I think it is time to create stable-newton branch now and Kato-san >> will deal >>>>>> with, >>>>>> but I would like to ask some details to clarify the best timing of >> creating >>>>>> a stable branch. >>>>>> >>>>>> When should i18n team create a stable branch (e.g., stable-newton) in >>>>>> Zanata? >>>>> >>>>> Although I am not familiar with Zanata operations, I think the i18n >>>>> team needs to >>>>> create 'stable-newton' version by branching 'master' version in Zanata >>>>> to inherit >>>>> translation works made in the master version so far. >>>>> >>>>> In my understanding, what we need to do are: >>>>> (a) create stable-newton version in Zanata from master version -> >> i18n team >>>>> (b) release RC1 deliverables and create stable/newton branch in git >>>>> repositories -> each project team and release team >>>>> (c) set up project-config to sync repositories and translations for >>>>> stable/newton -> infra team (I can as well) >>>> >>>> Syncing to Zanata works automatically if there is a stable-newton (note >>>> the "-", Zanata does not allow "/"!) branch. Importing into >>>> stable/newton needs project-config changes. If you would do that, it >>>> would be great! >>>> >>>> >>>>> There is no strict relationship between (a) and (b), and either of >>>>> them can happen first. >>>>> If the timing of (a) and (b) are closer, most translation work in >>>>> 'master' in Zanata are copied into 'stable-newton' version. >>>>> (c) needs to be done after both (a) and (b). >>>> >>>> Indeed, >>>> >>>> Andreas >>>> >>>>>> I thought just after from "Hard StringFreeze" in [2] would be the >> right >>>>>> time, >>>>>> or checking at least Horizon development status (since the focus of >> i18n >>>>>> team now is Horizon related projects) >>>>>> would be needed. (Previously we had I18n cross project liaisons [3].) >>>>> >>>>> To be honest, RC1 release means 'Hard String Freeze'. That's all. >>>>> We can know RC1 release notices by various ways: >>>>> - checking release announcements, >>>>> - checking openstack/releases reviews [5], >>>>> - checking releases.openstack.org [6] >>>>> >>>>> I think we should prepare stable-newton version in Zanata for all >> projects, >>>>> even though most of the i18n team focus on horizon related >> translations. >>>>> >>>>> I am not sure i18n liaisons for horizon related projects work in this >> cycle. >>>>> We have sent no reminder for i18n liaisons... >>>>> In the previous release, I took care of horizon related projects but >>>>> it is beyond >>>>> the role of horizon-i18n liaison and I am not taking care of them >>>>> (except horizon itself). >>>>> >>>>> Horizon RC1 will be shipped in several hours. The team is preparing >>>>> the release now. >>>>> >>>>>> Or should we start gradually the projects merged with >> "topic:create-[release >>>>>> name]" patches, like [4]? >>>>>> >>>>>> [1] >>>>>> http://eavesdrop.openstack.org/meetings/openstack_i18n_ >> meeting/2016/openstack_i18n_meeting.2016-09-15-13.03.html >>>>>> [2] https://releases.openstack.org/newton/schedule.html >>>>>> [3] https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n >>>>>> [4] https://review.openstack.org/#/q/topic:create-newton >>>>> >>>>> [5] https://review.openstack.org/#/q/project:openstack/releases+ >> path:%255Edeliverables/newton/.* >>>>> [6] https://releases.openstack.org/newton/index.html >>>>> >>>>> Thanks, >>>>> Akihiro >>>>> >>>>>> >>>>>> >>>>>> With many thanks, >>>>>> >>>>>> /Ian >>>>>> >>>>>> Andreas Jaeger wrote on 9/16/2016 3:35 AM: >>>>>>> >>>>>>> Could somebody please set up stable-newton branches for those >> projects >>>>>>> that should get translations of them, please? >>>>>>> >>>>>>> With RC1 today, projects are creating stable/newton branches now, >>>>>>> >>>>>>> Andreas >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> OpenStack-I18n mailing list >>>>>> OpenStack-I18n(a)lists.openstack.org <javascript:;> >>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >>>> >>>> >>>> -- >>>> Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: >> jaegerandi >>>> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany >>>> GF: Felix Imend?rffer, Jane Smithard, Graham Norton, >>>> HRB 21284 (AG N?rnberg) >>>> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 >> A126 >

1 0

[String freeze exception] Horizon https://review.openstack.org/#/c/371907/
by Akihiro Motoki 17 Sep '16

17 Sep '16

Hi i18n team, I would like to request a string freeze exception for horizon: https://review.openstack.org/#/c/371907/ which fixes https://bugs.launchpad.net/horizon/+bug/1624197 . It is small enough and can be accepted. Can we move this forward? This patch allows translators to control the word order in delete confirm forms. Currently "You have selected: " and selected items are concatenated and in some language the selected items need to be placed first. Thanks, Akihiro

3 2

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

16 Sep '16

Hi everyone, Newton goes out in three weeks, and the release team and I have been busy working with our cross-project liaisons to ensure the docs suite is up to date and ready to go. Don't forget that you can contact any of us (or just send mail to the docs mailing list) if you have any questions about the Newton docs release. This week, I've also been working on Summit planning, and drafting my PTL candidacy, which you can read here: http://lists.openstack.org/pipermail/openstack-docs/2016-September/009112.h… Big thanks to everyone who has emailed me over the past few days to offer their support. Knowing you all have my back is the reason I keep doing this :) == Progress towards Newton == 19 days to go! Bugs closed so far: 444 Release managers: Olena Logvinova and Alexandra Settle Release tasks are being tracked here: https://etherpad.openstack.org/p/NewtonRelease Install Guide testing is being tracked here: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting == The Road to Barcelona == * I have a draft schedule starting to take shape, which you can see here: https://etherpad.openstack.org/p/Ocata-DocsSessions I'll put this into Sched once the tool becomes available, and your early feedback is welcome. Additionally, if you're interested in moderating a session in Barcelona, please let me know. * By now, you should be well on the way to having your travel and accommodation booked for Barcelona. In case you're still working on it, though, there's travel information available on the Summit site here: https://www.openstack.org/summit/barcelona-2016/travel/ * Looking a little further forward, Foundation have now announced that the first Project Team Gathering (PTG) will be held in Atlanta, US, on Feb 20-24: http://www.openstack.org/ptg == Speciality Team Reports == This will be the last Speciality Team report before we release Newton, as focus shifts to final preparations, testing, and release notes. I'd like to take this opportunity to thank all our speciality team leads, who work very hard behind the scenes to keep their books in top shape, and their teams working together towards a common goal. Our docs suite wouldn't be what it is without these hard working people. '''HA Guide: Andrew Beekhof''' No report this week. '''Install Tutorials: Lana Brindley''' Core Guide testing is underway! Check out progress and sign up here: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting Next meeting: 27 September August 0600UTC. '''Networking Guide: Edgar Magana''' No report this week. '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' No report this week. '''Ops Guide: Shilla Saebi, Darren Chan''' No report this week. '''API Guide: Anne Gentle''' Working with teams who want to write guides similar to FirstApp: Murano and Heat for example. This patch moves Cinder v1 API to Deprecated: https://review.openstack.org/#/c/370407/ Thanks Mark Voelker for all the links to go with the patch! '''Config/CLI Ref: Tomoyuki Kato''' Updating Config reference for Newton release. We need to help, especially for vendor plug-in configuration. '''Training labs: Pranav Salunke, Roger Luethi''' No report this week. '''Training Guides: Matjaz Pancur''' No report this week. '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Rodrigo Caballero''' No report this week. == Doc team meeting == Next meetings: The US meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-09-14 Next meetings: APAC: Wednesday 21 September, 00:30 UTC US: Wednesday 28 September, 19:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#16_September_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

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

11 Sep '16

Hi everyone, Only four weeks to go until Newton! Andreas, Brian, Olga, and I met with our new release managers Olena and Alex a few days ago, and we're all ready and waiting with bated breath to get started on the release. Don't forget that you can contact any of us (or just send mail to the docs mailing list) if you have any questions about the Newton docs release. This week, I've also done a core team review, and we bid farewell to two core team members. More on that in this newsletter. == Progress towards Newton == 26 days to go! Bugs closed so far: 428 Release managers: Olena Logvinova and Alexandra Settle Release tasks are being tracked here: https://etherpad.openstack.org/p/NewtonRelease Install Guide testing is being tracked here: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting == The Road to Barcelona == * If there's something you want to make sure we discuss at Summit, please put your ideas here: https://etherpad.openstack.org/p/Ocata-DocsSessions When we get our room allocations, I'll organise it into a schedule. * If you require a visa invitation letter to travel to Spain, then you need to fill out the form here: https://www.openstack.org/summit/barcelona-2016/travel/#visa Looking a little further forward, Foundation have now announced that the first Project Team Gathering (PTG) will be held in Atlanta, US, on Feb 20-24: http://www.openstack.org/ptg == Core Team Review == The core team have completed their review for August, and I'm a bit sad to announce that both Atsushi Sakai and Gauvain Pocontek are no longer core team members. Gauvain has been committing to OpenStack manuals since well before my time, and has been an invaluable resource for many people (including myself!) over the years. He is currently working on some new projects, but we hope to still see him around from time to time. Atsushi-san joined the core team last year, and during that time has proven an extremely effective reviewer. He is still very busy on OpenStack, with an increased focus on cross-project tasks, so we will be sure to still see him around. I wish you well on your endeavours! I thank you both for your commitment to being core team members, and for all your contributions. We are better because of your effort. == Speciality Team Reports == '''HA Guide: Andrew Beekhof''' Organizing a HA meetup at summit Intention is get an update plan finalized shortly '''Install Tutorials: Lana Brindley''' Core Guide testing is underway! Check out progress and sign up here: https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting Next meeting: 13 September August 0600UTC. '''Networking Guide: Edgar Magana''' No report this week. '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' No report this week. '''Ops Guide: Shilla Saebi, Darren Chan''' No report this week. '''API Guide: Anne Gentle''' Working on an article for Super User describing the switchover in API guide sources to project repos and the new navigation. '''Config/CLI Ref: Tomoyuki Kato''' Consolidating the OSC command reference into the OSC specific doc. '''Training labs: Pranav Salunke, Roger Luethi''' No report this week. '''Training Guides: Matjaz Pancur''' Finished first day of our virtual sprint series (6 Sep): Common items: https://etherpad.openstack.org/p/upstream-uni-common-items (coordinated by Ildiko Vancsa, ildikov), Code contribution: https://etherpad.openstack.org/p/upstream-uni-code-contribution (coordinated by Kendall Nelson, diablo_rojo) Next virtual sprint dates: 12,13 and 16 September (https://wiki.openstack.org/wiki/VirtualSprints#Upstream_training_Sprint) '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Rodrigo Caballero''' No report this week. == Doc team meeting == Next meetings: The APAC meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-09-07 Next meetings: US: Wednesday 14 September, 19:00 UTC APAC: Wednesday 21 September, 00:30 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#9_September_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

2 1

[Bug 1536226] Re: Not all .po files compiled
by OpenStack Infra 08 Sep '16

08 Sep '16

Reviewed: https://review.openstack.org/319276 Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=0adde01a06d81ab3… Submitter: Jenkins Branch: master commit 0adde01a06d81ab39f536794e178d0434e9783a2 Author: Sven Anderson <sven(a)redhat.com> Date: Fri May 20 16:20:48 2016 +0200 Let setup.py compile_catalog process all language files Two years ago the translation files have been split into several files, separating the log messages of different log levels from each other, like X.pot, X-log-warning.pot, X-log-info.pot, and so on. However, the setup.py command `compile_catalogs`, that comes from the babel package and compiles the corresponding .po files into .mo files, only supported one file per python package. This means that during packaging `compile_catalogs` never compiled the X-log-*.po files, so the corresponding translations were always missing. Since babel 2.3 the domain can be set to a space separated list of domains. This change adds the the additional log level files to the domain list. The obsolete check that .po and .pot files are valid is removed from tox.ini. Change-Id: I149c2254cb04297e598cfd3ca73b24efd0c8ef18 Closes-Bug: #1536226 ** Changed in: cinder 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/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: New Status in OpenStack Compute (nova): Fix Released Status in openstack i18n: New 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

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

02 Sep '16

Hi everyone, We have five weeks left until the Newton release goes out, so this week has been all about getting started on testing the Install Guide. We now have beta releases for all our distros, so thanks to our lovely package maintainers for getting back to me so quickly! We can still use more testers, though, all you need to do is sign up on the wiki page and start testing: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting This week Andreas, Brian, Olga, and I will be meeting with our new release managers Olena and Alex, to make sure they're up to speed. Don't forget that you can contact any of us (or just send mail to the docs mailing list) if you have any questions about the Newton docs release. == Progress towards Newton == 33 days to go! Bugs closed so far: 407 Release managers: Olena Logvinova and Alexandra Settle Install Guide testing is being tracked here: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting == The Road to Barcelona == * If there's something you want to make sure we discuss at Summit, please put your ideas here: https://etherpad.openstack.org/p/Ocata-DocsSessions When we get our room allocations, I'll organise it into a schedule. * Talk acceptances have gone out, congratulations to everyone who got something accepted! * If you require a visa invitation letter to travel to Spain, then you need to fill out the form here: https://www.openstack.org/summit/barcelona-2016/travel/#visa == Docs Tools == There is a lot of cleanup happening on the docs site right now, so you might see some old and unloved content disappear. If you notice anything strange, please let Andreas or the docs mailing list know so we can get it straightened out. == Speciality Team Reports == '''HA Guide: Andrew Beekhof''' No report this week. '''Install Tutorials: Lana Brindley''' Core Guide testing is underway! Check out progress and sign up here: https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting Next meeting: 13 September August 0600UTC. '''Networking Guide: Edgar Magana''' No report this week. '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' No report this week. '''Ops Guide: Shilla Saebi, Darren Chan''' No meeting last week in light of the ops mid cycle and OpenStack East conference Updating use cases chapter in Arch Guide Looking for more enterprise troubleshooting docs to push upstream for the ops guide '''API Guide: Anne Gentle''' New landing page for a collection of all API Reference docs and Guides in one place: https://review.openstack.org/#/c/361480/ Improvements to the sidebar link collection: https://review.openstack.org/#/c/362436/ '''Config/CLI Ref: Tomoyuki Kato''' Updated some CLI reference. Closed some bugs for Config Reference. '''Training labs: Pranav Salunke, Roger Luethi''' No report this week. '''Training Guides: Matjaz Pancur''' No report this week. '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Rodrigo Caballero''' No report this week. == Site Stats == For the month of August, we had a 6% increase in traffic over July. == Doc team meeting == Next meetings: The US meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-08-31 Next meetings: APAC: Wednesday 7 September, 00:30 UTC US: Wednesday 14 September, 19:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#2_September_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Fwd: Re: [OpenStack-docs] Stopping DocBook Building
by Ian Y. Choi 31 Aug '16

31 Aug '16

Hello! Recently I have found that there has been some changes on the following landing pages : French, Japanese, Chinese (Simplified) and draft. You can check: https://review.openstack.org/#/c/362350 Thank a lot, Andreas! With many thanks, /Ian -------- Original Message -------- Subject: Re: [OpenStack-docs] Stopping DocBook Building Date: Tue, 23 Aug 2016 13:08:53 +0200 From: Andreas Jaeger <aj(a)suse.com> Organization: SUSE Linux GmbH, Nuernberg, GF: Felix Imendörffer, Jane Smithard, Graham Norton , HRB 21284 (AG Nuernberg) To: Anne Gentle <annegentle(a)justwriteclick.com> CC: openstack-docs(a)lists.openstack.org <Openstack-docs(a)lists.openstack.org> On 2016-08-22 18:03, Andreas Jaeger wrote: > On 08/22/2016 02:33 PM, Anne Gentle wrote: >> Hurray! >> >> >> >>> On Aug 22, 2016, at 2:23 AM, Andreas Jaeger <aj(a)suse.com> wrote: >>> >>> I think we're far enough with DocBook building removal that we can >>> Release openstack-doc-tools without DocBook support. >>> >>> For older branches, I'll put up a request to cap openstack-doc-tools. >>> >>> https://review.openstack.org/#/q/topic:openstack-doc-tools-1 >>> >>> One question: Can we stop building api-site DocBook documents now as >>> well? With most api-ref projects moved over, we already froze the >>> content. Is there a need to continue publishing? >> >> >> None that I can think of now that trove has migrated. >> >> I'm also going to stop building OpenAPI / swagger from that source. > > I stop building the swagger documents and also stop building the DocBook > XML content on api-site with: > https://review.openstack.org/358734 Let's continue this road - and disable DocBook XML and swagger building completely for api-site: https://review.openstack.org/358727 https://review.openstack.org/358734 I have not removed those files yet, 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 _______________________________________________ OpenStack-docs mailing list OpenStack-docs(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

1 0

What's Up, Doc? 26 August
by Lana Brindley 26 Aug '16

26 Aug '16

Hi everyone, This week marks six weeks left to the Newton release, so I've been busy getting everything prepared. We're now ready to start testing the core Installation Tutorial, so check out the wiki and get signed up: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting#Testers We've also selected two new release managers to assist with this release, please welcome Olena and Alex! More on those topics in this newsletter. == Progress towards Newton == 40 days to go! Bugs closed so far: 387 Release planning: https://etherpad.openstack.org/p/NewtonRelease == Release Managers == There was an overwhelming response to my request for release managers, which was very cool! The first two responders were Olena Logvinova <ologvinova(a)mirantis.com> and Alexandra Settle <alexandra.settle(a)RACKSPACE.COM>, so please welcome them to the release team. Their main role during this process is to make sure that all the tasks we have to complete get done accurately and on schedule. It's an important job, and we're really glad to have you both on board. == Install Tutorial Testing == Install Tutorial testing is just about ready to kick off. If you're interested in helping, make sure you've added your name on to the list on our testing wiki page: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting (if you don't have wiki access, just email me directly and I'll add you in). Thanks to our package maintainers, we now have b2 pre-release packages ready for Ubuntu and Debian, so those are ready to be tested. == Docs Tools == I'm very pleased to announce that we have now removed DocBook from our build tools. The end of an era! Thanks to Anne, Andreas, and David Cramer for keeping this project alive for so long, and eventually seeing it come to fruition. Version 1.5.0 of openstackdoccstheme was released this week. In other tools news, there are plans afoot to move developer.openstack.org and docs.openstack.org away from Rackspace Cloudsites, and on to pages that OpenStack Infra control. This has been on the proverbial backburner for a long time, but the Infra team is now in a position to make it happen. You can read and comment on the Infra spec here: https://review.openstack.org/#/c/276482/ == Speciality Team Reports == '''HA Guide: Andrew Beekhof''' No report this week. '''Install Tutorials: Lana Brindley''' Core Guide testing is underway! Check out progress and sign up here: https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting Next meeting: 30 August 0600UTC. '''Networking Guide: Edgar Magana''' Attending the OpenStack East in NYC. No report this week. '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' No report this week. '''Ops Guide: Shilla Saebi, Darren Chan''' No report this week. '''API Guide: Anne Gentle''' Releasing openstackdocstheme with new sidebar and integration with os-api-ref Sphinx Extension. Many thanks to Karen Bradshaw, Sean Dague, Graham Hayes, Andreas Jaeger (and anyone I may have missed!) for their tireless efforts on this release. WOW. '''Config/CLI Ref: Tomoyuki Kato''' Merged some patches, updated a few CLI reference, nothing special. '''Training labs: Pranav Salunke, Roger Luethi''' Some minor changes, backports of features. The parser is almost done. https://github.com/dguitarbite/rst2bash Updated the openstack-manuals, install-guides with the new syntax which is parser friendly. I should start sending the required patches to manuals repo. soon after finalizing the syntax.. https://github.com/dguitarbite/openstack-manuals/commit/c9e7e1bb2c7269f02a7… '''Training Guides: Matjaz Pancur''' Upstream training improvement (https://etherpad.openstack.org/p/upstream-university-improvements) Please consider participating in the Remote content sprint (proposed timeframe: first half of September, see etherpad for details). '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Rodrigo Caballero''' No report this week. == Site Stats == Keystone and Ceph are this week's most popular search terms. == Doc team meeting == Next meetings: The APAC meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-08-24 Next meetings: US: Wednesday 31 August, 19:00 UTC APAC: Wednesday 7 September, 00:30 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#26_August_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Fwd: [openstack-dev] [release] Release countdown for week R-5, 29 Aug - 2 Sept
by Ian Y. Choi 26 Aug '16

26 Aug '16

Hello, Hope that everything goes well for all. I am forwarding one e-mail which recalls 'soft string freeze'! By the way, when is the next IRC i18n meeting? 06:00 UTC on September 1 is correct? If it is correct, I think it is a good time to summarize what we did and decide which projects to be translated as i18n team objectives. With many thanks, /Ian -------- Original Message -------- Subject: [openstack-dev] [release] Release countdown for week R-5, 29 Aug - 2 Sept Date: Thu, 25 Aug 2016 14:58:49 -0400 From: Doug Hellmann <doug(a)doughellmann.com> Reply-To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> To: openstack-dev <openstack-dev(a)lists.openstack.org> Focus ----- The feature freeze deadline is 1 Sept. All project teams should be putting the last minute touches on feature work. General Notes ------------- Non-client libraries are frozen and will only see updates for release-critical bugs. We have not created stable branches, yet, in case we do need those releases. Teams who haven't frozen master will need to create the stable branch from their most recent release and backport fixes before doing a patch release. The third milesone occuring this week includes several freezes in our release cycle to let us shift our focus to bug fixes and generally hardening the release. * We freeze releases of all libraries and changes to requirements between the third milestone and the final release to give downstream packagers time to vet the libraries. Only emergency bug fix updates are allowed during that period, not releases for FFEs. * The overall feature freeze allows teams to wrap up Newton and start thinking about Ocata planning. * We start a soft string freeze at the milestone to give translators time to catch up with the work that has already been done this cycle. A hard string freeze will follow two weeks later at R-3. Release Actions --------------- The last day for releases for client libraries will be 1 Sept. File your release request in time to have the release done on the 1st. The milestone deadline is also 1 Sept. Please file your 0b3 tag request in time to have the release done on the 1st. Review the members of your $project-release group in gerrit, based on the instructions Thierry sent on 15 Aug. Important Dates --------------- Newton RC-1, 15 Sept. Newton release schedule: http://releases.openstack.org/newton/schedule.html __________________________________________________________________________ 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

Asking for update in some language team wiki pages
by Ian Y. Choi 26 Aug '16

26 Aug '16

Hello, First of all, thanks a lot Akihiro-san for your kind updates (e.g., [1]) on OpenStack I18n Guide [2]. I have just found that some language team Wiki pages in I18nTeam/team [3] still refer to Transifex, which is deprecated and now we use Zanata. I do not have much knowledge on interpreting and reading different languages, but from my brief observation, it seems that those language team pages need to be updated: - Catalan: https://wiki.openstack.org/wiki/I18nTeam/team/ca => mentions Transifex & wrong IRC channel #openstack-translation (changed to #openstack-i18n) - English (Austraila): https://wiki.openstack.org/wiki/I18nTeam/team/en_au => mentions www.transifex.com - Hindi: https://wiki.openstack.org/wiki/I18nTeam/team/hi => mentions www.transifex.com - Polish: https://wiki.openstack.org/wiki/I18nTeam/team/pl => mentions Transifex with web site URL and a profile - Punjabi: https://wiki.openstack.org/wiki/I18nTeam/team/pa_IN => mentions Transifex with URL and a project link - Spanish: https://wiki.openstack.org/wiki/I18nTeam/team/es => Profile IDs refer to Transifex profile links - Assamese, Bodo, Gujarati, Kashmiri, Maithili, Sindhi (C-DAC) : https://wiki.openstack.org/wiki/I18nTeam/team/CDACTeam => mentions www.transifex.com Let's update them :) [1] https://review.openstack.org/#/c/360663/ [2] http://docs.openstack.org/developer/i18n/ [3] https://wiki.openstack.org/wiki/I18nTeam/team With many thanks, /Ian

1 0

What's Up, Doc? 19 August
by Lana Brindley 19 Aug '16

19 Aug '16

Hi everyone, Watch out, Install Guide testing season is about to begin! If you're a package maintainer, cross-project liaison, or just a helpful testing regular, look out for an email from me real soon now! In the meantime, keep hitting those bugs, and letting us know if you spot any problems in the guide. == Progress towards Newton == 47 days to go! Bugs closed so far: 371 Newton deliverables: https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables Feel free to add more detail and cross things off as they are achieved throughout the release. == Speciality Team Reports == '''HA Guide: Andrew Beekhof''' Some reviews, nothing interesting '''Install Tutorials: Lana Brindley''' Core Guide testing to kick off Real Soon Now (tm). Next meeting: 30 August 0600UTC. '''Networking Guide: Edgar Magana''' No report this week. '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' No report this week. '''Ops Guide: Shilla Saebi, Darren Chan''' Reorganized monitoring content in the Ops Guide Migrating ops, legal, and security content in the Arch Guide Working on use cases chapter and design chapter in the Arch Guide '''API Guide: Anne Gentle''' No report this week. '''Config/CLI Ref: Tomoyuki Kato''' A few cleanups are under going. Updated some client references. '''Training labs: Pranav Salunke, Roger Luethi''' No report this week. '''Training Guides: Matjaz Pancur''' No report this week. '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Rodrigo Caballero''' No report this week. == Site Stats == Just under 90,000 sessions on the docs site this week. == Doc team meeting == Next meetings: The US meeting failed to make quorum this week. We're seeing this a lot recently, is there still a need for a regular docs meeting? Next meetings: APAC: Wednesday 24 August, 00:30 UTC US: Wednesday 31 August, 19:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#19_August_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 1

Barcelona Design Summit space needs
by Kato, Tomoyuki 19 Aug '16

19 Aug '16

Hi team, This is preparation for the Barcelona Design Summit. As of now, I'd like to request 2 spaces for I18n. due date: August 30 - 1 workroom session - 1 contributor meetup Any thought? Note that we should probably require *less* slots than in Austin because the whole Summit event starts on the Tuesday and is only 4 days. - Ops summit on Tuesday morning until 4pm - Cross-project workshops from Tuesday 4pm to Wednesday 4pm - Fishbowl/Workroom sessions from Wednesday 4pm to Friday noon - Contributors meetups on Friday afternoon * Fishbowl sessions (from Wednesday 4pm to Friday noon) Our traditional largish rooms organized in fishbowl style, with advertised session content on the summit schedule for increased external participation. Ideal for when wider feedback is essential. * Workroom sessions (from Wednesday 4pm to Friday noon) Smaller rooms organized in boardroom style, with topic buried in the session description, in an effort to limit attendance and not overcrowd the room. Ideal to get work done and prioritize work in small teams. * Contributors meetup (Friday afternoon) Half-day session on Friday afternoon to get into the Ocata action while decisions and plans are still hot, or to finish discussions started during the week, whatever works for you. Best Regards, KATO Tomoyuki

1 0

Fwd: [openstack-dev] [all][ptl][tc] extra ATCs for newton
by Akihiro Motoki 18 Aug '16

18 Aug '16

Forwarded to i18n list. My big question is what is our ATC process in Newton. I think everyone has the same question. IIRC, an effort to track translator activity automatically is on-going, but I don't know the current status. I believe it should be announced officially. Akihiro ---------- Forwarded message ---------- From: Doug Hellmann <doug(a)doughellmann.com> Date: 2016-08-11 1:24 GMT+09:00 Subject: [openstack-dev] [all][ptl][tc] extra ATCs for newton To: openstack-dev <openstack-dev(a)lists.openstack.org> It's time to make sure we have all of our active technical contributors (ATCs) identified for Newton. Following the Foundation bylaws [1] and TC Charter [2], Project teams should identify contributors who have had a significant impact this cycle but who would not qualify for ATC status using the regular process because they have not submitted a patch. Contributions might include, but aren't limited to, bug triage, design work, and documentation -- there is a lot of leeway in how teams define contribution for ATC status. The resulting list of names should be submitted as a patch to the "extra-atcs" section in openstack/governance/reference/projects.yaml for review by the TC. Although extra ATCs can be nominated at any point, there is a deadline to be included in the electorate for the next release cycle. The ATC list needs to be approved by the TC by 25 Aug, and in order to appear on the TC agenda to be discussed, the proposals need to be submitted by 16 Aug. PTLs can delegate preparing the patch to the governance repository, but please +1 the patch indicating that you agree with the list to avoid delays in the TC review. Thanks, Doug [1] http://www.openstack.org/legal/technical-committee-member-policy/ [2] http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-… __________________________________________________________________________ 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

5 8

Request for OpenStack Mitaka pii files for IBM documentation translation project with quotes from OpenStack
by Monika Wolf 18 Aug '16

18 Aug '16

Hello, I am currently working on an IBM translation project which contains quoted pii strings from OpenStack Mitaka release. In order to be able to use the translated version of those strings I would need the English and German Mitaka files (including Horizon UI). When I checked with the IBM lab responsible for this project I got this answer: > Here is the response from Development: > "We're using mitaka release .More details about release dates here: > http://releases.openstack.org/ > In the past , OpenStack used to assign a certain version to the entire > > distribution . Now individual projects in OpenStack have their own > version (e.g. nova-manage --version returns 13.0.1, which is the > version of nova associated with mitaka)" Please also refer to the attached shot (which contains part of the quoted pii strings). I appreciate your support. (See attached file: TCT25_a.jpg) Mit freundlichen Grüßen / Kind regards Monika Wolf Translator/Tester Contractor IBM Sales & Distribution, Software Sales Translation Services Center (TSC) Germany Phone: 0711 83889237 IBM Deutschland GmbH Email: vcomas3(a)de.ibm.com Am Fichtenberg 1 71083 Herrenberg IBM Deutschland GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Martina Koederitz (Vorsitzende), Susanne Peter, Norbert Janzen, Dr. Christian Keller, Ivo Koerner, Markus Koerner Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart, HRB 14562 / WEEE-Reg.-Nr. DE 99369940

5 5

No meeting 8/18
by Kato, Tomoyuki 18 Aug '16

18 Aug '16

Hi team, No meeting 8/18 due to my personal reason. KATO Tomoyuki

1 0

[Bug 1534418] Re: Wrong Chinese translation in OpenStack install doc
by Ian Y. Choi 12 Aug '16

12 Aug '16

Fix released (e.g., Mitaka: http://docs.openstack.org/mitaka/zh_CN /install-guide-rdo/environment-ntp-controller.html ) ** Changed in: openstack-i18n Status: Fix Committed => 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/1534418 Title: Wrong Chinese translation in OpenStack install doc Status in openstack i18n: Fix Released Bug description: The original link is http://docs.openstack.org/liberty/install-guide-rdo/environment-ntp-control… The translation draft link is http://docs.openstack.org/liberty/zh_CN/install-guide-rdo/environment-ntp-c… There is an extra "中" in the translation. It should be translated to "组织中提供的". The picture is attached. + Mitaka : http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/environment-ntp-co… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1534418/+subscriptions

1 0

[Bug 1556886] Re: zh_CN in trove-dashboard string looks wrong
by Ian Y. Choi 12 Aug '16

12 Aug '16

Merged: https://review.openstack.org/#/c/353343/ (stable/mitaka) and https://review.openstack.org/#/c/351998/ (master). Thanks, Shengjing! ** Changed in: openstack-i18n Status: Fix Committed => 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/1556886 Title: zh_CN in trove-dashboard string looks wrong Status in openstack i18n: Fix Released Bug description: Please see https://review.openstack.org/#/c/290287/2/trove_dashboard/locale/zh_CN/LC_M…: #, python-format msgid "" "[flavor=%(flavor)s, volume=%(volume)s, name=%(name)s, type=%(type)s, " "related_to=%(related_to)s]" msgstr "" "[flavor=%(flavor)s, volume=%(volume)s, name=%(name)s, type=%(type)s, " "related_to=%(related_to)s]" As Amrid says: " This doesn't look right. Shouldn't this be <chinese characters for flavor>=..., etc., Like line 1029" j To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1556886/+subscriptions

1 0

What's Up, Doc? 12 August
by Lana Brindley 12 Aug '16

12 Aug '16

Hi everyone, I have been struck down with flu yet again this week, so a quiet one from me (I'll be glad when winter is over, let me tell you!). Anne, however, has been kicking it out of the park with her work on the API docs; I suggest you take a look at the update she sent to the mailing lists the other day to catch up: http://lists.openstack.org/pipermail/openstack-dev/2016-August/101380.html == Progress towards Newton == 54 days to go! Bugs closed so far: 365 Newton deliverables: https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables Feel free to add more detail and cross things off as they are achieved throughout the release. == Speciality Team Reports == '''HA Guide: Andrew Beekhof''' No report this week. '''Install Tutorials: Lana Brindley''' Next meeting: 16 August 0600UTC '''Networking Guide: Edgar Magana''' No report this week. '''Security Guide: Nathaniel Dillon''' Bug hunt continued, all contributions are welcome, grammatical and technical alike! Focusing on the last half of the SecurityGuide, and the 'freshness' of code examples Threat analysis documentation and templates added '''User Guides: Joseph Robinson''' The Consistency and Editing patch is ready to merge, and just needs more reviews https://review.openstack.org/#/c/347641/ . Some pages in the User Guides are resulting in 404s (dashboard manage shares for example), and this bug is tracking the changes https://bugs.launchpad.net/openstack-manuals/+bug/1611792 Thanks to Maria for taking on the file name changes to the User Guide, and Anne for also patching the Admin Guide file names! '''Ops Guide: Shilla Saebi, Darren Chan''' Working on storage, networking, and compute sections in the Arch Guide. Arch Guide working group proposed a series of short sprints, working in pairs as SME/writer. Dates TBD Waiting on enterprise ops documentation to migrate to the Ops Guide. '''API Guide: Anne Gentle''' Ceilometer migrated content has landed! \o/ https://review.openstack.org/334028 Many thanks to Khushbu Parakh for sticking with it, and to Julien Danjou and Gordon Chung for accepting the (rather outdated) migrated content and taking responsiblity for it from now on. Working on a template for http-status.yaml file that teams can use for new pretty HTTP Status code tables that just landed last week. https://review.openstack.org/#/c/351835/ Ever closer to landing the API reference navigation. https://review.openstack.org/#/c/329508/ Refer to status report on -dev and -docs mailing lists: http://lists.openstack.org/pipermail/openstack-dev/2016-August/101380.html '''Config/CLI Ref: Tomoyuki Kato''' Closed a few bugs with mitaka backport. '''Training labs: Pranav Salunke, Roger Luethi''' No report this week. '''Training Guides: Matjaz Pancur''' Updating Upstream training for the next OpenStack Summit (https://etherpad.openstack.org/p/upstream-university-improvements) Next meeting: Monday 15 August 1700 UTC in #openstack-meeting '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Rodrigo Caballero''' No report this week. == Site Stats == This week, 385 visitors came to the docs site from Stack Overflow, 423 visitors came via searching on duckduckgo, and 508 came from ask.openstack.org. == Doc team meeting == Next meetings: The APAC meeting failed to make quorum this week, but thanks to Darren for trying anyway :) Next meetings: US: Wednesday 17 August, 19:00 UTC APAC: Wednesday 24 August, 00:30 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#12_August_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Re: [OpenStack-I18n] Broken translations...
by Kato, Tomoyuki 12 Aug '16

12 Aug '16

Hi Andreas, Thanks for your help. I sent a email to the translator and coordinators directly. Regards, KATO Tomoyuki > -----Original Message----- > Same failure pattern for zh_CN, this time on sahara-dashboard and ironic-ui: > > http://logs.openstack.org/periodic/sahara-dashboard-propose-translation-upd… > > http://logs.openstack.org/periodic/ironic-ui-propose-translation-update/d53… > > Could somebody reach out to the translators that break this? > > Andreas > -- > Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany > GF: Felix Imendörffer, Jane Smithard, Graham Norton, > HRB 21284 (AG Nürnberg) > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 > > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

5 6

[Bug 1609474] [NEW] [Chinese] ironic-ui and sahara-dashboard translation error
by Ian Y. Choi 10 Aug '16

10 Aug '16

Public bug reported: The following wrong strings generate Jenkins periodic job errors: 1) zh-CN : ironic_ui/locale/djangojs (URL: https://translate.openstack.org/webtrans/translate?project=ironic-ui&iterat… ) - #10; "Unable to delete node %s: %s" or #39; "{$ property.getDescription() $}" (IMO #10 has more possibility on the error) 2) zh-CN: sahara_dashboard/locale/django (URL: https://translate.openstack.org/webtrans/translate?project=sahara-dashboard… ) - #50; Start Verification & Start Verifications => only 1 of 2 is translated, which cause the error - 58; "Uptime" => Deleting unnecessary '\n' is needed ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: simplified-chinese ** 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/1609474 Title: [Chinese] ironic-ui and sahara-dashboard translation error Status in openstack i18n: New Bug description: The following wrong strings generate Jenkins periodic job errors: 1) zh-CN : ironic_ui/locale/djangojs (URL: https://translate.openstack.org/webtrans/translate?project=ironic-ui&iterat… ) - #10; "Unable to delete node %s: %s" or #39; "{$ property.getDescription() $}" (IMO #10 has more possibility on the error) 2) zh-CN: sahara_dashboard/locale/django (URL: https://translate.openstack.org/webtrans/translate?project=sahara-dashboard… ) - #50; Start Verification & Start Verifications => only 1 of 2 is translated, which cause the error - 58; "Uptime" => Deleting unnecessary '\n' is needed To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1609474/+subscriptions

2 1

[Bug 1535501] Re: Chinese translation of Install doc
by Shengjing Zhu 10 Aug '16

10 Aug '16

Documents have been updated and these strings are not available now. ** Changed in: openstack-i18n Status: Confirmed => 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/1535501 Title: Chinese translation of Install doc Status in openstack i18n: Invalid Bug description: The original link is http://docs.openstack.org/liberty/install-guide-rdo/neutron-controller-inst… The translation link is http://docs.openstack.org/liberty/zh_CN/install-guide-rdo/neutron-controlle… The picture is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1535501/+subscriptions

1 0

Do you translate these...
by Adrien Cunin 09 Aug '16

09 Aug '16

Hi everyone, Working on the Horizon translation in French, I came across these translatable strings and wondered if it makes sense to keep them translatable: * "Material": as in the name of the Horizon theme inspired by Google's Material Design. Anyone wants to have that translatable for their language? As the name of the theme, I'd keep it as is in French. * "10%", "75%": I think I have a first answer with https://en.wikipedia.org/wiki/Percent_sign#Spacing - but are there more differences in some languages? Can we imagine a better way to handle this than having potentially dozens of "xx%" strings to translate? Adrien

2 1

Broken translations...
by Andreas Jaeger 07 Aug '16

07 Aug '16

FYI, these currently fail: http://logs.openstack.org/periodic/ironic-ui-propose-translation-update/3ff… http://logs.openstack.org/periodic/sahara-dashboard-propose-translation-upd… Both cases mean a broken zh-CN translation. Can we tighten the zanata settings to avoid that people introduce such bugs? Or what can be done? 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 3

I18n team mascot
by Kato, Tomoyuki 04 Aug '16

04 Aug '16

Hi team, We have a chance to get our team mascot with an illustrator[1][2]. Any ideas are welcome. Please write your candidacy. https://etherpad.openstack.org/p/i18n-mascot Due date: July 25 [1] http://lists.openstack.org/pipermail/openstack-dev/2016-July/099046.html [2] http://www.openstack.org/project-mascots Thanks, KATO Tomomoyuki

13 22

[Bug 1605261] Re: 错别字 CentOS 镜像 in OpenStack 虚拟机镜像制作指南
by Ian Y. Choi 02 Aug '16

02 Aug '16

Hello maoshuai, Unfortunately, your change will not reflect to the documentation. The documentation was generated with xml-based maven build. However, now image-guide documentation is based on rst, and currently Chinese translation is about 4%, which implies that the rst image-guide build for Chinese is not included in current html generation jobs. Since there is no resource on xml-based image-guide, this bug would be invalid. ** Changed in: openstack-i18n Status: Confirmed => 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/1605261 Title: 错别字 CentOS 镜像 in OpenStack 虚拟机镜像制作指南 Status in openstack i18n: Invalid Bug description: 在最开始的安装启动菜单，选择 Install or upgrade an existing system ，这*事*默认的。事->是 ----------------------------------- Built: 2015-11-24T07:20:44 00:00 git SHA: ed0b07948cdc10b7fb962ec8aba3c3cb299fe053 URL: http://docs.openstack.org/zh_CN/image-guide/content/centos-image.html source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishlang/generated/zh_CN/image-guide/section_centos-example.xml xml:id: centos-image To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1605261/+subscriptions

1 0

Current status of important topics??
by Akihiro Motoki 02 Aug '16

02 Aug '16

Hi all, Newton-2 is approaching. I would like to know the current status of important topics in Newton cycle. IIRC, we have several critical and important topics Kato-san listed. ## Translation check site We spent two cycles already, but it is not yet ready. We need to wait it one more cycle? ## Glossary management I would like to update Japanese glossary with our latest glossary but it is not easy to add several number of new entries to PO file manually. Is there any progress? If we don't plan any change soon, I will import Japanese glossary on Wiki into PO glossary by script (no manual edit). ## Release notes translation Are translated versions published somewhere? Unfortunately I cannot spend time for these efforts as I mentioned before. I hope you have good progress. Akihiro

3 3

why is "Fix Committed' status used
by Akihiro Motoki 01 Aug '16

01 Aug '16

I see bugs with Fix Committed status in openstack-i18n launchpad. Who changes their status to Fix Released? Why don't we set Fix Released when a bug is fixed? Most OpenStack projects set a bug status to Fix Released when a fix is merged into a repo. What is the bug lifecycle in openstack-i18n?

2 1

[Bug 1573514] Re: Typos in Italian Mitaka translation
by Ian Y. Choi 01 Aug '16

01 Aug '16

No extra character currently on https://git.openstack.org/cgit/openstack/neutron/tree/neutron/locale/it/LC_… ** Changed in: openstack-i18n Status: Fix Committed => 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/1573514 Title: Typos in Italian Mitaka translation Status in openstack i18n: Fix Released Bug description: Zanata proposed another update for mitaka neutron Italian translation: https://review.openstack.org/#/c/309280/ There are several concerns I have here. First, it seems that the change has some typos (e.g. using a ¥ character while the language does not use it at all). Second, the change removes authorship for multiple contributors. I suspect it's not expected. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1573514/+subscriptions

1 0

[Bug 1606115] [NEW] mistranslation in install guide japanese
by Yusuke HIgashino 01 Aug '16

01 Aug '16

Public bug reported: openstack-manuals master Documents (ja) doc/install- guide/source/locale/install-guide Edit the ``/etc/chrony/chrony.conf`` file and add, change, or remove the following keys as necessary for your environment: ↓ ファイル ``/etc/ntp.conf`` を編集して、お使いの環境の必要に応じて、以下の項目の追加、変更、削除を行います。 ``/etc/chrony/chrony.conf``→ ``/etc/ntp.conf``に翻訳されている。 ** 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/1606115 Title: mistranslation in install guide japanese Status in openstack i18n: New Bug description: openstack-manuals master Documents (ja) doc/install- guide/source/locale/install-guide Edit the ``/etc/chrony/chrony.conf`` file and add, change, or remove the following keys as necessary for your environment: ↓ ファイル ``/etc/ntp.conf`` を編集して、お使いの環境の必要に応じて、以下の項目の追加、変更、削除を行います。 ``/etc/chrony/chrony.conf``→ ``/etc/ntp.conf``に翻訳されている。 To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1606115/+subscriptions

2 1

[Bug 1592687] [NEW] wrong cs translation in magnum-ui and designate-dashboard
by Andreas Jaeger 01 Aug '16

01 Aug '16

Public bug reported: >From http://logs.openstack.org/periodic/magnum-ui-propose-translation- update/d8f24a9/console.html 2016-06-15 07:32:26.968627 + msgfmt --check-format -o /dev/null magnum_ui/locale/cs/LC_MESSAGES/djangojs.po 2016-06-15 07:32:26.971559 magnum_ui/locale/cs/LC_MESSAGES/djangojs.po:150: number of format specifications in 'msgid_plural' and 'msgstr[1]' does not match 2016-06-15 07:32:26.971678 magnum_ui/locale/cs/LC_MESSAGES/djangojs.po:411: number of format specifications in 'msgid_plural' and 'msgstr[2]' does not match 2016-06-15 07:32:26.971752 msgfmt: found 3 fatal errors 2016-06-15 07:32:26.972356 + ret=1 2016-06-15 07:32:26.972416 + set -e 2016-06-15 07:32:26.972478 + '[' 1 -ne 0 ']' 2016-06-15 07:32:26.972534 + changed=0 2016-06-15 07:32:26.972612 + echo 'ERROR: File magnum_ui/locale/cs/LC_MESSAGES/djangojs.po is an invalid po file.' 2016-06-15 07:32:26.972679 ERROR: File magnum_ui/locale/cs/LC_MESSAGES/djangojs.po is an invalid po file. 2016-06-15 07:32:26.972748 + echo 'ERROR: The file has not been imported and needs fixing!' 2016-06-15 07:32:26.972795 ERROR: The file has not been imported and needs fixing! ** Affects: openstack-i18n Importance: Undecided Status: New ** Summary changed: - wrong cs translation in magnum-ui + wrong cs translation in magnum-ui and designate-dashboard -- 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/1592687 Title: wrong cs translation in magnum-ui and designate-dashboard Status in openstack i18n: New Bug description: From http://logs.openstack.org/periodic/magnum-ui-propose-translation- update/d8f24a9/console.html 2016-06-15 07:32:26.968627 + msgfmt --check-format -o /dev/null magnum_ui/locale/cs/LC_MESSAGES/djangojs.po 2016-06-15 07:32:26.971559 magnum_ui/locale/cs/LC_MESSAGES/djangojs.po:150: number of format specifications in 'msgid_plural' and 'msgstr[1]' does not match 2016-06-15 07:32:26.971678 magnum_ui/locale/cs/LC_MESSAGES/djangojs.po:411: number of format specifications in 'msgid_plural' and 'msgstr[2]' does not match 2016-06-15 07:32:26.971752 msgfmt: found 3 fatal errors 2016-06-15 07:32:26.972356 + ret=1 2016-06-15 07:32:26.972416 + set -e 2016-06-15 07:32:26.972478 + '[' 1 -ne 0 ']' 2016-06-15 07:32:26.972534 + changed=0 2016-06-15 07:32:26.972612 + echo 'ERROR: File magnum_ui/locale/cs/LC_MESSAGES/djangojs.po is an invalid po file.' 2016-06-15 07:32:26.972679 ERROR: File magnum_ui/locale/cs/LC_MESSAGES/djangojs.po is an invalid po file. 2016-06-15 07:32:26.972748 + echo 'ERROR: The file has not been imported and needs fixing!' 2016-06-15 07:32:26.972795 ERROR: The file has not been imported and needs fixing! To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1592687/+subscriptions

2 1

Disabling translation sync for mitaka?
by Andreas Jaeger 30 Jul '16

30 Jul '16

Hi, we're preparing the move to Xenial now in OpenStack CI and for those I wonder how to handle translations. We have these options: 1) We can continue to run mitaka on Trusty but that means work to split up jobs so that newton runs on Xenial but mitaka on Trusty. 2) We can disable mitaka on Trusty and only do Xenial jobs. 3) We can use translation setup for both newton and mitaka using Xenial. In addition, I'd like to disable the liberty documentation translation that we currently still have for OpenStack manuals. I can work on option 2 - but options 1 and 3 are more involved, if that is the overall preference, I will need help from others - especially in reviewing that everything works and fixing if needed. Can we go with 2 now? If not, which projects still get mitaka translation? 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

5 10

Talk for I18N@Openstack summit
by Alex Eng 29 Jul '16

29 Jul '16

Guys, Kato has submitted a talk for Openstack summit Barcelona and it is open for voting. Please vote for the talk! https://www.openstack.org/summit/barcelona-2016/vote-for-speakers/presentat… --------------------------------------------- Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com

5 7

What's Up, Doc? 29 July
by Lana Brindley 29 Jul '16

29 Jul '16

Hi everyone, A fairly quiet week this week, as I've been gradually working my way through old bugs. We're now only ten weeks out from release, so I've also been trying to tidy up some loose ends around the Contributor Guide. We have a couple of specs out for review right now, so if you're looking for some docs work to pick up, try checking these out: https://review.openstack.org/#/q/status:open+project:openstack/docs-specs,n… == Progress towards Newton == 68 days to go! Bugs closed so far: 339 Newton deliverables: https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables Feel free to add more detail and cross things off as they are achieved throughout the release. == Speciality Team Reports == '''HA Guide: Andrew Beekhof''' Informal discussions about appropriate contents and structure '''Install Tutorials: Lana Brindley''' Next meeting: 2 August 0600 UTC '''Networking Guide: Edgar Magana''' Guide re-organization patch has been merged: https://review.openstack.org/#/c/345110/ '''Security Guide: Nathaniel Dillon''' Performing full read-through and bug hunt Opened 5 new bugs Currently looking at Neutron chapter Incoming addition on rate-limiting and anti-DDoS (framework merged tonight (thanks Kato!) and additional details coming) '''User Guides: Joseph Robinson''' No report this week. '''Ops Guide: Shilla Saebi, Darren Chan''' Weekly Arch Guide working group meeting on Wednesday 20:00 UTC in progress. Currently drafting the Design chapter and reusing existing content. Working on getting more enterprise docs uploaded and pushed upstream for ops guide '''API Guide: Anne Gentle''' First App tutorial for the Shade SDK now moving out of draft state. Way to go Marcela Bonell and infra people who make this SDK possible. Thank you to Kato Tomoyuki for deletions of the Image and Networking WADL files in api-site. This ongoing dedication and cleanup is super valuable and much appreciated. '''Config/CLI Ref: Tomoyuki Kato''' Reflecting comments from Stackers. Closed a few bugs for Configuration Reference. Working on the common configurations. '''Training labs: Pranav Salunke, Roger Luethi''' No report this week. '''Training Guides: Matjaz Pancur''' No report this week. '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Rodrigo Caballero''' No report this week. == Site Stats == Just under 55% of our mobile visitors are using an Android operating system to access the site, while just under 40% of our mobile visitors are using iOS. A statistically insignificant 0.07% are still using their Blackberries ... == Doc team meeting == Next meetings: The APAC meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-07-27 Next meetings: US: Wednesday 3 August, 19:00 UTC APAC: Wednesday 10 August, 00:30 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#29_July_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

What's Up, Doc? 22 July
by Lana Brindley 22 Jul '16

22 Jul '16

Hi everyone, As many of you would have noticed from the email onslaught, I've been working on some Launchpad housekeeping this week. The blueprints are all tidied up now, and I intend to start on the bug list next week, so keep those email filters handy ;) I'd also like to point out the hard work Andreas has been putting in to evaluate moving our docs jobs to Ubuntu Xenial. If you notice any weirdness, please let Andreas know. == Progress towards Newton == 75 days to go! Bugs closed so far: 315 Newton deliverables: https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables Feel free to add more detail and cross things off as they are achieved throughout the release. == Speciality Team Reports == '''HA Guide: Andrew Beekhof''' Got drafted (pun intended) Started figuring out the current status and direction '''Install Tutorials: Lana Brindley''' Next meeting: 2 August 0600 UTC '''Networking Guide: Edgar Magana''' No report this week. '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' No report this week. '''Ops Guide: Shilla Saebi, Darren Chan''' Started a weekly Arch Guide working group meeting on Wednesday 20:00 UTC. Currently drafting the Design chapter and reusing existing content. '''API Guide: Anne Gentle''' Sent email to -dev and -docs list to determine next steps for releasing openstackdocstheme and os-api-ref sphinx extension so we can get the better theming output: http://lists.openstack.org/pipermail/openstack-dev/2016-July/099373.html Released 1.4.0 of openstackdocstheme in preparation for August (hopefully) readiness of theme/extension for unifying API docs navigation. Completed updated of governance/reference/projects.yaml to indicate contributor and api docs URLs. Found that three projects have not completed migration (trove, telemetry/ceilometer, ) and found that nn projects don't use the openstackdocstheme and os-api-ref extension and then won't be included in a unified navigation solution for all OpenStack APIs. '''Config/CLI Ref: Tomoyuki Kato''' Adding Clustering service configuration options. Fixed some bugs. Updated a few CLI reference. Added python-watcherclient. '''Training labs: Pranav Salunke, Roger Luethi''' No report this week. '''Training Guides: Matjaz Pancur''' No report this week. '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Rodrigo Caballero''' All five personas are up for review on Gerrit. https://review.openstack.org/#/c/326662/ Further improvements are planned for after the basic information is merged. == HA Guide Speciality Team Update == Bogdan Dobrelya is stepping down from leading the HA Guide Speciality Team, and I would like to thank him for his hard work. I'd like to welcome Andrew Beekhof to the role, and wish him all the best. If you're interesting in helping out on the HA Guide, please let Andrew or me know and we'll get you started. == Site Stats == While 70% of our site traffic comes through Google, just under 5% comes through Baidu, beating Bing on just 1.45%. == Doc team meeting == Next meetings: The US meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-07-20 Next meetings: APAC: Wednesday 27 July, 00:30 UTC US: Wednesday 3 August, 19:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#22_July_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

[Bug 1605261] [NEW] 错别字 CentOS 镜像 in OpenStack 虚拟机镜像制作指南
by Launchpad Bug Tracker 21 Jul '16

21 Jul '16

You have been subscribed to a public bug: 在最开始的安装启动菜单，选择 Install or upgrade an existing system ，这*事*默认的。事->是 ----------------------------------- Built: 2015-11-24T07:20:44 00:00 git SHA: ed0b07948cdc10b7fb962ec8aba3c3cb299fe053 URL: http://docs.openstack.org/zh_CN/image-guide/content/centos-image.html source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishlang/generated/zh_CN/image-guide/section_centos-example.xml xml:id: centos-image ** Affects: openstack-i18n Importance: Undecided Status: New -- 错别字 CentOS 镜像 in OpenStack 虚拟机镜像制作指南 https://bugs.launchpad.net/bugs/1605261 You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n.

1 0

[Bug 1605261] Re: 错别字 CentOS 镜像 in OpenStack 虚拟机镜像制作指南
by KATO Tomoyuki 21 Jul '16

21 Jul '16

** Project changed: openstack-manuals => openstack-i18n -- 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/1605261 Title: 错别字 CentOS 镜像 in OpenStack 虚拟机镜像制作指南 Status in openstack i18n: New Bug description: 在最开始的安装启动菜单，选择 Install or upgrade an existing system ，这*事*默认的。事->是 ----------------------------------- Built: 2015-11-24T07:20:44 00:00 git SHA: ed0b07948cdc10b7fb962ec8aba3c3cb299fe053 URL: http://docs.openstack.org/zh_CN/image-guide/content/centos-image.html source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishlang/generated/zh_CN/image-guide/section_centos-example.xml xml:id: centos-image To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1605261/+subscriptions

1 0

[Bug 1602596] [NEW] HOrizon mitaka zh_CN broken
by Andreas Jaeger 18 Jul '16

18 Jul '16

Public bug reported: >From http://logs.openstack.org/periodic/horizon-propose-translation- update-mitaka/1a32f93/console.html 2016-07-13 07:35:16.087163 | + msgfmt --check-format -o /dev/null openstack_dashboard/locale/zh_CN/LC_MESSAGES/django.po 2016-07-13 07:35:16.115302 | openstack_dashboard/locale/zh_CN/LC_MESSAGES/django.po:8083: a format specification for argument 'req' doesn't exist in 'msgstr[0]' 2016-07-13 07:35:16.115546 | msgfmt: found 1 fatal error Please fix the zh_CN format. ** 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/1602596 Title: HOrizon mitaka zh_CN broken Status in openstack i18n: New Bug description: From http://logs.openstack.org/periodic/horizon-propose-translation- update-mitaka/1a32f93/console.html 2016-07-13 07:35:16.087163 | + msgfmt --check-format -o /dev/null openstack_dashboard/locale/zh_CN/LC_MESSAGES/django.po 2016-07-13 07:35:16.115302 | openstack_dashboard/locale/zh_CN/LC_MESSAGES/django.po:8083: a format specification for argument 'req' doesn't exist in 'msgstr[0]' 2016-07-13 07:35:16.115546 | msgfmt: found 1 fatal error Please fix the zh_CN format. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1602596/+subscriptions

1 3

What's Up, Doc? 15 July
by Lana Brindley 15 Jul '16

15 Jul '16

Hi everyone, CFP for the Barcelona Summit closed this week, so I've been caught up in the flurry of talk submissions. I hope you got yours in on time! We have more Installation Tutorials going up all the time, with Swift up and Designate now in progress. I'd also like to remind you all that we have instructions for creating your team's Install Tutorial in our Contributor Guide here: http://docs.openstack.org/contributor-guide/project-install-guide.html We'd love to get your feedback on that content! == Progress towards Newton == 82 days to go! Bugs closed so far: 280 Newton deliverables: https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables Feel free to add more detail and cross things off as they are achieved throughout the release. The CFP for Barcelona is now closed. Best of luck to everyone who submitted a talk :) == Speciality Team Reports == '''HA Guide: Bogdan Dobrelya''' No report this week. '''Install Tutorials: Lana Brindley''' Continued to publish new guides, Swift is now up, Designate is on review. Submitted Summit talk on this topic. Don't miss our instructions for creating a new Install Tutorial: http://docs.openstack.org/contributor-guide/project-install-guide.html Next meeting: 19 July 0600 UTC '''Networking Guide: Edgar Magana''' No meeting this week. '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' No report this week. '''Ops Guide: Shilla Saebi''' OpenStack ops guide reorg in progress & documented here: https://etherpad.openstack.org/p/ops-guide-reorg Added enterprise docs troubleshooting information to the Ops Guide '''API Guide: Anne Gentle''' Keystone API sprint this week, details are here: https://etherpad.openstack.org/p/keystone-api-sprint Lance Bragstad is on FIRE! Review these api-ref patchsets in progress: https://review.openstack.org/#/q/status:open+file:api-ref Working on a plan for how to merge HTTP Status Code tables and Graham Hayes's patch to use the openstackdocstheme and Karen Bradshaw's overall API navigation in time for release, stay tuned. '''Config/CLI Ref: Tomoyuki Kato''' Got feedbacks from Dolph Matthews, thank you! Closed a few bugs. Updated some CLI reference. '''Training labs: Pranav Salunke, Roger Luethi''' Many minor improvements to training-labs library scripts Finalizing PXE feature, still more work is required but the current patch should be in a state to be merged soon. Finalizing parser POC to parse install-guides to BASH for testing install guides and also auto-creation of guest side scripts for training-labs '''Training Guides: Matjaz Pancur''' Removed unused images for Training guides, improvements on Getting Started (core and optional services, link updates). '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Rodrigo Caballero''' No report this week. == Core Team Review == Regretfully, Diane Fleming is no longer a core team member. I'd like to thank Diane for all her contributions to our team. She's been a powerhouse core team member since well before I did my very first OpenStack patch, and I think it's fair to say that many of us wouldn't be here without Diane's support and guidance. == Site Stats == The number of people browsing the site using Opera has dropped by 5% over the past 30 days, but nearly 20% more people are using Edge (which I'm told is the new Windows browser that's replacing IE). Oddly, IE users have increased slightly as well, though, by 7%. Are people abandoning their Macs?! == Doc team meeting == Next meetings: The APAC meeting was held this week (big thanks to Joseph for chairing that meeting in my absence!), you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-07-13 Next meetings: US: Wednesday 20 July, 19:00 UTC APAC: Wednesday 27 July, 00:30 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#15_July_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

[Bug 1600704] Re: 例: CentOS イメージ in Virtual Machine Image GuideのACPI サービスのインストールについて
by KATO Tomoyuki 12 Jul '16

12 Jul '16

It is difficult to configure the ACPI service during CentOS installaion. I recommend to move the section after the cloud-init section. ** Project changed: openstack-i18n => openstack-manuals ** Changed in: openstack-manuals Status: New => Confirmed ** Changed in: openstack-manuals Assignee: (unassigned) => KATO Tomoyuki (kato-tomoyuki) ** Changed in: openstack-manuals Importance: Undecided => Medium -- 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/1600704 Title: 例: CentOS イメージ in Virtual Machine Image GuideのACPI サービスのインストールについて Status in openstack-manuals: Confirmed Bug description: English description is in #1 ACPI サービスのインストールをCentOS 7のインストール中にやるような流れになっていますが、それは難しいのでCentOSゲストの中で作業をやる「cloud-init を使用した公開鍵の取得」のあたりに「ACPI サービスのインストール」のインストール手順を移動した方が良いです。 ----------------------------------- Release: 0.9 on 2016-07-11 00:30 SHA: e49aed7a448b0ca377553d24d1179f5e6cda9727 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/image-gu… URL: http://docs.openstack.org/ja/image-guide/centos-image.html To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1600704/+subscriptions

1 0

What's Up, Doc? 8 July
by Lana Brindley 08 Jul '16

08 Jul '16

Hi everyone, This week I'm pleased to report that the index page for the new Install Tutorials is up and running! We also had some lengthy discussions about the use of conditionalised formatting (with ``only``), so there were a few meaty topics to go through in the meeting this week. It's also been way too long since we last did a core team review, so that happened this week. I'd also like to remind you that the CFP for Barcelona is only open until mid next week, so get your proposals in soon! == Progress towards Newton == 89 days to go! Bugs closed so far: 256 I think 50 bugs in two weeks is something of a record! Thanks to all the bug smashers working hard this week :) Newton deliverables: https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables Feel free to add more detail and cross things off as they are achieved throughout the release. The CFP for Barcelona is open now, until 13 July. If you want to brainstorm some documentation-related ideas, please get in touch! == Speciality Team Reports == '''HA Guide: Bogdan Dobrelya''' No report this week. '''Install Guide: Lana Brindley''' Index page is now up, needs some iteration to improve. Decided against using ``only`` for now (review after Newton), Manila patch to be updated. Next meeting: 19 July 0600 UTC '''Networking Guide: Edgar Magana''' No meeting this week. Keep trying to move documentation from other dispersed places to the networking guide. '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' Adding the consistency notes to the work items wiki page. Team emails. '''Ops Guide: Shilla Saebi''' No report this week. '''API Guide: Anne Gentle''' Sign up on the etherpad to participate in a keystone Identity API sprint: https://etherpad.openstack.org/p/keystone-api-sprint New patch this week to migrate the ceilometer Telemetry API docs, please review: https://review.openstack.org/334028 Thank you Khushbu! Need another +2 from the swift team for their migration patch: https://review.openstack.org/#/c/312315/ Updated patch in the governance repo projects.yaml file to indicate both contributor docs URLs and API docs URLs: https://review.openstack.org/#/c/316396/ Consider a work in progress for URL completeness and accuracy, but please review for format. Responding to input about API versions and release versions. See http://lists.openstack.org/pipermail/openstack-docs/2016-July/008818.html '''Config/CLI Ref: Tomoyuki Kato''' Closed many bugs. Implementing common configuration sections for shared services and libraries. Updated a few clients reference, and added solum client. '''Training labs: Pranav Salunke, Roger Luethi''' No report this week. '''Training Guides: Matjaz Pancur''' No report this week. '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Rodrigo Caballero''' Three out of the five personas have been created and are being reviewed. https://review.openstack.org/#/c/326662/ The last two personas will be added to the change within the week. It was suggested to add a checklist for developers to be able to identify the appropriate persona for their work. == Core Team Review == The core team have completed their review for July, and we would like to welcome Joseph Robinson to the openstack-doc-core team. Joseph has been leading the User Guides speciality team for some time now, and has been a docs-specs-core as part of that role. Welcome to the larger core team, Joseph, we're really pleased to have you aboard :) == Site Stats == 25% of our hits are coming from new (rather than returning) users. == Doc team meeting == Next meetings: The US meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-07-06 Next meetings: APAC: Wednesday 13 July, 00:30 UTC US: Wednesday 20 July, 19:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#8_July_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Release notes translation
by Ying Chun Guo 05 Jul '16

05 Jul '16

Hello, team Release notes[1] are published. I know our tools don't support release notes at present. I have gotten requests from Chinese team to translate release notes. Any suggestions to do that? Surely we can download and translate offline. One more question is where we should put the translated release notes. I hope to get some inputs from other language teams who want to translate release notes. Thank you. Best regards Ying Chun Guo (Daisy) [1] http://releases.openstack.org/mitaka/index.html

9 9

no meeting 7 July
by Kato, Tomoyuki 05 Jul '16

05 Jul '16

Hi I18n team, No meeting 7 July. I have OpenStack Days Tokyo in Japan, 6-7 July. And, I'm leading the Upstream Training in Japan at that time! Regards, KATO Tomoyuki

1 0

[Bug 1593281] [NEW] Wrong title in Mitaka Ubuntu install doc in FR
by Pauline Castets 02 Jul '16

02 Jul '16

Public bug reported: The page title is currently "Installer et configurer un nœud contrôleur" instead of "Installer et configurer un nœud Compute". http://docs.openstack.org/mitaka/fr/install-guide-ubuntu/nova-compute-insta… ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: i18n install-guide translation -- 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/1593281 Title: Wrong title in Mitaka Ubuntu install doc in FR Status in openstack i18n: New Bug description: The page title is currently "Installer et configurer un nœud contrôleur" instead of "Installer et configurer un nœud Compute". http://docs.openstack.org/mitaka/fr/install-guide-ubuntu/nova-compute-insta… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1593281/+subscriptions

3 2

[Bug 1536226] Re: Not all .po files compiled
by OpenStack Infra 01 Jul '16

01 Jul '16

Reviewed: https://review.openstack.org/319279 Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=1d8a6a96329b87300d… Submitter: Jenkins Branch: master commit 1d8a6a96329b87300dcf711912ab3b1c9f428cf3 Author: Sven Anderson <sven(a)redhat.com> Date: Fri May 20 16:23:55 2016 +0200 Let setup.py compile_catalog process all language files Two years ago the translation files have been split into several files, separating the log messages of different log levels from each other, like X.pot, X-log-warning.pot, X-log-info.pot, and so on. However, the setup.py command `compile_catalogs`, that comes from the babel package and compiles the corresponding .po files into .mo files, only supported one file per python package. This means that during packaging `compile_catalogs` never compiled the X-log-*.po files, so the corresponding translations were always missing. Since babel 2.3 the domain can be set to a space separated list of domains. This change adds the the additional log level files to the domain list. The obsolete check that .po and .pot files are valid is removed from tox.ini. Change-Id: I4d05c98b8ddd1a8416d7e0bc0298e86a0adc77d8 Closes-Bug: #1536226 ** Changed in: heat 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/1536226 Title: Not all .po files compiled Status in Cinder: New Status in Glance: In Progress Status in heat: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in neutron: New Status in OpenStack Compute (nova): Fix Released Status in openstack i18n: New 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

What's Up, Doc? 24 June 2016
by Lana Brindley 24 Jun '16

24 Jun '16

Hi everyone, We're starting to see a real rush of projects publishing their Install Guides this week, which is really exciting! We're also working on getting the index page on docs.openstack.org up and running, so we should have that ready to go up by the time I'm writing this newsletter next week. Well done to all the docs people, and the cross-project liaisons who have been working hard to make this happen. It's great to see it all start to come together :) == Progress towards Newton == 103 days to go! Bugs closed so far: 207 Newton deliverables: https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables Feel free to add more detail and cross things off as they are achieved throughout the release. Also, just a note that the CFP for Barcelona is open now, until 13 July. If you want to brainstorm some documentation-related ideas, please get in touch! == Speciality Team Reports == '''HA Guide: Bogdan Dobrelya''' No report this week. '''Install Guide: Lana Brindley''' Swift, Manila patches in progress. Petr is working on the index page: https://review.openstack.org/331704 Feedback requested! Next meeting: 5 July 0600 UTC '''Networking Guide: Edgar Magana''' No report this week. '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' No report this week. '''Ops Guide: Shilla Saebi''' Team is currently reviewing enterprise ops documentation to incorporate into the Ops Guide. Ops tasks are documented here: https://etherpad.openstack.org/p/ops-arch-tasks OpenStack ops guide reorg in progress & documented here: https://etherpad.openstack.org/p/ops-guide-reorg Members of the ops guide team are joining ops meetings to find volunteers '''API Guide: Anne Gentle''' Progress ongoing on navigation for multiple OpenStack APIs: https://review.openstack.org/#/c/329508 Working on lists of project's API references that don't use RST+YAML framework: http://lists.openstack.org/pipermail/openstack-docs/2016-June/008775.html '''Config/CLI Ref: Tomoyuki Kato''' Got some comments for improvements from Brian Rosmaita, Hemanth Makkapati and Richard Jones. Thank you! Closed many bugs for Configuration Reference. Updated openstack, glance, neutron-sanity-check, and trove-manage CLI reference. '''Training labs: Pranav Salunke, Roger Luethi''' Webpage is looking good and also all the URL's point to the right link http://docs.openstack.org/training_labs/ Trying to finalize PXE support https://review.openstack.org/#/c/305991/ '''Training Guides: Matjaz Pancur''' Italian translation of the Upstream training Details about running a Lego session (https://review.openstack.org/#/c/325020/, https://review.openstack.org/#/c/330819/) '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Rodrigo Caballero''' No report this week. == Site Stats == The top five search terms on the site so far during June: snapshot, cinder, nova, security group, quota == Doc team meeting == Next meetings: The US meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-06-22 Next meetings: APAC: Wednesday 29 June, 00:30 UTC US: Wednesday 6 July, 19:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#24_June_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Re: [OpenStack-I18n] Current status of important topics??
by Kato, Tomoyuki 23 Jun '16

23 Jun '16

Hi Akihiro, All stated things are ongoing. A little slow progress, but I believe we will archive them for Newton release. KATO Tomoyuki > Hi all, > > Newton-2 is approaching. > I would like to know the current status of important topics in Newton cycle. > IIRC, we have several critical and important topics Kato-san listed. > > ## Translation check site > We spent two cycles already, but it is not yet ready. > We need to wait it one more cycle? > > ## Glossary management > I would like to update Japanese glossary with our latest glossary > but it is not easy to add several number of new entries to PO file manually. > Is there any progress? If we don't plan any change soon, > I will import Japanese glossary on Wiki into PO glossary by script (no > manual edit). > > ## Release notes translation > Are translated versions published somewhere? > > > Unfortunately I cannot spend time for these efforts as I mentioned before. > I hope you have good progress. > > Akihiro > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

2 1

Welcome new Cores and extra ATCs!
by Kato, Tomoyuki 21 Jun '16

21 Jun '16

Hi team, I'm happy to announce new cores and extra ATCs. Congratulations! Core: Frank Kloeker, Ian Y. Choi, JF Taltavull in honor of very active contribution for team extra ATC: Alex Eng, Carlos Munoz in honor of active Zanata development and support Best Regards, KATO Tomoyuki

10 10

[vote] meeting time change
by Kato, Tomoyuki 17 Jun '16

17 Jun '16

Hi team, As Akihiro noticed, we have booking issue of IRC meeting channel. Taking this opportunity, I'm considering change the meeting time. Which do you like? Or, another? Option 1. bi-weekly meeting, with two time slots # Similar to current cycle Every four weeks on Thursday at 0600 UTC Every four weeks on Thursday at 1300 UTC Option 2. bi-weekly meeting, with two time slots # Change to Americas friendly Every four weeks on Thursday at 0200 UTC Every four weeks on Thursday at 1300 UTC Option 3. twice a month, with two time slots # Keep current cycle. Don't take cake the booking issue :) Week 1 of the month on Thursday at 0600 UTC Week 3 of the month on Thursday at 1300 UTC [1] http://lists.openstack.org/pipermail/openstack-i18n/2016-May/002192.html Best Regards, KATO Tomoyuki

9 10

What's Up, Doc? 17 June 2016
by Lana Brindley 17 Jun '16

17 Jun '16

Hi everyone, This week I've very pleased to announce that we have our first project-specific Install Guide published! Petr Kovar got Heat over the line in first place, and it's looking great: http://docs.openstack.org/project-install-guide/orchestration/draft/index.h… Well done Petr, and of course all the wonderful docs people who helped us get to this point. We're also expecting to see Trove published very soon. I've been using the lessons learned from these early projects to flesh out our instructions a little more, so it should be even easier for projects to get their Install Guides up and running. We still need to create the central index, but it's all starting to come together now. I'm also excited to announce that, for the very first time, we have a specific Ops Cross-Project Liaison. Please welcome Robert Starmer to the CPL family :) == Progress towards Newton == 110 days to go! Bugs closed so far: 185 Newton deliverables: https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables Feel free to add more detail and cross things off as they are achieved throughout the release. Also, just a note that the CFP for Barcelona is open now, until 13 July. If you want to brainstorm some documentation-related ideas, please get in touch! == Speciality Team Reports == '''HA Guide: Bogdan Dobrelya''' No report this week. '''Install Guide: Lana Brindley''' Orchestration is done! Well done, Petr :) Working on updating instructions in the Contributor Guide. Instructions: http://docs.openstack.org/contributor-guide/project-install-guide.html Next meeting: Tue 21 June 0600 UTC '''Networking Guide: Edgar Magana''' No report this week. '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' Began a consistency and IA plan, and held the US meeting. Emailing one new interested contributor. '''Ops Guide: Darren Chan''' Some architecture content moved from the Ops Guide to the draft Arch Guide. Patches will be submitted to remove old content from the Ops Guide. Team is currently reviewing enterprise ops documentation to incorporate into the Ops Guide. '''API Guide: Anne Gentle''' Check out all the open reviews for api-ref: https://review.openstack.org/#/q/status:open+file:api-ref Nice. Went to weekly team meeting for swift, landed build patch for swift's api-ref, responding to reviews. Noodling with Karen Bradshaw about API navigation, https://review.openstack.org/#/c/329508/ (though I can't take any credit for the work!) '''Config/CLI Ref: Tomoyuki Kato''' Closed many bugs continuously. Started working on the common configurations for shared services and libraries. '''Training labs: Pranav Salunke, Roger Luethi''' No report this week. '''Training Guides: Matjaz Pancur''' No report this week. '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Stephen Ballard''' No report this week. == Training Guides/Labs Core Team Changes == We've adjusted the training guides and labs core teams so that speciality team leads are core in their own repos, and the docs core team is an 'included group' in both repos. This is intended to stop the core teams for these groups drifting out of date too quickly. Note that it is expected that docs cores will not be the primary reviewers/mergers for training repos, but are there as backup in case extra eyes are needed. That responsibility will continue to lie with the training teams themselves, as they know the codebase the best. You can see the updated core team lists here: Training Guides: https://review.openstack.org/#/admin/groups/uuid-3490bf37012cb344104cb315f3… Training Labs: https://review.openstack.org/#/admin/groups/1118,members == Site Stats == During May the top viewed book was the Mitaka Ubuntu Install Guide, followed closely by the Mitaka RDO Install Guide. Rolling into third place was the Admin Guide. Also, apologies for an error I made in this section last week. The correct number for the total number of views in May was 2,365,626. == Doc team meeting == Next meetings: The APAC meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-06-15 Next meetings: US: Wednesday 22 June, 19:00 UTC APAC: Wednesday 29 June, 00:30 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#17_June_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

FYI: Translation Sync jobs in Healthboard
by Andreas Jaeger 15 Jun '16

15 Jun '16

Thanks to Matthew's work on the OpenStack Health board, there's now an easy way to check whether any of the translation infra jobs fail: Post jobs - syncing to Zanata: http://status.openstack.org/openstack-health/#/g/build_queue/post?groupKey=… Periodic jobs: Syncing into repos: http://status.openstack.org/openstack-health/#/g/build_queue/periodic?group… Hope that helps reviewing what's happening for those that are curious like me, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 2

Re: [OpenStack-I18n] FYI: Translation Sync jobs in Healthboard
by Kato, Tomoyuki 15 Jun '16

15 Jun '16

Thanks, Matthew, Andreas. It is exactly what I need. KATO Tomoyuki > Thanks to Matthew's work on the OpenStack Health board, there's now an easy > way to check whether any of the translation infra jobs fail: > > Post jobs - syncing to Zanata: > > http://status.openstack.org/openstack-health/#/g/build_queue/post?grou > pKey=build_queue&searchJob=translation > > Periodic jobs: Syncing into repos: > http://status.openstack.org/openstack-health/#/g/build_queue/periodic? > groupKey=build_queue&searchJob=translation > > Hope that helps reviewing what's happening for those that are curious like > me, > > Andreas

2 2

[Bug 1580585] [NEW] [install-guide] Korean: "one or greater" should be translated into Korean
by Ian Y. Choi 14 Jun '16

14 Jun '16

Public bug reported: In Korean install-guide documentation, one sentence looks strange : "명령에대해 one or greater 값으로 반환되면, compute 노드에서 하드웨어 가속을 지원하는 것이니 추가적인 구성이 필요하지 않습니다." ( http://docs.openstack.org/mitaka/ko_KR/install-guide-ubuntu/nova-compute-in… ) "one or greater" should be translated. ** Affects: openstack-i18n Importance: Undecided Status: Confirmed ** Tags: install-guide korean ** Tags added: korean ** Changed in: openstack-i18n Status: New => Confirmed ** Tags added: 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/1580585 Title: [install-guide] Korean: "one or greater" should be translated into Korean Status in openstack i18n: Confirmed Bug description: In Korean install-guide documentation, one sentence looks strange : "명령에대해 one or greater 값으로 반환되면, compute 노드에서 하드웨어 가속을 지원하는 것이니 추가적인 구성이 필요하지 않습니다." ( http://docs.openstack.org/mitaka/ko_KR/install-guide-ubuntu/nova-compute-in… ) "one or greater" should be translated. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1580585/+subscriptions

1 1

[Bug 1542487] Re: extraneous spaces in some files in Glance translations
by Ian Y. Choi 10 Jun '16

10 Jun '16

Italian po files were also fixed through : https://review.openstack.org/#/c/325542/2/glance/locale/it/LC_MESSAGES/glan… : https://review.openstack.org/#/c/325543/1/glance/locale/it/LC_MESSAGES/glan… ** Changed in: openstack-i18n Status: Fix Committed => 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/1542487 Title: extraneous spaces in some files in Glance translations Status in openstack i18n: Fix Released Bug description: Left comments in the files on this review: https://review.openstack.org/#/c/276056/2 The two files affected are: * glance/locale/it/LC_MESSAGES/glance.po * glance/locale/ko_KR/LC_MESSAGES/glance.po To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1542487/+subscriptions

2 1

What's Up, Doc? 10 June 2016
by Lana Brindley 10 Jun '16

10 Jun '16

Hi everyone, My week has been spent on the Install Guide, and a big thanks to Andreas for getting the Infra patch up and documenting the new process. The Install Guide team meeting was well attended this week, and I've been following up on the actions from that. I also contacted the cross project liaisons with the information they need to get their content moved, and I'm looking forward to seeing some of these start work next week. In other news, Joseph has been busy reviewing the User Guides, and could use a little help working on the information architecture, and getting a few new projects documented. User Guide meetings are held in US and APAC timezones and volunteers are essential to get this effort complete for Newton. Get all the info here: https://wiki.openstack.org/wiki/User_Guides == Progress towards Newton == 117 days to go! Bugs closed so far: 163 Newton deliverables: https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables Feel free to add more detail and cross things off as they are achieved throughout the release. == Speciality Team Reports == '''HA Guide: Bogdan Dobrelya''' No report this week. '''Install Guide: Lana Brindley''' Infra patch: https://review.openstack.org/#/c/326039/ Instructions: http://docs.openstack.org/contributor-guide/project-install-guide.html Next meeting: Tue 21 June 0600 UTC '''Networking Guide: Edgar Magana''' No meeting this week. Working on a better ToC for the guide that may impact of the of scenarios. Moving more networking content from other guides into the Networking one in order to keep everything in one central point and better updated. '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' Outstanding Tasks - Contacting more project teams for inclusion status, IA plans for the new guide. Some team discussion on fixing old links - contact me if anyone is interested in contributing more content to the User Guides team. '''Ops Guide: Shilla Saebi''' Ops tasks are documented here: https://etherpad.openstack.org/p/ops-arch-tasks OpenStack ops guide reorg in progress & documented here: https://etherpad.openstack.org/p/ops-guide-reorg Working on posting enterprise docs for cleanup. Looking for volunteers in ops/arch docs group to attend ops specific meetings to find additional info and help. '''API Guide: Anne Gentle''' Call for help for unified all-OpenStack API navigation design: http://lists.openstack.org/pipermail/openstack-docs/2016-June/008730.html Discussing project-level organization in https://review.openstack.org/312259 Discussing source organization in https://review.openstack.org/314819 Redirects and deletions in api-site are welcomed! For example, see https://review.openstack.org/327399 Updated README for api-site: https://review.openstack.org/327395 '''Config/CLI Ref: Tomoyuki Kato''' Closed a few bugs continuously. Cleaned up many bugs about tool-generated configuration options that are already released for Mitaka. **We need folks for vendor plug-in docs from each vendor.** '''Training labs: Pranav Salunke, Roger Luethi''' Working on the training-labs landing page to make it look much better. Reintroducing the tooling to build zip files. Working on PXE support for baremetal provisioning. Working on Python port of training-labs. '''Training Guides: Matjaz Pancur''' No report this week. '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Stephen Ballard''' No report this week. == Site Stats == During May, the docs.openstack.org site had 620 sessions, with just under 20% by new users. The average time of all sessions for the month was about 5 and a half minutes, looking at an average of 3 and a half pages. == Doc team meeting == Next meetings: The US meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-06-08 Next meetings: APAC: Wednesday 15 June, 00:30 UTC US: Wednesday 22 June, 19:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#10_June_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

2 1

[Bug 1536226] Re: Not all .po files compiled
by OpenStack Infra 07 Jun '16

07 Jun '16

Reviewed: https://review.openstack.org/319260 Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=16d0cdba47a0ad… Submitter: Jenkins Branch: master commit 16d0cdba47a0ad976f1500cd91c420860c3ad149 Author: Sven Anderson <sven(a)redhat.com> Date: Fri May 20 15:54:27 2016 +0200 Let setup.py compile_catalog process all language files Two years ago the translation files have been split into several files, separating the log messages of different log levels from each other, like X.pot, X-log-warning.pot, X-log-info.pot, and so on. However, the setup.py command `compile_catalogs`, that comes from the babel package and compiles the corresponding .po files into .mo files, only supported one file per python package. This means that during packaging `compile_catalogs` never compiled the X-log-*.po files, so the corresponding translations were always missing. Since babel 2.3 the domain can be set to a space separated list of domains. This change adds the the additional log level files to the domain list. The obsolete check that .po and .pot files are valid is removed from tox.ini. Change-Id: I1f0bfb181e2b84ac6dd0ce61881cd2cc4400bdcb Closes-Bug: #1536226 ** Changed in: keystone 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/1536226 Title: Not all .po files compiled Status in Cinder: New Status in Glance: In Progress Status in heat: New Status in OpenStack Identity (keystone): Fix Released Status in neutron: New Status in OpenStack Compute (nova): Fix Released Status in openstack i18n: New 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

Re: [OpenStack-I18n] [openstack-dev] [zaqar][zaqar-ui][i18n] Translation enabled
by Akihiro Motoki 07 Jun '16

07 Jun '16

Forwarded to openstack-i18n list. > Shu The dev list is not an appropriate place to announce this kind of information. Translators are not developers, so in generally translators do not subscribe the dev ML. Akihiro 2016-06-07 10:19 GMT+09:00 Shuu Mutou <shu-mutou(a)rf.jp.nec.com>: > Hi everyone, > > Now, we can translate Zaqar-UI on Zanata, please translate Zaqar-UI into your native language!! > Translation is another good review for Zaqar-UI, so I hope your help. > > See also https://wiki.openstack.org/wiki/I18nTeam > > > Best regards, > > Shu Muto > > > __________________________________________________________________________ > 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

What's Up, Doc? 3 June 2016
by Lana Brindley 03 Jun '16

03 Jun '16

Hi everyone, I'm very pleased to be able to announce the results of our Install Guide naming poll this week. We ended up with 31 responses, and a very clear winner in "OpenStack Installation Tutorial". Thank you to everyone who voted! Also, just a note that I'm still very much in need of representatives from the various project teams to pitch in and help us get things running. Please make sure your project is represented by coming along to meetings, or at least contacting us through the mailing list. This week I've also spent some time with the Upstream training team, identifying gaps in the current material, and preparing for Barcelona. == Progress towards Newton == 124 days to go! Bugs closed so far: 134 Newton deliverables https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables Feel free to add more detail and cross things off as they are achieved throughout the release. == Speciality Team Reports == '''HA Guide: Bogdan Dobrelya''' No report this week. '''Install Guide: Lana Brindley''' Poll concluded, winner is "OpenStack Installation Tutorial". Connected with CPLs this week to encourage more participation. Next meeting: Tue 7 June 0600 UTC. '''Networking Guide: Edgar Magana''' Moved DHCP HA chapter to Networking Guide for better maintenance and updates. Planning to move more sections and focus on DVR HA. Suffering of very low attendance for the IRC meeting. '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' Some contact with the Magnum team. Held meetings, brought up the link changes, which is something I most need some assistance with. IA plan still forthcoming. '''Ops Guide: Shilla Saebi''' No report this week. '''API Guide: Anne Gentle''' New layout for API reference docs from additions to openstackdocs theme. Also already added four-color scheme for GET/PUT/POST/DELETE Thanks Graham Hayes! Work in progress here: https://api.os.gra.ham.ie/compute/ Reviews: https://review.openstack.org/#/q/project:openstack/openstackdocstheme+statu… and https://review.openstack.org/#/q/project:openstack/os-api-ref+status:open Discussion on SDKs and FirstApp audience happening on user-committee list: http://lists.openstack.org/pipermail/user-committee/2016-May/000889.html '''Config/CLI Ref: Tomoyuki Kato''' Closed some bugs with Mitaka backport. Fixed the incorrect RST markup at the new options section, with generation tool update. '''Training labs: Pranav Salunke, Roger Luethi''' No report this week. '''Training Guides: Matjaz Pancur''' Upstream training updates, Barcelona schedule. '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Stephen Ballard''' The first prototype of content was presented and source information gaps were identified. A first draft will be complete by June 9. == Site Stats == In the Install Guide naming poll, "OpenStack Installation Tutorial" finished with 29% of the vote, well ahead of "OpenStack Evaluation Setup Guide" at 19%, and "Basic Install Guide" at 16%. And, because charts are fun, here are the final results: https://docs.google.com/spreadsheets/d/1VlNFebI_KFobs-XIT5oRhULRymwrqON8SV9… I personally thought "OpenStack from Scratch" was the most creative title. And the potentially confusing "Manual Install Guide" ("Guided Install Manual"?) had a small following at just under 10% of the vote. Thanks for all the great suggestions :) == Doc team meeting == Next meetings: The APAC meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-06-01 Next meetings: US: Wednesday 8 June, 19:00 UTC APAC: Wednesday 15 June, 00:30 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#3_June_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Documentation list for translation
by Kato, Tomoyuki 03 Jun '16

03 Jun '16

Hi team, As Akihiro requested at today's meeting, I have written the documentation list for translation. https://etherpad.openstack.org/p/i18n-docs If it contains an error, please correct it. Regards, KATO Tomoyuki

2 1

[Bug 1536226] Re: Not all .po files compiled
by Sven Anderson 02 Jun '16

02 Jun '16

** Also affects: cinder Importance: Undecided Status: New ** Also affects: heat Importance: Undecided Status: New ** Also affects: neutron Importance: Undecided Status: New ** Changed in: cinder Assignee: (unassigned) => Sven Anderson (ansiwen) ** Changed in: keystone Assignee: (unassigned) => Sven Anderson (ansiwen) ** Changed in: heat Assignee: (unassigned) => Sven Anderson (ansiwen) ** Changed in: neutron Assignee: (unassigned) => Sven Anderson (ansiwen) -- 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: New Status in Glance: In Progress Status in heat: New Status in OpenStack Identity (keystone): New Status in neutron: New Status in OpenStack Compute (nova): Fix Released Status in openstack i18n: New 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 1536226] Re: Not all .po files compiled
by Andreas Jaeger 02 Jun '16

02 Jun '16

keystone change: https://review.openstack.org/#/c/319260/ ** Also affects: keystone 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/1536226 Title: Not all .po files compiled Status in Glance: In Progress Status in OpenStack Identity (keystone): New Status in OpenStack Compute (nova): Fix Released Status in openstack i18n: New 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/glance/+bug/1536226/+subscriptions

1 0

meeting in 2 hours at 06:00 UTC
by Kato, Tomoyuki 02 Jun '16

02 Jun '16

Hi team, I18n meeting will start in 2 hours in #openstack-meeting. See you there, KATO Tomoyuki

1 0

[Bug 1536226] Re: Not all .po files compiled
by Nikhil Komawar 29 May '16

29 May '16

** Also affects: glance Importance: Undecided Status: New ** Changed in: glance Status: New => In Progress ** Changed in: glance Importance: Undecided => High ** Changed in: glance Assignee: (unassigned) => Sven Anderson (ansiwen) -- 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 Glance: In Progress Status in OpenStack Compute (nova): Fix Released Status in openstack i18n: New 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/glance/+bug/1536226/+subscriptions

1 0

What's Up, Doc? 27 May 2016
by Lana Brindley 27 May '16

27 May '16

Hi everyone, This week I've been focused on getting the Install Guide project back up and running, with the team meeting being rebooted, our specs finally merged, and organising the list of tasks to be getting on with. Also, don't forget to vote in our naming poll: http://goo.gl/forms/Eqf9WOGqsXjkRbdc2 I'm still very much in need of representatives from the various project teams to pitch in and help us get things running. Please make sure your project is represented by coming along to meetings, or at least contacting us through the mailing list. In other news, the Ops and Arch Guide re-architecture is proceeding apace. Specs were merged this week, and the new Arch Guide ToC is looking great! Check it out here: http://specs.openstack.org/openstack/docs-specs/specs/newton/arch-guide-res… We are also still looking for feedback on the current Ops guide. Add your notes here: https://etherpad.openstack.org/p/ops-guide-reorg == Progress towards Newton == 131 days to go! Bugs closed so far: 107 Newton deliverables https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables Feel free to add more detail and cross things off as they are achieved throughout the release. == Speciality Team Reports == '''HA Guide: Bogdan Dobrelya''' No report this week. '''Install Guide: Lana Brindley''' Specs are now merged, an blueprints created. Tasks listed here: https://wiki.openstack.org/wiki/Documentation/InstallGuideWorkItems Please go ahead and pick up work items. Need project representation in meetings. Next meeting: Tue 7 June 0600 UTC '''Networking Guide: Edgar Magana''' We did not have meeting this week. Nothing to report. Next IRC meeting: Thursday June 2nd at 1600 UTC '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' Action items to follow up - email meeting minutes to the mailing list to update the community. Currently, the team has two contributors. Please let me know if you're interested in working on the User Guide Team. '''Ops Guide: Shilla Saebi''' Shilla & Darren working on collecting enterprise docs to push upstream Ops tasks are documented here: https://etherpad.openstack.org/p/ops-arch-tasks OpenStack ops guide reorg in progress & documented here: https://etherpad.openstack.org/p/ops-guide-reorg Spec was merged: https://review.openstack.org/#/c/311998/ '''API Guide: Anne Gentle''' No report this week. '''Config/CLI Ref: Tomoyuki Kato''' A few configuration docs patches for some vendor plug-ins has been merged, with mitaka backport. Heat CLI is marked as deprecated. '''Training labs: Pranav Salunke, Roger Luethi''' No report this week. '''Training Guides: Matjaz Pancur''' Updates for Upstream training material '''Hypervisor Tuning Guide: Blair Bethwaite No report this week. '''UX/UI Guidelines: Michael Tullis, Stephen Ballard''' No report this week. == Site Stats == This month, two thirds of our site visitors have been using their Mac to read the docs. Just under 30% used Windows, and Linux rounded out the remainder at 4%. So far in the Install Guide naming poll, "OpenStack Installation Tutorial" has a commanding lead at 30%, with "Basic Install Guide" and "OpenStack Evaluation Setup Guide" (try saying that ten times fast!) tying for second place with 17% of the vote each. I'll keep the poll open for another week or so, and announce our winning name in next week's newsletter. == Doc team meeting == Next meetings: The US meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-05-25 Next meetings: APAC: Wednesday 1 June, 00:30 UTC US: Wednesday 8 June, 19:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#27_May_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Re: [OpenStack-I18n] stackalytics translation stats API is broken????
by Kato, Tomoyuki 23 May '16

23 May '16

> Hmm... It seems a problem is limited to "stable-mitaka vs stable/mitaka". > > It seems 'master' version of translation stats also has a problem. okay, good information. thanks. > I translated more than 2000 words in 'master' version, but > stackalytics says I translated only 251 words. To understand the situation more exactly, which do you mean 2000 "Words" or "Messages" at Zanata? > Is it better that I stop translation? If exact stats is important for you, you should stop translation. Otherwise, translation process itself works fine. Also, I'm not sure, but we will get proper stats after stackalytics works fine. Regards, KATO Tomoyuki

9 14

[Bug 1581970] [NEW] [Install-guide] Some translated pages are missing even in pot files for liberty
by Ian Y. Choi 23 May '16

23 May '16

Public bug reported: For example, there is a original page : http://docs.openstack.org/liberty/install-guide-ubuntu/common/get_started_o… The translated pages would be :http://docs.openstack.org/liberty/ko_KR/install-guide-ubuntu/common/get_started_openstack_networking.html : http://docs.openstack.org/liberty/ja/install-guide-ubuntu/common/get_starte… ... However, the pages are not translated! Interestingly, pot files do not contain the original strings on that page : https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/common-… However, there is a original rst file : https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/common-… ** Affects: openstack-i18n Importance: Undecided Status: New ** Affects: openstack-manuals Importance: Undecided Status: New ** Also affects: openstack-manuals 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/1581970 Title: [Install-guide] Some translated pages are missing even in pot files for liberty Status in openstack i18n: New Status in openstack-manuals: New Bug description: For example, there is a original page : http://docs.openstack.org/liberty/install-guide-ubuntu/common/get_started_o… The translated pages would be :http://docs.openstack.org/liberty/ko_KR/install-guide-ubuntu/common/get_started_openstack_networking.html : http://docs.openstack.org/liberty/ja/install-guide-ubuntu/common/get_starte… ... However, the pages are not translated! Interestingly, pot files do not contain the original strings on that page : https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/common-… However, there is a original rst file : https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/common-… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1581970/+subscriptions

2 1

[Bug 1556887] Re: Themes setting is not translated
by Rob Cresswell 21 May '16

21 May '16

It seems like the string is tranlatable, but this is an i18n issue. ** Changed in: horizon Status: Confirmed => Incomplete ** Also affects: openstack-i18n Importance: Undecided Status: New ** Changed in: horizon Status: Incomplete => Invalid ** Changed in: horizon Milestone: newton-1 => None -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1556887 Title: Themes setting is not translated Status in OpenStack Dashboard (Horizon): Invalid Status in openstack i18n: New Bug description: The theme string should be translated. The screen shot is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1556887/+subscriptions

1 0

What's Up, Doc? 20 May 2016
by Lana Brindley 20 May '16

20 May '16

Hi everyone, I've been struck down by the dreaded flu this week, so it's been a bit quiet around here. I have, however, crawled out from under the tissues, throat lozenges, and episodes of Containment to pen my regular newsletter for you. See how dedicated I am to the cause? ;) The biggest updates this week have been on the API side of the ship, with the api-site bug list cleared out. Well done to Anne and Atsushi-san for the heavy lifting there. We also saw a lot of speciality team meetings kick off again this week, with more coming next week, so keep an eye on the mailing list and your ical for the projects you're interested in. We have also now hit our stride on the regular docs meetings, with the APAC meeting held this week, and the US one rolling around again next week. If you're a docs cross-project liaison, make sure you check out the timing and pick one that works for you, so we can make sure we're discussing *your* project. == Progress towards Newton == 138 days to go! Bugs closed so far: 89 Newton deliverables https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables Feel free to add more detail and cross things off as they are achieved throughout the release. I will also do my best to ensure it's kept up to date for each newsletter. == Speciality Team Reports == '''HA Guide: Bogdan Dobrelya''' No report this week. '''Install Guide: Lana Brindley''' Meetings start up next week: http://eavesdrop.openstack.org/#Documentation_Install_Team_Meeting Cookie cutter has been merged, repo here: http://git.openstack.org/cgit/openstack/installguide-cookiecutter/ Need to merge spec: https://review.openstack.org/#/c/310588 '''Networking Guide: Edgar Magana''' We have successfully changed the bi-weekly meeting schedule from odd to even weeks. There will not be meeting this week. Next meeting will be on June 2nd. '''Security Guide: Nathaniel Dillon''' No report this week. '''User Guides: Joseph Robinson''' Team Meeting restarted - Just me this week, I'll send a summary to the mailing list to keep everyone up to date, and if anyone is interested in joining in. Python SDK file moving - one item left from the Mitaka patch - Finding a location to move these files - dev and doc mailing list email forthcoming on where to put these files. '''Ops Guide: Shilla Saebi''' No report this week. '''API Guide: Anne Gentle''' The extension, os-api-ref, is now available via Pypi so that all projects can re-use it with test-requirements.txt. Thanks Sean Dague for this effort! Several projects have reviews in progress for their API reference conversion: glance https://review.openstack.org/#/c/312259/, manila https://review.openstack.org/#/c/313874, neutron https://review.openstack.org/#/c/314819, swift https://review.openstack.org/#/c/312315/, trove https://review.openstack.org/#/c/316381. (There are probably more but those are on my radar). Please review the response code table at https://review.openstack.org/#/c/318281/ and http://i.imgur.com/onsRFtI.png for your use cases for API reference docs. '''Config/CLI Ref: Tomoyuki Kato''' No report this week. '''Training labs: Pranav Salunke, Roger Luethi''' No report this week. '''Training Guides: Matjaz Pancur''' Work on the slides for Training guides (https://review.openstack.org/#/c/295016/) Feedback about Upstream training in Austin (see http://eavesdrop.openstack.org/meetings/training_guides/2016/training_guide…) '''Hypervisor Tuning Guide: Blair Bethwaite Hi! I'm going to try looking after this for a while as Joe focuses on other things. Not promising much at this point beyond a little wiki gardening, but longer term I hope to align it with some activities in the scientific-wg (which I'm co-chairing with Stig Telfer), and it will probably become a point of reference for some of the activities we already have planned this cycle. '''UX/UI Guidelines: Michael Tullis, Stephen Ballard''' No report this week. == Site Stats == While 90% of our readers have their browsers set to US English, just under 8% browse in Chinese, and a mere 0.15% use British English. That last one might be just me ;) == Doc team meeting == Next meetings: The APAC meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-05-18 Next meetings: US: Wednesday 25 May, 19:00 UTC APAC: Wednesday 1 June, 00:30 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#20_May_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

2 1

stable-mitaka openstack-manuals is not updated?
by Akihiro Motoki 20 May '16

20 May '16

According to Zanata information, the last update of openstack-manuals stable-mitaka version in Zanata is 13/05/16 19:21 (perhaps my local time JST+09:00). The last merge of openstack-manuals stable/mitaka branch is May 17 18:16 (in my local time too). We cannot access jenkins.openstack.org now (due to the security reason), so I cannot check what happens). Akihiro

4 7

empty PO-Revision-Date in tr_TR neutron log PO file
by Akihiro Motoki 19 May '16

19 May '16

Hi team, There was a report in #-i18n channel that tr_TR neutron PO file contains empty PO-Revision-Date [1]. Can anyone dig into the detail? In addition, there seems very few folks on the IRC channel. Is it a right contact point to the i18n team? Is it better to add some warning to our document to encourage to use the mailing list? Surprisingly, the above it the first conversation in #-i18n channel in May! [1] http://eavesdrop.openstack.org/irclogs/%23openstack-i18n/%23openstack-i18n.… Akihiro

1 0

i18n meeting in IRC meeting calendar looks wrong....
by Akihiro Motoki 19 May '16

19 May '16

OpenStack IRC meeting calendar says that we have a meeting today (19 May) at 0600UTC [1]. However, i18n team doc [2] says we will have a meeting today at 1300UTC, week 3 of May. This means a meeting slot described at [2] is NOT reserved. (Don't worry. The slot is not booked as of today.) I think the reason is because OpenStack IRC meeting scheduler does not support monthly meeting schedule. It only supports weekly or bi-weekly (based on a week number in a year). It is to reduce meeting time conflicts. I have no good solution but it is better to be solved. Just FYI. Akihiro [1] http://eavesdrop.openstack.org/calendars/i18N-team-meeting.ics [2] http://docs.openstack.org/developer/i18n/i18n_team_meeting.html

1 0

Re: [OpenStack-I18n] stackalytics translation stats API is broken????
by Kato, Tomoyuki 17 May '16

17 May '16

> which is Remo(a)rm.ht > > This should be also usable on OpenStack. > > Any other suggestions Hi Remo, As of now, we maintain the user list manually. So, we should add users to the list... I'll check the list, but anyone can submit a patch for addition. http://git.openstack.org/cgit/openstack/i18n/tree/tools/zanata/translation_… Next release of Zanata will support the feature to dump user list with email. Thanks, KATO Tomoyuki

2 1

Re: [OpenStack-I18n] stackalytics translation stats API is broken????
by Ian Y. Choi 17 May '16

17 May '16

Hello Remo! Your translation count on Stackalytics is zero? If then, I think [1] and [2] will help to solve your problem :) [1] http://lists.openstack.org/pipermail/openstack-dev/2016-February/087537.html [2] http://lists.openstack.org/pipermail/openstack-dev/2016-February/087659.html With many thanks, /Ian Remo Mattei wrote on 5/16/2016 2:22 AM: > The last 2 months I translated about 400 words but stack does not even show any. It will be great to get this fixed. > > Thanks > > Inviato da iPhone > >> Il giorno 15 mag 2016, alle ore 09:56, Ian Y. Choi <ianyrchoi(a)gmail.com> ha scritto: >> >> Hello, >> >> I might have found the problem. >> >> The problem is that there can be several 'Translated' results within a week, >> however, those results are saved with the same primary key. >> >> I have just proposed https://review.openstack.org/316460 . >> >> I am not sure whether 'date' field is used on other Stackalytics sources, >> but at least, generating the primary key for translation records on record_processor.py >> does not use 'savedDate' field, as Shengjing mentioned. >> If 'date' field is used on other Stackalytics sources, please tell me, then I will change the review :) >> >> >> With many thanks, >> >> /Ian >> >> >> SJ Zhu wrote on 5/16/2016 12:14 AM: >>>> On Sun, May 15, 2016 at 10:42 PM, Ian Y. Choi <ianyrchoi(a)gmail.com> wrote: >>>> I have a question, although it is not mainly related to wrong Stackalytics >>>> stats. >>>> >>>> I have found that API 'stats/user/%s/%s..%s' >>>> and API 'stats/project/%s/version/%s/contributor/%s/%s..%s' generate >>>> different results. >>>> >>>> For example, from Apr 1 2016 to today, my count is 34320 with the first API, >>>> but the send API generates 29490 for the same period. >>>> >>>> I do know why the two APIs generate different numbers. >>>> Can statistics numbers on user API and the sum of results from each project >>>> API be different? >>> Hi all, >>> >>> Previously Stackalytics uses API >>> 'stats/project/%s/version/%s/contributor/%s/%s..%s'. >>> But I change it to 'stats/user/%s/%s..%s' in >>> https://review.openstack.org/#/c/288871/ >>> >>> I may find the BUG but I have no time to fix it these days. So I hope >>> someone to help. >>> >>> Stackalytics will get the results every week. And >>> 'stats/user/%s/%s..%s' will return >>> everyday's count. However Stackalytics seems not to sum a week's work. >>> >>> To fix it, I think we can change the way how Stackalytics uses >>> Zanata's API. Based on >>> 'stats/user/%s/%s..%s' we can get 'savedDate'. So just use the >>> 'savedDate' to display >>> on Stackalytics. I haven't read the code carefully but I think the >>> change is possible. >>> What's more we can debug the wrong results on Stackalytics more conveniently. >>> >>> But there's another question. How can we fix the old results on Stackalytics? >> >> _______________________________________________ >> OpenStack-I18n mailing list >> OpenStack-I18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >> !DSPAM:5738aa786031686312732! >> >>

3 5

stackalytics translation stats API is broken????
by Akihiro Motoki 15 May '16

15 May '16

Hi, Does stackalytics translation stats API work? I translated 7827 words this month according to Zanata homepage, but stackalytics says just 251 words translated. I translated thousands of words at least 2 or 3 days ago, so I think it should be visible at stackalytics now. I wonder what happens in Stackalytics integration..... Does anyone know the status? Akihiro

5 5

What's Up, Doc? 13 May
by Lana Brindley 13 May '16

13 May '16

= 13 May 2016 = Hi everyone, Wow, what a busy week! I've been mainly focused on the Install Guide speciality team this week, with gathering interested participants, ensuring our specs are ready to be merged, and setting a new meeting time. I'm also pleased to say that our speciality team reports make a post-Summit comeback in this newsletter. Just another reminder that all projects should update their cross-project liaison for docs on the wiki here: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation If you're one of the lucky people nominated by your PTL to be a docs CPL, then please do your very best to attend docs meetings in your favourite timezone to make sure we hear the voice of your project when we're making documentation decisions. Details of upcoming docs meetings are at the end of this newsletter every week. On a related note, it was refreshing to read the conversation from the US meeting this week, and the associated conversation on the mailing lists about developer contributions to documentation. We'd love to find out what it is that prevents you from contributing to the docs, and what the docs team can do to make things that little bit easier for you! Reach out to us either on the dev mailing list (with [docs] in the subject line), or on the docs mailing list at openstack-docs(a)lists.openstack.org. == Progress towards Newton == 145 days to go! Bugs closed so far: 71 Newton deliverables https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables Feel free to add more detail and cross things off as they are achieved throughout the release. I will also do my best to ensure it's kept up to date for each newsletter. The Ops and HA Guides now exist in openstack-manuals, and the old repos have now been set to read-only. We also have the first patch in for the Install Guide 'cookie cutter' template, which is a great start! == Speciality Team Reports == '''HA Guide: Bogdan Dobrelya''' No report this week. '''Install Guide: Lana Brindley''' New meeting time proposed: https://review.openstack.org/#/c/314831/ Still need to merge final spec: https://review.openstack.org/#/c/310588/ If you're interested in helping out, add your name here: https://wiki.openstack.org/wiki/Documentation/InstallGuide#Team_members '''Networking Guide: Edgar Magana''' We are planning to resume the meeting next week. '''Security Guide: Nathaniel Dillon''' Summit Recap: https://etherpad.openstack.org/p/austin-docs-workgroup-security Good conversations around API rate limiting, OSSN in-flight, SecGuide work being prep'd (Thanks to Luke Hinds for taking this on!) Added Doc reviewer (Thanks Shilla and welcome!) Will be focusing on Neutron security '''User Guides: Joseph Robinson''' No report this week. '''Ops Guide: Shilla Saebi''' Proposed architecture guide restructure: https://review.openstack.org/#/c/311998/ Ops guide session Etherpad from Austin: https://etherpad.openstack.org/p/AUS-ops-Docs-ops-guide OpsGuide reorg: https://etherpad.openstack.org/p/PAO-ops-ops-guide-fixing Newton Plans: Review content of both guides, and delete anything out of date Review architecture of both guides, and possibly combine Ops Guide in openstack-manuals repo Gather content from Ops internal documentation '''API Guide: Anne Gentle''' All but two services have someone working on landing a migration patch in the project's repo. Read: Status on bugs and migration http://lists.openstack.org/pipermail/openstack-docs/2016-May/008624.html Read: Summit session recap http://lists.openstack.org/pipermail/openstack-dev/2016-May/094472.html '''Config/CLI Ref: Tomoyuki Kato''' Discussing documenting auto generation of config options with Oslo team. Dropped keystone command-line client from CLI reference. Keystone CLI was removed in python-keystoneclient 3.0.0 release. '''Training labs: Pranav Salunke, Roger Luethi''' Working on adding new features like PXE boot. Stabilizing current release and backends. Figuring out the zip file generation and web site/page. Chaging the meeting time to more CET/CEST friendly time. '''Training Guides: Matjaz Pancur''' No report this week. '''Hypervisor Tuning Guide: Joe Topjian''' No report this week. '''UX/UI Guidelines: Michael Tullis, Stephen Ballard''' No report this week. == Site Stats == The interesting fact I'd like to share with you this week is that just over 25% of our viewers this month are new to the site. == Doc team meeting == Next meetings: The US meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-05-11 Next meetings: APAC: Wednesday 18 May, 00:30 UTC US: Wednesday 25 May, 19:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#13_May_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

where are translated documents (master/stable-mitaka) published
by Akihiro Motoki 11 May '16

11 May '16

Hi, In Zanata, we have master and stable-mitaka versions for openstack-manuals. Where are these translated documents published? For Japanese install guide, I see only http://docs.openstack.org/draft/ja/install-guide-ubuntu/ and no http://docs.openstack.org/mitaka/ja/install-guide-ubuntu/ . Which zanata version (master or stable-mitaka) corresponds to http://docs.openstack.org/draft/ja/install-guide-ubuntu/ ? Akihiro

2 2

[all][i18n] translation import: No more pot files in git trees
by Andreas Jaeger 08 May '16

08 May '16

Instead of storing the generated source translation files (*/locale/*.pot) in git and proposing them as part of the translation import, we publish these files now whenever we push to the translation server also to http://tarballs.openstack.org/translation-source/ Therefore, the source files are not needed in the git repositories anymore, the proposal bot will now - when it proposes translations - remove existing pot files. This will reduce the size of the imports significantly. Please import the translations with these removed pot files: https://review.openstack.org/#/q/status:open+topic:zanata/translations,n,z Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 1

pot files in git trees?
by Andreas Jaeger 07 May '16

07 May '16

Looking at the daily imports we do for our translations, a lot of that is importing pot files (translation source). Do we really need these for anything in the git trees? We've stopped importing those pot files which are not translated at all but import pot files that have translations and update them daily (only if there are real translations as well). I really wonder whether we need these pot files in our git repositories at all, 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

5 14

Re: [OpenStack-I18n] [OpenStack-docs] What's Up, Doc? 6 May 2016
by Matt Kassawara 07 May '16

07 May '16

One significant advantage of central documentation involves providing content in a single location with consistent structure or format that best serves the particular audience. Moving most or all documentation into project trees essentially eliminates this advantage, leaving our audiences with an impression that OpenStack consists of many loosely associated projects rather than a coherent cloud computing solution. However, as a contributor to a few other OpenStack projects who helps other developers contribute to central documentation, I can understand some of the frustrations with it. I prefer to resolve these frustrations and have some ideas that I intend to float in separate thread, but if you don't think that's possible, consider submitting a spec to change the primary purpose of the central documentation team to simply managing links to content in the project trees. On Fri, May 6, 2016 at 10:03 AM, Ildikó Váncsa <ildiko.vancsa(a)ericsson.com> wrote: > Hi Lana, > > Thanks for the summary, it's pretty good reading to catch up what happened > recently. > > I have one question, I might missed a few entries, so please point me to > the right document in this case. We had a docco session with the Telemetry > team and we agreed on moving back the documentation snippets, like for > instance the Install Guide, to the project trees is a really good step and > we're very supportive. In this sense I would like to ask about the plans > regarding the Admin guide. We have a chapter there, which is on one hand > outdated and on the other hand would be better to move under the project > trees as well. Is this plan/desire in line with your plans regarding that > document? > > Thanks, > /Ildikó > > > -----Original Message----- > > From: Lana Brindley [mailto:openstack@lanabrindley.com] > > Sent: May 06, 2016 08:13 > > To: enstack.org; OpenStack Development Mailing List; > openstack-i18n(a)lists.openstack.org > > Subject: What's Up, Doc? 6 May 2016 > > > > Hi everyone, > > > > I hope you all had a safe journey home from Summit, and are now fully > recovered from all the excitement (and jetlag)! I'm really > > pleased with the amount of progress we made this time around. We have a > definitive set of goals for Newton, and I'm confident that > > they're all moving us towards a much better docs suite overall. Of > course, the biggest and most important work we have to do is to get > > our Install Guide changes underway. I'm very excited to see the new > method for documenting OpenStack installation, and can't wait > > to see all our big tent projects contributing to docs in such a > meaningful way. Thank you to everyone (in the room and online) who > > contributed to the Install Guide discussion, and helped us move forward > on this important project. > > > > In other news, I've written a wrapup of the Austin design summit on my > blog, which you might be interested in: > > http://lanabrindley.com/2016/05/05/openstack-newton-summit-docs-wrapup/ > > > > == Progress towards Newton == > > > > 152 days to go! > > > > Bugs closed so far: 61 > > > > Because we have such a specific set of deliverables carved out for > Newton, I've made them their own wiki page: > > https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables > > Feel free to add more detail and cross things off as they are achieved > throughout the release. I will also do my best to ensure it's kept > > up to date for each newsletter. > > > > One of the first tasks we've started work on after Summit is moving the > Ops and HA Guides out of their own repositories and into > > openstack-manuals. As a result, those repositories are now frozen, and > any work you want to do on those books should be in > > openstack-manuals. > > > > We are almost ready to publish the new RST version of the Ops Guide, > there's just a few cleanup edits going in now, so make sure you > > have the right book, in the right repo from now on. This was our very > last book remaining in DocBook XML, so the docs toolchain will > > be removing DocBook XML support. See spec > https://review.openstack.org/311698 for details. > > > > Another migration note is that the API reference content is moving from > api-site to project specific repositories and api-site is now > > frozen. For more detail, see Anne's email: > http://lists.openstack.org/pipermail/openstack-docs/2016-May/008536.html > > > > == Mitaka wrapup == > > > > We performed a Mitaka retrospective at Summit, notes are here: > https://etherpad.openstack.org/p/austin-docs-mitakaretro > > > > In particular, I'd like to call out our hard working tools team Andreas > and Christian, all our Speciality Team leads, and the Mitaka release > > managers Brian and Olga. Well done on a very successful release, > everyone :) > > > > Total bugs closed: 645 > > > > == Site Stats == > > > > Thanks to the lovely people at Foundation (thanks Allison!) I now have > access to more stats than I could possibly guess what to do > > with, and I'm hoping to be able to share some of these with you through > the newsletter. If there's something in particular you would > > like to see, then please let me know and I'll endeavour to record it > here! > > > > So far I can tell you that docs.openstack.org had 1.63M unique > pageviews in April, down slightly from 1.72M in March, and the average > > session duration is just over six minutes, looking at just under 4 pages > per session. > > > > == Doc team meeting == > > > > Next meetings: > > > > We'll be restarting the meeting series next week. > > > > Next meetings: > > US: Wednesday 11 April, 19:00 UTC > > APAC: Wednesday 18 April, 00:30 UTC > > > > Please go ahead and add any agenda items to the meeting page here: > > > https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… > > > > -- > > > > Keep on doc'ing! > > > > Lana > > > > https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#6_May_2016 > > > > -- > > Lana Brindley > > Technical Writer > > Rackspace Cloud Builders Australia > > http://lanabrindley.com > > _______________________________________________ > OpenStack-docs mailing list > OpenStack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs >

1 0

What's Up, Doc? 6 May 2016
by Lana Brindley 06 May '16

06 May '16

Hi everyone, I hope you all had a safe journey home from Summit, and are now fully recovered from all the excitement (and jetlag)! I'm really pleased with the amount of progress we made this time around. We have a definitive set of goals for Newton, and I'm confident that they're all moving us towards a much better docs suite overall. Of course, the biggest and most important work we have to do is to get our Install Guide changes underway. I'm very excited to see the new method for documenting OpenStack installation, and can't wait to see all our big tent projects contributing to docs in such a meaningful way. Thank you to everyone (in the room and online) who contributed to the Install Guide discussion, and helped us move forward on this important project. In other news, I've written a wrapup of the Austin design summit on my blog, which you might be interested in: http://lanabrindley.com/2016/05/05/openstack-newton-summit-docs-wrapup/ == Progress towards Newton == 152 days to go! Bugs closed so far: 61 Because we have such a specific set of deliverables carved out for Newton, I've made them their own wiki page: https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables Feel free to add more detail and cross things off as they are achieved throughout the release. I will also do my best to ensure it's kept up to date for each newsletter. One of the first tasks we've started work on after Summit is moving the Ops and HA Guides out of their own repositories and into openstack-manuals. As a result, those repositories are now frozen, and any work you want to do on those books should be in openstack-manuals. We are almost ready to publish the new RST version of the Ops Guide, there's just a few cleanup edits going in now, so make sure you have the right book, in the right repo from now on. This was our very last book remaining in DocBook XML, so the docs toolchain will be removing DocBook XML support. See spec https://review.openstack.org/311698 for details. Another migration note is that the API reference content is moving from api-site to project specific repositories and api-site is now frozen. For more detail, see Anne's email: http://lists.openstack.org/pipermail/openstack-docs/2016-May/008536.html == Mitaka wrapup == We performed a Mitaka retrospective at Summit, notes are here: https://etherpad.openstack.org/p/austin-docs-mitakaretro In particular, I'd like to call out our hard working tools team Andreas and Christian, all our Speciality Team leads, and the Mitaka release managers Brian and Olga. Well done on a very successful release, everyone :) Total bugs closed: 645 == Site Stats == Thanks to the lovely people at Foundation (thanks Allison!) I now have access to more stats than I could possibly guess what to do with, and I'm hoping to be able to share some of these with you through the newsletter. If there's something in particular you would like to see, then please let me know and I'll endeavour to record it here! So far I can tell you that docs.openstack.org had 1.63M unique pageviews in April, down slightly from 1.72M in March, and the average session duration is just over six minutes, looking at just under 4 pages per session. == Doc team meeting == Next meetings: We'll be restarting the meeting series next week. Next meetings: US: Wednesday 11 April, 19:00 UTC APAC: Wednesday 18 April, 00:30 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#6_May_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Newton Design Summit summary
by Kato, Tomoyuki 05 May '16

05 May '16

Hi everyone, Here is Newton Design Summit I18n sessions summary. I18n Design Summit ------------------ * Thursday 2016-04-28 13:30 - 15:00 I18n workshop: translation processes and tools https://etherpad.openstack.org/p/austin-i18n-workshop * Friday 2016-04-29 9:00 -12:30 I18n Contributors meetup https://etherpad.openstack.org/p/austin-i18n-meetup Summary ------- * Newton cycle translation priority - Dashboard and plug-ins: require ALL with appropriate priority [TBD] - Documentation: install-guide, user-guide, api-quick-start - Glossary (not yet implemented) * I18n Guide revision - String freeze policy - How to translate release notes - How to archiving ATC, coordinators and core reviewers * Release notes translation - At now, we have translation resources at Zanata, which is named "releasenotes" at each project - Discussion with Doug Hellman, Release Management team PTL - publish to http://docs.openstack.org/<lang>/releasenotes/<project>/ - create each language index page, manually or automatically - each release note page doesn't contain language selector * Translation check site - patch review is under going. need review * Zanata upgrade - we need more time because it does not work fine * Automatic generation of ATC list - First, need to upgrade Zanata to version 3.9 or later * Glossary management - First, need to upgrade Zanata to version 3.9 or later - Need to decide management process, file formats, and so on * Improve Stackalytics - Add "translation review" count as new metrics - Update the stats daily, not weekly, as others * Docs translation publication - Simplify the maintainance process of traslated docs publication - Need to work with docs and infra team * Bug management - Email bug report to i18n ML when it is submitted * Transifex closure [Done] For more information, please see the Etherpad pages. -- KATO Tomoyuki

3 3

[i18n] Meeting reminder
by Kato, Tomoyuki 05 May '16

05 May '16

Hi team, This is a meeting reminder. I think it will be a short meeting, mainly for summit non-attendency. Kato

1 0

Create new language team called "Hinglish"
by Nitin Madhok 04 May '16

04 May '16

Hello, I’m Nitin Madhok working for Clemson University and currently contributing to various open source projects. I’m multi lingual and can read/write/speak the following languages: English(US) English(UK) French Hindi Hinglish Punjabi I want to create a language team called “Hinglish” (https://en.wikipedia.org/wiki/Hinglish <https://en.wikipedia.org/wiki/Hinglish>). My ID on Zanata is nmadhok -- Thanks, Nitin Madhok Clemson University

3 3

Fw: [OpenStack-docs] Freezing operations-guide repository
by KATO Tomoyuki 02 May '16

02 May '16

Hi team, Docs team decided to move operations guide into openstack-manuals repo. Also, XML DocBook is freezed, so we should not translate it. i.e. operations-guide/openstack-ops at Zanata. Stay tuned, the newer operations guide in RST format will appear at openstack-manuals project at Zanata, which will occur soon. KATO Tomoyuki ----------------------- Original Message ----------------------- Since we have now imported the RST ops-guide in openstack-manuals, let's freeze the operations-guide repository. We do not need to make any further edits there, any further updates should be done to the RST guide. I'm working on retiring the repository following the process documented at http://docs.openstack.org/infra/manual/drivers.html#retiring-a-project . Once this is done, the repository will be completely read-only. For that, I will propose a few final cleanup changes. So, let's do now: * Freeze repo - no more approvals for it (besides retiring). * Retire repository 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 _______________________________________________ OpenStack-docs mailing list OpenStack-docs(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

1 0

FW: [Bug 1573514] [NEW] Typos in Italian Mitaka translation
by Kato, Tomoyuki 22 Apr '16

22 Apr '16

Hi Italian team, KATO Tomoyuki > -----Original Message----- > Title: > Typos in Italian Mitaka translation > > Status in openstack i18n: > New > > Bug description: > Zanata proposed another update for mitaka neutron Italian translation: > https://review.openstack.org/#/c/309280/ > > There are several concerns I have here. > > First, it seems that the change has some typos (e.g. using a ¥ character while the language does not use it at all). > Second, the change removes authorship for multiple contributors. I suspect it's not expected.

2 1

Re: [OpenStack-I18n] IRC meeting this week
by Kato, Tomoyuki 21 Apr '16

21 Apr '16

> Thank you, Kato-san. > I'm not able to attend the meeting this time because of a conflict. > I have added some topics to austin-i18n-workshop. quick short response. > In total we have 2 i18n related sessions, 40-minute austin-i18n-workshop 90-minutes, isn't it? https://www.openstack.org/summit/austin-2016/summit-schedule/events/7707 Kato > and a half day austin-i18n-meetup. > I see there are a long list of topics in austin-i18n-workshop. > I suggest we move some topics to austin-i18n-meetup in order to have > thorough discussions for every topic. > Maybe we move glossary and bug management discussions to > austin-i18n-meetup. > And in austin-i18n-workshop, we focus on Zanata, translation check website > and stackalytics. > > Best regards > Ying Chun Guo (Daisy) > > > "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> wrote on 04/19/2016 > 11:12:05 AM: > > > From: "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> > > To: "'openstack-i18n(a)lists.openstack.org'" <openstack- > > i18n(a)lists.openstack.org> > > Date: 04/19/2016 11:14 AM > > Subject: [OpenStack-I18n] IRC meeting this week > > > > Hi team > > > > We will have IRC meeting at UTC 13:00 UTC Thursday in > #openstack-meeting. > > > > The agenda is > > > > * Summit Planning > > - https://etherpad.openstack.org/p/austin-i18n-workshop > > - https://etherpad.openstack.org/p/austin-i18n-meetup > > > > If you have more topics, feel free to email. > > > > Regards, > > KATO Tomoyuki (katomo) > > > > _______________________________________________ > > OpenStack-I18n mailing list > > OpenStack-I18n(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > >

2 1

IRC meeting this week
by Kato, Tomoyuki 19 Apr '16

19 Apr '16

Hi team We will have IRC meeting at UTC 13:00 UTC Thursday in #openstack-meeting. The agenda is * Summit Planning - https://etherpad.openstack.org/p/austin-i18n-workshop - https://etherpad.openstack.org/p/austin-i18n-meetup If you have more topics, feel free to email. Regards, KATO Tomoyuki (katomo)

2 1

translation syncronization disabled due to broken Babel release
by Andreas Jaeger 17 Apr '16

17 Apr '16

A heads up and a request for advise: Babel 2.3.3 release broke extraction of log level messages from strings and extracted instead of e.g. "_LW" the default "_". So, the proposal job removed all content for that. Fortunately, Zanata will keep the strings, so once an upload with a fixed Babel happens, this should be fine again. See https://review.openstack.org/#/c/304985/ for one example - the error manifests with all pot files having exactly the same content. But I wanted to be safe and since babel 2.3.2 broke horizon and now 2.3.3 breaks python projects, I have - as teemporary measure - disabled translation sync completely to buy us time to evaluate what to do. There's a requirements change to update versions (blocking all broken babel releases): https://review.openstack.org/#/c/305000 Upstream bug report https://github.com/python-babel/babel/issues/388 And one way of working around it the bug is not using "python setup.py" but "pybabel" directly for python projects - like we do for django already. This needs testing and review - and some updates (see review comment): https://review.openstack.org/305043 We can also wait for Babel 2.3.4 release - and test first that it works as desired. Advise on which way to go forward as well as testing and review of 305043 are welcome! 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 3

技术因素 in OpenStack 架构设计指南 - 当前最新
by KATO Tomoyuki 16 Apr '16

16 Apr '16

Hi Chinese team, Please take a look at: https://bugs.launchpad.net/openstack-i18n/+bug/1571100 Kato

1 0

Renaming of resources
by Andreas Jaeger 13 Apr '16

13 Apr '16

I propose to change the setting of the locale source dir from "$module/locale" to "." for all projects to have this consistent. This will change the names of all resources since those are relative to the locale source dir. This will enable us to translate release notes using Zanata for the python projects. This is only relevant for python projects - not for documentation ones or for Django based projects since those already use "." as source directory. This implies a scripting change as well as a manual copying translation files around. I'm willing to do both later this week. My proposal would be to only do this for *master* but not for stable/mitaka, I don't want to risk anything on that branch. Everybody ok with this? Or has anybody concerns and suggestions? 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

4 6

Re: [OpenStack-I18n] Renaming of resources
by Andreas Jaeger 12 Apr '16

12 Apr '16

On 2016-04-12 12:03, Ying Chun Guo wrote: > Hi, Andreas > > Just release Horizon project have two pairs of resources with same name: > django and djangojs. And that will not change, they will stay the same. > Will they have both the same name and same location after changing ? Yes, as the new setup is exactly the setup that horizon has. > Is there a way to separate them from the web UI after changing? > See: > https://translate.openstack.org/iteration/view/horizon/master/documents I think that is clear, it gives name and path now, 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

Re: [OpenStack-I18n] Renaming of resources
by Andreas Jaeger 12 Apr '16

12 Apr '16

On 2016-04-12 11:08, Ying Chun Guo wrote: > Hi, Andreas > > Do you mean to move the *.pot files from "$module/locale" to the root > folder of module ( or the root folder of project ) ? Will you move > translation files in language folders ? Only the name in Zanata is changed, see "Translation script challenges" as well. The files will stay the same in the repositories. But the parameter we give zanata is different and thus the files in Zanata are renamed. > The purpose of this change is to support release notes translation, right > ? Yes. Also, it avoids problems like we had with keystone (see above referenced email for full details), Andreas > Best regards > Ying Chun Guo (Daisy) > > > Andreas Jaeger <aj(a)suse.com> wrote on 04/12/2016 02:56:34 PM: > >> From: Andreas Jaeger <aj(a)suse.com> >> To: "openstack-i18n(a)lists.openstack.org" > <openstack-i18n(a)lists.openstack.org> >> Date: 04/12/2016 02:58 PM >> Subject: [OpenStack-I18n] Renaming of resources >> >> I propose to change the setting of the locale source dir from >> "$module/locale" to "." for all projects to have this consistent. This >> will change the names of all resources since those are relative to the >> locale source dir. This will enable us to translate release notes using >> Zanata for the python projects. >> >> This is only relevant for python projects - not for documentation ones >> or for Django based projects since those already use "." as source >> directory. >> >> This implies a scripting change as well as a manual copying translation >> files around. I'm willing to do both later this week. >> >> My proposal would be to only do this for *master* but not for >> stable/mitaka, I don't want to risk anything on that branch. >> >> Everybody ok with this? Or has anybody concerns and suggestions? >> >> 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 >> >> >> _______________________________________________ >> OpenStack-I18n mailing list >> OpenStack-I18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > -- 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

Translation script challenges
by Andreas Jaeger 12 Apr '16

12 Apr '16

I think this is mainly of interest to KATO-san, Akihiro-san, Alex, and infra folks but wanted to send it here to have it recorded. This is about the scripting we use in project-config to push content to zanata. I just did two changes to fix problems I noticed with release notes translation and with python projects that use more than one module (keystone): https://review.openstack.org/303727 https://review.openstack.org/303722 But now I see have another problem: Since keystone went from one to two modules, the srcdir setting changed and thus it's not anymore keystone but keystone/locale/keystone as resource name. Compare: https://translate.openstack.org/iteration/view/keystone/master/documents https://translate.openstack.org/iteration/view/keystone/stable-mitaka/docum… The rename deleted the old content and created new files ;( We can fix this with downloading the translation of mitaka files and pushing them to master. But this will hit us every time a project moves from one to multiple modules. Now, checking releasenotes push for python projects: It still does not work due to the ../.. zanata-cli does not see files outside of the srcdir. For reference: We need to push nova/locale/nova.pot and releasenotes/locale/releasenotes.pot zanata.xml contains: <rules> <rule pattern="**/*.pot">{locale_with_underscore}/LC_MESSAGES/{filename}.po</rule> <rule pattern="../../releasenotes/source/locale/releasenotes.pot">../../releasenotes/source/locale/{locale_with_underscore}/LC_MESSAGES/releasenotes.po</rule> </rules> So, I'm proposing to set sourcedir and transdir *everywhere* to "." instead of "$module/locale" - like done for multiple modules: <rules> <rule pattern="**/*.pot">{path}/{locale_with_underscore}/LC_MESSAGES/{filename}.po</rule> <rule pattern="releasenotes/source/locale/releasenotes.pot">releasenotes/source/locale/{locale_with_underscore}/LC_MESSAGES/releasenotes.po</rule> </rules> Does anybody have a better idea on how to fix these two problems? Or a better way to write the rules above for this? Alex, is there a way to not lose the content when this change is done since it will rename the translation files? Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 5

RFC: Zanata enhancement
by Kato, Tomoyuki 12 Apr '16

12 Apr '16

Hi team, I'd like to collect Zanata enhancement requests. I believe Zanata enhancement improve your work effciency, as translator, coordinator, or infra engineer... Please feel free to write your requests. https://etherpad.openstack.org/p/I18n-Zanata-enhancement I have a chance to talk with Alex, Zanata dev team, at Austin Summit. Unfortunately, we don't have enough official session slot, but we will talk at somewhere. Also, everyone is welcome to join us. Exact date and location are to be determined. I'll email details around summit. Thanks, KATO Tomoyuki

1 0

Approval
by Remo Mattei 12 Apr '16

12 Apr '16

hello all, what is the process to approve a new translation? Thanks

2 1

today's horizon import puzzles me...
by Andreas Jaeger 11 Apr '16

11 Apr '16

Could somebody closely review today's horizon translation import, please? I'm surprised by the deletions but couldn't find an error with them either: https://review.openstack.org/#/c/303807/ Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 4

Fw: [openstack-announce] OpenStack Mitaka is officially released!
by KATO Tomoyuki 10 Apr '16

10 Apr '16

Hi team, OpenStack Mitaka was officially released. Congratulations! Also, it's time to take over the PTL role from Daisy to me. Again, I appreciate all your work, Daisy. Sincerely. KATO Tomoyuki ----------------------- Original Message ----------------------- Hello OpenStack community, I'm excited to announce the final releases for the components of OpenStack Mitaka, which conclude the 6-month Mitaka development cycle. You will find a complete list of all components, their latest versions, and links to individual project release notes documents listed on the new release site: http://releases.openstack.org/mitaka/ Congratulations to all of the teams who have contributed to this release! I also want to extend a big thank you to AJAeger and jhesketh for their help with build issues today, and to ttx and dims for their help with release work all this cycle and especially over the last couple of weeks. Thank you! Our next production cycle, Newton, has already started. We will meet in Austin April 25-29 at the Newton Design Summit to plan the work for the upcoming cycle. I hope to see you there! Doug

2 1

IRC meeting tomorrow
by Ying Chun Guo 07 Apr '16

07 Apr '16

Hi, team We will have IRC meeting tomorrow at UTC 0600 in #openstack-meeting. The agenda is - Summary of Mitaka translation - New translation priorities - Continued discussion about glossary management If you have more topics, feel free to add. Best regards Ying Chun Guo (Daisy)

3 2

Re: [OpenStack-I18n] Opening master again?
by Andreas Jaeger 04 Apr '16

04 Apr '16

Daisy, KATO, could either of you update the translate.openstack.org main page, please? The mitaka translation period is over according to it, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 1

Re: [OpenStack-I18n] Opening master again?
by Andreas Jaeger 04 Apr '16

04 Apr '16

On 2016-04-04 03:28, Ying Chun Guo wrote: > Agree to open master again. > We will keep both master and stable open for a period, till string freeze > of next release. OK, I'll open up master now and merge content to master as well, 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

Opening master again?
by Andreas Jaeger 04 Apr '16

04 Apr '16

The translations have merged for mitaka, latest import was on Wednesday (30th) and for some even on Thursday - so some extra days after official end of the 28th. The last RC has been cut for all projects. I've seen an impressive amount of changes coming in, thanks! Any new translations will go into the first stable release unless a project needs an extra RC and takes in translations as well. Last time we made at this time the master branch writeable again and merged the stable branch translations to master - and left the stable branches open for further submissions. So, time to do this again now? That means translations on both master and stable can happen going forward, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 2

stable/liberty version fo Zanata networking-guide
by Akihiro Motoki 03 Apr '16

03 Apr '16

Hi, networking-guide in openstack-manuals is now versioned. Can we have a stable-liberty version for networking-guide on Zanata? Akihiro

4 4

Austin Design Summit track layout
by Kato, Tomoyuki 02 Apr '16

02 Apr '16

Hi team, Austin Design Summit track layout is announced. http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html I18n team has a contributor meetup at Friday. I'm looking forward to meet many people. Thank you to coodinate, Daisy. Thanks, KATO Tomoyuki

6 5

Strange projects on translate.openstack.org
by Andreas Jaeger 01 Apr '16

01 Apr '16

Hi, does anybody know what these are? https://translate.openstack.org/project/view/swift-italian/ https://translate.openstack.org/project/view/tempest https://translate.openstack.org/project/view/test-json-md IMHO we should not add new projects that are manually translated - instead let's integrate them in the usual toolchain. Also, why do these have some projects separate maintainers? We don't need them IMHO at all. I propose to delete them. Going forward, I suggest that any new projects outside of the usual process get discussed on the openstack-i18n mailing list, so that we know what's going on. Can we also document the reason for them somewhere? 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

5 6

What's Up, Doc? Mitaka Release Edition
by Lana Brindley 01 Apr '16

01 Apr '16

Hi everyone, While it was very tempting to write something something shocking here for April Fools', I thought everyone might have already had their heart rate raised enough by the fact that Mitaka is only five days away! This will be my final docs newsletter before the release, and the docs are in great shape ready to go out. I would like to sincerely thank Andreas and our release managers Brian and Olga, not only for the hard work they've done so far, but also for holding down the fort over the next few days while I'm out of contact. Please remember to contact them directly if you have any last minute documentation fires that need putting out. I'd also like to mention the hard work that the Installation Guide testers have been putting in over the past couple of weeks. The testing matrix is looking very green (https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting) and I'm confident that we'll get the Mitaka guide out fully tested and on schedule. Don't forget you can check release progress on the etherpad here: https://etherpad.openstack.org/p/MitakaRelease == Progress towards Mitaka == 5 days to go! 558 bugs closed so far for this release. Docs Testing * https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting * Only a few items left to check off, at this stage we're good to publish the Ubuntu, RDO, and Suse guides on release day. Release Tasks: * Release planning occurs in our etherpad here: https://etherpad.openstack.org/p/MitakaRelease * All tasks that should be completed at this stage are done, and we're on track to start the release process in the 24-48 hours before the release drops. * Release notes for the docs project are in a "reno-style" directory in the openstack-manuals repo. This directory is not being managed by Reno, however, so please propose patches to it directly. == The Road to Austin == * First of all, thanks for the amazing feedback on what docs sessions you would like to see at the Austin Design Summit! We have filled our entire allocation (and then some), and the schedule so far is here: https://etherpad.openstack.org/p/Newton-DocsSessions * There's been a really robust and exciting conversation about the Install Guide on the dev list over the past week or so, which I have been following closely. If you're interested in overhauling our Install Guide (and it certainly seems like a lot of people are!), then please make sure you add our Install Guide Design Summit session to your agenda. It is on Wednesday at 11:50, so placed so that it can run over into lunchtime if required. * A note for those who noticed the Ops guide omission: this should take place in the Ops track, and I'll let you know when that session will be. == Doc team meeting == Next meetings: The US meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-03-30 Next meetings: APAC: No APAC meeting this week US: Wednesday 13 April, 19:00 UTC (This is after the Mitaka release) Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#1_April_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Starting translations for libraries (like djnago-openstack-auth) earlier in Newton?
by Akihiro Motoki 31 Mar '16

31 Mar '16

During the Mitaka RC phase, I released django-openstack-auth only for translation. At that time, I was asked from Doug Hellmann, the release manamgement PTL, whether the i18n team can start translations for libraries earlier, i.e., sooner before the freeze date of libraries. [1] Can we do this in Newton or later? If we accept this, please keep it in mind when planning translation schedule and make sure to announce it to the team. I am just sharing information and won't lead this discussion. I have been coordinating this kind of things for long and now am tired to do it. I hope someone else takes the role. Background: django-openstack-auth is a library used by horizon. In the OpenStack release process, all libraries are frozen when the milestone-3 is cut. [1] http://lists.openstack.org/pipermail/openstack-dev/2016-March/090112.html

2 1

Re: [OpenStack-I18n] Criteria of Horizon language list forMitakarelease
by Kato, Tomoyuki 30 Mar '16

30 Mar '16

> As of now, 15 languages satisfy the criteria. > https://translate.openstack.org/version-group/view/mitaka-translation/ > projects/horizon/stable-mitaka > and > http://git.openstack.org/cgit/openstack/horizon/tree/openstack_dashboa > rd/settings.py?h=stable/mitaka#n198 > match, > so there is no need to update. Thanks, Akihiro. And, congrats, 15 languages coordinators! Mitaka is really coming soon. KATO Tomoyuki > This is the final check from my side. > If your language satisfies this criteria after this mail, feel free to > propose a patch to update the language list in Horizon by yourself. > > I believe various projects will release RC including translations this week. > > Akihiro

1 0

Re: [Openstack-i18n] Criteria of Horizon language list forMitakarelease
by Akihiro Motoki 30 Mar '16

30 Mar '16

Hi Doug and all, I needed to spend some time to look for the history. Roughly speaking our history can be broken donw into three categories: [1] Liberty Horizon [2] documentation translation from 2014. [3] up to Kilo Horizon I think following the history clarified what happened. --- [1] Liberty Horizon In Liberty, we migrated the translation platform to Zanata and all imports were done by Jenkins jobs (thanks to Andreas). [2] documentation translation from 2014 In parallel, there was the ongoing efforts to automate documentation translations. The thread is [2] and we discussed the threshold for translation addition (75%) and removal (60%). It is documented very well at https://wiki.openstack.org/wiki/Translations/Infrastructure. [3] up to Kilo Horizon The following are my translation import patch for Horizon up to Kilo: * KIlo : https://github.com/openstack/horizon/commit/56d5683c8c49558ae22200bc01ec87e… (The commit message was wrong not Juno but Kilo :p) * Juno : https://github.com/openstack/horizon/commit/9b0ba951c07af13aa4c386b19876474… * Icehouse : https://github.com/openstack/horizon/commit/a9cf547d20065b2bd49e101364b46cf… * Havana : https://github.com/openstack/horizon/commit/4910222356fbd2aeb0dab1b3cebe003… All of these commit messages said "Import ~100% completed translaitons". It seems we used almost all are translated. I could not find the meeting log where we discussed this criteria first for Havana or Icehouse. According to [1] it seems we had the criteria of 95% for Juno. --- commit 56d5683c8c49558ae22200bc01ec87ea83144003 Author: Akihiro Motoki <motoki(a)da.jp.nec.com> Date: Thu Apr 23 06:58:49 2015 +0900 Import translations from Transifex for Juno * Import ~100% completed translations (translations available for 12 languages) * Delete incomplete languages * Update language list in openstack_dashboard settings.py --- That's all what I succeeded to gather. Akihiro [1] http://lists.openstack.org/pipermail/openstack-i18n/2014-October/000806.html [2] http://lists.openstack.org/pipermail/openstack-i18n/2014-October/thread.htm… 2016-03-22 22:32 GMT+09:00 Douglas Fish <drfish(a)us.ibm.com>: > Akihiro, > > I've been trying to find where we documented the 90% cutoff used by Horizon > in past releases. I can't find it (and I'm afraid I'm the one who documented > it). Were you able to find that reference? > > I think it's reasonable to manage the Horizon language list to match the > same set of languages for which we have PO files included in the project. > The 66% cutoff would apply in both cases then. It should be easy for a > consumer or distro to provide a shorter list than what we've defaulted by > changing the value of the LANGUAGES setting in local_settings.py or a > local_settings.d file. > > Doug Fish > > > > "Ying Chun Guo" <guoyingc(a)cn.ibm.com> wrote on 03/22/2016 05:56:45 AM: > >> From: "Ying Chun Guo" <guoyingc(a)cn.ibm.com> >> To: Akihiro Motoki <amotoki(a)gmail.com> >> Cc: "openstack-i18n(a)lists.openstack.org" >> <openstack-i18n(a)lists.openstack.org> >> Date: 03/22/2016 05:59 AM >> Subject: Re: [Openstack-i18n] Criteria of Horizon language list for >> Mitakarelease >> >> Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/22/2016 06:43:33 PM: >> >> > From: Akihiro Motoki <amotoki(a)gmail.com> >> > To: Ying Chun Guo/China/IBM@IBMCN >> > Cc: "openstack-i18n(a)lists.openstack.org" >> <openstack-i18n(a)lists.openstack.org> >> > Date: 03/22/2016 06:45 PM >> > Subject: Re: [Openstack-i18n] Criteria of Horizon language list for > >> > Mitakarelease >> > >> > 2016-03-22 18:00 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/22/2016 02:27:21 AM: >> > > >> > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> > >> To: "openstack-i18n(a)lists.openstack.org" >> > > <Openstack-i18n(a)lists.openstack.org> >> > >> Date: 03/22/2016 02:29 AM >> > >> Subject: [Openstack-i18n] Criteria of Horizon language list for >> Mitaka >> > > release >> > >> >> > >> Hi i18n team, >> > >> >> > >> As Horizon liaison, I would like to ask you all about the criteria of >> > >> Horizon language list for Mitaka release. >> > >> >> > >> The same topic was discussed several releases ago and the consensus >> at >> > >> that time were: >> > >> * remove all translations with less than 90% progress >> > >> * update the language list accordingly. >> > >> >> > >> Translations were imported manually at that time and the situation >> may >> > >> be changed now. >> > >> I don't have an opinion and will just follow the i18n project >> decision. >> > >> If no response or well-defined criteria, I will just keep the current >> > >> language list [1]. >> > > >> > > Thank you for taking care of that, Akihiro. >> > > I don't see any requests to change the language list. >> > > >> > >> >> > >> The following is just information: >> > >> We have four PO files (django/djangojs for horizon and >> > > openstack_dashboard). >> > >> The current translation import policy for each PO file is >> documentedhere >> > > [2]. >> > >> Each PO file is imported once the translation percentage becomes over >> > > 75% >> > >> and it will be removed when the translation percentage becomes less >> than >> > > 20%. >> > >> What is our criteria? >> > > >> > > My opinion is to follow the previous guidelines. >> > >> > Do you mean we should remove <90% translations and update the lang >> > list accordingly? >> > >> > I made a quick survey. The result is not so happy, but I will just >> > follow the team decision. >> > >> > We have four PO files per language for horizon. >> > My understanding is 90% means 90% translations for all these PO files. >> > Unfortunately, as of today, only four languages satisfy this criteria >> > (90%): de, fr, ja, ko >> > If we change the criteria to 66%, we will have three more languages: >> > pt-br, ru, zh-cn. >> > >> > It is too sad statistics. openstack_dashboard/djangojs is the >> > bottleneck of the progress. >> > >> > On the other hand, the current language list contains 15 translated >> languages: >> > cs, de, en-gb, en-au, es, fr, it, ja, ko, pl, pt-br, ru, tr, zh-cn, >> zh-tw. >> > >> >> No, I didn't mean to remove <90% translations. >> Did we do that before ? >> I thought the criteria was 66%. >> >> I just realized the difference situation we met in this release. >> We have included plugin projects. >> Before mitaka, we only focus on Horizon translation. >> If we only take a look at the completion rate of Horizon[1], I think most >> active translation team have achieved >66%. So it means, we don't need to >> remove any languages from the list. >> If we consider the overall completion rate of plugin projects together >> with Horizon projects, some languages are less than 66%. >> My suggestion is to only consider the progress of Horizon project. >> 90% is too strict, I think. 66% is better. >> >> > Akihiro >> > >> > > >> > > >> > >> >> > >> In future releases, I think we should automate this as a part of >> > >> translation import jobs. >> > >> I will reduce the work of horizon liaison. >> > >> >> > > >> > > I agree. >> > > >> > > >> > >> Akihiro >> > >> >> > >> [1] https://github.com/openstack/horizon/blob/master/ >> > >> openstack_dashboard/settings.py#L198-L215 >> > >> [2] https://wiki.openstack.org/wiki/Translations/ >> > >> Infrastructure#Translation_percentage_changes >> > >> >> > >> _______________________________________________ >> > >> Openstack-i18n mailing list >> > >> Openstack-i18n(a)lists.openstack.org >> > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > >> >> > > >> > > >> > >> >> >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >

4 5

unable to login to Zanata
by Nikita Burtsev 29 Mar '16

29 Mar '16

Hello, When I try to login to production Zanata I get forwarded to openstackID first then to Zanata profile creation page. This page tells me that my username/email are already in use. I've never used production Zanata before but I did use 'dev' version. I guess my profile was migrated from dev but never associated with openstackID (or something like that) Could someone help me out with this please? Thank you. -- BR Nikita

7 15

Setting up stable-mitaka in Zanata
by Andreas Jaeger 26 Mar '16

26 Mar '16

Team, the release manager have setup stable/mitaka for these projects: https://review.openstack.org/#/q/topic:create-mitaka We should create stable-mitaka again in zanata and freeze master. Daisy, will you do this? I'm taking care of the infra side now, change is https://translate.openstack.org/ Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 4

designate-dashboard missing template strings
by Akihiro Motoki 24 Mar '16

24 Mar '16

Hi, Strings in templates of designate-dashboard are not extracted now. https://bugs.launchpad.net/designate/+bug/1561203 and I proposed a fix at https://review.openstack.org/#/c/296807/ Questions for the team is whether we should have this in mitaka? We are in the hard string freeze after RC1 phase. This change violates the string freeze. However this change only add new strings and allows translators to translate strings which cannot be translated now. This add 18 fuzzy translations, 8 untranslated messages. I think it is acceptable from i18n view. Thought? Akihiro

2 1

Do you need a temporary translation check site?
by Akihiro Motoki 24 Mar '16

24 Mar '16

Unfortunately the official translation check site is not announced yet. If you need an alternative one, try the following. Horizon is now available at http://157.7.133.23:13580/dashboard The default users are: admin and demo The password: UW3D9n6TqdGn Note that it is temporary and I am using this site for development and testing. The enabled panel may sometimes be changed. Do not ask me :)

2 2

[release][horizon][i18n] can we release django-openstack-auth of stable/mitaka for translations
by Akihiro Motoki 24 Mar '16

24 Mar '16

Hi release management team, Can we have a new release of django-openstack-auth from stable/mitaka branch for translations? What is happening? django-openstack-auth is a library project consumed by Horizon. The (soft) string freeze happens when the milestone-3 is cut. The milestone-3 is also the dependency freeze. This is a dilemma between dependency freeze and translation start, and there is no chance to import translations of django-openstack-auth for Mitaka. There are several updates of translations after 2.2.0 (mitaka) release [1]. As the i18n team, we would like to have a released version of django-openstack-auth with up-to-date translations. Which version? The current version of django-openstack-auth for Mitaka is 2.2.0. What version number is recommended, 2.2.1 or 2.3.0? When? Hopefully a new version is released soon around Mitaka is shipped. The current translation deadline is set to Mar 28 (the beginning of the release week). In my understanding we avoid releasing a new version of library before the Mitaka release. Distributors can choose which version is included in their distribution. Any suggestions would be appreciated. Thanks, Akihiro [1] https://review.openstack.org/#/q/topic:zanata/translations+project:openstac…

2 2

Re: [Openstack-i18n] Zanata Group for Mitaka dashboard translations
by Akihiro Motoki 23 Mar '16

23 Mar '16

Thanks Daisy! I am using this to check the progress of translations per language. The link like https://translate.openstack.org/version-group/view/mitaka-translation/langu… helps me. Akihiro 2016-03-18 16:04 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > It has been corrected, Akihiro. > Thank you for pointing out. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/18/2016 02:44:39 PM: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: "openstack-i18n(a)lists.openstack.org" > <Openstack-i18n(a)lists.openstack.org> >> Date: 03/18/2016 02:47 PM >> Subject: [Openstack-i18n] Zanata Group for Mitaka dashboard translations >> >> Hi Zanata admin, >> >> I noticed Zanata group "Mitaka dashboard translations" has strange > entries. >> > https://translate.openstack.org/version-group/view/mitaka-translation/proje… > >> >> - two versions for django_openstack_auth : master and stable-mitaka >> - read-only version for horizon : master-old-keepforstatistics >> >> Could you correct these versions to the appropriate ones? >> >> Thanks, >> Akihiro >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > >

2 3

Re: [Openstack-i18n] Criteria of Horizon language list for Mitakarelease
by Akihiro Motoki 22 Mar '16

22 Mar '16

2016-03-22 19:56 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/22/2016 06:43:33 PM: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: Ying Chun Guo/China/IBM@IBMCN >> Cc: "openstack-i18n(a)lists.openstack.org" > <openstack-i18n(a)lists.openstack.org> >> Date: 03/22/2016 06:45 PM >> Subject: Re: [Openstack-i18n] Criteria of Horizon language list for >> Mitakarelease >> >> 2016-03-22 18:00 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/22/2016 02:27:21 AM: >> > >> >> From: Akihiro Motoki <amotoki(a)gmail.com> >> >> To: "openstack-i18n(a)lists.openstack.org" >> > <Openstack-i18n(a)lists.openstack.org> >> >> Date: 03/22/2016 02:29 AM >> >> Subject: [Openstack-i18n] Criteria of Horizon language list for > Mitaka >> > release >> >> >> >> Hi i18n team, >> >> >> >> As Horizon liaison, I would like to ask you all about the criteria of >> >> Horizon language list for Mitaka release. >> >> >> >> The same topic was discussed several releases ago and the consensus > at >> >> that time were: >> >> * remove all translations with less than 90% progress >> >> * update the language list accordingly. >> >> >> >> Translations were imported manually at that time and the situation > may >> >> be changed now. >> >> I don't have an opinion and will just follow the i18n project > decision. >> >> If no response or well-defined criteria, I will just keep the current >> >> language list [1]. >> > >> > Thank you for taking care of that, Akihiro. >> > I don't see any requests to change the language list. >> > >> >> >> >> The following is just information: >> >> We have four PO files (django/djangojs for horizon and >> > openstack_dashboard). >> >> The current translation import policy for each PO file is > documentedhere >> > [2]. >> >> Each PO file is imported once the translation percentage becomes over >> > 75% >> >> and it will be removed when the translation percentage becomes less > than >> > 20%. >> >> What is our criteria? >> > >> > My opinion is to follow the previous guidelines. >> >> Do you mean we should remove <90% translations and update the lang >> list accordingly? >> >> I made a quick survey. The result is not so happy, but I will just >> follow the team decision. >> >> We have four PO files per language for horizon. >> My understanding is 90% means 90% translations for all these PO files. >> Unfortunately, as of today, only four languages satisfy this criteria >> (90%): de, fr, ja, ko >> If we change the criteria to 66%, we will have three more languages: >> pt-br, ru, zh-cn. >> >> It is too sad statistics. openstack_dashboard/djangojs is the >> bottleneck of the progress. >> >> On the other hand, the current language list contains 15 translated > languages: >> cs, de, en-gb, en-au, es, fr, it, ja, ko, pl, pt-br, ru, tr, zh-cn, > zh-tw. >> > > No, I didn't mean to remove <90% translations. > Did we do that before ? I re-read the old logs. My memory is not correct. We first import ~100% translated languages, and then relaxed the criteria to 90~95%. It seems I thought this is the criteria. After that, we discussed and agreed the criteria of >75% for addition and <66% for deleteion for each PO file. That's the history. > I thought the criteria was 66%. I got it. I just quoted the i18n team consensus several release ago and I didn't thought it has been updated as wrote above. Thanks. > I just realized the difference situation we met in this release. > We have included plugin projects. > Before mitaka, we only focus on Horizon translation. > If we only take a look at the completion rate of Horizon[1], I think most > active translation team have achieved >66%. So it means, we don't need to > remove any languages from the list. > If we consider the overall completion rate of plugin projects together > with Horizon projects, some languages are less than 66%. > My suggestion is to only consider the progress of Horizon project. > 90% is too strict, I think. 66% is better. Totally agree. I just would like to clarify the criteria. Is it okay that I just update the language list with >66% progress? Everyone can see the progress at https://translate.openstack.org/iteration/view/horizon/stable-mitaka/langua… I will decide the progress based on this. Thanks, Akihiro > >> Akihiro >> >> > >> > >> >> >> >> In future releases, I think we should automate this as a part of >> >> translation import jobs. >> >> I will reduce the work of horizon liaison. >> >> >> > >> > I agree. >> > >> > >> >> Akihiro >> >> >> >> [1] https://github.com/openstack/horizon/blob/master/ >> >> openstack_dashboard/settings.py#L198-L215 >> >> [2] https://wiki.openstack.org/wiki/Translations/ >> >> Infrastructure#Translation_percentage_changes >> >> >> >> _______________________________________________ >> >> Openstack-i18n mailing list >> >> Openstack-i18n(a)lists.openstack.org >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >> >> > >> > >> > >

3 2

Re: [Openstack-i18n] Setting up stable-mitaka in Zanata
by Andreas Jaeger 22 Mar '16

22 Mar '16

On 2016-03-22 11:39, Ying Chun Guo wrote: > Hi, Andreas > > Can you kindly add job to support stable-mitaka for project > designate-dashboard ? We just found we missed it in the Mitaka translation > plan. Luckily, it has only a small po file with 68 words. We still have > time to add it back to the translation plan. Sorry for the trouble. Please > help. I'll setup the jobs. Do you add it to zanata? Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 2

Re: [Openstack-i18n] Criteria of Horizon language list for Mitakarelease
by Akihiro Motoki 22 Mar '16

22 Mar '16

2016-03-22 18:00 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/22/2016 02:27:21 AM: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: "openstack-i18n(a)lists.openstack.org" > <Openstack-i18n(a)lists.openstack.org> >> Date: 03/22/2016 02:29 AM >> Subject: [Openstack-i18n] Criteria of Horizon language list for Mitaka > release >> >> Hi i18n team, >> >> As Horizon liaison, I would like to ask you all about the criteria of >> Horizon language list for Mitaka release. >> >> The same topic was discussed several releases ago and the consensus at >> that time were: >> * remove all translations with less than 90% progress >> * update the language list accordingly. >> >> Translations were imported manually at that time and the situation may >> be changed now. >> I don't have an opinion and will just follow the i18n project decision. >> If no response or well-defined criteria, I will just keep the current >> language list [1]. > > Thank you for taking care of that, Akihiro. > I don't see any requests to change the language list. > >> >> The following is just information: >> We have four PO files (django/djangojs for horizon and > openstack_dashboard). >> The current translation import policy for each PO file is documentedhere > [2]. >> Each PO file is imported once the translation percentage becomes over > 75% >> and it will be removed when the translation percentage becomes less than > 20%. >> What is our criteria? > > My opinion is to follow the previous guidelines. Do you mean we should remove <90% translations and update the lang list accordingly? I made a quick survey. The result is not so happy, but I will just follow the team decision. We have four PO files per language for horizon. My understanding is 90% means 90% translations for all these PO files. Unfortunately, as of today, only four languages satisfy this criteria (90%): de, fr, ja, ko If we change the criteria to 66%, we will have three more languages: pt-br, ru, zh-cn. It is too sad statistics. openstack_dashboard/djangojs is the bottleneck of the progress. On the other hand, the current language list contains 15 translated languages: cs, de, en-gb, en-au, es, fr, it, ja, ko, pl, pt-br, ru, tr, zh-cn, zh-tw. Akihiro > > >> >> In future releases, I think we should automate this as a part of >> translation import jobs. >> I will reduce the work of horizon liaison. >> > > I agree. > > >> Akihiro >> >> [1] https://github.com/openstack/horizon/blob/master/ >> openstack_dashboard/settings.py#L198-L215 >> [2] https://wiki.openstack.org/wiki/Translations/ >> Infrastructure#Translation_percentage_changes >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > >

5 4

Re: [Openstack-i18n] why is designate-dashboard excluded from the prioritized translation list?
by Akihiro Motoki 22 Mar '16

22 Mar '16

Thanks for your quick support! 2016-03-22 19:36 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Thank you, Kato. > stable-mitaka for designate-dashboard is created. The translation plan in > the front page is updated. Dashboard group is updated too. > > Best regards > Ying Chun Guo (Daisy) > > > "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> wrote on 03/22/2016 > 06:23:52 PM: > >> From: "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> >> To: Ying Chun Guo/China/IBM@IBMCN, Akihiro Motoki <amotoki(a)gmail.com> >> Cc: "openstack-i18n(a)lists.openstack.org" > <Openstack-i18n(a)lists.openstack.org> >> Date: 03/22/2016 06:25 PM >> Subject: RE: [Openstack-i18n] why is designate-dashboard excluded >> from the prioritized translation list? >> >> > hmm. >> > I don't know neither. >> > Maybe nobody proposed to add designate-dashboard in I18n mailing list. >> > And I don't think I see its liaison when I proposed plugin projects in > Feb >> > 29. >> > For whatever reasons, the reality is that we missed it in the plan. >> > >> > There are two possible solutions. >> > #1 we add it back to the plan. It has only 1 file with 68 words, > really a >> > very small workload. >> >> my +1 for #1 >> >> KATO Tomoyuki >> >> > #2 we told designate team that we missed it and we will include it in > next >> > release. >> > >> > I prefer the first one. >> > If you agree, I can make stable-mitaka version and we can ask Andreas > to >> > add the corresponding job. >> > >> > Best regards >> > Ying Chun Guo (Daisy) >> > >> > >> > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/22/2016 02:59:53 AM: >> > >> > > From: Akihiro Motoki <amotoki(a)gmail.com> >> > > To: "openstack-i18n(a)lists.openstack.org" >> > <Openstack-i18n(a)lists.openstack.org> >> > > Date: 03/22/2016 03:02 AM >> > > Subject: [Openstack-i18n] why is designate-dashboard excluded from >> > > the prioritized translation list? >> > > >> > > Does anyone describe why designate-dashboard is not listed in the >> > > prioritized list? >> > > I see designate has assigned a cross project liaison for i18n at > least >> > Mar 4 >> > > (according to the wiki history) and the project seem to be taking > care >> > > of translations well. >> > > >> > > I have no answer for >> > > >> > > http://lists.openstack.org/pipermail/openstack-dev/2016-March/090022.html >> > > ? >> > > Can we describe a reasonable reason for them? >> > > Daisy, could you follow up the mailing thread? >> > > >> > > stable-mitaka is not setup for designate-dashboard. >> > > As far as I know, they have setup translation support in the early >> > stage. >> > > >> > > If I remember correctly, we include murano-dashboard and magnum-ui >> > > because they responded in the -dev list. I am not sure we checked > the >> > > wiki at that time, >> > > and the nomination period is enough. >> > > >> > > Akihiro >> > > >> > > _______________________________________________ >> > > Openstack-i18n mailing list >> > > Openstack-i18n(a)lists.openstack.org >> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > > >> > >> > >> > >> > _______________________________________________ >> > Openstack-i18n mailing list >> > Openstack-i18n(a)lists.openstack.org >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > >

1 0

Re: [Openstack-i18n] Setting up stable-mitaka in Zanata
by Andreas Jaeger 22 Mar '16

22 Mar '16

I just added trove-dashboard for mitaka, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 5

why is designate-dashboard excluded from the prioritized translation list?
by Akihiro Motoki 22 Mar '16

22 Mar '16

Does anyone describe why designate-dashboard is not listed in the prioritized list? I see designate has assigned a cross project liaison for i18n at least Mar 4 (according to the wiki history) and the project seem to be taking care of translations well. I have no answer for http://lists.openstack.org/pipermail/openstack-dev/2016-March/090022.html ? Can we describe a reasonable reason for them? Daisy, could you follow up the mailing thread? stable-mitaka is not setup for designate-dashboard. As far as I know, they have setup translation support in the early stage. If I remember correctly, we include murano-dashboard and magnum-ui because they responded in the -dev list. I am not sure we checked the wiki at that time, and the nomination period is enough. Akihiro

3 3

Re: [Openstack-i18n] why is designate-dashboard excluded from the prioritized translation list?
by Akihiro Motoki 22 Mar '16

22 Mar '16

Hi Daisy, Thanks for your reply to my rude mail forwarding _o_ > #1 we add it back to the plan. It has only 1 file with 68 words, really a > very small workload. My vote is #1. The following is just to record my memory. I think it was just a bad timing. We can improve the process in the future releases. * designate-dashboard is a candidate of the list, but we didn't see i18n liaison when the team meeting was held on Mar 3. This is the only reason. * In the mail to ask i18n liaison, we just asked to input his/her name to CPL wiki page if you are interested in i18n liaison, but we checked mail response only. * We decided the priority list just three days after the mail of i18n liaison request. Most teams are driven by weekly basis (IRC meeting or something), so three days is too short. Akihiro 2016-03-22 19:16 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > hmm. > I don't know neither. > Maybe nobody proposed to add designate-dashboard in I18n mailing list. > And I don't think I see its liaison when I proposed plugin projects in Feb > 29. > For whatever reasons, the reality is that we missed it in the plan. > > There are two possible solutions. > #1 we add it back to the plan. It has only 1 file with 68 words, really a > very small workload. > #2 we told designate team that we missed it and we will include it in next > release. > > I prefer the first one. > If you agree, I can make stable-mitaka version and we can ask Andreas to > add the corresponding job. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/22/2016 02:59:53 AM: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: "openstack-i18n(a)lists.openstack.org" > <Openstack-i18n(a)lists.openstack.org> >> Date: 03/22/2016 03:02 AM >> Subject: [Openstack-i18n] why is designate-dashboard excluded from >> the prioritized translation list? >> >> Does anyone describe why designate-dashboard is not listed in the >> prioritized list? >> I see designate has assigned a cross project liaison for i18n at least > Mar 4 >> (according to the wiki history) and the project seem to be taking care >> of translations well. >> >> I have no answer for >> > http://lists.openstack.org/pipermail/openstack-dev/2016-March/090022.html >> ? >> Can we describe a reasonable reason for them? >> Daisy, could you follow up the mailing thread? >> >> stable-mitaka is not setup for designate-dashboard. >> As far as I know, they have setup translation support in the early > stage. >> >> If I remember correctly, we include murano-dashboard and magnum-ui >> because they responded in the -dev list. I am not sure we checked the >> wiki at that time, >> and the nomination period is enough. >> >> Akihiro >> >> _______________________________________________ >> 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] Will translation cleanup happen for Mitaka?
by Akihiro Motoki 22 Mar '16

22 Mar '16

Hi Daisy, 2016-03-22 19:01 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Hi, Akihiro > > I see [1] says the clean up patch will remove translations less than 66% ( > infra jobs will only delete translation files less than 20% ). > I remember [1] was an agreement made I18n team before. I was not aware of this agreement. Thanks. > I don't have strong opinion whether to clean up translations or not. > I respect any decisions made by you and Horizon team. I am really surprised. I have never been involved in the decision of translation cleanup. I don't know any decision around this by the Horizon team. Horizon team are always following the I18n team decision about i18n related topic. > If you are going to propose a clean up patch, I will suggest to follow the > same criteria in [1]. It is not a decision of Horizon team, so I am not going to do this. This is the reason I asked this. Thanks, Akihiro > > Best regards > Ying Chun Guo (Daisy) > > [1] > https://wiki.openstack.org/wiki/Translations/Infrastructure#Release_handling > > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/22/2016 01:11:08 AM: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: "openstack-i18n(a)lists.openstack.org" > <Openstack-i18n(a)lists.openstack.org> >> Date: 03/22/2016 01:13 AM >> Subject: [Openstack-i18n] Will translation cleanup happen for Mitaka? >> >> Hi, >> >> I saw translation cleanup which removed PO files of less translated >> language before Liberty release. >> Will the same thing happen for Mitaka release? >> Is anyone from the i18n project aware of it? >> >> I cannot find good information on this. >> The only information is [1] but it looks a proposal. >> I am not sure where it is discussed and who is the contact. >> >> I am writing another mail as Horizon liaison which asks how to update >> horizon language list >> before the release. If some cleanup happens for Mitaka, I hope the >> language list update happens >> at the same time or follow the same criteria. >> >> [1] https://wiki.openstack.org/wiki/Translations/ >> Infrastructure#Release_handling >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > >

1 0

Will translation cleanup happen for Mitaka?
by Akihiro Motoki 22 Mar '16

22 Mar '16

Hi, I saw translation cleanup which removed PO files of less translated language before Liberty release. Will the same thing happen for Mitaka release? Is anyone from the i18n project aware of it? I cannot find good information on this. The only information is [1] but it looks a proposal. I am not sure where it is discussed and who is the contact. I am writing another mail as Horizon liaison which asks how to update horizon language list before the release. If some cleanup happens for Mitaka, I hope the language list update happens at the same time or follow the same criteria. [1] https://wiki.openstack.org/wiki/Translations/Infrastructure#Release_handling

3 2

Criteria of Horizon language list for Mitaka release
by Akihiro Motoki 22 Mar '16

22 Mar '16

Hi i18n team, As Horizon liaison, I would like to ask you all about the criteria of Horizon language list for Mitaka release. The same topic was discussed several releases ago and the consensus at that time were: * remove all translations with less than 90% progress * update the language list accordingly. Translations were imported manually at that time and the situation may be changed now. I don't have an opinion and will just follow the i18n project decision. If no response or well-defined criteria, I will just keep the current language list [1]. The following is just information: We have four PO files (django/djangojs for horizon and openstack_dashboard). The current translation import policy for each PO file is documented here [2]. Each PO file is imported once the translation percentage becomes over 75% and it will be removed when the translation percentage becomes less than 20%. What is our criteria? In future releases, I think we should automate this as a part of translation import jobs. I will reduce the work of horizon liaison. Akihiro [1] https://github.com/openstack/horizon/blob/master/openstack_dashboard/settin… [2] https://wiki.openstack.org/wiki/Translations/Infrastructure#Translation_per…

2 1

Translations for release notes in Mitaka? Perhaps NO
by Akihiro Motoki 22 Mar '16

22 Mar '16

The release management team has changed the process of generating releases notes for Mitaka. Release notes are generated from YAML files in individual repos by using reno. My understanding is that we don't have translation support for Mitaka release notes. Is it correct? After checking the meeting minutes, I found Kato has an action item to talk about it with the relmgt team. is there any feedback? Personally I am okay with it. I am always using English release notes :-) I am translating release notes only for reading them carefully and better understanding of the release. Thanks, Akihiro

4 7

Re: [Openstack-i18n] Looking for Translations for Nova Mitaka RC1
by Augustina Ragwitz 22 Mar '16

22 Mar '16

On Fri, Mar 18, 2016 at 12:34 AM, Ying Chun Guo <guoyingc(a)cn.ibm.com> wrote: > Ragwitz, > > I hope your team can cut RC2 on March 28, leaving a whole week for > translators to complete their work. > Please help to talk to nova team. > Thank you. > > Best regards > Ying Chun Guo (Daisy) > > > "Ragwitz, Augustina" <augustina.ragwitz(a)hpe.com> wrote on 03/18/2016 > 12:12:53 AM: > > > From: "Ragwitz, Augustina" <augustina.ragwitz(a)hpe.com> > > To: Openstack-i18n Openstack-i18n <openstack-i18n(a)lists.openstack.org> > > Date: 03/18/2016 12:14 AM > > Subject: Re: [Openstack-i18n] Looking for Translations for Nova Mitaka > RC1 > > > > > According the agreement about StringFreeze[1], cutting RC1 means > hard > > > freeze and translators can get extra 10 days to complete their > > > translations after hard freeze. So I don't think we can finish the > job > > > next week. The translation work is planned to be finished at > > the early of > > > the week after next. > > > > > > Can you figure out when is the last day to merge nova translations > ? > > > > I will follow up with the Nova team to find out our projected > > timeline for RC2. We have our team meeting today so I'll bring it up > > then. I assumed it would be end of next week based on the date in > > Launchpad for the OpenStack project [1], but this might not be accurate. > > > > [1] https://launchpad.net/openstack/+milestone/mitaka-rc2 > The Nova team will need to cut RC2 this week because we have some critical issues that need to be addressed before translations will be available. We will include whatever translations are available at that time. We will then cut RC3 the following week per your timeline to ensure all translations are included in the final release. If there is going to be any change to this, then I will follow up and let you all know. We recognize the value of the translations your team provides and will make sure they make it into the final release. --- Augustina Ragwitz Sr Systems Software Engineer, HPE Cloud Hewlett Packard Enterprise --- irc: auggy

1 0

My less activity in Newton (as i18n project) and some suggestions to the team
by Akihiro Motoki 22 Mar '16

22 Mar '16

Hi team, I am writing this mail to announce my less activity in Newton cycle (as I18n project) and will focus on translations and reviews of my focused and interested areas (i.e, dashboards and documentations). Translation is just my spare-time activity, so I need to choose how to spend my time. I have been involved in OpenStack translation activity before the I18n team is organized. The community is growing continuously and it is time for me to focus on translation itself again. I have made various activities including the following for the i18n team so far, but most of them are now over or can be shared by the community. * Coordinate the translation import timing for Horizon (now importing translation are done automatically) * Coordinate the final release timing of dashboards (now we have cross-project liaisons. it is no longer a personal role.) * Coordinate translation imports for stable updates (now imported automatically) * Provide translation check site for dashboards (we will have the official translation check site and I intentionally decided not to provide such site to encourage the effort in the i18n project.) * Continuously improve the upstream of Horizon and documentations for translation friendly. * Setup translation setup for horizon plugins in Mitaka (Completed) * Write various documentations around translation and I18n activities Finally, I would like to share several thoughts and suggestions for the i18n project before stepping down from the main activity of the i18n team. I hope the community is healthy enough and see much progress in Newton. I will help your efforts from individual project side. * Glossary management: It needs to be improved along with a new version of Zanata. The basic process itself on how to update glossary is not documented. In addition to this, contextual information support would be great. * Release notes translation * Documentation around i18n are spread: * We have i18n related documentations in several places. The infra manuals, horizon devref docs, i18n docs, and openstack wiki. We should have better guidance for readers considering their interests. Although appropriate place depends on a content, the i18n team should lead the effort. * Need more documentations for various processes. For example, how we decide prioritized projects for translations should be documented. In Mitaka translations, some dashboard plugin whose member responded in the ML is prioriptized and some plugin who added an entry to the cross project liaison wiki page are not. This is unfair. Another example is the criteria of the language list of Horizon translations. Maintaining the translation check site is another one. * Discussion process: I previously proposed several questions or improvements via MLs or gerrit. In many times, hey let's discuss in team meetings and that's all. No feedback or continued discussion on the original place where discussions happened. This is the point I feel frustrated and one of reason I am leaving. I understand IRC meeting is important, but that's not all. I am not a full-timer for translations and it leads most meeting times do not work. Translations are supported by not small number of volunteers, so I believe more async communications like ML or gerrit should be encouraged. * Better translation quality with technical knowledge: * Previously we try to increase the number of translators to encourage transltaions. I think it is now time to improve the quality of translations for languages translated well. To improve the translation quality, understanding OpenStack projects is inevitable. It is not enough to see strings in Zanata. * We need to explore a way how to improve the quality. In addition to involving technical contributors in translation reviews, I believe pure translators understand the basics of OpenStack projects and their concepts. As I mentioend in a recent IRC meeting (which I could luckily job), translation and reviews of documentations are one of ways to understand OpenStack projects. * For example, in Japanese translations, I played a role of technical reviewers so far, but I am not scalable, so I cannot play this role and have no more time to review server side projects which I am not interested in translations for. I believe other language teams have similar problems. Thanks for your all help so far. Note that I will continue my role as i18n liaison of horizon and neutron. I also continue to be a translator and a reviewer. Best Regards, Akihiro

1 0

PTL non-candidacy
by Ying Chun Guo 21 Mar '16

21 Mar '16

Hi, team I'm writing to let team know I will not run for I18n PTL in Newton cycle. I18n team have a long history starting from July of 2013. I was there at the beginning. Almost 3 years passed, I see the team growth rapidly. Especially in the recently year, a lot of things happened. In Vancouver, we had the first I18n team meeting and we decided to go official. We made it in Liberty cycle. In Tokyo, tens of translators got their ATC codes because of translation contributions. We successfully moved to Zanata. We set up our own I18n repository. Translation contributions can be shown in stackalytics. Translation check website will be ready soon. Full time translators work together with us in Mitaka translation. There were 1 million words translations in Zanata after Liberty translation. I'm sure the number will grow a big amount in Mitaka. I'm so proud of the team and progresses we made. I appreciated the great support from coordinators. I appreciated the help of Elizabeth, Steve, Carlos and Alex, who helped to set up our own dedicated translation website. I appreciated Andreas's work on infra side. I appreciated Tom and Stefano who helped to set up the team. I'm so glad that I made a lot of friends there. I'm happy to see Kato announced his candidacy for the new PTL. I think he is well qualified. I will not leave. I will support the new PTL to make a smooth transition. I will continue as the coordinator of Simplified Chinese team and contributor of I18n team. I'm looking forward to see more achievements we make in the future. Thank you and best regards. Ying Chun Guo (Daisy)

11 10

Hard string freeze and version switch
by Ying Chun Guo 21 Mar '16

21 Mar '16

Hi, team Now there are 5 server side projects and 1 dashboard project which have met the hard string freeze and cut the RC1 ( release candidate 1 ). In their source code repositories, the stable/mitaka branch is created. In Zanata translation server, I created corresponding versions named as "stable-mitaka". The translation works need to be switched to "stable-mitaka" version from master version. I also changed the links in the front page of translation server. If you don't know which version you should work with, an easy way is to navigate to the correct version from the links in the front page. The 5 server side projects are: nova, glance, keystone, cinder, neutron, and heat. The 1 dashboard projects are: django_openstack_auth. The translations are planned to be imported in RC2. The server projects will have their source codes ready for RC2 next week. It's good if we can have the translations completed by the end of next week. Of course, the early, the better. The dashboard projects are slower than server projects. Horizon project will probably cut RC1 in the early of next week. Any questions, please let me know. Best regards Ying Chun Guo (Daisy)

1 1

Call for participation in evolving GILT in curriculum
by chandan kumar 18 Mar '16

18 Mar '16

Hi All, Most in FUEL community must have heard on the initiative to bring out a formal curriculum in GILT which can be taught either as short term or long term course. This was outcome of discussions at past FUEL-GILT events and FUEL meetings in Gnunify. Attached is presentation on how we intend to proceed. Have also created a draft document, link given below. We have been working on creating a draft curriculum, which becomes the starting point. https://docs.google.com/document/d/1M4KgUy4VOU8aIlo8XT-C7HW2no_B0B5ZhkM69TZ… Stage 1: Review draft & expand topic index. Owners for topics identified and available to work in Stage 2. This will be come the curriculum/syllabus. Target Date: 31st March 2016 Stage 2: On each identified topic, owners will collaboratively write a chapter of few pages (upto 10 should be good to start with). This would contain brief on the topic and sub topics, but not going into too much detail, external references can be given. In long term this content would evolve into one or more chapters of book on GILT which will be used as book in training/teaching GILT. Date: 1-2 months from completion of Stage 1. Welcome everyone to contribute to this. - Review the draft, give suggestions on what can be added. - Take ownership of topics, so can build topic index in chosen topic and write chapter on it. Link to document: https://docs.google.com/document/d/1M4KgUy4VOU8aIlo8XT-C7HW2no_B0B5ZhkM69TZ… If you wish to edit, please request someone who has edit permission to add you, or post comments/suggestions to start with. Thanks, Chandan Kumar

1 0

Zanata Group for Mitaka dashboard translations
by Akihiro Motoki 18 Mar '16

18 Mar '16

Hi Zanata admin, I noticed Zanata group "Mitaka dashboard translations" has strange entries. https://translate.openstack.org/version-group/view/mitaka-translation/proje… - two versions for django_openstack_auth : master and stable-mitaka - read-only version for horizon : master-old-keepforstatistics Could you correct these versions to the appropriate ones? Thanks, Akihiro

2 1

What's Up, Doc? 18 March 2016
by Lana Brindley 18 Mar '16

18 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, It is with great pleasure that I announce that I will be the PTL again for Newton, which will be my third release for openstack-manuals. I'm overwhelmed by the positive messages I've received since announcing my candidacy, and very excited to be leading such a dedicated and innovative group into the fray again. This week I spent some time on the Contributor Guide, working with Brian to get the docs tools documented, which is something we've been wanting to do for some time. Very soon I'll be calling for your ideas on Summit sessions, and beginning to do Design Summit planning. The Install Guide is now in the last push to have everything tested before release, but we can still use your help getting it all done! If you can help, please contact Matt Kassawara, or any docs core. == Progress towards Mitaka == 19 days to go! 515 bugs closed so far for this release. Docs Testing * Volunteers required! * https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting Release Tasks: * Release planning occurs in our etherpad here: https://etherpad.openstack.org/p/MitakaRelease * We're now freezing larger changes to the Install Guide, so cores will not be merging anything that changes the architecture of the guide, or significantly changes the technical content (except where that change is as a result of testing). This is to make the Install Guide testers work a little easier, by stopping the book from moving too much from under them. * We will be publishing release notes for our own projects to == Docs-tools == * Andreas and team have released a new version of the docs theme, which removes the versions information from the sidebar, and also removes the duplicated titles. This should make navigating the CI guides much easier, and reduce confusion over versions. == The Road to Austin == * PTL elections are now open for those projects that have more than one candidate. You should have received an email for elections in which you are eligible to vote. * I am pleased to announce that I am remaining as docs PTL for Newton (elected unopposed). I would also like to congratulate KATO Tomoyuki on becoming the new PTL for i18n, and to thank Daisy for her hard work in that group for many releases. * I have requested workrooms and fishbowls for the Austin Design Summit. I'll let you know when we get our allocation. I will send out a note next week to start gathering your ideas for sessions. == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' New for Mitaka release notes: Improved Pacemaker/Corosync cluster installation and configuration details http://docs.openstack.org/ha-guide/controller-ha-pacemaker.html (kudos Andrew Beekhof). Pacemaker Cluster Manager http://docs.openstack.org/ha-guide/intro-ha-arch-pacemaker.html and Keepalived http://docs.openstack.org/ha-guide/intro-ha-arch-keepalived.html architecture details and limitations (kudos Andrew Beekhof). Detailed Mariadb/Galera cluster installation, configuration and management guide http://docs.openstack.org/ha-guide/controller-ha-galera.html (kudos Kenneth Dyer). Improved RabbitMQ clustering guide http://docs.openstack.org/ha-guide/controller-ha-rabbitmq.html - HAProxy antipattern explained, new A/A option with Pacemaker resource agents (kudos KATO Tomoyuki, Andrew Beekhof). Many more, so read everything carefully ;-) '''User Guides - Joseph Robinson''' Larger patch for editing submitted this week, and working within the user guide team to reorganize the command line content in the admin user guide by moving common files into the cloud admin guide. '''API Docs - Anne Gentle''' Swagger files now built to developer.openstack.org. Project teams have templates for writing API guides within their project repository . == Doc team meeting == Next meetings: No meeting was held this week. Next meetings: APAC: Wednesday 23 March, 00:30 UTC US: Wednesday 30 March, 19:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… - -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#18_March_2016 - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJW642DAAoJELppzVb4+KUyfDcIAMpfegqx4dfyFCbK2LzhBzT0 Ky9CVUCzKJQGdZQVCGcfJZRJI3OtLXfWMKrkx5v5pE6lw0UJ1a8RfR8/46weUn1v wlC9k95RLeff64Wa16AE6YQc6oXEhsGWWciptgeTmg2aeWJfax7S1wx2F8UhF419 FM4iFr/PhvyrVs4BXeyx6l3LLRFfSWo/YiyEHDUOAPOQMJ0N/gZaOL5ir+fASEwl xSXbb9fzdVfhrJivnPOrxYoZBSivTSlIn4xWmGsMaoCUzV2xrQmwCWRV07TVneYp nthofj01Ij3kNWv2Gm3XrIkJFkHX7OG0+tlxPs3CUm2bguzQlpND45I/ILv8TbE= =GmrT -----END PGP SIGNATURE-----

1 0

Translation server is back !
by Ying Chun Guo 18 Mar '16

18 Mar '16

With the great support from infrastructure team, now we have our translation server back. You can login to http://translate.openstack.org to continue your work then. Sorry for the inconvenience. Best regards Ying Chun Guo (Daisy)

2 1

Re: [Openstack-i18n] Looking for Translations for Nova Mitaka RC1
by Ragwitz, Augustina 18 Mar '16

18 Mar '16

> According the agreement about StringFreeze[1], cutting RC1 means hard > freeze and translators can get extra 10 days to complete their > translations after hard freeze. So I don't think we can finish the job > next week. The translation work is planned to be finished at the early of > the week after next. > > Can you figure out when is the last day to merge nova translations ? I will follow up with the Nova team to find out our projected timeline for RC2. We have our team meeting today so I'll bring it up then. I assumed it would be end of next week based on the date in Launchpad for the OpenStack project [1], but this might not be accurate. [1] https://launchpad.net/openstack/+milestone/mitaka-rc2 --- Augustina Ragwitz Sr System Software Engineer, HPE Cloud Hewlett Packard Enterprise --- irc: auggy

1 0

Glossary management
by Akihiro Motoki 17 Mar '16

17 Mar '16

# I changed the thread title to the appropriate one. 2016-03-01 17:23 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Thank you for the input, Akihiro and Kato. > > I'm not strict in local communication method and IRC ID. > If you have clearly documented them in your team wiki, that's fine. > > As to the glossary, I still think git repository is better than > wiki to store glossaries. Git repo has strict control, while wiki > has no controls at all. Wiki is used for frequently update purpose. > After it turns to mature, Git repo is good to store. I agree that it is better to use gerrit to manage glossaries, but all of my efforts disappointed me and discourage me to do more efforts. I already tried to maintain our glossary with context in our git repository. It used YAML file and converts it to PO files. It allowed us to keep contextual information. You said it will be discussed in the IRC meetings, but I got no feedback. I felt it was simply ignored (or rejected). (I could not join IRC meetings. If joining meetings is a requirement, I have to go away.) I clearly define what is required, but I don't see any counter solution provided and it forces me to use useless format (i.e., PO files). I believe I already have made enough proposal, but all of the results disappoints me and discourage me to try more efforts because it tends to waste my time. Finally, I tried to use another way to manage the glossary, then I was complained that it is not a standard way...... As a result, I had no way to satisfy requirements. Managing the glossary in two places is completely less-productive, maintain the master glossary with context information and then copy it into i18n repo (with losing the contextual information). > And, using pot/po file can make all translation teams to easily follow the > same glossary list. Do you mean even if the data format does not satisfy our requirements we should use it? Unified tools or formats are also important, but tools/format which do not satisfy requirements are useless. > As to the glossary, I still think git repository is better than > wiki to store glossaries. Git repo has strict control, while wiki > has no controls at all. Wiki is used for frequently update purpose. > After it turns to mature, Git repo is good to store. Regarding wiki usage, I don't think each language team page is not frequently updated. Does this mean a language team page does not fit into Wiki? I am not sure why we need to apply strict policy only for glossary. If the problem is that a wiki allows everyone to edit contents (i.e. glossary in this case), it is a problem of communication in a local language team. Final question. Gerrit is an easy way for translators or translation reviewers? If a language coordinator is forced to proxy maintaining glossaries, Perhaps, I am expecting too much and I may be better to be a translator. Akihiro > I understand Japanese glossaries are out of date and your team don't > like the current one in Zanata. If that's your team decision, I'm OK > to delete it from Zanata. > > Thoughts? > > Best regards > Ying Chun Guo (Daisy) > > > "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> wrote on 2016/02/27 > 17:08:46: > >> From: "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> >> To: "'Akihiro Motoki'" <amotoki(a)gmail.com>, Ying Chun Guo/China/IBM@IBMCN >> Cc: Openstack-i18n <openstack-i18n(a)lists.openstack.org> >> Date: 2016/02/27 17:40 >> Subject: RE: [Openstack-i18n] To language team coordinators: get >> ready for Mitaka translation >> > >> > Thanks Daisy for initiating this. >> > >> > 2016-02-25 17:53 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> > > Dear coordinators, >> > > >> > > Mitaka translation will be started at the beginning of March, and >> > > probably ended in the week of March 28. >> > > We need to get ourselves ready for Mitaka translation from now on. >> > > >> > > Because of the join of IBM professional translators, we will be able >> > > to cover more projects in our translation plan of this release. >> > > Generally, the jobs of existing community translators will not be >> > > affected, focus on Horizon, same as before. >> > > IBM translators will focus on "other" projects. >> > > >> > > Before Mitaka translation starts, there are several things you can do: >> > > >> > > 1. Update glossary. >> > > >> > > If you don't have glossary translations in i18n repo[1], or you want >> > > to update glossary translations, you can send a patch with your >> > > translations or your updates to i18n repo directly. >> > >> > I would like to raise a question how the glossary work? Is it actually >> > working? >> > >> > As one of coordinators of Japanese team, the glossary list itself is >> > out-of-date. >> > In addition to update per-language glossary, can we update a list >> of glossary >> > itself? >> > >> > Beyond this, the current format of PO file for the glossary lacks an >> > essential feature as I described before. There is no way to describe the >> > context. >> > I wonder how the glossary help translations without the contextual >> > information. >> > As a result, Japanese team is forced to describe contextual information >> > in translated strings. >> > This is the reason we preferred to Wiki style glossary. >> > >> > From the above observation, does it sound a good option to clear the >> > whole >> > entry of Zanata glossary of a specific language? >> >> +1 to clear, as long as Japanese, as of now. >> >> > > 2. Document your local team communication method in the team wiki >> > > page[2]. >> > > >> > > While Mitaka translation starts, it's good to open your local >> > > communication channel to all of your language translators. Good >> > > communication is quite important for people from different places to >> > > work well together. >> > >> > I missed the previous team meeting (it is not special to me due to >> the meeting >> > time). >> > I would like to make some follow-up comments on a local communication. >> > >> > I personally would like to continue to use Gitter (hosted by Github) as >> > a communication channel in Japanese team. From my past experience, it >> > has >> > various good merits. >> > I felt the first point is really useful in the crunch time of Liberty >> > translation reviews. >> > >> > * Pros: >> > * it has a notification mechanism. Unread messages will be notified >> > via >> > email. >> > * It can be used via browser (without any extra application) >> > * Unlimited archive as long as gitter room is open to everyone >> > * Cons >> > * it is not provided by OpenStack infra >> > >> > Kato-san and Japanese team members, feel free to comment it. >> > Your feedbacks would be really appreciated. >> >> I agree to using Gitter in Japanese team. >> >> In my understand, using IRC channel for local team is not mandatory, >> just an option. >> >> >> > > 3. Join IRC channel[3] #openstack-i18n with your zanata ID >> > > >> > > As a coordinator, you have the responsibility to coordinate your >> > > language translations. >> > > A good practise is to show up in IRC and have your people to get you >> > > easily when they have troubles. >> > >> > "with Zanata ID"? It is just an option. It is not a requirement. >> > It is not a surprising thing someone uses an IRC nickname different from >> > Zanata ID. >> >> I'm using different IDs :) >> And, I'm not always join IRC because of my business reason and equipments. >> To coordinate my local language team, I'd like to use Gitter and >> local mailing list. >> >> >> Regards, >> KATO Tomoyuki >> >> > Note that it is important we need to know each other who you are but it >> > is not a requirement to use Zanata ID as IRC nickname if you already use >> > a different IRC nick. >> > >> > > If you have any questions, talk to me. >> > > My IRC ID is "Daisy" in the channel of #openstack-i18n. >> > >> > I can help you too. My nick is 'amotoki'. >> > I am usually online from 0200UTC to 1600UTC. >> > >> > # It will be easier to find me compared to finding Daisy on IRC :) # >> > Just >> > joking.. never mind Daisy! >> > >> > Akihiro >> > >> > > Thank you. >> > > >> > > Best regards >> > > Ying Chun Guo (Daisy) >> > > >> > > [1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n/locale >> > > [2] https://wiki.openstack.org/wiki/I18nTeam/team >> > > [3] https://wiki.openstack.org/wiki/IRC >> >

3 2

Re: [Openstack-i18n] Cannot connect to Zanata
by Ilya Alekseyev 17 Mar '16

17 Mar '16

Dear Yumiko, Ian, Kato-san, same here, i can login to openstack.org and more i've checked in https://openstackid.org/accounts/user/profile that authentification is successfull: https://translate.openstack.org:443/openid.seam | LOGIN But unfortunatelly can't login to zanata. Kind regards, Ilya Alekseyev. 2016-03-17 10:28 GMT+03:00 Yumiko Ogawa <OGAWAYUM(a)jp.ibm.com>: > > Kato-san, > > Yes, I can login www.openstack.org without any problem, but not Zanata... > > Best regards, > > 小川優美子 Yumiko Ogawa, PMP® <ogawayum(a)jp.ibm.com> > Translation Services Center, IBM Japan > Tel: 03-3808-5007 > > > "Kato, Tomoyuki" ---2016/03/17 16:22:32---Hi, Can you login www.openstack.org? > > From: "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> > To: Yumiko Ogawa/Japan/IBM@IBMJP, Ilya Alekseyev <ilyaalekseyev(a)acm.org> > Cc: "openstack-i18n(a)lists.openstack.org" < openstack-i18n(a)lists.openstack.org> > Date: 2016/03/17 16:22 > Subject: RE: [Openstack-i18n] Cannot connect to Zanata > > > ________________________________ > > > > Hi, > > Can you login www.openstack.org? > # I can. But I can not login translate.openstack.org, too. > > I guess it seems to be a combination problem between > Zanata and OpenStack OpenID, or Zanata standalone problem... > > KATO Tomoyuki > > > -----Original Message----- > > Hi, > > > > We have the same problem in Japan. I understand that the OpenID authentication system is down. Our translators have been > > on standby all day today, so hopefully Zanata will be back soon. > > > > 小川優美子 Yumiko Ogawa, PMP® <ogawayum(a)jp.ibm.com> > > Translation Services Center, IBM Japan > > Tel: 03-3808-5007 > > > > > > Ilya Alekseyev ---2016/03/17 15:59:39---Dear colluegues, for some unknown reason i cannot connect to Zanata. > > > > From: Ilya Alekseyev <ilyaalekseyev(a)acm.org> > > To: "openstack-i18n(a)lists.openstack.org" < openstack-i18n(a)lists.openstack.org> > > Date: 2016/03/17 15:59 > > Subject: [Openstack-i18n] Cannot connect to Zanata > > > > ________________________________ > > > > > > > > > > Dear colluegues, > > > > for some unknown reason i cannot connect to Zanata. > > Tried different browsers and it just don't work. > > Wonder if somebody have the same problems? > > > > Kind regards, > > Ilya Alekseyev_______________________________________________ > > Openstack-i18n mailing list > > Openstack-i18n(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > > > > > > > >

1 0

Mitaka translation, go!
by Ying Chun Guo 17 Mar '16

17 Mar '16

Hi, team According to the release schedule, Mitaka translation starts from today. In the home page of translation website[1], you can find the detail information of Mitaka translation plan. The plan includes 6 web projects and 8 backend projects. Mitaka translation will last for above 3 weeks, from March 4th to March 28th. Here are some points for your attention during translation. 1. We start translations after soft string freeze. It means there will be string changes while you are translating. So don't be surprise when you notice the percentage of translation progress becomes smaller. 2. The hard string freeze will happen in the week of March 14-18. Different projects have different exact time of hard freeze. After hard freeze, our translation work will switch from master version to mitaka version. The links in the translation plan in the home page will be changed correspondingly. So continue your translation work from links in the home page is a good practise. Also, I will send notice to mailing list when the switch happens. 3. After hard string freeze and switch to mitaka version, there will be very few string changes. We can get 10(almost) more days after hard string freeze to finish up the translations. Let's work together to make a great success of mitaka translation. If you have any questions or get into troubles, there are several ways to ask help from: 1. Get help from your local team through the local communication method 2. Go to #openstack-i18n 3. Send mail to I18n mailing list There is a whole team who are willing to help. Enjoy translations! Best regards Ying Chun Guo (Daisy) [1] http://translate.openstack.org

4 8

Cannot connect to Zanata
by Ilya Alekseyev 17 Mar '16

17 Mar '16

Dear colluegues, for some unknown reason i cannot connect to Zanata. Tried different browsers and it just don't work. Wonder if somebody have the same problems? Kind regards, Ilya Alekseyev

4 4

IRC meeting today
by Ying Chun Guo 17 Mar '16

17 Mar '16

Hi, team We will have IRC meeting today at UTC 1300 in #openstack-meeting. The agenda in my mind are: * Mitaka translation updates * Open discussions If you have more topics, feel free to add. Best regards Ying Chun Guo (Daisy)

1 0

Re: [Openstack-i18n] Wrong plural formula for russian
by Ilya Alekseyev 16 Mar '16

16 Mar '16

Dear Daisy, Akihiro, Alex, thank you very much for your investigation and fix of this issue. Kind regards. Ilya Alekseyev 2016-03-15 10:14 GMT+03:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > I think you are right. > plural can be only set once. > After setting, it's not able to change. > > python-neutronclient is fixed. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/14/2016 07:21:10 PM: > > > From: Akihiro Motoki <amotoki(a)gmail.com> > > To: Ying Chun Guo/China/IBM@IBMCN > > Cc: Alex Eng <aeng(a)redhat.com>, Ilya Alekseyev > > <ilyaalekseyev(a)acm.org>, "openstack-i18n(a)lists.openstack.org" > > <openstack-i18n(a)lists.openstack.org> > > Date: 03/14/2016 07:22 PM > > Subject: Re: [Openstack-i18n] Wrong plural formula for russian > > > > Hi Daisy, > > > > 2016-03-14 17:33 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > > > Hi, Akihiro > > > > > > I tried to upload a new Russian translation file with the correct > plural > > > formula to django-openstack-auth. > > > And then I downloaded it. Yet the header is not changed at all. > > > I'm afraid uploading po files will not change the header. > > > > I made some tests with nplurals. > > My conclusion is that Zanata allows to update nplurals ONLY ONCE. > > I succeed to change nplural to 2 by putting japanese PO file, but once > > it was changed, > > even though I put Japanese PO file with nplural==1, nplural was not > changed. > > > > I tested it using neutronclient Japanese. > > As an unfortunate result, Japanese resource in neutronclient now have > > the wrong nplurals (2). > > Could you reset neutronclient in Japanese? > > (There is no translation in neutronclient, so we can do this more easily > :-) > > > > Thanks, > > Akihiro > > > > > > > > Best regards > > > Ying Chun Guo (Daisy) > > > > > > > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/12/2016 09:13:09 PM: > > > > > >> From: Akihiro Motoki <amotoki(a)gmail.com> > > >> To: Ying Chun Guo/China/IBM@IBMCN > > >> Cc: Alex Eng <aeng(a)redhat.com>, Ilya Alekseyev > > >> <ilyaalekseyev(a)acm.org>, "openstack-i18n(a)lists.openstack.org" > > >> <openstack-i18n(a)lists.openstack.org> > > >> Date: 03/12/2016 09:14 PM > > >> Subject: Re: [Openstack-i18n] Wrong plural formula for russian > > >> > > >> Hi Daisy, Alex, > > >> > > >> I think the steps Daisy describes is the last resort. > > >> Regarding translation statistics, I have nothing to say as I don't > > >> know any about stats. > > >> > > >> There are a couple of things I would like to note. > > >> > > >> * It is better to first try to upload Russian PO files with > nplurals=3 > > >> even though you failed it last time. > > >> * We need to check other Russian resources other than Horizon. > > >> I checked django-openstack-auth and nova and they have nplurals=4. > > >> There might be more. > > >> At now only Horizon and dashboard-related projects use plural > cases, > > >> so we see this issue only in Horizon now. > > >> > > >> Akihiro > > >> > > >> > > >> > > >> 2016-03-11 14:20 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > > >> > Thank you for the investigation, Akihiro and Alex. > > >> > > > >> > Below are the steps we previously used. > > >> > We can follow the same steps, just changing "stable" version to > > > "master" > > >> > version. > > >> > I think the statistic data will not be affected in step 1 to 5. > > >> > But, if we delete master-old, the contribution data in master-old > will > > > be > > >> > removed. > > >> > So my suggestion is to do the same steps, and keep master-old > version > > > (mark > > >> > it as readonly) > > >> > till 6 month or 12 month later when the contribution data is not > that > > >> > important. > > >> > > > >> >> 1. Create Russian translation files with only the correct header > and > > > the > > >> >> pluralities translation items. > > >> >> 2. Create a new version named as russian-fix > > >> >> 3. Upload the source files and the Russian translation files > created > > > in #1 > > >> >> to the version russian-fix > > >> >> 4. Merge the stable version with version russian-fix > > >> >> 5. Rename stable version to stable-old, and rename russian-fix to > > > stable. > > >> > > > >> > Alex and Akihiro, please confirm my proposal. > > >> > Then I can take actions. > > >> > > > >> > Best regards > > >> > Ying Chun Guo (Daisy) > > >> > > > >> > > > >> > Alex Eng <aeng(a)redhat.com> wrote on 2016/03/11 04:36:15: > > >> > > > >> >> From: Alex Eng <aeng(a)redhat.com> > > >> >> To: Ilya Alekseyev <ilyaalekseyev(a)acm.org> > > >> >> Cc: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun Guo/China/ > > >> >> IBM@IBMCN, "openstack-i18n(a)lists.openstack.org" <openstack- > > >> >> i18n(a)lists.openstack.org> > > >> >> Date: 2016/03/11 04:37 > > >> >> Subject: Re: [Openstack-i18n] Wrong plural formula for russian > > >> > > > >> > > > >> >> > > >> >> Hi, > > >> >> > > >> >> If we fix the plural forms in pot file and push to Zanata, that > > >> >> would not affect the statistics. > > >> >> > > >> >> But I remember last time when we trying to fix this, there are > some > > >> >> limitation of the pluralform wont update after the file is being > > >> >> uploaded once to Zanata. And we have to create a new version with > > >> >> fixed pot file and use "merge translation" feature to bring over > all > > >> >> the translations. > > >> >> > > >> >> We can do the same thing again and the statistics won't be > affected. > > >> >> (copied translation doesn't count in as contribution) > > >> >> > > >> >> I checked and Zanata has the correct form. > > >> >> > > >> >> nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 > && > > >> >> (n%100<10 || n%100>=20) ? 1 : 2) > > >> >> > > >> >> --------------------------------------------- > > >> >> > > >> >> Alex Eng > > >> >> Senior Software Engineer > > >> >> Globalisation Tools Engineering > > >> >> DID: +61 3514 8262 > > >> >> Mobile: +614 2335 3457 > > >> >> > > >> >> Red Hat, Asia-Pacific Pty Ltd > > >> >> Level 1, 193 North Quay > > >> >> Brisbane 4000 > > >> >> Office: +61 7 3514 8100 > > >> >> Fax: +61 7 3514 8199 > > >> >> Website: www.redhat.com > > >> >> > > >> >> On Fri, Mar 11, 2016 at 3:00 AM, Ilya Alekseyev > > > <ilyaalekseyev(a)acm.org> > > >> >> wrote: > > >> >> Daisy, > > >> >> > > >> >> i remember we fixed this for Liberty. But looks like somewhere > wrong > > >> >> config or error in script that creating master version. > > >> >> How ca we fix it? How i can help with this issue? > > >> >> > > >> >> Alex, is it possible to fix plural formula ofr version and keep > > >> >> statistics safe? > > >> >> > > >> >> We need to fix it as soon as possible, because 4 plural forms > making > > >> >> issues for russian translation (empty message, empty buttons, etc, > > >> >> as we can seee in Kilo release). > > >> >> > > >> >> Kind regards, > > >> >> Ilya Alekseyev. > > >> >> > > >> >> С уважением, > > >> >> Илья Алексеев > > >> >> > > >> >> Russian OpenStack Community > > >> >> > > >> >> 2016-03-10 19:37 GMT+03:00 Akihiro Motoki <amotoki(a)gmail.com>: > > >> >> Russian translations in the horizon repo is downloaded from > Zanata, > > >> >> OpenStack translation platform. > > >> >> It seems Zanata has wrong plural configuration. > > >> >> > > >> >> > Daisy, Alex, > > >> >> Could you check Russian configuration in Zanata is correct? > > >> >> > > >> >> 2016-03-10 22:42 GMT+09:00 Ilya Alekseyev <ilyaalekseyev(a)acm.org>: > > >> >> > Dear collegues, > > >> >> > > > >> >> > i've checked current russian translation in horizon repository > and > > > find > > >> >> > out > > >> >> > that we have wrong plural formula in upstream. > > >> >> > > > >> >> > https://github.com/openstack/horizon/blob/master/ > > >> >> openstack_dashboard/locale/ru/LC_MESSAGES/django.po#L35-L37 > > >> >> > > > >> >> > There is only 3 plural forms in Russian. > > >> >> > And correct formula should be > > >> >> > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && > n%10<=4 > > > && > > >> >> > (n%100<10 || n%100>=20) ? 1 : 2); > > >> >> > > > >> >> > Looks like some script is wrong. > > >> >> > Does anybody know how to fix it? > > >> >> > > > >> >> > Kind regards, > > >> >> > Ilya Alekseyev > > >> >> > > > >> >> > _______________________________________________ > > >> >> > 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] Wrong plural formula for russian
by Akihiro Motoki 15 Mar '16

15 Mar '16

Hi Daisy, 2016-03-14 17:33 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Hi, Akihiro > > I tried to upload a new Russian translation file with the correct plural > formula to django-openstack-auth. > And then I downloaded it. Yet the header is not changed at all. > I'm afraid uploading po files will not change the header. I made some tests with nplurals. My conclusion is that Zanata allows to update nplurals ONLY ONCE. I succeed to change nplural to 2 by putting japanese PO file, but once it was changed, even though I put Japanese PO file with nplural==1, nplural was not changed. I tested it using neutronclient Japanese. As an unfortunate result, Japanese resource in neutronclient now have the wrong nplurals (2). Could you reset neutronclient in Japanese? (There is no translation in neutronclient, so we can do this more easily :-) Thanks, Akihiro > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/12/2016 09:13:09 PM: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: Ying Chun Guo/China/IBM@IBMCN >> Cc: Alex Eng <aeng(a)redhat.com>, Ilya Alekseyev >> <ilyaalekseyev(a)acm.org>, "openstack-i18n(a)lists.openstack.org" >> <openstack-i18n(a)lists.openstack.org> >> Date: 03/12/2016 09:14 PM >> Subject: Re: [Openstack-i18n] Wrong plural formula for russian >> >> Hi Daisy, Alex, >> >> I think the steps Daisy describes is the last resort. >> Regarding translation statistics, I have nothing to say as I don't >> know any about stats. >> >> There are a couple of things I would like to note. >> >> * It is better to first try to upload Russian PO files with nplurals=3 >> even though you failed it last time. >> * We need to check other Russian resources other than Horizon. >> I checked django-openstack-auth and nova and they have nplurals=4. >> There might be more. >> At now only Horizon and dashboard-related projects use plural cases, >> so we see this issue only in Horizon now. >> >> Akihiro >> >> >> >> 2016-03-11 14:20 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> > Thank you for the investigation, Akihiro and Alex. >> > >> > Below are the steps we previously used. >> > We can follow the same steps, just changing "stable" version to > "master" >> > version. >> > I think the statistic data will not be affected in step 1 to 5. >> > But, if we delete master-old, the contribution data in master-old will > be >> > removed. >> > So my suggestion is to do the same steps, and keep master-old version > (mark >> > it as readonly) >> > till 6 month or 12 month later when the contribution data is not that >> > important. >> > >> >> 1. Create Russian translation files with only the correct header and > the >> >> pluralities translation items. >> >> 2. Create a new version named as russian-fix >> >> 3. Upload the source files and the Russian translation files created > in #1 >> >> to the version russian-fix >> >> 4. Merge the stable version with version russian-fix >> >> 5. Rename stable version to stable-old, and rename russian-fix to > stable. >> > >> > Alex and Akihiro, please confirm my proposal. >> > Then I can take actions. >> > >> > Best regards >> > Ying Chun Guo (Daisy) >> > >> > >> > Alex Eng <aeng(a)redhat.com> wrote on 2016/03/11 04:36:15: >> > >> >> From: Alex Eng <aeng(a)redhat.com> >> >> To: Ilya Alekseyev <ilyaalekseyev(a)acm.org> >> >> Cc: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun Guo/China/ >> >> IBM@IBMCN, "openstack-i18n(a)lists.openstack.org" <openstack- >> >> i18n(a)lists.openstack.org> >> >> Date: 2016/03/11 04:37 >> >> Subject: Re: [Openstack-i18n] Wrong plural formula for russian >> > >> > >> >> >> >> Hi, >> >> >> >> If we fix the plural forms in pot file and push to Zanata, that >> >> would not affect the statistics. >> >> >> >> But I remember last time when we trying to fix this, there are some >> >> limitation of the pluralform wont update after the file is being >> >> uploaded once to Zanata. And we have to create a new version with >> >> fixed pot file and use "merge translation" feature to bring over all >> >> the translations. >> >> >> >> We can do the same thing again and the statistics won't be affected. >> >> (copied translation doesn't count in as contribution) >> >> >> >> I checked and Zanata has the correct form. >> >> >> >> nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && >> >> (n%100<10 || n%100>=20) ? 1 : 2) >> >> >> >> --------------------------------------------- >> >> >> >> Alex Eng >> >> Senior Software Engineer >> >> Globalisation Tools Engineering >> >> DID: +61 3514 8262 >> >> Mobile: +614 2335 3457 >> >> >> >> Red Hat, Asia-Pacific Pty Ltd >> >> Level 1, 193 North Quay >> >> Brisbane 4000 >> >> Office: +61 7 3514 8100 >> >> Fax: +61 7 3514 8199 >> >> Website: www.redhat.com >> >> >> >> On Fri, Mar 11, 2016 at 3:00 AM, Ilya Alekseyev > <ilyaalekseyev(a)acm.org> >> >> wrote: >> >> Daisy, >> >> >> >> i remember we fixed this for Liberty. But looks like somewhere wrong >> >> config or error in script that creating master version. >> >> How ca we fix it? How i can help with this issue? >> >> >> >> Alex, is it possible to fix plural formula ofr version and keep >> >> statistics safe? >> >> >> >> We need to fix it as soon as possible, because 4 plural forms making >> >> issues for russian translation (empty message, empty buttons, etc, >> >> as we can seee in Kilo release). >> >> >> >> Kind regards, >> >> Ilya Alekseyev. >> >> >> >> С уважением, >> >> Илья Алексеев >> >> >> >> Russian OpenStack Community >> >> >> >> 2016-03-10 19:37 GMT+03:00 Akihiro Motoki <amotoki(a)gmail.com>: >> >> Russian translations in the horizon repo is downloaded from Zanata, >> >> OpenStack translation platform. >> >> It seems Zanata has wrong plural configuration. >> >> >> >> > Daisy, Alex, >> >> Could you check Russian configuration in Zanata is correct? >> >> >> >> 2016-03-10 22:42 GMT+09:00 Ilya Alekseyev <ilyaalekseyev(a)acm.org>: >> >> > Dear collegues, >> >> > >> >> > i've checked current russian translation in horizon repository and > find >> >> > out >> >> > that we have wrong plural formula in upstream. >> >> > >> >> > https://github.com/openstack/horizon/blob/master/ >> >> openstack_dashboard/locale/ru/LC_MESSAGES/django.po#L35-L37 >> >> > >> >> > There is only 3 plural forms in Russian. >> >> > And correct formula should be >> >> > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 > && >> >> > (n%100<10 || n%100>=20) ? 1 : 2); >> >> > >> >> > Looks like some script is wrong. >> >> > Does anybody know how to fix it? >> >> > >> >> > Kind regards, >> >> > Ilya Alekseyev >> >> > >> >> > _______________________________________________ >> >> > Openstack-i18n mailing list >> >> > Openstack-i18n(a)lists.openstack.org >> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >> > >> > >

2 1

GILT in Curriculum
by Rajesh Ranjan 14 Mar '16

14 Mar '16

Hi We, FUEL Community [1], are in discussion with SICSR [2] and some other institutes to introduce a formal curriculum on GILT (Globalization, Internationalization, Localization, Translation) technology which can be taught either as short term or long term course. This was outcome of discussions at past FUEL GILT Conference and FUEL meetings in Gnunify. Please refer the mail by Karunakar: https://lists.fedorahosted.org/archives/list/fuel-discuss@lists.fedorahoste… Please check the draft curriculum link: https://docs.google.com/document/d/1M4KgUy4VOU8aIlo8XT-C7HW2no_B0B5ZhkM69TZ… You are invited to contribution in the formation of the curriculum and take any chapter/sub chapter. Your suggestions are also welcome! Like all the content of FUEL Project, the content of the curriculum will be under open license. This is a unique activity and will help GILT technology. Thanks [1]. http://fuelproject.org/ [2]. http://sicsr.ac.in/ -- *Rajesh Ranjan* Open Source Community Manager Digital India, Govt. of India https://twitter.com/kajha

1 0

Re: [Openstack-i18n] Wrong plural formula for russian
by Akihiro Motoki 14 Mar '16

14 Mar '16

Hi Daisy, Alex, I think the steps Daisy describes is the last resort. Regarding translation statistics, I have nothing to say as I don't know any about stats. There are a couple of things I would like to note. * It is better to first try to upload Russian PO files with nplurals=3 even though you failed it last time. * We need to check other Russian resources other than Horizon. I checked django-openstack-auth and nova and they have nplurals=4. There might be more. At now only Horizon and dashboard-related projects use plural cases, so we see this issue only in Horizon now. Akihiro 2016-03-11 14:20 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Thank you for the investigation, Akihiro and Alex. > > Below are the steps we previously used. > We can follow the same steps, just changing "stable" version to "master" > version. > I think the statistic data will not be affected in step 1 to 5. > But, if we delete master-old, the contribution data in master-old will be > removed. > So my suggestion is to do the same steps, and keep master-old version (mark > it as readonly) > till 6 month or 12 month later when the contribution data is not that > important. > >> 1. Create Russian translation files with only the correct header and the >> pluralities translation items. >> 2. Create a new version named as russian-fix >> 3. Upload the source files and the Russian translation files created in #1 >> to the version russian-fix >> 4. Merge the stable version with version russian-fix >> 5. Rename stable version to stable-old, and rename russian-fix to stable. > > Alex and Akihiro, please confirm my proposal. > Then I can take actions. > > Best regards > Ying Chun Guo (Daisy) > > > Alex Eng <aeng(a)redhat.com> wrote on 2016/03/11 04:36:15: > >> From: Alex Eng <aeng(a)redhat.com> >> To: Ilya Alekseyev <ilyaalekseyev(a)acm.org> >> Cc: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun Guo/China/ >> IBM@IBMCN, "openstack-i18n(a)lists.openstack.org" <openstack- >> i18n(a)lists.openstack.org> >> Date: 2016/03/11 04:37 >> Subject: Re: [Openstack-i18n] Wrong plural formula for russian > > >> >> Hi, >> >> If we fix the plural forms in pot file and push to Zanata, that >> would not affect the statistics. >> >> But I remember last time when we trying to fix this, there are some >> limitation of the pluralform wont update after the file is being >> uploaded once to Zanata. And we have to create a new version with >> fixed pot file and use "merge translation" feature to bring over all >> the translations. >> >> We can do the same thing again and the statistics won't be affected. >> (copied translation doesn't count in as contribution) >> >> I checked and Zanata has the correct form. >> >> nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && >> (n%100<10 || n%100>=20) ? 1 : 2) >> >> --------------------------------------------- >> >> Alex Eng >> Senior Software Engineer >> Globalisation Tools Engineering >> DID: +61 3514 8262 >> Mobile: +614 2335 3457 >> >> Red Hat, Asia-Pacific Pty Ltd >> Level 1, 193 North Quay >> Brisbane 4000 >> Office: +61 7 3514 8100 >> Fax: +61 7 3514 8199 >> Website: www.redhat.com >> >> On Fri, Mar 11, 2016 at 3:00 AM, Ilya Alekseyev <ilyaalekseyev(a)acm.org> >> wrote: >> Daisy, >> >> i remember we fixed this for Liberty. But looks like somewhere wrong >> config or error in script that creating master version. >> How ca we fix it? How i can help with this issue? >> >> Alex, is it possible to fix plural formula ofr version and keep >> statistics safe? >> >> We need to fix it as soon as possible, because 4 plural forms making >> issues for russian translation (empty message, empty buttons, etc, >> as we can seee in Kilo release). >> >> Kind regards, >> Ilya Alekseyev. >> >> С уважением, >> Илья Алексеев >> >> Russian OpenStack Community >> >> 2016-03-10 19:37 GMT+03:00 Akihiro Motoki <amotoki(a)gmail.com>: >> Russian translations in the horizon repo is downloaded from Zanata, >> OpenStack translation platform. >> It seems Zanata has wrong plural configuration. >> >> > Daisy, Alex, >> Could you check Russian configuration in Zanata is correct? >> >> 2016-03-10 22:42 GMT+09:00 Ilya Alekseyev <ilyaalekseyev(a)acm.org>: >> > Dear collegues, >> > >> > i've checked current russian translation in horizon repository and find >> > out >> > that we have wrong plural formula in upstream. >> > >> > https://github.com/openstack/horizon/blob/master/ >> openstack_dashboard/locale/ru/LC_MESSAGES/django.po#L35-L37 >> > >> > There is only 3 plural forms in Russian. >> > And correct formula should be >> > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && >> > (n%100<10 || n%100>=20) ? 1 : 2); >> > >> > Looks like some script is wrong. >> > Does anybody know how to fix it? >> > >> > Kind regards, >> > Ilya Alekseyev >> > >> > _______________________________________________ >> > Openstack-i18n mailing list >> > Openstack-i18n(a)lists.openstack.org >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >

2 1

Wrong plural formula for russian
by Ilya Alekseyev 14 Mar '16

14 Mar '16

Dear collegues, i've checked current russian translation in horizon repository and find out that we have wrong plural formula in upstream. https://github.com/openstack/horizon/blob/master/openstack_dashboard/locale… There is only 3 plural forms in Russian. And correct formula should be nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2); Looks like some script is wrong. Does anybody know how to fix it? Kind regards, Ilya Alekseyev

4 10

[I18n] PTL Candidacy
by Kato, Tomoyuki 14 Mar '16

14 Mar '16

Hello everyone, I'd like to announce my candidacy for I18n PTL. I'm one of the most active translators since July 2013 when I18n team is a just working group, not an official project. Also, I'm one of Japanese coordinators. Japanese translation team is the most active team in I18n team. We sometimes share a few tips from our experience to I18n team. I18n team have spent a very great time for a long time. Especially, after we became an official project, we have became more collaborative in cross-language activity, such as building dashboard translation check site. I appreciate the current I18n PTL Daisy. She made our team become an official project. In the Newton cycle, I'd like to * support dashboard and its plug-ins tranlation into more languages, * facilitate documentation tranlation into more languages, * design and improve translation process, glossary management, translation bug triage process, and so on. Also, I'd like to feedback our experience to the translation system Zanata and cooperate with Zanata and Infra team to improve our translation efficiency. I think user facing contents translation is essential to improve user experience to the people having various language background. I believe I18n activity is necessary for OpenStack to become more and more universal. Best regards, KATO Tomoyuki (katomo)

1 0

[Docs] PTL Candidacy
by Lana Brindley 14 Mar '16

14 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, I am seeking re-election as Documentation PTL for Newton. I have now been the docs PTL for two releases (Liberty and Mitaka), and would love another term in the middle of the alphabet! We've achieved a lot this time around, including an almost complete conversion to RST, quite a few structural overhauls of popular books, and some fundamental toolchain improvements. There is still lots to be done, though, and I would love your support to achieve this in Newton. During Liberty we got the bulk of our books migrated away from Docbook XML and into RST. In Mitaka, we completed that work (with only the Ops Guide remaining to be converted in Newton). For the last couple of releases, we've also had a focus on improving the information architecture of our books, and have now successfully completed overhauls of our most popular books, with the Architecture Guide also well underway. All of these tasks will be carried over to Newton, with many of them finally coming to completion. In Newton, I would also like to address some of the larger issues around the organisation of our documentation suite, making it easier for developers to contribute quality code to our docs, and better welcoming and introducing new big tent projects to the documentation team. At the Mitaka summit in Tokyo, we decided to make a concerted effort to pay down a lot of our tech debt, and one of the main ways we chose to do that was to change the way we handled the DocImpact flag in our bugs. We merged those changes to DocImpact about a month ago now, and it is already having a significant impact on the amount of untriaged bugs outstanding. We're now much more able to keep on top of our bug queue, which is giving us a much greater ability to pay down tech debt. In this vein, we also have put a lot of effort into ensuring new contributors have a better onboarding experience to docs, with the creation of our new Contributor Guide which replaces a lot of old wiki-based content, a great 'get started with docs' campaign at the last Summit (which resulted in a hard copy article in the Summit edition of SuperUser, and Anne and I on SuperUser TV), and a general willingness to respond to questions on the mailing lists and help out new users wherever we find them. In the Liberty release cycle, we closed just over 600 bugs, and we're very close to matching that number for Mitaka, with 505 bugs closed as I write this. Again, we've managed to keep on top of the aging bugs as well, with all bugs older than a year now closed. In the Mitaka release, we managed to close 16 blueprints, which is a massive increase over Liberty's 7. I'm very excited about making the trek to Austin soon for the Newton summit, to catch up with old friends, and hopefully meet some of our newest contributors. Please be sure to stop for a chat if you see me around :) I'd love to have your support for the PTL role for Newton, and I'm looking forward to continuing to grow the documentation team. Thanks, Lana (@loquacities) - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJW5g++AAoJELppzVb4+KUy9LAH/RC5y/gM22qywGZaE2y4hWEc b+xdCxFUuh41l3WJhQ2iRJrnZUjm84doG2eCIcCpJW/OC5udo+2GiQYGmLUH278A uz8Rfglsu/SmDhWZbaIWtiKXo3WedmWzXUbBCV7/+aftphKLMdckD1KAharZZOWq Jqzg56SjWRqzbO++XiciCVwQ+zgoGuzJzYEQ1SsYsAdp/+wdtO2qPORZO1UuoOfz wFFS/OG8O4PsJa3e9KW/kHzDY3Emkz7bhqDcbE6w3HyszC6bEq8lDgmcXtg2SoNn FzjEpoiiAyalncUfo3p+v+7CV/3M/N4nCB2K+VhYO0hIAxPgUMxhrP3jzzq/gSI= =sboQ -----END PGP SIGNATURE-----

1 0

Re: [Openstack-i18n] Wrong plural formula for russian
by Alex Eng 14 Mar '16

14 Mar '16

+1 Daisy --------------------------------------------- Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com On Fri, Mar 11, 2016 at 3:20 PM, Ying Chun Guo <guoyingc(a)cn.ibm.com> wrote: > Thank you for the investigation, Akihiro and Alex. > > Below are the steps we previously used. > We can follow the same steps, just changing "stable" version to "master" > version. > I think the statistic data will not be affected in step 1 to 5. > But, if we delete master-old, the contribution data in master-old will be > removed. > So my suggestion is to do the same steps, and keep master-old version > (mark it as readonly) > till 6 month or 12 month later when the contribution data is not that > important. > > > 1. Create Russian translation files with only the correct header and the > > pluralities translation items. > > 2. Create a new version named as russian-fix > > 3. Upload the source files and the Russian translation files created in > #1 > > to the version russian-fix > > 4. Merge the stable version with version russian-fix > > 5. Rename stable version to stable-old, and rename russian-fix to stable. > > Alex and Akihiro, please confirm my proposal. > Then I can take actions. > > Best regards > Ying Chun Guo (Daisy) > > > Alex Eng <aeng(a)redhat.com> wrote on 2016/03/11 04:36:15: > > > From: Alex Eng <aeng(a)redhat.com> > > To: Ilya Alekseyev <ilyaalekseyev(a)acm.org> > > Cc: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun Guo/China/ > > IBM@IBMCN, "openstack-i18n(a)lists.openstack.org" <openstack- > > i18n(a)lists.openstack.org> > > Date: 2016/03/11 04:37 > > Subject: Re: [Openstack-i18n] Wrong plural formula for russian > > > > Hi, > > > > If we fix the plural forms in pot file and push to Zanata, that > > would not affect the statistics. > > > > But I remember last time when we trying to fix this, there are some > > limitation of the pluralform wont update after the file is being > > uploaded once to Zanata. And we have to create a new version with > > fixed pot file and use "merge translation" feature to bring over all > > the translations. > > > > We can do the same thing again and the statistics won't be affected. > > (copied translation doesn't count in as contribution) > > > > I checked and Zanata has the correct form. > > > > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && > > (n%100<10 || n%100>=20) ? 1 : 2) > > > > --------------------------------------------- > > > > Alex Eng > > Senior Software Engineer > > Globalisation Tools Engineering > > DID: +61 3514 8262 > > Mobile: +614 2335 3457 > > > > Red Hat, Asia-Pacific Pty Ltd > > Level 1, 193 North Quay > > Brisbane 4000 > > Office: +61 7 3514 8100 > > Fax: +61 7 3514 8199 > > Website: www.redhat.com > > > > On Fri, Mar 11, 2016 at 3:00 AM, Ilya Alekseyev <ilyaalekseyev(a)acm.org> > wrote: > > Daisy, > > > > i remember we fixed this for Liberty. But looks like somewhere wrong > > config or error in script that creating master version. > > How ca we fix it? How i can help with this issue? > > > > Alex, is it possible to fix plural formula ofr version and keep > > statistics safe? > > > > We need to fix it as soon as possible, because 4 plural forms making > > issues for russian translation (empty message, empty buttons, etc, > > as we can seee in Kilo release). > > > > Kind regards, > > Ilya Alekseyev. > > > > С уважением, > > Илья Алексеев > > > > Russian OpenStack Community > > > > 2016-03-10 19:37 GMT+03:00 Akihiro Motoki <amotoki(a)gmail.com>: > > Russian translations in the horizon repo is downloaded from Zanata, > > OpenStack translation platform. > > It seems Zanata has wrong plural configuration. > > > > > Daisy, Alex, > > Could you check Russian configuration in Zanata is correct? > > > > 2016-03-10 22:42 GMT+09:00 Ilya Alekseyev <ilyaalekseyev(a)acm.org>: > > > Dear collegues, > > > > > > i've checked current russian translation in horizon repository and > find out > > > that we have wrong plural formula in upstream. > > > > > > https://github.com/openstack/horizon/blob/master/ > > openstack_dashboard/locale/ru/LC_MESSAGES/django.po#L35-L37 > > > > > > There is only 3 plural forms in Russian. > > > And correct formula should be > > > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && > > > (n%100<10 || n%100>=20) ? 1 : 2); > > > > > > Looks like some script is wrong. > > > Does anybody know how to fix it? > > > > > > Kind regards, > > > Ilya Alekseyev > > > > > > _______________________________________________ > > > Openstack-i18n mailing list > > > Openstack-i18n(a)lists.openstack.org > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > >

1 0

Wow!
by Andreas Jaeger 13 Mar '16

13 Mar '16

Habe mir gerade mal Statistiken angesehen. Deutsche Übersetung bei Dashboard ist auf Platz 2 und bei Server auf dem 2. Platz! Klasse! Ein Kommentar noch zu den Prozenten: Wir importieren neu von zanata in die Projekte nur solche Dateien, die mindestens 75 % der Messages übersetzt haben. Angezeigt wird in Zanata per Default als Prozentsatz aber die Wörter, aber das kann man temporär umschalten. Die Logdatein würde ich übrigens nicht übersetzen, die sehen wirklich nur Admins und können zu Verwirrung führen. Die wurden ausgelagert, damit wir ihnen niedrigere Priorität geben können. Gruß Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 2

What's Up, Doc? 11 March 2016
by Lana Brindley 11 Mar '16

11 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, This week I've been smashing some older bugs from our queue, and can now confirm that as a team we've closed everything older than a year! What a great effort, and a fabulous way to go into our release period. We have less than a month now before release, so I've been briefing our new release managers Brian and Olga, and have also spent some time speaking to various people about what docs will be releasing for Mitaka. Install Guide testing is now well underway, but we can always use more hands, so please consider getting involved. If you need help getting started, please contact Matt Kassawara, or any docs core. == Progress towards Mitaka == 26 days to go! 500 bugs closed so far for this release, which means we're about on par with where we were this time last release. Keep squishing those bugs! Docs Testing * Volunteers required! * https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting Release Managers: We now have two release managers for Mitaka: Brian Moss, and Olga Gusarenko. They'll be making sure we stay on track as we hurtle towards 7 April, and will be backed up by Anne, Andreas, myself, and of course our lovely core team. == The Road to Austin == * Speaker acceptances have now gone out, and the schedule is available: https://www.openstack.org/summit/austin-2016/summit-schedule/#day=2016-04-24 * PTL nominations for Newton have now opened: https://wiki.openstack.org/wiki/PTL_Elections_March_2016. I'm very pleased to announce that I will be submitting my candidacy for docs. * I have requested workrooms and fishbowls for the Austin Design Summit. I'll let you know when we get our allocation. * You should be starting to think about booking travel and accommodation soon! If you need a visa to travel to the United States, there's more info here: https://www.openstack.org/summit/austin-2016/austin-and-travel/#visa == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' No update this week. '''Installation Guide - Matt Kassawara''' No update this week. '''Networking Guide - Edgar Magana''' Progress towards the missing features and new ones for Mitaka. DSCP for QoS section is in good shape: https://review.openstack.org/#/c/273638/ Last Networking Guide meeting: http://eavesdrop.openstack.org/meetings/networking_guide/2016/networking_gu… Still missing a lot of attendence to the IRC meeting but we are happy with more contributions to the guide. Matt provided a short overview on how to contribute during the Neutron mid-cycle sessions '''Security Guide - Nathaniel Dillon''' No update this week. '''User Guides - Joseph Robinson''' User Guide APAC and US meetings this week - discussed merging the CLI reorganization patch, which was merged following the meeting. Becuase of a meetbot error, the APAC meeting did not take place, but I am sending a summary out to the mailing list, which I am still working on. '''Ops and Arch Guides - Shilla Saebi''' No update this week. '''API Docs - Anne Gentle''' No update this week. Bug days: Work on api-site bugs: https://bugs.launchpad.net/openstack-api-site Work on these remaining WADL bugs which have patches: https://review.openstack.org/#/c/288315/ https://review.openstack.org/#/c/283114/ Continue to review and work on bootprint patch. Karin Bradshaw working on CSS updates. '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Pranav Salunke, Roger Luethi''' We merged support for snapshots in the KVM backend. Osbash works now on 32-bit i386 nodes which also makes nested virtualization (creating the whole VM cluster within a VM) possible. There is a new configuration file for users who only want an automated VM cluster setup, but no automated OpenStack installation. Finally, a new feature splits server log files according to cluster build phases, which makes it much easier to identify the origin of a specific log entry. '''Training Guides - Matjaz Pancur''' Enabled automatic bug status resolving at merge (https://review.openstack.org/#/c/283453/) WIP - Upstream training - add toolchain info for trainees (https://review.openstack.org/#/c/286941/) '''Hypervisor Tuning Guide - Joe Topjian''' I included a bunch of links related to NUMA and large memory pages. It'd be nice if the relevant information was pulled from the links and summarized. I also included some information about virtio-scsi. '''UX/UI Docs Guidelines - Linette Williams''' No update this week. == Doc team meeting == Next meetings: The APAC meeting was held this week. You can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-03-09 Next meetings: US: No meeting this week APAC: Wednesday 23 March, 00:30 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… - -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#11_March_2016 - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJW4kjpAAoJELppzVb4+KUyUSEH/iBWAOfRKZd8xEjUUh6roBPY XMeQh13RTBLBftyQoyzgIDenWfnaUeCrcDWlyNdY3jOVsDVQF9q0AkvuuzqXrfUu /LsnqcSHwJO0ervp6z7d0iJ0droUnJf0Qf3h1MMwutcwynRJtHVOsUYMVTLG9Dcw wALqlmxFwukD3GrbQfZ1M8MDGwVMopWU9/GsFNlHnBnbJ6DQFLBylWzGPEUQFR3e x/HAEC/ofNANZ5GqUTroqArNbv12bOTQanBGzIpcqEJ3hNG1c9tUMA3xH8ygLdCG cRoeDA4sCheYn8LWr1eNnw1jx4CAjUiO7d91Tf12c7Wp8XhMSquU18JzZ+g6Rkc= =lGay -----END PGP SIGNATURE-----

1 0

Re: [Openstack-i18n] Zanata Group for server project translations?
by Akihiro Motoki 09 Mar '16

09 Mar '16

2016-03-07 0:08 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Administrators can create groups. > > When you are talking about "server projects", > do you mean projects like nova, glance, keystone, and etc ? Yes. nova and others. We usually use this term in -dev list. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/05/2016 09:32:08 PM: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: "openstack-i18n(a)lists.openstack.org" > <Openstack-i18n(a)lists.openstack.org> >> Date: 03/05/2016 09:34 PM >> Subject: [Openstack-i18n] Zanata Group for server project translations? >> >> Hi Daisy, >> >> Can' t we have Zanata Group for server project translations as well? >> In my understanding, only you can create a Zanata group and I failed >> to catch you in IRC. >> >> Akihiro >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > >

4 4

Re: [Openstack-i18n] To language team coordinators: get ready for Mitaka translation
by Alex Eng 07 Mar '16

07 Mar '16

Daisy, If you're importing po files, the only field it will populate is the "description" field which extract from comment in message. There's no "pos" related field in po file. See the attached file. --------------------------------------------- Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com On Tue, Mar 1, 2016 at 6:05 PM, Ying Chun Guo <guoyingc(a)cn.ibm.com> wrote: > Thank you for the information, Alex. > I know Zanata allows to import glossaries from CSV and po files. > I can see a sample of CSV file, with "description" and "pos" field[1]. > Can you provide us a sample of po file, with "description" and "pos" field > for an entry ? > > Best regards > Ying Chun Guo (Daisy) > [1] > http://docs.zanata.org/en/release/user-guide/glossary/upload-glossaries/ > > > Alex Eng <aeng(a)redhat.com> wrote on 2016/02/29 05:58:23: > > > From: Alex Eng <aeng(a)redhat.com> > > To: "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> > > Cc: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun Guo/China/ > > IBM@IBMCN, Openstack-i18n <openstack-i18n(a)lists.openstack.org> > > Date: 2016/02/29 05:59 > > Subject: Re: [Openstack-i18n] To language team coordinators: get > > ready for Mitaka translation > > > > On Sat, Feb 27, 2016 at 7:08 PM, Kato, Tomoyuki < > kato.tomoyuki(a)jp.fujitsu.com > > > wrote: > > > Beyond this, the current format of PO file for the glossary lacks an > > > essential feature as I described before. There is no way to describe > the > > > context. > > > I wonder how the glossary help translations without the contextual > > > information. > > > As a result, Japanese team is forced to describe contextual information > > > in translated strings. > > > This is the reason we preferred to Wiki style glossary. > > > > > > From the above observation, does it sound a good option to clear the > whole > > > entry of Zanata glossary of a specific language? > > > > FYI, as of Zanata 3.8, we support same source string with unique > > "description" and "pos" field for each glossary entry. > > This will help translator with more context information and able to > > have similar string with different context. > > > > > > > > > --------------------------------------------- > > > > Alex Eng > > Senior Software Engineer > > Globalisation Tools Engineering > > DID: +61 3514 8262 > > Mobile: +614 2335 3457 > > > > Red Hat, Asia-Pacific Pty Ltd > > Level 1, 193 North Quay > > Brisbane 4000 > > Office: +61 7 3514 8100 > > Fax: +61 7 3514 8199 > > Website: www.redhat.com >

2 3

Zanata Group for server project translations?
by Akihiro Motoki 07 Mar '16

07 Mar '16

Hi Daisy, Can' t we have Zanata Group for server project translations as well? In my understanding, only you can create a Zanata group and I failed to catch you in IRC. Akihiro

3 2