April 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

Release notes translation
by Ying Chun Guo 05 Jul '16

05 Jul '16

Hello, team Release notes[1] are published. I know our tools don't support release notes at present. I have gotten requests from Chinese team to translate release notes. Any suggestions to do that? Surely we can download and translate offline. One more question is where we should put the translated release notes. I hope to get some inputs from other language teams who want to translate release notes. Thank you. Best regards Ying Chun Guo (Daisy) [1] http://releases.openstack.org/mitaka/index.html

9 9

pot files in git trees?
by Andreas Jaeger 07 May '16

07 May '16

Looking at the daily imports we do for our translations, a lot of that is importing pot files (translation source). Do we really need these for anything in the git trees? We've stopped importing those pot files which are not translated at all but import pot files that have translations and update them daily (only if there are real translations as well). I really wonder whether we need these pot files in our git repositories at all, 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

5 14

FW: [Bug 1573514] [NEW] Typos in Italian Mitaka translation
by Kato, Tomoyuki 22 Apr '16

22 Apr '16

Hi Italian team, KATO Tomoyuki > -----Original Message----- > Title: > Typos in Italian Mitaka translation > > Status in openstack i18n: > New > > Bug description: > Zanata proposed another update for mitaka neutron Italian translation: > https://review.openstack.org/#/c/309280/ > > There are several concerns I have here. > > First, it seems that the change has some typos (e.g. using a ¥ character while the language does not use it at all). > Second, the change removes authorship for multiple contributors. I suspect it's not expected.

2 1

Re: [OpenStack-I18n] IRC meeting this week
by Kato, Tomoyuki 21 Apr '16

21 Apr '16

> Thank you, Kato-san. > I'm not able to attend the meeting this time because of a conflict. > I have added some topics to austin-i18n-workshop. quick short response. > In total we have 2 i18n related sessions, 40-minute austin-i18n-workshop 90-minutes, isn't it? https://www.openstack.org/summit/austin-2016/summit-schedule/events/7707 Kato > and a half day austin-i18n-meetup. > I see there are a long list of topics in austin-i18n-workshop. > I suggest we move some topics to austin-i18n-meetup in order to have > thorough discussions for every topic. > Maybe we move glossary and bug management discussions to > austin-i18n-meetup. > And in austin-i18n-workshop, we focus on Zanata, translation check website > and stackalytics. > > Best regards > Ying Chun Guo (Daisy) > > > "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> wrote on 04/19/2016 > 11:12:05 AM: > > > From: "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> > > To: "'openstack-i18n(a)lists.openstack.org'" <openstack- > > i18n(a)lists.openstack.org> > > Date: 04/19/2016 11:14 AM > > Subject: [OpenStack-I18n] IRC meeting this week > > > > Hi team > > > > We will have IRC meeting at UTC 13:00 UTC Thursday in > #openstack-meeting. > > > > The agenda is > > > > * Summit Planning > > - https://etherpad.openstack.org/p/austin-i18n-workshop > > - https://etherpad.openstack.org/p/austin-i18n-meetup > > > > If you have more topics, feel free to email. > > > > Regards, > > KATO Tomoyuki (katomo) > > > > _______________________________________________ > > OpenStack-I18n mailing list > > OpenStack-I18n(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > >

2 1

IRC meeting this week
by Kato, Tomoyuki 19 Apr '16

19 Apr '16

Hi team We will have IRC meeting at UTC 13:00 UTC Thursday in #openstack-meeting. The agenda is * Summit Planning - https://etherpad.openstack.org/p/austin-i18n-workshop - https://etherpad.openstack.org/p/austin-i18n-meetup If you have more topics, feel free to email. Regards, KATO Tomoyuki (katomo)

2 1

translation syncronization disabled due to broken Babel release
by Andreas Jaeger 17 Apr '16

17 Apr '16

A heads up and a request for advise: Babel 2.3.3 release broke extraction of log level messages from strings and extracted instead of e.g. "_LW" the default "_". So, the proposal job removed all content for that. Fortunately, Zanata will keep the strings, so once an upload with a fixed Babel happens, this should be fine again. See https://review.openstack.org/#/c/304985/ for one example - the error manifests with all pot files having exactly the same content. But I wanted to be safe and since babel 2.3.2 broke horizon and now 2.3.3 breaks python projects, I have - as teemporary measure - disabled translation sync completely to buy us time to evaluate what to do. There's a requirements change to update versions (blocking all broken babel releases): https://review.openstack.org/#/c/305000 Upstream bug report https://github.com/python-babel/babel/issues/388 And one way of working around it the bug is not using "python setup.py" but "pybabel" directly for python projects - like we do for django already. This needs testing and review - and some updates (see review comment): https://review.openstack.org/305043 We can also wait for Babel 2.3.4 release - and test first that it works as desired. Advise on which way to go forward as well as testing and review of 305043 are welcome! 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 3

技术因素 in OpenStack 架构设计指南 - 当前最新
by KATO Tomoyuki 16 Apr '16

16 Apr '16

Hi Chinese team, Please take a look at: https://bugs.launchpad.net/openstack-i18n/+bug/1571100 Kato

1 0

Renaming of resources
by Andreas Jaeger 13 Apr '16

13 Apr '16

I propose to change the setting of the locale source dir from "$module/locale" to "." for all projects to have this consistent. This will change the names of all resources since those are relative to the locale source dir. This will enable us to translate release notes using Zanata for the python projects. This is only relevant for python projects - not for documentation ones or for Django based projects since those already use "." as source directory. This implies a scripting change as well as a manual copying translation files around. I'm willing to do both later this week. My proposal would be to only do this for *master* but not for stable/mitaka, I don't want to risk anything on that branch. Everybody ok with this? Or has anybody concerns and suggestions? 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

4 6

Re: [OpenStack-I18n] Renaming of resources
by Andreas Jaeger 12 Apr '16

12 Apr '16

On 2016-04-12 12:03, Ying Chun Guo wrote: > Hi, Andreas > > Just release Horizon project have two pairs of resources with same name: > django and djangojs. And that will not change, they will stay the same. > Will they have both the same name and same location after changing ? Yes, as the new setup is exactly the setup that horizon has. > Is there a way to separate them from the web UI after changing? > See: > https://translate.openstack.org/iteration/view/horizon/master/documents I think that is clear, it gives name and path now, 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

1 0

Re: [OpenStack-I18n] Renaming of resources
by Andreas Jaeger 12 Apr '16

12 Apr '16

On 2016-04-12 11:08, Ying Chun Guo wrote: > Hi, Andreas > > Do you mean to move the *.pot files from "$module/locale" to the root > folder of module ( or the root folder of project ) ? Will you move > translation files in language folders ? Only the name in Zanata is changed, see "Translation script challenges" as well. The files will stay the same in the repositories. But the parameter we give zanata is different and thus the files in Zanata are renamed. > The purpose of this change is to support release notes translation, right > ? Yes. Also, it avoids problems like we had with keystone (see above referenced email for full details), Andreas > Best regards > Ying Chun Guo (Daisy) > > > Andreas Jaeger <aj(a)suse.com> wrote on 04/12/2016 02:56:34 PM: > >> From: Andreas Jaeger <aj(a)suse.com> >> To: "openstack-i18n(a)lists.openstack.org" > <openstack-i18n(a)lists.openstack.org> >> Date: 04/12/2016 02:58 PM >> Subject: [OpenStack-I18n] Renaming of resources >> >> I propose to change the setting of the locale source dir from >> "$module/locale" to "." for all projects to have this consistent. This >> will change the names of all resources since those are relative to the >> locale source dir. This will enable us to translate release notes using >> Zanata for the python projects. >> >> This is only relevant for python projects - not for documentation ones >> or for Django based projects since those already use "." as source >> directory. >> >> This implies a scripting change as well as a manual copying translation >> files around. I'm willing to do both later this week. >> >> My proposal would be to only do this for *master* but not for >> stable/mitaka, I don't want to risk anything on that branch. >> >> Everybody ok with this? Or has anybody concerns and suggestions? >> >> 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

3 2

Translation script challenges
by Andreas Jaeger 12 Apr '16

12 Apr '16

I think this is mainly of interest to KATO-san, Akihiro-san, Alex, and infra folks but wanted to send it here to have it recorded. This is about the scripting we use in project-config to push content to zanata. I just did two changes to fix problems I noticed with release notes translation and with python projects that use more than one module (keystone): https://review.openstack.org/303727 https://review.openstack.org/303722 But now I see have another problem: Since keystone went from one to two modules, the srcdir setting changed and thus it's not anymore keystone but keystone/locale/keystone as resource name. Compare: https://translate.openstack.org/iteration/view/keystone/master/documents https://translate.openstack.org/iteration/view/keystone/stable-mitaka/docum… The rename deleted the old content and created new files ;( We can fix this with downloading the translation of mitaka files and pushing them to master. But this will hit us every time a project moves from one to multiple modules. Now, checking releasenotes push for python projects: It still does not work due to the ../.. zanata-cli does not see files outside of the srcdir. For reference: We need to push nova/locale/nova.pot and releasenotes/locale/releasenotes.pot zanata.xml contains: <rules> <rule pattern="**/*.pot">{locale_with_underscore}/LC_MESSAGES/{filename}.po</rule> <rule pattern="../../releasenotes/source/locale/releasenotes.pot">../../releasenotes/source/locale/{locale_with_underscore}/LC_MESSAGES/releasenotes.po</rule> </rules> So, I'm proposing to set sourcedir and transdir *everywhere* to "." instead of "$module/locale" - like done for multiple modules: <rules> <rule pattern="**/*.pot">{path}/{locale_with_underscore}/LC_MESSAGES/{filename}.po</rule> <rule pattern="releasenotes/source/locale/releasenotes.pot">releasenotes/source/locale/{locale_with_underscore}/LC_MESSAGES/releasenotes.po</rule> </rules> Does anybody have a better idea on how to fix these two problems? Or a better way to write the rules above for this? Alex, is there a way to not lose the content when this change is done since it will rename the translation files? 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

3 5

RFC: Zanata enhancement
by Kato, Tomoyuki 12 Apr '16

12 Apr '16

Hi team, I'd like to collect Zanata enhancement requests. I believe Zanata enhancement improve your work effciency, as translator, coordinator, or infra engineer... Please feel free to write your requests. https://etherpad.openstack.org/p/I18n-Zanata-enhancement I have a chance to talk with Alex, Zanata dev team, at Austin Summit. Unfortunately, we don't have enough official session slot, but we will talk at somewhere. Also, everyone is welcome to join us. Exact date and location are to be determined. I'll email details around summit. Thanks, KATO Tomoyuki

1 0

Approval
by Remo Mattei 12 Apr '16

12 Apr '16

hello all, what is the process to approve a new translation? Thanks

2 1

today's horizon import puzzles me...
by Andreas Jaeger 11 Apr '16

11 Apr '16

Could somebody closely review today's horizon translation import, please? I'm surprised by the deletions but couldn't find an error with them either: https://review.openstack.org/#/c/303807/ 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

3 4

Fw: [openstack-announce] OpenStack Mitaka is officially released!
by KATO Tomoyuki 10 Apr '16

10 Apr '16

Hi team, OpenStack Mitaka was officially released. Congratulations! Also, it's time to take over the PTL role from Daisy to me. Again, I appreciate all your work, Daisy. Sincerely. KATO Tomoyuki ----------------------- Original Message ----------------------- Hello OpenStack community, I'm excited to announce the final releases for the components of OpenStack Mitaka, which conclude the 6-month Mitaka development cycle. You will find a complete list of all components, their latest versions, and links to individual project release notes documents listed on the new release site: http://releases.openstack.org/mitaka/ Congratulations to all of the teams who have contributed to this release! I also want to extend a big thank you to AJAeger and jhesketh for their help with build issues today, and to ttx and dims for their help with release work all this cycle and especially over the last couple of weeks. Thank you! Our next production cycle, Newton, has already started. We will meet in Austin April 25-29 at the Newton Design Summit to plan the work for the upcoming cycle. I hope to see you there! Doug

2 1

IRC meeting tomorrow
by Ying Chun Guo 07 Apr '16

07 Apr '16

Hi, team We will have IRC meeting tomorrow at UTC 0600 in #openstack-meeting. The agenda is - Summary of Mitaka translation - New translation priorities - Continued discussion about glossary management If you have more topics, feel free to add. Best regards Ying Chun Guo (Daisy)

3 2

Re: [OpenStack-I18n] Opening master again?
by Andreas Jaeger 04 Apr '16

04 Apr '16

Daisy, KATO, could either of you update the translate.openstack.org main page, please? The mitaka translation period is over according to it, 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

Re: [OpenStack-I18n] Opening master again?
by Andreas Jaeger 04 Apr '16

04 Apr '16

On 2016-04-04 03:28, Ying Chun Guo wrote: > Agree to open master again. > We will keep both master and stable open for a period, till string freeze > of next release. OK, I'll open up master now and merge content to master as well, 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

1 0

Opening master again?
by Andreas Jaeger 04 Apr '16

04 Apr '16

The translations have merged for mitaka, latest import was on Wednesday (30th) and for some even on Thursday - so some extra days after official end of the 28th. The last RC has been cut for all projects. I've seen an impressive amount of changes coming in, thanks! Any new translations will go into the first stable release unless a project needs an extra RC and takes in translations as well. Last time we made at this time the master branch writeable again and merged the stable branch translations to master - and left the stable branches open for further submissions. So, time to do this again now? That means translations on both master and stable can happen going forward, 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

3 2

stable/liberty version fo Zanata networking-guide
by Akihiro Motoki 03 Apr '16

03 Apr '16

Hi, networking-guide in openstack-manuals is now versioned. Can we have a stable-liberty version for networking-guide on Zanata? Akihiro

4 4

Austin Design Summit track layout
by Kato, Tomoyuki 01 Apr '16

01 Apr '16

Hi team, Austin Design Summit track layout is announced. http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html I18n team has a contributor meetup at Friday. I'm looking forward to meet many people. Thank you to coodinate, Daisy. Thanks, KATO Tomoyuki

6 5

Strange projects on translate.openstack.org
by Andreas Jaeger 01 Apr '16

01 Apr '16

Hi, does anybody know what these are? https://translate.openstack.org/project/view/swift-italian/ https://translate.openstack.org/project/view/tempest https://translate.openstack.org/project/view/test-json-md IMHO we should not add new projects that are manually translated - instead let's integrate them in the usual toolchain. Also, why do these have some projects separate maintainers? We don't need them IMHO at all. I propose to delete them. Going forward, I suggest that any new projects outside of the usual process get discussed on the openstack-i18n mailing list, so that we know what's going on. Can we also document the reason for them somewhere? 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

5 6

What's Up, Doc? Mitaka Release Edition
by Lana Brindley 01 Apr '16

01 Apr '16

Hi everyone, While it was very tempting to write something something shocking here for April Fools', I thought everyone might have already had their heart rate raised enough by the fact that Mitaka is only five days away! This will be my final docs newsletter before the release, and the docs are in great shape ready to go out. I would like to sincerely thank Andreas and our release managers Brian and Olga, not only for the hard work they've done so far, but also for holding down the fort over the next few days while I'm out of contact. Please remember to contact them directly if you have any last minute documentation fires that need putting out. I'd also like to mention the hard work that the Installation Guide testers have been putting in over the past couple of weeks. The testing matrix is looking very green (https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting) and I'm confident that we'll get the Mitaka guide out fully tested and on schedule. Don't forget you can check release progress on the etherpad here: https://etherpad.openstack.org/p/MitakaRelease == Progress towards Mitaka == 5 days to go! 558 bugs closed so far for this release. Docs Testing * https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting * Only a few items left to check off, at this stage we're good to publish the Ubuntu, RDO, and Suse guides on release day. Release Tasks: * Release planning occurs in our etherpad here: https://etherpad.openstack.org/p/MitakaRelease * All tasks that should be completed at this stage are done, and we're on track to start the release process in the 24-48 hours before the release drops. * Release notes for the docs project are in a "reno-style" directory in the openstack-manuals repo. This directory is not being managed by Reno, however, so please propose patches to it directly. == The Road to Austin == * First of all, thanks for the amazing feedback on what docs sessions you would like to see at the Austin Design Summit! We have filled our entire allocation (and then some), and the schedule so far is here: https://etherpad.openstack.org/p/Newton-DocsSessions * There's been a really robust and exciting conversation about the Install Guide on the dev list over the past week or so, which I have been following closely. If you're interested in overhauling our Install Guide (and it certainly seems like a lot of people are!), then please make sure you add our Install Guide Design Summit session to your agenda. It is on Wednesday at 11:50, so placed so that it can run over into lunchtime if required. * A note for those who noticed the Ops guide omission: this should take place in the Ops track, and I'll let you know when that session will be. == 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-03-30 Next meetings: APAC: No APAC meeting this week US: Wednesday 13 April, 19:00 UTC (This is after the Mitaka release) 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#1_April_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0