14:05:37 #startmeeting uc 14:05:38 Meeting started Mon Mar 12 14:05:37 2018 UTC and is due to finish in 60 minutes. The chair is mrhillsman. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:05:39 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:05:41 The meeting name has been set to 'uc' 14:05:53 #topic rollcall 14:06:57 o/ 14:07:00 o/ 14:07:09 #chair spotz zioproto 14:07:10 Current chairs: mrhillsman spotz zioproto 14:07:28 o/ 14:07:47 o/ 14:07:55 hello 14:08:27 o/ 14:08:30 hello 14:09:11 o/ 14:09:27 thx smcginnis 14:09:39 welcome all :) 14:09:41 Hey all 14:09:46 Sorry spotz 14:09:50 #topic Update following Ops Mid-cycle (tentative) 14:09:54 :) 14:10:14 i invited smcginnis to give us some output regarding the midcycle 14:10:29 The event went well I thought. 14:10:30 smcginnis basically as it relates to feedback gathering 14:10:42 And from the feedback I got from other attendees as all good. 14:10:57 There ended up being 100 people registered, 89 I believe that actually showed up. 14:11:02 Which I think is actually good. 14:11:20 that definitely is 14:11:32 Attendees were primarily from Japan, but there were a few from South Korea, China, India, US, and possibly a few others. 14:11:49 Much better turn out the Mexico City at least. ;) 14:12:09 There were two main tracks, General and NFV. 14:12:28 I mostly was in the General room, but the NFV room was pretty full whenever I looked. 14:13:03 Not sure if we got any kind of feedback from participants on topics, but I think most were useful. 14:13:34 anyone have questions/concerns for smcginnis ? 14:13:44 There was a little talk about trying to vote on topics again next time to try to make sure the topics were of interest to attendees, but I felt most of what we ended up with was of interest. 14:13:50 Do we have much of a South American user base? That could explain the low turnout there 14:14:12 Were there any key takeaways that we could convert into forum topics? 14:14:13 I think that was more due to the organization issues we had with two sponsors backing out late. 14:14:23 Or rather, one sponsor backing out twice. 14:14:30 Bleh 14:14:30 jamesmcarthur_: Good question. 14:14:50 We tried to wrap up with a feedback session and a "3 takeaways for development". 14:14:52 Could definitely mail the attendees 14:15:24 We got some feedback, but then kind of ran out of time and energy and didn't get as much of a ranked "takeaways" list as we would have liked. 14:15:48 There is an etherpad where Anne put some ideas to get the discussion started, but I think all we got were some +1's on those. 14:15:54 Let me see if I can find that etherpad. 14:16:20 It’s a start 14:16:44 #link https://etherpad.openstack.org/p/TYO-ops-meetup-2018-top3-requests Top 3 discussion 14:17:05 This was also interesting - 14:17:09 #link https://etherpad.openstack.org/p/TYO-ops-meetup-2018 also where all the pads are 14:17:11 #link https://etherpad.openstack.org/p/TYO-ops-meetup-2018-feedback Feedback session notes 14:17:19 mrhillsman: ++ 14:17:37 The idea of colocating with the PTG came up again. 14:17:46 Especially in light of the PTG financial issues. 14:17:53 Probably more discussion needed there. 14:18:23 But I believe we are all set for the second event this September. 14:18:25 got quite a few +1s there :) 14:18:58 Definitely some pros and cons with that idea, but I'm starting to like it after initially being against it. 14:20:03 discussion with jimmy and thierry on format was really good, i think we have/had a good idea to make it work 14:20:19 anything else on the midcycle? 14:20:32 Nothing from me, but feel free to ask any other questions. 14:20:52 I think it would have a lot of benefit especially if one day was planned for crossover discussions 14:21:01 ++ 14:21:13 #chair VW 14:21:14 Current chairs: VW mrhillsman spotz zioproto 14:21:22 hey folks - osrry for being late 14:21:46 Opportunities for evening drinks and casual conversation has a lot of benefits too. 14:22:05 we discussed ensuring the venting/discussing aspect lives in openstack days events and keep the spirit of work at the ptg 14:23:13 like at the midcycle we discuss monitoring, and it ends up being what tools you are using and why, which is fine, but then find out if folks would like prometheus for example, and then have a ops monitoring session at the ptg, and work on prometheus support or whatever other tool 14:23:59 anywho, do not want to detour us :) 14:24:20 so moving on, looks like we are good here? 14:24:40 yep 14:24:51 Yep 14:24:52 #topic Formal UC vote on temporary governance proposal for SIGs 14:25:06 everyone clear on the temporary governance proposal? 14:25:42 Yeah 14:26:06 any questions/concerns before we vote? 14:27:18 none here 14:27:48 Nope 14:27:53 #startvote Is the UC ok with temporary governance proposal for SIGs? Yes, No, Abstain 14:27:54 Begin voting on: Is the UC ok with temporary governance proposal for SIGs? Valid vote options are Yes, No, Abstain. 14:27:55 Vote using '#vote OPTION'. Only your last vote counts. 14:28:07 #vote Yes 14:28:13 #vote Yes 14:28:35 #vote yes 14:29:00 #vote yes 14:29:12 #endvote 14:29:13 Voted on "Is the UC ok with temporary governance proposal for SIGs?" Results are 14:29:14 Yes (4): spotz, VW, zioproto, mrhillsman 14:29:33 good stuff, will let thierry know and we will get a clear communication out 14:30:13 going to skip 4 as i think we can clear 5 and 6 quickly 14:30:18 #topic Determine if any Zoom session are need to do discuss PTG output 14:30:33 do we need this? if so, doodle poll ok? 14:31:03 to determine day/time or just do via current meeting day/time? 14:31:10 I think we covered most things pretty well during the one meeting 14:31:34 well, but this was more for the specific things we got from Tokyo right? 14:31:54 and I dropped the ball this weekend and didn't reach out to Anne 14:31:59 or the ops meetup folks 14:32:33 we had smcginnis go over tokyo 14:32:51 but we can definitely schedule additional time 14:32:56 Right before you logged in:) 14:32:59 we got this - https://etherpad.openstack.org/p/TYO-ops-meetup-2018-top3-requests 14:33:36 Not quite as concise as we were hoping, but at least some feedback. 14:33:54 ah 14:34:00 I'll read the logs and go from there 14:35:02 #action VW to determine if we need session to cover tokyo ops midcycle more thoroughly 14:35:06 ^ VW ok? 14:35:08 yeah 14:35:10 I'm thinking not 14:35:36 as smcginnis - not super detailed stuff, but plenty to start working with and circulating to regional meetups, etc 14:35:45 ok cool 14:36:00 #topic User Survey changes 14:36:09 aprice anything here? 14:36:12 there aren't any updates from last week's meeting 14:36:21 awesome, thank you 14:36:24 I will be sharing the changes this week though - just need to get some time with folks internally 14:36:26 no problem 14:36:41 #topic Further discussion on SIGs, their governance and relationship to Teams/Working Groups following PTG discussion 14:37:21 so we have #link https://governance.openstack.org/uc/reference/charter.html#structure-functional-teams 14:37:31 and #link https://governance.openstack.org/uc/reference/charter.html#structure-working-groups 14:38:16 and we have confused them a lot ;) 14:38:25 indeed 14:39:46 we have the summary here #link https://etherpad.openstack.org/p/UC-Rocky-PTG line 30 14:40:21 is the problem basically no clear definition of SIG 14:40:45 that's a big part of it 14:41:13 but I stand by my statements, that the reasoning of "this is how we can get devs and ops together on something" is flawed 14:41:18 we'd love that in Teams too 14:41:37 agreed 14:42:03 I think, for now, the UC should focus on cultivating Teams around operators that represent static groups of users - like Public Clouds - and making sure they are very successful 14:42:41 ++ 14:42:43 So are SiGs just the new thing because that’s what kubernetes has? 14:43:03 some of that 14:43:03 #action mrhillsman create a draft of what SIGs are and where they differentiate from TC/UC governed teams, projects, and working groups 14:43:25 nah, SIGs have been around for a long time in varying capacities 14:43:36 but they have been called working groups 14:43:37 i first learned about them from centos/fedora 14:43:48 and there was legit concern that if UC "owned" some groups and TC "owned" others, then the folks on the other side couldn't participate 14:43:58 so this was a bit of an attempt to fix 14:44:05 potentially misguided, but it is what it is 14:44:12 they are here, and they are doing some good things 14:44:28 so we should really firm up what we thing best represents ongoing groups of users 14:44:39 and assign a UC member to liaison to each 14:44:44 and help tem get what all they need 14:44:49 well said VW: 14:44:54 including dev participation, etc 14:45:17 Sounds reasonable thanks 14:46:15 here is the current list #link https://governance.openstack.org/sigs/ 14:48:03 even though there was a "push" to move to SIG we still have quite a few teams/wgs that are not 14:48:24 and i think they would agree we need to do the same for them 14:49:09 how do we want to handle liaising? 14:49:26 it's probably time to have another cross WG meeting 14:49:30 o/ 14:49:47 or at least have a them all let us know if they are still active and/or need to be spun down 14:50:09 hey thingee 14:50:09 mine, for example, is probably the latter, but I need to confirm with the previously active members 14:50:15 howdy thingee 14:50:29 vw I know a few showed up during the session in Sydney 14:50:34 hey thingee 14:50:48 it can be tough to get folks 14:51:07 can we do email + meeting 14:52:16 time check - 8 minutes left 14:52:46 hi hi, meant to be here earlier to participate :) 14:54:16 yeah - we can start with email 14:54:26 give me the action to draft first one 14:54:36 but I'd like two weeks since i'll be skiing this week :) 14:54:47 hehe, ++ 14:55:29 #action VW draft email for cross-wg discussion on active/non-active in a couple weeks 14:55:48 Not enough snow in Dublin?:) 14:55:51 #topic Open Discussion 14:56:05 anything in the last 5? :) 14:56:45 i would like to say please be sure to review #link https://etherpad.openstack.org/p/UC-Rocky-PTG if you have not already and put comments/suggestions 14:57:44 I've read it many times, but will continue to noodle on it and refine comments 14:58:33 welp, thx everyone for joining! 14:58:38 will end here 14:58:41 thanks! 14:58:45 #endmeeting