08:00:41 #startmeeting OpenStack I18n Meeting 08:00:42 Meeting started Thu Feb 5 08:00:41 2015 UTC and is due to finish in 60 minutes. The chair is Daisy. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:43 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:45 The meeting name has been set to 'openstack_i18n_meeting' 08:00:56 who is around? 08:00:56 Daisy, Hello 08:01:03 Hi! 08:01:06 * DeeJay1 is here 08:01:11 Hello, Daisy. 08:01:21 epico, anish__ hello 08:01:26 Good to see you there ! 08:01:36 I don't see Carlos from Zanata team. 08:01:45 Hello Daisy :) 08:01:51 So we start from chandankumar's topic. 08:01:54 hello all :) 08:02:09 #topic #startmeeting OpenStack I18n Meeting 08:02:11 sorry 08:02:17 wrong type 08:02:28 #topic Fuel-cloud translation and review 08:02:35 let me introduce fuel-cloud 08:02:51 fuel stands for frequently used entries of localization 08:02:55 hello, chandankumar 08:03:30 fuel-cloud is a module which is basically targeted of cloud platform 08:03:39 It is a collection of commonly used enteries of cloud terms which are used by many cloud service providers 08:03:40 like: openstack, cloudstack and eucalyptus 08:04:02 for example: storage, volume, network, instance and a lot common words are used by various cloud service providers. 08:04:21 fuel-cloud is a module which had collected all the terms at one place. 08:04:21 So, many translators can translate it in respective langauge, which may having different meaning in a particular language translated by different translators. 08:04:34 After translation, we sit with cloud users and developers to review these modules in a particular languages and than release for a particular language. 08:04:50 if you have any questions feel free to stop me 08:04:59 how translators can use it 08:05:06 who will translate these entries? 08:05:13 These words are common and used at many places. we use this module in translation memory, when one translator translate a cloud file, common translated words of these modules from translation memory will be visible with their meaning with their language. so people can easily translate their module. 08:05:41 Daisy, software translator will translate it 08:05:47 where is stored this translation memory ? 08:06:20 Daisy, it is good to have they have used cloud before 08:06:34 because they know the technology very well 08:06:53 Fdot, right now it is hosted on zanata and translate wiki 08:07:11 so when we move to Zanata, we could use these translation memory? 08:07:13 chandankumar, ok :) 08:07:23 but we just need to integrate in the zanata tm used by openstack 08:07:26 Daisy, yes 08:07:40 It is different from terminology 08:07:40 Oh, no. We have our own Zanata instance, which means, the memory is not shared, I think. 08:08:25 Daisy, we will pull and merge there or create a project named fuel-cloud which will use it on openstack zanata instance 08:08:30 ok. thanks. 08:08:42 terminology is a collection of unique terms used by cloud service provider to define their respective components and their uses. 08:08:42 fuel module - it is a collection of common entires of cloud collected from different cloud service provides. 08:08:51 Here is the benefits : 08:09:02 if many translators translates the same file in same language the translation will be different. 08:09:03 it creates inconsistency on the cloud platform. 08:09:03 there fuel-cloud helps to remove incosistency by keeping the meaning of common enteies same across the lanuage. 08:09:03 it helps in reviewing the translation. 08:09:29 here is the pot file : https://git.fedorahosted.org/cgit/fuel.git/tree/language/en/terminology/cloud/fuel-cloud-en.pot 08:09:45 it is translated on zanata : https://translate.zanata.org/zanata/project/view/fuel-project 08:10:02 we have started receiving translations from translate wiki 08:10:08 https://translatewiki.net/w/i.php?title=Special:Translate&action=proofread&group=out-fuel-cloud&language=qqq&filter=translated|!reviewer%3A4668|!last-translator%3A4668 08:10:27 and we have got submission from other languages also http://fuelproject.org/stats/index 08:10:37 chandankumar: the module is useful. How to keep the consistency ? I mean, there might be different version of module translations in different software. 08:10:39 now i am open for questions 08:10:58 new version will contains some new strings 08:11:13 and maybe new translations too. 08:11:36 chandankumar: https://fedorahosted.org/fuel/wiki/contribution contains dead links (for example to the evaluated terminology repo) 08:12:16 will Fuel keep on release new versions ? and somebody will be the focal in a certain project to keep the consistency? 08:12:16 Daisy, many translators will start translating in one language. 08:12:45 so we have revisions in git 08:13:21 and from that revisions we can sit and evaluate the translations of entries then release a reviewed version for that language 08:13:24 chandankumar: what do you want us to do? 08:13:56 Daisy, right now we want it to transalte in the respective languages which be as a openstack support 08:14:15 you mean, you need translators? 08:14:47 Daisy, suppose i translate in hindi and we can translate it in hindi and made it avaiable for review 08:15:04 that is the first thing we need 08:15:31 using translatewiki to translate? 08:15:54 use translate wiki or zanata or you can locally and send us the file 08:15:57 I see Chinese translation is done. 08:16:07 Daisy, you can review it then 08:16:19 chandankumar: you could send these information to our I18n mailing list, and call for people's help. 08:16:26 Daisy, sure 08:16:32 I would like to help to review Chinese translations. 08:16:32 Daisy, i will send it today 08:16:39 Thanks, chandankumar . 08:16:43 DeeJay1, i will fix it soon 08:17:08 any more questions? 08:17:16 if not we can move to next topic 08:17:42 Daisy, ^^ 08:17:43 Thanks, chandankumar 08:17:50 Let's move to next topic. 08:17:51 Daisy, you are welcome :) 08:17:54 #topic Zanata related discussion 08:18:23 Fdot, to your question to I18n mailing list about Zanata 08:19:00 I don't get specific target data from infrastructure team, to set up Zanata in OpenStack. 08:19:05 Daisy, i can't wait to use Zanata ;) 08:19:25 Why you hate Transifex so much? :) 08:19:49 Our infra team may be caught by other kilo deadlines. 08:19:58 Daisy, no transifex is nice :) I just happy to use a new tool ! 08:20:06 So I don't know when the Zanata env would get ready. 08:20:31 Daisy, do they know if it will be ready for the kilo release ? 08:20:32 Daisy, we need to ping carlos regarding updates on this 08:20:55 I guess, probable not. 08:21:17 and also ask if they have blockers if possible we can help in getting it up 08:21:20 chandankumar: I don't see Carlos online. 08:21:30 Daisy, yes 08:21:43 Daisy, ok :) thanks a lot for the update 08:22:29 I'm very eager to see Zanata online too because stackalytics new feature: translators contribution would have deep dependencies with Zanata API. 08:22:36 anish__ is helping us on that. 08:22:55 Daisy, that's why i can't wait ;) 08:23:11 me too, Fdot. But we have to. 08:23:24 Daisy, one more thing about deploying projects into zanata https://bugzilla.redhat.com/show_bug.cgi?id=1186606 08:24:06 we need to determine protocol when we deploy our projects for translations 08:24:12 anish__: do you know when Zanata team would fire the new release with your required features? 08:24:31 Daisy, yet to decide 08:24:46 what protocol? 08:25:02 for deploying projects with their names 08:25:05 protocol with whom? 08:25:31 with zanata, in zanata you can have project and then submodules 08:25:46 e.g openstack is project and nova is submodule 08:26:14 let me think. 08:26:16 then your project name would be openstack-nova 08:26:19 kind of 08:26:57 anish__: I don't know if it could solve this issue. If we set up our own Zanata instance, we might have Nova as project, not submodules. 08:27:31 we may have a zanata.openstack.org, something like that. 08:27:44 but we need to name it as openstack-nova 08:27:50 why? 08:28:05 In http://stackalytics.com/ we have Project type and Module type 08:28:18 each project has module associated with it 08:28:45 and then? 08:28:51 what if two projects have same module name 08:29:12 could we translate Zanata response to stackalytics acceptable format? 08:29:56 yes we can translate that format 08:30:12 For example, we translate /stat/project/nova/version/1/contributor/john/2015-1-1 to /stat/project/openstack/nova/version/1/contributor/john/2015-1-1 ? 08:30:38 yes we can do that 08:30:46 can this issue be resolved ? 08:31:25 yes we can solve this issue in way that we already know which modules are associated with which projects 08:31:32 That's right. 08:31:43 In a small scope, the translation could work. 08:32:12 yeah 08:32:48 I don't think there would be same module names in openstack, and stackforge. But I'm not sure about cloudfoundary. 08:33:11 but anyway, let's use "format translate" for now. 08:33:21 Daisy, okay 08:33:26 thanks, anish__ 08:33:33 Daisy, thank you 08:33:44 next topic then. 08:34:02 #topic Introduction of translation test project 08:35:00 translation test project is to test openstack in different langauges, to verify openstack functions could work well and our translations could display as expected. 08:35:32 cool 08:35:50 +1 for that, what do we need? 08:36:09 +1 for that too :) 08:36:10 for example, I set up openstack in a Chinese enabled machine. I expect Openstack is running well there, my Chinese translations are displayed, and my Chinese input would not break functions. 08:36:30 It's a new project now. 08:36:37 I need contributors. :) 08:36:45 https://etherpad.openstack.org/p/i18n-test 08:36:47 See here. 08:37:00 I would like to join in :) 08:37:06 There is a stackforge project ready, named as i18n-test. 08:37:19 I have some test scenarios in mind. 08:38:10 As to the scenario 3 and 4, there are some implementations by developers. 08:38:35 Daisy: as you may know, "pseudo translation check" tool was recenlty added to Horizon. 08:38:36 http://docs.openstack.org/developer/horizon/contributing.html#translatability 08:38:47 scenario 3 is related with Horizon. There is a program in this patch, to generate a fack translation file. 08:38:57 Yes, amotoki . I'm talking about it now. 08:39:36 scenario 4 is related with lazy translation, and oslo.i18n developer is working on it. 08:39:49 So I think, as to us, we could focus on scenario 1 and 2. 08:40:32 We test the command line in different languages. We test APIs with different language inputs. For example, I create an image with a Chinese name. 08:41:32 We could have write automation test scripts to test these scenarios. 08:41:46 We could write automation test scripts to test these scenarios. 08:42:38 That's my thoughts. And I welcome the inputs from you. 08:47:59 https://en.wikipedia.org/wiki/Pseudolocalization 08:49:36 it's a useful link to read, epico . 08:49:55 Daisy :) 08:50:15 another form of mock translations. 08:51:01 petersen told me that link. :) 08:51:17 anish__: would you still like to join this test project ? 08:51:40 Daisy, yeah i would like to 08:51:44 epico, aha :) 08:51:52 Nice. So I have you. 08:52:18 I hope to set up another IRC meeting to discuss this new project, till I get enough people. 08:52:35 great! 08:53:50 OK. I've finished my topics. 08:53:56 #topic open discussion 08:55:56 no discussions any more ? 08:56:39 OK. I will close this meeting. 08:56:56 Thank you very much for attending. It's a very good meeting. 08:57:08 #endmeeting