08:00:38 #startmeeting OpenStack I18n Meeting 08:00:39 Meeting started Thu Oct 16 08:00:38 2014 UTC and is due to finish in 60 minutes. The chair is Daisy. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:40 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:42 The meeting name has been set to 'openstack_i18n_meeting' 08:00:44 Ah~ ;) 08:00:56 Nice to see you, ujuc 08:01:02 Hi :) 08:01:06 hi, Daisy 08:01:14 Good afternoon, epico 08:01:54 Fdot: will you join us? 08:02:16 hello Daisy 08:02:22 Hi, welcome 08:02:22 Yes I am here :) 08:02:27 Let's start. 08:02:45 #topic Preparation for Paris summit 08:03:12 We will have two or three sessions related with our team. 08:03:23 The first one is translator meetup. 08:03:33 https://etherpad.openstack.org/p/paris_translators_meetup 08:03:43 Many thanks to team's input. 08:03:50 We have a good shape now. 08:03:58 There is only 40 minutes. 08:04:13 I will move "translation tool discussion" out of this session. 08:04:36 I think, we are possible to cover these topics in 40 minutes. 08:05:49 While discussion in Paris, we will follow the current sequence in the Etherpad. 08:06:10 If we cannot finish on time, we could have special "project pod" to continue the discussion. 08:06:29 The "translation tool discussion" will be a separate session. 08:07:31 Ely from Infrastructure team is helping us to apply for a slot in infrastructure track. I will let you know the time after it is scheduled. 08:07:39 Daisy, hello 08:07:47 Hi, chandankumar 08:07:53 I thought you were in vacation. 08:08:13 Daisy, just back right now :) 08:08:26 I raised a request in QA slot to discuss translation test. I'm not sure if it will be arranged. 08:09:23 By the way, in order to prepare for the translation tool discussion, I will need some testers to help go through the trials of Pootle and Zanata. 08:09:37 https://etherpad.openstack.org/p/translation-tools-comparation 08:10:20 I create a simple survey. I would like a volunteer from each translation team to go through the test websites of Pootle and Zanata, give the feedbacks in the Etherpad page. 08:10:44 chandankumar: could you help to test the trials? 08:10:53 ujuc: could you help? 08:10:53 Daisy, yes sure 08:11:06 Fdot: could you ask somebody help to test the trials? 08:11:26 Daisy: yes I can :) 08:11:32 Thanks. 08:11:34 Daisy: yes :) 08:11:55 I am going to send an e-mail today based on the etherpad content ;) 08:12:06 Thank you, Fdot. 08:12:28 any questions for the summit or comments? 08:13:13 Daisy, is it possible to join the paris translation meetup through irc? 08:13:13 OK. Let's move on. 08:13:26 A good suggestion, chandankumar 08:13:49 i have added one item : fuel-cloud on the etherpad. 08:14:08 Daisy, may be i can discuss there through irc. 08:14:51 I will help you to figure out how to join this session remotely. 08:15:03 It's Tuesday, November 4 • 17:30 - 18:10 08:15:12 Is the time suitable to you? 08:15:18 Daisy, yes 08:15:22 OK, great. 08:15:22 it is in UTC ? 08:15:32 I think, Paris time, locale time. 08:15:39 local time 08:16:38 chandankumar: please check if the time is ok for you. We will move on. 08:16:51 Daisy, ok 08:17:00 chandankumar: it is UTC+2 ;) 08:17:06 :) 08:17:26 #topic How to handle with translation assets 08:17:48 "translation assets" here, mean our translations in old releases. 08:17:54 They are our assets. 08:18:11 Now we have a considerable assets in Horizon translation now. 08:19:13 Generally speaking, translation tool will help us to build these assets into translation memory. 08:19:46 in Transifex, even we delete them, the TM will save them into memory. 08:21:06 amotoki initiated two mail thread to discuss: (1) whether the old translation allow to be updated (2) whether the old translation resources should be kept in Transifiex 08:21:14 http://lists.openstack.org/pipermail/openstack-i18n/2014-October/000799.html 08:21:24 http://lists.openstack.org/pipermail/openstack-i18n/2014-October/000798.html 08:21:45 I'm going to start the discussion from the first one: whether the old translations allow to be updated. 08:22:19 Daisy, we can remove the old translation as translations are saved in TM. 08:22:33 how do you think, ujuc and Fdot? Do you have requirements to update the old versions of Horizon? 08:22:54 no. 08:23:01 chandankumar: do you have requirements to update the old versions of Horizon? 08:23:05 Daisy: no :) 08:23:06 no 08:23:29 The update of old versions seldom happen. 08:24:28 chandankumar: I need to ask Zanata dev team to check how things happen in Zanata after we remove some resources. 08:25:05 OK. Then we could make a rule there: 08:25:33 yes 08:25:43 accept translations only for the latest stable release. 08:26:52 import translations 3 days before the update of stable version is released. 08:27:25 I don't know if the second point is OK. I need to check with amotoki. 08:27:50 I think it's ok, but it's a manual process 08:28:04 so it's good to let the developers know that there are new translations and they should import them 08:28:07 But anyway, there is chances to update translations before the stable update release. 08:28:14 Absolutely :) 08:28:20 OK, jpich 08:28:28 Thanks for reminder. And somebody need to take care of it. 08:29:26 I don't know if there is automatic alert in translation tools if the old translations are updated. 08:30:08 Maybe the developers can try by doing an import locally, they should see if there are changes... 08:30:26 If there's a new language to be added though we'll need to be notified separately 08:30:32 I could take care of this action. If horizon is going to release a update version, some developer tells me. I ask in ML about which languages would like to have the update. 08:31:15 Sounds good. The stable release schedule should be added to https://wiki.openstack.org/wiki/StableBranchRelease#Planned_stable.2Ficehouse_releases once they're decided for Juno 08:31:18 probably in a week or two 08:31:33 OK. 08:31:40 Cool! 08:32:21 So we move to the second one question: whether the old translation resources should be kept in Transifiex 08:33:03 my answer is: if the old translations could be built into TM and there is no update requirements ( not the last stable version ), we should delete them. 08:33:28 so I need to check if the deleted resources would be kept in TM. 08:33:31 Daisy: can we keep the 2 versions ? 08:33:45 2 + 1 current 08:33:52 Why 2 ? 08:34:05 If you can update the TM and want to delete the old translations, I think it would make sense to do it at the same time than the schedule for the code releases (for instance, the Havana branches were deleted from the repositories a few weeks ago) 08:34:16 we have 1 current, 1 latest stable release. 08:34:21 do we need to keep more ? 08:34:42 Daisy: 1 + 1 it is good :) 08:34:51 1 + 1 ~~ :) 08:35:04 1 + 1 08:35:29 Just for background: the code usually keeps 2 stable branches, though the one two releases ago tends to be a bit more ignored (or only security fixes) 08:35:36 jpich: I cannot understand you long sentence. 08:35:49 eep, sorry! 08:35:55 ok, that make sense, jpich 08:36:21 I meant, if you want to delete old translations, maybe we can delete them as the same time as the developers delete the code branches (since translations can't be imported after that, either) 08:37:06 codes keep 2 stables. The result of our discussion just now is to keep 1 stable and 1 current. 08:37:28 Got it 08:38:10 so I'm done now, and give the time to you. 08:38:15 #open discussions 08:38:21 #topic open discussions 08:38:49 Who has topics to talk? Please speak out. 08:39:21 no? 08:39:45 not for me :) 08:39:49 no 08:39:52 ok. Then we could close the meeting and you could come back to your work. 08:40:14 #endmeeting