September 2015 - OpenStack-I18n - lists.openstack.org

[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 09 Sep '15

09 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 07 Sep '15

07 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 07 Sep '15

07 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