17:00:50 #startmeeting training-guides 17:00:51 Meeting started Mon Aug 25 17:00:50 2014 UTC and is due to finish in 60 minutes. The chair is sarob_. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:52 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:55 The meeting name has been set to 'training_guides' 17:01:50 Til call 17:01:56 hello 17:02:02 Hi 17:02:03 hey 17:02:05 Roll call I mean 17:02:07 hi 17:02:07 Hi 17:02:20 Hi y'all 17:02:36 #topic training docs 17:03:00 hello - Shilla here 17:03:11 Afternoon 17:03:36 Take it away dbite 17:03:48 sure 17:04:04 the labs section for Icehouse are ready, needs some testing 17:04:39 the associate and operator book should be ready for Icehouse by the end of this month 17:05:40 by labs section I meant basic-install-guides 17:05:43 my bad 17:06:40 Dbite: great progress. 17:07:00 I will be working with Comcast team to update the Associate and Operator books 17:07:03 not much work remaining 17:07:05 there 17:07:15 Dbite: do you think juno will be a lot easier 17:07:28 yes it should be lot easier 17:07:43 we should meet Juno on time for the official Juno release 17:07:52 Dbite: nice 17:08:37 #info docs on target for icehouse by the end of aug 17:08:46 any questions? if not lets move on 17:08:57 nope 17:09:24 #info docs juno support by release schedule 17:09:39 #topic infra update 17:10:39 scripts are almost ready for wider testing. 17:11:00 there are a couple of issues that dbite and I are working on right now. 17:11:35 the cluster is ready, it deploys openstack and automates everything required to get OpenStack on VirtualBox 17:11:40 If someone wants to start testing already, I wouldn't try to talk them out of it anymore :). 17:11:45 we just have a few bugs that should be fixed soon 17:12:35 I'll run through it wed when I back home 17:13:13 Anything else? 17:13:33 not from me. 17:13:42 #topic testing update 17:13:43 ohh ues we need to update the documentation for the labs section 17:14:07 Who can take that on? 17:14:07 I have finished compute node quiz for associate guide 17:14:23 i would like to do that 17:14:32 Matjazp: good 17:14:44 i can help with that as well 17:14:54 I'm working on network node quizzes 17:15:07 ShillaSaebi: cool, I'll be glad 17:15:12 #action sayali update documentation for labs section 17:15:14 #action sayali, shillasaebi will update the labs documentation 17:15:33 Beat me 17:15:37 hehe 17:15:44 sorry 17:16:11 #undo 17:16:11 Removing item from minutes: 17:16:43 So shillasaebi you are signing up for quizzes? 17:16:53 yes 17:17:00 Coolness 17:17:39 I am interested in helping with the quizzes, but will be out the second half of this week, will be avail. next week 17:17:39 You guys synch up over the docs channel 17:17:57 Meganr: excellent 17:18:02 yes... or mail 17:18:10 ok 17:18:27 Matjazp: will be great to get momentum behind the quizzes 17:19:19 Matjazp: anything else? 17:19:26 nope 17:19:45 #topic upstream training merge 17:20:08 so the blueprint is out there 17:20:23 And we have the first patch in 17:20:34 Reed is here with me 17:20:45 ok, cool, hi reed 17:20:49 In San Antonio 17:21:06 Well not next to me 17:21:06 how should we create slides... one for each guide or one for each section of each guide? 17:21:37 Its going to depend 17:21:38 that is for training guides content 17:22:01 not just for upstream training 17:22:06 I'm going to help reed on the blueprint task breakdown 17:22:18 Ah 17:22:21 Okay 17:22:22 upstream training has its own folder structure 17:22:27 Right 17:22:30 I suggest that we let the upstream training content in there 17:22:40 and then we work on improving it book wise 17:23:06 dbite: yes, we can move/integrate later, if the need arise 17:23:29 Keeping separate right now makes sense 17:23:58 As far as slides breakdown for the rest of the content 17:23:59 so in the mean time, we just put slides for training guides in a coresponding directory structure? slides for assoc guide in its folder, etc. 17:24:19 Hmm, not sure 17:24:36 matjazp, are the slides in XML? 17:25:00 dbite: no, the same as for upstream univ 17:25:18 ok, then may be another folder and move the slides in there 17:25:27 we should use the same tech for slides through the whole project 17:25:30 also move upstream in that folder 17:25:32 One step at a time 17:26:06 We will need to figure out the common slide tech 17:26:10 In the future 17:26:34 Perhaps ASCIIdoc or other 17:26:36 sarob_: we just use the same as for Upstream training... 17:26:53 That would mean converting xml to rst 17:27:12 sarob_: why two different formats? 17:27:39 We wouldn't have different 17:27:49 slides for Upstream training will be in landslide, so why not use that same approach for "our" slideware 17:27:57 In that case we would pick rst 17:28:05 As source 17:28:06 I think rst for slides should be good 17:28:10 should we vote on it? 17:28:14 sarob_: yes, that is what I'm saying 17:28:27 Let's stablize 17:28:41 First before a major change like that 17:28:57 Markdown? 17:29:22 I want like juno released before we vote on any major changes 17:29:32 sarob_: currently, there are no slides, so whatever we choose, its not a major change 17:29:50 True 17:30:01 I think we should follow upstream-training's footsteps 17:30:01 sarob_: I'm talking just for slides, not everything 17:30:12 the rst to html and pdf is possible 17:30:14 If we use xml to slides tool for now 17:30:21 so we meet all the requirements 17:30:29 Matjazp: ah okay 17:30:43 Matjazp: me confused 17:30:45 sarob_: I think XML should be standard for the current books 17:31:13 sarob: training guides will stame tha same, slides will adopt Upstream's approach 17:31:22 For the short term, having separate slide source is okay 17:31:27 stame=stay the same 17:31:50 Staleware concern past 3 months 17:32:53 So short term build slidesware within the same tree as the upstream stuff? 17:33:16 sarob: no, I think a separate folder in each guide is better 17:33:34 Rest like that too? 17:33:45 sarob: for Training guides slides 17:34:18 Who wants to post the first patch as example? 17:34:42 We can vote on the structure through gerrit 17:34:56 sarob: ok, that is also an option 17:35:24 I think it's too nuanced 17:35:35 To be discussed in irc 17:35:59 My opinion for what is with 17:36:04 Worth 17:36:18 ill push the first slide 17:36:22 in that case 17:36:27 Sweet 17:36:34 Thx 17:36:35 and we discuss the structure over the gerrit review process 17:36:36 OK, so first patch for slides should be WIP long enough so we all can tune in 17:36:51 #action dguitarbite push first slide for associate guide and operator guide 17:37:01 Nice 17:37:15 #info discussion and design of presentation slides will be done via. gerrit while reviewing the patch 17:37:28 I will push more upstream patches this week 17:37:42 Converting the odp xml to rst 17:38:01 Moving on? 17:38:04 yes 17:38:17 #topic any other business 17:39:08 Do we know anyone that would be interested in joining us on audio 17:39:17 Visual stuff 17:39:31 Supporting it that is 17:40:43 Hmm, we will keep the slot open for the interested person 17:40:56 If that is it 17:40:56 up for it 17:41:12 Sayali: cool 17:41:46 Propose how you would want the subteam to work 17:42:16 Sayali and how the content would be organized 17:42:28 For this next weeks meeting 17:42:36 Sayali okay? 17:42:46 alright sarob_ 17:43:34 #action sayali propose audio visual subteam content and structure 17:43:38 Any 17:43:45 Thing 17:43:48 Else 17:44:24 nope im good 17:44:28 then I call this meeting concluded 17:44:43 Thanks for your work team 17:45:14 #endmeeting