- OpenStack-I18n - lists.openstack.org

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

08 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

Fwd: [openstack-tw] [Hackathon]Call for translator
by Tom Fifield 04 Mar '16

04 Mar '16

FYI - ZH_TW Team is making progress on the First App guide :) -------- Forwarded Message -------- Subject: [openstack-tw] [Hackathon]Call for translator Date: Thu, 3 Mar 2016 22:38:59 +0800 From: Rico Lin <rico.l(a)inwinstack.com> To: openstack-tw(a)lists.openstack.org Dear all we already have 59% of "Write your first app" doc complete thank for a group of hard working student from 臺中科技大學National Taichung University 大家覺的我們有機會在18號前將剩下的部份全部翻譯完畢嗎：） translate.openstack.org/webtrans/Application.seam?project=api-site&iteratio… <http://translate.openstack.org/webtrans/Application.seam?project=api-site&i…> -- Best regards, */Rico Lin/* <http://www.inwinstack.com> 迎棧科技股份有限公司 │ 886-963-612-021 <tel:886-963-612-021> │ rico.l(a)inwinstack.com <mailto:rico.l@inwinstack.com> │ 886-2-7738-6804 <tel:886-2-7738-6804> #7754 │ 新北市220板橋區遠東路3號5樓C室 Rm.C, 5F., No.3, Yuandong Rd., Banqiao Dist., New Taipei City 220, Taiwan (R.O.C)

2 1

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

04 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, This week I've been concentrating on getting ready for the release, and I'm very pleased to announce that we now have not one but two release managers for Mitaka. Please welcome Brian and Olga, thanks to you both for stepping up to the challenge! I'm looking forward to working with you both to get this out the door. We also completed the docs core team review, with no changes for this month. 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 == 33 days to go! 465 bugs closed so far for this release. There is a global bug smash event next week to try and hit as many Mitaka bugs as possible. You can join an in-person group near you, or participate remotely. Details here: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka Docs Testing * Volunteers required! * https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting API Docs I'm very pleased to announce that Anne and the API docs team have managed to get HTML generation working directly from Swagger now. This is a massive leap forward for the API docs conversion. Well done to everyone involved! 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 == * The final round of ATC passes have now gone out. * 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 == Core Team reviews == I completed the core team review for March this week, and we decided to make no changes. We did, however, have some discussion about the stats we use to determine the core team membership. I currently use the 30 and 90 day russellbryant stats for determining review participation, and Stackalytics for commit participation, with emphasis being on the top 12 participants in each category. Feedback on the core team selection process is, as always, welcome. It is documented here: http://docs.openstack.org/contributor-guide/docs-review.html#achieving-a-co… == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' No update this week. '''Installation Guide - Matt Kassawara''' More patches and testing for Mitaka. '''Networking Guide - Edgar Magana''' No update this week. '''Security Guide - Nathaniel Dillon''' No update this week. '''User Guides - Joseph Robinson''' A patch for the reorganisation is under review - shifting the command line content in the admin user guide to the cloud admin guide. Following this patch merging, the next step is moving down the task list, and completing edits to the content in the Cloud Admin guide to improve the document. '''Ops and Arch Guides - Shilla Saebi''' The work items for the Architecture Design Guide converted to bugs: https://bugs.launchpad.net/openstack-manuals/+bugs?field.tag=arch-guide We still need people to confirm the bugs. Call for volunteers email went out to the ops and docs ML from Devon Boatwright. We are still looking for help, not getting many responses. Considering doing a swarm or work session at the summit in Austin for the Arch guide '''API Docs - Anne Gentle''' Patch fixing three of remaining 7 WADL bugs here: https://review.openstack.org/#/c/283114/ Patch that builds HTML from Swagger files here: https://review.openstack.org/#/c/286659/ This gets us over a big hurdle of making fairy-slipper "feature complete" while also ensuring the migration is complete. Great week, huge shoutout and thanks to Michael Krotscheck for the node/npm solution for building HTML. '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Pranav Salunke, Roger Luethi''' No update this week. '''Training Guides - Matjaz Pancur''' "Getting started" module for Training guides is published (http://docs.openstack.org/draft/training-guides/) Added "Local trainings" chapter to the Upstream training archive (http://docs.openstack.org/upstream-training/upstream-archives.html) cleanup patches (unused extensions, text redundancies and cleanup). Team meetings will be held on 1st and 3rd week in the month. '''Hypervisor Tuning Guide - Joe Topjian''' No update this week. '''UX/UI Docs Guidelines - Linette Williams''' Reviews continue for proposed UI panels in Invision == Doc team meeting == Next meetings: The US meeting was held this week, at the new time. You can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-03-02 Next meetings: APAC: Wednesday 9 March, 00:30 UTC US: Wednesday 16 March, 19:00 UTC ***Note the new time!*** 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#4_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/ iQEcBAEBCAAGBQJW2RKeAAoJELppzVb4+KUyiVEH/ROrKbQvJ3VEr1jVMNn5g16O aFu2aNjEd3cOJ50FHkzi0NdsHJoNslFq6NpSEcWdFQihKh5anZeaFA8flO8bKA/L xepUnQjTvcgvZgiREutcQGkowaIqZiUxkXr8YV36So+K8CQwyHOcBfBlcR8hSMRa r2k0o+BA2GjBZuAvjt4P6eIfCNrAA8N2oycXTU0F2j6IIwDoQ23A8uyTuKHrBArQ 8FYeUv31fabqA+jsRZRpYr2QinpyRW+m1xbeYsnh3cXq9QciwEqbdC44d/+MZsJq dOTI2MeUmCKz72Y7ftwPXGuyKcv84RNe/FSRoZWgCdIK3RSdChD/IVoiHtRbtUo= =+XXP -----END PGP SIGNATURE-----

1 0

French team mailing list and IRC channel
by JF Taltavull 03 Mar '16

03 Mar '16

Hello Daisy, The IRC channel #openstack-i18n-fr and the mailing list openstack-i18n-fr(a)lists.openstack.org are up and running :) Best regards, Jean-François Taltavull (jftalta) i18n french team coordinator

1 0

translation team communication, how to create mailing list
by Robert Simai 03 Mar '16

03 Mar '16

Hi, to get back on an older topic, e.g. see http://lists.openstack.org/pipermail/openstack-i18n/2015-September/001380.h… Zanata apparently doesn't have the capabilities to send messages to the translation team (the built in chat is not too helpful) and it doesn't seem realistic to expect such a feature in the near future. Since the German translator team is growing and to have some appropriate forum to discuss language specific issues and agree on standards, I thought about finally managing an email list, something like [Openstack-i18n-DE]. Would anyone know how to request/create an email list on lists.openstack.org? -- Thanks, Robert

3 5

Re: [Openstack-i18n] translation check site local.conf andconfiguraitons
by Akihiro Motoki 03 Mar '16

03 Mar '16

I am not sure the translation check site supports trove/sahara-dashboard for mitaka translation, so I decided not to push my current version of local.conf to the review of puppet-translation_checksite. You can freely pull my local.conf to the transaltion check site configuration! My latest version of local.conf is found at [1]. It supports trove-dashboard, sahara-dashboard and various neutron configurations. I also updated ansible-i18n-playbook [2] because it is referred to by the effort of the translation check site, but this repository will be deleted soon after the translation check site launches. [1] and [2] is used in my current developments. Akihiro [1] https://github.com/amotoki/ansible-playbook/tree/master/roles/devstack/temp… [2] https://github.com/amotoki/ansible-i18n-devstack/blob/master/roles/i18n-dev… 2016-02-24 16:55 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > I support to use puppet-translation_checksite to store a newest and latest > workable local.conf. > For various versions of local.conf, they mostly are used as references. > I think personal github is good to keep them. > > Thank you, Akihiro. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2016/02/24 00:32:42: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: SungJin Kang <gang.sungjin(a)gmail.com> >> Cc: "openstack-i18n(a)lists.openstack.org" >> <Openstack-i18n(a)lists.openstack.org> >> Date: 2016/02/24 00:34 >> Subject: Re: [Openstack-i18n] translation check site local.conf and >> configuraitons >> > >> I just remembered puppet-translation_checksite repo [1] is created to >> maintain the infra configuration for our translation check site. >> >> BTW, it sounds good to use i18n repo to share various contents >> including local.conf. >> We have various potential configuration options, so it is nice to have >> docs or files in our repo :-) >> >> [1] http://git.openstack.org/cgit/openstack-infra/puppet- >> translation_checksite/ >> >> 2016-02-24 1:22 GMT+09:00 SungJin Kang <gang.sungjin(a)gmail.com>: >> > HI, Akihiro. >> > >> > I things using i18n repo [1] >> > >> > Make directory /config? or /devstack/version? anythings. >> > >> > Thanks, >> > Sungjin >> > >> > [1]: http://git.openstack.org/cgit/openstack/i18n/ >> > >> > 2016-02-24 0:58 GMT+09:00 Akihiro Motoki <amotoki(a)gmail.com>: >> >> >> >> Hi, >> >> >> >> Thanks for working on translation check site as the upstream. >> >> >> >> Where is the configuration files maintained in OpenStack repositories? >> >> I can share my local.conf with GitHub gist or in other ways, but it is >> >> not the OpenStack way. >> >> We use gerrit to share everything. I would like to follow it. >> >> >> >> I promised to provide devstack local.conf which enables almost all >> >> features for the check site. >> >> I now have local.conf compatible with Liberty OpenStack dashboard >> >> ('compatible' means Trove and Sahara horizon plugins are supported). >> >> >> >> To support more horizon plugins beyond sahara/trove dashboard for >> >> translations, >> >> everyone can push a new version of local.conf once he/she finds and >> >> confirms >> >> a right configuration. There are many horizon plugins, so it is not >> >> reasonable to >> >> depend devstack configurations on a small group of peoples. >> >> >> >> Thanks, >> >> 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 >> >

2 3

IRC meeting tomorrow
by Ying Chun Guo 02 Mar '16

02 Mar '16

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

3 3

Re: [Openstack-i18n] To language team coordinators: get ready for Mitaka translation
by Akihiro Motoki 02 Mar '16

02 Mar '16

Do you want we have out-of-date Japanese glossary in i18n repo? I am not a fan of this but am okay if you want. 2016-03-02 22:05 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > I hope you can agree to abandon it. > We can work on the improvement after the po format for new glossary > feature is clear. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/02/2016 09:01:12 PM: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: Ying Chun Guo/China/IBM@IBMCN >> Cc: Tomoyuki KATO <tomo(a)dream.daynight.jp>, "openstack- >> i18n(a)lists.openstack.org" <openstack-i18n(a)lists.openstack.org> >> Date: 03/02/2016 09:02 PM >> Subject: Re: [Openstack-i18n] To language team coordinators: get >> ready for Mitaka translation >> >> Daisy, >> >> What should I do for https://review.openstack.org/285725 ? >> Should abandon it? >> >> 2016-03-02 19:05 GMT+09:00 Akihiro Motoki <amotoki(a)gmail.com>: >> > Daisy and Tomo, >> > >> > Thanks for dropping Japanese glossaries (+ follow-up). >> > >> > We Japanese team are happy to re-join the standard way of I18n team >> > once we support contextual information. >> > It was not an easy choice, but from our discussion one-to-one mapping >> > from the source lang to Japanese does not work. >> > >> > Akihiro >> > >> > 2016-03-01 22:45 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> >> >> >> Hi, KATO >> >> >> >> I have deleted Japanese glossaries. >> >> You can check now. >> >> >> >> Best regards >> >> Ying Chun Guo (Daisy) >> >> >> >> >> >> >> >> ----- Original message ----- >> >> From: KATO Tomoyuki <tomo(a)dream.daynight.jp> >> >> To: Ying Chun Guo/China/IBM@IBMCN >> >> Cc: Openstack-i18n <openstack-i18n(a)lists.openstack.org> >> >> Subject: Re: [Openstack-i18n] To language team coordinators: get > ready for >> >> Mitaka translation >> >> Date: Tue, Mar 1, 2016 7:21 PM >> >> >> >> Hi Daisy, >> >> >> >>> 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. >> >> >> >> Already enough clear in wiki, >> >> but only in Japanse :) because of local communication method. >> >> >> >>> 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. >> >>> And, using pot/po file can make all translation teams to easily > follow the >> >>> same glossary list. >> >> >> >> Yeah, I myself am generally agree to managing glossary on git > repository. >> >> But, as of now, it doesn't meet the requirements from Japanese team > fully. >> >> We need a little more work. >> >> >> >>> 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. >> >> >> >> I think so. It's Japanese team dicision at now. >> >> >> >> Thanks, >> >> KATO Tomoyuki >> >> >> >>> Thoughts? >> >>> >> >>> Best regards >> >>> Ying Chun Guo (Daisy) >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> 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] French team irc channel
by JF Taltavull 01 Mar '16

01 Mar '16

On 01/03/2016 14:46, Ying Chun Guo wrote: > I think #openstack-i18n-fr is good. So, let's go for it. > Do you need me to submit the patch to create this IRC channel ? Thanks Daisy,I will do it by myself. I'll let you know if something goes wrong. > Best regards > Ying Chun Guo (Daisy) > > ----- Original message ----- > From: JF Taltavull <jftalta(a)gmail.com> > To: Ying Chun Guo/China/IBM@IBMCN > Cc: Openstack-i18n Openstack-i18n > <openstack-i18n(a)lists.openstack.org>, Maxime Coquerel > <max.coquerel(a)gmail.com>, Safouen Benhadj <safouen.benhadj(a)gmail.com> > Subject: French team irc channel > Date: Tue, Mar 1, 2016 7:08 PM > Hi Daisy, > > In order to be more OpenStack compliant and more open, the i18n french > team would like to stop using Slack and start to communicate > through an > IRC channel. > > What would you think of creating a new channel like #openstack-i18n-fr > or #openstack-i18n-french-fr ? > > > Best regards > Jean-François Taltavull (jftalta) > >

1 0

French team irc channel
by JF Taltavull 01 Mar '16

01 Mar '16

Hi Daisy, In order to be more OpenStack compliant and more open, the i18n french team would like to stop using Slack and start to communicate through an IRC channel. What would you think of creating a new channel like #openstack-i18n-fr or #openstack-i18n-french-fr ? Best regards Jean-François Taltavull (jftalta)

2 1

Translation priority for Mitaka
by KATO Tomoyuki 01 Mar '16

01 Mar '16

Hi team, It's time to update our translation priority [1]. Here is my draft as high priority. Any comments are welcome. OpenStack Dashboard - Horizon - Authorization Page - Essential Plug-ins [TBD] Documentation [2] - Installation Guide - End User Guide - API Guide [1] https://translate.openstack.org/ [2] https://wiki.openstack.org/wiki/I18nTeam/docs-translation Thanks, KATO Tomoyuki

3 6

Closing Liberty translations?
by Andreas Jaeger 29 Feb '16

29 Feb '16

Since Mitaka translations start next week, I propose we close the Liberty translations now as discussed last autumn. How should we do this? Is there a need to keep the liberty branches for some time as read-only? Or should we delete them directly? 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

8 16

What's Up, Doc? 26 Feb 2016
by Lana Brindley 26 Feb '16

26 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, This week I've been working on code reviews and closing some of our oldest bugs from the bug queue. I've also updated the docs-specs core team list to reflect some recent changes to the Speciality Team leads, and doing some general prep work for the Mitaka release. We are now well and truly ready to start testing the Install Guide. If you need help getting started, please contact Matt Kassawara, or any of your friendly core team members :) == Progress towards Mitaka == 40 days to go! 445 bugs closed so far for this release. There is a global bug smash event coming up March 7-9 to try and hit as many Mitaka bugs as possible. You can join an in-person group near you, or participate remotely. There are still plenty of docs bugs that can be attended to. Details here: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka Docs Testing * Volunteers required! * https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting RST Conversions * All planned RST conversions are now complete! Reorganisations * Arch Guide: really needs a last minute push to get this complete before Mitaka. If you can help out, it would be greatly appreciated! ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * User Guides ** https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… ** Contact the User Guide Speciality team: https://wiki.openstack.org/wiki/User_Guides DocImpact * Is now complete == The Road to Austin == * The final round of ATC passes should be going out shortly. * I have now requested workrooms and fishbowls for the Austin Design Summit. I'll let you know when we get our allocation. * There is a plan to separate the Design Summit from the main conference after Barcelona. I strongly suggest you read the thread on the dev mailing list, if you haven't done so already: http://lists.openstack.org/pipermail/openstack-dev/2016-February/087161.html * 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''' Continue updating the guide for Mitaka using primarily RDO milestone 3 packages. Review patch that adds manila to the guide. Review patch that adds magnum to the guide. '''Networking Guide - Edgar Magana''' No update this week. '''Security Guide - Nathaniel Dillon''' No update this week. '''User Guides - Joseph Robinson''' Team successfully moved across dashboard content from the Admin User Guide to the Cloud Admin guide. Team is preparing to move the command line content, and then continue to edit the Cloud Admin guide over the next week. '''Ops and Arch Guides - Shilla Saebi''' The work items for the Architecture Design Guide have been converted to bugs: https://bugs.launchpad.net/openstack-manuals/+bugs?field.tag=arch-guide We need people to confirm the bugs, so we can start working on them. Call for volunteers email went out to the ops and docs ML from Devon Boatwright. We are still looking for help, not getting many responses. Architecture guide reorganization is underway. We have a drafts repo in openstack-manuals, feel free to ping Shilla or Darren Chan if you are interested in helping out. Considering doing a swarm or work session at the summit in Austin for the Arch guide '''API Docs - Anne Gentle''' Check for API migration bugs: https://bugs.launchpad.net/openstack-api-site/+bugs?field.tag=migration There are five bugs remaining. Look at the infra spec if you're interested in how we'll build docs with Swagger files. https://review.openstack.org/#/c/276484/ I'm investigating using this tool so that we replace flat HTML files built from WADL with flat HTML files built from Swagger. https://github.com/nknapp/bootprint-openapi '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Pranav Salunke, Roger Luethi''' Continued fixes to KVM backend and the library functions. Working on creating a webpage for training-labs. https://review.openstack.org/#/c/281713/ https://review.openstack.org/#/c/281721/ https://review.openstack.org/#/c/281367/ Hosting an additional meeting to get our new member on-board and some general discussion. '''Training Guides - Matjaz Pancur''' No update this week. '''Hypervisor Tuning Guide - Joe Topjian''' No update this week. '''UX/UI Docs Guidelines - Linette Williams''' Reviews continue for proposed panels in Invision. Enhancement in UI content guidelines complete for text and icon formatting recommendations (http://docs.openstack.org/contributor-guide/ui-text-guidelines.html) == Doc team meeting == Next meetings: The APAC meeting attempted to be held this week, but failed to meet quorum. Next meetings: US: Wednesday 2 March, 19:00 UTC ***Note the new time!*** APAC: Wednesday 9 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#26_February_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/ iQEcBAEBCAAGBQJWz9fuAAoJELppzVb4+KUycvYIAJcS46IEaJ10izihei5rFTC3 Y90og8sCTOBTtD36L/la4EQEb33gEzozvOfJlN+nXBbyI1J85q5Bbaxhvmt6WgVy 8lS7hGS8RD74caYM2Hyfby8LHfNXlnXDO9NKGBy10RCqsLMw5sgcNcnA0r5IcwVx OrWOSMwcA/T0oJybSeKrgnaUDwXFwaPpZP4LGGblJrw2+WI7TamxgYEBYG5fumWo FVyAaswBdu1+zA+bCN6KwtbhfbM0VYpQeAuafE8GMYXqeiuVdvTu67z4S4bQUnR2 1JsADOBi77i7AyzP9OknvcGTjxuwXzWopvSi01si16mzQ1CAtdimDej4lyaSJ1Q= =DM9Z -----END PGP SIGNATURE-----

1 0

Planning I18n sessions in Austin summit
by Ying Chun Guo 26 Feb '16

26 Feb '16

Hello, team I'm planning I18n session in Austin summit now. I have planned two sessions: 1. A 40 minutes working session to discuss translation processes and tools. 2. A half-day contributors meetup If you have other topics to discussion and want to organize a specific i18n session, please reply this email. Thank you. Best regards Ying Chun Guo (Daisy)

2 1

Re: [Openstack-i18n] Closing Liberty translations?
by Andreas Jaeger 24 Feb '16

24 Feb '16

On 2016-02-24 09:29, Ying Chun Guo wrote: > If we delete them, translation memory and translators contribution > statistic data will be affected. Really? Interesting. Alex, can you explain what deletion of a branch will do to the stats and memory, please? > So I don't support deleting. > I think we mark them as read only. > > If no objections, we can do it by the end of this week. Fine by me, I can work on the infra change, Andreas > Best regards > Ying Chun Guo (Daisy) > > > Andreas Jaeger <aj(a)suse.com> wrote on 2016/02/24 16:16:37: > >> From: Andreas Jaeger <aj(a)suse.com> >> To: "openstack-i18n(a)lists.openstack.org" > <openstack-i18n(a)lists.openstack.org> >> Date: 2016/02/24 16:18 >> Subject: [Openstack-i18n] Closing Liberty translations? >> >> Since Mitaka translations start next week, I propose we close the >> Liberty translations now as discussed last autumn. >> >> How should we do this? >> >> Is there a need to keep the liberty branches for some time as read-only? >> Or should we delete them directly? >> >> 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

2 1

translation check site local.conf and configuraitons
by Akihiro Motoki 24 Feb '16

24 Feb '16

Hi, Thanks for working on translation check site as the upstream. Where is the configuration files maintained in OpenStack repositories? I can share my local.conf with GitHub gist or in other ways, but it is not the OpenStack way. We use gerrit to share everything. I would like to follow it. I promised to provide devstack local.conf which enables almost all features for the check site. I now have local.conf compatible with Liberty OpenStack dashboard ('compatible' means Trove and Sahara horizon plugins are supported). To support more horizon plugins beyond sahara/trove dashboard for translations, everyone can push a new version of local.conf once he/she finds and confirms a right configuration. There are many horizon plugins, so it is not reasonable to depend devstack configurations on a small group of peoples. Thanks, Akihiro

4 4

Document your language team communication method in the wiki
by Ying Chun Guo 22 Feb '16

22 Feb '16

Hello, team According to the Mitaka dev schedule[1], the community will reach "soft string freeze" in Feb 29-4. We will start Mitaka translation at that time. In order to well collaboration among translator team, lower the barrier to new translators, we need good communication within each language team in the local language. So I hope each language team can have a clear communication method and document the method in the team wiki page.[2] The communication method can be openstack-i18n, if the language team don't want to create a new one. It can be a separate IRC channel other than openstack-i18n, for example, openstack-i18n-zh-cn. It can be a local communication method. Whatever it is, I'd like coordinators clearly document in the team wiki page. We can work well together with good communications. Thank you. Best regards Ying Chun Guo (Daisy) [1] http://releases.openstack.org/mitaka/schedule.html [2] https://wiki.openstack.org/wiki/I18nTeam/team

1 0

Fwd: [openstack-dev] [Horizon][Trove][Sahara] Horizon-Trove/Sahara External Repository
by Akihiro Motoki 20 Feb '16

20 Feb '16

Hi team, Forwarded to i18n list. trove-dashaboard and sahara-dashboard are now ready for translation. Translations for horizon plugins are now working well I believe. If you have any troubles, let me know. One thing to note. If your language team made a lot of translations on Trove and Sahara dashboard in Liberty, you can upload it for Mitaka translations. I already did this for Japanese. Akihiro ---------- Forwarded message ---------- From: Akihiro Motoki <amotoki(a)gmail.com> Date: 2016-02-19 11:50 GMT+09:00 Subject: Re: [openstack-dev] [Horizon][Trove][Sahara] Horizon-Trove/Sahara External Repository To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev(a)lists.openstack.org> Cc: Vince Brunssen <brunssen(a)us.ibm.com> Hi, > Horizon still have some things we need to tidy up on our end to make sure we > have full support for testing and localization for external plugins. I am pleased to announce that translations of trove-dashboard and sahara-dashboard now work for the master branch. We have the parity to Liberty release :-) Thanks Andreas and folks involved in this effort. Akihiro 2015-12-04 6:44 GMT+09:00 Thai Q Tran <tqtran(a)us.ibm.com>: > Hello Trovers and Horizoneers, > > The intention of this email is to get everyone on the same page so we are > all aware of what is going on. As many of you are probably already aware, > Horizon is moving toward the plugin model for all of its dashboards > (including existing dashboards). This release cycle, we are aiming to move > Sahara and Trove into their own repository with joint ownership of the > respective project. I have spoken to interested parties, Craig, and David > about it and we are all in agreement. Ideally, this should help speed up the > review process for Trove, as you now own part of the code and ownership. > > Horizon still have some things we need to tidy up on our end to make sure we > have full support for testing and localization for external plugins. We > expect this to get resolve within the next few weeks. Work on excising the > Trove code will begin this week so expect a patch for that soon! It would be > ideal if we can merge existing Trove code before the excision happens. David > has agreed to let these patches merge with one core vote if we have enough > Trovers reviewing/reverifying them. So please help us help you. > > David and Craig, if I left anything else out, feel free add to this. > Otherwise, have a good xmas everyone. Looking to working with you all in the > coming weeks. > > Regard, > Thai (tqtran) > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >

2 1

What's Up, Doc? 19 Feb 2016
by Lana Brindley 19 Feb '16

19 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, This week I've been focusing on general housekeeping duties as we prepare to rush headlong into the release. I've cleaned up the blueprints list, and also been burning through the oldest bugs in our queue. I'm very pleased to report that the overall number of bugs has reduced dramatically in the past month or two, and the number of untriaged bugs is holding steady at a much lower rate than previously. I think this probably has a lot to do with the DocImpact changes we made at the beginning of the year, so it's very gratifying to see some solid improvement starting to filter through. In other news, thanks to all those people who helped us with locating pre-release packages for the Install Guide. Please feel free to begin testing! The more people we have testing, the better and more accurate our docs will be, which helps everyone. == Progress towards Mitaka == 47 days to go! 417 bugs closed so far for this release. There is a global bug smash event coming up March 7-9 to try and hit as many Mitaka bugs as possible. You can join an in-person group near you, or participate remotely. There are still plenty of docs bugs that can be attended to. Details here: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka Docs Testing * Volunteers required! * https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting RST Conversions * All planned RST conversions are now complete! Reorganisations * Arch Guide: really needs a last minute push to get this complete before Mitaka. If you can help out, it would be greatly appreciated! ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * User Guides ** https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… ** Contact the User Guide Speciality team: https://wiki.openstack.org/wiki/User_Guides DocImpact * Is now complete == The Road to Austin == * ATC passes are going out now, so keep an eye on your inbox for your discount code if you haven't received yours yet. * Talk voting is now closed * 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''' Testing Mitaka milestone 3 using RDO packages and submitting patches for review. Lead of the install guide changed from Christian Berendt to Matt Kassawara. '''Networking Guide - Edgar Magana''' No update this week. '''Security Guide - Nathaniel Dillon''' No update this week. '''User Guides - Joseph Robinson''' The new User Guide team meetings are a success. We now have more contributors, and are discussing doc editing, new content, and Information Architecture of the User Guides. '''Ops and Arch Guides - Shilla Saebi''' Architecture guide reorganization is underway. We have a drafts repo in openstack-manuals, feel free to ping Shilla or Darren Chan if you are interested in helping out. Considering doing a swarm or work session at the summit in Austin for the Arch guide. Operations guide RST migration pending - conversations still happening to see which route we'll take. Still deciding if the ops guide should have another revision or edition, see ML e-mails. Call for volunteers email went out to the ops and docs ML from Devon Boatwright. We are looking for help! There is a global OpenStack bug smash scheduled for the Mitaka release in March. Details can be found here: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka We're looking for people to specifically help with the Architecture Guide, which is currently going through a reorganization. Here is the link for more details: https://wiki.openstack.org/wiki/Architecture_Design_Guide_work_items If you are interested in helping out, more detail s can be found about our team and our meetings here: https://wiki.openstack.org/wiki/Documentation/OpsGuide '''API Docs - Anne Gentle''' http://lists.openstack.org/pipermail/openstack-docs/2016-February/008286.ht… Swagger files now available at http://developer.openstack.org/draft/swagger/ '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Pranav Salunke, Roger Luethi''' Fixing various things in training-labs cluster for VirtualBox and KVM backends. Improving workflow, configuration and making the library scripts nicer. Adding training-labs landing page (WIP). Summit related work. Some minor improvements. '''Training Guides - Matjaz Pancur''' No update this week. '''Hypervisor Tuning Guide - Joe Topjian''' No update this week. '''UX/UI Docs Guidelines - Linette Williams''' Enhancement to UI content guidelines underway. Expect a new review shortly that covers icons and text formatting. If interested or have questions, contact Linette or Piet Kruithof. == 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-02-14 Next meetings: APAC: Wednesday 24 February, 00:30 UTC US: Wednesday 2 March, 14: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… Note that there is currently discussion about moving the US meeting to 20:00 UTC. A patch is open to change this, with ongoing discussion about finding a meeting room: https://review.openstack.org/#/c/271361/ - -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#19_February_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/ iQEcBAEBCAAGBQJWxpUQAAoJELppzVb4+KUyM5IIAKXT4U1SDq8K1+3u41qchjRe tXx3DCHp+O70krBFP+b6xaYXsuIwd6G4iroUXtl0RodlNAxdBjFf82fnpTlt/sz9 tjlST4nt/Z93shaA5b0AkOzEKJhoHCyH0ucq2GCQ81P5mEM3ZkFOYsEjdQjckPhu fc8yvbgjo1Dvxjk6/bEV6c1hroEqLVrzhpd9jstefA/1ATTCg3hR/IWQ9cXscMn0 8qutBYibhFcXzcCVj4/aafjUH+1punMgGeb2KcjrmA0z345WcmS4+IWR4NZrCiMg WWEKbFT8MvGuLEU79KNs+cZBWA+TQnlD2d1fsuCHFKU/eqFeyPmc3P/tI9YM7Jo= =2AkG -----END PGP SIGNATURE-----

1 0

Re: [Openstack-i18n] [stable][i18n] What is the backport policy on i18n changes?
by Kato, Tomoyuki 18 Feb '16

18 Feb '16

> hmm, I think the policy should depends on projects. > For projects which don't have active translations, I think it's OK to backport. > For projects which have active translations, "Exception procedure" of StringFreeze could help. > Translators need to be notified for the changes. > > If you don't know whether the project has active translations or not, > "Exception procedure" can help, anyway. +1 KATO Tomoyuki > Best regards > Ying Chun Guo (Daisy) > > > Matt Riedemann <mriedem(a)linux.vnet.ibm.com> wrote on 2016/02/18 08:16:26: > > > From: Matt Riedemann <mriedem(a)linux.vnet.ibm.com> > > To: "OpenStack Development Mailing List (not for usage questions)" > > <openstack-dev(a)lists.openstack.org>, openstack-i18n(a)lists.openstack.org > > Date: 2016/02/18 08:18 > > Subject: [Openstack-i18n] [stable][i18n] What is the backport policy > > on i18n changes? > > > > I don't think we have an official policy for stable backports with > > respect to translatable string changes. > > > > I'm looking at a release request for ironic-inspector on stable/liberty > > [1] and one of the changes in that has translatable string changes to > > user-facing error messages [2]. > > > > mrunge brought up this issue in the stable team meeting this week also > > since Horizon has to be extra careful about backporting changes with > > translatable string changes. > > > > I think on the server side, if they are changes that just go in the > > logs, it's not a huge issue. But for user facing changes, should we > > treat those like StringFreeze [3]? Or only if the stable branches for > > the given project aren't getting translation updates? I know the server > > projects (at least nova) is still get translation updates on > > stable/liberty so if we do backport changes with translatable string > > updates, they aren't getting updated in stable. I don't see anything > > like that happening for ironic-inspector on stable/liberty though. > > > > Thoughts? > > > > [1] https://review.openstack.org/#/c/279515/ > > [2] https://review.openstack.org/#/c/279071/1/ironic_inspector/process.py > > [3] https://wiki.openstack.org/wiki/StringFreeze

1 0

[stable][i18n] What is the backport policy on i18n changes?
by Matt Riedemann 18 Feb '16

18 Feb '16

I don't think we have an official policy for stable backports with respect to translatable string changes. I'm looking at a release request for ironic-inspector on stable/liberty [1] and one of the changes in that has translatable string changes to user-facing error messages [2]. mrunge brought up this issue in the stable team meeting this week also since Horizon has to be extra careful about backporting changes with translatable string changes. I think on the server side, if they are changes that just go in the logs, it's not a huge issue. But for user facing changes, should we treat those like StringFreeze [3]? Or only if the stable branches for the given project aren't getting translation updates? I know the server projects (at least nova) is still get translation updates on stable/liberty so if we do backport changes with translatable string updates, they aren't getting updated in stable. I don't see anything like that happening for ironic-inspector on stable/liberty though. Thoughts? [1] https://review.openstack.org/#/c/279515/ [2] https://review.openstack.org/#/c/279071/1/ironic_inspector/process.py [3] https://wiki.openstack.org/wiki/StringFreeze -- Thanks, Matt Riedemann

3 2

IRC meeting today
by Ying Chun Guo 18 Feb '16

18 Feb '16

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

1 0

Zanata 3.8 available
by Carlos Munoz 15 Feb '16

15 Feb '16

Hi All, Just a heads-up that Zanata 3.8.2 has been released and is ready for installation (See: https://github.com/zanata/zanata-server/releases) Please let us know if you want to do the upgrade and need any assistance. Regards, Carlos -- Carlos A. Muñoz Software Engineering Supervisor Globalization Red Hat

6 8