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

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

17 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 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