February 2016 - OpenStack-I18n - lists.openstack.org

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

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

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 25 Feb '16

25 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