- OpenStack-I18n - lists.openstack.org

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

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

23 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 19 Feb '16

19 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 18 Feb '16

18 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 17 Feb '16

17 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 14 Feb '16

14 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