- OpenStack-I18n - lists.openstack.org

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

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 ਅਨਪੜ੍ਹ ਜਿਮੀਂਦਾਰ 08 Sep '15

08 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

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 27 Aug '15

27 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 21 Aug '15

21 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