- OpenStack-I18n - lists.openstack.org

Translation of Nova
by Ying Chun Guo 21 Sep '15

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

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