20:00:59 #startmeeting openstack_upstream_institute 20:01:00 Meeting started Mon Dec 4 20:00:59 2017 UTC and is due to finish in 60 minutes. The chair is ildikov. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:01:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:01:03 The meeting name has been set to 'openstack_upstream_institute' 20:01:06 @! 20:01:07 <_pewp_> jungleboyj (;-_-)ノ 20:02:21 ./ 20:02:35 hi :) 20:02:44 \o/ 20:03:25 thanks to diablo_rojo_phon, we have a long agenda for today :) 20:03:28 #link https://etherpad.openstack.org/p/openstack-upstream-institute-meetings 20:04:01 I can be here until the flight attendant tells me to turn my phone off :) 20:04:19 diablo_rojo_phon: safe travels! :) 20:04:29 I think we can start 20:04:55 #Announcements 20:05:03 Mondays... 20:05:07 #topic Announcements 20:05:46 It happens to the best of us. :-) 20:05:58 we are pretty close to the holidays, so we should try to get some progress now! :) 20:06:40 beyond this we have a couple of OpenStack Days events for next year interested, we will get back to you with more info once the event planes and dates are settled 20:07:17 Three events. One in Europe. One is South America. One is Asia. 20:07:31 Cool. 20:07:32 and we will have two Summits next year as usual with two trainings that we need to prepare to 20:07:59 so let's talk a bit about Vancouver 20:08:03 #topic Schedule of flow for Vancouver 20:08:19 #link https://etherpad.openstack.org/p/OUI_exercises_reform 20:08:28 we have our reform etherpad still open 20:08:52 the goal is to re-think the training with the Contributor Portal in mind 20:09:25 we can also think about how to get the students more engaged during the course 20:09:34 beyond stickers :) 20:09:43 :-) 20:09:50 chocolate doesn't work that well 20:10:02 ildikov: I thought it worked well. :-) 20:10:02 and pens are heavy to carry home after the training... :) 20:10:13 Beer and Wine! 20:10:22 jungleboyj: people were more excited about the stickers 20:10:29 I thought the tim tas went well even the Aussies were picking them:) 20:10:29 :) 20:10:45 spotz: You can get them a Target now. 20:11:13 Don't tell anyone jungleboyj I'm making gift tins out of a couple boxes! 20:11:16 not bad, but stickers were *the* hit as far as I remember 20:11:30 spotz: nice! :) 20:11:32 spotz: Nice. :-) 20:11:38 ok, back to the meeting topic :) 20:11:46 so please throw ideas to the etherpad 20:11:56 go crazy and try to think outside the box 20:11:58 Will do. 20:12:14 we should at least try :) 20:12:50 we would also like to continue building a liaison team that we started early this year 20:13:01 to get the activity on the project teams' mind 20:13:27 we could also connect the on boarding room activities with the training activities this way easier 20:13:32 ildikov: I think the main probably is most folks don't know necessarily months or even weeks in advance they're going 20:14:15 spotz: I thought to have people who can give a heads up to their team when we're having more info on what projects we need coverage for 20:14:37 spotz: also to maintain some ideas and exercises for the on boarding rooms 20:14:49 the latter one is more of a nice to have 20:14:58 ok 20:15:14 spotz: does it make sense? 20:15:32 ildikov: Yeah I was thinking more of Laison to line up folks to come 20:15:45 spotz: Makes sense. 20:15:51 I mean ildikov 20:16:08 we can also set a deadline on how much in advance we can expect/try to get reps from project teams where we need it from 20:16:30 ildikov: That would be good so we aren't scrambling at the last minute. 20:16:43 spotz: yep, someone who's on board roughly with what we do and can help us find someone 20:16:59 I think even if we don't get reps from projects, making sure they are aware of the activities could be good. 20:17:12 Would be good to have someone bringing it up in weekly meetings a month or so before the Summit. 20:17:19 smcginnis: ++ 20:17:21 jungleboyj: we will have a little scrambling anyway, but hopefully we can reduce that 20:17:32 I am in the Cinder/Swift and Manila meetings and can keep covering those. 20:17:33 smcginnis: +1 20:17:36 And if we push that we can be a stepping stone for their onboarding rooms that might get us more input 20:17:54 spotz: exactly! 20:18:04 spotz: Might be good to start more like 6 - 8 weeks ahead of time then 20:19:13 I think it ties back in with our discussions about helping to give folks ideas on what to do in their onboarding rooms 20:19:14 I can take the action to reach out to the liaisons we have currently on the list and check whether they are still willing to do it 20:19:33 and find a new person if needed 20:19:58 and we can expend on the list picking those projects we got interest on the past 2-3 trainings 20:21:47 Sounds good. Keep expanding our reach. 20:22:04 Yeah there were definitely tables the last 2 summits with no one interested in the projects 20:22:06 I think 3-4 weeks before the training we should have a 70-80% coverage as for mentors 20:22:22 ++ 20:22:24 +2 20:22:32 depends a bit on RSVP's as well, which I expect better now that we'll be back in North America 20:22:54 Yeah, that will be nice to have a better idea of the audience. 20:23:08 will be back to that topic in a bit 20:23:36 another idea is to set a date for the pre-Summit mentor meeting, which we usually have as a Hangouts call 20:23:50 I think it's a tougher one 20:24:06 we can give it a try to set one in the 3-4 weeks prior timeframe 20:24:10 I think that's a hrd call not knowing who's going to mentor yet 20:24:12 Might be hard to know availability too far ahead of time, but if we get it on the cal=endar that might be good. 20:24:39 I would avoid setting one too far in advance as we will most probably need to change it anyhow 20:24:44 I think we should also make that meeting a hard stop for changes to the training exercises. 20:24:59 Exceptions can be made of course, but as a general rule. 20:25:09 Going dark :) 20:25:35 Well we can go with the vague, 3 weeks before summit we will have a meeting:) 20:25:54 spotz: That is a good target. 20:26:46 I would have it closer to the Summit 20:27:14 ildikov: 2 weeks? People start disappearing after that. 20:27:16 and try to set an exact date like 3-4 weeks before the Summit if we managed to get mentors by then 20:27:26 yeah, two weeks I think would be ideal 20:27:35 Ok. 20:28:03 to see where we have anything last minute to fix/do without people thinking we have a plenty of time so no one does anything :) 20:29:01 that would definitely be a hard deadline for exercises and the flow of the training 20:29:17 fixing bugs, typos of course encouraged any time 20:29:34 Agreed. That should be the target for having all the main changes in place. 20:30:30 we can get back to the timeline, but sounds like a good start 20:31:14 ok, let's move on if no questions/objections to this topic? 20:31:45 I am good. 20:31:50 #topic Migration of Info from OUI Content to contributor Portal 20:32:07 * jungleboyj head explodes 20:32:22 #link https://storyboard.openstack.org/#!/project/913 20:32:36 so we have a few tasks in Storyboard already for the migration 20:32:39 please check 20:32:54 and pick one or create new tasks and pick one after that :) 20:33:24 Ok. 20:33:54 I think we should move slides over to archive once content is moved with a huge warning on the date it was last updated 20:34:05 So the goal there is to start taking what we currently have in our slides and make them a part of the portal? 20:34:12 and adding a link to the contributor portal page where the latest info can be found 20:34:19 ++ 20:34:33 jungleboyj: yes, moving the content over and keep the exercises in the training slides 20:34:48 Ok. 20:35:22 so we would basically create exercises to walk the students through the relevant info 20:37:07 as a strategy we will also try to use diagrams/pictures where we can 20:37:13 in the Portal 20:38:17 to avoid people being overwhelmed with a lot of text, especially in case of non-native speakers 20:38:49 Yeah, that is one of my worries moving to the Portal. Could be even more boring. We need to figure out how to avoid that. 20:38:49 think about what make sense, there's no pressure either way, the point is to ensure that people get the information we would like to share 20:39:20 Will there be translations made for the portal? 20:39:30 yeah, that's certainly not the point :) 20:39:44 Just curious. :) 20:39:46 smcginnis: good question, I need to ask around about that 20:39:58 I would think so 20:40:09 Cool. 20:40:59 any further questions/comments to this one? 20:41:55 Not from me. I really need to look closer at the Portal and figure out how we can maybe map the pieces together. 20:42:48 jungleboyj: sounds good 20:42:52 moving on then 20:43:01 #topic Brainstorm how better to promote for Vancouver? 20:43:29 we were facing a bit of a challenge in promoting Sydney 20:43:34 We need an OUI jingle. 20:43:38 Radio ... TV 20:43:48 I think that was a bit of a unique situation due to the location 20:43:50 BUT 20:44:09 it will not hurt to think about how to spread the word 20:44:38 we are usually doing a few rounds of Tweets 20:44:42 Nice to have a Logo now. That helps. 20:44:51 I wonder if we can get more visibility on the summit web site. And mention in the Reason to Attend. 20:45:16 Another Superuser article maybe about what we are doing to develop the project between now and then to get this in people's minds. 20:45:20 smcginnis: those are good ideas 20:45:22 smcginnis: ++ 20:45:47 I know we were linked from the Summit website but it was kind of hidden I thought. 20:45:54 smcginnis: some web pages have those headers that are switching a few images, we could have something like that for the Summit having the training up there 20:46:01 ++ 20:46:27 I do think it could help somem get justification to go if their management knows they will come back smarterer. 20:46:29 if the info needs to be found on the web site then it's like wheel of fortune anyway... 20:47:19 I think we could user the SuperUser blog to both advertise the new Portal and the training 20:48:09 True enough. I should probably start the sponsorship discussion soon and I wonder if there is anything we can do to help promote. 20:48:19 smcginnis: yeah, they'll be smarter however it's trickier to turn into immediate progress; hence challenge re management... 20:51:01 jungleboyj: good question, we can get back to that early next year after giving it some thoughts 20:51:24 Right. Miro and I are kind-of talking about this right now. 20:52:01 if anyone would like to write up a SuperUser blog post please do so and ping me or diablo_rojo_phon if you need any help! :) 20:52:14 jungleboyj: coolio! 20:53:27 jungleboyj: thanks! 20:53:37 ildikov: No problem! 20:54:29 we will also keep experimenting with the OpenStack Days events regarding trainings and use that for advertising if that format works out well 20:55:01 ildikov: I wonder if we should also see if there is any interest in a mini training at the ops midcycle. 20:55:24 smcginnis: sure, we can do an ops focused one 20:55:25 I think a few of those folks already participate, but there might be more than would contribute if they knew how. 20:55:39 I've been attending the weekly meetings. I'll see if there's interest. 20:55:48 smcginnis: the question is how much it is a mid cycle for already experienced people and how much we expect new people to show up 20:55:48 smcginnis: ++ 20:55:52 They are looking for session proposals for the next event in March. 20:56:05 Already experienced people running OpenStack. 20:56:26 But there might be some that would contribute docs, etc., if they were more comforatable with how that works. 20:56:37 happy to look into whether we could share any useful info with them 20:56:56 VW might have an opinion. 20:57:05 as if they made it to the mid cycle then they are already engaged with the community at least a bit :) 20:57:15 ildikov: Yep! 20:57:34 smcginnis: having them contributing back would be great! 20:57:47 smcginnis: so plz keeps us up to date 20:57:53 Will do. 20:58:22 smcginnis: I'm also happy to join any of the weekly meetings if you need support :) 20:59:06 ok, let's open up the floor for the remaining one minute :) 20:59:12 ildikov: Sure, I can try to remember to ping you before the next one, or pull you in if it looks like the conversations going anywher. 20:59:14 #topic Open dicussion 20:59:28 smcginnis: sounds good, thanks! 20:59:39 what might I have an opinion on smcginnis 20:59:44 * VW reads scrollback 21:00:08 I need to close the meeting 21:00:17 thanks everyone! 21:00:25 VW: We were just talking about whether it might be useful to do a min Upstream Institute training for the ops midcycle folks. 21:00:28 VW We can follow up later. 21:00:30 VW Not time critical. 21:00:32 move chats over to #openstack-upstream-institute 21:00:37 cool - let's do 21:00:38 #endmeeting