- OpenStack-I18n - lists.openstack.org

What's Up, Doc? 25 September 2015
by Lana Brindley 25 Sep '15

25 Sep '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, First of all, thank you to everyone who has suggested sessions for docs at Tokyo. I'll keep the etherpad open for another week or so, just to give everyone a chance, and will start working on a draft schedule next week. I have spent most of this week on bug triage, which is repetitive work, but it's gratifying to see the numbers drop a little! == Progress towards Liberty == 19 days to go 534 bugs closed so far for this release. The main areas of focus we had during Liberty were the RST migration, paying down some of our technical debt, and improving our general communication issues. The RST conversion is well and truly complete, with just a couple of books waiting in the wings to be published. We have made some progress on improving our communication generally, with liaisons now more visible and involved, and some improved processes. Regarding old bugs, during Liberty we spotlighted a total of 24 bugs, exactly half of which have now been closed. == Mitaka Summit Prep == The schedule app for your phone is now available. This is a great tool once you're on the ground at Summit: https://itunes.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=98721 6292&mt=8 (Apple) and https://play.google.com/store/apps/details?id=org.sched.openstacksummitm ay2015vancouver (Android) Docs have been allocated two fishbowls, four workrooms, and a half day meetup, so now is the time to start gathering ideas for what you would like to see us cover. Add your ideas to the etherpad here: https://etherpad.openstack.org/p/Tokyo-DocsSessions I'll create a draft session based on this feedback next week. == Bug Triage Process == The core team have been noticing a lot of people trying to close bugs that haven't been triaged recently. It is very important that you have someone else confirm your bug before you go ahead and create a patch. Waiting just a little while for triage can save you (and our core team!) a lot of work, and makes sure we don't let wayward changes past the gate. If you're unsure about whether you need to wait or not, or if you're in a hurry to work on a bug, you can always ping one of the core team on IRC or on our mailing list. The core team members are listed here, and we're always happy to help you out with a bug or a patch: https://launchpad.net/~openstack-doc-core This is even more important than usual as we get closer to the Liberty release, so remember: If it's not triaged, don't fix it! == Spotlight Bugs == During Liberty we spotlighted a total of 24 bugs, exactly half of which have now been closed. This is a great effort to clear out some old dusty bugs and pay down some technical debt. Thanks go out to Tom Fifield, Olga Gusarenko, Yusuke Ide, Brian Moss, Deena Cooper, and Alexandra Settle for taking them on! With Liberty and the Summit bearing down on us, though, let's focus back on what needs to be done for release. At Summit, we'll discuss how to expand and improve on this effort in future releases. == Doc team meeting == The US meeting was held this week. The minutes are here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-09-23 The next meetings will be the final meetings before the Liberty release: APAC: Wednesday 30 September, 00:30:00 UTC US: Wednesday 7 October, 14:00: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_ meeting - -- Remember, if you have content you would like to add to this newsletter, or you would like to be added to the distribution list, please email me directly at openstack(a)lanabrindley.com, or visit: https://wiki.openstack.org/w/index.php?title=Documentation/WhatsUpDoc Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJWBNTTAAoJELppzVb4+KUyW6EH/2kYOYHa2DHfHJxN2XC1QcpD L3wwDWxu9B2G6M/hNzRJ/KELSVikfuK9+ChOA+kD2kXLs6dV1oLXXCbV2KIdHKWP +EYPG0G/CsMkoq8KIfzYwW6c2k+RzSXZAnI1ZhcRJiwhlIC5JlSZ118Y64GeLxmB jISEqsi7WdK76caMmEy+3+QrpBY/WNOVE5Dyu0TiwGTPtU1EuZEAXHkdFjczKEKM azlyyFIF4V28+BjrZpUybarEL2hZerHt2XiNd5dCRoQgE7b8ubJ0cidErPazI9AV mZNZO3VtLTfSC2ytNBwIBaN3ezJzC5mvba6ofDdej3jIvZf3o6IQihbMaYWyLDI= =uZBu -----END PGP SIGNATURE-----

1 0

translating python clients
by Andreas Jaeger 25 Sep '15

25 Sep '15

We now have setup python-keystoneclient for translation and there're requests for python-heatclient and python-novaclient (https://review.openstack.org/224832 heat and https://review.openstack.org/224222 nova) Does it really make sense to translate these? Especially with the openstack client getting translated already? My proposal would be to concentrate on the openstack client and tell the teams to not mark the clients for translation. What do you think? Please see also http://lists.openstack.org/pipermail/openstack-dev/2015-September/073698.ht… 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 11

stable-liberty is created for nova project
by Ying Chun Guo 24 Sep '15

24 Sep '15

Hi, translation team Nova has its RC1 cut yesterday. Hard string freeze is happened. I have created the corresponding version for liberty in Zanata. The version name is stable-liberty. So from now on, all translations/review should be made in the stable-liberty version. The master version is set "Read Only" and will be open to accept translations after Liberty is done. Any problems, please let me know. Best regards Ying Chun Guo (Daisy)

1 0

Re: [Openstack-i18n] Would like Zanata branch to correct 1494819
by Douglas Fish 24 Sep '15

24 Sep '15

1 0

Re: [Openstack-i18n] Would like Zanata branch to correct 1494819
by Ying Chun Guo 24 Sep '15

24 Sep '15

Thank you for looking into it, Illya. I think we need to fix it, although the manually process might be a little complex. I'm going to: 1. Create a new version in Zanata 2. Mark master as read only 2. Pull the source files and the translation files. 3. Change the pluralities settings in Russian translation files. 4. Upload the source files and translation files to the new version. 5. Check if the all things are right, change master version name to "master-old", and then change the new version name to "master" How do you want to update these pluralities then? By program ? Or manually ? Is it possible to make the changes through Zanata UI, other than uploading po files ? Best regards Ying Chun Guo (Daisy) Douglas Fish/Rochester/IBM wrote on 09/23/2015 04:38:19 AM: > From: Douglas Fish/Rochester/IBM@IBMUS > To: ilyaalekseyev(a)acm.org > Cc: guoyingc(a)cn.ibm.com, openstack-i18n(a)lists.openstack.org > Date: 09/23/2015 04:38 AM > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > Hi Ilya, > > Thanks for looking at this! Unfortunately having 4 pluralities > confuses Horizon. I've tested out stripping one of the pluralities > and restoring the expected Plural-forms definition (just like the > one you linked) and it works great. > > I had hoped to just repair the PO files in this way and upload the > corrected translations to Zanata. > > Unfortunately, I understand from Daisy's research that once a > language/project has been created in Zanata in this way we cannot > just upload a PO file with corrected pluralities . More > investigation will be needed to understand the process to fix this. > > Doug > > > ----- Original message ----- > From: Ilya Alekseyev <ilyaalekseyev(a)acm.org> > Sent by: ilya(a)phpcoder.ru > To: Douglas Fish/Rochester/IBM@IBMUS > Cc: Ying Chun Guo <guoyingc(a)cn.ibm.com>, "openstack- > i18n(a)lists.openstack.org" <openstack-i18n(a)lists.openstack.org> > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > Date: Tue, Sep 22, 2015 2:39 PM > > Hi Doug and Daisy! > > Looks like we have wrong pluralities in current release: > in https://github.com/openstack/horizon/blob/master/ > openstack_dashboard/locale/ru/LC_MESSAGES/django.po > > we have: > "Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n" > "%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n" > "%100>=11 && n%100<=14)? 2 : 3);\n" > > but in previuos releses we have: > "Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n% > 10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" > > Last one is right for Russian. > > We can make translation in Zanata for 4 pluralities, but it can give > in some cases bugs with wrong plural forms. > > Kind regards, > Ilya Alekseyev. > > 2015-09-22 14:22 GMT+03:00 Douglas Fish <drfish(a)us.ibm.com>: > Hi Daisy, > > I am certain this issue is caused by plural forms. The issue with > missing menus is seen with the current 4 plural form translations; > when I correct the PO file to have 3 forms Horizon properly displaysthe menus. > > Doug > > > ----- Original message ----- > From: Ying Chun Guo/China/IBM > To: Douglas Fish/Rochester/IBM@IBMUS@IBMAU > Cc: openstack-i18n(a)lists.openstack.org > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > Date: Tue, Sep 22, 2015 12:49 AM > > Hi, Doug > > We need to consider it carefully. > > After working with Zanata dev team, I got to understand: > > 1. Zanata has its own plural forms. If po file has its own plural > form, Zanata will use that. > Otherwise, Zanata will use its own plural form. Pluralforms in Zanata: > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && > (n%100<10 || n%100>=20) ? 1 : 2). > So it looks like that OpenStack po files overrode the pluralforms in Zanata. > > 2. Zanata currently don't allow update of plural forms once the > document has been uploaded to Zanata. > Even with deletion of that source document and re-upload (in the > same project-version, same doc name and same path), > Zanata will still reuse the old pluralform. > > 3. If we want to update the pluralforms, we will need to do it in > new project-version > (don't use copy-from previous version function). > > I think we need to carefully design the steps to change pluralforms > of Russian. > At first, I want to confirm with you, are you sure this issue is > caused by plural forms? > > Best regards > Ying Chun Guo (Daisy) > > > Douglas Fish/Rochester/IBM wrote on 2015/09/18 23:38:22: > > > From: Douglas Fish/Rochester/IBM@IBMUS > > To: guoyingc(a)cn.ibm.com > > Cc: openstack-i18n(a)lists.openstack.org > > Date: 2015/09/18 23:38 > > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > > > Hi Daisy, > > > > Yes, I understand - I don't think I can even propose my branch > > unless I am added as a translator by the Russian team. > > > > My proposal would include removing one plural form for > > 4 messages in horizon django.po > > 1 message in horizon djangojs.po > > 144 messages in openstack_dashboard django.po > > 0 messages in openstack_dashboard djangojs.po > > plus the pluralization specification would be updated in all 4 files. > > > > Doug > > > > ----- Original message ----- > > From: Ying Chun Guo <guoyingc(a)cn.ibm.com> > > To: Douglas Fish/Rochester/IBM@IBMUS > > Cc: openstack-i18n(a)lists.openstack.org > > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > Date: Fri, Sep 18, 2015 3:25 AM > > > > Are there a lot of changes in your proposed po files ? > > I'm still waiting for Russian team's response. > > > > Best regards > > Ying Chun Guo (Daisy) > > > > > > "Douglas Fish" <drfish(a)us.ibm.com> wrote on 09/18/2015 05:37:07 AM: > > > > > From: "Douglas Fish" <drfish(a)us.ibm.com> > > > To: openstack-i18n(a)lists.openstack.org > > > Date: 09/18/2015 05:38 AM > > > Subject: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > > > > > Hi translation friends, > > > > > > I'd like to contribute 4 PO files for the Horizon Russian > > > translation to correct the issue > > > https://bugs.launchpad.net/openstack-i18n/+bug/1494819 > > > > > > These uploads won't contain any new translations, but instead will > > > be an adjustment to the PO files so they have 3 pluralities, which > > is standard > > > http://localization-guide.readthedocs.org/en/latest/l10n/pluralforms.html > > > > > > Specifically, I plan to remove the msgstr[2] translation from the > > > files (because msgstr[2] is blank for many cases), rename the msgstr > > > [3] translation to msgstr[2] and adjust the plurality specification to > > > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && > > > (n%100<10 || n%100>=20) ? 1 : 2); > > > > > > As discussed in the team meeting http://eavesdrop.openstack.org/ > > > meetings/openstack_i18n_meeting/2015/openstack_i18n_meeting. > > > 2015-09-17-13.00.log.html > > > please create a Zanata branch so I can propose these corrections > for review. > > > > > > Thanks! > > > > > > Doug > > > _______________________________________________ > > > 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 >

1 0

Re: [Openstack-i18n] IBM translations to contribute: update
by Ying Chun Guo 23 Sep '15

23 Sep '15

Hi, team I have made enough tests on the test server with the help from Doug and his colleagues. In the test server, I created versions for nova, glance, cinder, swift, ceilometer, heat, keystone, and ironic. Doug and his colleagues uploaded their po files for languages de, es, fr, it, ja ko-KR, pr-BR, ru, zh-CN, and zh-TW. I tested merging two versions. Things are running well. The test server is still in good condition. So there is no technical issues block me to do the same in the production server. I even tried "Group" in the test server. The "Group" feature looks wonderful. So if there is no objections, I will go to production server, doing the same as what I did in the test server. Best regards Ying Chun Guo (Daisy) Douglas Fish/Rochester/IBM wrote on 09/18/2015 05:14:22 AM: > From: Douglas Fish/Rochester/IBM@IBMUS > To: guoyingc(a)cn.ibm.com > Cc: openstack-i18n(a)lists.openstack.org > Date: 09/18/2015 05:14 AM > Subject: Re: [Openstack-i18n] IBM translations to contribute: update > > Hi Daisy, > > We have translations to contribute for ceilometer, cinder, glance, > heat, ironic, keystone, nova and swift for languages de, es, fr, it, > ja ko-KR, pr-BR, ru, zh-CN, and zh-TW > > We are working to upload those to the Zanata test server to make > sure there are no technical issues. > > Doug > > ----- Original message ----- > From: Ying Chun Guo <guoyingc(a)cn.ibm.com> > To: Douglas Fish/Rochester/IBM@IBMUS > Cc: "Openstack-i18n Openstack-i18n" <openstack-i18n(a)lists.openstack.org> > Subject: Re: [Openstack-i18n] IBM translations to contribute: update > Date: Thu, Sep 17, 2015 11:04 AM > > Hi Doug, Hi team, > > In today's IRC meeting, we talked about the process to get IBM translations. > I'm going to normalize the process to contribute translations by > uploading po files. > > Here are some key points during the meeting: > > 1. It is strongly discouraged to use the offline editor other than web tool. > Because the offline editor could not take the advantages of > translation memory and glossary, > which might affect the translation quality. > 2. Simply uploading po files are not allowed because it has a risk > that the po files might contain bad translations. > 3. In some special cases, if people who want to contribute > translations by uploading po files, following below steps > 3.1 Send email to I18n mailing list, describing the source > documents and languages he/she is going to upload. > 3.2 Zanata admin will create a branch. Then contributors could > upload po files to the proposed branch. > 3.3 When the uploading is done, language coordinators could > review the translations. > The coordinators could have two kinds of review results: > agree to merge or deny to merge. > If the coordinators deny to merge, coordinators should > give some comments, either to delete this branch, or to suggestions > to improve. > 3.4 If the coordinators agree to merge to the master branch, > Zanata admin will make the merge. > A option could set during the branches merging to make sure not > overwrite translated/approved translations in the source branch. > After merging, the proposed branch will be deleted. > > I have been testing branches in the Zanata test server for several days. > When I make sure it works fine, I will go to the production server. > > @Doug, please let us know which resources and which languages you > are going to propose ? > > Best regards > Ying Chun Guo (Daisy) > > > "Douglas Fish" <drfish(a)us.ibm.com> wrote on 09/16/2015 08:05:52 PM: > > > From: "Douglas Fish" <drfish(a)us.ibm.com> > > To: "Openstack-i18n Openstack-i18n" <openstack-i18n(a)lists.openstack.org> > > Date: 09/16/2015 08:06 PM > > Subject: [Openstack-i18n] IBM translations to contribute: update > > > > Here's the revised approach we are taking to contributing our IBM > > translations to the community, based on feedback on suggestions: > > > > We are planning to make the proposed translations available for a > > pre-review as a separate branch in Zanata, but they are not there > > yet. While testing out this upload on the development server we > > discovered that uploading PO files caused the server to become > > unresponsive for a while. Thanks to pleia2 and the infra team for > > sorting that out and addressing the issue. We'll try the upload on > > dev again tomorrow and if it goes well we will make the translations > > available for pre-review in a separate Zanata branch. > > > > I had originally proposed ending the pre-review on Monday. Obviously > > that's not going to happen! I understand that different language > > teams have differing levels of readiness to accept these > > contributions. I understand some groups are ready at this time, > > while others would like to have more time, possibly even into Mitaka > > to review. We aren't going to upload PO files for any language were > > the team does not want them. > > > > Language coordinators, please let me know how you'd like to proceed > > with these contributions for your language. Do you want > > 1) us to upload them to Zanata's current master translations for > > normal review and editing as soon as we can, > > 2) us to upload them to Zanata as a separate branch for further > pre-review, or > > 3) hold off any submission or preview at this time. > > > > Please note that it important to us that we upload these > > translations. The translations are a valued IBM asset, it's > > important to us that they are recognized as contributed by IBM. > > > > I'll be at the Thursday i18n team meeting, and am available by IRC > > (doug-fish) or email if you have questions or further concerns. > > > > Thanks! > > > > Doug_______________________________________________ > > Openstack-i18n mailing list > > Openstack-i18n(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

6 17

Arabic Script mixed with Gurmukhi Script in Translation Memory
by ਅਨਪੜ੍ਹ ਜਿਮੀਂਦਾਰ 23 Sep '15

23 Sep '15

Hi there, As I don't know how this mix up happened so someone please respond to this issue. After the migration has done and i am doing translation in Zanata I am quite surprised to see Arabic script in my Translation Memory of many projects. I have clarified before, and explaining again, that Punjabi has two entirely different scripts i.e. Gurmukhi (ਪੈਂਤੀ) and Shahmukhi (اردو), while former is widely used in Indian side of Punjab aka Eastern Punjab the latter is used in Pakistani side of Punjab aka Western Punjab. I guess while migration someone has mistaken both the scripts as one and joined them. As this is my assumption so it is you guys, will have to help me out. Thanks Amandeep Singh Saini Co-ordinator Punjabi Team (pa-IN)

3 5

Re: [Openstack-i18n] Russian translations with 4 pluralities?
by Douglas Fish 23 Sep '15

23 Sep '15

3 2

Re: [Openstack-i18n] Would like Zanata branch to correct 1494819
by Douglas Fish 23 Sep '15

23 Sep '15

2 2

Automatic copying of translations in Zanata?
by Andreas Jaeger 23 Sep '15

23 Sep '15

Today the majority of the IBM translations got merged into the the normal versions since zanata by default searches at every upload with the zanata client for translation of untranslated strings and merges them [1]. So, when ceilometer got uploaded as master version, the IBM ceilometer strings where searched for already translated strings and untranslated ceilometer strings where automatically translated with the IBM version. Daisy, Clark, Lyz, and myself just had some discussion on #openstack-i18n and decided to disable for now the automatic copying of translations while we discuss what to do next. The question for me is, do we want this kind of automatic copying of translations - and if, how do we want it. Previously enabled was copying only in a project between versions. So, for example if there is a stable/liberty and a master version (or an IBM and a master version) of the same document, and one contains a translated string and the other gets updated, the translated string gets copied over if the string is not translated yet. This feature can also be enabled for copying between projects and files. So, we could enable it and then when a string gets translated in let's say nova and exactly the same string is in neutron and untranslated, the translation would be copied from nova to neutron. So, question to discuss: 1) Do we translators want such automatic translations? 2) And if yes, only between: a) versions of same document b) inside a project (so, only inside nova) c) across all projects and documents Note that this setting is the same for all languages. Note that there's an option as well to do this automatic translation manually, for example at project creation time. So, if a new project gets setup, Zanata could try to copy automaticly translations across projects for a quick start. What do you think? Do you want to translate each string manually - or let Zanata do the work and to which extend? I hope I summarized everything correctly, if not please correct my understanding, Andreas References: [1] http://zanata.org/help/copytrans-explained/ -- 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

1 0

Please review IBM translations in the master branch
by Ying Chun Guo 23 Sep '15

23 Sep '15

Hi, friends Something unexpected happened tonight. IBM translations were copied into master branches. The copy action is triggered by uploading of pot files, which are executed by automatic Jenkins jobs when the source pot files in code repo are updated. Nobody expects it. Infrastructure team have figure out a way to stop auto copy while uploading pot files so this kind of things won't happen the second time. IBM translations only fill in blanks without overwriting the others. I hope translation teams could take a look at IBM translations in the master branches. IBM contributions could be located by searching "last-modified-after: 2015-09-21". You could * improve translations if they are easily to improve. Different terminologies could easily be fixed by "project-wide Search & Replace". ( in the Editor view, click the magnifying glass icon on the right top corner to open the search&replace view.) * reject some translations if you don't like. * If you don't like the whole translations at all, I may work out a way to revert it but it will cost time. The relevant translation teams include: de es fr it ja ko_KR pt_BR ru zh_CN zh_TW. The relevant documents are: nova.pot, glance.pot, swift.pot, ceilometer.pot, cinder.pot, heat.pot, ironic.pot, keystone.pot and neutron.pot. Sorry for the troubles and thank you for your work. Best regards Ying Chun Guo (Daisy)

1 0

IP capitalization change in nova - ok to merge?
by Andreas Jaeger 22 Sep '15

22 Sep '15

Translation team, I've just send a patch for review that fixes lots of user visible capitalization strings in nova as I noticed during translation that it should be "IP" and not "ip" for example in "fixed IP". Is it ok to get this patch in now - or should I wait after liberty and mark it as WIP for now? https://review.openstack.org/225923 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

2 1

Re: [Openstack-i18n] Would like Zanata branch to correct 1494819
by Ying Chun Guo 22 Sep '15

22 Sep '15

Hi, Doug We need to consider it carefully. After working with Zanata dev team, I got to understand: 1. Zanata has its own plural forms. If po file has its own plural form, Zanata will use that. Otherwise, Zanata will use its own plural form. Pluralforms in Zanata: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2). So it looks like that OpenStack po files overrode the pluralforms in Zanata. 2. Zanata currently don't allow update of plural forms once the document has been uploaded to Zanata. Even with deletion of that source document and re-upload (in the same project-version, same doc name and same path), Zanata will still reuse the old pluralform. 3. If we want to update the pluralforms, we will need to do it in new project-version (don't use copy-from previous version function). I think we need to carefully design the steps to change pluralforms of Russian. At first, I want to confirm with you, are you sure this issue is caused by plural forms? Best regards Ying Chun Guo (Daisy) Douglas Fish/Rochester/IBM wrote on 2015/09/18 23:38:22: > From: Douglas Fish/Rochester/IBM@IBMUS > To: guoyingc(a)cn.ibm.com > Cc: openstack-i18n(a)lists.openstack.org > Date: 2015/09/18 23:38 > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > Hi Daisy, > > Yes, I understand - I don't think I can even propose my branch > unless I am added as a translator by the Russian team. > > My proposal would include removing one plural form for > 4 messages in horizon django.po > 1 message in horizon djangojs.po > 144 messages in openstack_dashboard django.po > 0 messages in openstack_dashboard djangojs.po > plus the pluralization specification would be updated in all 4 files. > > Doug > > ----- Original message ----- > From: Ying Chun Guo <guoyingc(a)cn.ibm.com> > To: Douglas Fish/Rochester/IBM@IBMUS > Cc: openstack-i18n(a)lists.openstack.org > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > Date: Fri, Sep 18, 2015 3:25 AM > > Are there a lot of changes in your proposed po files ? > I'm still waiting for Russian team's response. > > Best regards > Ying Chun Guo (Daisy) > > > "Douglas Fish" <drfish(a)us.ibm.com> wrote on 09/18/2015 05:37:07 AM: > > > From: "Douglas Fish" <drfish(a)us.ibm.com> > > To: openstack-i18n(a)lists.openstack.org > > Date: 09/18/2015 05:38 AM > > Subject: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > > > Hi translation friends, > > > > I'd like to contribute 4 PO files for the Horizon Russian > > translation to correct the issue > > https://bugs.launchpad.net/openstack-i18n/+bug/1494819 > > > > These uploads won't contain any new translations, but instead will > > be an adjustment to the PO files so they have 3 pluralities, which > is standard > > http://localization-guide.readthedocs.org/en/latest/l10n/pluralforms.html > > > > Specifically, I plan to remove the msgstr[2] translation from the > > files (because msgstr[2] is blank for many cases), rename the msgstr > > [3] translation to msgstr[2] and adjust the plurality specification to > > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && > > (n%100<10 || n%100>=20) ? 1 : 2); > > > > As discussed in the team meeting http://eavesdrop.openstack.org/ > > meetings/openstack_i18n_meeting/2015/openstack_i18n_meeting. > > 2015-09-17-13.00.log.html > > please create a Zanata branch so I can propose these corrections for review. > > > > Thanks! > > > > Doug > > _______________________________________________ > > Openstack-i18n mailing list > > Openstack-i18n(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

1 0

Translation of Nova
by Ying Chun Guo 22 Sep '15

22 Sep '15

Hi, John I put nova project as the first non-user interface project in Liberty translation. I set nova.pot as "required to be translated" and set nova-log-* as "optional to be translated". I understand nova.pot contains all user facing messages. But I don't clear what kinds of messages they are. Could you explain what kinds of messages nova.pot includes and how these messages are visible to end users ? There is another mail thread[1] discussing that python-openstackclient should be high priority to translate. And other clients such as python-novaclient are deprecating and should not be translated or lower priority to be translated. I know you are busy with the RC1 cut. When you are available, help to share some inputs. Thank you. Best regards Ying Chun Guo (Daisy) [1] http://lists.openstack.org/pipermail/openstack-i18n/2015-September/001389.h…

2 1

Re: [Openstack-i18n] Zanata, message to the team
by Akihiro Motoki 21 Sep '15

21 Sep '15

I see no technical reason. I am okay if we have a consensus that we can use various languages on the list to discuss topics specific to languages. Does everybody want this? I don't think it works if message in Frensh, Spanish, Chinese, Russian, Japanese, Korean, Turkish, Arabian and more on a single list. I might be missing something important. OpenStack foundation provides use the mailing list server under openstack.org domain and local communities can use it. Akihiro 2015-09-17 23:40 GMT+09:00 Douglas Fish <drfish(a)us.ibm.com>: > Can't other languages be used on the mailing list? Is this a technical > limitation? > > Doug > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 09/17/2015 09:08:26 AM: > > > From: Akihiro Motoki <amotoki(a)gmail.com> > > To: Openstack-i18n Openstack-i18n <openstack-i18n(a)lists.openstack.org> > > Date: 09/17/2015 09:09 AM > > Subject: Re: [Openstack-i18n] Zanata, message to the team > > > > One thing to note is that each language team would like to discuss > > in its language in most cases. > > > We don't want to use English in translation discussion :p > > Thus I think this mailing does not work to address the original question. > > > > In Japanese case, we use a mailing list in the local community, > > but not all language team has such media and they might had Transifex > > messaging to communicate each other. > > > > 2015-09-17 22:50 GMT+09:00 Andreas Jaeger <aj(a)suse.com>: > > On 2015-09-17 15:19, Jeremy Stanley wrote: > > On 2015-09-17 07:58:39 -0500 (-0500), Douglas Fish wrote: > > Can't the openstack-i18n mailing list be used for this? In the > > openstack-dev lists multiple teams use it and we just include [horizon] > or > > [keystone] or similar as appropriate to help sort out messages to > > interested parties. > > > > The nice thing about this is that it makes the discussion open to others > > who might take interest periodically. > > > > Not only that, the discussion is also archived and accessible > > anonymously over the Web. Any group contact mechanism built into > > Zanata as an afterthought is going to be inferior to proper mailing > > lists as a general discussion platform. > > > > > Challenge is that not every translator is subscribed here AFAIU. How > > can we encourage usage of this mailing list? > > > > 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 > > > > > > > > _______________________________________________ > > 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 > >

4 4

Liberty translation progress report
by Ying Chun Guo 21 Sep '15

21 Sep '15

Hi, team 10 days passed since we started Liberty translation. Now let's review the progress we made. 1. Horizon translations Till today, following teams have made amazing progress. Many thanks for their works. These teams could certainly finish Horizon translation on time. They are: Japanese 100.0% English (Australia) 99.63% French 98.61% German 98.51% Chinese (China) 97.56% Spanish 97.28% Turkish (Turkey) 96.76% Czech 96.55% Korean (South Korea) 96.0% Chinese (Taiwan) 95.12% Portuguese (Brazil) 93.13% Following teams have possibilities to catch the deadline too. They are: English (United Kingdom) 87.85% Russian 83.58% Polish (Poland)80.48% If coordinators of those language teams have difficulties to catch the goal, please let me know as soon as possible. 2. Horizon authorization page translations This is not a big resource. There are 12 languages 100% completed. They are: Chinese (China),Czech,English (Australia), English (United Kingdom),German, Japanese,Korean (South Korea), Portuguese (Brazil),Russian,Spanish,Spanish (Mexico), Turkish (Turkey). There are only a very few strings left in Chinese (Taiwan), Polish (Poland), and French translations. Please don't forget to finish them. 3. Nova translations nova.pot is included in Liberty translation plan. Following language teams have made good progress: Chinese (China) 100.0% Czech 99.63% Spanish 94.78% Turkish (Turkey) 94.1% Some others languages team might not have good progress. I understand some translators are not active in Nova translations. For those language teams, I will suggest to import IBM translations. While I did test, after merging IBM translations, the percentage will increase to 90% and even more. I hope coordinators could take a serious consideration of this suggestion. I appreciate very much your contributions in Liberty translations. I'm very sure we will get a good result in Liberty. Thank you. Best regards Ying Chun Guo (Daisy)

1 0

PTL Elections September 2015
by Ying Chun Guo 21 Sep '15

21 Sep '15

Hi, team We just became a official team in Liberty, I guess some of you are not familiar with PTL elections process. Every official project must elect a PTL. PTLs are elected for 6 months. All ATC's have the right to vote for your favorite PTL for a cycle. Refer to this wiki page: https://wiki.openstack.org/wiki/PTL_Elections_September_2015 I have submitted my candidacy for I18n team just now. Hope to get your support for my PTL role for Mitaka. Thank you. Regards Daisy

2 2

Would like Zanata branch to correct 1494819
by Douglas Fish 19 Sep '15

19 Sep '15

2 2

Re: [Openstack-i18n] Zanata, message to the team
by Robert Simai 18 Sep '15

18 Sep '15

Hi Doug, I see one advantage in that approach, the list is already there. I see more disadvantages: - we'd need to make sure that all translators are subscribed. I don't think it's the case - for a regular translator many stuff discussed here may not be relevant or interesting - they will all have to setup proper email filtering and it needs discipline for the poster to stick to that. You'd probably need two tags, one for the project and one for the language - we can't use the local language to discuss language specific stuff but need to stick to English And there may be a few more. These however were my thoughts why I (still) think it should rather be a Zanata feature as there we have user/team information and could easily target messages to relevant people. -- Thanks, Robert On Thu Sep 17 2015 14:58:39 GMT+0200 (CEST) drfish(a)us.ibm.com wrote: > Can't the openstack-i18n mailing list be used for this? In the > openstack-dev lists multiple teams use it and we just include [horizon] > or [keystone] or similar as appropriate to help sort out messages to > interested parties. > > The nice thing about this is that it makes the discussion open to others > who might take interest periodically. > > Doug > > > Robert Simai <robert.simai(a)suse.com> wrote on 09/17/2015 03:32:30 AM: > > > From: Robert Simai <robert.simai(a)suse.com> > > To: Ying Chun Guo <guoyingc(a)cn.ibm.com>, > openstack-i18n(a)lists.openstack.org > > Date: 09/17/2015 03:33 AM > > Subject: Re: [Openstack-i18n] Zanata, message to the team > > > > Hi Daisy, > > > > On Thu Sep 17 2015 09:04:33 GMT+0200 (CEST) guoyingc(a)cn.ibm.com wrote: > > > > > Hi, Rob > > > > > > I didn't find the method to message team either. > > > I just find an instance messaging method to communicate with people who > > > are translating the same document. > > > > Yes, but that clearly has another purpose. > > > > > I think you might use email to talk with your team members. > > > I know it's not good. > > > > Frankly, it's less than not good as it means I (and whoever wants to do > > this) need to setup and maintain my own email distribution list all > > manually. > > > > > We could discuss how to add more communication ways. > > > Either ask Zanata to provide a feature, or we use a communicate method > > > on top of openstack infra. > > > > Well, I don't mind how it's done but would greatly appreciate if there's > > some easy way to send notifications to the specific language team. It > > probably should be a Zanata feature. > > > > > Best regards > > > Ying Chun Guo (Daisy) > > > > Thanks, > > Robert > > > > > > > > Robert Simai <robert.simai(a)suse.com> wrote on 2015/09/16 23:38:10: > > > > > > > From: Robert Simai <robert.simai(a)suse.com> > > > > To: openstack-i18n(a)lists.openstack.org > > > > Date: 2015/09/16 23:38 > > > > Subject: [Openstack-i18n] Zanata, message to the team > > > > > > > > Hi, > > > > > > > > probably I simply don't see it but how would I - as coordinator or > > > > regular team member - send a message to the translation team for my > > > > language? The only message I can create is "contact coordinators", > > > > myself so to say. > > > > > > > > Do I overlook this feature or is it just missing? If the latter, I'd > > > > clearly like to have it as I'm not sure if we can expect to have all > > > > translators on the openstack-i18n mailing list. In Transifex we > had the > > > > "discussions" forum to reach out to all team members, that was very > > > helpful. > > > > > > > > -- > > > > Thanks, > > > > Robert > > > > > > > > _______________________________________________ > > > > 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 > > >

3 2

Zanata, message to the team
by Robert Simai 18 Sep '15

18 Sep '15

Hi, probably I simply don't see it but how would I - as coordinator or regular team member - send a message to the translation team for my language? The only message I can create is "contact coordinators", myself so to say. Do I overlook this feature or is it just missing? If the latter, I'd clearly like to have it as I'm not sure if we can expect to have all translators on the openstack-i18n mailing list. In Transifex we had the "discussions" forum to reach out to all team members, that was very helpful. -- Thanks, Robert

6 9

What's Up, Doc? 18 Sep 2015
by Lana Brindley 18 Sep '15

18 Sep '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, First of all, with PTL candidacy now closed, it appears that I will be continuing to hold the docs reins through to Mitaka. Thank you to all of you who contacted me personally over the last week or so, expressing their support. I'm very honoured to be leading such a great team, and I'm looking forward to continuing to serve you. As always, my door will continue to be open to ideas, comments, and criticism, so please keep telling me what you do and don't like! We're less than a month away from the Liberty release now, and with the Mitaka PTL question settled, I'll be working on Design Summit session planning over the next few weeks. I've created an etherpad to gather your ideas, more on that in this newsletter. In other news, testing is now well underway on the Install Guide, I've knocked our existing blueprints into order, been doing some thinking about the DocImpact script, and worked with the speciality teams on determining the final work items for Liberty. == Progress towards Liberty == 26 days to go 514 bugs closed so far for this release. * RST conversion: ** Done. * User Guides information architecture overhaul ** Underway. Some tasks to be held over to Mitaka. * Greater focus on helping out devs with docs in their repo ** A certain amount of progress has been made here, and some wrinkles sorted out which will improve this process for the future. * Improve how we communicate with and support our corporate contributors ** I'm still trying to come up with great ideas for this, please let me know what you think. * Improve communication with Docs Liaisons ** I'm very pleased to see liaisons getting more involved in our bugs and reviews. Keep up the good work! * Clearing out old bugs ** Great work this week, with two bugs from the last two weeks closed (thanks Deena and Tom!). Three new bugs this week. == Mitaka Summit Prep == The schedule app for your phone is now available. This is a great tool once you're on the ground at Summit: https://itunes.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=98721 6292&mt=8 (Apple) and https://play.google.com/store/apps/details?id=org.sched.openstacksummitm ay2015vancouver (Android) Docs have been allocated two fishbowls, four workrooms, and a half day meetup, so now is the time to start gathering ideas for what you would like to see us cover. Add your ideas to the etherpad here: https://etherpad.openstack.org/p/Tokyo-DocsSessions == Outstanding Specs == * Third Party Driver Content: This spec has been outstanding for a while, and we've finally reached a consensus on how to move forward. Please take a moment to review the spec here before we go ahead merge it: https://review.openstack.org/#/c/191041/ * DocImpact: These are my ideas for reducing the noise from the DocImpact script, now up for discussion and ideas: https://review.openstack.org/#/c/224420/ == Doc team meeting == The APAC meeting was held this week. The minutes are here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-09-16 The next meetings are: US: Wednesday 23 September, 14:00:00 UTC APAC: Wednesday 30 September, 00:30: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_ meeting == Spotlight bugs for this week == Let's show these three that we're never going to give them up, never going to let them down: https://bugs.launchpad.net/openstack-manuals/+bug/1293328 Review Identity & LDAP integration https://bugs.launchpad.net/openstack-manuals/+bug/1294726 Update Cloud Administration Guide for OpenDaylight ML2 MechanismDriver https://bugs.launchpad.net/openstack-manuals/+bug/1300960 Making DB sanity checking be optional for DB migration - -- Remember, if you have content you would like to add to this newsletter, or you would like to be added to the distribution list, please email me directly at openstack(a)lanabrindley.com, or visit: https://wiki.openstack.org/w/index.php?title=Documentation/WhatsUpDoc Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJV+5L5AAoJELppzVb4+KUyEUcIANEavuRkTwSC44KEMVCvdzBw Q/luFp6zO/mySSfys0mFnB3/3GmQFQqSqW3FqLc9hWHIQQxxmG8VW9/Bhym5GNmr UMveZw+0winC4y41en1ZFFBz03uiQTvHVAFDmqjFHtgvWd/L3O9isrCsP3hnQ3JK Dl4Huaw6ZowbRgYTK7Jaspuu/mS7Me8hUsvOCpBPvxQX3lYFBvOR93lwBEqNHp5B gu05Cy50KnwbrY+TQfrTEMiYxtyia1nf9SHF+9/5fxkzq9i4/Ine9WKIuYsOYI8u crJl9IPPKbgyMSp775RLQ9nFIXeh6cRDYWVVW29z1n1zYt9C7zcpZiDngkD8Zqg= =5yfK -----END PGP SIGNATURE-----

1 0

IBM translations to contribute: update
by Douglas Fish 18 Sep '15

18 Sep '15

Here's the revised approach we are taking to contributing our IBM translations to the community, based on feedback on suggestions: We are planning to make the proposed translations available for a pre-review as a separate branch in Zanata, but they are not there yet. While testing out this upload on the development server we discovered that uploading PO files caused the server to become unresponsive for a while. Thanks to pleia2 and the infra team for sorting that out and addressing the issue. We'll try the upload on dev again tomorrow and if it goes well we will make the translations available for pre-review in a separate Zanata branch. I had originally proposed ending the pre-review on Monday. Obviously that's not going to happen! I understand that different language teams have differing levels of readiness to accept these contributions. I understand some groups are ready at this time, while others would like to have more time, possibly even into Mitaka to review. We aren't going to upload PO files for any language were the team does not want them. Language coordinators, please let me know how you'd like to proceed with these contributions for your language. Do you want 1) us to upload them to Zanata's current master translations for normal review and editing as soon as we can, 2) us to upload them to Zanata as a separate branch for further pre-review, or 3) hold off any submission or preview at this time. Please note that it important to us that we upload these translations. The translations are a valued IBM asset, it's important to us that they are recognized as contributed by IBM. I'll be at the Thursday i18n team meeting, and am available by IRC (doug-fish) or email if you have questions or further concerns. Thanks! Doug

2 2

IBM translations to contribute
by Douglas Fish 17 Sep '15

17 Sep '15

Hi i18n Friends, I'm happy to share that we are proceeding with our plan to share our IBM translations with the OpenStack community. To review and follow up on what was shared in the 2015-08-20 i18n team meeting [1]: - We would like to contribute our IBM translations for projects ceilometer, glance, heat, nova, ironic, neutron, cinder, keystone, and swift. Note that Horizon is not in this list because the community has been focused on translating Horizon; I'm concerned there may be excessive terminology conflicts. - We have translations for de es fr it ja ko_KR pt_BR ru zh_CN zh_TW - These contributions are based on our Kilo translations. They have been reviewed and tested. - In order to facilitate an informal review by the translation teams before uploading I've made the translations available at https://github.com/doug-fish/openstack-translations . The repository is private. If you'd like access, just share your github id with me via email (drfish(a)us.ibm.com) or IRC (doug-fish) and I'll give you access. - Segments that have been updated with IBM translations have a comment "Contributed by IBM" added. This is to enable reviewing; I don't expect these comments to remain in Zanata after the upload. At a high level, our process is that we are extracting the existing PO files from Zanata, then using Babel based code to compare our IBM translations with the community ones and filling in any blanks. We've taken care not to overwrite any existing translations. These proposed files are based on what we extracted from Zanata recently (today). Our intent is to run this tooling again after the review period to pick up any community translations that have occurred. I'm aware that translations for Nova are not updated in Zanata yet, but again, I expect to handle this by re-running our tools. I'm working with Thomas Cocozzello (tjcocozz) and Lucas Palm (lapalm) who have coded our tools and scripts to handle this. They are requesting to join the language teams in Zanata so that if there are no concerns noted during the review they can upload translation contributions. I plan to ask Tom and Lucas to upload these files on 2015-09-14 unless there are concerns noted during the reviews. Please let me know if you have questions or concerns! Doug 1. http://eavesdrop.openstack.org/meetings/openstack_i18n/2015/openstack_i18n.… Doug Fish

6 8

Migration to Zanata will start at 00:00UTC September 9th
by Ying Chun Guo 16 Sep '15

16 Sep '15

Hello, team I'm so excited that the migration to Zanata finally comes, officially. It will start at 00:00UTC Sep 9th, (~2 hour from now). Please STOP your translations on Transifex now, till infrastructure team makes the announcement that migration is completely done. Or else, it could cause problems and your work will be lost. Translations from September 8th UTC time will be included in the migration. When the switch is made, pushing to and pulling from Transifex will be stopped. Please NOTICE: Translations made in Transifex after September 8th UTC will NO LONGER be submitted to OpenStack. All the users information and teams information in translate-dev.openstack.org will be included in the migration too. Please STOP the registration and adding team members in translate-dev.openstack.org. When migration is done, you could use the official website: translate.openstack.org. Hope everything runs well. Thank you for your corporation. Best regards Ying Chun Guo (Daisy)

6 11

IRC meeting tomorrow
by Ying Chun Guo 16 Sep '15

16 Sep '15

Hello, team We will have the IRC meeting at UTC 1300 in the channel #openstack-meeting, on September 17th. Following topics will be covered: * Collect issues/questions for Zanata and Liberty translation * Discussion: IBM contributions * Open discussions If you have other topics, feel free to propose. Best regards Ying Chun Guo (Daisy)

1 0

am I getting it wrong?
by ਅਨਪੜ੍ਹ ਜਿਮੀਂਦਾਰ 16 Sep '15

16 Sep '15

check these strings in nova-log-warning please 1) - %(logprefix)sfile does not exist - Resource ID: 8b11140881a372e28617726d6551bf55 2) - %(logprefix)unexpected IOError when reading - Resource ID: cb2f6d7cc64d66e928c3d4bfc62fc2f0 3) - %(logprefix)sfailed to load json - Resource ID: 82759c0db94169cf8d6b3bf6d5bb28ae Am i getting these wrong or there are actually some blank spaces missing in the source strings? Sorry for spamming the mailing list :) Amandeep Singh

4 7

[all] New Gerrit translations change proposals from Zanata
by Elizabeth K. Joseph 16 Sep '15

16 Sep '15

Hi everyone, Daisy announced to the i18n team last week[0] that we've moved to using Zanata for translations for the Liberty cycle. Everyone should now be using Zanata at https://translate.openstack.org/ for translations. We're just now finishing up the infrastructure side of things with the switch from having Transifex submit the translations proposals to Gerrit to having Zanata do it. The Gerrit topic for these change proposals for all projects with translations has been changed from "transifex/translations" to "zanata/translations". After a test with oslo.versionedobjects last week[1], we're moving forward this Wednesday morning UTC time to have the jobs run so that all translations changes proposed to Gerrit are made by Zanata. Please let us know if you run into any problems or concerns with the changes being proposed to your project. The infra and i18n teams will have a look and provide help as needed. Thanks everyone, these are exciting times for the i18n team! [0] http://lists.openstack.org/pipermail/openstack-i18n/2015-September/001331.h… [1] https://review.openstack.org/#/c/222712/ note that the topic: had not yet been updated at the time of this change, but it has now -- Elizabeth Krumbach Joseph || Lyz || pleia2

1 0

Usability problem for coordinators: managing join requests?
by Tom Fifield 15 Sep '15

15 Sep '15

Hi, Please excuse me if I'm missing something obvious here - Zanata is quite new to me :) Based on my experience, it seems the process for approving a member request is very "manual" and could be quite frustrating for the large teams. 1. Email comes in: """ Dear Language Team Coordinator, Zanata user "Example Name" with id "example" is requesting to join the en (English) language team Roles requested: Translator Reviewer Coordinator Example Name has included the following message with this request: You can add user with username "Example Name" to the "en" team as translator using the "Add Team Member" action on the language team page. You can click the link below to go directly to the en-GB Language Team Page. Please reply to Example Name at example(a)example.org when you have finished processing this request. https://translate.openstack.org:443/language/view/en You are receiving this mail because: You are a coordinator in the "English" language team """ 2. Click the link to go to the Language Team 3. Can't do anything - need to login, so click login 4. After logging in, you are back at your personal profile page. Can't action the request here, so go back to the email and click the link again 5. Expect to see something about the new request on the language team page, but there's nothing there. Can't action the request, so go back and read the email again. 6. Click the plus button to get the "Add Team Member" dialogue and realise you need to copy and paste the username from the email into the box. 7. Realise you don't remember which roles the user applied for. Go back and check the email a fourth time, then enter the roles and click add. 8. Email says it's now up to you to manually email the user to let them know they were added :) Are any other coordinators having this experience? Transifex wasn't perfect in how it dealt with join requests, but at least you could easily see a list of all of the requests for your language and approve them with a single click. If I'm not missing something, and this really is the procedure we need to run through 50 times for the larger languages to on-board everyone, then doing it on an ongoing basis, it seems less than ideal :) Regards, Tom

4 4

Updating Translations documentation for Zanata
by Elizabeth K. Joseph 15 Sep '15

15 Sep '15

Hi everyone, The documentation on https://wiki.openstack.org/wiki/Translations is now out-dated with our switch to Zanata, and just this morning we had a question about it in the #openstack-i18n channel. For now, I've placed a heading on that page explaining that the Transifex information is now out-dated, but we will work to get this documentation updated over the next couple weeks. If there's other documentation out there about OpenStack Translations please let me know so I can make sure it's on my list to update. -- Elizabeth Krumbach Joseph || Lyz || pleia2

3 3

What Up, Doc? 11 September, 2015
by Lana Brindley 14 Sep '15

14 Sep '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, Things are really starting to heat up now! Summit preparations are well underway, PTL elections just opened, and testing is proceeding apace on the Install Guide. As well as preparing my candidacy for Mitaka Docs PTL, I've been continuing to sort out the outstanding blueprints, and also planning for some announcements in Tokyo. One of the interesting things I learned while compiling a list of Liberty achievements is that we have released fixes for nearly 500 bugs since Kilo was released. What an amazing achievement! == Progress towards Liberty == 33 days to go 496 bugs closed so far. * RST conversion: ** Done. * User Guides information architecture overhaul ** This is now well underway. * Greater focus on helping out devs with docs in their repo ** A certain amount of progress has been made here, and some wrinkles sorted out which will improve this process for the future. * Improve how we communicate with and support our corporate contributors ** I'm still trying to come up with great ideas for this, please let me know what you think. * Improve communication with Docs Liaisons ** I'm very pleased to see liaisons getting more involved in our bugs and reviews. Keep up the good work! * Clearing out old bugs ** We've had some solid progress on last week's bugs, with two assigned, and one of those in progress. Three new bugs this week. == Mitaka Summit Prep == The schedule has now been released, congratulations to everyone who had a talk accepted this time around: https://www.openstack.org/summit/tokyo-2015/schedule/ All ATCs should have received their pass by now, so now is the time to be booking your travel and accommodation: https://www.openstack.org/summit/tokyo-2015/tokyo-and-travel/ Docs have been given their design summit session allocation, so start thinking about what you would like to see discussed. I'll send out an etherpad to start planning in the next week or two. == Conventions == A new governance patch has landed which changes the way we capitalise service names (I know almost exactly 50% of you will be happy about this!): https://wiki.openstack.org/wiki/Documentation/Conventions#Service_and_pr oject_names Please be aware of this when editing files, and remember that the 'source of truth' for these things is the projects.yaml file: http://git.openstack.org/cgit/openstack/governance/tree/reference/projec ts.yaml == Doc team meeting == The US meeting was held this week. The minutes are here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-09-09 The next meetings are: APAC: Wednesday 16 September, 00:30:00 UTC US: Wednesday 23 September, 14:00: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_ meeting == Spotlight bugs for this week == Let's show these three how much we care: https://bugs.launchpad.net/openstack-manuals/+bug/1284301 Document Neutron SSL-VPN for cloudadmin https://bugs.launchpad.net/openstack-manuals/+bug/1288044 Add user defined extra capabilities https://bugs.launchpad.net/openstack-manuals/+bug/1292327 Make cors work better - -- Remember, if you have content you would like to add to this newsletter, or you would like to be added to the distribution list, please email me directly at openstack(a)lanabrindley.com, or visit: https://wiki.openstack.org/w/index.php?title=Documentation/WhatsUpDoc Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJV9km4AAoJELppzVb4+KUyr0kIALxedlQxY0jONXXD+xaPNW76 JPjpnBrBjGyIvq09qeqU4vYVkSq56eF2qPtY6YCKmu0nkjTxAoJX0JxqGyTq3J+H nPv/+Hyg/VOJaZmJ6Qs3Ij1w9759OLiovnUjh3IsjkkZOXN/uHxw5LZQ3oXhmK+j Ydui86STbM1OUtOeNcxgH5zGl4aj/SWCrOwARAKXs6K0JShUvvtYmxPnQwvX/Mgn uLy9976PoboOR6SCW052ZBNT1VKHPOjpCaK3xOf7JJZQYi1V1Uv7BJwpSTBiyYOv MFvHRETKiWvfbyDKvvR1tYxyQixGq/aQWWcxke14YugEjFZ3wUAoWdwiD0VfXsA= =52+9 -----END PGP SIGNATURE-----

1 0

[nova] [all] Updated String Freeze Guidelines
by John Garbutt 10 Sep '15

10 Sep '15

Hi, I have had quite a few comments from folks about the string freeze being too strict. It was noted that: * users will prefer an untranslated log, over a silent failure * translators don't want existing strings changing while they are translating them * translators tooling can cope OK with moved strings and new strings After yesterday's cross project meeting, and hanging out in #openstack-i18n I have come up with these updates to the String Freeze Guidelines: https://wiki.openstack.org/wiki/StringFreeze Basically, we have a Soft String Freeze from Feature Freeze until RC1: * Translators work through all existing strings during this time * So avoid changing existing translatable strings * Additional strings are generally OK Then post RC1, we have a Hard String Freeze: * No new strings, and no string changes * Exceptions need discussion Then at least 10 working days after RC1: * we need a new RC candidate to include any updated strings Is everyone happy with these changes? Thanks, John

2 1

String Freeze Guidelines Update
by John Garbutt 10 Sep '15

10 Sep '15

Hi all, Daisy and I have been chatting about the String Freeze guidelines. After our conversations, and some discussion in the cross project meeting, I have updated them here: https://wiki.openstack.org/wiki/StringFreeze It seems the general string freeze got accidentally got made super strict. Hopefully this slight relaxing of the rules will work better for everyone, particularly for our users. Certainly right now we are only merging bug fixes, but they often include the need for extra log messages, or similar. Right now we are hiding logs as debug messages, etc, to try and get them merged during the freeze. The above changes should stop all that pain, and help our users too. Does this sound sensible? Thanks, John IRC: johnthetubaguy

3 4

Liberty translation, go!
by Ying Chun Guo 10 Sep '15

10 Sep '15

Hello, team As the new translation tool - Zanata is ready to use, let's kick off the Liberty translation from today. The Liberty translation plan includes Horizon translation and Nova translation. We are quite familiar with Horizon translations. Here are the Horizon documents to be translated in Liberty: https://translate.openstack.org/iteration/view/horizon/master/documents Since Kilo release, there are 500+ new introduced messages. Nova is the first time to be included in the translation plan. It could be regarded as a trial that I18n team would translate more kinds of user facing messages in the future. Here are the Nova documents to be translated: https://translate.openstack.org/iteration/view/nova/master/documents Document "nova" contains user facing messages, which is required to be translated. Documents "nova-log-*" contain different levels of log messages, which are optional to be translated. Whether to translate log messages and which levels to be translated could be the decision of each language team. In Liberty translation, we use two phases of string freeze: the soft freeze and the hard freeze[1]. Soft freeze is already happened at feature freeze time. Hard freeze will be happened in the week of 21st September. New strings will be added before the strict freeze while we are translating. After strict freeze there will be few strings added, and then we will get 10 days to finish up the translations. Oct 12-16 is the official Liberty release date. We have to finish all the translations several days before the final release, in order to give time to development team to import translations, package everything, and run final tests. So Oct 5 would be an appropriate deadline for translation. If you want your language pack to be included in Liberty release, work with your language team, finish these translations before Oct. 5. Zanata is a new tool for translation team. Wiki page [2] describes how to register and how to join a language team. Zanata translators guide [3] is helpful if you don't know how to use Zanata. If you meet with any issues or problems you cannot solve, ask for help through the IRC channel and the mailing list. There is a strong infrastructure team and a supportive Zanata team behind us. September is a busy time for translators. Let's start Liberty translation now. Any questions, please let me know. Best regards Ying Chun Guo (Daisy) [1] https://wiki.openstack.org/wiki/StringFreeze [2] https://wiki.openstack.org/wiki/I18nTeam/become-a-official-translator [3] http://docs.zanata.org/en/release/user-guide/translator-guide/

1 0

Request for Assistance with OpenStack Diversity Survey
by Roland Chan 10 Sep '15

10 Sep '15

Hi All, As part of the OpenStack Foundation's Diversity Working Group. ( https://wiki.openstack.org/wiki/Diversity) I am coordinating a survey of the OpenStack community. The intent of the survey is the measure the diversity of the community in various areas to determine priorities for action. The survey covers a great number of topics: gender, sexuality, geography and language use. It would be of assistance if the survey could be translated into multiple languages to maximise the ease with which the people can respond. There are about 15 short questions that would need to be translated. I'm aware that additional work at this time of the cycle is probably the last thing anyone needs, but if anyone is free to assist for any language, please contact me. Even advice would be welcome if translation is not feasible. Also, if anyone is interested in participating in the Diversity Working Group, check out the link above and come to a meeting. Thanks! Roland Chan

1 0

[Openstack-infra] No encoding string on Zanata
by SungJin Kang 10 Sep '15

10 Sep '15

hi Today translation tool maigration to Zanata. I no see korean string. [1] .po file is show korean string. Maybe you want korean font. Using NanumGothic font [2]. Thanks, sungjin. [1]: http://imgur.com/Bu7IJH5 [2]: https://github.com/ujuc/nanum-font

1 1

Fwd: Final plans before translations switch to Zanata
by ਅਨਪੜ੍ਹ ਜਿਮੀਂਦਾਰ 09 Sep '15

09 Sep '15

---------- Forwarded message ---------- From: *Arvinder Singh Kang* <contact(a)arvinderkang.com> Date: Tuesday, September 8, 2015 Subject: [Openstack-i18n] Final plans before translations switch to Zanata To: Amandeep Saini <jimidar(a)gmail.com> pa-IN is flawed and Panjabi is not a proprietary language of India - but language is spread across the world.e.g. It is the third most spoken/written language in BC after English. Also pa-Arab is not appropriate because there is no direct connection between spoken Arabic and Punjabi. pa-Guru / pa-Shah would make a much better argument. On Sep 8, 2015, at 12:18 AM, ਅਨਪੜ੍ਹ ਜਿਮੀਂਦਾਰ <jimidar(a)gmail.com <javascript:_e(%7B%7D,'cvml','jimidar(a)gmail.com');>> wrote: What you think about suggested language codes for opensatck in zanata? ---------- Forwarded message ---------- From: *Sean Flanigan* <sflaniga(a)redhat.com <javascript:_e(%7B%7D,'cvml','sflaniga(a)redhat.com');>> Date: Sunday, September 6, 2015 Subject: [Openstack-i18n] Final plans before translations switch to Zanata To: ਅਨਪੜ੍ਹ ਜਿਮੀਂਦਾਰ <jimidar(a)gmail.com <javascript:_e(%7B%7D,'cvml','jimidar(a)gmail.com');>> Cc: openstack-i18n(a)lists.openstack.org <javascript:_e(%7B%7D,'cvml','openstack-i18n(a)lists.openstack.org');>, openstack-infra(a)lists.openstack.org <javascript:_e(%7B%7D,'cvml','openstack-infra(a)lists.openstack.org');> On 5 September 2015 at 05:41, ਅਨਪੜ੍ਹ ਜਿਮੀਂਦਾਰ <jimidar(a)gmail.com> wrote: > Please find my comments for bn and pa inline. > > Thanks > Jimidar > (Amandeep Singh) > > On Thu, Aug 27, 2015 at 10:48 AM, Andreas Jaeger <aj(a)suse.com> wrote: > >> >> pa-IN >>> >> >> Rename to pa? > > > Punjabi (pa) has two scripts, one is Gurmukhi used in Indian side of > Punjab and the other is Shahmukhi (Urdu) used in Pakistan's Punjab, so > renaming to a generalized name wont do the justice to both entirely > different scripts. > Would "pa-Guru" work as a more general locale for Punjabi Gurmukhi? With "pa-Arab" for Punjabi Shahmukhi? -- Sean Flanigan Principal Software Engineer Globalisation Tools Engineering Red Hat

1 0

Final plans before translations switch to Zanata
by Elizabeth K. Joseph 08 Sep '15

08 Sep '15

Hi everyone, As I mentioned at the infrastructure meeting yesterday[0], we are almost ready to launch the production Zanata server (translate.openstack.org) I have a week long trip starting this Friday night so I'm sharing my plans here so clarkb, StevenK and others can continue the work while I'm gone. I'm Cc:ing the translations team on this message so they are kept in the loop. First of all, timeline-wise we're aiming to get this in the hands of the translators by the week of September 7th so they have time to do their work before the Liberty release. We have a few improvements to installation that we still need to work out: 1. Switch to archive module for server installation (change here: https://review.openstack.org/#/c/192901/) 2. Switch to archive module for client installation (I'll get that change proposed today) 3. Figure out why Wildfly 9.1 isn't being installed and used (instead of 8.1 that we began with), in spite of changing the download link (it's being downloaded) and upgrading the puppet-wildfly module (Steve: you've doven into the latest changes in the puppet-wildfly module, perhaps you're in a good place to look at this?) This should all be finished in the next couple days and we can then launch translate.openstack.org Beyond raw server launching, there are a few other things that we need to make sure happen: 1. Work with Carlos to get instructions for properly importing the user database to the new server (I've Cc:ed him here, we need this ASAP) 2. Work with Daisy to make sure there are cut-over instructions from Transifex to Zanata, and if there's anything we need to do (we should make a plan, even if the exact date is not clear) 3. Generally make sure everything on our script side of things is going well (StevenK has done an amazing job with these so I'm not worried) 4. Make sure we have imported everything we need. AJaeger will be traveling some too, but had the following to say: "First priority would be that the translators can translate. So, this means pushing source strings to Zanata (at least once initially) and getting them working is most important. Then the regular update after each change (which should be working fine already). Importing in the projects can wait a few days, there's no harm if that one stops for a week or two since we do not lose time this way. For translation the most important project is horizon with it's friends" I think that's it. I'll do my best to check in and reply to email and IRC pings while I'm traveling, but some things may need to wait until I'm back at my hotel in the [US east coast] evening. I'll be back the [US west coast] night of Sunday, September 6th. The 7th is a holiday in the US, but I'll be available if we have unexpected problems to work through. Thanks everyone. [0] Starting 19:19: http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-08-25-19.00.l… -- Elizabeth Krumbach Joseph || Lyz || pleia2

10 19

Migrating to Zanata - Progress update
by Ying Chun Guo 08 Sep '15

08 Sep '15

Hello, team According to the update from infrastructure team, the migration will happen in this week, probably on late Tuesday PDT time. All the preparation work is done. Just need an appropriate time to kick off. Now there are 92 users registered in Zanata trial instance (i.e. translate-dev.openstack.org ). 8 language teams have coordinators. Comparing with 900+ translators and 80+ language teams in Transifex, there is still a big gap. More details about the translation teams in Zanata could be found here: https://wiki.openstack.org/wiki/I18nTeam/Migration-to-zanata I'm going to use "messaging" in Transifex to inform the change to coordinators of some "important" language teams , one by one. If you have good suggestions to attract more translators from Transifex to Zanata, please let me know. Thank you. Best regards Ying Chun Guo (Daisy)

1 0

[nova][i18n] Is there any point in using _() in python-novaclient?
by Matt Riedemann 06 Sep '15

06 Sep '15

I noticed this today: https://review.openstack.org/#/c/219768/ And it got me thinking about something I've wondered before - why do we even use _() in python-novaclient? It doesn't have any .po files for babel message translation, it has no babel config, there is nothing in setup.cfg about extracting messages and compiling them into .mo's, there is nothing on Transifex for python-novaclient, etc. Is there a way to change your locale and get translated output in nova CLIs? I didn't find anything in docs from a quick google search. Comparing to python-openstackclient, that does have a babel config and some locale po files in tree, at least for de and zh_TW. So if this doesn't work in python-novaclient, do we need any of the i18n code in there? It doesn't really hurt, but it seems pointless to push changes for it or try to keep user-facing messages in mind in the code. -- Thanks, Matt Riedemann

2 1

What's Up, Doc? 4 September, 2015
by Lana Brindley 04 Sep '15

04 Sep '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, This has been a fairly busy week, with Summit preparations beginning, more newly migrated RST books going live, and testing starting on the Install Guide. I've been spending time on sorting out the Liberty blueprints still outstanding, and also working on some old bugs. == Progress towards Liberty == 40 days to go! * RST conversion: ** Is now completed! Well done and a huge thank you to everyone who converted pages, approved reviews, and participated in publishing the new guides. This was a truly phenomenal effort :) * User Guides information architecture overhaul ** Some user analysis has begun, and we have a new blueprint: https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reo rganised * Greater focus on helping out devs with docs in their repo ** A certain amount of progress has been made here, and some wrinkles sorted out which will improve this process for the future. * Improve how we communicate with and support our corporate contributors ** If you currently work on documentation for a company that would like to improve their upstream commits for documentation, please contact me! * Improve communication with Docs Liaisons ** I'm very pleased to see liaisons getting more involved in our bugs and reviews. Keep up the good work! * Clearing out old bugs ** The last lot of old bugs are still languishing. I'm assuming you all hate them so very much that I've decided to give you three more to pick from. Have at it! == Countdown to Summit == With the Liberty release less than two months away, that means it's nearly Summit time again: https://www.openstack.org/summit/tokyo-2015/ The schedule has now been released, congratulations to everyone who had a talk accepted this time around: https://www.openstack.org/summit/tokyo-2015/schedule/ All ATCs should have received their pass by now, so now is the time to be booking your travel and accommodation: https://www.openstack.org/summit/tokyo-2015/tokyo-and-travel/ == Conventions == A new governance patch has landed which changes the way we capitalise service names (I know almost exactly 50% of you will be happy about this!): https://wiki.openstack.org/wiki/Documentation/Conventions#Service_and_pr oject_names Please be aware of this when editing files, and remember that the 'source of truth' for these things is the projects.yaml file: http://git.openstack.org/cgit/openstack/governance/tree/reference/projec ts.yaml == Docs Tools == openstack-doc-tools 0.30.0 and openstackdocstheme 1.2.1 have been released. openstack-doc-tools allows translation of the Install Guide. openstackdocstheme contains fixes for the inclusion of metatags, removes unused images and javascript files, and fixes the "Docs Home" link. == Doc team meeting == The APAC meeting was not held this week. The minutes from the previous US meeting are here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-08-26 The next meetings are: US: Wednesday 9 September, 14:00:00 UTC APAC: Wednesday 16 September, 00:30: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_ meeting == Spotlight bugs for this week == Let's give these three a little love: https://bugs.launchpad.net/openstack-manuals/+bug/1280092 end user guide lacks doc on admin password injection https://bugs.launchpad.net/openstack-manuals/+bug/1282765 Chapter 6. Block Storage in OpenStack Cloud Administrator Guide https://bugs.launchpad.net/openstack-manuals/+bug/1284215 Driver for IBM SONAS and Storwize V7000 Unified - -- Remember, if you have content you would like to add to this newsletter, or you would like to be added to the distribution list, please email me directly at openstack(a)lanabrindley.com, or visit: https://wiki.openstack.org/w/index.php?title=Documentation/WhatsUpDoc Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJV6TlFAAoJELppzVb4+KUy/zkIAKYKbKdw78Nv8dpB8d9Rj4qh +JTK2rTlz/Up5F10OzIoJoNMIvySeKH+jHV1CP0qL9KigYaepkEeMn8RnNSayYww cgSmk/8gpzGTTd17JK0Rrn+RjOb3XMYeNH2d4OkvIQPGBAYsnerODrvEK3GG7YHO oo5xYSkLdYH54qnXhhvNZxjxDclT1P5QgpUP6M6KcB3bcKt4niHGLHnBHFoqvlMR gJA1BtKR6CackhZbkJpPFCpEHimm4xdWwF+q7xRezy599MbkkPAIxR/oMuEkqU2H zj+tm9sHDxOoH2j4Hfkbw7xxF+/NjvGtm41JCPsUVBxuAocaBbJ1kZRbbRzrafI= =2TAI -----END PGP SIGNATURE-----

1 0

IRC meeting tomorrow
by Ying Chun Guo 02 Sep '15

02 Sep '15

Hello, team We will have the IRC meeting at UTC 0600 in the channel #openstack-meeting, on September 3rd. I will be there to answer any questions about Liberty translation and new translation platform. Join the meeting if you have any concerns and questions. Following topics will be covered: * Zanata status and QA * Liberty translation plan and QA * Open discussions If you have other topics, feel free to propose. Best regards Ying Chun Guo (Daisy)

1 0

Zanata migration on 9/7?
by Akihiro Motoki 01 Sep '15

01 Sep '15

Hi Daisy, I heard from other Japanese translators that we will move to Zanata on Sep 7. Is it officially decided? As far as I heard it was announced only on Transifex message [1]. After I heard that, I checked various place in Transifex but I could not find any announce. In addition, I completely disable Transifex message as almost of them are useless. Has it already been announced in this list? Don't we need to announce it in this list? I thought this list is the official place where this kind of important information is announced. Is my understanding wrong? Akihiro [1] https://www.transifex.com/openstack/teams/670/discussions/13508/

3 3

Russian translations with 4 pluralities?
by Douglas Fish 28 Aug '15

28 Aug '15

I notice that the RU files that are coming out of Transifex right now have 4 pluralities: https://www.transifex.com/openstack/horizon/horizon-translations/ru/downloa… which is unexpected to me. I'd expect RU files to have 3 pluralities like we see in Zanata https://translate-dev.openstack.org/rest/file/translation/horizon/master/ru… Does anyone know why the RU files from Transifex look this way? Should it concern us? Will this make any uploading to Zanata difficult? Doug Fish

1 0

HA Conversion to RST and translations
by Andreas Jaeger 27 Aug '15

27 Aug '15

Dear i18n team, The High Availability Guide is now nearly finished with the RST conversion and we now have both old and new guide in transifex. You have now these resources in transifex: * high-availability-guide: This is the old DocBook version, it will soon get removed. Don't translate anymore! * ha-guide: This is the new RST version. The HA team is still doing some rework of the new RST HA guide, so I suggest you don't start translation of it yet until we tell you that it's ready. 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

1 0

Japanese Install Guides publishing - and openstack-doc-tools 0.30.1
by Andreas Jaeger 27 Aug '15

27 Aug '15

Congrats to the Japanese translation team! We now have the RST Install Guides translated and up for review on http://docs.openstack.org/draft/draft-index.html To properly publish the Debian version of it, we had to release openstack-doc-tools 0.30.1. 0.30.1 fixes also one annoying issue a few of you fall into: When you run tox -e checklang, files were changed and some of you committed them by accident. This will not happen anymore, checklang now cleans up properly. 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 3

Re: [Openstack-i18n] Zanata trial starts ! Please register and try - requirements before production
by Ying Chun Guo 24 Aug '15

24 Aug '15

Thank you, Elizabeth. If you could manipulate user database, it would be great. Even a coordinator gets a OpenStack ID, he/she still needs to do the first time "log in" and then create his/her profiles, then his/her user id is shown up in the user list. If his/her user id doesn't appear in the user list, I could not assign him/her any roles, except waiting for him/her to log in. The same thing happens when a coordinator wants to create his/her language team. The coordinator has to wait for the team members to do the first time "log in". There are 40+ language teams. So creating language teams will be a time consuming work. In September, we don't have much time to wait. If you could import database, it will be a one minute task. That will save us a lot of time. Best regards Ying Chun Guo (Daisy) "Elizabeth K. Joseph" <lyz(a)princessleia.com> wrote on 08/22/2015 01:24:49 AM: > From: "Elizabeth K. Joseph" <lyz(a)princessleia.com> > To: Ying Chun Guo/China/IBM@IBMCN > Cc: Openstack-i18n Openstack-i18n <openstack-i18n(a)lists.openstack.org> > Date: 08/22/2015 01:25 AM > Subject: Re: [Openstack-i18n] Zanata trial starts ! Please register > and try - requirements before production > > On Fri, Aug 21, 2015 at 10:17 AM, Elizabeth K. Joseph > <lyz(a)princessleia.com> wrote: > > As far as I know, there is > > no export tool and the whole process would be raw database > > manipulation and I don't know all the things that I'd need to change, > > it's a complicated database. I'll follow up with Carlos to confirm. > > Just read the back scroll in the #zanata channel, as I suspected it > does sound like the API won't work for us, but manual editing of the > database will: > > 00:33:31 < camunoz> well, I don't think you need a list (unless you > want to filter out some users). We could just take an extract of the > relevant tables from the database right before the move, and then dump > that extract onto the new database > > So with it sound like he knows the right sections to export from the > data to make this possible. I'll work with him next week to come up > with a detailed plan. > > -- > Elizabeth Krumbach Joseph || Lyz || pleia2 >

1 0

Re: [Openstack-i18n] Zanata trial starts ! Please register, and try - requirements before production
by Carlos Munoz 24 Aug '15

24 Aug '15

Hi, Just a couple of points from some discussions that I've had with Daisy and Elizabeth in the past few days. 1. About Zanata's short session timeout: I did some research and unfortunately the most recent versions of Wildfly removed the capability of changing the session timeout outside of the application. What this means is that in order to increase we are going to need to modify an xml file inside the Zanata package. This is a minimal change that can be puppetized if needed. I will try to add this as a permanent change in Zanata for future releases. 2. About the migration of user accounts from the Development server to a production one. My recommendation is that we do a copy of the relevant tables in the dev server directly onto production. This way the full registered user base will be copied over. We could even look at doing the same for language teams if needed. Let me know if there are any questions. Regards, -- Carlos A. Munoz Software Engineering Supervisor Engineering - Internationalization Red Hat

1 0

admin-guide-cloud is converted to RST
by Andreas Jaeger 22 Aug '15

22 Aug '15

The Cloud Admin Guide resource is now migrated from XML to RST, admin-guide-cloud is therefore now fully RST. The guide currently has no full translations and will now get revised - so don't give it any priority for now, 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

1 0

IRC meeting tomorrow
by Ying Chun Guo 21 Aug '15

21 Aug '15

Hello, team We will have the IRC meeting at UTC 1300 in the channel #openstack-meeting, on August 20th. I'm going to cover following topics: * I18n sessions in Tokyo summit * Open discussions If you have other topics, feel free to propose. Best regards Ying Chun Guo (Daisy)

2 1

Meeting minutes of last IRC meeting - must read
by Ying Chun Guo 21 Aug '15

21 Aug '15

Hello, team There are several important topics mentioned in last IRC meeting, which I would let you know. 1. I18n sessions in Tokyo summit I have booked several time slots for I18n meeting. Now they are opening for proposals. If you have any topics related with I18n and want to have face to face discussion in Tokyo summit, please propose your topics here: https://etherpad.openstack.org/p/tokyo-i18n-sessions If the time slots are not suitable for you, please let me know before Aug. 24. As to the summit registration codes, after the ATC list is approved by TC, I will continue the process to get discount codes for the ATCs. 2. Liberty translation According to the release schedule of Liberty, the feature freeze date is Sep. 1-3, the official release date is Oct. 15th. So when the Zanata production environment is ready, the translation team have to kick off Liberty translations as soon as possible. The deadline is usually 7-10 days before the final release date, although nobody knows the exact date now. So we will have a busy September. Please arrange your time in advance. Before Liberty translation starts, the most important thing is to move the whole team to Zanata ! Please help to encourage your team to sign the CLA, register in Zanata, join the language team, and get familiar with Zanata. More details information could be found here: https://wiki.openstack.org/w/index.php?title=I18nTeam/become-a-official-tra… Please distribute to your team. 3. IBM wants to contribute its professional translations IBM had contributed its professional translations to upstream before, in two old releases. They keep on the update of translations in downstream, now the latest translations in their hands are for Kilo. They want to contribute these translations to upstream, just as what they did before. The translations are for projects: ceilometer glance heat nova ironic neutron cinder keystone swift ( note that horizon is not included. ) and for languages: de es fr it ja ko_KR pt_BR ru zh_CN zh_TW. These translations were translated by professional translators and tested under Kilo release. The plan is to add translations where the community translations don't not exist. The existing translations won't be overwritten. If you have any concerns, please let me know. Best regards Ying Chun Guo (Daisy) [1] https://wiki.openstack.org/wiki/Liberty_Release_Schedule

1 0

Zanata trial starts ! Please register and try.
by Ying Chun Guo 21 Aug '15

21 Aug '15

Hello, team Infra team have set up the Zanata test instance on top of openstack infrastructure. OpenStack projects, together with the translations, in Transifex have been moved to Zanata test instance now. So we could start the Zanata trial now. https://translate-dev.openstack.org/ (it's a self-signed certificate, so you will be presented with a warning, it's ok) 1. Log in You can use your OpenStack ID to log in. If you don't have, register here: https://www.openstack.org/join/register I will suggest to register with your company email, which will help your company to get the credit. If you don't want to, that's OK. :)) When you log in, you will be required to fill in your profile. Then you can start the trial. 2. Join a translation team List all languages by clicking "Languages" on the top. Click your language, you will go to that language page. On the right of the language name, there is a button "^..." which means "more actions". Click on the button and select "Request to Join Team". Then wait for your request to be approved. When it is approved, you will get the email notification. 3. Manage your team member if you are a coordinator If you are assigned a coordinator role, you will be able to see "Add Team Members" in the language page after clicking "^..." (more actions). You can only search users by user id. You can assign a member different roles (translator, reviewer, coordinator) 4. Translate After you have a language team, list the projects by clicking "Projects" on the top. Select a project, select a version, then you can translate. 5. Feedback We hope to get your feedback to the Zanata trial. If you find any resources/translations missed, which is in Transifex but not in Zanata, please let us know. If you find any bugs, please let us know. If you don't know how to operate, please let us know. We use https://etherpad.openstack.org/p/zanata-feedback to track the feedback. Reference link: Documentation for Zanata can be found here: http://docs.zanata.org/en/release/ Specifically for translators: http://docs.zanata.org/en/release/user-guide/translator-guide/ Note: 1. This is only a trial. All the projects, teams, and translations will not be preserved. This test instance will be wrapped off when the trail is done. Then infra team will create a formal website. You will be notified when we officially move to Zanata. Now if you want to translate, please still use Transifex for your primary translations work. Your registration to OpenStack ID will be preserved for ever. When we officially move to Zanata, you don't need to register again. But we need to create the language team once more. 2. Anyone can create projects, for the sake of this demonstration please don't create your own Thanks! Best regards Ying Chun Guo (Daisy)

8 22

Re: [Openstack-i18n] Install Guide: Converted to RST
by Andreas Jaeger 21 Aug '15

21 Aug '15

On 2015-08-20 16:59, Andreas Jaeger wrote: > The Install Guide is now completely RST and the resource "install-guide" > in transifex has been updated for translation of the RST files. > > Next guide to move to RST is "admin-guide-cloud", > > Andreas Note that as part of this change, we're not publishing the translated DocBook XML Install Guides anymore. Once we have Zanata and can publish from release branches - and have sufficient translation - we can publish again, 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

1 0

Re: [Openstack-i18n] Install Guide: Converted to RST
by Ying Chun Guo 21 Aug '15

21 Aug '15

Thank you for the update. The new install guide is for which release ? Best regards Ying Chun Guo (Daisy) Andreas Jaeger <aj(a)suse.com> wrote on 08/20/2015 10:59:47 PM: > From: Andreas Jaeger <aj(a)suse.com> > To: "openstack-i18n(a)lists.openstack.org" <openstack-i18n(a)lists.openstack.org> > Date: 08/20/2015 11:00 PM > Subject: [Openstack-i18n] Install Guide: Converted to RST > > The Install Guide is now completely RST and the resource "install-guide" > in transifex has been updated for translation of the RST files. > > Next guide to move to RST is "admin-guide-cloud", > > 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 > > > _______________________________________________ > Openstack-i18n mailing list > Openstack-i18n(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

2 1

What's Up, Doc? 21 August 2015 (Early edition)
by Lana Brindley 20 Aug '15

20 Aug '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, First of all, apologies for missing last week's newsletter: I got so caught up in the documentation swarm happening here in Brisbane that it totally slipped my mind! To make up for it, have this week's newsletter a day early :) In swarm news, the two days ran extremely smoothly, much to the credit of Suyog, Brian, and Alex who did the heavy lifting of preparation and organisation. While we focused largely on copy editing, we also had a lot of great discussion about the overall architecture of the book, and now have a draft plan ready for Mitaka, which Darren is driving with the Ops/Arch Guide speciality team. While last week was all about the docs swarm, this week has been doing the final cleanup on our newly converted RST books. The Security Guide is now up, and the Cloud Admin and HA Guides aren't far behind. We're also about to start testing the Install Guide, now that its conversion is complete. Well done to all the people who have helped out on these efforts, great job! == Progress towards Liberty == 55 days to go! * RST conversion: ** Install Guide: Conversion is done, testing to begin soon. ** Cloud Admin Guide: is complete! The new version will be available on docs.openstack.org very soon. ** HA Guide: is also done, and will available on the site soon. ** Security Guide: is complete, and live: http://docs.openstack.org/security-guide/ * User Guides information architecture overhaul ** Some user analysis has begun, with a new blueprint to land soon. * Greater focus on helping out devs with docs in their repo ** Work has picked up on the Ironic docs again. * Improve how we communicate with and support our corporate contributors ** If you currently work on documentation for a company that would like to improve their upstream commits for documentation, please contact me! * Improve communication with Docs Liaisons ** I'm very pleased to see liaisons getting more involved in our bugs and reviews. Keep up the good work! * Clearing out old bugs ** Sadly, no action on the spotlight bugs again this week. I'll keep the current three bugs for this week, to give everyone a little more time. == RST Migration == That's it! We're done! Do you have ideas for which book should be next? Have a think on it, and we'll discuss this at Summit. == Training Guides == I'm happy to announce that the Training Labs are now in their own repo, and are considered a documentation speciality team. Well done to Pranav, Matjaz, Sayali, and Roger for driving this effort. == Countdown to Summit == With the Liberty release less than two months away, that means it's nearly Summit time again: https://www.openstack.org/summit/tokyo-2015/ Here's a few things you might want to be thinking about: * Do you need a visa to visit Japan? If so, you need to be organising this NOW: https://www.openstack.org/summit/tokyo-2015/tokyo-and-travel/#visa * Do you have an ATC pass? If you haven't received your pass yet, and you're an ATC, please contact me so I can chase this up for you. Remember to use your ATC discount code before 31 August to make sure you get the full price discounted. == Doc team meeting == The APAC meeting was held this week. Read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-08-19 The next meetings are: US: Wednesday 26 August, 14:00:00 UTC APAC: Wednesday 2 September, 00:30: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… == Spotlight bugs for this week == Let's give these three a little more love: https://bugs.launchpad.net/openstack-manuals/+bug/1257018 VPNaaS isn't documented in cloud admin https://bugs.launchpad.net/openstack-manuals/+bug/1257656 VMware: add support for VM diagnostics https://bugs.launchpad.net/openstack-manuals/+bug/1261969 Document nova server package - -- Remember, if you have content you would like to add to this newsletter, or you would like to be added to the distribution list, please email me directly at openstack(a)lanabrindley.com, or visit: https://wiki.openstack.org/w/index.php?title=Documentation/WhatsUpDoc Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJV1TwWAAoJELppzVb4+KUylDUIALVRDpsMU+xM+7x8AsJKfnwv BRmGvUQWrrneBdx99b4Dyq/qianUPxz0hHjdchdeA37JfQYGiKoaVWVR1QAj5aPs WSg5/KRKI8cjHdfGDo7o0NhFIl2d9cyLj55xXap89QWSZvGoRSn8pXIibRoGd+1t Pp4RpxqftB8BYTlDkrdePYDIb0X+um3CJ2a/0DwuKUUVfn5zWxt9pOBYrYuqyFbK fUmI0LzRtopT+hmk02eHaefFzq+nQg5RO64osxd3JG/Zibgb8nIqw6eTjMBLvLs8 aPiNQ5ZSi5dwwRfy3pX8XpM4bl9iXOjhEAxtBT+6Zen4MvaTLehXbnoQ+ooETcQ= =ul61 -----END PGP SIGNATURE-----

1 0

ATC candidates listing
by KATO Tomoyuki 18 Aug '15

18 Aug '15

Hi Daisy, Action item from last meeting. Japanese team finished ATC candidates listing. Thanks, KATO Tomoyuki

7 16

Upgrade translate-dev to Zanata 3.7.1 8/17 0100UTC
by Clark Boylan 18 Aug '15

18 Aug '15

Hello, This is just a friendly heads up to let you all know that StevenK, Carlos, and I will be upgrading the Zanata instance running on translate-dev on August 17 at 0100 UTC. Expect the service to be offline while we perform the upgrade. Sorry for the trouble, but hopefully this pulls in bug fixes and other improvements (some of which based on your feedback I am sure) that will make the translate-dev experience much better. Let me know if you have any questions. Clark

1 1

Security Guide RST published
by Andreas Jaeger 13 Aug '15

13 Aug '15

The Security Guide has been converted to RST and we renamed it. So, the security-guide resource is now the resource for the RST guide. security-guide-rst is read-only now and not used anymore, 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, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 3

New Oslo projects for translation
by Davanum Srinivas 11 Aug '15

11 Aug '15

Andreas, Team, Can you please add the following projects to Transifex? * oslo.cache * oslo.policy * oslo.reports * oslo.service Thanks, Dims -- Davanum Srinivas :: https://twitter.com/dims

2 2

What's Up, Doc? 7 August 2015
by Lana Brindley 07 Aug '15

07 Aug '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, Welcome to August! Today we can finally announce that the Cloud Admin Guide is now completely converted to RST! I have been doing a fair bit of 'behind the scenes' work this week, focusing mainly on Training Guides and our docs licensing. We also welcome another new core team member this week, and for those of you in the APAC region, get ready for the Docs Swarm in Brisbane, where we'll be working on restructuring the Architecture Design Guide. == Progress towards Liberty == 68 days to go! * RST conversion: ** Install Guide: Conversion is nearly done, sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Installation_Guide_Mi… ** Cloud Admin Guide: is complete! The new version will be available on docs.openstack.org very soon. ** HA Guide: is also nearly done. Get in touch with Meg or Matt: https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update ** Security Guide: Conversion is now underway, sign up here: https://etherpad.openstack.org/p/sec-guide-rst * User Guides information architecture overhaul ** Waiting on the RST conversion of the Cloud Admin Guide to be complete * Greater focus on helping out devs with docs in their repo ** Work has stalled on the Ironic docs, we need to pick this up again. Contact me if you want to know more, or are willing to help out. * Improve how we communicate with and support our corporate contributors ** I have been brainstorming ideas with Foundation, watch this space! * Improve communication with Docs Liaisons ** I'm very pleased to see liaisons getting more involved in our bugs and reviews. Keep up the good work! * Clearing out old bugs ** Sadly, no action on the spotlight bugs this week. Perhaps we're all worn out from the RST conversions? I'll keep the current three bugs for this week, to give everyone a little more time. == RST Migration == With the Cloud Admin Guide complete, we are now working on the Install Guide, HA Guide, and the Security Guide. If you would like to assist, please get in touch with the appropriate speciality team: * Install Guide: ** Contact Karin Levenstein <karin.levenstein(a)rackspace.com> ** Sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Installation_Guide_Mi… * HA Guide ** Contact Meg McRoberts <dreidellhasa(a)yahoo.com> or Matt Griffin <me(a)mattgriffin.com> ** Blueprint: https://blueprints.launchpad.net/openstack-manuals/+spec/improve-ha-guide * Security Guide ** Contact Nathaniel Dillon <nathaniel.dillon(a)hp.com> ** Info: https://etherpad.openstack.org/p/sec-guide-rst For books that are now being converted, don't forget that any change you make to the XML must also be made to the RST version until conversion is complete. Our lovely team of cores will be keeping an eye out to make sure loose changes to XML don't pass the gate, but try to help them out by pointing out both patches in your reviews. == Training Guides == I've been working with the Training Guides group and the docs core team to determine the best way to move forward with the Training Guides project. At this stage, we're planning on breaking the project up into a few distinct parts, and bringing Training Guides back into the documentation group as a speciality team. If you have any opinions or ideas on this, feel free to contact me so I can make sure we're considering all the options. == APAC Docs Swarm == We're less than a week away from the APAC doc swarm! This time we'll be working on the Architecture Design Guide. It's to be held at the Red Hat office in Brisbane, on 13-14 August. Check out http://openstack-swarm.rhcloud.com/ for all the info and to RSVP. == Core Team Changes == This month, we welcome KATO Tomoyuki on to our docs core team. Thanks for all your hard work Tomoyuki-san, and welcome to the team! == Doc team meeting == The APAC meeting was held this week. Read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-08-05 The next meetings are: US: Wednesday 12 August, 14:00:00 UTC APAC: Wednesday 19 August, 00:30: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… == Spotlight bugs for this week == Let's give these three a little more oxygen: https://bugs.launchpad.net/openstack-manuals/+bug/1257018 VPNaaS isn't documented in cloud admin https://bugs.launchpad.net/openstack-manuals/+bug/1257656 VMware: add support for VM diagnostics https://bugs.launchpad.net/openstack-manuals/+bug/1261969 Document nova server package - -- Remember, if you have content you would like to add to this newsletter, or you would like to be added to the distribution list, please email me directly at openstack(a)lanabrindley.com, or visit: https://wiki.openstack.org/w/index.php?title=Documentation/WhatsUpDoc Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVxFJBAAoJELppzVb4+KUy9d8IAKgEM8succPKaPrmFzY1V5cS 402VF4uR8XzelkkJWQWCG6U1OWP+m6X3n5SFuFraZKLCQmUXL0HG0L3PrLB7eryT 0VKDiGTKcPW5MukLUtKRdkqoyJ5GYWTO6oT3l07tqkCWuGTI5Chp0gcOJDG2spLi D8BAGAlQ42E+2NqgaxTmU+7uE60CyzXBXsquLcxwnuRr1ih18S5N8Cxkks17XOkL XSejUisrRVX4lpVdCZw/VdXCBQ6+4YLC9xdnfpPWgXsAc2npPdrUfwju9Tf4JHxF OmrAQ1igdYDd3KJP4H6tQcIabN5HZuAseOEGZFtWu6bnteyh/1Vz2RI+lUBNo/E= =TmFH -----END PGP SIGNATURE-----

1 0

oslo.i18n now support contextual and plural messages
by Peng Wu 06 Aug '15

06 Aug '15

Hi, The oslo.i18n library already supports standard gettext message. Now the contextual and plural messages are also supported now, which is needed for better translation quality. For more information: http://git.openstack.org/cgit/openstack/oslo.i18n/tree/doc/source/gui delines.rst#n18 http://git.openstack.org/cgit/openstack/oslo-specs/tree/specs/liberty /more-gettext-support.rst Feel free to comment it. Best Regards, Peng Wu

1 0

Admin Guide Cloud RST conversion
by Andreas Jaeger 05 Aug '15

05 Aug '15

The Admin Guide Cloud has been converted to RST and the team is doing the final review now. I've created a new resource admin-guide-cloud-rst for translation and synced the existing matching translations over. We will soon remove the old admin-guide-cloud - and afterwards move admin-guide-cloud-rst to admin-guide-cloud. For now I suggest to not touch these guides and wait until we're finished with the final cleanup. And then I'll send out a note again, 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, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 0

IRC meeting tomorrow
by Ying Chun Guo 05 Aug '15

05 Aug '15

Hello, team We will have the IRC meeting at UTC 0600 in the channel #openstack-meeting, on August 6th. I'm going to cover following topics: * Prioritise requirements/bugs of Zanata server * Progress track on two bp: "translation check website" and "translation metric" * Open discussions If you have other topics, feel free to propose. Best regards Ying Chun Guo (Daisy)

1 0

Glance needs some fields in JSON files translated.
by Okuma, Wayne 05 Aug '15

05 Aug '15

Hi i18n team, My name is Wayne Okuma. I work with the Glance team and am focused on Glance's Metadata Definition (metadef) Library support. We currently have ~20 metadef JSON files which are loaded into the Glance database. We would like to have some of the fields in the JSON files localized. I'm not clear what the process is for getting the glance.po file uploaded to Transifex. I have a pybabel extractor that can generate a "glance-json.pot" with just the fields I'm interested in localizing and am wondering what the steps would be for me to get it uploaded to Transifex. Also, although I can manually run the extraction routine, is there a way this can be done automatically? Thanks for any information you can provide. Wayne Okuma

3 4

Renaming IRC channel?
by Adrien Cunin 02 Aug '15

02 Aug '15

Hi, Following a recent discussion, I was going to make sure the team IRC channel is logged at http://eavesdrop.openstack.org/. Then I realized the IRC channel name #openstack-translation is not really consistent with the project team name "i18n" and the mailing-list name "openstack-i18n". Would it make sense to rename the IRC channel to #openstack-i18n? Thanks, Adrien

3 9

What's Up, Doc? 31 July 2015
by Lana Brindley 31 Jul '15

31 Jul '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, This week, like last, was all about the RST conversion. With just a 48 hour long sprint, the Install Guide is almost complete! A hearty congratulations to everyone who contributed. One of the interesting things about doing all these conversions is the amount of conversation it has started about our conventions, and I'm pleased to see that we're really starting to get a feel for how RST can work for us, and what we can demand of it. It's also great to see some related changes to the sphinx theme that handles how we display our shiny RST books. == Progress towards Liberty == 75 days to go! * RST conversion: ** Install Guide: Conversion is nearly done, sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Installation_Guide_Mi… ** Cloud Admin Guide: is nearly done. Sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Cloud_Admin_Guide_Mig… ** HA Guide: is also nearly done. Get in touch with Meg or Matt: https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update ** Security Guide: Conversion is now underway, sign up here: https://etherpad.openstack.org/p/sec-guide-rst * User Guides information architecture overhaul ** Waiting on the RST conversion of the Cloud Admin Guide to be complete * Greater focus on helping out devs with docs in their repo ** Work has stalled on the Ironic docs, we need to pick this up again. Contact me if you want to know more, or are willing to help out. * Improve how we communicate with and support our corporate contributors ** I have been brainstorming ideas with Foundation, watch this space! * Improve communication with Docs Liaisons ** I'm very pleased to see liaisons getting more involved in our bugs and reviews. Keep up the good work! * Clearing out old bugs ** Thanks to Brian for picking up one of the spotlight bugs from last week. Three new bugs to look at this week. == RST Migration == The next books we are focusing on for RST conversion are the Install Guide, Cloud Admin Guide, HA Guide, and the Security Guide. If you would like to assist, please get in touch with the appropriate speciality team: * Install Guide: ** Contact Karin Levenstein <karin.levenstein(a)rackspace.com> ** Sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Installation_Guide_Mi… * Cloud Admin Guide: ** Contact Brian Moss <kallimachos(a)gmail.com> & Joseph Robinson <joseph.r.email(a)gmail.com> ** Sign up to help out here: https://wiki.openstack.org/wiki/Documentation/Migrate#Cloud_Admin_Guide_Mig… * HA Guide ** Contact Meg McRoberts <dreidellhasa(a)yahoo.com> or Matt Griffin <me(a)mattgriffin.com> ** Blueprint: https://blueprints.launchpad.net/openstack-manuals/+spec/improve-ha-guide * Security Guide ** Contact Nathaniel Dillon <nathaniel.dillon(a)hp.com> ** Info: https://etherpad.openstack.org/p/sec-guide-rst For books that are now being converted, don't forget that any change you make to the XML must also be made to the RST version until conversion is complete. Our lovely team of cores will be keeping an eye out to make sure loose changes to XML don't pass the gate, but try to help them out by pointing out both patches in your reviews. == Docs Tools == Thanks to Dave for picking up a bug this week and adding a navigation bar to the sidepane of the docs theme for our RST books. We should be releasing an updated docs theme shortly so you can play with this new functionality. In the meantime, if you have suggestions for the docs theme, raise the issue on the docs mailing list, or go right ahead and create a bug for it. == APAC Docs Swarm == The APAC team have been working on holding another doc swarm, this time working on the Architecture Design Guide. It's to be held at the Red Hat office in Brisbane, on 13-14 August. Check out http://openstack-swarm.rhcloud.com/ for all the info. == Doc team meeting == The US meeting got cancelled this week. The next meetings are: APAC: Wednesday 5 August, 00:30:00 UTC US: Wednesday 12 August, 14:00: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… == Spotlight bugs for this week == Three new spotlight bugs for you to sink your teeth into: https://bugs.launchpad.net/openstack-manuals/+bug/1257018 VPNaaS isn't documented in cloud admin https://bugs.launchpad.net/openstack-manuals/+bug/1257656 VMware: add support for VM diagnostics https://bugs.launchpad.net/openstack-manuals/+bug/1261969 Document nova server package - -- Remember, if you have content you would like to add to this newsletter, or you would like to be added to the distribution list, please email me directly at openstack(a)lanabrindley.com, or visit: https://wiki.openstack.org/w/index.php?title=Documentation/WhatsUpDoc Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVuySjAAoJELppzVb4+KUymgUH/Rfh9srfYeY+tzgE1lHm5XW1 USac40LqOOT9TtBtepqxTO3JlqNt5DusYy/TPMp5U0ctqOuzy4UQPPR0WljjBSNe nV3uspX6CNzhbWGAtF96a5Tv/d7VDyWvc8p8VyHV18dgOk5rgtbO7IixgoFh9tWs MQoEvhsH3PwK9UTk0+LJZ2qlYX1NCXJH1KeTrqq/uy76EUFGjSfrNHWu4BxmHPhO hDbpuFMTRM9mvGrYG0gu+tvlOGHMIf3tngPa1Zslhg8Y3xgvSBiCgWeJR1sCokOi 6RVFMMayX+dLU9JEEl6+kIZ4ID+eIvNQErMu/4EfZKlN3S+Y8LroxzF8CZCqCc4= =0MR8 -----END PGP SIGNATURE-----

1 0

Fwd: [openstack-dev] [security] [docs] Security Guide Freeze and RST migration
by Andreas Jaeger 28 Jul '15

28 Jul '15

FYI, I suggest you stop translation and start once the RST conversion is done. Currently the RST files are not in transifex, I'll wait for the conversion to finish, Andreas -------- Forwarded Message -------- Subject: [openstack-dev] [security] [docs] Security Guide Freeze and RST migration Date: Tue, 21 Jul 2015 14:46:33 +0000 From: Dillon, Nathaniel <nathaniel.dillon(a)hp.com> Reply-To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> To: OpenStack Development Mailing List <openstack-dev(a)lists.openstack.org> All, The OpenStack Security Guide is migrating to RST format [1] and with help from the docs team we hope to have this completed shortly. We will therefore be entering a freeze on all changes coming into the Security Guide until the migration is complete, and all future changes will be in the much easier RST format. Progress can be tracked on the etherpad [2] or specific issues can be asked in reply to this message or during the Security Guide weekly meeting [3], and an announcement will be made when the migration is complete. Thanks, Nathaniel [1] https://bugs.launchpad.net/openstack-manuals/+bug/1463111 [2] https://etherpad.openstack.org/p/sec-guide-rst [3] https://wiki.openstack.org/wiki/Documentation/SecurityGuide __________________________________________________________________________ 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 -- 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, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 1

What's Up, Doc? 24 July 2015
by Lana Brindley 24 Jul '15

24 Jul '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, Wow! What a great week for RST conversion patches! As I write this, there are only a handful of outstanding sections on the Cloud Admin and HA Guides, and well over 40 sections have now been converted on the Install Guide, with the conversion sprint running for another twelve hours or so. Thank you to everyone who has taken the time to grab a section and do a conversion, and to all those people who have given their +1 to a patch. I can't wait to see all our shiny new books up on docs.openstack.org :) == Progress towards Liberty == * RST conversion: ** Install Guide: Conversion is now underway, sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Installation_Guide_Mi… ** Cloud Admin Guide: is nearly done. Sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Cloud_Admin_Guide_Mig… ** HA Guide: is also nearly done. Get in touch with Meg or Matt: https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update ** Security Guide: Conversion is now underway, sign up here: https://etherpad.openstack.org/p/sec-guide-rst * User Guides information architecture overhaul ** Waiting on the RST conversion of the Cloud Admin Guide to be complete * Greater focus on helping out devs with docs in their repo ** Work has stalled on the Ironic docs, we need to pick this up again. Contact me if you want to know more, or are willing to help out. * Improve how we communicate with and support our corporate contributors ** I have been brainstorming ideas with Foundation, watch this space! * Improve communication with Docs Liaisons ** I'm very pleased to see liaisons getting more involved in our bugs and reviews. Keep up the good work! * Clearing out old bugs ** Sadly, no progress on the spotlight bugs from last week. I'll hold them over for another week, so now is your chance to jump in and grab them! == RST Migration == The next books we are focusing on for RST conversion are the Install Guide, Cloud Admin Guide, HA Guide, and the Security Guide. If you would like to assist, please get in touch with the appropriate speciality team: * Install Guide: ** Contact Karin Levenstein <karin.levenstein(a)rackspace.com> ** Sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Installation_Guide_Mi… ** The sprint on this book has been a major success, and there's still about twelve hours left until it wraps up at 1500 UTC (24 July). Info and sign up here: https://wiki.openstack.org/wiki/VirtualSprints#Installation_guide_conversio… * Cloud Admin Guide: ** Contact Brian Moss <kallimachos(a)gmail.com> & Joseph Robinson <joseph.r.email(a)gmail.com> ** Sign up to help out here: https://wiki.openstack.org/wiki/Documentation/Migrate#Cloud_Admin_Guide_Mig… * HA Guide ** Contact Meg McRoberts <dreidellhasa(a)yahoo.com> or Matt Griffin <me(a)mattgriffin.com> ** Blueprint: https://blueprints.launchpad.net/openstack-manuals/+spec/improve-ha-guide * Security Guide ** Contact Nathaniel Dillon <nathaniel.dillon(a)hp.com> ** Info: https://etherpad.openstack.org/p/sec-guide-rst For books that are now being converted, don't forget that any change you make to the XML must also be made to the RST version until conversion is complete. Our lovely team of cores will be keeping an eye out to make sure loose changes to XML don't pass the gate, but try to help them out by pointing out both patches in your reviews. == HA Guide Works == With the RST conversion on the HA Guide wrapping up, the HA Guide speciality team are looking for people to help out with the reorganisation and writing the new content. They have quite a few bugs to get through, and they need your help! Contact Matt Griffin, or any other member of the HA Guide Speciality Team, or join their weekly IRC meeting. Details here: https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update == Docs Tools == While they're not strictly docs tools, I wanted to mention review dashboards here today. Did you know that we maintain a list of custom OpenStack review dashboards for you to use? They're customised to show only the reviews you care about, which can save you a lot of time and needless clicking. All you need to do is pick the dashboard you want to use, copy the URL, and save it to your bookmarks. Anne has just updated the Docs Review Inbox dashboard to include DocImpact reviews, so it's worth checking out: http://ghostcloud.net/openstack_gerrit_dashboards/dashboard_doc-program.html You can see the full list here: http://ghostcloud.net/openstack_gerrit_dashboards/ == APAC Docs Swarm == The APAC team have been working on holding another doc swarm, this time working on the Architecture Design Guide. It's to be held at the Red Hat office in Brisbane, on 13-14 August. Check out http://openstack-swarm.rhcloud.com/ for all the info. == Doc team meeting == The APAC docs meeting was held this week, catch up on the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-07-22 The next meetings are: US: Wednesday 29 July, 14:00:00 UTC APAC: Wednesday 5 August, 00:30: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… == Spotlight bugs for this week == Giving these three poor old bugs some extra oxygen: https://bugs.launchpad.net/openstack-manuals/+bug/1241116 Using policies for protected properties https://bugs.launchpad.net/openstack-manuals/+bug/1241179 Add notifications for groups and roles https://bugs.launchpad.net/openstack-manuals/+bug/1251060 Xenapi: Allow windows builds with xentools 6.1 and 6.2 - -- Remember, if you have content you would like to add to this newsletter, or you would like to be added to the distribution list, please email me directly at openstack(a)lanabrindley.com, or visit: https://wiki.openstack.org/w/index.php?title=Documentation/WhatsUpDoc Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVsasKAAoJELppzVb4+KUyDJ0H/jZFcRFiwCljVZiNAyGAz1KY 1pb0TF/e42jImw1H89aGXs9QvNIUqDFOuLp+iCWGh5UKPFH/p2R1j1pv3a0lZk8y dhUjwVEpXJXgW5cFAYSiq3x7yKa8d0HIQtDTsJT78uckR0TbI55IXG8J117fcD3e yLY4AJNNyX9SGtAUKMy6wdalAdv5+bkKbDfuCPRwOHxfi5Rvy0XWxC+ufvt8muZf Qt8AiDSsTrLrWyaocunpTU2QA8+EA3cxnKEv/TL2tThuLfAVB3JWmU8pGjiL9fpx xgt1V+c30hcKQQ+RumcEobuU/zjLCi19VzFH7RaaS3X/FWM0vskmrAApklm3czE= =P15L -----END PGP SIGNATURE-----

1 0

What's Up, Doc? 17 July 2015
by Lana Brindley 17 Jul '15

17 Jul '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, I'm very pleased to announce that we finally have a name for our M release: Mitaka (三鷹)! Accordingly, the Tokyo Summit for the Mitaka release is only just over 100 days away. CFP closed a couple of days ago, and I've noticed that the first round of ATC discount codes have gone out. If you haven't got yours yet, then keep patching Liberty and sit tight. The discount codes will come out in stages after every snapshot. This week, we've had some great discussions about networking scenarios in the Install Guide, and the best way to include RST files in our newly converted books. We also have both the HA Guide and the Cloud Admin Guide conversions in their final stages, and the Install Guide conversion sprint coming up. Very exciting! == Progress towards Liberty == * RST conversion: ** Install Guide: Conversion is now underway, sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Installation_Guide_Mi… ** Cloud Admin Guide: is nearly done. Sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Cloud_Admin_Guide_Mig… ** HA Guide: is also nearly done. Get in touch with Meg or Matt: https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update ** Security Guide: Spec has merged. Planning is happening here: https://etherpad.openstack.org/p/sec-guide-rst * User Guides information architecture overhaul ** Waiting on the RST conversion of the Cloud Admin Guide to be complete * Greater focus on helping out devs with docs in their repo ** Work has stalled on the Ironic docs, we need to pick this up again. Contact me if you want to know more, or are willing to help out. * Improve how we communicate with and support our corporate contributors ** I have been brainstorming ideas with Foundation, watch this space! * Improve communication with Docs Liaisons ** I'm very pleased to see liaisons getting more involved in our bugs and reviews. Keep up the good work! * Clearing out old bugs ** A small amount of progress on the old bugs we held over from last week. New ones to check out in this newsletter! == RST Migration == The next books we are focusing on for RST conversion are the Install Guide, Cloud Admin Guide, HA Guide, and the Security Guide. If you would like to assist, please get in touch with the appropriate speciality team: * Install Guide: ** Contact Karin Levenstein <karin.levenstein(a)rackspace.com> ** Sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Installation_Guide_Mi… ** There's a sprint happening on this book later next week. Info and sign up here: https://wiki.openstack.org/wiki/VirtualSprints#Installation_guide_conversio… * Cloud Admin Guide: ** Contact Brian Moss <kallimachos(a)gmail.com> & Joseph Robinson <joseph.r.email(a)gmail.com> ** ** Sign up to help out here: https://wiki.openstack.org/wiki/Documentation/Migrate#Cloud_Admin_Guide_Mig… * HA Guide ** Contact Meg McRoberts <dreidellhasa(a)yahoo.com> or Matt Griffin <me(a)mattgriffin.com> ** Blueprint: https://blueprints.launchpad.net/openstack-manuals/+spec/improve-ha-guide * Security Guide ** Contact Nathaniel Dillon <nathaniel.dillon(a)hp.com> ** Bug: https://bugs.launchpad.net/openstack-manuals/+bug/1463111 ** Info: https://etherpad.openstack.org/p/sec-guide-rst For books that are now being converted, don't forget that any change you make to the XML must also be made to the RST version until conversion is complete. Our lovely team of cores will be keeping an eye out to make sure loose changes to XML don't pass the gate, but try to help them out by pointing out both patches in your reviews. == Install Guide RST Conversion Sprint == In order to kick off the RST conversion of the Install Guide, the speciality team have decided to run a virtual conversion sprint over two days on July 22-24. For more information, see the https://wiki.openstack.org/wiki/VirtualSprints#Installation_guide_conversio… wiki page, and the https://etherpad.openstack.org/p/installguide-rst-virtual-sprint etherpad. == HA Guide Works == With the RST conversion on the HA Guide wrapping up, the HA Guide speciality team are looking for people to help out with the reorganisation and writing the new content. They have quite a few bugs to get through, and they need your help! Contact Matt Griffin, or any other member of the HA Guide Speciality Team, or join their weekly IRC meeting. Details here: https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update == Docs Tools == Last week, we released openstackdocstheme 1.1.0, see http://lists.openstack.org/pipermail/openstack-announce/2015-June/000392.ht…. The main new features in this release are improvements for bug reporting, variable lists like the glossary are now indented, and next/prev links are now icons on the upper right part of the page. Additionally, the stable/icehouse branch of openstack-manuals has been EOLed, no further updates will be done from it. For more information, see http://lists.openstack.org/pipermail/openstack-infra/2015-July/002888.html == Doc team meeting == The next meetings are: APAC: Wednesday 22 July, 00:30:00 UTC US: Wednesday 29 July, 14:00: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… == Spotlight bugs for this week == We've now got people assigned to work on last week's old bugs, which is great! Here are three more rusty old bugs that could use some love: https://bugs.launchpad.net/openstack-manuals/+bug/1241116 Using policies for protected properties https://bugs.launchpad.net/openstack-manuals/+bug/1241179 Add notifications for groups and roles https://bugs.launchpad.net/openstack-manuals/+bug/1251060 Xenapi: Allow windows builds with xentools 6.1 and 6.2 - -- Remember, if you have content you would like to add to this newsletter, or you would like to be added to the distribution list, please email me directly at openstack(a)lanabrindley.com, or visit: https://wiki.openstack.org/w/index.php?title=Documentation/WhatsUpDoc Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVqJabAAoJELppzVb4+KUyDkoIAKIiNrURthUi+Dzj86zkfQHA dKOHDBIfGmeDgQ059EE+oiuJI8qM+xqvz7zTXAGFhMDzEQ4rfx1lJd6UWwyohwdJ 80hNK696YjsKIIHelN+7zFuzG6jdWHtx9mdVLbnaBU+k0HYDRIEmkyIlRw9WIJRD YKCRvvijN0Dgwj5EQoyFYSM3/6BQlO1jyX2qf8zUkTjbKKr5d1yJqAnzAXEz0rD0 Hwa7CKVJXaxs1dIF9kdgYFqp+tUHfCRnfD8kQ+CgDpZiZmraXe8mgXFCoSufKCxW FkqfADfnRWHywnC/G9EtlOWdy8tLsM2CB7GZcicvVIAYIRa3ws/xy6JI/C/fsRU= =4chR -----END PGP SIGNATURE-----

1 0

IRC meeting on Thursday
by Ying Chun Guo 16 Jul '15

16 Jul '15

Hello, team We will have the IRC meeting at UTC 1300 in the channel #openstack-meeting, on July 16th. I'm going to cover following topics: * Zanata trial feedback collection * Steps to get translators as "ATC" * Progress track on two bp: "translation check website" and "translation metric" * Open discussions If you have other topics, feel free to propose. Best regards Ying Chun Guo (Daisy)

1 0

Turkey Horizon translation broken
by Akihiro Motoki 15 Jul '15

15 Jul '15

Hi Turkey language team and I18N whole team, Horizon daily translation import patch [1] detects an translation error that turkey translation has invalid message format string. It is detected in "check-tempest-dsvm-full" job [2], more precisely [3]. It is an expected behavior, but my question is how we should deal with. Is there any defined process? AFAIK we have never had this kind of discussion. Ideally, it is great that Turkey team can take an action soon. On the other hand, we need to have a process as the I18N project because this blocks translations of all languages. Transifex administrators can delete such translations, but I would like to see the consensus. [1] https://review.openstack.org/#/c/200793/ [2] http://logs.openstack.org/93/200793/4/check/check-tempest-dsvm-full/33e49b1/ [3] http://logs.openstack.org/93/200793/4/check/check-tempest-dsvm-full/33e49b1… Thanks, Akihiro

3 4

Hungarian Translation Team
by Gergely Szalay 15 Jul '15

15 Jul '15

Hi, We noticed that there is no Hungarian Translation Team yet, so we would like to form it. The Team would consist of: Translator: Szilvia Racz (id: sziike) Szilvia works as a Technical Consultant at HP and SDN expert Coordinator: Gergely Szalay (id:gergelys) Manager in IT/Cloud industry, Organizer of the Hungarian OpenStack user group. Reviewer: we are constantly looking for reviewers to join the team. Looking forward to work with you! Thank you, Gergely and Szilvia

2 1

What's Up, Doc? 10 July 2015
by Lana Brindley 10 Jul '15

10 Jul '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, First of all, apologies for my absence over the past couple of weeks. I took some time off to spend with my daughter while she was on school holidays, and then got ill! It never rains but it pours ;) While I was out, our M release was named, and then unnamed, and we're now waiting for a new name. We also had a great discussion about which networking scenario is the best fit for our new-and-improved Installation Guide, and planned a sprint to get the RST conversion for that book happening. More on that in this newsletter. == Progress towards Liberty == * RST conversion: ** Install Guide: Conversion is now underway, sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Installation_Guide_Mi… ** Cloud Admin Guide: is nearly done. Sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Cloud_Admin_Guide_Mig… ** HA Guide: is also underway. Get in touch with Meg or Matt: https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update ** Security Guide: In planning. Stand by for more info. * User Guides information architecture overhaul ** Waiting on the RST conversion of the Cloud Admin Guide to be complete * Greater focus on helping out devs with docs in their repo ** Work has started on the Ironic docs, we're now trying to resolve some issues with service name standards ("Bare Metal" or "Bare metal"?). Contact me if you want to know more, or are willing to help out. * Improve how we communicate with and support our corporate contributors ** I have been brainstorming ideas with Foundation, watch this space! * Improve communication with Docs Liaisons ** I'm very pleased to see liaisons getting more involved in our bugs and reviews. Keep up the good work! * Clearing out old bugs ** Sadly, no progress this week. == RST Migration == The next books we are focusing on for RST conversion are the Install Guide, Cloud Admin Guide, HA Guide, and the Security Guide. If you would like to assist, please get in touch with the appropriate speciality team: * Install Guide: ** Contact Karin Levenstein <karin.levenstein(a)rackspace.com> ** Sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Installation_Guide_Mi… ** There's a sprint happening on this book later this month. Info and sign up here: https://wiki.openstack.org/wiki/VirtualSprints#Installation_guide_conversio… * Cloud Admin Guide: ** Contact Brian Moss <kallimachos(a)gmail.com> & Joseph Robinson <joseph.r.email(a)gmail.com> ** Sign up to help out here: https://wiki.openstack.org/wiki/Documentation/Migrate#Cloud_Admin_Guide_Mig… * HA Guide ** Contact Meg McRoberts <dreidellhasa(a)yahoo.com> or Matt Griffin <me(a)mattgriffin.com> ** Blueprint: https://blueprints.launchpad.net/openstack-manuals/+spec/improve-ha-guide * Security Guide ** Contact Nathaniel Dillon <nathaniel.dillon(a)hp.com> ** Bug: https://bugs.launchpad.net/openstack-manuals/+bug/1463111 ** Spec: https://review.openstack.org/#/c/196165/ For books that are now being converted, don't forget that any change you make to the XML must also be made to the RST version until conversion is complete. Our lovely team of cores will be keeping an eye out to make sure loose changes to XML don't pass the gate, but try to help them out by pointing out both patches in your reviews. == Install Guide RST Conversion Sprint == In order to kick off the RST conversion of the Install Guide, the speciality team have decided to run a virtual conversion sprint over two days on July 22-24. For more information, see the https://wiki.openstack.org/wiki/VirtualSprints#Installation_guide_conversio… wiki page, and the https://etherpad.openstack.org/p/installguide-rst-virtual-sprint etherpad. == New core team == The core team have just completed our review for July, and would like to welcome two new core contributors: Alexandra Settle, and Olena Logvinova. Congratulations to you both :) == Doc team meeting == The APAC meeting was cancelled this week, our next meetings are: US: Wednesday 15 July, 14:00:00 UTC (note that this has NOT changed with daylight savings time) APAC: Wednesday 22 July, 00:30: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… == Spotlight bugs for this week == Sadly, even with an extra week, our three spotlight bugs remain unloved. I'm going to keep them here for another week, so now is your chance to swoop in and make a difference! https://bugs.launchpad.net/openstack-manuals/+bug/1212349 vmware documentation https://bugs.launchpad.net/openstack-manuals/+bug/1212687 xenapi https://bugs.launchpad.net/openstack-manuals/+bug/1239308 Add notifications for groups and roles - -- Remember, if you have content you would like to add to this newsletter, or you would like to be added to the distribution list, please email me directly at openstack(a)lanabrindley.com, or visit: https://wiki.openstack.org/w/index.php?title=Documentation/WhatsUpDoc Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVnyqlAAoJELppzVb4+KUy2S4H/3dhgq6wspQhEYBTBvSc2n3k LJt9DjOBhCPfZk/hBTuDYRmrQw4os+URwFmUiQTAgeuTF6HEyGnHZ/19bY3eEYVL Hv271jMPlTIp1CmzVoMflmWEO6ppIstcZQEJLbJnu6xkN9n9uT+mQKtomplsypt6 sLptEBilSnr/ZLYPutrsGioMQrn8w7LMSFQvr56br0z0pr3CG8oZxktsFYC6GbM/ HuRqPnRLSUI1y54ieH/t0QwR+89rKP0OwTqkON53flA3SwPddduo9GEvQm33uZUx 1TdWeHG70dXIwEArvYncQ+9dHsQ7XGtBztdnpD6p5/YzesQC4VwXhteBpGezVs4= =zYRD -----END PGP SIGNATURE-----

1 0

localised API message responses - possible?
by Tom Fifield 04 Jul '15

04 Jul '15

Hi all, I'm just going through old questions on Ask OpenStack, and thought we might have an answer for this one: https://ask.openstack.org/en/question/4346/is-there-a-way-of-passing-the-la… I wanted to know if it is possible to get the localized openstack messages when I make a openstack REST API call? If so how can I pass the language header? Regards, Tom

3 2

IRC meeting tomorrow
by Ying Chun Guo 01 Jul '15

01 Jul '15

Hello, team We will have the IRC meeting at UTC 0600 in the channel #openstack-meeting, on July 2nd. I'm going to cover following topics: * Feature design: translation metrics in stackalytics * Open discussions If you have other topics, feel free to propose. Best regards Ying Chun Guo (Daisy)

1 0

What's Up, Doc? 26 June 2015
by Lana Brindley 26 Jun '15

26 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, First of all, our M release has been named! Sadly, it hasn't cleared legal yet, so we can't publicly announce it, however, here are the poll results: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4983776e190c8dbc It was a close-run contest! This week, I've been continuing to dust off some old bugs, and have been chatting to a few of our docs liaisons to work out how we can best get them engaged with what we're working on. I've also been spending a lot of time on standards questions, and thinking about the future of the DocImpact flag. == Progress towards Liberty == * RST conversion: ** Install Guide: Conversion is now ready to start, sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Installation_Guide_Mi… ** Cloud Admin Guide: is chugging along. Sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Cloud_Admin_Guide_Mig… ** HA Guide: is also underway. Get in touch with Meg or Matt: https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update ** Security Guide: In planning. Stand by for more info. * User Guides information architecture overhaul ** Waiting on the RST conversion of the Cloud Admin Guide to be complete * Greater focus on helping out devs with docs in their repo ** Work has started on the Ironic docs, we're now trying to resolve some issues with service name standards ("Bare Metal" or "Bare metal"?). Contact me if you want to know more, or are willing to help out. * Improve how we communicate with and support our corporate contributors ** No progress this week * Improve communication with Docs Liaisons ** I'm very pleased to see liaisons getting more involved in our bugs and reviews. Keep up the good work! * Clearing out old bugs ** Thanks to Yusuke-san for closing bug 1330005! == RST Migration == The next books we are focusing on for RST conversion are the Install Guide, Cloud Admin Guide, HA Guide, and the Security Guide. If you would like to assist, please get in touch with the appropriate speciality team: * Install Guide: ** Contact Karin Levenstein <karin.levenstein(a)rackspace.com> ** Sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Installation_Guide_Mi… * Cloud Admin Guide: ** Contact Brian Moss <kallimachos(a)gmail.com> & Joseph Robinson <joseph.r.email(a)gmail.com> ** Sign up to help out here: https://wiki.openstack.org/wiki/Documentation/Migrate#Cloud_Admin_Guide_Mig… * HA Guide ** Contact Meg McRoberts <dreidellhasa(a)yahoo.com> or Matt Griffin <me(a)mattgriffin.com> ** Blueprint: https://blueprints.launchpad.net/openstack-manuals/+spec/improve-ha-guide * Security Guide ** Contact Nathaniel Dillon <nathaniel.dillon(a)hp.com> ** Bug: https://bugs.launchpad.net/openstack-manuals/+bug/1463111 ** Blueprint+Spec: TBD For books that are now being converted, don't forget that any change you make to the XML must also be made to the RST version until conversion is complete. Our lovely team of cores will be keeping an eye out to make sure loose changes to XML don't pass the gate, but try to help them out by pointing out both patches in your reviews. == Docs Tools == Andreas and Nick just released openstack-docs-tools 0.29.1, after we discovered an RST translation bug in 0.29. Thanks for the quick turnaround on that! == Documentation Standards == There's been quite a lot of conversation this week over capitalisation of service names, with the community divided down the middle as to which we prefer! While we all enjoy a good style discussion, I've also asked Anne (in her role on the TC) to confirm the legal restrictions for us. Watch this space! In the meantime, continue to discuss this on the mailing list :) == Docs Liaisons == Don't forget that we have subject matter experts to help you with documentation questions that you might have. One of the best ways to get our liaisons' attention is to add them to a bug or a patch. Feel free to look up the liaison for the project you're working with, and add them to the cc list for your patch: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation == Doc team meeting == The APAC meeting was held this week, see the minutes here to catch up: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-06-24 Next meetings are: US: Wednesday 1 July, 14:00:00 UTC (note that this has NOT changed with daylight savings time) APAC: Wednesday 8 July, 00:30: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… == Spotlight bugs for this week == Of the three bugs we spotlighted last week, one of them was closed (thanks Yusuke-san!), and the other two are still up for grabs. Olga is working on a Spotlight bug from last week, too. Let's keep the momentum, with another three sad old bugs that could use some love: https://bugs.launchpad.net/openstack-manuals/+bug/1212349 vmware documentation https://bugs.launchpad.net/openstack-manuals/+bug/1212687 xenapi https://bugs.launchpad.net/openstack-manuals/+bug/1239308 Add notifications for groups and roles - -- Remember, if you have content you would like to add to this newsletter, or you would like to be added to the distribution list, please email me directly at openstack(a)lanabrindley.com, or visit: https://wiki.openstack.org/w/index.php?title=Documentation/WhatsUpDoc Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVjOGvAAoJELppzVb4+KUy+3EH/RkUHZwCY6VS43k36x/d0ue9 Zl2Y8d9OJPZwElmhQ7Zl+LOpM1k+vpYDJs6WiCGiGsLVdg8tJX6bdoW1QZwH6+dV d2qR0yOitQ1/Z2W8y2EK6yAjMmLy7GU3fQBVi742A3g7V0FtbSduCEUwEWBdAv6A hIMY5nr5nXX0X0oiDro6XcdgHHLtIaFLpumbLE8AcPoYlAauaSjNyT7o4vKqz26u GxHioUtizv/G+fYWjeejQ3wFGRRbIU5H18h5ohPF4tPlUBKn3pHL7w9RCkzj/993 lJQh3fi4ONwIU0c5tHmqolXAAiWvzROf/l6da1BtSQeSp4qwR2XN+KcsZBQ1V/4= =Bq+e -----END PGP SIGNATURE-----

1 0

Help with RST translation tool chain needed
by Andreas Jaeger 22 Jun '15

22 Jun '15

The Japanese translation of the User Guide should be complete according to transifex but looking at docs.openstack.org/draft/ja/user-guide/ I see only a few words in Japanese. Building the guide locally, I see po files that are completely translated but somehow the sphinx tools are not picking these up properly. I'm puzzled on what's going wrong here. Is there anybody that can look at the RST building and tell us what's wrong - and fix if possible ;), please? Note to build the document locally yourself, you can run: tox -e buildlang -- ja 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, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 4

Terminologies
by Ying Chun Guo 20 Jun '15

20 Jun '15

Hello, In Vancouver translation workshop, we decided to compose the translation terminologies. I merged the terminologies used by Japanese team, German team and French team and made out the first version of translation terms. When we generate it, terminology will be the first contents to be translated in any translation teams. It is a good way to get the consistency among different translators and different translation resources. Please take a look and let me know if you have any comments and suggestions. https://docs.google.com/spreadsheets/d/1BRizUNhDLl_6NtsGconFkxsKUqAmEEGum9I… Best regards Ying Chun Guo (Daisy)

7 9

What's Up, Doc? 19 June 2015
by Lana Brindley 19 Jun '15

19 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, This week, I've been working on helping out the Ironic team to sort out their Install Guide (thanks have to go to Gauvain and Nick, who have offered to help out with writing assistance here), and trying to come up with some better ways to work with the i18n team, and our docs liaisons. More on all of that further in. == Progress towards Liberty == * RST conversion: ** Install Guide: Spec is merged, stand by for conversion to start ** Cloud Admin Guide: is well on the way. Get in touch with Brian or Joe, or sign up here: https://wiki.openstack.org/wiki/Documentation/Migrate#Cloud_Admin_Guide_Mig… ** HA Guide: is also underway. Get in touch with Meg or Matt: https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update ** Security Guide: In planning. Stand by for more info. * User Guides information architecture overhaul ** Waiting on the RST conversion of the Cloud Admin Guide to be complete * Greater focus on helping out devs with docs in their repo ** We now have a team starting to form to work on Ironic docs. Contact me if you want to know more, or are willing to help out. * Improve how we communicate with and support our corporate contributors ** No progress this week * Improve communication with Docs Liaisons ** I have now reached out to liaisons. More later in this newsletter. * Clearing out old bugs ** Thanks to Tom for closing bug 1195875. Let's keep up the great work! == RST Migration == The next books we are focusing on for RST conversion are the Install Guide, Cloud Admin Guide, HA Guide, and the Security Guide. If you would like to assist, please get in touch with the appropriate speciality team: * Install Guide: ** Contact Karin Levenstein <karin.levenstein(a)rackspace.com> ** Spec: https://review.openstack.org/#/c/183138/ ** Watch this space: https://wiki.openstack.org/wiki/Documentation/Migrate#Installation_Guide_Mi… * Cloud Admin Guide: ** Contact Brian Moss <kallimachos(a)gmail.com> & Joseph Robinson <joseph.r.email(a)gmail.com> ** Blueprint: https://blueprints.launchpad.net/openstack-manuals/+spec/reorganise-user-gu… ** Sign up to help out here: https://wiki.openstack.org/wiki/Documentation/Migrate#Cloud_Admin_Guide_Mig… * HA Guide ** Contact Meg McRoberts <dreidellhasa(a)yahoo.com> or Matt Griffin <me(a)mattgriffin.com> ** Blueprint: https://blueprints.launchpad.net/openstack-manuals/+spec/improve-ha-guide * Security Guide ** Contact Nathaniel Dillon <nathaniel.dillon(a)hp.com> ** Bug: https://bugs.launchpad.net/openstack-manuals/+bug/1463111 ** Blueprint+Spec: TBD For books that are now being converted, don't forget that any change you make to the XML must also be made to the RST version until conversion is complete. Our lovely team of cores will be keeping an eye out to make sure loose changes to XML don't pass the gate, but try to help them out by pointing out both patches in your reviews. == Docs Tools == Andreas will shortly be updating openstack-docs-tools to 0.29. == Docs Liaisons == Don't forget that we have subject matter experts to help you with documentation questions that you might have. As you're working on bugs, feel free to give them a quick ping or an email to ask questions. They promise not to laugh at you! https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation == i18n Team == At Summit, I spent a lot of time with Ying Chun Guo (Daisy) from the translation team, to try and come up with a way we can make sure our teams are working together better. To that end, we've got a few ideas we're going to be implementing over the next few weeks. First of all, this newsletter now goes direct to the the translation mailing list, as well the dev and doc lists (hi translators!). Secondly, Daisy is going to poll her team to identify an i18n documentation liaison, who will be the go-to person for all questions about translation for docs. The other thing we're going to do is to make sure we're helping the i18n team to keep their status page up to date: https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categori… If you're working on a doc that is translated, please check that table and make sure the translation team know what you're up to! This will help prevent needless effort on their part, which benefits us all in the end. == Doc team meeting == The US meeting was held this week, see the minutes here to catch up: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-06-17 Apologies for the timing confusion on that one, it seems as though daylight savings changes took us by surprise. For now, the meeting will remain at 1400UTC. If you would prefer it to be at a different time, bring it up on the mailing list, or in the next US meeting. Next meetings are: APAC: Wednesday 24 June, 00:30:00 UTC US: Wednesday 1 July, 14:00: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… == Spotlight bugs for this week == Of the three bugs we spotlighted last week, one of them got marked as invalid (thanks Tom!), and another is in progress with SME assistance (thanks Olga!). That's great! Here's another three dusty old bugs that could use a polish up: https://bugs.launchpad.net/openstack-manuals/+bug/1330005 Glance image properties and values (low hanging fruit) https://bugs.launchpad.net/openstack-manuals/+bug/1394397 Nova notification_driver https://bugs.launchpad.net/openstack-manuals/+bug/1205402 iPXE ISO boot support - -- Remember, if you have content you would like to add to this newsletter, or you would like to be added to the distribution list, please email me directly at openstack(a)lanabrindley.com, or visit: https://wiki.openstack.org/w/index.php?title=Documentation/WhatsUpDoc Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVg34hAAoJELppzVb4+KUyBWcIAM+914bjuU/6BwFQqWUwTiEA Ed5wAfdr55kE4QT6OZgaBWUH7e3qyjk6VHmfIKXKyoYaMXq82oT0gBEsJYH4PY46 q/lOYG9tkDUuPjA3i4ibPYClGfLC3Ku0zOdwG9alg/2AystOqW/VbGLRQLhHQavD JgZs5/iB8S1JvBhHEiAixMyRgM5NMuXiM/j6TXVTw1tSm3Iz1KRnm2z8RiYVxBYj 9HKHKNy50PFXpubnYYu+B6iBqWv2JggkeCYOL2G0MiQubdnoXekNCKxNlHKiaPPU xCTj3qzUNW/UJZHVLpQskuD736kli2pqkEbiCeuNcqd3VQicE6VvY3QV31kGU5c= =IC4Z -----END PGP SIGNATURE-----

1 0

Specialty teams connecting to translation team
by Anne Gentle 19 Jun '15

19 Jun '15

Hi all, I'm sitting here in Vancouver next to Daisy (Ying Chun Guo) who leads the i18N efforts for OpenStack. She would like each specialty team lead to connect with the i18N team to communicate the amount of change expected so that they can evaluate the timing of translation, and how much is done that can be translated. We also had a session with the i18N team and want to work on more communication with each team, and I think the specialty team leads are a great way to start that effort. Thoughts or ideas? Let us know. Thanks, Anne -- Anne Gentle annegentle(a)justwriteclick.com

4 6

common (RST) translation
by KATO Tomoyuki 18 Jun '15

18 Jun '15

Hi team, I'm translating User Guides (RST) recently. I found a below problem. Any thought? Problem: Each message catalog "pot" file contains all strings of the RST document, including "common" files (glossary and so on). In particular, "user-guide" and "user-guide-admin" resource at Transifex have same strings in "common" files respectively. This causes unintended inconsistency of translation. In fact, Japanese "user-guide" and "user-guide-admin" have different translated strings, which need to sync manually. Solution (just my idea): As is: 1. Sphinx(?) generates the "pot" file. 2. translate at Transifex. 3. Sphinx(?) merge the translated strings. To be: 1. Sphinx(?) generates the "pot" file. 2. A new script split message stringss for "common". (maybe, based on "msgcat") So, generate 2 resources (main document resource and "common" resource). 3. translate at Transifex. 4. merge the 2 resources for Sphinx(?). 5. Sphinx(?) merge the translated strings. Regards, KATO Tomoyuki

3 10

Criteria of core members and active members
by Ying Chun Guo 18 Jun '15

18 Jun '15

Hello, In today's IRC meeting, we discussed about the criteria of core members and active members. Here are some outputs. If you don't joined the discussion, please comment here. -------- I18n Core Contributors The coordinator of active language teams, who coordinates Dashboard translation or two documents translations during the previous two release cycles and attend team meetings at least once a month, will be granted as "I18n Core Contributors" I18n Active Contributors Translators or reviewers, who translate or review more than 200 words during the previous two release cycles, will be granted as "I18n Active Contributors" Best regards Ying Chun Guo (Daisy)

6 6

IRC Meeting
by Ying Chun Guo 18 Jun '15

18 Jun '15

Hello, team We will have the IRC meeting at UTC 1300 in the channel #openstack-meeting, on June 18th. I'm going to cover following topics: * Review translation terminologies * Open discussions If you have other topics, feel free to propose. Best regards Ying Chun Guo (Daisy)

1 0

French User Guide publication
by KATO Tomoyuki 17 Jun '15

17 Jun '15

Hi fdot, I noticed draft "fr/user-guide" link is broken[1]. Do you know what is the present situation? [1] http://docs.openstack.org/draft/draft-index.html Reagards, KATO Tomoyuki

3 4

Turkish translation
by Hüseyin Çotuk 16 Jun '15

16 Jun '15

Dear All, My name is Huseyin Cotuk, and i have been using OpenStack for more than 3 years in production. I am working for the Turkish government and we operate an OpenStack cloud for governmental institutions, universities, other research institutes and internal projects. Currently we have more than 4000 cpu cores, 500 TBytes of storage and so on. I am head of cloud department at TUBITAK ULAKBIM in Turkey, and while OpenStack Days Istanbul yesterday, we met with Jonathan and Lauren. We talked about our projects and i promised for the Turkish translation of OpenStack dashboard for the Turkish community. My organization TUBITAK ULAKBIM is also coordinating national operating system (Pardus), and we already have a translation team for this OS. We will work together with this translation team, and my team will review the translations after OS team finishes. My transifex id is huseyincotuk and the project name is openstack_turkish. I am looking forward to hearing from you. Best regards, Huseyin

3 3

Thought on String Freeze
by Akihiro Motoki 16 Jun '15

16 Jun '15

Hi I18N folks, # Congratulation for the official I18N project!! I first thought to send this mail to the dev list, but it seems better to share my thought in the I18N folks first. Problems ========== I am feeling that String Freeze does not work well in the past several releases.There are several I think we should not apply String Freeze for projects for which not so many translators work on. As far as I understand, Horizon and documentations are targets for most translations in the past several releases. On the other hands, core reviewers of projects other than Horizon and docs (including keystone) were taking care of String Freeze exception WELL. My Proposal ============= Considering the current status, I think we should limit "String Freeze" only to projects which translators are interested in. My idea is to declare projects we would like to enable "String Freeze" just after Liberty-3 is cut. By doing so, other projects no longer need to take care of String Freeze exception. (Note that the freeze date of the documentation projects are different and we can apply some different policy on documentations). Thought? I cannot join the team meeting tomorrow due to LinuxCon/CloudOpen Japan, but I hope you will share your thought on this topic. Thanks, Akihiro

2 2

Fwd: [openstack-dev] [horizon][i18n] Ordering of PO files
by Tom Fifield 09 Jun '15

09 Jun '15

-------- Forwarded Message -------- Subject: [openstack-dev] [horizon][i18n] Ordering of PO files Date: Mon, 8 Jun 2015 17:28:39 -0600 From: Thai Q Tran <tqtran(a)us.ibm.com> Reply-To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> Hi folks, In the midst of shifting to angular, we are making use of babel for extracting messages. This would then allow us to write a custom extractor for angular templates. Here's the patch that compare PO files: https://review.openstack.org/#/c/189502/ It looks worse than reality, if you compare the django vs babel makemessages, they are nearly identical, only the ordering is different. Which leads me to my next point. If the ordering of the translatable strings are not the same, how does that affect translation (if at all)?

1 0

I18n team working sessions in Vancouver
by Ying Chun Guo 06 Jun '15

06 Jun '15

Hello, all We had a great day yesterday. There were two I18n team working sessions. People from Japanese, Frech, Russian, Polish, Chinese and Chinese Taiwan team attended. Key persons from Doc team, infra team, and Horizon dev team joined the discussions too. We made good progress with glossaries, document translations, string freeze, tool migration, and etc. More details could be found in the etherpad pages [1] [2]. Yet our translators still want more face to face communications. So I organize an ad hoc meeting on Wednesday afternoon, only for translators. If you are translators and in Vancouver summit now, come to join the ad hoc meeting. The place is at a round table outside the Room 1, East Building at the Vancouver Convention Centre. The time is from 2:05pm to 5:05pm on Wednesday, May 21st. I will sit there and wait for you to join. I created an Etherpad page for us to track the discussion. Feel free to add the topics you want to cover. https://etherpad.openstack.org/p/vancouver-translation-team-workshop Thank you. Best regards Ying Chun Guo (Daisy) [1] https://etherpad.openstack.org/p/Vancouver-I18n-WG-session [2] https://etherpad.openstack.org/p/Vancouver-I18n-Translation-platform-session

3 5

I18n team, OpenStack Project Team!
by Ying Chun Guo 04 Jun '15

04 Jun '15

Hello, all I'm pleased to announce that I18n team is approved by TC to become a OpenStack Project Team. We are now under the authority of the OpenStack Technical Committee. In return, we could get some space and time to discuss our future development at the Design Summits. Our contributors could vote in the Technical Committee election. This is a great milestone after I18n team was created. Next, we need to figure out the criteria of our core members and active members, which might be different from dev team. We will initialize the core team, then grow the team and increase the contributions. Let's work together to make it a successful team. Best regards Ying Chun Guo (Daisy)

11 12

IRC meeting tomorrow
by Ying Chun Guo 03 Jun '15

03 Jun '15

Hello, team There are several responses to the mail "Review IRC meeting time"[1]. I don't see objections. So let's use them from now on. I hope active team members could have chances to join the discussion at least once a month. If these two time slots are not suitable for you, please let me know. We could still adjust the meeting times in the future. Tomorrow, we will have the IRC meeting at UTC 0600 in the channel #openstack-meeting, on June 4th. Following topics would be covered: * Briefing of I18n meetings in Vancouver summit * Criteria of I18n core members and active members * Open discussions Hope to talk to you then. Best regards Ying Chun Guo (Daisy) [1] http://lists.openstack.org/pipermail/openstack-i18n/2015-June/001107.html

1 0

Review IRC meeting time
by Ying Chun Guo 02 Jun '15

02 Jun '15

Hello, team I would like to review our IRC meeting time. Now we are using UTC 0800 and we meet on every first and third Thursday. I18n team have people from all over the world. Some people would like to use their day time, and some people prefer to use their evening time. I want to change to two time slots for the meetings. We use them alternately. Hope every team member could find a suitable time to join the team meeting. I suggest below two time slots: 1. The first Thursday every month UTC 6am, Thur Paris 08am, Thur Warsaw 08am, Thur Moscow 09am, Thur New Delhi 11:30am, Thur Beijing 14pm, Thur Seoul 15pm, Thur Tokyo 15pm, Thur Vancouver 23pm, Wed 2. The third Thursday every month UTC 13pm, Thur Paris 15pm, Thur Warsaw 15pm, Thur Moscow 16am, Thur New Delhi 18:30am, Thur Beijing 21pm, Thur Seoul 22pm, Thur Tokyo 22pm, Thur Vancouver 06am, Thur Please let me know which time slot works for you. Or if neither works for you, please suggest a time. Thank you. Best regards Ying Chun Guo (Daisy)

4 3

Re: [Openstack-i18n] Specialty teams connecting to translation team
by Ying Chun Guo 22 May '15

22 May '15

Sorry, wrong wiki link in my last email. It is https://wiki.openstack.org/wiki/I18nTeam/docs-translation Best regards Ying Chun Guo (Daisy) Ying Chun Guo/China/IBM wrote on 2015/05/22 01:42:18: > From: Ying Chun Guo/China/IBM > To: Anne Gentle <annegentle(a)justwriteclick.com> > Cc: "openstack-docs(a)lists.openstack.org" <openstack- > docs(a)lists.openstack.org>, "openstack-i18n(a)lists.openstack.org" > <openstack-i18n(a)lists.openstack.org> > Date: 2015/05/22 01:42 > Subject: Re: [Openstack-i18n] Specialty teams connecting to translation team > > Thank you, Anne. > > We use a wiki page to track the status of documentation: > https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categori… > > I hope specialty team leads could keep an eye on this table. > If there is any changes of your documents, like, changing from > stable to unstable, changing from unstable to stable, > let the translation team know by sending an email to openstack-i18n > mailing list. > So that we could make a translation plan for your documents. > > Thanks. > Best regards > Ying Chun Guo (Daisy) > > Anne Gentle <annegentle(a)justwriteclick.com> wrote on 2015/05/22 01:35:14: > > > From: Anne Gentle <annegentle(a)justwriteclick.com> > > To: "openstack-docs(a)lists.openstack.org" <openstack- > > docs(a)lists.openstack.org>, "openstack-i18n(a)lists.openstack.org" > > <openstack-i18n(a)lists.openstack.org> > > Date: 2015/05/22 01:35 > > Subject: [Openstack-i18n] Specialty teams connecting to translation team > > > > Hi all, > > I'm sitting here in Vancouver next to Daisy (Ying Chun Guo) who > > leads the i18N efforts for OpenStack. She would like each specialty > > team lead to connect with the i18N team to communicate the amount of > > change expected so that they can evaluate the timing of translation, > > and how much is done that can be translated. > > > > We also had a session with the i18N team and want to work on more > > communication with each team, and I think the specialty team leads > > are a great way to start that effort. > > > > Thoughts or ideas? Let us know. > > Thanks, > > Anne > > > > -- > > Anne Gentle > > annegentle@justwriteclick.com_______________________________________________ > > Openstack-i18n mailing list > > Openstack-i18n(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

1 0

Magnum, magnumclient translations?
by Andreas Jaeger 14 May '15

14 May '15

The magnum project wants to enable translation, see https://review.openstack.org/#/c/182835/ and https://review.openstack.org/#/c/182848/ Is there any guideline from the translation team which projects get translation enabled? I know that enabling translation does not mean, something gets translated - Davanum, keep that in mind ;) Btw. magnum is an OpenStack project that provides a set of services for management of application containers in a multi-tenant cloud environment. And so far we've enabled all projects in the OpenStack project. Only the last months this was not done with each new project moving under the big tent. I'll review the requests today or tomorrow and will setup transifex for the team unless I hear otherwise from the translation team, 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, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 2

Update on Dogri, Konkani, Manipuri, Sanskrit, Santali
by Tom Fifield 14 May '15

14 May '15

Hi all, I just wanted to let you know that Transifex has added Dogri, Konkani, Manipuri, Sanskrit and Santali to their site's code repository, and will update the code of the live site (so we can use them) before the end of this month. Regards, Tom

2 4

Horizon translation check site
by KATO Tomoyuki 14 May '15

14 May '15

Hi team, Motoki-san, We did not have Horizon translation check site for Kilo release cycle from my understanding. We previously discussed this topic in this ML. Do we have a conclusion? Need more discussion? Thanks, KATO Tomoyuki

3 2

Separating User Guides
by Andreas Jaeger 14 May '15

14 May '15

FYI, we're separating the User Guides again into two directories. Once this is done, we will have again user-guide and user-guide-admin resources. I will copy over all content from the current user-guides to these and then remove the user-guides. Patch series: https://review.openstack.org/#/q/status:open+project:openstack/openstack-ma… Docs discussion: http://lists.openstack.org/pipermail/openstack-docs/2015-May/006581.html 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, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 1

I18n team working sessions in Vancouver summit
by Ying Chun Guo 11 May '15

11 May '15

Hello, We have 2 working sessions in Vancouver summit. They are: * Translation team working session [1] * Building translation platform [2] The first session is for discussions related with our translations. The second session is for discussions related with moving to Zanata. I18n team members who would go to Vancouver summit are strongly recommended to attend these sessions. You can edit Etherpad pages to add the topics you want to discuss. The links to Etherpad pages are: https://etherpad.openstack.org/p/Vancouver-I18n-WG-session https://etherpad.openstack.org/p/Vancouver-I18n-Translation-platform-session Hope to see you in Vancouver. Thank you. Best regards Ying Chun Guo (Daisy) [1] https://openstacksummitmay2015vancouver.sched.org/event/f008932bfc685abe742… [2] https://openstacksummitmay2015vancouver.sched.org/event/83ceed4873820c889e7…

1 0

website translation
by KATO Tomoyuki 10 May '15

10 May '15

Hi team, I want to translate website "www.openstack.org" as whole as possible. However, I don't understand how website are maintained. So, I will investigate. Are you interested in website translation? Does anyone help me? My Requirement(priority): 1. automatically periodic (eg:every 1H) update translation 2. use Transifex(/Zanata) for translation tool -> need to generate pot files It is easy to translate for translator. Thanks, KATO Tomoyuki

2 2

IRC meeting tomorrow
by Ying Chun Guo 06 May '15

06 May '15

Hello team I would use tomorrow's IRC meeting to prepare for the Vancouver summit meetings. People who would go to Vancouver are strongly desired to show up. Following topics would be covered: * Agenda of I18n team meetings in Vancouver summit * Open discussions Hope to see you in IRC channel of #openstack-meeting at 0800 UTC. Best regards Ying Chun Guo (Daisy)

1 0

Persian translate
by کاربرخوب لینوکس 29 Apr '15

29 Apr '15

Salam Hello I am Contributing some project to translate to farsi such as debian , ... I like to start and Contribute open stack translation for persian users. Thanks

2 1

Decreasing size of PO files
by Andreas Jaeger 23 Apr '15

23 Apr '15

Our PO files contain information about location (filename and line numbers) as well as untranslated strings. Dolph suggested to me recently to import into projects only the *translated* strings and I did some investigation and implementation. I don't expect this to have any negative impact but wanted to inform you and ask for feedback. We will continue to push the full location information to transifex and leave it in the POT files that are stored in each repository. Thus if you download a file from transifex, you have all location information. During the import from transifex into the OpenStack git repositories, our scripts remove the location information as well as any untranslated strings thus reducing the files to import significantly. This also reduces the change of an import significantly since a line number change will not cause many location information to be updated. The gettext tools we use can cope fine with this smaller PO file since it contains everything that is needed - just nothing more ;) Also, it's easy to rebuild the full PO file from the date in the repository using the msgmerge command: msgmerge POT-FILE PO-FILE -o FULL-PO-FILE As a first step, I have made this change for documentation projects like openstack-manuals only: https://review.openstack.org/176313 If this works as expected, I plan to do it for other projects as well. Please review and tell me if you have any further ideas or if I overlooked something, 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, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 5

Final call for Horizon translations for Kilo
by Akihiro Motoki 23 Apr '15

23 Apr '15

Hi all! Horizon RC1 was just shipped yesterday. This means we are now in the deep string freeze and no string changes are expected. I hope you all keep your translations up-to-date in time. I would like to share some important topics with you. TRANSIFEX RESOURCE: Liberty development cycle is now open. You will see resource names with Liberty. For Kilo translation, please translate the resources whose names have "Kilo". IMPORTANT DATE: The final translation import is planed on Apr 23. I talked with David, Horizon PTL and the above date works for Horizon team. I don't set the exact time of the deadline, but I will do the final import in the day of Apr 23 (UTC timezone). Please don't bother me on the deadline:-) IMPORT CRITERIA: I would like to set the criteria to import to 90% completion rate (as we discussed before), OR language coordinator request. Horizon now covers various new services and in some case translation rate does not work, so I would like to honor language coordinator decision. Daisy and the team, does it make sense? If not, please start a new thread to discuss this topic. Thanks, Akihiro

3 8

Draft Documents published, next steps with draft publishing and RST translation
by Andreas Jaeger 19 Apr '15

19 Apr '15

As part of the draft publishing spec [1], we now publish all draft documents to docs.openstack.org/drafts. To read or review, go to http://docs.openstack.org/draft/draft-index.html Translation team, as part of this, the draft-i18n-manuals.html page has been removed, the content is in draft-index.html now. Next steps are moving draft language guides also to /draft/ For this, let's merge [2], release openstack-doc-tools 0.25 and then I'll adjust and remove the script changes from [3] and [4]. The script changes in [3] and [4] are part of the openstack-doc-tools patch [2] and give you the chance to review the patches and scripts independently. Andreas [1] http://specs.openstack.org/openstack/docs-specs/specs/kilo/draft-publishing… [2] https://review.openstack.org/175190 [3] https://review.openstack.org/#/c/162424/ [4] https://review.openstack.org/#/c/175157/ -- 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, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 0

Status of the RST Documentation Toolchain
by Tom Fifield 16 Apr '15

16 Apr '15

Hi, Andreas, Daisy, Motoki-san and myself have just had an impromptu hour-long discussion regarding the Status of the RST Documentation Toolchain, particularly its translation components. This meeting was spurred on by the email to the i18n mailing list announcing the pending removal of docbook user guides, and all present acknowledged the meeting would have been great if it had happened sooner :) This is the brief summary! 1. Everyone involved wants to make translators happy, and hopes that the process of moving to RST can deliver an improved toolchain 2. There has been inadequate communication between the documentation team and the i18n team regarding requirements and timelines during this process and we will strive to improve this 3. Previous statement that RST-based docs would not be published without agreement on the translation toolchain was acknowledged 4. Based on the user guide example, about 50% of existing translated strings (1943 vs 943) need to be re-translated with the current conversion process 5. Noone on the i18n team had yet the opportunity to assess the strings produced by the RST in a fuller guide and problems weren't picked up with initial version of guides in the playground folder 6. Daisy in particular hasn't been able to log in to transifex today to check the new user guide. We are currently using the standard Sphinx translation tools, though, there was some definite concern over the quality of the strings produced by the RST, including: 1. Strings that should have been trivially updated during conversion from docbook without human interaction needed (eg **string**\n) 2. Strings that are entirely markup (eg :ref:`Boot_instance_from_image_and_attach_non-bootable_volume`) 3. Strings that contain significant amounts of markup 4. Strings that contain markup characters that are unusual for translations, eg backticks, asterisks 5. Strings that contain markup where placeholders were previously used 6. ... this list is incomplete and comes only from what amotoki and fifieldt saw during the meeting - the broader i18n community has not yet been asked for feedback outside of Andreas' recent email 7. There is an open issue about how to fix problems like the above. 1. Andreas stated that not maintaining our own custom scripts is a good aim, and some of the issues above could be handled with a one time fix at conversion time 2. Daisy & Tom stated that they preferred such issues to be fixed in the toolchain 3. Just looking at the "** STRING **" issue, it's 70 strings but a quick proof of concept didn't result in fixing the issue - we haven't worked out why yet. 4. The current toolchain is difficult to modify, since it relies on an upstream component that is used by multiple projects, meaning post processing and pre-processing are the only real approach we have 5. It could be complicated to use post-processing and pre-processing to implement fixes for issues beyond the trivially updated string example in the current toolchain 8. There is an open question about whether it is possible to deliver an improved i18n experience with the current toolchain 9. There is not yet agreement that the current documentation toolchain is meeting the needs of the i18n team Based on the meeting, and especially the fact that due to inadequate communication the i18n team (inc Daisy) has not yet had the opportunity to assess the RST documentation toolchain fully, I would propose that the removal of existing guides and publication of RST guides be delayed until that's happened. We suggest that Daisy does an initial assessment and arrange a meeting to discuss next steps as soon as possible.There are many things we can fix with the the toolchain any time after publication, however it is important that we assess what needs to be done and ensure that we can actually feasibly deliver an improved experience for our translations, as well as our doc team. Regards, Tom

6 11

北京约克仪器公司上海
by 谈辛海 15 Apr '15

15 Apr '15

wxawryvz 16:56:58 2015/4/15

1 0

IRC meeting tomorrow
by Ying Chun Guo 15 Apr '15

15 Apr '15

Hello, all We will have IRC meeting tomorrow, at 0800 UTC in the channel of #openstack-meeting. Following topics will be covered: * rst document translation discussion with doc team * Final push on Horizon translation There is a wiki page [1] highlighting typical rst markups used by openstack manuals. Please go through it before the meeting. Thank you. Best regards Ying Chun Guo (Daisy) [1]https://wiki.openstack.org/wiki/I18nTeam/rst-markups

1 0

What's Up Doc? Apr 10 2015
by Anne Gentle 13 Apr '15

13 Apr '15

Hi all, As you probably saw from PTL nominations last week, I'm happy to hand the docs PTL baton to Lana Brindley! I loved leading this group and thank you all for supporting me. Thank you Lana for your willingness to lead. I'm still here to bring us to the Kilo release, so this week's What's Up Doc brings sharp focus requests to everyone to work on docs. These are the top priorities that we all need to work on - devs, writers, testers, gaters, everyone. 1. Bug triaging and fixing, especially for openstack-manuals. There are nearly 300 DocImpact bugs logged that we need developers to circle back to. With nearly 600 bugs overall, we need lots of focus here. To that end, I propose we hold a bug triage day. I'll send details in a separate email. 2. Install Guide testing and reviewing. The Install Guide team has a published spec that will help reviewers see what's changing with the Kilo Install guide: http://specs.openstack.org/openstack/docs-specs/specs/kilo/installguide-kil… Join them for weekly meetings Tuesdays at at 13:00 UTC (8:00 AM US CDT) in Google Hangout: https://plus.google.com/hangouts/_/calendar/a2FyaW4ua2F0aG9kZUBnbWFpbC5jb20… If you do nothing else but these two focus areas we'll be in good shape. There are other activities going on leading up to Vancouver but those two are top priorities. _RST Migration_ We are working to resolve translation tool expectations with the i18N team. I want to publish the RST-based English End User Guide and Admin User Guide once we're all comfortable with the way forward. Daisy will discuss the implications at the next i18N team meeting Thursday at 0800 UTC, and we'll implement and communicate the plan. _Networking Guide_ Next on the list is Networking Guide testing and reviewing. The Networking Guide team has a talk in Vancouver and needs to get their guide in shape for publishing. The neutron team is holding a doc day April 23. Please join in -- they'll post details in their notes. _First App Tutorial_ There's also the First Application Tutorial that needs to finish the spec and needs an editing cleanup prior to publishing. Ideally that will happen before Vancouver, we need to get it to the finish line. _HA Guide_ With everything else going on we need an updated spec for the HA Guide - the wiki page isn't enough. Based on this week's doc team meeting it sounds like that can go to RST as well but we need it in the spec so we can plan and cross-coordinate with the other priorities leading up to Vancouver. _Vancouver Summit _ The docs team has four Fishbowl time slots, 2 Workroom slots, and 1 Meetup allocated now. If you'd like to discuss a cross-project idea, please use the form to suggest new ideas: http://goo.gl/forms/S69HM6XEeb. You can see the current suggestions already posted here: https://docs.google.com/spreadsheets/d/1vCTZBJKCMZ2xBhglnuK3ciKo3E8UMFo5S5l… Lana or I will send out an etherpad in the next week or so with topic suggestions for our allocation. Thanks, Anne -- Anne Gentle annegentle(a)justwriteclick.com

3 3

User Guides Changes
by Andreas Jaeger 09 Apr '15

09 Apr '15

The two User Guide, Admin User Guide and End User Guide, have been converted from Docbook XML to RST. The conversion shouldn't have changed sentences but since markup has changed, strings for translation have changed as well. I've tried to merge the strings in transifex, so please have a look - and update the guides. I've marked the old guides as read-only in transifex, so that you cannot change them anymore but still can use them as reference. The documentation team will remove the old-guides from their project today. Transifex resources: Old End User Guide: https://www.transifex.com/projects/p/openstack-manuals-i18n/resource/user-g… Old Admin User Guide: https://www.transifex.com/projects/p/openstack-manuals-i18n/resource/user-g… New RST User Guides (single resource for both books): https://www.transifex.com/projects/p/openstack-manuals-i18n/resource/user-g… If there's anything else I can do, please speak up, 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, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

5 21

Horizon/Kilo, string freeze?
by Robert Simai 09 Apr '15

09 Apr '15

Hi, I was working on translations for Horizon/Kilo through Transifex during the last weeks and I've noticed there were at least 2 updates during the last few days, about 20 new strings have been added after I was on 100% done. I thought there should be some string freeze!? Anyone knows how this is supposed to work or better when to expect the final set of strings? -- Thanks, Robert

3 7

IRC meeting tomorrow
by Ying Chun Guo 02 Apr '15

02 Apr '15

Hello, all We will have IRC meeting tomorrow, at 0800 UTC in the channel of #openstack-meeting. I'm going to cover following topics: * Status update of Horizon translation and issue collections * Open discussions If you have anything to discuss with the team, welcome to join. Best regards Ying Chun Guo (Daisy)

2 1

Does anyone want to update Juno Horizon translation for the next stable update?
by Akihiro Motoki 02 Apr '15

02 Apr '15

Juno 2014.2.3 stable release will be freezed Apr 2nd. Does anyone want to update your translations in Horizon? If no response, I won't take no action (without checking Transifex diff). If you want, please let me know by Friday (in UTC timezone). Thanks, Akihiro

4 3

[glance] bug 1436275/string freeze
by stuart.mclaren＠hp.com 27 Mar '15

27 Mar '15

Hi, I understand that the doc/source part of this patch: https://review.openstack.org/#/c/130222 doesn't impact the string freeze, but it also changes a couple of print statements so I'm sending notification as per the string freeze wiki page. Thanks, -Stuart

1 0

Checking PO Files before uploading in Transifex
by chandrakant dhutadmal 26 Mar '15

26 Mar '15

Hi. How does one check if the translated PO file is up to the expectation of the developer ? It is better to cross check the po file before uploading it on Transifex. What are the general "take care" points while translating OpenStack files ? Any pointers. Regards,Chandrakant Dhutadmal.

3 2

[Keystone] String Freeze Exceptions for Feature Freeze Exception BPs
by Morgan Fainberg 26 Mar '15

26 Mar '15

There are Feature Freeze Exception BPs [1][2][3] for Keystone that will cause string changes after string freeze. I am bringing these to the attention of this list per the wiki [4]. [1] https://blueprints.launchpad.net/keystone/+spec/domain-config-ext [2] https://blueprints.launchpad.net/keystone/+spec/idp-id-registration [3] https://blueprints.launchpad.net/keystone/+spec/ecp-wrapped-saml-assertions [4] https://wiki.openstack.org/wiki/StringFreeze

2 2

Re: [Openstack-i18n] [openstack-dev] [glance] Applying patch in bug #1414725 while string freeze in place
by ashish.jain14＠wipro.com 24 Mar '15

24 Mar '15

Hello, Moving this mails from openstack-dev to docs/i18n list. Please see the details below: I have submitted a patch to address the bug(https://bugs.launchpad.net/glance/+bug/1414725). This patch updates glance-manage documentation. Currently the documentation misses details on handling the glance-manage metadata definitions. I have submitted https://review.openstack.org/#/c/166597/ which addresses this deficiency in the documentation. Is it possible to include this change in the latest kilo documentation while the string freeze is in place? Regards Ashish -----Original Message----- From: Nikhil Komawar [mailto:nikhil.komawar@RACKSPACE.COM] Sent: Tuesday, March 24, 2015 12:53 AM To: openstack-dev(a)lists.openstack.org Subject: Re: [openstack-dev] [glance] Applying patch in bug #1414725 while string freeze in place Please direct this query to documentation and i18n lists [1, 2, 3] and include the response (if any) as a comment on the review so that the core reviewers are aware. Thanks for bringing this up and helping in contributing to the project! [1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs [2] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n [3] https://wiki.openstack.org/wiki/Mailing_Lists Thanks, -Nikhil ________________________________________ From: ashish.jain14(a)wipro.com <ashish.jain14(a)wipro.com> Sent: Monday, March 23, 2015 1:01 PM To: openstack-dev(a)lists.openstack.org Subject: [openstack-dev] [glance] Applying patch in bug #1414725 while string freeze in place Hello, I have submitted a patch to address the bug(https://bugs.launchpad.net/glance/+bug/1414725). This patch updates glance-manage documentation. Currently the documentation misses details on handling the glance-manage metadata definitions. I have submitted https://review.openstack.org/#/c/166597/ which addresses this deficiency in the documentation. Is it possible to include this change in the latest kilo documentation while the string freeze is in place. Regards Ashish The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com __________________________________________________________________________ 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 __________________________________________________________________________ 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 The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

2 1

Horizon translation check site for Kilo
by Akihiro Motoki 20 Mar '15

20 Mar '15

Hi, Kilo-3 is approaching and it is the time to start translations for Kilo. I would like to know the status of the community effort on preparing the Horizon translation check site. In the past releases, I18N team has the horizon translation check site but it was completely provided by my resource and time. For Kilo cycle, I am sure I can provide such site at all because I am spending very busy days on my main work. The same situation continues for three release cycles and I think it is time we should have such site as the team. We should not depend on someone's personal effort as OpenStack community. I may be able to provide the site for Kilo release if I have time but not sure. I would like to raise this topic. If nobody other than me raises a hand, it is no longer a team and it means we fail as a community. I can help the work but don't have enough time to lead it. I hope we have a progress on it. Thanks, Akihiro

6 11

Horizon translation for Kilo starts !
by Ying Chun Guo 19 Mar '15

19 Mar '15

Hello, all As OpenStack Kilo development draws to a close, it's time for our translators to start one of our major works: translating OpenStack Dashboard into multiple languages. Till now, around 558 new strings are added since Juno to Kilo. The official date of Kilo release is April 30. We'd better to finish the translations before April 20, in order to reserve enough times to merge the translations into the final release. I did a check of the translation website: https://www.transifex.com/projects/p/horizon/ The translations of following languages have been completed more than a half. Their translations are most likely completed by April 20. They are: Korean (Korea) 55 strings left Japanese 316 strings left German 487 strings left Chinese (China) 558 strings left French 558 strings left Portuguese (Brazil) 558 strings left Spanish 558 strings left Kannada 747 strings left Russian 767 strings left Chinese (Taiwan) 830 strings left Polish (Poland) 870 strings left Hindi 1068 strings left Czech 1355 strings left Dutch (Netherlands) 1420 strings left Serbian 1433 strings left The contributions to other languages are welcomed too. There is still 1 month left. The strings in total is around 3300. If several friends/colleagues work together, it's very possible to complete The resources of Kilo release in Transifex are: Kilo - Horizon Java Script Translations (133 strings in total) https://www.transifex.com/projects/p/horizon/resource/horizon-js-translatio… Kilo - Horizon Translations (104 strings in total) https://www.transifex.com/projects/p/horizon/resource/horizon-translations/ Kilo - OpenStack Dashboard Translations (3141 strings in total) https://www.transifex.com/projects/p/horizon/resource/openstack-dashboard-t… Please join this most valuable and high priority work. Let's work together to help OpenStack dashboard speak multiple langauges ! Thank you and best regards Ying Chun Guo (Daisy)

1 0

IRC meeting tomorrow
by Ying Chun Guo 18 Mar '15

18 Mar '15

Hello, all We will have IRC meeting tomorrow, at 0800 UTC in the channel of #openstack-meeting. I'm going to cover following topics: * Kick off Horizon translation for Kilo * Open discussions If you have anything to discuss with the team, welcome to join. Best regards Ying Chun Guo (Daisy)

2 1

Translating RST source with Sphinx builds
by Anne Gentle 10 Mar '15

10 Mar '15

Hi all, We're preparing to migrate user guides to RST to improve ease of authoring for documentation. The spec [1] is now published, and we've got a research item for a toolchain that can "slice" RST similar to the DocBook slicing we do now. Reading the Sphinx documentation, it seems that you can run sphinx-build -b get-text to extract translatable strings to get a collection of .po files. This seems very similar to our current docbook slicing script. Does anyone have time this release to go through the RST files we're creating with the Sphinx workflow and analyze the results? I don't intend to publish the RST-based user guides until we have agreement on the translation toolchain, so we have until April 9, but ideally we'll have answers this month -- originally on the spec I wanted answers by last month, but without a lot of complex RST to test there wasn't a great way to research. Now that we are getting more RST files in openstack/openstack-manuals/doc/playground-user-guide [3] I would appreciate help here. Thanks, Anne 1. http://specs.openstack.org/openstack/docs-specs/specs/kilo/migrate-to-new-w… 2. http://sphinx-doc.org/latest/intl.html

3 9

docs.openstack.org - What to put on translated pages?
by Andreas Jaeger 10 Mar '15

10 Mar '15

Reviewing https://review.openstack.org/#/c/162045, I noticed that the patch adds all manuals to it - so both the translated Korean ones as well as English titles. In the past, the translated pages only contained links to translated manuals but not to English ones. But I noticed that the Japanese index page was changed recently as well and puts up all the document. How do we want to continue here? My suggest would be to only list translated manuals on a localized index page to not confuse the users. 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, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

4 4

OpenStack interface in Indian languages
by chandrakant dhutadmal 08 Mar '15

08 Mar '15

Hi All. It gives me great pleasure in informing you all that C-DAC, Pune (Centre for development of advanced computing) has decided to contribute in translating OpenStack interface in all 22 Scheduled Indian languages. @Chandan Kumar has been helpful in getting started. Need to discuss this with language team leaders/ maintainers in order to avoid duplicate efforts. Please comment. RegardsChandrakant DhutadmalC-DAC, Pune.

4 17

I18n meeting tomorrow
by Ying Chun Guo 04 Mar '15

04 Mar '15

Hello, all We will have IRC meeting tomorrow, at 0800 UTC in the channel of #openstack-meeting. I'm going to cover following topics: * Translation test discussion * Open discussions If you have anything to discuss with the team, welcome to join. Best regards Ying Chun Guo (Daisy)

1 0

Re: [Openstack-i18n] [OpenStack-docs] [ha-guide] RST or Docbook?
by Anne Gentle 02 Mar '15

02 Mar '15

On Thu, Feb 26, 2015 at 3:38 PM, Nick Chase <nchase(a)mirantis.com> wrote: > We decided we'd take this to the mailing list, for obvious reasons. > > I vote RST. We do have a good bit of existing material, but it could > easily be converted to RST, and I know how to set it up, now that I've done > the Networking Guide. :) > > That said, where are we on the translation status? > I emailed Daisy earlier this week but haven't seen a reply (hopefully haven't just missed it.) Anyone else on the i18n list know where we are with testing RST/Sphinx and the translation toolchain? Anne > > Thanks... > > ---- Nick > > _______________________________________________ > OpenStack-docs mailing list > OpenStack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs > -- Anne Gentle annegentle(a)justwriteclick.com

5 7

Re: [Openstack-i18n] [OpenStack-docs] I question html tag status in API Reference Document
by Andreas Jaeger 26 Feb '15

26 Feb '15

On 02/25/2015 09:41 AM, SungJin Kang wrote: > Hi, > I translation document to Korean. API Reference [1] > > this 'maxServerMeta' [2] is tag '<code>'. > this 'maxPersonality' [3] is tag 'no'. > > two attribute is different?? > > two attribute is same... added '<code>' tag?? Hi, I strongly advise to not translate the API reference document, it includes lots of WADL that our toolchain does not handle and thus you will never be able to fully translate the manual. That's why the guide has a tag "do-not-translate-yet", Andreas > Thanks, > Sungjin. > > > [1] : > https://www.transifex.com/projects/p/openstack-manuals-i18n/resource/api-re… > [2]: > https://github.com/openstack/api-site/blob/master/api-ref/src/docbkx/ch_com… > [3]: > https://github.com/openstack/api-site/blob/master/api-ref/src/docbkx/ch_com… > > > _______________________________________________ > OpenStack-docs mailing list > OpenStack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs > -- 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, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 1

State of the RST docs migration
by Anne Gentle 24 Feb '15

24 Feb '15

Hi all, I hope it's not poor form to post a blog post, but I wrote this up to talk about the current state of our migration. http://justwriteclick.com/2015/02/23/state-of-the-migration-to-sphinxrst/ I want to hear from you all "what's essential" for us to begin publishing. I've promised we won't publish until the translation tool chain is complete. Anything else in the bug list that is a "must have?" https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=openstackdocs… Thanks, Anne

2 1

Here be dragons - Summit talk proposal
by Łukasz Jernaś 18 Feb '15

18 Feb '15

Hi I18N list! As the voting period for Summit talks has opened, I'd like to shamelessly propose my talk about my experiences in translating OpenStack in the hope to raise awareness about i18n in the developer community and also to get new translators on board. So if you think you'd be interested in listening or that other people may be interested please cast your vote on https://www.openstack.org/vote-vancouver/presentation/here-be-dragons-trans… Have a nice day! -- Łukasz [DeeJay1] Jernaś

1 0

IRC meeting tomorrow
by Ying Chun Guo 18 Feb '15

18 Feb '15

Hello, all We will have IRC meeting tomorrow, at 0800 UTC in the channel of #openstack-meeting. I'm going to cover following topics: * Research result on translating RST documents * Open discussions If you have anything to discuss with the team, welcome to join. Best regards Ying Chun Guo (Daisy)

1 0

IRC meeting tomorrow
by Ying Chun Guo 04 Feb '15

04 Feb '15

Hello, all We will have IRC meeting tomorrow, at 0800 UTC in the channel of #openstack-meeting. I'm going to cover following topics: * Zanata related discussion * Fuel-cloud translation and review * Introduction of translation test project * Open discussions If you have anything to discuss with the team, welcome to join. Best regards Ying Chun Guo (Daisy)

1 0

Re: [Openstack-i18n] [OpenStack-docs] What's Up Doc? Jan 30 2015
by KATO Tomoyuki 02 Feb '15

02 Feb '15

> We have a new Sphinx theme for docs.openstack.org, called > openstackdocstheme. It should be available on pipy as soon as we can get it > released. Once that's released I'll write instructions for how to apply it > to migrated content. A huge thanks to Doug Hellman for getting it to > releasable! > > We are working through migrations for the End User Guide and Admin User > Guide, sign up for a section at > https://wiki.openstack.org/wiki/Documentation/Migrate. > > While migrating a chapter, I found I wanted some guidelines for how to > migrate, so I wrote some here: > https://wiki.openstack.org/wiki/Documentation/Migrate#Migration_Conventions > Feel free to disagree with my notes so far, but my main theme is "simplify." > > The Foundation is working on letting people know about the new home page > design for docs.openstack.org probably through a Superuser post so that we > can dig into the techie details. :) Please let me know if you have > questions, and realize we're working through the kinks as we go. Do we have i18n tool chain for new format? KATO Tomoyuki

3 3

Do we need to update translations for 2014.2.2 (Juno update)?
by Akihiro Motoki 28 Jan '15

28 Jan '15

Hi, 2014.2.2 Juno Stable update schedule was just announced: http://lists.openstack.org/pipermail/openstack-dev/2015-January/054924.html Does anyone want to update translations for this stable update? -- Akihiro Motoki <amotoki(a)gmail.com>

2 2

knowing translation team
by Frans Thamura 23 Jan '15

23 Jan '15

hi all any idea to know the translator team in our chapter? esp to make a coordination work. Frans

2 1

Re: [Openstack-i18n] [OpenStack-docs] transifex birocrachy
by Ying Chun Guo 23 Jan '15

23 Jan '15

Hi, Frans Which translation team do you belong to? Would you go to openstack-i118n mailing list? You could find more translators there. See https://wiki.openstack.org/wiki/I18nTeam Best regards Ying Chun Guo (Daisy) From: Frans Thamura <frans(a)meruvian.org> To: "openstack-docs(a)lists.openstack.org" <openstack-docs(a)lists.openstack.org> Date: 2015/01/23 12:33 Subject: [OpenStack-docs] transifex birocrachy hi all i have several new people part of the openstack-translation team and we can see anyone can join, and be part of it, and several of the people, i dont understand and know, any idea to coordinate this work in best way? i find several people in the list, approved by openstack global team (me also :)) F _______________________________________________ OpenStack-docs mailing list OpenStack-docs(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

1 0

Zanata? New translation platform for Kilo?
by Akihiro Motoki 20 Jan '15

20 Jan '15

Hi, I see there are some discussion related to Zanata in the last IRC meeting. I have a question on the status of the transition to the new translation platform. When will the new platform be available to all translators? Do we migrate our translation platform to the new one in Kilo? If so, IMO we need to migrate to the new one and clarify its basic workflow until Kilo-3 is released. Many translations are done by volunteers who are not backed by companies, so we need to provide enough time for them to learn new workflows. Thanks, Akihiro

2 2

Re: [Openstack-i18n] IRC meeting tomorrow
by Ying Chun Guo 20 Jan '15

20 Jan '15

I'm not able to answer your question now. Let me dig out and reply later. Best regards Ying Chun Guo (Daisy) François Bureau <francois.bureau(a)cloudwatt.com> wrote on 2015/01/15 15:53:18: > From: François Bureau <francois.bureau(a)cloudwatt.com> > To: Ying Chun Guo/China/IBM@IBMCN > Date: 2015/01/15 15:53 > Subject: Re: [Openstack-i18n] IRC meeting tomorrow > > Hello Daisy, > > First I would like to wish you a happy new year ! :) > > I am sorry I will not be able to participate to the IRC meeting. I > am currently on a middle of an important work for my company and I > don't a lot of time. > > It will be finish in a couple of days. > > I just have a small question, do you have a date when we are going > to move on Zanata ? > > All the best :) > > F. > Le 14/01/2015 09:50, Ying Chun Guo a écrit : > Hello, all > > We will have the first I18n meeting in 2015 tomorrow at 0800 UTC in > the channel of #openstack-meeting. > > I'm going to cover below topics: > * Status update of document translations > * Open discussions > > Feel free to propose any interested topics you have. > > 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

2 1

IRC meeting tomorrow
by Ying Chun Guo 15 Jan '15

15 Jan '15

Hello, all We will have the first I18n meeting in 2015 tomorrow at 0800 UTC in the channel of #openstack-meeting. I'm going to cover below topics: * Status update of document translations * Open discussions Feel free to propose any interested topics you have. Best regards Ying Chun Guo (Daisy)

2 2

Install Guide translated into Portuguese
by Tom Fifield 05 Jan '15

05 Jan '15

Thanks to Fernando Pimenta and the OpenStack Brazil team, the OpenStack install guide has been translated into Portuguese. You can see an example PDF at: http://www.ph.unimelb.edu.au/~fifieldt/openstack-install-guide-apt-local-pt… The patch to add the sub-site to the documentation is at: https://review.openstack.org/#/c/144569 There are a still a few strings in common that need to be translated, so once that passes the 8% threshold this patch will start building and can be merged. Regards, Tom

2 2

No IRC meeting this week
by Ying Chun Guo 31 Dec '14

31 Dec '14

Hello, Tomorrow is the New Year's Day. I'm afraid many people are on vacations. So let's cancel the IRC meeting this week. Talk to you on Jan. 15th then. Happy new year! Best regards Ying Chun Guo (Daisy)

1 0

IRC meeting tomorrow
by Ying Chun Guo 17 Dec '14

17 Dec '14

Hello, all We will have the I18n meeting tomorrow at 0800 UTC in the channel of #openstack-meeting. I'm going to cover below topics: * Blueprint: Add a new metrics "translations" [1] * Open discussions Feel free to propose any interested topics you have. Best regards Ying Chun Guo (Daisy) [1]: https://blueprints.launchpad.net/stackalytics/+spec/translators-contribution

1 0

IRC meeting tomorrow
by Daisy Guo 17 Dec '14

17 Dec '14

Hello, all We will have the I18n meeting tomorrow at 0800 UTC in the channel of #openstack-meeting. I'm going to cover below topics: * Discuss the blueprint: Add a new metrics "translations" [1] * Open discussions Feel free to propose any interested topics you have. Best regards Ying Chun Guo (Daisy) [1]: https://blueprints.launchpad.net/stackalytics/+spec/translators-contribution

1 0

Request for work: Juno Horizon translations
by Akihiro Motoki 05 Dec '14

05 Dec '14

Hi I18N team. The Juno stable update was deferred one week and is scheduled this week. Unluckily enough a patch with JavaScript string changes was merged just before the freeze. When you visit Transifex, you will notice that Juno Horizon JavaScript translations is down to around 70-80%. The change is simple and most strings are also avalable in other resources. It will take only a few of minutes. Please update your translations. -- Akihiro Motoki <amotoki(a)gmail.com>

7 6

IRC meeting tomorrow
by Ying Chun Guo 03 Dec '14

03 Dec '14

Hello, all We will have the I18n meeting tomorrow at 0800 UTC in the channel of #openstack-meeting. I'm going to cover below topics: * Review the status of TODO last time * Documentation translation plan in Kilo * Open discussions Feel free to propose any interested topics you have. Best regards Ying Chun Guo (Daisy)

1 0

Open Stack Coordinator and Resources for Marathi language
by chandrakant dhutadmal 26 Nov '14

26 Nov '14

Hi. I was on https://wiki.openstack.org/wiki/I18nTeam page to know more about Marathi language Translation team. I could not find Marathi language listed there. I am not sure why ?. When i logged in to Transifex, i found out that there are two language teams. 1) Marathi and 2) Marathi( India). I did not understand the difference between these two teams. Is there a need for maintaining these two teams for Marathi ? I have already registered for Marathi language as translator. But i am unable to proceed with translating as it throws message "There are no resources to translate." Who is supposed to make sure that there are resources available which translator's can translate ? If any one has information regarding this, Kindly share. Regards,Chandrakant Dhutadmal.

1 0

OpenStack translations in Marathi Language
by chandankumar 26 Nov '14

26 Nov '14

Hello Chandrakant, On 11/15/2014 01:35 PM, chandrakant dhutadmal wrote: > > > On Saturday, November 15, 2014 1:30 PM, chandrakant dhutadmal > <cpdhutadmal(a)yahoo.com> wrote: > > > Hi All. > > Just heard a talk by Daisy and Chandan Kumar regarding translations of > OpenStack in various languages across the globe. My name is > Chandrakant Dhutadmal, working with C-DAC, Pune, India. I am ready to > contribute to Marathi language translation. Kindly let me know the > process to start with. > Welcome to the OpenStack-i18n team. You are added as a translator in marathi language team of openstack. Please add your Language under [ Local Translation Teams] section in https://wiki.openstack.org/wiki/I18nTeam . You can start translating Juno - OpenStack Dashboard Translations and Juno - horizon Translation at https://www.transifex.com/projects/p/horizon/language/mr/ . If you face any issue, feel free to shoot a mail to the mailing list or poke us on #openstack-translation channel on freenode server. Thanks, Chandan Kumar

2 1

[Horizon] Backport question with string change
by Abishek Subramanian (absubram) 21 Nov '14

21 Nov '14

Hi Translation team, This is only a question - about a patch I have in Juno that I¹d like to get back ported to Icehouse. It is isolated to the Horizon openstack_dashboard ³Router² and it fixes a broken 'update profile' functionality. The issue is the patch has a new error string. I was wondering what the procedure would be with regard to string translation. Since it is in Juno, is there any way I could potentially back port the string translation as well? The review itself is at - https://review.openstack.org/#/c/129007/ Thanks in advance for your guidance. Regards, Abishek

1 0

swift-propose-translation-update is failing
by Tom Fifield 20 Nov '14

20 Nov '14

Hi, I just lodged a new bug: https://bugs.launchpad.net/openstack-i18n/+bug/1394120 Basically, the periodic job to propose translations to swift is failing. and we need to get it to work, since swift is now translated into Chinese by Seagate! :DDD >From the log: 2014-11-19 06:09:39.316 | ++ find swift/locale -name swift.po 2014-11-19 06:09:39.318 | + PO_FILES=swift/locale/zh_CN/LC_MESSAGES/swift.po 2014-11-19 06:09:39.318 | + '[' -n swift/locale/zh_CN/LC_MESSAGES/swift.po ']' 2014-11-19 06:09:39.318 | + python setup.py update_catalog --no-fuzzy-matching --ignore-obsolete=true 2014-11-19 06:09:39.525 | running update_catalog 2014-11-19 06:09:39.525 | error: locale: No such file or directory 2014-11-19 06:09:39.547 | Build step 'Execute shell' marked build as failure https://jenkins.openstack.org/job/swift-propose-translation-update/63/conso… Previously the locale directory in swift was at the top level of the repo. Now it is a subdiretory under swift. Likely the script needs updating. Regards, Tom

3 5

IRC meeting on Thursday
by Ying Chun Guo 20 Nov '14

20 Nov '14

Hello, all We will have the I18n meeting tomorrow at 0800 UTC in the channel of #openstack-meeting. I'm going to cover below topics: * Follow up actions after translators meet-up in Paris ( refer to [1] ) * Open discussions Feel free to propose any interested topics you have. Best regards Ying Chun Guo (Daisy) [1] http://lists.openstack.org/pipermail/openstack-i18n/2014-November/000871.ht…

1 0

Bugfix for Icehouse changing strings
by Matthias Runge 17 Nov '14

17 Nov '14

Hello, is there a process to update strings in older versions? E.g. there is an ugly bug in Horizon Icehouse version[1], and it has a user impact. It says: <start_ip_address>,<end_ip_address> rather than start_ip_address,end_ip_address It's fixed in Juno. Thanks, Matthias [1] https://github.com/openstack/horizon/blob/stable/icehouse/openstack_dashboa…

3 3

OpenStack translations in Marathi Language
by chandrakant dhutadmal 15 Nov '14

15 Nov '14

Hi All. Just heard a talk by Daisy and Chandan Kumar regarding translations of OpenStack in various languages across the globe. My name is Chandrakant Dhutadmal, working with C-DAC, Pune, India. I am ready to contribute to Marathi language translation. Kindly let me know the process to start with. Regards,Chandrakant Dhutadmal.

1 0

Stable translation import schedule (Juno and Icehouse)
by Akihiro Motoki 13 Nov '14

13 Nov '14

Hi, The dates of upcoming Stable update releases of Juno and Icehouse are fixed during the summit discussion and available at [1]. Translation import patch will be proposed three days after the freeze. (Note that the freeze date is one week before the release). According to the rule, the dates of translation import deadline will be as follows. The first upcoming date is Nov 23 (the first Juno stable update). If your language team has an update, please keep the date in your mind. This is the last call from me and I won't send another reminder mail on it. Juno 2014.2.1 Nov 23, 2014 2014.2.2 Jan 25, 2015 2014.2.3 Apr 5, 2015 Icehouse 2014.1.4 Feb 14, 2015 (we don't have a plan to import translation for 2014.1.5) As long as I remember the date, I will be able to propose a patch, but it will be appreciated if someone reminds me. [1] https://wiki.openstack.org/wiki/StableBranchRelease#Planned_stable.2Ficehou… -- Akihiro Motoki <amotoki(a)gmail.com>

2 2

Discussion on fuel-cloud module in Pune Linux User Group Meet
by Rajesh Ranjan 07 Nov '14

07 Nov '14

fyi. ---------- Forwarded message ---------- From: Manjusha Joshi <manjusha.joshi(a)gmail.com> Date: Tue, Nov 4, 2014 at 3:03 PM Subject: [PLUG] [Confirmation] Monthly PLUG meet on 8th Nov., 2014 To: Pune GNU/Linux Users Group Mailing List <plug-mail(a)plug.org.in> Hello, PLUG meeting for Month of November, 2014 will be held on 8th Nov., Saturday at 4pm in SICSR. Location: SICSR, Atur Centre, Model Colony, Pune Room No 704, 7th floor Time: 4:00 pm Agenda: 1. Discussion about Upcoming event: Please mark the calendar a) 14-15 November FUEL : Venue: Yashada, near University circle, Pune website: : http://fuelproject.org/gilt2014/index b) 22 November CenOS DOJO venue : CMS, Univ. Pune website: http://wiki.centos.org/Events/Dojo/Pune2014 2. There will be session on FUEL Cloud Rajesh & Chandan will introduce FUEL Cloud module for review. Explore it. FUEL-CLOUD is a collection of commonly used entries for localization of cloud computing related software and docs. Today, Cloud is very new to this world and is an emerging technology to the future. Lots of companies are switching their application to cloud. To understand and reach to various corner of world, it is necessary to made it available in different languages. To make the life of translators and localizer easier, it is necessary to provide a list of commonly used entries from cloud computing with its context. fuel-cloud module is prepared from different cloud technologies so that the module can be used across platform. This module will help to use a particular word precisely in cloud computing. Here is the link of FUEL-CLOUD module. https://docs.google.com/spreadsheets/d/1UYbFoANH7pFdjaEJ3aGFZcYaE22-Ierf4iB… Chandan will take the session, introducing FUEL cloud module and if enough folks in audience interested then a quick review of the module can be done. FUEL Project (http://fuelproject.org/) is the largest and fastest growing open source based language resource repository that works to create standard terminology, style guide, assessment methodology etc with the help of community and different organizations. Currently it works with c.60 languages community One can exchange CDs, DVDs of new versions. All are welcome to attend the meeting. There is no fee to attend the meeting. See you there. -- Manjusha <http://manjushajoshi.wordpress.com/> _______________________________________ Pune GNU/Linux Users Group Mailing List -- Rajesh Ranjan www.rajeshranjan.in @kajha <https://twitter.com/kajha> Can the FOSS community save 197 endangered Indian languages? <http://opensource.com/community/14/7/save-endangered-language-today> -- Rajesh Ranjan www.rajeshranjan.in @kajha <https://twitter.com/kajha> Can the FOSS community save 197 endangered Indian languages? <http://opensource.com/community/14/7/save-endangered-language-today>

2 1

Re: [Openstack-i18n] Summaary of Paris Translators meeting
by Ying Chun Guo 07 Nov '14

07 Nov '14

I'm in the talk with Francois now. Transifex provides a report of all translators contributions, which could be viewed in projects, languages, and a specific duration. He suggested to send the translator contribution statics of each translation team to the coordinators, per month. I will add it as a TODO. Best regards Ying Chun Guo (Daisy) Ying Chun Guo/China/IBM wrote on 2014/11/05 17:49:33: > Ying Chun Guo/China/IBM > 2014/11/05 17:49 > > To > > openstack-i18n(a)lists.openstack.org, > > cc > > Subject > > Summaary of Paris Translators meeting > > Hello, team > > There was a session yesterday in Paris Design summit to gather > translators together. > There were 6 translation teams joined the meeting locally. They are > French team, Spanish team, German team, Catalan team, Chinese Taiwan > team, and Chinese team. > Some team members were trying to join the meeting remotely through > Google Hangout. Yet they failed because of a fault made by me. I'm > very sorry for that. > > We discussed how to build translation teams, how to make a high > quality translation, and how to maintain the priority definition of > documents. There are some good suggestions I could collect. Feel > free to add more if I miss. > > * how to build translation teams > #1: Use local Openstack meetups to promote translations > #2: Use a blog post on OpenStack planet to promote translations. > #3: Give the new comers a start point > #4: Give people a goal and a timeframe (a focus) > #5: A overall description of translation priorities, including both > docs and messages > #6: Create mailing lists on OpenStack infrastructure for local > translation teams > #7: Improve our tools to clearly state translators contributions and > teams progresses. Integrate with Stackalytics in the future. > > * how to make a high quality translation > #1: Maintain a glossary > #2: Report bugs to projects if the problems of translations are due > to the source strings, with a "i18n" tag. > #3: Report bugs i18n team if the problems of translations are due to > the translation quality, with a tag of language code. (https:// > bugs.launchpad.net/openstack-i18n) > #4: Keep on the improving of "Horizon translatable strings rules" ( > https://etherpad.openstack.org/p/i18n_translatable_strings) Educate > our developers. > > * how to maintain the priority definition of documents > #1: Team discussion and team decision, including both i18n team and doc team. > #2: Keep up to date of the priorities defined now: https:// > wiki.openstack.org/wiki/I18nTeam/docs-translation > > Let's define some action items based on these useful suggestions. > Keep on the discussion in the ML. We could make a list of actions > and owners in our next I18n meeting on Nov 20th. > The I18n meeting of this week will be ignored because of the summit. > > Thank you all for your active participation and contributions. > Merci. > > Best regards > Ying Chun Guo (Daisy)

1 0

Re: [Openstack-i18n] Pootle and Zanata trial - summary of responses from translators
by Ying Chun Guo 05 Nov '14

05 Nov '14

Hello, all Till now, I got responses from 5 translators in Japanese, Korean, Spanish, French and Chinese translation team. 4 of them clearly described their preferences is Zanata. Here are some comments from them to support Zanata: "Using Zanata, cooperation with other translators is easier: chat room, listing translators who are translating at the same time, comments if a translation is rejected." "The role management of Zanata is powerful. It clearly defines translators, reviewers, and project maintainers." "I like the Project-wide search and replace feature in particular. It allows translators or maintainer to search for a word, a phrase, a sentence, or a paragraph and replace it across multiple files within a single project. It is extremely useful when you do the final editing or reviewing." "I guess the impression a translator can have is that Zanata is more user friendly, whilst Pootle looks a bit quirky makinf finding info or the right links a bir more difficult. I think Zanata is very easy to use and also promote s translator engagement." Also, there are some problems with Pootle which will block us: The support of CJK (Chinese font, Japanese font and Korean font) is poor, for example: saved translations in Korean font is ???; saved translations in CJK fonts do not seem to be recognized by the TM. No official client till now. Our current translation process (uploading, downloading and reviewing) could not be implemented. So as a summary of the translators evaluation, we would prefer to use Zanata. If you have any questions, please let me know. Best regards Ying Chun Guo (Daisy) Ying Chun Guo/China/IBM wrote on 2014/10/16 17:04:27: > Ying Chun Guo/China/IBM > 2014/10/16 17:04 > > To > > openstack-i18n(a)lists.openstack.org, > > cc > > Subject > > Pootle and Zanata trial > > Hello, team > > Pootle and Zanata trial are ready for test. > 1. Pootle > http://23.253.231.198/projects/ > 2. Zanata > http://15.126.226.230:8080/ > > I need volunteers to test features and feed back how satisfied you feel. > I use an Etherpad page to track: > https://etherpad.openstack.org/p/translation-tools-comparation > > I have gotten volunteers from Korean and Indian team. > I'm looking for volunteers from other translation teams. > > If you want to help, please let me know. > If you want to try admin features, send me emails with your account ID. > > Thank you. > > Best regards > Ying Chun Guo (Daisy)

1 1

Summaary of Paris Translators meeting
by Ying Chun Guo 05 Nov '14

05 Nov '14

Hello, team There was a session yesterday in Paris Design summit to gather translators together. There were 6 translation teams joined the meeting locally. They are French team, Spanish team, German team, Catalan team, Chinese Taiwan team, and Chinese team. Some team members were trying to join the meeting remotely through Google Hangout. Yet they failed because of a fault made by me. I'm very sorry for that. We discussed how to build translation teams, how to make a high quality translation, and how to maintain the priority definition of documents. There are some good suggestions I could collect. Feel free to add more if I miss. * how to build translation teams #1: Use local Openstack meetups to promote translations #2: Use a blog post on OpenStack planet to promote translations. #3: Give the new comers a start point #4: Give people a goal and a timeframe (a focus) #5: A overall description of translation priorities, including both docs and messages #6: Create mailing lists on OpenStack infrastructure for local translation teams #7: Improve our tools to clearly state translators contributions and teams progresses. Integrate with Stackalytics in the future. * how to make a high quality translation #1: Maintain a glossary #2: Report bugs to projects if the problems of translations are due to the source strings, with a "i18n" tag. #3: Report bugs i18n team if the problems of translations are due to the translation quality, with a tag of language code. ( https://bugs.launchpad.net/openstack-i18n) #4: Keep on the improving of "Horizon translatable strings rules" ( https://etherpad.openstack.org/p/i18n_translatable_strings) Educate our developers. * how to maintain the priority definition of documents #1: Team discussion and team decision, including both i18n team and doc team. #2: Keep up to date of the priorities defined now: https://wiki.openstack.org/wiki/I18nTeam/docs-translation Let's define some action items based on these useful suggestions. Keep on the discussion in the ML. We could make a list of actions and owners in our next I18n meeting on Nov 20th. The I18n meeting of this week will be ignored because of the summit. Thank you all for your active participation and contributions. Merci. Best regards Ying Chun Guo (Daisy)

1 0

Infrastructure Translations Tools session at Kilo Summit
by Elizabeth K. Joseph 31 Oct '14

31 Oct '14

Hello translators! Thanks for your work evaluating Pootle and Zanata, the etherpad[0] will be very helpful to us. If others could chime in on Pootle in the next week or so it would be great. The Infrastructure team has reserved a spot in our track at the summit next week in order to discuss the tools and next steps based on your input and what Andreas and I have discovered about maintainability and process with regard to both tools. The session will be on Thursday at 11AM local (Paris) time: http://kilodesignsummit.sched.org/event/d40800cfbdcd2c9cf752c3cede10cf6e#.V… Please join us if you're available. We've put some infrastructure notes and what we expect from the translations team in the "Summit session" part of our etherpad, so if there are other topics you wish to cover, please add them there: https://etherpad.openstack.org/p/kilo-translations If you're not available to join, feedback here on list, on the above etherpad or to Daisy, Andreas or myself is welcome so we can make sure your opinions/suggestions are represented at the session. [0] https://etherpad.openstack.org/p/translation-tools-comparation -- Elizabeth Krumbach Joseph || Lyz || pleia2

3 3

Need more inputs: Pootle and Zanata trial
by Ying Chun Guo 31 Oct '14

31 Oct '14

Hello, Thank you for those volunteers who are registered as testers: Chandan Kumar Sungjin Kang Tom Fifield Andreas Jaeger Marian Tort Pablo Iranzo Maxime Coquerel (ZiGMaX) I would like to collect more inputs from you. Please response to me with answers to those questions by next Tuesday: (You could response my personal email if you don't want to public your choice.) 1. Which tool do you prefer? 2. Why do you make such choice? e.g. what features of the selected tool do you like? what features of the other tool do you not like? Your inputs will help us to provide good translation services to all translators. Thank you in advance. Best regards Ying Chun Guo (Daisy) ----- Forwarded by Ying Chun Guo/China/IBM on 2014/10/31 11:25 ----- Ying Chun Guo/China/IBM wrote on 2014/10/16 17:04:27: > Ying Chun Guo/China/IBM > 2014/10/16 17:04 > > To > > openstack-i18n(a)lists.openstack.org, > > cc > > Subject > > Pootle and Zanata trial > > Hello, team > > Pootle and Zanata trial are ready for test. > 1. Pootle > http://23.253.231.198/projects/ > 2. Zanata > http://15.126.226.230:8080/ > > I need volunteers to test features and feed back how satisfied you feel. > I use an Etherpad page to track: > https://etherpad.openstack.org/p/translation-tools-comparation > > I have gotten volunteers from Korean and Indian team. > I'm looking for volunteers from other translation teams. > > If you want to help, please let me know. > If you want to try admin features, send me emails with your account ID. > > Thank you. > > Best regards > Ying Chun Guo (Daisy)

1 0

Translation update process for stable branch(es)
by Akihiro Motoki 28 Oct '14

28 Oct '14

Hi all, In this mail I would like to discuss what releases do we accept translations. At now there is no systematic process when we import translations after the initial release of some version (Juno, Icehouse, ...). Importing translations to stable update is done occasionally so far. It is almost up to me. When I noticed some need for translation update (mainly in Japanese :-)), I propose a patch to import translations. It is really not systematic. If I am busy, I don't check it. This is the reason the first Icehouse update didn't have translation update. Questions are: - What release(s) we accept translations? Note that "Accept translations" means translations will be imported into a stable branch and releases as a part of the stable update release. My idea is to accept translations only for the latest stable release. - When should we import translations to a stable branch? Systematically (as a team)? Occasionally (up to someone's interest)? My vote is to import translations for each stable update of the latest stable branch. At least the first and second stable update (201X.Y.1 or .2) need to be considered. If we decide to do import as a stable release process as a team, we should assign someone to work on for each stable update (because I can't always take care of it). Assigned person(s) should check the date of a next stable update, check if there are new translations to be imported, and then propose a patch to import translations to a corresponding stable branch. I already have a consensus with the stable maintenance team that the deadline of translations import proposal is 3 day after the freeze date. The freeze date of a stable maintenance release is usually announced in stable-maint list. Thought? Any volunteer? -- Akihiro Motoki <amotoki(a)gmail.com>

4 9

OpenStack Docs and OpenStack Academy
by Frans Thamura 28 Oct '14

28 Oct '14

Hi all sorry for cross posting I have several schools, univs and company that join the translation program, and there are discussion regarding this work. because this is voluntaire based work they want a "aknowledgement" and this is my proposal to them 1. OpenStack User Group in their places (as sub OSUG). 2. OpenStack Translation Team 3. OpenStack Academic Team (because we start from Insallation Guide and Training Guide) In another area, the companies that work with me, now also bring to become HP Helion Partner (and Sub Partner) and Ubuntu Advantage Sub-Partner (Which I stand as partner of UA). Any legal thing that I must process, that I can guarrantee this work will grow the openstack movement in this country, and all the content from OpenStack will manage in the same web with OpenStack , https://www.transifex.com/organization/openstack/ I got this idea, because slow process in translation, and there are hugh 55.000 word we need to work :) My propsal If a school and univ commit to join the work, we can bring "OpenStack Translation Team" or "OpenStack Training Guide Team" but the logo of openstack is belong to "openstack foundation" any idea all Thx

2 2

Pootle and Zanata trial
by Ying Chun Guo 24 Oct '14

24 Oct '14

Hello, team Pootle and Zanata trial are ready for test. 1. Pootle http://23.253.231.198/projects/ 2. Zanata http://15.126.226.230:8080/ I need volunteers to test features and feed back how satisfied you feel. I use an Etherpad page to track: https://etherpad.openstack.org/p/translation-tools-comparation I have gotten volunteers from Korean and Indian team. I'm looking for volunteers from other translation teams. If you want to help, please let me know. If you want to try admin features, send me emails with your account ID. Thank you. Best regards Ying Chun Guo (Daisy)

4 10

Japanese operations-guide does not build
by Andreas Jaeger 23 Oct '14

23 Oct '14

The Japanese operations-guide fails to build due to some XML errors that seems to be coming from the translated files Could somebody check and fix the translations, please? https://review.openstack.org/#/c/130133/ http://logs.openstack.org/33/130133/1/check/gate-operations-guide-tox-check… Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 8

Wiki.openstack.org now supports translations
by Stefano Maffulli 23 Oct '14

23 Oct '14

Hello folks, I just wanted to quickly update the i18n team that OpenStack wiki now supports translations. For example, I marked for translation the release notes for Juno: https://wiki.openstack.org/wiki/ReleaseNotes/Juno Pages need to be marked for translation and documentation on how to do that is on Mediawiki Translate help page: https://www.mediawiki.org/wiki/Help:Extension:Translate The short version is: - Edit the page and add the tag <language /> on top - wrap the whole content of the page in the tags <translate> </translate> - save the page and follow instructions on the page itself Let me know if you have more questions. Regards, Stef PS thanks to Fungi for fixing https://bugs.launchpad.net/openstack-ci/+bug/1254911 and Niklas Laxström (Nikerabbit) for fixing the issue upstream. -- Ask and answer questions on https://ask.openstack.org

4 5

Removal of Horizon translations for OLD releases from Transifex
by Akihiro Motoki 22 Oct '14

22 Oct '14

Hi, I would like to discuss when we remove Horizon translations for *old* releases from Transifex. My proposal is to remove translations for old releases when a corresponding stable release is marked as EOL (end of life). After the final release of some version, the corresponding Transifex Horizon resources will be removed. Havana is now EOL and 2013.2.4 release on Sep 23, 2014 is the final Havana release. If the above proposal is accepted, we will remove Havana translation. Thought? Thanks, Akihiro

3 4

Fwd: Making an infra+translations session valuable at the Summit
by Elizabeth K. Joseph 18 Oct '14

18 Oct '14

Hello translators! The Infrastructure team is currently discussing whether we'll have a translations tools session in one of our slots during the session. Please feel free to chime in on the Etherpad linked in the email below if you also have feedback. Thanks. ---------- Forwarded message ---------- From: Elizabeth K. Joseph <lyz(a)princessleia.com> Date: Fri, Oct 17, 2014 at 1:45 PM Subject: Making an infra+translations session valuable at the Summit To: OpenStack Infra <openstack-infra(a)lists.openstack.org> Cc: Ying Chun Guo <guoyingc(a)cn.ibm.com> Hi everyone, My plane will be in the process of landing during our meeting on Tuesday, so I'll be in that unfortunate spot between air wifi and ground wifi. So instead of a meeting agenda item you get an email thread! There is a question as to whether a translations session will be valuable during summit since we have limited slots. So as promised at the last meeting I've put together this Etherpad to help us figure that out: https://etherpad.openstack.org/p/kilo-translations What I need from all of you is to chime in (here or in the pad) on what we should discuss and where we need to push forward so we can confirm that a discussion at summit with be valuable. If there are things I should research (like API usefulness/flexibility as compared to our current Transifex scripts) or specific questions about maintainability that I should follow up on, please let me know. The week before Paris I'll be working from the east coast where my environment will be quite accommodating to this kind of research and follow-up. Thanks. -- Elizabeth Krumbach Joseph || Lyz || pleia2

1 0

Obsolete documentation resources
by Andreas Jaeger 15 Oct '14

15 Oct '14

I see that some people are still translating the old z-old* resources: https://www.transifex.com/projects/p/openstack-manuals-i18n/resources/ This includes the old basic Install guide that has been removed over a year ago ;( I suggest to remove all of them. Or is there any reason to keep some of them? Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

5 6

IRC meeting tomorrow
by Ying Chun Guo 15 Oct '14

15 Oct '14

Hello, We will have the I18n meeting tomorrow at 0800 UTC in the channel of #openstack-meeting. We could use this time slot to discuss translation related topics in Paris summit, including: * Translators/I18n meet up * Translation tool discussion Feel free to propose any interested topics you have. Talk to you tomorrow. Best regards Ying Chun Guo (Daisy)

2 1

Documented translation infrastructure
by Andreas Jaeger 15 Oct '14

15 Oct '14

Elizabeth and myself just had a documentation session and created the following wiki page to document what our infra scripts do: https://wiki.openstack.org/wiki/Translations/Infrastructure If you have any questions, please ask - and let's improve the documentation further! Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 4

Juno Horizon translation import
by Akihiro Motoki 10 Oct '14

10 Oct '14

Hi translators, As Daisy announced last week, I will propose a patch to import Horizon translations at Oct 9. My planned time is around 1300UTC Oct 9. If you have any problems let me know. The criteria of translation progress in my mind is 95%. Languages with >= 95% translated will be imported. Although we voted and the criteria is 100% or with language coordinator request, Juno Horizon has a lot of translation strings, so I think it is reasonable. At the moment, 11 languages with over 95% and 8 languages with 99%. Thought? I would like not to enforce strict criteria, so if there is any request, please let me know. Thanks, Akihiro

3 5

Translators meet-up in Paris summit
by Ying Chun Guo 09 Oct '14

09 Oct '14

Hello, team We got a 40 minutes translators meet up scheduled in Paris summit: http://kilodesignsummit.sched.org/event/799166eb7cc14d410dcc712621ba318c I know there will be 10+ translators to Paris summit, from Franch, Spanish, Japanese, Chinese, and etc. Let's have a face to face meeting there. An Etherpad page is opened to collect topics in this session: https://etherpad.openstack.org/p/paris_translators_meetup Welcome to input your thoughts there. If we have special topics that need more time to work on, we could claim a "project pod" session to get extra time to work on it. So let's do the brainstorming firstly. Best regards Ying Chun Guo (Daisy)

1 0

Notices about Horizon translation
by Ying Chun Guo 03 Oct '14

03 Oct '14

Hello, all Horizon translations for Juno is almost over. Now there are 11 languages reaching 97% completion rate: Chinese (China), Japanese, Chinese (Taiwan), French, German, Polish (Poland), Portuguese (Brazil), Spanish, English (United Kingdom), English (Australia), Korean (Korea). Congratulations to those translation teams, and many thanks to the coordinators and translators. There are some notices I would like to let you know. 1. Horizon RC1 (release candidate 1) will be cut in 1 day or 2. There are some string freeze exceptions in RC1 in recent days. Please pay attention to the resources update in Transifex even after you complete the translation. 2. After communication with Horizon team, Horizon RC2 (release candidate 2) will be only for translations. We got an extra one week to work on the translation after RC1. The deadline for translation is set to Oct. 9th for the moment. 3. After RC1 is cut, the Juno dev code repository will be changed from "master" branch to "stable/juno" branch. At the same time, the links to Juno translation resources in Transifex will be changed and suffixed with "*-juno". I will let you know when the changes are made. Please pay attention to my following emails. Thank you very much for your hard work! Best regards Ying Chun Guo (Daisy)

4 4

I18n meeting tomorrow
by Ying Chun Guo 02 Oct '14

02 Oct '14

Hello, all We will have our I18n meeting tomorrow at 0800 UTC in the channel of #openstack-meeting. We could discuss following topics: * Status update on Horizon translation * Translators' meet up in Paris summit * Open discussions Welcome to attend. Thanks and best regards Ying Chun Guo (Daisy)

3 2

Call for participation: Juno translation starts
by Ying Chun Guo 02 Oct '14

02 Oct '14

Hello, all The translation for Juno release has been started. In this release, we focus on the Dashboard translation, i.e. Horizon. If you want your language pack to be shipped with OpenStack Juno, please join the translation work. We especially need translators in the following languages: German, Czech, Polish, Portuguese, Chinese (Taiwan), Dutch, Serbian, Hindi and Russian. The translations of these languages translation have made good progress, only around 800 strings left. If these translations could be finished by Oct. 2nd, these language packs could be included in Juno release. We use Transifex to manage the translation. Here are the translation resources that need translation: https://www.transifex.com/projects/p/horizon/resource/openstack-dashboard-t… https://www.transifex.com/projects/p/horizon/resource/horizon-translations/ https://www.transifex.com/projects/p/horizon/resource/horizon-js-translatio… If you are a member of your translation team, just jump in and translate. If you are not, you need to register an account in Transfiex and request to join your translation team. If you have any problems with the translation, please send an email to openstack-i18n(a)lists.openstack.org. The whole I18n team would be there to help. Thank you. Best regards Ying Chun Guo (Daisy)

3 2

Comments for translators in Horizon source codes
by Ying Chun Guo 01 Oct '14

01 Oct '14

Hello, all It looks like Horizon developers write many comments in their codes to translators. According to https://docs.djangoproject.com/en/1.7/topics/i18n/translation/#comments-for…, these comments should show up in the po files. Yet I checked English version po files and found no comments there. I think the problem may be caused by the po file generation method. Is there anybody who would like to look into this issue? Best regards Ying Chun Guo (Daisy)

4 7

"sell puppies" and "sold puppies" in Horizon
by Ying Chun Guo 30 Sep '14

30 Sep '14

Hello, all If you are translating Horizon today, you may notice two new strings appeared in "Juno - Horizon translations": "sell puppies" and "sold puppies". Don't worry about the translations of these two strings. They are just for testing. You could translate them as usual or just copy the English version there. Best regards Ying Chun Guo (Daisy)

1 0

[nova] new log warning, need string freeze exception
by Matt Riedemann 30 Sep '14

30 Sep '14

I've got an rc1 bug which adds a new warning message to the logs, it's not a user-facing error message change so I figure this is safe for string freeze - can someone confirm? https://review.openstack.org/#/c/123811/5/nova/virt/libvirt/driver.py -- Thanks, Matt Riedemann

2 1

translation member coordination
by Frans Thamura 29 Sep '14

29 Sep '14

hi all we have a lot new translator right now, but we still dont have fulltime and yes as the coordinator, i found several people do translation, and i found also several translate horizon, which I am working with training guide and installation guide any idea to know, which area that we should work. sadly, i dont think can release the horizon in on time, because the time deadline. i need to know, the contribution of each member for the openstack and i accidently several translated string, but i dont know it. this is because i visiting and review several guide can help all? F

3 3

[Keystone] String Freeze Exception for https://review.openstack.org/#/c/119452
by Morgan Fainberg 23 Sep '14

23 Sep '14

A release blocking change[1] is adding an exception for a timeout acquiring a connection object from a pool. This string change is meant to help ensure we have clearly communicated the error case. This change has not merged as of the writing of this email but is pending final review. Bringing it to the attention of this list per the wiki [2]. [1] https://review.openstack.org/#/c/119452 [2] https://wiki.openstack.org/wiki/StringFreeze

1 0

Horizon translation check site
by Akihiro Motoki 18 Sep '14

18 Sep '14

Hi I18N folks, I can have time to setup a new translation check site of Horizon. The URL is unchanged and only the password is changed. http://157.7.133.23:13580/ Username: demo or admin Password: i18n-juno Note that a new machine only has 16GB disk due to VM. Please make sure that only small volume 1~2GB x ~2 can be created. I would like to know who uses the Horizon translation check site in the past and current releases. I am not sure how many people use the site and it would be a good information whether we need this kind of site as OpenStack infrastructure. Thanks, -- Akihiro Motoki <amotoki(a)gmail.com>

8 7

Some more required changes in translations.
by Yves-Gwenaël Bourhis 18 Sep '14

18 Sep '14

Hi all. We have some pending patches here: https://review.openstack.org/121842 https://review.openstack.org/121879 https://review.openstack.org/121913 https://review.openstack.org/121957 https://review.openstack.org/121962 https://review.openstack.org/121972 These patches are *needed* to properly handle the translations in all languages, however if we merge them now you will have some extra strings to re-translate before the release. Please give all your feedback to know if you can handle them in the shortcoming, or if we have to wait before merging. NOTE that these changes allow you to properly translate the strings on the action buttons in Horizon. Thanks. -- Yves-Gwenaël Bourhis

2 4

[Keystone] String Freeze Exception for https://review.openstack.org/#/c/121246/
by Morgan Fainberg 18 Sep '14

18 Sep '14

A release blocking change[1] is adding a new exception for handling a case where there are multiple SQL configurations in a multi-domain setup. This is a case where the exception makes sense as there are no current exceptions that cover this specific error in enough detail. Bringing it to the attention of this list per the wiki [2]. [1] https://review.openstack.org/#/c/121246/ [2] https://wiki.openstack.org/wiki/StringFreeze — Morgan Fainberg

1 0

[nova] string freeze exception/fyi for https://review.openstack.org/#/c/121916/
by Matt Riedemann 17 Sep '14

17 Sep '14

This [1] changes an error message that was super generic to have more context and is a problem we were seeing in the gate. Since the Nova PTL was one of the +2s on the change I'm assuming he's OK with the change. Bringing it to the attention of this list per the wiki [2]. [1] https://review.openstack.org/#/c/121916/ [2] https://wiki.openstack.org/wiki/StringFreeze -- Thanks, Matt Riedemann

1 0

IRC meeting tomorrow
by Ying Chun Guo 17 Sep '14

17 Sep '14

Hello, all We will have the I18n meeting tomorrow at 0800 UTC in the channel of #openstack-meeting. We begin to sprint on horizon translation now. Hope language coordinators could show up if the time slot is OK for you. We could discuss following topics: * Horizon translation progress check and issues collection * Open discussions Talk to you tomorrow. Best regards Ying Chun Guo (Daisy)

1 0

Slides on Localization efforts in OpenStack from openstack meetup at Pune (India)
by chandankumar 15 Sep '14

15 Sep '14

Hello, Last Saturday i have presented a talk on "Localization efforts in OpenStack' in the openstack india meetup held at Pune. Here is the slide link: [1.] http://chandankumar.dgplug.org/talks/index.html#1 Here is the meetup link. [2.] http://www.meetup.com/Indian-OpenStack-User-Group/events/200883082/ Thanks, Chandan Kumar

2 1

FUEL-CLOUD : Frequently used entries for Localization of cloud technologies
by chandan kumar 10 Sep '14

10 Sep '14

Hello, We are pleased to release the first draft version of FUEL-CLOUD. FUEL-CLOUD is a collection of commonly used entries for localization of cloud computing related software and docs. Today, Cloud is very new to this world and is an emerging technology to the future. Lots of companies are switching their application to cloud. To understand and reach to various corner of world, it is necessary to made it available in different languages. To make the life of translators and localizer easier, it is necessary to provide a list of commonly used entries from cloud computing with its context. fuel-cloud module is prepared from different cloud technologies so that the module can be used across platform. This module will help to use a particular word precisely in cloud computing. Here is the link of FUEL-CLOUD module. https://docs.google.com/spreadsheets/d/1UYbFoANH7pFdjaEJ3aGFZcYaE22-Ierf4iB… We request everybody to take a look at the module and suggest changes in the module. FUEL Project (http://fuelproject.org/) is the largest and fastest growing open source based language resource repository that works to create standard terminology, style guide, assessment methodology etc with the help of community and different organizations. Currently it works with c.60 languages community. Links: Thanks, Chandan Kumar

4 3

Fwd: Call for Papers - FUEL GILT Conference 2014
by chandankumar 10 Sep '14

10 Sep '14

FYI -------- Original Message -------- Subject: Call for Papers - FUEL GILT Conference 2014 Date: Fri, 5 Sep 2014 17:23:55 +0530 From: Rajesh Ranjan <rajesh672(a)gmail.com> Reply-To: fuel-discuss(a)lists.fedorahosted.org To: fuel-discuss(a)lists.fedorahosted.org <fuel-discuss(a)lists.fedorahosted.org> FUEL GILT Conference 2014 November 14-15, 2014 Pune, India http://fuelproject.org/gilt2014/index#paper Welcome to the 2nd FUEL GILT Conference - the largest event of FOSS language technology - its challenges, solutions, best practices and its conventions. FUEL GILT Conference is all about language technology world, all about GILT industry - G11N, I18N, L10N, and Translation world. The event is showcase of the efforts of volunteer communities and different organizations in the field of language technology. This event also tells us the pain and conflicts of different cultures and languages. All things are revolved around the language - related to words! We are the worshipper of words! The organizers of FUEL GILT Conference are Red Hat and C-DAC GIST! Thanks a lot to both the organizations for continuous support and helping hand. FUEL is growing only because of the support of volunteer communities world-wide and several well known organizations! The power of the event is the power of collaboration, the power of sharing, the power of volunteerism! Currently, almost 60 language communities are working with the FUEL Project across various domain including desktop, mobile, cloud, web, agriculture, health etc. Since 2008, FUEL Project is consistently working with the different language communities to provide standard linguistic resources eg. terminologies, style guides, assessment methods etc to the world. Like last year, please collaborate and cooperate to make the event a huge success! Call for Papers We are pleased to announce the Call For Papers for FUEL GILT Conference 2014. Abstracts are invited for presentation/workshop on substantial, original and unique research on all aspects of GILT Industry (Globalisation, Internationalization, Localization and Translations) with special focus on linguistic resources, standardization, e-governance and language technology. The areas of interest include, but are not limited to, the following: Language Technology; Corpus Linguistics; Machine Translation; Natural Language Processing; Globalization; Language and Translations; Technical Terminology; Dictionary; Style Guide; Unicode/CLDR; Script Grammar; Translation Editor; Rendering Systems; Quality Assessment; Fonts; Input methods; FOSS and Localization; Computational Linguistics; Language & Culture; Dying Language; Internationalization Please visit the page for detailed information: http://fuelproject.org/gilt2014/index Thanks! Regards, Rajesh Ranjan twitter: @kajha <https://twitter.com/kajha> facebook: rajeshkajha <http://www.facebook.com/rajeshkajha> www.rajeshranjan.in <http://www.rajeshranjan.in>

1 0

Allow translators to translate BatchActions
by Yves-Gwenaël Bourhis 09 Sep '14

09 Sep '14

Hi all, I reported a bug concerning the way strings where conjugated on action buttons here: https://bugs.launchpad.net/horizon/+bug/1307476 The issue is that automatic conjugation works in English, but may lead the impossibility to have a properly translated string in some languages which have different and more complex conjugation rules. I made a patch to fix this here: https://review.openstack.org/#/c/91338/ However, not all strings are fixed in this patch, only a few ones, and I kept the legacy conjugation method not to brake all existing strings on the action buttons at once. This patch will allow developers to progressively change strings on action buttons per translators request, to strings which can have proper translations. I also added contextual markers on instance actions or status. i.e.: "Shut Down" could be an action to perform, or an instance status, which is the same string in English but different in many languages, this patch allows differentiating them. Could it help to have a test catalog on Transifex based on this patch to have translators feedback on the change brought to the strings? The translators could give feedback to know if translations are improved. Also translators could ask for more strings which they could not translate properly before, to be migrated to this new translating method on action buttons as new (dependent) patches. Also, how fast do translators want all the existing "action buttons" and "status" strings to be migrated to this method? If all are migrated at once we would lose a lot of the currently existing translations on action buttons and status (even though they are not properly translatable) and they would have to be translated again. So adding patches progressively could bring smooth changes. This is where translators feedback would be interesting to know if: - The changes allow translating properly? - They want smooth changes on action buttons to translate progressively, or want a complete fix right now because to many buttons can not be translated properly? - They want changes in other places too where they can not currently translate properly? Thanks -- Yves-Gwenaël Bourhis

4 4

[Horizon Juno Translations] Proposed string changes -- Request for Comments
by Akihiro Motoki 09 Sep '14

09 Sep '14

Hi I18N folks, During Horizon Juno translations, I found several points to be improved. I proposed several patches to Horizon review. All of them affect translations but I believe it helps us for better translations. Can I move them forward? If you have any concern, please reply to share it. - https://review.openstack.org/#/c/120009/ Translation feedback - Correction/update of help texts - https://review.openstack.org/#/c/120010/ Translation feedback - Add contextual marker for short strings - https://review.openstack.org/#/c/119602/ Avoid string concatenation in Volume Type Extra Spec Edit - https://review.openstack.org/#/c/119903/ Replace "tenant" with "project" in visible strings Thanks, Akihiro

1 0

I18n meeting tomorrow
by Ying Chun Guo 03 Sep '14

03 Sep '14

Hello, all We will have our I18n meeting tomorrow at 0800 UTC in the channel of #openstack-meeting. We could discuss following topics: * Update on translation tools * Kick off Juno Horizon translation * Open discussions Welcome to attend. Thanks and best regards Ying Chun Guo (Daisy)

1 0

Fwd: [openstack-dev] [all] Gerrit Downtime on August 30, 2014
by Tom Fifield 29 Aug '14

29 Aug '14

This may affect transifex project name... -------- Forwarded Message -------- Subject: [openstack-dev] [all] Gerrit Downtime on August 30, 2014 Date: Thu, 28 Aug 2014 08:39:20 -0700 From: James E. Blair <corvus(a)inaugust.com> Reply-To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> To: OpenStack Development Mailing List <openstack-dev(a)lists.openstack.org> CC: openstack-infra(a)lists.openstack.org Hi, Gerrit will be unavailable starting at 1600-1630 UTC on Saturday, August 30, 2014 to rename the glance.store project to glancestore. I apologize for the late notice, however, in another thread on the -dev list, you'll find the rationale for executing this change swiftly. Thanks, Jim _______________________________________________ OpenStack-dev mailing list OpenStack-dev(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

4 3

Glossary clarification?
by Andreas Jaeger 22 Aug '14

22 Aug '14

I see on: https://wiki.openstack.org/wiki/I18nTeam/docs-translation "08/21/2014 - Waiting for a feedback from the doc team about the content of the Glossary " What exactly is your question? could you give some background, please? Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 4

Switch to itstool for docs translation?
by Shaun McCance 20 Aug '14

20 Aug '14

Hi all, I've been working on switching the docs translation infrastructure over to itstool. This affects openstack-manuals, operations-guide, and api-site. The current tools are based on xml2po, but they don't call xml2po directly. Instead, they import xml2po and mess around with its internals to get some custom behavior. itstool is designed to handle custom behavior with rules from the W3C Internationalization Tag Set (ITS). You can see the ITS I put together so far here: https://review.openstack.org/#/c/91869/3/os_doc_tools/resources/openstack.i… Using ITS also allows us to do local ITS attributes to override the behavior for specific elements. See a simple example here: https://review.openstack.org/#/c/91872/1/api-quick-start/src/docbkx/api-qui… Most messages in the PO files will be the same. The one big difference will be in how placeholders are done when there's a block-level element inside a block-level element (a practice I discourage anyway). Blueprint and some patches: https://blueprints.launchpad.net/openstack-manuals/+spec/itstool-for-docs https://review.openstack.org/#/q/topic:bp/itstool-for-docs,n,z I'd like to get input from translators, as well as any other docs folks who've worked on this. Most of the document translations are incomplete anyway, but it would nevertheless be best to do this at the beginning of a release cycle. -- Shaun

4 12

IRC meeting tomorrow
by Ying Chun Guo 20 Aug '14

20 Aug '14

Hello, all We will have our IRC meeting tomorrow at 0800 UTC. >From now on, we will use only 1 meeting time - 0800 UTC - for I18N meetings, till we get attending requests from translators in America. We could discuss following topics: * Conclusions for the discussion "documents categorization" * Next steps for translation tools * Open discussions Thanks and best regards Ying Chun Guo (Daisy)

1 0

Pootle Demo: Tuesday 19 August at 0800 UTC
by Elizabeth K. Joseph 19 Aug '14

19 Aug '14

Hi everyone, We've finally pinned down a date and time for the Pootle Demonstration by Pootle contributor Dwayne Bailey! It will be on Tuesday, 19 August at 0800 UTC http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140819T08 We'll probably coordinate in #openstack-translation, folks can ask questions there or join the video (we'll provide a link in channel when it's set up). The session will be recorded and available on YouTube following the session so that others can review it if they miss the live demo. In the meantime, I'll be working to schedule an upgrade of our demo Pootle instance at http://translate-dev.openstack.org/ so that we have the latest RC version installed for their upcoming 2.6.0 release to work with. Please let me know if there's anything else I can do to help coordinate this. -- Elizabeth Krumbach Joseph || Lyz || pleia2 http://www.princessleia.com

1 3

FUEL GILT Conference 2014
by Rajesh Ranjan 14 Aug '14

14 Aug '14

Hi, FUEL GILT Conference 2014! Welcome to the 2nd FUEL GILT Conference - the largest event of FOSS language technology - its challenges, solutions, best practices and its conventions. FUEL GILT Conference is all about language technology world, all about GILT industry - G11N, I18N, L10N, and translation world. The event is showcase of the efforts of volunteer communities and different organizations in the field of language technology. This event also tells us the pain and conflicts of different cultures and languages. All things are revolved around the language - related to words! We are the worshipper of words! So, please mark your calendar - possibly 2nd/3rd week of November 2014. And the place is Pune, India - culturally one of the most vibrant city of India! We will announce the final date in about two weeks. Like last year, the organizers of FUEL GILT Conference are Red Hat and C-DAC GIST! Thanks a lot to both the organizations for continuous support and helping hand. FUEL is growing only because of the support of volunteer communities world-wide and several well known organizations! The power of the event is the power of collaboration, the power of sharing, the power of volunteerism! Currently, c.60 language communities are working with the FUEL Project. Since 2008, FUEL Project is consistently working with the different language communities to provide standard linguistic resources eg. terminologies, style guides, assessment methods etc to the world. Like last year, please collaborate and cooperate to make the event a huge success! Please keep visiting here for more details: http://fuelproject.org/gilt2014/index Here you can find report about 1st FUEL GILT Conference 2013: https://fedorahosted.org/fuel/wiki/fuel-gilt/2013 Thanks! -- Rajesh Ranjan www.rajeshranjan.in @kajha <https://twitter.com/kajha> Can the FOSS community save 197 endangered Indian languages? <http://opensource.com/community/14/7/save-endangered-language-today>

1 0

IRC meeting tomorrow
by François Bureau 10 Aug '14

10 Aug '14

Hello all, Tomorrow we will have our meeting at 0800UTC in IRC in #openstack-meeting. Daisy will be in vacation, so she has asked me to host this IRC meeting . We could discuss following items : * Documents categorization * Open Discussion Every other topics are welcomed too ! Dont hesitate to contact me if you want to add some into the agenda :) Thanks and best regards, François Bureau

3 2

Where should bugs on translation reported to?
by Akihiro Motoki 06 Aug '14

06 Aug '14

Hi, I would like to raise a question where we should report translation bug. Horizon project sometimes receives bugs on translations of OpenStack Dashboard. Horizon team notes the translation work is done on Transifex and marks such bug as Invalid. For example, https://bugs.launchpad.net/horizon/+bug/1353344 However, I noticed we don't have a official place where translation bug should be filed. Transifex is a platform for translators and it is not a bug tracking system. We already have "openstack-i18n" launchpad and can use it, but I am not sure who triages bug reports constantly. Handling translation bugs is not same as bug triaging in other projects as we need per-language bug triaging team (in theory). If we have a consensus on transltaion bug report, Horizon team can forward bugs on translations to the system. Just marking translation bugs as Invalid loses valuable bug reports and it is not good. Thought? I cannot join the I18N team meeting tomorrow due to meeting conflicts, but I hope someone leads the discussion. Thanks, Akihiro

2 1

Update of translation roadmap
by Marian Tort 05 Aug '14

05 Aug '14

Hi! Is it possible to have an update of the translation roadmap for next releases? I know there will be an update for Icehouse of Aug 7. Regarding Juno, is that Sep 4th? I'd also like to know if there is a translation check site for Juno? Is there any project in particular we need to focus on right now? There are several projects in Transifex, it would be nice to have a priority list :) Many thanks and sorry if anything has already been answered! -- Marian

2 1

Hi from a newbie :)
by Nicolas HAHN 05 Aug '14

05 Aug '14

Hello, I'm interested by OpenStack and I think a good way to learn is by proposing to contribute. I'm french (working in switzerland) and I've started to take a look at things about documentation and available translations. I found one documentation translated in french: "Démarrage rapide pour l'API OpenStack <http://docs.openstack.org/fr/api/quick-start/content/index.html>" I would like to propose my help, if it is accepted, to translate anything from english to french. I'm currently in the process of understanding how translations are managed, how things are working, for OpenStack. Best regards, Nicolas HAHN

2 1

openstack-ja.github.io outdated
by Andreas Jaeger 31 Jul '14

31 Jul '14

Hi, openstack-ja.github.io has an old version of the guide that is different from what we have on docs.openstack.org at: http://docs.openstack.org/ja/trunk/install-guide/install/yum/content/instal… The guide was last updated on 2014-04-27. I suggest to remove that version and point to the version on docs.openstack.org instead. I don't know who is responsible for that server and hope one of you can help, Andreas -------- Original Message -------- Subject: [Bug 1349285] [NEW] a description of /etc/xinetd.d/rsync is wrong in installation guide for rhel Date: Mon, 28 Jul 2014 07:55:12 -0000 From: Hisashi Osanai <osanai.hisashi(a)jp.fujitsu.com> Reply-To: Bug 1349285 <1349285(a)bugs.launchpad.net> To: aj(a)suse.de Public bug reported: In Japanese version of the installation guide, there is a wrong description for /etc/xinetd.d/rsync. Wrong configuration is : disable = false Correct configuration is : disable = no The rsync command doesn't run correctly with the wrong configuration OPENSTACK INSTLATION GUIDE FOR RED HAT ENTERPRISE LINUX, CENTOS, AND FEDORA - ICEHOUSE (Japanese version) => 10. Add Object Storage => 5. Edit the following line in /etc/xinetd.d/rsync: http://openstack-ja.github.io/openstack-manuals/install- guide/yum/content/installing-and-configuring-storage-nodes.html ** Affects: openstack-manuals Importance: Undecided Status: New -- You received this bug notification because you are subscribed to openstack-manuals. Matching subscriptions: os-manuals https://bugs.launchpad.net/bugs/1349285 Title: a description of /etc/xinetd.d/rsync is wrong in installation guide for rhel Status in OpenStack Manuals: New Bug description: In Japanese version of the installation guide, there is a wrong description for /etc/xinetd.d/rsync. Wrong configuration is : disable = false Correct configuration is : disable = no The rsync command doesn't run correctly with the wrong configuration OPENSTACK INSTLATION GUIDE FOR RED HAT ENTERPRISE LINUX, CENTOS, AND FEDORA - ICEHOUSE (Japanese version) => 10. Add Object Storage => 5. Edit the following line in /etc/xinetd.d/rsync: http://openstack-ja.github.io/openstack-manuals/install- guide/yum/content/installing-and-configuring-storage-nodes.html To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1349285/+subscriptions -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 5

Icehosue Horizon translation update
by Akihiro Motoki 30 Jul '14

30 Jul '14

Hi I18N folks, Icehouse stable update release 2014.1.2 is planned at Aug 7 [1]. I have a plan to update Horizon translations for this stable release. In the current plan I will import the latest Icehouse translations at Aug 1 and propose a patch to gerrit. Jul 31 is a planned date of the feature freeze for 2014.1.2. Please update Transifex by then if you want. At a glance at Transifex status, most languages (included in Icehouse) are 100%. Thought? [1] https://wiki.openstack.org/wiki/StableBranchRelease#Planned_stable.2Ficehou… Thanks, Akihiro

2 1

Re: [Openstack-i18n] [Openstack-docs] TG Indonesia Translation
by Ying Chun Guo 24 Jul '14

24 Jul '14

It looks great, Frans. We are using Transifex to manage the document translation now. https://www.transifex.com/projects/p/openstack-manuals-i18n/resource/traini… Would you like to join us? Go to I18n team to understand more about our translation work. https://wiki.openstack.org/wiki/I18nTeam Best regards Ying Chun Guo (Daisy) Frans Thamura <frans(a)meruvian.org> wrote on 2014/07/08 02:55:29: > Frans Thamura <frans(a)meruvian.org> > 2014/07/08 02:55 > > To > > "openstack-docs(a)lists.openstack.org" <openstack-docs(a)lists.openstack.org>, > > cc > > Subject > > [Openstack-docs] TG Indonesia Translation > > our indonesian translation > > still in OpenOffice and PDF > > still working to put in OpenStack;s standard > > review welcome > > https://drive.google.com/file/d/ > 0ByN0uD7ycYUqSXVFdXpHSHlvaVNuNmJHYnM2djhJUHRMT3BR/edit?usp=sharing > https://drive.google.com/file/d/ > 0ByN0uD7ycYUqeTlxdEVUa3NGcFRTRGtHWTl4SHFMOTEyUkZ3/edit?usp=sharing > > my team still working to make better wording for indonesia. > > > > > _______________________________________________ > Openstack-docs mailing list > Openstack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs >

6 17

Scheduling a Pootle demonstration
by Elizabeth Krumbach Joseph 24 Jul '14

24 Jul '14

Hi everyone, I work on the OpenStack infrastructure team and we're planning on supporting your team with whichever choice for translations tool you decide upon. There was just a Zanata demo this week, and I've reached out to the Pootle project at Daisy's request to organize a similar demo some time next week. The individual from Pootle who has volunteered to give the demo is in the UTC+1 time zone and has asked for some timing proposals from the team for when we can attend a demo so he can check his schedule and we can settle on a time. Suggestions? As a reminder, the infrastructure team set up a demo site for Pootle last October, details about this demo site can be found here if you wish to poke around: http://lists.openstack.org/pipermail/openstack-i18n/2013-October/000209.html Thanks. -- Elizabeth Krumbach Joseph || Lyz || pleia2 http://www.princessleia.com

5 13

Collaboration in Catalan translation
by Robla Mota, Yolanda 17 Jul '14

17 Jul '14

Hi, I'm Yolanda Robla. I work for HP , mostly in projects related to Openstack-Infra. I saw that there is an entry for catalan translation for Openstack and I'd like to collaborate with it. What should be the best way to start? Best Yolanda Robla Mota Cloud automation and Distribution Engineer yolanda.robla-mota(a)hp.com +34 605641639 Spain

4 4