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

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

12 Oct '16

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

4 7

First translated releasenotes up
by Andreas Jaeger 11 Oct '16

11 Oct '16

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

2 2

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

07 Oct '16

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

1 0

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

07 Oct '16

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

6 7

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

07 Oct '16

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

4 6

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

06 Oct '16

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

4 4

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

05 Oct '16

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

2 1

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

04 Oct '16

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

4 3

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

03 Oct '16

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

1 0

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

03 Oct '16

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

3 2