20:00:07 #startmeeting training-manuals 20:00:08 Meeting started Mon Sep 16 20:00:07 2013 UTC and is due to finish in 60 minutes. The chair is sarob. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:11 The meeting name has been set to 'training_manuals' 20:00:18 colin here 20:00:38 hello 20:00:45 anyone else? 20:00:46 hello 20:01:10 hmm, we need to change something 20:01:26 you and i are the only cores showing up to the meetings 20:01:35 you think it is time? 20:01:44 what time is good for tristan 20:01:46 early or late? 20:02:16 its 6am his time 20:02:26 1am pranav's time 20:02:50 so, no good for either 20:03:15 mestery not interested anymore? 20:03:51 I know he is traveling this week 20:04:04 well he has never shown up to a meeting 20:04:07 he has been in a crunch with Nuetron + ovsdb 20:04:08 yeah 20:04:15 maybe he didnt know or remember 20:04:27 possible. I know he is super overcommited right now 20:04:29 could really use a few more eyeballs 20:04:42 agreed 20:04:44 on getting more committers 20:05:03 so, the perfect global time is 7:00 PM 20:05:16 syndney is 12 hours off 20:05:25 err 20:05:29 pune is 12 off 20:05:40 and sydney is +15 20:05:48 right 20:06:13 not sure what pranav's work hours are 20:06:14 est would kinda stink at +3 20:06:20 doh 20:06:21 good call 20:06:44 but we have pst, and sydney, and india committers right now 20:06:55 no europe or est or cst 20:07:29 building a time table right now to check for the witching hour 20:07:49 7pm pst would be 12pm sydney and 7-9am india 20:08:04 would stink for europe 20:08:15 http://www.timeanddate.com/worldclock/meetingtime.html?iso=20130916&p1=224&p2=179&p3=195&p4=240&p5=1038 20:08:17 but loic is too busy right now 20:08:39 slightly suck for cst and est 20:08:43 but doable 20:09:02 i like 7pm pst 20:09:22 I like too, but that kills our east coast guys 20:09:27 well, theoretical 20:09:31 right 20:09:43 and when we get the beta out, there a bunch of users groups on the east coast 20:09:48 lets worry about our aptira committers 20:09:49 including one in my office in alpharetta 20:09:56 oh 20:09:58 well 20:10:02 err 20:10:09 * sarob sigh 20:10:13 The only solution we have found for teaching worldwide is to hold two meetings, typcially 7am and 7pm (Los Angeles) 20:10:24 7am is better imho 20:10:42 7am cover Americas and most of Europe 20:10:47 7pm is for Asia 20:10:57 http://www.timeanddate.com/worldclock/meetingdetails.html?year=2013&month=9&day=17&hour=14&min=0&sec=0&p1=224&p2=179&p3=195&p4=240&p5=1038 20:11:07 hmm, bad for sydney, but... 20:11:09 it is midnight in sidney 20:11:19 and evening in pune 20:11:35 made an assumption that prahpul is in pune 20:11:48 pranav not sure 20:12:00 he told me 12 hours ahead 20:12:44 ill go over the agenda stuff real quick for the records 20:12:51 k 20:13:01 #topic review action items from last meeting 20:13:15 #info ACTION: sarob setup reoccuring hangout for thurs sfbay hackathons (sarob, 20:11:09) 20:13:29 i havent figured that out yet 20:13:34 two ways 20:13:53 first way, is to create a google event 20:13:57 and then update when you launch 20:14:00 = sub optimal 20:14:01 i can create a scheduled onair hangout event, but cant start it 20:14:05 second way 20:14:25 is set up a page with a redirect 20:14:35 even better 20:14:51 set up a page with a redirect and update it when you start the hangout 20:15:05 right, i was going to do that 20:15:20 I was obviously experimenting with the sprint 20:15:56 #action sarob create html 5sec refresh page with redirect to onair hangout URL 20:16:36 where to put it.... 20:16:52 i can create a page on sarob.com 20:17:16 like openstack-sfbay-hackathon.sarob.com 20:17:16 works for me. I can throw up a bunch of sites if you need 20:17:24 including sdnopencloud.net 20:17:27 l;) 20:17:50 sounds like a plan 20:18:04 #url waytooopencloud.net 20:18:12 LOL = win 20:18:31 #info ACTION: colinmcnamara will write up user groups, contacts, and status for reproducing sfbay training focused hackathons (sarob, 20:24:37) 20:19:26 no done yet 20:19:36 I captured some lessons learned from the sprint 20:19:43 e.g. jambox for hangouts 20:20:01 question. do you think I should throw it in the training guide 20:20:02 my quickie list for next takers would be 20:20:08 or should I put it on the wiki? 20:20:21 so, vote for the training-guide? 20:20:29 austin, seattle, LA, DC, new york, boston, sydney, 20:20:44 next takers = user groups? 20:20:51 denver, minn 20:20:55 yeah 20:21:08 when we have the beta ready to delivery, I also have the Alpheretta group ready 20:21:16 NC? 20:21:19 I had one of my SE managers found it 20:21:26 Alpharetta is in GA 20:21:32 oh right 20:21:32 outside of ATL 20:21:39 and then we have philly 20:21:48 my vote, we keep a short list for the alpha 20:21:51 and pittsburg 20:21:51 and then expand for the beta 20:21:54 yes 20:22:00 Pyladies cross over 20:22:03 okay this 20:22:21 austin, LA, sydney for alpha 20:22:37 should we include SFbay? 20:22:42 or is that implicit 20:23:02 ny, dc, boston, seattle, denver, atl, minn, philly, pitts 20:23:04 beta 20:23:24 right sf for alpha 20:23:36 I 2nd that vote 20:23:58 I want to have slides ready as a deliverable for the alpha though 20:24:03 as in, a techable course 20:24:05 #info sf, austin, LA, sydney for alpha training rollout 20:24:27 #info ny, dc, boston, seattle, denver, atl, minn, philly, pitts for beta training rollout 20:24:41 slides right for alpha 20:25:06 #topic docboot camp results 20:25:37 seems like a year ago already 20:25:46 last week? 20:25:52 yeah 20:25:55 it's been a long couple weeks 20:26:17 im so glad i didnt go to linuxcon 20:26:23 me too 20:26:31 id be sleeping right now in the hotel 20:26:37 exactly 20:26:41 so, results 20:26:54 are we combining docsbootcamp and sprint into this discussion? 20:27:11 i was going to separate them but whatever 20:27:33 Problem with camp was I felt no structure. Success was I feel I finally got a feel for the OpenStack community. 20:27:41 hey there 20:28:03 yes, I don't think there was much structure. Good or bad 20:28:08 I know this is the first one for Anne 20:28:17 openflow :) 20:28:19 Suggest for next time have some state objectives that are measurable. 20:28:31 docs bootcamp 20:28:34 or sprint? 20:28:38 ... also good idea for your alpha and beta class 20:28:51 sprint problems were technical 20:29:16 i.e,, Maven not working OOTB 20:30:09 (out of the box) 20:30:23 yeah, it was a mix of n00b and oldtimers 20:30:34 doesnt work for structure 20:30:35 still on docsbootcame? 20:30:38 camp 20:30:41 I agree btw 20:30:47 but still, I got alot out of it 20:30:50 me too 20:31:02 conversations with jim and david kramer were the top ones 20:31:05 agreed 20:31:08 good experience 20:31:18 the api doc discusion was valuable 20:31:21 its still too fluid to expect structure i think 20:31:26 yes 20:31:53 want to formally discuss the sprint = areas to improve / lessons learned? 20:32:27 #topic training sprint day 11sep results 20:32:34 suggest, debug process before meeting so participant have better chance at success 20:32:52 agreed 20:32:54 ... or it could've been my weird (i.e., Windows) box 20:32:59 :-) 20:33:05 well, I think there is a pre-sprint setup 20:33:10 so, attendees that join sprint 20:33:23 tell everyone to bring a Mac or Linux or dont bother. ;-D 20:33:24 will ideally have had one or two patches in 20:33:25 this was the first time everyone was actually committing a page 20:33:30 we can coach before 20:33:38 right 20:33:53 mentor run through would have caught the bugs 20:34:07 right! 20:34:23 I think that is an action - create sprint prep document (I have that one) 20:34:34 #action colin to create sprinter prep guide 20:34:51 #action cmcnamara to create sprinter prep guide 20:35:06 Are there any test scripts to verify that Docs chain is setup correctly (locally)? 20:35:15 I feel that google hangout worked OK 20:35:29 hangout was fine 20:35:31 setting up a speaker phone, or jambox to one laptop would have stopped the echo 20:35:38 right 20:35:47 I have a jambox now, and google hangout can dial into a conference phone 20:36:22 rev: i think the tools are so flaky that a script would be more work that just installing and debuging the tools 20:36:48 also, making sure to pre-coach sprint attendees 20:36:53 to make sure their workstations are set up 20:36:57 is a must 20:37:02 to make use of time 20:37:21 we as mentors need to have more experience debuging build tools 20:37:29 agreed. More time spent on content the better 20:37:37 agree 20:37:37 .. i.e., not the process 20:38:05 that being said, we were able to get new commiters 20:38:20 im hoping the updated commit instructions are a vast improvement 20:38:20 maybe there is something to be said to holding special hackathon day, just for setup 20:38:23 the week before a sprint 20:38:35 good idea 20:38:41 well, that what i was doing at the hackathon 20:38:48 i think at least 20:38:51 true 20:39:02 I was thinking, attendee checkbox 20:39:14 something we can do to help ease the process, and get focus on merging 20:39:21 the hackathons should be all comers 20:39:25 agreed 20:39:35 users of training, new committers without tools installed 20:39:36 I am differentiating between a sprint and a hackaton 20:39:47 oldtimers committing, and mentors 20:40:06 right, okay 20:40:53 sprint should have only oldtimers committing , but we making oldtimer committers right now 20:41:17 I am just setting the expecations for sprint #2. We make sure to mentor new commiters the week before on the preocess 20:41:21 by next sprint rev will be mentoring the n00b 20:41:22 so we can get 1:1 time with them 20:41:26 ;) 20:41:39 agreed... hopefully 20:41:40 and then during the sprint, we are focused on coordinating work 20:41:41 agreed 20:42:04 I am being inclusive, just acknowleging that 1:1 time is necessary for an individual before a sprint 20:42:36 #action pre-sprint hackathon at training user group locations focused on sprint readiness 20:43:35 moving on? 20:43:58 yes 20:43:59 #topic target date for associate guide rough draft publish 20:44:18 we still have alot of work to do 20:44:54 yes, I think that it is a bit pre-mature to put a target date 20:45:02 I do think we need to start managing by a burn down chart 20:45:12 and at least get an estimate of work hours 20:45:55 alpha training user groups will start with rough draft associate guide, right? 20:46:06 current burndown chart = 75 hours of work remaining 20:46:15 with an estimation of 1 hour per card 20:46:16 sounds about right 20:46:36 we should assume that the people we have involved are it for right now 20:46:48 yes, 20:46:57 on a positive note 20:47:00 pranav, colin, sarob, rev, keith, 20:47:04 we are now actually burning down items 20:47:08 five is good 20:47:16 vs increasing faster then we decrease in work 20:47:34 Summary stats 20:47:34 Total Cards: 123 20:47:34 Remaining Cards: 80 20:47:35 Done Cards: 43 20:47:37 Percent of cards done: 34.96% 20:47:39 five is a good number to start with 20:47:39 Hours at start: 73 20:47:41 Hours est total: 93 20:47:43 Hours remaining: 61 20:47:45 Hours done: 32 20:47:47 Percent of hours done: 34.41% 20:47:48 cool 20:47:49 ---- ---- 20:47:51 Days Elapsed 20 20:47:53 Daily Burndown 1.6 20:47:56 Est. Days Left 47 20:47:57 Est. Completion Date 11/02/13 20:48:03 well, there you go. estimated completion 11/02 20:48:16 ill start eating cards 20:48:39 doh, forgot to put hours on some cards 20:48:41 let me rerun 20:48:43 =80/5 20:48:52 hey dguitarbite 20:49:00 excellent timing 20:49:26 updated project stats - 20:49:31 Summary stats 20:49:31 Total Cards: 123 20:49:31 Remaining Cards: 80 20:49:32 Done Cards: 43 20:49:34 Percent of cards done: 34.96% 20:49:36 Hours at start: 61 20:49:38 Hours est total: 123 20:49:40 Hours remaining: 80 20:49:43 Hours done: 43 20:49:44 Percent of hours done: 34.96% 20:49:47 ---- ---- 20:49:48 Days Elapsed 20 20:49:50 Daily Burndown 2.15 20:49:53 Est. Days Left 35 20:49:54 Est. Completion Date 10/21/13 20:49:57 one important note, we have doubled the estimated effort from the start 20:50:56 url for burndown board - https://BurndownForTrello.com/share/9c3rfd2fu9 20:51:06 5 devs, 80 cards, 16 cards apiece 20:51:36 doable 20:51:38 could go fast, could go slow. There is still some debugging time 20:51:43 but absolutely doable 20:52:42 Keith and I will be doing a mobile hackathon on tuesday 20:52:45 err thursday 20:52:50 okay so lets target end of october for alpha release of associate training-guide to the alpha user groups 20:52:50 we are driving to the desert 20:53:06 I'd put some slack 20:53:10 but that is just me 20:53:24 give it a week 20:53:25 summit is nov 20:53:30 that puts the alpha at the summit 20:53:54 i think that month of debugging and feedback before the summit is critical 20:53:56 also with lots of the user group leaders there 20:54:13 summit is nov8 20:54:20 that is just a week after the end of october 20:54:21 otherwise it will just be a bitch session on what is broken 20:54:38 ok, I'm just estimating time here 20:54:40 ahh, of course 20:54:55 not trying to be pesimistic 20:54:56 * sarob brain flop 20:55:23 just trying to be aware that there are travel schedules, and day jobs 20:55:24 really need to be done by the end of september then 20:55:39 two week!? 20:55:40 Sean, I don't think that is realistic 20:55:45 me either 20:56:00 let's focus on tracking foward movement 20:56:11 and on keeping the burn down line sloping down 20:56:25 okay, lets target the end of october 20:56:59 better 20:57:00 week of debugging with austin, sf, and LA user groups 20:57:01 note, to hit that we really need to start engaging a larger audience 20:57:18 sean, you do need to remember that lots of people have day jobs too 20:57:28 for me lots of time it is nights and weekends 20:57:35 I spent most of this weekend working on this 20:57:58 I do need to get a couple releases out at work before Hong Kong or I'm in serious poop 20:57:58 understood, this is my 120% time too 20:58:21 well, considering that this is 120% time. Let's focus on the burn down 20:58:33 guess you could be in a sticky situation 20:58:42 everyone is at one point or another 20:58:44 Hint: Training is a lot like theater. Rehearsing is key. Rehearsing can prepare you to workaround bad content. Or at least know when to tap dance., 20:58:52 agreed 20:58:55 that's why 20:59:01 my suggestion is to keep a sane pace 20:59:06 let's focus on a burn down 20:59:10 when the alpha is ready 20:59:11 got it 20:59:15 let's get the users group input 20:59:27 and then plan the alpha 20:59:44 so target end of oct for alpha release, week of debugging, review at summit 20:59:46 we'll have better luck planning a specific release date when we are at about 20% cards left 21:00:04 gut feel Sean, is that the dates are arbitrary right now 21:00:14 my spidey sense is going off 21:00:22 yeah, i like having something to drive to 21:00:25 again my focus - increasing the burn down rate 21:00:31 feel free to drive to it 21:00:31 got it 21:00:43 if we focus on increasing our average burn down rate 21:00:49 it will bring in the release date more then anything 21:01:01 average daily burn down is 2.15 cards 21:01:07 yup, ill see what i can get done this week 21:01:10 if we double that rate, we bring in the release by a month 21:01:18 we can do that by expanding our commiters 21:01:24 or by making the process easier 21:01:31 or by working harder 21:01:38 i'm up for all 3 21:02:31 roger that, ill work on all three 21:02:58 review the new instructions guys, and update if needed 21:03:17 i have one of my many bosses bugging me, gotta go 21:03:29 vote for adjurned 21:03:34 adjourned that is 21:03:54 #end-meeting 21:04:01 #action no target date for alpha training-guide until closer to completion 21:04:17 you cant do that ;) 21:04:23 I tried 21:04:24 #end-meeting 21:04:33 apparently you can't either ;) 21:04:36 #endmeeting