16:01:13 #startmeeting uc 16:01:13 Meeting started Wed Feb 28 16:01:13 2018 UTC and is due to finish in 60 minutes. The chair is VW. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:16 The meeting name has been set to 'uc' 16:01:32 o/ 16:01:43 #chair zioproto spotz leong mrhillsman 16:01:44 Current chairs: VW leong mrhillsman spotz zioproto 16:01:54 o/ 16:02:06 \o/ 16:02:06 welcome to the UC spotz :) 16:02:10 fyi - mrhillsman and I are in a room where another conversation is going on, so he may be focused on that 16:02:13 thanks zioproto:) 16:02:20 yes - first off, congrats to leong and spotz 16:02:31 multitasking... mrhillsman 16:02:37 thanks VW 16:02:43 Thanks VW:) 16:02:51 welcome leong :) 16:02:56 we'll do more of the formal welcomes, chair elections, etc on Monday 16:03:22 but we did want to catch the whole team up on conversations to date 16:03:43 VW: what's the agenda today? 16:03:57 my thought was we could walk through https://etherpad.openstack.org/p/UC-Rocky-PTG 16:04:03 at a high level of course 16:04:25 part of why we set up the meeting was to have a place holder if we needed any votes 16:04:33 doesn't look like we'll need that 16:04:53 but we'd love to pass on some key items coming out of the strategic planning sessions 16:05:00 which reminds me... 16:05:17 #topic Review UC PTG discussions 16:05:48 i did read through the etherpad.. looks good to me from a high-level perspective 16:05:56 cool 16:05:57 sorry i'm here :) 16:06:54 just a few nits when comes into detailed discussion 16:07:12 so, I think one of the key summary items is that the UC needs to start channeling output from Ops and end users in to more tangible items in the dev process 16:07:37 for example - can we help get topics at the Ops Mid-cycle translated into forum submissions at the next summit 16:07:38 i assume that we also need to review UC 2018 Goals in alignment with Boards' strategic focus areas 16:07:55 yes 16:08:20 but there seems to be general agreement that the user space across all the SFA's is probably largely shared 16:08:32 Can OPs submit for forum sessions and if so do they know? 16:08:33 so the UC as it is today probably needs to play a role across them all 16:08:39 They can 16:08:41 some do 16:09:03 our hope is that we can help make it all more obvious and successful 16:09:33 our realistic goals are looking to getting feedback from mid-cycles, OS days and regional meetups into Berlin as forum sessions 16:09:36 spotz: VW: need to clarify with Foundation staff on how to structure the Ops and Forum session 16:09:51 Might be a good superuser article, A hey OPs did you know... and that could be one item 16:10:00 not sure I follow, leong 16:10:14 it used to have a Ops "summit" alongside with the normal summit 16:10:25 ah yes - words are hard :) 16:10:31 let me try and explain a bit 16:10:39 Jimmy is unable to join the meeting today, but I will pass along any notes from the meeting 16:10:49 thanks aprice 16:10:52 Thanks aprice 16:10:57 and it is being recorded 16:11:09 let's put that an AR to follow up and clarify with Jimmy (they have been doing a great job!) 16:11:47 anyway, beginning in Atlanta, we started having sessions co-located with the design summit for Operators 16:12:08 however, the design summit, itself, changed to the forum in Boston 16:12:25 VW: do you want to take that AR to follow up with Jimmy? :) 16:12:43 or i can shoot an email now..:) 16:12:45 sure - not sure what I'm following up on 16:13:05 yeah, im happy to follow up as well, but am confused about the action item 16:13:11 Criteria for submitting to the forum I think? 16:13:41 ah - let me finish the brief history lesson and I think it will make more sense :) 16:14:28 back in the design summit days, the primary summit sessions were very much about HOW things would be implemented in software. The conversations in the room were very blueprint and code focused 16:14:55 it was often hard to feel useful if you were an operator in the room that hadn't been involved in all the dev team work to that point 16:15:31 with the shift to the Forum model, the focus on the sessions is now more about WHAT the software should do - high level feature/function conversations that aren't too deep in the code 16:15:55 they should attract both dev and ops looking to discuss these items 16:16:13 the "HOW" bit now takes place at the PTG 16:16:41 anyway, to leong's point, it's really more that the old design summits and Ops sessions merged (or got replaced) by the new forum sessions 16:17:05 there isn't a lot of risk of us driving submissions by Ops/Users colliding with other things 16:17:37 does that make a little more sense? 16:18:50 the all story you described makes sense to me 16:18:52 VW I think it's more of a communication issue of what can be submitted for the Forum and when 16:18:58 it is a perfect summary of the current situation 16:20:07 spotz: https://wiki.openstack.org/wiki/Forum 16:20:15 At least from the OSA side of things we're following what you've described and the few others I've seen prepping for Forums have as well 16:20:44 what we are trying to do is leverage Ops/user gatherings for the "Brainstorming" portion 16:21:11 my assumption is that: anyone including ops can propose forum sessions. Today Forum sessions is focus around 3 areas: project-specific, cross-project, and strategic. 16:21:21 and it is still more "dev-centric" 16:21:31 and turning common issues, pain, concerns into forum submissions for fixes, features, functions 16:21:37 i think there should have an area which is more "ops-centric" 16:21:48 not really 16:21:51 leong I think that's a result of OPs not submitting things which goes back to us helping to drive it 16:22:03 we aren't looking to make ops/distinctions here 16:22:04 spotz: +1 16:22:15 we are looking to take the concerns of the users and turn them in to change/action 16:22:26 yeah - +1 spotz 16:22:46 that's what i am trying to say.. more forum sessions are driven by dev 16:22:53 ah - yes 16:22:56 got ya 16:23:32 cool - so we all are in general agreement that anything we can do as a body to help get more session driven by Ops input, the better things will be 16:23:34 we need a focus where users can express their needs/requirements and get these into the development priority 16:23:38 plenty of details to figure out :) 16:23:44 VW: +1 16:23:51 VW +1 16:24:13 VW: +1 16:24:17 so, leong - that's where we want to really focus things like the mid-cycle and gatherings at the OS days and regional meetups 16:24:28 these are places where OPs/Users are already gathering 16:24:35 VW: +1 16:24:42 and to date, the discussions there don't turn into much tangible action 16:24:57 VW: I would say that we tried to group in the same geo location PTG and Ops Mid-Cycle but Ops community refused the idea 16:25:08 we have been trying to collect those data from mid-cycle / os days or meetups.. but haven't been very effective 16:25:23 zioproto: What was the reason? 16:25:26 agreed leong 16:25:57 mrhillsman and I were driving the "etherpad digging and summarized action items" 16:26:05 personally i believe the process was too heavy 16:26:19 we discussed very simple process during sessions 16:26:29 let's be careful. co-locating the Ops-midcycle isn't the way to really push what I am describing above 16:26:40 spotz: Ops felt their importance would be smaller merging their event into the PTG. Ops mid-cycle is a 2 days event. PTG is a full week. Putting the events together in the same place and the same week sounded scary to ops. They were afraid to be overwhelmed by the PTG 16:26:47 there may be reasons to co-locate in the future for budget/facility reasons 16:27:12 BUT the forum sessions are the discussions where Ops and Dev in the same room provides the most value 16:27:15 for information: #link etherpad double-hashtag result: https://github.com/openstack/development-proposals/tree/master/forum/201705-bos 16:27:56 VW: +1... co-locating is not a solution 16:28:15 but it still might need to happen, but we'll table that discussion for now :D 16:28:25 ++ 16:28:44 we actually decided to do a little pilot test with the Tokyo meeting next week 16:28:49 we have two simple goals 16:29:07 1. can we get a list of 3 or 4 key issues that are common to most of the attendess 16:29:12 Ok so we've got promoting OPs to submit forum sessions as an action everyone can agree on:) 16:29:41 the hope is that we, as the UC, can circulate that back to the regional meetups and such to get more feedback and channel to forum sessions by Berlin 16:29:55 * leong unfortunately i won't be attending Tokyo Ops midcycle 16:30:36 2. Since there are some specific tracks in Tokyo (NFV for example), we are going see if we "might" be able to get 1 or 2 direct forum submissions out of the conversations there 16:30:41 #2 is a long shot 16:31:06 but if the UC can show that kind of success, it would be a huge win 16:31:18 none of us will be there leong 16:31:32 but anne from the foundation is here and will be attending Tokyo 16:31:58 jamesmcarthur, aprice, mrhillsman and myself have been working with her to try and do some of what I just described 16:31:59 VW if we can get the top 1-4 pain points, could the UC submit and drive the coversation? 16:32:09 VW: i agree with the goal... the challenge is 'how' and 'who' to drive the 3-4 key issues (assuming that not all UC has the relevant domain knowledge in every issues) 16:32:14 yes, spotz - exactly 16:32:29 well, leong - that ties in to another part of the etherpad 16:32:46 better use of regional ambassadors, regional meetups, etc 16:33:15 We should get that top 4 things in their hands and get input from the users we may not hear from as often 16:33:28 scratching the etherpad contents is a pain especially if you are not "in that" discussion 16:33:42 agreed 16:34:08 but if we can make the ambassadors or meetup leaders more active in the process... 16:34:28 we are also hoping that the organizers are going to send a summary as well so that digging through the etherpads are not as much of a pain 16:34:30 maybe they can translate the conversations into some specifics for us 16:34:34 Anne is going to try and help them do that 16:34:45 (ops meetup organizers) 16:34:53 or OpenStack Days organizers 16:35:00 or meetup organziers 16:35:01 etc 16:35:16 ++ 16:35:34 I'll try to hit the next Austin meetup, the last one I went to wasn't very OpenStack related 16:35:42 that's fair 16:35:54 but what if we had that top 4 list for you to float and get feedback ;) 16:36:09 aprice: VW: +1 i think we should *kind of* put some guidelines in place and encourage coordinator/organizer to send a summary *with action items* 16:36:26 when is the next Austin meetup? 16:36:58 but yes - you guys are totally getting it 16:37:28 and leong your question is exactly why we want to "test" some of the process with Tokyo 16:37:56 VW: cool... let;s get that going and sync up with shintaro 16:38:34 yeah - since he and Chris were online yesterday for the normal Ops Meetup team meeting, we did a preliminary dump of these ideas on them 16:38:40 they were open to it 16:38:54 and Anne will help drive things there 16:39:10 there's a chance we got it all wrong, but we will just iterate on the process based on how things go 16:39:25 leong In the next week or 2 I think 16:39:47 spotz: ok... got it.. you mean to regional meetup... i thought you refer to ops-midcycle :-) 16:40:04 leong: Oh no though it would be nice if there was one there:) 16:40:26 #action spotz confirm next Austin regional meetup date 16:40:45 VM MArch 8:) 16:41:04 #action VW add iterating on feedback loop via Austin meetup to agenda 16:41:37 we'll try and revisit that on Monday, spotz 16:42:31 so, the last big thing I wanted to touch on from the PTG etherpad is we may be looking at further defining/expanding the AUC designation 16:44:05 jamesmcarthur, aprice, lsell, mrhillsman and myself don't know exactly what that looks like yet, but we discussed the need to make improvements 16:44:32 that's likely to be a recurring topic in our regular meetings 16:45:50 AUC needs to be reviewed and updated per cycle and published 16:46:01 right 16:46:15 we need to figure out to better catch ALL the right folks 16:46:20 ++ 16:46:25 and do so as programmatically as possible 16:46:36 ++ 16:46:44 sounds good 16:47:04 so tl;dr - the work here has been good, and the UC has a pretty full plate for the next year 16:47:18 but the foundation is all about helping us be successful in all of the stuff above 16:47:48 also on how SIG to be included in AUC 16:48:01 again, it looks like enough stuff to justify a Foundation person working in the UC, like there are already Foundation persons in the TC. This was also proposed in the past. 16:48:20 so that is where jamesmcarthur comes in 16:48:21 jamesmcarthur from the Foundation is going to be working very closely with the UC 16:48:27 the UC isn't the only thing he does 16:48:30 great news ! :) thanks 16:48:35 but he has been doing a lot for us 16:48:40 and will continue to 16:49:03 because it takes a lot of time to finalize all this things, and all of us are doing UC out of our core business 16:49:14 but, zioproto - I can attest to the fact that a lot of the discussions that are in the etherpad included many many Foundation members 16:49:33 and they are all very interested in helping us accomplish these things 16:49:46 ++ 16:50:01 VW: yes. But there are some steps that require a single person gathering the material, polish it, and perform an action step 16:50:17 I think SIGs and a lot of the ops/user/new folks facing groups should be included for UC. The trouble is weeding through to get the folks who are actually active 16:50:17 agreed 16:50:30 right spotz 16:50:38 we'll talk about it though 16:51:15 we spent some time on SIGs, but there is still lots of confusion and very mixed opinions about what they are, should they exist, how they should be governed, etc 16:51:17 I mean that we can provide input with these meetings. We can do some actions, but we cannot work 20 or 30% of our time as community managers for the UC. This is why the help from jamesmcarthur is very welcome 16:51:21 more stuff for us to spend time on :D 16:51:46 I think this is the same vision also Edgar had in the past 16:52:00 true zioproto, but we should expect to have to spend some time out side of the meetings, etc working on things 16:52:05 to run the UC it is not enough to work on it 3 or 4 hours per week 16:52:51 that is why it is important to have a person that can spend more time on this actions, finalizing the things, after we provide input and material to work on 16:52:51 time check - this was supposed to be a quick update and we've gone almost an hour 16:53:11 anything else we need to discuss today? 16:53:53 not from me 16:53:54 thanks VW 16:54:00 thanks VW 16:54:07 I think we covered alot:) 16:54:16 awesome - thank you all for taking the time 16:54:21 welcome again, leong and spotz 16:54:33 will see you all on Monday at 1800 UTC!! 16:54:45 Thanks, take care all:) 16:54:48 have a good day! 16:55:05 #endmeeting