17:01:16 #startmeeting training-manuals 17:01:16 Meeting started Mon Dec 30 17:01:16 2013 UTC and is due to finish in 60 minutes. The chair is sarob. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:01:19 The meeting name has been set to 'training_manuals' 17:01:48 I have news on publishing 17:02:05 Whatcha you got? 17:03:04 well 17:03:26 either being productive or not productive 17:03:36 but it may be relevant to training-guides 17:03:49 you go first 17:03:56 Sure 17:04:13 #topic publishing 17:04:34 I worked out the plan 17:05:12 We will keep a single repo location, 17:05:37 Rather branch of master 17:06:22 Publish to http via docs.openstack.org/training-guides 17:06:50 I'll add a redirect for training as well 17:07:42 Andreas should have the yaml files updated today 17:07:49 cool 17:07:49 For the FTP moves 17:08:34 the publishing job in the CI system? 17:08:37 I'll update the index, redirect, 17:08:44 Right 17:09:35 #topic quizzes 17:10:08 I'll finish the patch with Ed's quiz questions 17:10:09 Today 17:10:35 Dguitarbyte here? 17:10:36 k 17:11:31 #action sarob publish ehorley quiz questions today 17:12:16 #action dguitarbyte needs to update us on moodle hosting design 17:12:29 Anything else? 17:13:02 #topic active contributors 17:13:14 yeah 17:13:40 so, I have to say. If I never see a bug in docbooks xml again I'll be happy 17:13:50 so, over this weekend 17:13:52 I'd like to post the monthly active contributors to help promote 17:14:00 agreed 17:14:05 so, I've been working on something 17:14:11 that addresses a few issues 17:14:17 Cool 17:14:21 1. without oxygen, really can't write for training-guides 17:14:34 2. docbooks xml is a pain in the but, even with oxygen 17:14:54 3. still have to integrated with the openstack -docs toolchain 17:14:57 Sure 17:15:02 the background is 17:15:10 I signed up to write a chapter for an O'reilly book 17:15:19 and they are basically the king of docbooks 17:15:20 Cool 17:15:30 and then switched over to a new system instead of oxygen 17:15:35 to generate the docbooks xml files 17:15:52 I'm very interested 17:16:11 so, they use a toolchain similar to what the redhat jboss team (and publican if you remember the demo) 17:16:20 that takes a markdown format called asciidoc 17:16:21 Yup 17:16:24 which is super f'n simple 17:16:27 human readable 17:16:32 no xml 17:16:57 they basically have a translator that goes from docbooks to asciidoc and back again 17:17:15 sooo 17:17:30 I've been experimenting in a place where I won't rock the boat 17:17:37 and creating 17:17:39 a workflow 17:17:50 where you write in AsciiDOc 17:18:01 then mvn tranlates to docbooks 17:18:14 and then it fits right into the normal openstack asciidoc toolchain 17:18:44 I'm doing it for OpenDaylight OVSDB. which will be used as the reference SDN controller for nuetron 17:18:59 basically making it so all their docs will be able to be integrated into the openstack docs 17:19:03 Could we develop using asciidoc, patch with xml 17:19:07 yup 17:19:09 exactly 17:19:15 we can lower the barrier to contribution 17:19:26 as well as integrate a web (kind of like wiki) 17:19:28 UI 17:19:28 So the yaml jobs run as is 17:19:55 mvn runs the pom.xml 17:19:58 multple jobs 17:20:12 it basically prepends the openstack mvn jobs 17:20:15 HTML and PDF now 17:20:18 yup 17:20:22 but, you can do more stuff 17:20:24 like slidey 17:20:27 ppt 17:20:28 odf 17:20:29 etc 17:20:49 so, it's WIP right now 17:20:52 So we would need to mod our pom? 17:21:46 Or could we start with just using asciidocs like an editor? 17:22:08 well, first 17:22:19 I need to make sure the bidir workflow works with the clouddocs plugin 17:22:28 other projects us jdocbooks 17:22:52 I'm thinking this is parallel work, probably 4-6 weeks worth 17:22:54 but at the end 17:23:10 we may have a way of getting non-tech writers to contribute 17:23:19 as well as maybe have a solution to the dev-docs challenge 17:23:32 Sounds great 17:23:47 Sync up the work on daylight as well 17:24:10 yup 17:24:11 exactly 17:24:22 hate to derail - did either of you look at the question pool I started? 17:24:23 since the ODL docs are going to have to fit into the Nuetron docs 17:24:34 morning edh: 17:25:03 Edh I like and I'm patching it to master this morning 17:25:14 You ready to make more? 17:26:13 Edh you keep it coming and I will add it to the repo 17:27:12 Edh we will have training-guides published on docs.openstack.org early this week 17:27:36 okay - I will work on sections as I have time - I just trying and pull directly from the text 17:27:49 but I want a better way to tag where I am pulling the question from 17:28:01 so in case the section gets updated - the question can get updated 17:28:09 and the answer(s) updated too 17:28:32 And I will get them added to the training.openstack.org 17:29:03 If you file a bug on the page 17:29:21 The bug marks the file version 17:29:55 So make sure the bug filed is on the quiz page you want to update 17:30:04 Right, I am aware of that, just the concern is that the questions have some sort of meta data to associate them to a section 17:30:27 so if someone updates a section they know that a question is affected - does that make sense? 17:30:46 Ah right 17:31:11 Well, not sure how to automajikally fix that 17:31:56 We can crank out questions all day but they are basically out of context... 17:32:01 Yeah, I'm not sure either 17:32:03 Best right now that we as reviewer make sure before approving patches 17:32:35 That the quiz questions get patched at the same time 17:33:33 And tests 17:34:11 So basically Colin and I will enforce for now 17:34:24 Fair enough - I also am not sure if the question and answer method I am using is appropriate for the level 17:34:33 I am using choose all that apply 17:34:40 and true and false 17:35:16 It's good with me. Until someone comes up with something better. 17:35:46 Help is help 17:35:54 it's really awesome 17:36:24 Spectacular maybe but not awesome 17:36:31 lol 17:36:56 Don't want to give edh a big head 17:37:24 I'm tapped out of new stuff 17:37:42 Any more news or info? 17:37:48 lol - okay - I need to run - conference call - later 17:37:56 i'm good. 17:37:56 Righto 17:38:01 Sweet 17:38:19 Thanks for joining guys 17:38:29 Happy new yearish 17:39:01 #endmeeting