17:02:35 #startmeeting training-guides 17:02:36 Meeting started Mon Nov 30 17:02:35 2015 UTC and is due to finish in 60 minutes. The chair is matjazp. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:02:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:02:39 The meeting name has been set to 'training_guides' 17:02:44 roll call 17:02:51 Hi, matjazp 17:03:05 #link https://etherpad.openstack.org/p/training-guides-meeting-agenda 17:03:30 #info meeting agenda is in Etherpad at https://etherpad.openstack.org/p/training-guides-meeting-agenda 17:04:01 Yes, got it 17:04:13 last weeks action items 17:04:56 ok, translation has started without my (incomplete) patch... 17:05:15 #link https://translate.openstack.org/iteration/view/training-guides/master/languages/ko-KR 17:05:24 #topic review queue 17:05:28 #info Korean translation is now 100% completed as draft. 17:05:48 great work ianychoi ! 17:06:00 Thanks :) 17:06:04 you were damn quick at it, too! 17:06:21 I just merged a job that will publish the results 17:06:29 I have spent last weekdays a lot for this.. :) 17:06:36 https://review.openstack.org/#/c/251339/ 17:06:45 this should enable publishing 17:07:31 Yes. I agree with you. Hope that it works well. 17:07:33 ianychoi: so you can hopefully start using this material in your trainings, right? 17:08:06 ianychoi: if it doesn't, we'll patch it until it does ;) 17:08:11 matjazp, yes. I think I can start to use this material next year 17:08:20 Yep :) 17:08:36 #info ianychoi finished the Korean translation of th eUpstream training 17:09:12 After puslishing, I would like to discuss with other Korean guys to facilitate upstream training. 17:09:34 #info Kato's patches enabled translation on the Upstream training 17:10:06 #info currently there are no outstanding patches 17:10:16 Yes. Thank you so much for matjazp and KATO Tomoyuki. 17:10:45 ianychoi: you did all the work on the first translation 17:11:22 Yes, but it is just on draft now. In translation part, there are two stages. One is to translate, and the second is to review. 17:12:19 I will review Korean translation with publish results, since sometimes I miss-translate with rst syntax errors.. 17:12:43 s/miss-translate/mis-translate 17:13:35 hmm... the publishing patch merged, where is it published? 17:14:42 matjazp, so good question... 17:15:05 as far as I know, it depends on the structure of publish-docs directory. 17:15:32 Maybe KATO will help this. 17:16:25 Currently, publish-docs/upstream-training folder is the main content for docs.openstack.org/upstream-training I think. 17:16:45 However, ko_KR and ja folders are in publish-docs 17:17:13 * matjazp this is it I guess rsync -a ${DIRECTORY}/build/slides/ publish-docs/${language}/${DOCNAME}/ 17:17:44 e.g.) publish-docs/ko_KR/upstream-training/index.html, publish-docs/ja/upstream-training/index.html 17:17:46 so it just prepends a language before files 17:18:35 And publish-docs/upstream-training/index.html => It is the main of docs.openstack.org/upstream-training I think 17:19:06 yes 17:19:38 we need to update the kr index page manually? at http://docs.openstack.org/ko_KR/ 17:20:31 Maybe there would be another job to update it.. 17:20:43 For example, http://docs.openstack.org/liberty/ja/install-guide-ubuntu/ is Japanese install-guide for ubuntu 17:20:52 hmm.. it shoud be at http://docs.openstack.org/ko_KR/upstream-training/index.html? 17:21:36 Yep :) 17:21:53 ok.. I'll look into it 17:22:28 Yep thank you, and I will also look into it, since it is also related to i18n.. 17:22:42 #action matjazp looks if translated document index for each language needs to be updated manually 17:22:57 ianychoi: yes, please do 17:23:30 if it is a manual patching, you'll need to do it because I don't know the language :) 17:23:35 #action ianychoi looks translated document location related to i18n 17:24:09 It would be an automated way, but I think some patches would be needed. 17:24:33 I am not currently sure whether this patch would be in training-guides or in openstack-infra ... 17:25:38 if it is for index page, its in docs repo 17:26:29 eg you can look for a patch that added training guides at https://review.openstack.org/#/c/228530/ 17:27:13 Yep. Thanks for that link! 17:27:33 IMO it might be docs.openstack.org/ko_KR/upstream-training automatically 17:28:26 yes, I would think so... Maybe it is just not available yet, but it will be as soon as it propagates 17:29:04 +1 Let's wait for one day.. to execute the latest tox.ini patchset automatically 17:29:29 ok. 17:29:34 Thanks so much, matjazp ! 17:29:46 #topic any other business 17:30:02 ianychoi: you have anything else? 17:30:40 Just one question: training-labs was in training-guides, but it is not in training-guides anymore. 17:30:47 Am I understanding right? 17:30:49 yes 17:31:00 they have a separate repo now 17:31:17 we just merged a patch that cleaned up this repo 17:31:31 I think some bugs on training-guides launchpad are related to training-labs 17:31:36 we left a README to point to the new repo 17:31:45 For example, https://bugs.launchpad.net/openstack-training-guides/+bug/1435932 17:31:45 Launchpad bug 1435932 in OpenStack Training Guides "Automatic shutdown of vm for windows OSBASH script is not working" [Undecided,New] 17:32:12 For this bug, should we remain it? or should we change it to invalid or other status? 17:32:47 yes, this should be put into their queue 17:32:56 but I'm not sure what are they using 17:33:32 manuals queue or bugs.launchpad.net/lab? 17:33:44 I asked to training-labs guys by docs@lists.openstack.org and they said yes 17:33:46 https://launchpad.net/labs 17:34:01 aha ok 17:34:44 #link http://lists.openstack.org/pipermail/openstack-docs/2015-November/007952.html 17:35:28 ok, i just put it in their new queue 17:35:55 if you find another one, just reassign them to their new bugs queue 17:36:11 Aha... got it. Thanks! 17:36:22 Then, no more questions from me. 17:38:10 ok, i reassigned a few more 17:38:17 mugs queue should be clean now 17:38:25 only "our" bugs in it ;) 17:38:28 More clean wow :) 17:39:37 ok, lets wrap this, ok? 17:39:45 Okay! 17:39:58 thanks for your time! 17:40:08 see you next week 17:40:11 bye! 17:40:11 Thank you :) 17:40:14 bye~ 17:40:32 #endmeeting