- OpenStack-I18n - lists.openstack.org

IRC meeting tomorrow
by Ying Chun Guo 03 Mar '16

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