- OpenStack-I18n - lists.openstack.org

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

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

14 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