Monday, 2018-02-05

*** VW has joined #openstack-uc14:14
*** jamesmcarthur has joined #openstack-uc14:14
*** VW has quit IRC14:28
*** VW has joined #openstack-uc14:28
*** jamesmcarthur has quit IRC14:45
*** jamesmcarthur has joined #openstack-uc14:46
*** VW_ has joined #openstack-uc17:23
*** VW has quit IRC17:25
*** VW_ has quit IRC17:27
*** VW has joined #openstack-uc17:58
VWwhat's up, party people!18:00
jamesmcarthuro/18:00
VW#startmeeting uc18:00
openstackMeeting started Mon Feb  5 18:00:58 2018 UTC and is due to finish in 60 minutes.  The chair is VW. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: uc)"18:01
openstackThe meeting name has been set to 'uc'18:01
VW#chair zioproto18:01
openstackCurrent chairs: VW zioproto18:01
VWLooks like light attendance, but just to be sure18:01
VW#topic roll call18:01
*** openstack changes topic to "roll call (Meeting topic: uc)"18:01
VWlooks like it may just be me and you jamesmcarthur18:03
mrhillsmano/18:03
VWwoo hoo - we summoned a Melvin18:04
mrhillsmansorry so late18:04
VW#chair mrhillsman18:04
openstackCurrent chairs: VW mrhillsman zioproto18:04
VWagenda is here #link https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Meeting_Agenda.2FPrevious_Meeting_Logs18:05
VW#topic Update on Election Process18:06
*** openstack changes topic to "Update on Election Process (Meeting topic: uc)"18:06
jamesmcarthurSo far, I don't think we have any candidates.18:06
VWyeah :(18:06
*** leong has joined #openstack-uc18:06
mrhillsmani will get my nomination in later today; in the morning at the latest18:07
VWawesome! thanks mrhillsman18:07
jamesmcarthurwoot!18:07
leongo/ hi all18:07
jamesmcarthurleong: hello!18:08
VWhello leong18:08
mrhillsmanhey leong18:08
VWOk - I didn't see a reminder email go out either18:08
VWso, it sounds like we need to get one of those out and tweet the UC article18:09
mrhillsmani sent one later in the week i think iirc18:09
VWdid you - sorry18:09
mrhillsmanbut yes, we need one, and the twitter push as well ;)18:09
* VW missed it 18:09
VW#action mrhillsman VW zioproto tweet UC article18:09
jamesmcarthurI'll ping Anne/Allison re: Twitter/social. It's already on their radar, so I think they're anticipating.18:10
mrhillsman++18:10
VWexcellent!18:10
VWthanks jamesmcarthur18:10
VWanything else election related at this time?18:10
jamesmcarthurI do need some help getting SIG list together to add to the electorate list18:12
jamesmcarthurShould be a quick thing, but if anyone knows how to gather that info, would be great.18:12
leongi assume that we have the updated AUC list?18:12
mrhillsmanshould we send an email to the SIG leaders jamesmcarthur ?18:13
VWhmm - I am admittedly behind on the SIGs18:13
jamesmcarthurleong: yes, everything except the SIG attendees18:13
mrhillsmanwe should probably send a reminder late in the evening US time too for non-US folks :)18:13
jamesmcarthurmrhillsman: that would be great. Or if you have the SIG leader list, I'm happy to reach out.18:13
*** Ender948 has joined #openstack-uc18:14
VWI have a lot of quesitons about SIG in relation to AUC, but maybe that's a good conversation to have while some of us are in the same place at PTG18:15
jamesmcarthur+118:16
VWHowever, if we are saying that all SIG members are AUC, and therefor eligible to run and/or vote, I think we are also implying UC governance over them - imo18:16
Ender948yeah, I see what you are saying18:16
jamesmcarthuryeah VW, I don't think SIGs are specifically outlined as part of the electorate/AUC.18:17
jamesmcarthurMaybe SIG leaders?18:17
VWnot sure18:17
jamesmcarthurBut if it's not in existing governance, we can't let them vote.18:17
VWbut, on the flip side, does participation in SIG's by Operators/users satisfy the AUC requirements18:18
leongthat might lead some confusion? is SIG between UC/TC?18:18
Ender948we could try it for a short period of time18:18
mrhillsmanSIGs have developers and non-developers18:19
mrhillsmanso some folks within a SIG could be and not be AUC18:19
leong#link SIG https://governance.openstack.org/sigs/18:20
VWWell, to jamesmcarthur's immediate needs, I think we should get him a list of SIG leaders.  Then he can email them, show them the criteria of AUC and ask for them to send back list of members that qualify?18:20
mrhillsmanbut yes, we should discuss during PTG, maybe even before but right now it is very loosly governed still18:20
leongAs quoted: The OpenStack SIGs (Special Interest Groups) are a form of working group in OpenStack that is an emanation of the community as a whole and "is not directly tied to a specific governance body."18:20
mrhillsman++ VW18:20
VWthen we at least solve the immediate need of getting eligible voters accounted for18:20
leong"is not directly tied to a specific governance body."18:20
Ender948yeah, that is trye18:21
Ender948*ture18:21
leongquestion: does that mean SIG will lose voting rights?18:21
Ender948*true18:21
jamesmcarthurVW: If someone in a SIG is already qualified under one of the other criteria, we should already have them. The only question to me would be does leading or participating in a SIG itself qualify them as an AUC. And it soujnds like the answer is no.18:22
VWI think the more accurate answer is we don't know18:23
VWor haven't though of that scenario18:23
Ender948I am on the fence18:23
VWso, maybe we take a posture of no now, and clarify SIG participation in relation to AUC18:24
VWI'd rather expand voting rights going forward versus saying yes today and no tomororw18:24
leongjamesmcarthur: maybe this is something that need to discuss long term: i assume eventually most WG/Team are moving towards SIG, so the "other criteria" might eventually "shifted away"18:24
VWOk - so we clearly have some work to do going forward around this18:26
leongi am leaning towards to include SIG leaders + participants as AUC18:26
VWfor this election, do we take any specific action?18:26
leongmaybe for this election, we should stick to existing criteria and do not include SIG as this wasn't communicated before?18:27
mrhillsmanwe can do SIGs that were previously UC WG or Team18:28
leongthose previously UC WG/Team should already covered in the existing criteria18:28
*** VW has quit IRC18:29
jamesmcarthurleong: correct18:29
*** VW has joined #openstack-uc18:30
VWargh - home internet barfed18:30
VWsorry about that18:30
jamesmcarthursince we switched to SIGs kind of mid-cycle, I think we should already have accounted for those AUCs that were previously in WGs18:30
VWgood point18:31
*** leong has quit IRC18:33
VWwe don't even really have a quorum to vote on anything either I suppose with just two UC members18:33
mrhillsmannope18:34
mrhillsmanagree with you jamesmcarthur18:35
VWwell, then for now, I say we leave things as is, but we still have time to revisit next week if we feel we are missing a large part of the electorate18:35
VWbut this does shed light on the need for a formal position of the UC in relation to SIGS (at least for purposes of AUC) going forward - especially as we think about a multi-project world18:36
VWshall we move on for now?18:36
VWor do we have more to discuss here18:37
jamesmcarthuryes sir - writing this down for part of our PTG agenda :)18:37
mrhillsmanthx jamesmcarthur18:37
VWindeed18:37
VWwhich we'll get to that in a minute18:38
VW#topic Release Cycle Involvement18:38
*** openstack changes topic to "Release Cycle Involvement (Meeting topic: uc)"18:38
VWso, moving down the agenda, we added this last week18:38
VWbut I don't recall the context now18:38
VWnor, do I know if we have enough to discuss18:39
VWI know zioproto was very passionate about it18:39
*** Ender948 has left #openstack-uc18:39
VWmrhillsman thoughts?18:40
jamesmcarthurVW: notes from last weeK: can we target a set of operators from different industry size and type to see if we can get specific feedback around release cycles and upgrades?18:41
mrhillsmanyes, i think we can hold off for now because zioproto was primarily passionate about it18:41
jamesmcarthur(from mrhillsman)18:41
mrhillsmanyep, we have that in google docs18:41
mrhillsmani think we agreed to a mini-survey?18:41
VWcool18:41
VW#action mrhillsman VW get the rest of the UC to flesh out thoughts around user mini-survey in Google doc18:42
VWand I'll put this on the agenda for next week too18:42
VWTime check - we have 17 minutes.18:44
jamesmcarthurtopic change?18:44
VWyes - I propose we skip the mid-cycle one this week18:45
VWnot much new to report18:45
VWmrhillsman: agree?18:45
jamesmcarthurOnly small thing I'd add is Anne Bertucio from the Foundation will be in Japan to take feedback/represent18:46
VWnice!18:46
* VW needs to remember to let the Ops meetup teams know18:46
jamesmcarthurI'll be on that meeting as well, so happy to update in case you forget :)18:46
VWsweet!18:46
mrhillsmanagreed18:46
VW#topic UC planning at PTG18:46
*** openstack changes topic to "UC planning at PTG (Meeting topic: uc)"18:46
VWso, for the record, I have tickets booked18:47
mrhillsmansame18:47
VWthat makes mrhillsman and I who will both be in person18:47
VWhaven't heard the final on Shamail18:47
mrhillsmanshamail is waiting on travel support too last i heard18:47
jamesmcarthurAlan Clark also wants to join in to that meeting.18:47
mrhillsmanleong will not make it18:47
VW:(18:47
mrhillsmanthat would be awesome jamesmcarthur18:47
jamesmcarthurspecifically to discuss Product Working Group future18:48
VWcool18:48
VWI'm pretty much planning for all of Tuesday and Wednesday to be UC related stuff18:48
VWwhether formal sessions or something else18:48
jamesmcarthurMy concern is we won't have a quorum. I asked Saverio if he could join via Zoom. We might be able to do the same for some of our newly elected members18:48
VWagreed18:48
mrhillsmanwe should have new UC folks by then though :)18:49
VWwe should plan on some afternoon sessions with zoom/other virtual optoins18:49
mrhillsmansorry, did not read full sentence before responding18:49
mrhillsmaneven if we do not have quorum i think we can within the couple days get a decision18:49
VWagreed18:49
VWalso, just so you folks know.  I'll be getting in Saturday because the flights were much cheaper18:50
VWso, I have time to pre-plan during the weekend18:50
jamesmcarthursame18:50
VWcool18:51
jamesmcarthurCould we circulate a rough agenda via email?18:51
VWI think so18:51
VWor build one out in the doc18:51
VW?18:51
jamesmcarthurWould be nice to have something we can publish to etherpad b/f Dublin18:51
jamesmcarthuryep -that works too :)18:51
VW#action VW mrhillsman zioproto jamesmcarthur build rough schedule for UC conversations at PTG in Google doc18:52
VWcool - we'll revisit this the next couple of Mondays too18:52
VWso to honor whoever added it to the agenda18:53
VW#topic Meetings on 1st, 2nd, 3rd...vs Even/Odd18:53
*** openstack changes topic to "Meetings on 1st, 2nd, 3rd...vs Even/Odd (Meeting topic: uc)"18:53
mrhillsmanwe could start to circulate next Monday?18:53
mrhillsmansorry18:53
mrhillsmanok18:53
mrhillsmanyes, i put this one18:53
mrhillsmanjust seems a little odd trying to figure even/odd18:53
VWso, be more specific - 1st, 3rd, 5th Monday is X time and 2nd, 4th is Y?18:54
mrhillsmanseems it would be easier to just say 1 and 3 - 1800 UTC, 2 and 4 - 1400UTC18:54
mrhillsmanyes, 1 3 5 sorry18:54
mrhillsmanless brain cycles18:55
VWgood with me18:55
VWlooking for where we have odd/even written down18:55
mrhillsmanhttp://eavesdrop.openstack.org/18:56
mrhillsmanhttp://eavesdrop.openstack.org/#User_Committee_Meeting18:56
mrhillsmanwe do not have quorum to decide so it is ok18:57
VWOk - well, it's just a wording change18:58
VWbut I agree18:58
VWwe'll bring it up next week to get a formal vote18:58
VWwith that, I think we are at time18:59
jamesmcarthurthanks all!18:59
VWthanks to all those who made it today18:59
VW#endmeeting19:00
*** openstack changes topic to "Open Discussion (Meeting topic: uc)"19:00
openstackMeeting ended Mon Feb  5 19:00:07 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/uc/2018/uc.2018-02-05-18.00.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/uc/2018/uc.2018-02-05-18.00.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/uc/2018/uc.2018-02-05-18.00.log.html19:00
mrhillsmanthx gents!19:00
*** jamesmcarthur has quit IRC19:22
*** jamesmcarthur has joined #openstack-uc19:43
*** jamesmcarthur has quit IRC19:43
*** jamesmcarthur has joined #openstack-uc19:44
*** VW has quit IRC20:08
*** VW has joined #openstack-uc20:09
*** rockyg has joined #openstack-uc20:13
*** jamesmcarthur has quit IRC20:38
*** jamesmcarthur has joined #openstack-uc20:38
*** jamesmcarthur has quit IRC20:56
*** jamesmcarthur has joined #openstack-uc20:57
*** jamesmcarthur has quit IRC21:02
*** jamesmcarthur has joined #openstack-uc21:10
*** jamesmcarthur has quit IRC21:15
*** rockyg has quit IRC21:39
*** jamesmcarthur has joined #openstack-uc22:07
jamesmcarthurI updated the OpenStackUC 2018 Strategy doc to include some potential PTG discussion topics based on the past couple of UC Meetings22:38
jamesmcarthurThere is some overlap b/w our 2018 strategy goals, but I didn't want to muddy the waters by merging them22:39
jamesmcarthurFeel free to do what you will with all that :)22:39
jamesmcarthurMVW mrhillsman ^^22:42
mrhillsmanthx jamesmcarthur22:45
mrhillsmanWill review shortly ;)22:45
VWawesome - thanks jamesmcarthur22:49

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!