08:01:46 #startmeeting OpenStack I18n Meeting 08:01:47 Meeting started Thu Aug 21 08:01:46 2014 UTC and is due to finish in 60 minutes. The chair is Daisy. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:01:48 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:01:50 The meeting name has been set to 'openstack_i18n_meeting' 08:01:53 hello Daisyand chandankumar 08:02:05 Good morning, everyone. 08:02:15 * DeeJay1 partly i 08:02:31 We don't have attendees from both North America and South America for a long time. 08:02:43 So we will use only 1 time slot from today. 08:02:47 hello 08:03:38 Firstly, many thanks to fdot. He helped to host the previous meeting and made a wonderful table. 08:03:56 https://wiki.openstack.org/wiki/I18nTeam/docs-translation 08:03:58 yrw Daisy :) 08:04:38 #topic Conclude "documents categorization" and work out "next steps" 08:05:08 If I'm a new comers to doc translation, I cloud easily figure out my priority from this table. 08:05:25 fdot: do we have any left as to the document categorization table? 08:06:12 Daisy : I don't think so 08:06:24 Great. I think it's a wonderful table too. 08:06:34 but the size of each items are probably wrong 08:06:43 because it is moving all the time 08:06:46 Daisy, from table priority is clear. :) 08:06:48 it is just an indicator 08:07:10 is everybody agree with the priority into the table ? 08:07:17 We need somebody to keep on the update of this table. 08:07:32 I do have a question about glossory 08:07:39 I see it's high priority. 08:07:51 Glossary is attached to every documents in OpenStack. 08:08:08 If we translate glossary into different languages, how could we build it ? 08:08:33 I mean, glossary is not built separately. It's a part of every docs. 08:08:50 Even we translate it, we cannot display it. 08:10:36 Daisy, i have one query here 08:10:50 I think it's a question I should ask fifieldt or AJaeger. 08:11:06 what is the query? 08:11:58 translating whole lot of 15K word of gloassry is not that much useful 08:12:32 Glossary is not that big, rajeshr. Let me show you. 08:12:33 Daisy, rather we should concentrate on what chandankumar has proposed as fuel-cloud 08:12:46 http://docs.openstack.org/arch-design/content/go01.html 08:13:03 Daisy, http://docs.openstack.org/glossary/content/glossary.html 08:13:11 i was taking ^^ as a ref 08:13:44 oh. This one is bigger. 08:14:24 Daisy: yes this one is bigger 08:14:35 who is defining the content of the glossary ? 08:14:46 maybe there is too many things in it 08:14:52 should be doc team 08:15:16 fdot, Daisy i have proposed a fuel-cloud which contains only common entries across the docs. 08:15:29 it will be helpful to us during translation 08:15:42 chandankumar: give us a link, chandankumar . Sorry I lost it. 08:15:49 i have sent the mail to the i18n mailing list 08:15:57 Daisy, https://docs.google.com/spreadsheets/d/1UYbFoANH7pFdjaEJ3aGFZcYaE22-Ierf4iB6EcbBjuk/edit#gid=0 08:16:30 trac page: https://fedorahosted.org/fuel/wiki/fuel-terminology/fuel-cloud 08:16:37 http://lists.openstack.org/pipermail/openstack-i18n/2014-July/000698.html 08:16:40 I think, glossary in this table means the glossary in openstack-docs repository. It will be displayed as a part of each document. 08:16:41 Daisy, ^^ 08:17:21 Daisy, okay, now i can understand and then its fine 08:17:55 Translating "glossary" here, is just like we translate a common document. Chandankumar's fuel-cloud would help to get a consistent translation. They are different. 08:18:20 Daisy, sorry for confusion now got it 08:18:46 rajeshr chandankumar i am reading the document and i see a lot of entries wich are not relevant for a glossary 08:18:58 welcome, rajeshr. chandankumar 's work will be helpful if each translation team does the fuel-cloud translation at first, and then make the content translation. 08:19:04 for example, defining a volume is important 08:19:18 but not defining Volume Source or Volume Name 08:19:49 Daisy, fdot it is open for review 08:20:02 we need your feedback to improve it 08:20:07 Hope fifieldt could come and help to answer this question. 08:20:14 It is just a first draft 08:20:35 chandankumar: ok so how to contribute on this project ? 08:21:18 fdot, you can edit the google docs 08:21:56 fdot, we are storing the revisions in the google doc spread sheet 08:22:03 chandankumar: ok thanks 08:22:04 fdot, https://fedorahosted.org/fuel/wiki/contribution 08:22:17 So we have a concern to "glossary" in the high priority list. I will ask it in the ML and let's see what answers from doc team. 08:22:59 rajeshr: thanks :) 08:23:14 Based on fdot's table, I update the categories in Transifex. 08:23:16 https://www.transifex.com/projects/p/openstack-manuals-i18n/resources/ 08:23:17 Daisy: i am agree with you let's talk first with the doc team ;) 08:23:26 fdot, welcome 08:23:55 so in the table maybe we can change the priority of the glossary 08:24:03 You could see a drop down list in the right top, click it, you could filter based on the "category" 08:25:26 Anything else we should talk as to the categories? 08:26:07 we move to next topic. 08:26:20 #topic next steps to translation tools 08:26:44 We all know we are going to move away from Transifex. 08:26:49 yes 08:26:57 Does anybody have concerns to this decision? 08:27:11 both the tools have most of the features 08:27:29 pootle + zanata 08:27:46 Although we have been working with Transifex for a long time, we have to move away from it, since it's not open source. It's a community decision. 08:28:42 We, our translators, could choose a tool by ourselves. 08:28:46 open source tool. 08:29:14 Now we have connections with Zanata team and pootle team. They all made a demo to us. 08:29:50 Infrastructure team helped us to set up demo websites. Both of them have demo websites now. 08:30:15 chandankumar is right. Both of the tools have many features. 08:30:35 It's hard to say which is better and which is not. 08:30:49 yes 08:31:14 I have an idea as to the next step. 08:31:34 I will set up a project in both Zanata and Pootle. 08:31:48 two projects. One is in Zanata, and one is in Pootle. 08:32:13 Let's use them to translate for a while. And let's see which one is better to use, from a translator's perspective. 08:32:58 How do you think ? 08:33:08 it will be good. 08:33:20 If you have suggestions to help making decision, please speak out. 08:33:42 ur idea is fine, after set up please mail 08:33:46 hi Daisy, Carlos from the zanata team here... just ping us if you need any help setting that project up 08:33:57 Thanks, camunoz . 08:34:36 Daisy good idea +1 :) 08:35:02 Different people have different views. Infrastructure team would care about how easy it is to set up and maintain such a tool. Our translators should view from the usability perspective. 08:35:22 camunoz, ^^^ 08:35:37 yeah 08:35:56 So let's see how the usability of these tools by translating with them. 08:36:46 OK. let's move to open discussion. 08:36:52 #topic open discussions 08:37:12 I have two topics here. 08:37:27 Pairs summit will come soon. 08:37:47 If you have translators who want to join but no free tickets, please email me. 08:38:04 camunoz: if you want to join, email me too. :) 08:38:12 is there a deadline for sending the list ? 08:38:20 the soon the better. 08:38:25 ok 08:38:27 Daisy: will do. thx! 08:38:41 fdot: I think there should be many people who want to go from Paris. 08:38:55 Daisy, rajeshr probably will be going to paris summit. 08:39:05 is there a way to see in transifex which are the top contributors for a language ? 08:39:10 fdot: you could estimate a number, and let me know the number. 08:39:26 No, no such function in Transifex. 08:39:32 daisy: Ok i will send you by e-mail asap :) 08:39:46 Ok I will find an another way 08:39:54 rajeshr: do you have free registration key to pairs summit? 08:40:32 no i don;t have :) 08:40:34 fdot: I think the deadline for ATC registration code is Aug 24. 08:40:45 rajeshr: so I will get 1 for you. 08:41:18 fdot: but community should have some codes which have longer period of validity. 08:41:34 Daisy, thanks 08:41:47 Daisy: thanks 08:41:48 great. 08:41:57 Next topic is about Horizon translation. 08:42:10 The string freeze date is Sep 4th. Very near now. 08:42:36 Horizon resources in Transifex is up to date. 08:42:54 I see there are around 400+ new strings waiting for translation. 08:43:17 Daisy, will do that 08:43:31 So if you have free time, you could start the translation now, then you wont' get too busy in Sep. 08:43:58 I think we have at most 1 month to finish the translation. 08:44:06 since string freeze. 08:44:33 It might be good to start early, there are still a lot of features waiting for reviews so there'll likely be a lot of new strings added in the next couple of weeks 08:44:42 :) 08:45:00 jpich: thanks to jump out. 08:45:30 I guess there are a lot of new features in Horizon in Juno? 08:46:07 jpich: there is a question for you. Does Horizon have features removed from Icehouse to Juno? 08:46:37 Daisy: Not that I can think of 08:47:01 ok. 08:47:52 There's a lot of patches submitted, we're not quite sure at this point how many will make it through, but there's definitely still a lot going on 08:48:09 One more topic from me. 08:48:11 I'll keep you informed if there are exceptions approved after feature freeze 08:48:12 https://www.transifex.com/projects/p/nova/ 08:48:21 Thanks, jpich 08:48:35 Take a look at the resources under nova in Transifex. 08:49:22 Now nova messages have been split into different categories. 08:49:52 nova-translations contains all messages except log messages. 08:50:03 such as API response messages, exception messages. 08:50:29 In my mind, I think, we could translate such message in Juno release. 08:50:53 we could translate these messages in Juno release. 08:51:02 I want to get input from you. 08:51:25 It's 1800+ strings in nova-translations. 08:52:29 fdot: your thoughts? 08:52:37 chandankumar: and you? 08:53:39 API response message are display into Horizon 08:53:54 so we can translate them 08:53:57 Yes. 08:54:12 just looking if it is a lot of works 08:54:50 API messages are in nova-translations ? 08:54:50 I remember Horzion display the API response messages directly in the UI. 08:54:59 Yes. 08:55:23 12 620 words 08:55:30 The resources with nova-log-* are all log messages. 08:55:37 which is a little big 08:55:38 The other messages are in nova-translations. 08:55:46 I'm not sure Horizon is asking for the correct language from the APIs at the moment, but it's definitely a change we'll want to make (if it doesn't happen in Juno it will be in Kilo) 08:56:32 jpich: thanks for the information, so we are going to wait for this change before starting this part 08:56:33 Others to talk? 08:56:55 No? 08:57:08 I will close the meeting today. Thank you all for attending. 08:57:49 #closemeeting 08:58:19 #endmeeting