00:00:26 #startmeeting OpenStack I18n Meeting 00:00:27 Meeting started Thu Jan 16 00:00:26 2014 UTC and is due to finish in 60 minutes. The chair is Daisy. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:00:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 00:00:31 The meeting name has been set to 'openstack_i18n_meeting' 00:00:41 Good morning/evening ! 00:00:53 Hello everyone 00:00:54 Good moning :)) 00:01:00 good morning 00:01:00 good night ;) 00:01:28 Hello everyone. It's the first time meeting in 2014. 00:01:52 I hope you have a good time in new year days. 00:02:24 Today we will look at the progress of installation guide translation and collect issues if we have. 00:02:44 ok 00:02:51 ok :) 00:02:58 #topic Installation guide translation progress and issues 00:03:24 From Transifex, we can see: 00:03:27 Japanese translation is completed finished. very good work. 00:03:52 Korean and German have more than 50% completed. Thank you for your hard work, ujuc. 00:03:58 hu ;) 00:04:03 Russian, Chinese and Portuguese have certain progress. 00:04:17 As our plan, we will start to publish translations since today. :) 00:04:41 It's OK that some teams have not finished. We can publish those who has completed. 00:04:58 We can publish those translations when complete. 00:05:03 we will have better progress for pt_BR soon, I was short in time 00:05:18 Thank you, gabrielcw . 00:05:30 Our Chinese team will do too. :) 00:05:45 Since string forzen will start from the beginning of March. I will suggest we complete document translation by the end of February. Or else, the workload in March will become too big. 00:06:15 I mean, after string frozen, we will move to messages translations. 00:06:30 so we'd better to conclude our document translation work in Feb. 00:06:45 ok :) 00:06:55 Again, please record the names of conributors. Community should recognize them. I will collect contributors' names from you after we finish this work. Please pay attention too. Thank you. 00:07:26 ujuc: do you have people to help you in installation guide translation? 00:07:39 yap 00:07:43 good. 00:07:44 :) 00:08:42 Community will send free registration codes to those contributors. I know maybe some people won't have chance to fly to US to attend. But it's a kind of recognization. 00:09:22 #topic translation publish script 00:09:37 While the team is translating, we need somebody to take a look at the publish job in Jenkins. 00:10:03 We have one to manage operation guide in Japanese's publishing: 00:10:05 https://jenkins.openstack.org/view/Openstack-manuals/job/openstack-operations-guide-ja/ 00:10:11 But it doesn't work well now. 00:10:25 We need to have the similar jobs for installation guide and for several languages. 00:11:09 I'm working it now. I know Tom Fifield is also taking an eye on it too. 00:11:31 oh. Sorry, forget to mention one important thing in the first topic. 00:11:56 There are some contents in "installation guide" in the "common" folder. 00:12:20 https://www.transifex.com/projects/p/openstack-manuals-i18n/resource/common/ 00:12:50 Some of the contents of "installation guide" are in the resource of "common" in Transifex. 00:12:54 some XML files. 00:13:17 Ummm~~ T.T 00:13:55 I will get the name list of XML files and send to ML. So after we translate the strings in "installation guide", we also need to take care of those XMLs in "common". 00:14:10 right 00:14:20 #action Daisy to get the name list of XML files in common and send to ML. 00:14:35 yep 00:14:36 :) 00:15:08 I have finished what I want to talk. :) very quick. 00:15:15 #topic free discussion 00:15:33 :0 hhh 00:15:50 do you have anything to discussion? 00:16:18 nothing special here, but about the jenkins, i'm no specialist, but I can help maybe 00:16:34 nothing :) :) 00:16:42 thank you, gabrielcw . 00:17:05 i am looking at the code, if I figure it out I'll let you know so I can be useful 00:17:22 Now the question blocking me is that I don't know how to invoke a script in repository "doc-tools" from our publish Jenkins job. 00:17:58 We have some scripts called translation tools. 00:18:17 You know doc team have several repositories for their contents. 00:18:51 At the beginning, we put translation tools to every repository. 00:18:52 translation-jobs.yaml? 00:19:25 Now the translation tools have been moved to a new repository: doc-tools. 00:19:29 No, gabrielcw 00:19:33 Let me find a link. 00:19:46 oh :) 00:19:48 oh, ok 00:21:05 https://git.openstack.org/cgit/openstack/openstack-doc-tools/tree/bin 00:21:39 ok 00:21:45 You see: generatedocbook and generatepot there? 00:21:49 yes 00:23:17 https://git.openstack.org/cgit/openstack/operations-guide/tree/tools 00:23:40 https://git.openstack.org/cgit/openstack/openstack-manuals/tree/tools 00:24:03 you can also find generatedocbook and generatepot under the above two links to. 00:24:31 I think, now there should only be one place to put "generatedocbook and generatepot" 00:24:44 The others should be removed. 00:24:47 I see 00:25:20 Then I don't know if the others are removed, how to invoke them under operations-guide? 00:25:51 Maybe I'm wrong. Maybe the others should not be removed. :) 00:26:13 but who in fact calls them? 00:26:32 There is a job in Jenkins. Let me find the link. 00:26:51 that one? 00:26:51 https://jenkins.openstack.org/view/Openstack-manuals/job/openstack-operations-guide-ja/ 00:28:09 https://git.openstack.org/cgit/openstack-infra/config/tree/modules/openstack_project/files/jenkins_job_builder/config/manuals.yaml 00:28:22 See the end of this file: manuals.yaml 00:28:39 - job: 00:28:41 name: openstack-operations-guide-ja 00:29:15 yes 00:29:45 We should have similar ones: installation-guide-pt-br, installation-guide-zh-cn 00:30:13 understood 00:30:20 but at first, we need to have openstack-operations-guide-ja running well. :) 00:30:36 oh, what's wrong? 00:30:57 I don't know yet, actually. 00:31:48 https://bugs.launchpad.net/bugs/1216153 00:31:51 Launchpad bug 1216153 in openstack-i18n "ops guide japanese build fails" [High,Confirmed] 00:32:13 There is a bug to track it. 00:33:09 oh 00:33:23 that's seems a large change 00:33:56 moving repos around 00:34:33 I'm going to have a chat with Tom Fifield about it. He can help me to catch the current status. 00:34:59 nice 00:35:39 I don't think it's a big problem. But it's a problem that many projects and many people evolved. That's reason why it is complex. 00:35:40 meanwhile I will tinker with the manuals.yaml 00:35:54 nice. 00:35:58 yes, that`s what I think too 00:36:19 thank you, gabrielcw. 00:36:35 If we don't have topics, I'm going to close the meeting. 00:36:54 yes :) 00:37:58 ok! 00:38:04 I leave 20 minutes to us. You can go back to your work. I can drive to office then. 00:38:10 :) 00:38:15 So see you next meeting. 00:38:19 Thank you. 00:38:26 Let's keep contact through email. 00:38:35 thanks 00:38:40 #endmeeting