14:00:04 #startmeeting training-manuals 14:00:05 Meeting started Tue Oct 8 14:00:04 2013 UTC and is due to finish in 60 minutes. The chair is sarob. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:08 The meeting name has been set to 'training_manuals' 14:00:33 i have been a bit disconnected this last couple of weeks 14:00:41 i have no agenda 14:01:14 i almost have the pandoc python wrap script done though 14:01:21 Excellent, I was going to ask 14:02:03 I just did a pull, I see tools/validate.py 14:02:09 it clones repos, pulls updates, converts, and then some extra cleanup 14:02:15 colin here 14:02:25 validate.py is the gate script 14:02:35 sorry about being late. still getting started 14:02:43 no prob 14:02:48 Hi Colin 14:02:53 i forgot to post an agenda 14:02:56 :( 14:02:59 Good morning Keith 14:03:31 proposed topics 14:03:31 So is the training-labs/Scripts stuff for VirtualBox deployment?> 14:03:35 Progress 14:03:35 Blocking Items 14:03:35 Focus work for next week 14:03:37 xml include location 14:03:39 including non xml content 14:03:39 i was just babbling about the rst convert script 14:03:52 right 14:03:59 #topic progress 14:04:17 let me pull the burndown board real quick 14:04:20 speak to me oh oracle of the kanban 14:04:55 Total Cards: 137 14:04:55 Remaining Cards: 74 14:04:55 Done Cards: 63 14:04:57 Percent of cards done: 45.99% 14:04:59 Hours at start: 80 14:05:01 Hours est total: 137 14:05:03 Hours remaining: 74 14:05:05 Hours done: 63 14:05:07 Percent of hours done: 45.99% 14:05:09 ---- ---- 14:05:11 Days Elapsed 37 14:05:13 Daily Burndown 1.7 14:05:15 Est. Days Left 43 14:05:17 Est. Completion Date 11/20/13 14:05:21 so, compared to last week 14:05:23 last week we had 60 cards done 14:05:29 this week we have 63 cards done 14:05:37 poop 14:05:40 though I don't think that pranav's scripts were tracked in a card 14:05:51 big thing is, we added two cars 14:05:52 cards 14:06:00 https://BurndownForTrello.com/share/9c3rfd2fu9 - chart 14:06:15 so, our estimated completion date pushed 14:06:16 ohhh 14:06:24 pretty 14:06:35 im less bummed now 14:06:44 hi 14:06:50 basically pushed out a week or two 14:06:51 hey pranav 14:06:56 hello pranav 14:07:01 hey guys 14:07:10 we want the blue line going down, and the red line going up 14:07:26 ideally matching the slope of the yellow line 14:07:54 our daily burndown rate is still ok at 1.7 14:08:07 we need to double check our story at this point 14:08:15 explain? 14:08:30 what are we teaching associate or rather 14:08:47 what will we be testing the assoc knowledge 14:09:03 some of these cards could get pushed to operator 14:09:12 could or should? 14:09:14 or dev 14:09:20 well im not sure 14:09:30 I still think that mapping to the basic installation guide is just that 14:09:31 basic 14:09:34 i havent gone through the 'story' 14:09:40 and if I was going to look at the over all progress 14:09:48 the biggest limiter we have right now is concepts 14:09:57 we are pretty much completely through the task items 14:10:00 Which is all RST right ? 14:10:04 only a few of the horizon admin tasks remain 14:10:05 correct 14:10:10 the RST to XML translation 14:10:18 we should probably switch topic 14:10:19 to that 14:10:28 I'd say that is the most critical item for this weeks work 14:10:34 #topic rst xml convertion 14:10:42 nice spelling 14:10:52 close enough 14:10:55 beat me in spellings :O 14:11:08 so, if we can't get the conversion working right now 14:11:20 my vote, go ahead with manual inclusion of certain dev docs and diagrams 14:11:35 with an xml note in the section pointing to the root content 14:11:45 I agree 14:11:47 im very close to publishing the convertion script 14:12:03 although RST integration would have deeper impact on many other Maven based projects 14:12:20 sarob: is the code public ? 14:12:27 my preference is to have a converter 14:12:35 i havent pushed it yet 14:12:36 how close are you sean? I wasn not able to solve the problem 14:12:45 does it test locally? 14:12:47 i will do it this morning 14:13:05 k 14:13:07 If you push it, let me know and I'll have a crack at it on my end tonight 14:13:13 same here 14:13:24 im using reg expressions to match and mod content 14:13:53 s/h1/section/g ? 14:13:56 etc 14:13:56 as long as the tags dont change we should be good 14:14:08 is it grabbing the images too? 14:14:19 s/article/section/g 14:14:48 i havent gotten to images yet, but yes it shouldnt be a prob 14:14:51 Couldn't we leave the images alone with absolute reference? Or are we worried about RST content changing ? 14:15:22 the asolute reference points to an external repo. probably best to pull them in in the gross import 14:15:55 e.g. import Nova dev docs, Neutron Dev docs, Cinder Dev docs, etc all into a local directory in training guides 14:16:16 make it easy for the other contributors 14:16:39 So pull in all the RST content locally into training-guides, convert to XML and relative reference to the images? 14:16:41 the script clones and pulls updates 14:17:11 so you want the cloned repos within our repo? 14:17:18 for image ref 14:17:21 ? 14:17:28 I think that would be best for now 14:17:29 are you talking about repo inside repo? 14:17:39 not the full repos, but the dev docs directory 14:18:06 i could add in coping the image directories and update the image tags 14:18:11 instead 14:18:24 ahh ... I guess its better to get the images locally 14:18:41 also, one other thing 14:18:54 right now i have the repos all outside in the local repo root and only the xml in our repo 14:19:01 So clone the RST DevDocs into a temp repo, convert to XML into the training-guides and copy the images ? 14:19:09 so, sean 14:19:16 I agree with that statemtn 14:19:18 thats what i was thinking 14:19:21 only xml in our repo (xml and images) 14:19:24 Makes sense 14:19:26 we could reuse the images rather than make another copy 14:19:59 the script will pull down updates, convert the rst to xml, copy the images 14:20:11 kool 14:20:22 so, we can add that as a manual step in the repo 14:20:28 ill have to figure out the image tag pattern matching, should be okay 14:20:29 and then add it as a build step later 14:20:30 why do people like xml over rst ? :| 14:20:34 so, the tags 14:20:47 rst is not as powerful as XML 14:20:50 remember anne talked about about tagging images and tables with section id's 14:20:56 ok 14:21:19 hmm, could do it 14:21:32 make the code a bit more complicated 14:21:41 analogous to difference between JavaScript and Java 14:21:41 well, push the first push 14:21:54 prob need another card for that feature 14:21:59 but a good idea 14:22:11 sarob we can do that feature in the next iteration 14:22:15 just thinking forward to generating the presenter led content 14:22:18 yeah 14:22:21 so, if we have that conversion done 14:22:24 tool done 14:22:25 it will be simple hack to get the section ids into place 14:22:28 Sarob: you just using regex or the docutils library ? 14:22:29 then that removes a huge block 14:22:39 python regex 14:22:45 Did you look at docutils ? 14:22:50 nope 14:22:52 ok 14:23:30 docutils has some interesting stuff, but not a rst2docbooks 14:23:54 there is a rst2xml.py script though 14:23:57 But you should be able to parse out the RST tags and replace with XML if you find your RegEx fails, regardless was just curious 14:24:38 alagalah it needs some rigorous testing then 14:24:49 the rst2xml.py script is where? 14:25:12 http://docutils.sourceforge.net/tools/rst2xml.py 14:25:24 sudo port install docutils 14:25:31 cool, prob has the pattern matching i need to add 14:25:34 thx 14:26:40 #topic blockers 14:26:54 Card#114 ... still relevant? 14:26:59 (blockers) 14:27:26 that can be moved to done 14:27:41 Ok who did it so I can re-assign? 14:28:21 i could update the script as well 14:28:56 anything else? 14:29:19 let me check my notes 14:29:42 i guess the rst to xml conversion script is a blocker 14:29:51 I'd say that is the only blocking item 14:30:20 next topic? 14:30:33 #topic next week focus 14:31:08 id like to start on the quiz and test formatting 14:31:10 so, think we should try to get all the task oriented cards completed so we can chek for flow 14:31:26 sean, sanity check 14:31:31 that sounds good too 14:31:34 If the script works tonight I'll grab some more cards that require RST 14:31:40 cool 14:31:47 shouldn't the quiz come from the concepts and tasks? 14:32:08 yup, but im talkin format 14:32:11 not content 14:32:29 maybe we can get Rev to throw some idea's together 14:32:36 i know he does that for a living right? 14:32:59 front end surveymonkey.com ? 14:33:24 remember, online, printed pdf, instructor led 14:33:33 probably best to just go old school 14:33:40 list of questions, answer key seperate 14:33:50 out of that people can derive the testing engines 14:34:11 sounds like a good idea to start 14:34:11 yep 14:34:23 and I would guess that since the foundation is managing the cert program, that someone puts a quiz engine tied to openID on openstack.org 14:34:23 just expand the tables there now 14:34:26 we do not need to host a testing engine or system 14:34:28 just the content 14:34:43 ah, that sounds good 14:34:59 okay solution found 14:35:10 old school :) 14:35:23 old school :) 14:35:26 so whats xml include location topic? 14:35:44 oh, I pulled from last weeks 14:35:48 convertion script output dir? 14:35:49 probably can ignore that 14:36:06 just wanted to get the meeting going in an orderly fashion ;) 14:36:13 roger roger 14:36:28 so anything else troops? 14:36:34 yeah 14:37:13 I popped the google hangout into imovie and created a how to contribute to openstack-training videio http://www.youtube.com/watch?feature=player_embedded&v=Qz5NrbFfRi8 14:37:24 nice 14:37:45 sweet 14:37:49 how does youtube let you host 2 hour long videos? 14:38:00 you have to have a verified account 14:38:08 ok 14:38:13 and then go into settings and request extended access 14:38:29 the hangout+live ended up there automatically 14:38:47 alrite thanks 14:39:03 I then downloaded the hangout live locally, edited it to focus on content and then pushed it up after work yesterday 14:39:34 master of the video art 14:39:35 I've written a gdoc with step by step too for my own use. Not as good as the video, but if someone just wanted a quick prompt cheat sheet 14:39:45 awesome 14:39:56 let's all get that information out into the wild 14:40:03 sounds like a great add to the user group howto 14:40:06 Yeah I'll tighten it up and perhaps put it on the wiki 14:40:10 the biggest challenge we have is increasing the number of video's 14:40:13 err not video's 14:40:17 contributors 14:40:24 lol 14:40:29 What happened to other Meetups contributing ? 14:40:42 #link https://wiki.openstack.org/wiki/OpenStackUserGroups/HowTo 14:40:47 (apart from all the awesomeness that is Aptira) 14:40:53 welcome to OpenSource and User Groups 14:40:54 baby steps 14:41:09 basically have to hit critical mass, then everybody says they want to participate 14:41:10 yeah 14:41:12 No worries, just asking 14:41:20 as you can see, this is actual work 14:41:30 it is hard actual work 14:41:32 Sarob: want me to amend the wiki ? 14:41:40 (from that link) ? 14:41:42 amend away 14:41:47 yup 14:41:47 oh, I have one more topic 14:41:52 its very hard to get people 14:41:59 Is there a howto amend the howto :-P 14:42:12 I'll unicast you, Sean 14:42:12 click the edit button on the wiki 14:42:14 yea also need to change the IRC meeting timing on Wiki .. ill do it 14:42:16 its moinmoin wiki 14:42:25 thx 14:42:34 so, another proposed topic - whitespace checks 14:42:49 just log into the wiki and select edit from the top of page 14:43:04 ack got it now 14:43:08 anyone can edit any page on wiki.openstack.org 14:43:19 #topic whitespace checks 14:43:44 so, you may have noticed a non-voting stage in jenkins now 14:43:47 called niceness 14:43:59 it checks for whitespace and empty lines 14:44:10 i never claimed to be nice 14:44:15 you will get a -1 one, that won't stop a build 14:44:35 it caught some white space in the user-includes template as well as my section files 14:44:41 that I went and fixed 14:44:48 cool, thx 14:44:54 I ended up pushing a few patches for mycommit 14:45:03 I didn't however go back through the other cards and clean them up 14:45:15 please confirm IRC meeting on Tues at 14:00 UTC 14:45:29 Im bad with time ... so need to verify 14:45:39 yeah 1400 utc 14:45:43 tuesday 14:45:44 k thansk 14:45:54 I propose that as reviewers we treat the niceneness check as a strict check, and push back (unless it is timely) and request a 2nd patch to fix whitspace issues 14:45:58 Why the polgrom on whitespace? 14:46:17 Does having it break something? 14:46:24 coding standards in the project 14:46:35 Hmmmm interesting. Fair enough then. 14:47:03 and whenever possibly I would like us to confirm to the larger coding standards and methodologies of OpenStack as a whole 14:47:13 it was a simple change on my end to fix it. took 5 minutes 14:47:22 I had a couple tabs and a blank line 14:47:30 Well yeah, of course. Seems like an odd standard since whitespace increases code readability but greater minds than I have determined it's evil so we should comply 14:48:07 your compliance is noted 14:48:31 anything else guys? 14:48:33 I live to serve 14:48:35 spaces and tabs at the end of lines don't make anything easier to read 14:48:36 ;) 14:48:41 either way, wanted to discuss is 14:48:42 it 14:48:43 Ah 14:48:54 before pushing back on reviews 14:48:59 well, other then my own 14:49:00 Ack ... 14:49:00 what do mean? 14:49:10 Do we need to redo existing cards? 14:49:12 white spaces are bad for compiles have to read them 14:49:18 it reduces load on the infra 14:49:43 good point pranav 14:49:52 validate.py wont check already merged xml 14:50:16 python :) 14:50:28 my vote is not to go back and clean stuff up whitespace yet. Just to be a bit more rigorous moving forward 14:50:30 Not. Compiled. :) 14:50:33 hehehehe 14:50:38 Got it 14:50:47 hey guys 14:50:56 lets keep the white spaces as low hanging friuts 14:51:03 *fruits 14:51:10 You mean for new contributors? Great idea 14:51:13 sounds about right 14:51:16 yes 14:51:17 good idea 14:51:20 saves us some manual task 14:51:22 great idea pranav 14:51:35 have them log a bug for whitespace in files 14:51:38 and then clean it 14:51:42 yep 14:52:19 #info whitespace and orphaned tabs to be logged as bug 14:52:49 Hmmmm, I've never logged/resolved a bug so I may take one to fix to understand that process if thats ok? 14:52:50 #action sarob push convert rst xml scrpit today 14:53:14 alagalah: happy to help 14:53:28 instructions are in the operators guide 14:53:35 ack 14:53:39 thank you 14:53:48 anything else? 14:54:09 i'm good 14:54:28 pranav? 14:54:39 we need to discuss the course syllabus once 14:54:42 during the summit 14:54:53 sure 14:55:13 agreed 14:55:13 and I may have some feedback based on actual teaching 14:55:16 in India 14:55:17 i think we should reaccess the syllabus for all four books 14:55:23 sweet 14:55:25 hopefully before the summit \m/ 14:55:37 re-assess 14:55:40 super critical to have teaching feedback 14:55:42 Mr SpellCheck 14:55:58 :-P 14:56:01 :D 14:56:37 #action review books syllabus at summit 14:56:57 agree on getting feedback from a delivered class 14:57:19 yes, very important to know how good is the content delivery 14:57:23 Just for cross-reference... 14:57:33 we should setup a monkey survey and add link to the cource 14:57:36 couse 14:57:39 arrgg 14:57:57 #vBrownBag has a Couch to OpenStack series (#C2OS) I'm going to go through: http://openstack.prov12n.com/about-couch-to-openstack/ 14:58:04 yep, even something similar in kong to know what other experts say abotu it 14:58:09 It may serve as a sanity check 14:58:22 which what? 14:58:52 that's cody's series 14:58:56 yes 14:59:01 he's been hovering around our project 14:59:04 but, to be direct 14:59:16 it kinda competes with the books he has been releasing 14:59:21 so I don't expect much participation 14:59:24 until we hit critical mass 14:59:33 that is a common theme by the way 14:59:59 people keep focusing on putting out single release content 15:00:11 yup 15:00:12 that ends up full of bugs, and dated within 6 months 15:00:21 but, their name is on it 15:00:31 vs treating training and learning as open source 15:00:43 we are on an iterative model, tracked and stuff ... lets just hope they contribute to the official docs eventually 15:00:49 they will 15:00:52 my bet 15:00:53 is 15:01:02 when the course get out and are being delivered in the larger community 15:01:03 they will all come over to the dark side 15:01:06 yup 15:01:11 that will be the critical mass 15:01:13 and 15:01:22 if and when the foundation figures out the cert program 15:01:33 my assumption is that it will be based of this content 15:01:40 or at minimum alighned 15:01:45 then again, more people will jump on 15:02:12 ive got a hard stop 15:02:25 anymore training biz 15:02:31 I'm good 15:02:34 I'm good 15:02:36 im good 15:02:41 wrap up ? 15:02:49 sweet, thx for the great meet guys 15:02:55 see ya in the funny papers 15:02:57 thanks all 15:03:05 #endmeeting