17:00:10 #startmeeting training-guides 17:00:13 Meeting started Mon Dec 8 17:00:10 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:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:16 The meeting name has been set to 'training_guides' 17:00:30 agenda #link https://wiki.openstack.org/wiki/Meetings/training-guides 17:00:55 roll call 17:01:04 hey 17:01:11 hello 17:01:18 Hi 17:02:03 any pref on the order of items on the agenda? 17:02:08 any adds? 17:02:59 maybe we start with status reports? 17:03:11 hello 17:03:13 sure 17:03:27 evening dguitarbite 17:03:37 just asking about the agenda 17:03:39 morning sarob 17:03:54 #topic status reports 17:03:58 on branching 17:04:12 ahh 17:04:13 yes, I need to finish the branching and its part of the release 17:04:29 I got caughtup in some urgent work outside technical domain 17:04:40 and could not do much here, I just need to push a patch 17:04:48 and then ping the infra guys for the release and branching 17:05:19 basically this #link https://wiki.openstack.org/wiki/Branch_Model right? 17:06:01 so old XML text will become what? stable/icehouse? 17:06:15 yes, but it may not be the exact same model 17:06:22 matjazp: yes the old content will be stable/icehouse 17:06:28 then we start working on Juno 17:06:33 which should be the new slides 17:07:17 branch/icehouse this week? 17:08:11 yes 17:08:14 when new branch is made, we need to update wiki page... there's old stuff on it 17:08:24 #action dguitarbite will work with infra team on committing stable/icehouse branch 17:08:58 matjazp: very true, from summit etherpad plans 17:09:33 matjazp: you want me to do that or you want to take it on? 17:09:40 we all update our sections? 17:10:02 matjazp: sounds right 17:10:05 and I'll update common text 17:10:16 matjazp cool thx 17:10:49 #action subproject leads update their wiki sections, matjazp updates common text 17:11:05 #action matajzp post stable/icehouse branch, update common wiki text, team will update their sections 17:11:22 moving on? 17:11:53 yers 17:11:55 *yes 17:12:00 sure 17:12:03 unless anyone has any other point to add 17:12:11 nope not me 17:12:34 #topic trainers group 17:12:53 soo, i finally have this started up 17:13:09 see #link https://wiki.openstack.org/wiki/Meetings/trainers 17:13:39 the first big question is how to drive requirements 17:14:11 the trainers will do their thing from the materials this team creates 17:14:46 the trainees and trainers need to provide us ideas and feedback 17:15:13 we have used bug reports in the past with mixed results 17:15:32 i think we still use bug reports 17:15:40 feedback on slides should be just file bugs on stuff in repo 17:15:43 but need to add new ways 17:16:05 do we need to attend the trainers meeting? 17:16:15 i dont think so 17:16:31 you might lurk if you want to 17:16:45 of course you can attend if you want to 17:16:58 i just dont want to overload you guys 17:17:37 the trainers meet is meant to discuss the sessions, whats working and how to improve 17:17:41 sounds good to me 17:17:48 materials will only be a part of that 17:17:53 the time is kind of awkard for this time zone 17:18:07 6pm? 17:18:20 7 PM 17:18:25 ah 17:18:30 and 8 pm during the summers 17:18:38 i forget you are GMT+2 17:18:55 got GMT stuck in my head 17:19:30 ok 17:20:10 so you guys want me to gather the feedback manually for now 17:20:26 from the trainees and trainers and drop on docs ML? 17:20:31 well teem meetings will be recorded 17:20:38 true 17:20:45 duh 17:20:51 the meeting results could be good 17:21:00 of course you are correct 17:21:03 the action items etc. may be good summary so we do not need to do anything manually 17:22:00 sarob: you have any feedback on labs? from last week? 17:22:05 #action sarob training-guides team will review trainers action items as part of weekly meeting agenda 17:22:40 matjazp: not anything useful yet as we don't have the slides and structure down yet 17:23:21 matjazp adding the labs into the mix would be super difficult as a starting point 17:23:59 matjazp im shooting for jan as we should have slides and some structure ready by then 17:24:21 sarob: labs are ready for Icehouse 17:24:28 and debugged and tested really well 17:24:47 dguitarbite agreed 17:25:10 I used labs on my course... but I used Ubuntu as a host (they will test windows at home) 17:25:19 dguitarbite: we need to get the trainer stuff all org 17:25:54 matjazp: we only have a small window and volunteers so i need to keep this very easy 17:26:04 baby steps 17:26:24 it went ok... two guys had problems on their mac (smth. with locale settings caused keystone to not install), but as soon they used US, eveything went ok 17:26:29 labs are the most ready 17:26:59 but i cant through the trainees into the labs without some foundation 17:27:30 BTW the 35+ trainees are very interactive and engaged bunch 17:27:32 matjazp: good to know :) 17:27:36 matjazp: we could record the issues they face and work on it.. 17:27:46 we have had two sessions 17:27:55 it is true that we cannot generate the feedback on our selves 17:28:00 most have been to both sessions 17:28:02 *one our machines 17:28:32 ideas on how to get feedback on the trainees? 17:28:42 im going to ask the trainers as well 17:28:48 log bugs for the errors they run into? 17:28:51 how to get the feedback 17:28:57 sayali: yes, I forgot to tell them to explicitly record all errors... but it was based on using Slovene local settings on Mac 17:29:05 sayali sure for materials that works 17:29:14 bout the rest 17:29:45 sarob: materials that work? 17:30:10 sayali not sure i understand the question 17:30:39 sarob: I meant log bugs for errors while running the scripts 17:31:05 or video :) 17:31:18 bugs for video? 17:31:29 but I agree with sarob, trainees should have a super easy method for giving feedback - I'm not convinced filing bugs are easy enough? 17:31:32 the feedback has to be interactive 17:31:45 we get bugs 17:31:55 I guess they can write feedback on the videos.. 17:32:01 launchpad is way over most people's heads 17:32:04 we could keep an hangout 17:32:08 every month or two 17:32:17 hello 17:32:25 shillsaebi hi 17:32:39 we are discussing how to get feedback from trainees 17:32:50 if they can't write down their thoughts after an event, they sure aren't gonna do it later... 17:32:54 we could have a scheduled feedback time 17:32:55 Is there a way to solicit feedback through a survey 17:33:11 matjazp: yeah the feedback should be timely 17:33:14 hello ShillaSaebi MeganR1 17:33:27 sarob: maybe trainer can act as a collector and write few lines after each session? 17:33:27 hello ShillaSaebi 17:33:38 hey ShillaSaebi 17:33:40 meganr1 maybe surveymonkey per event is the way to go 17:33:44 that way you could direct the questions, especially if you are seeing continued issues/questions 17:33:54 yeah survey monkey per event sounds good 17:33:59 sarob - I have had good success with Survey Monkey 17:34:00 matjazp plus the trainer 17:34:44 maybe even write in 10 min at the end of the training to complete the survey 17:35:10 #action sarob will take first pass at surveymonkey template for trainer sessions, share with trainers and training-guides teams 17:35:43 other ideas? 17:36:44 okey dokey 17:37:14 im stuck with a git push error 17:37:45 lets do this in order 17:37:54 i hold on to that for a minute 17:38:08 any more on trainers team? 17:38:48 #topic criteria and candidates for core reviewership 17:39:01 i think rluethi posted this to the agenda 17:39:40 rluethi have you joined? 17:40:04 i ask him over ML 17:40:23 #topic Kilo blueprints signup 17:40:29 rluethi is not going to make this meeting 17:40:46 he is out of town till 20th December 17:41:09 dguitarbite: ah right 17:41:13 he asked me to start with this discussion 17:41:19 * sarob never enuf coffee 17:41:33 #link https://etherpad.openstack.org/p/training-guides-kilo-summit 17:42:07 at the bottom are the bp/topic i believe summarize what we have planned/discussed for kilo 17:42:22 i created bp from them 17:42:46 before i jump into push specs, 17:43:20 finally etherpad is working again 17:43:47 whatca all think? 17:45:06 sarob: everyone need to add their name to it 17:45:23 thats the general idea 17:46:34 and the date you think you can contribute to completing the bp 17:46:52 i used the milestone 17:47:06 you can use just a date if you prefer 17:47:21 ok 17:47:35 some items depend on other ppl (e.g. infra team for Moodle instance, integration with Launchpad IDs) 17:48:17 true, those dependencies go into the spec 17:48:28 once you sign up for a bp 17:48:48 pushing the spec to openstack/docs-specs/kilo is the next step 17:49:18 so the team can review and comment on the bp details in the spec 17:50:25 dguitarbite: you are already working on 3 17:51:01 dguitarbite: can i get you to commit to M1 for automate the slide build 17:51:29 sarob: creating new slide material is covered in convert-the-xml-into-rst? 17:51:35 sarob: I think stefanos team should be able to do this 17:51:46 I did that before and the time and effort was wasted 17:51:54 I do not want to do it till its very clear 17:52:05 dguitarbite: agreed 17:52:43 I believe things will change regarding slide's infra and tools... as we get feedback 17:52:45 dguitarbite: reed needs to figure out the requirements, then you can restart 17:53:10 matjazp: some sure, but the content needs to get out there for the trainees 17:54:22 dguitarbite: if I broker a resolution in what tools dhellman and reed want us to use, can you take this on? 17:54:44 dguitarbite: since you already did most of the work 17:55:25 sarob: I am supposed to do that as infra sub team lead 17:55:29 sayali: what do you think of bp #14? 17:55:32 I am waiting for feedback from reed 17:56:00 I will do the required things once I get feedback from reed 17:56:03 sarob: just updated that part with my name 17:56:19 dguitarbite: nope, not at all. i just thought you are in the best postion since you have already done work on it 17:56:39 sarob: yes 17:57:00 sayali: cool 17:57:21 ideas on dates for bp? 17:57:32 I think ShillaSaebi would also like to add her name there 17:57:35 we have a couple of minutes left 17:57:59 shillsaebi: all are welcome :) 17:58:30 any other last minute issues? 17:58:39 since BP #3 is important, we should comment on the spec for it as soon as possible 17:59:07 okay 17:59:27 I will push the spec with reed and dhellman feedback 17:59:45 dguitarbite can weigh in on if its doable 17:59:57 i think that is it 18:00:08 i have a git push issue 18:00:11 it is doable 18:00:22 talk on docs channel if you have a minute 18:00:24 but I cannot assume feedback 18:00:25 yes 18:00:32 #endmeeting