Monday, 2018-01-08

*** VW has joined #openstack-uc02:46
*** VW has quit IRC02:46
*** VW has joined #openstack-uc02:47
*** VW has quit IRC03:24
*** VW has joined #openstack-uc03:25
*** aprice has quit IRC07:13
*** aprice has joined #openstack-uc07:13
*** VW has quit IRC07:51
-openstackstatus- NOTICE: zuul has been restarted, all queues have been reset. please recheck your patches when appropriate10:26
*** VW has joined #openstack-uc14:31
*** VW has quit IRC15:10
*** VW has joined #openstack-uc15:10
*** shamail has joined #openstack-uc16:01
shamailHi everyone16:02
shamailPing mrhillsman VW16:05
VWsir, yes sir!16:05
mrhillsmanhey16:05
shamailAre we having the meeting today or is my calendar giving me the wrong info?16:06
mrhillsmanyes, 1800UTC?16:06
mrhillsmanat least i thought 180016:06
VWthat's what the wiki had for even weeks16:06
shamailSo 2 hours from now?16:06
VWyes, sir16:07
shamailAwesome, thanks!!16:07
*** shamail has quit IRC16:08
*** jamesmcarthur has joined #openstack-uc17:24
zioprotohello17:56
*** shamail has joined #openstack-uc17:57
VWhowdy17:57
shamailHi VW17:58
VWt minus two minutes until we dance17:58
shamail++17:59
shamailI am in two meetings at once17:59
VWI'll kick us off17:59
VW#startmeeting uc18:00
mrhillsmano/18:00
openstackMeeting started Mon Jan  8 18:00:20 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:00
*** openstack changes topic to " (Meeting topic: uc)"18:00
openstackThe meeting name has been set to 'uc'18:00
VW#chair mrhillsman shamail zioproto18:00
openstackCurrent chairs: VW mrhillsman shamail zioproto18:00
shamailo718:00
VWagenda published here:18:01
VW#link https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee18:01
VW#topic Roll Call18:01
*** openstack changes topic to "Roll Call (Meeting topic: uc)"18:01
VWo/18:01
shamailo/18:01
zioprotohere I am18:02
apriceo/18:02
shamailhi zioproto & aprice18:02
mrhillsmano/18:02
shamailHappy New Year aprice18:02
jamesmcarthuro/18:02
*** lsell has joined #openstack-uc18:02
shamailHi jamesmcarthur, mrhillsman, and lsell18:03
VWAwesome - looks like we have a full house18:03
VWmoving on to the agenda18:03
apricehappy new year18:03
jamesmcarthurhi all!18:03
VW#topic Election Kickoff18:03
zioprotoHappy new year everyone18:03
*** openstack changes topic to "Election Kickoff (Meeting topic: uc)"18:03
VWSo, the uc members had a quick video call last week.  One of the things we wanted to get a good start on was prepping for the UC elections next month18:04
VWOur target for announcing results is 2/1818:04
zioprotoWe needed to find the election chairs, right ?18:05
VWi have an open action to send out requests for election officials.  Does anyone happen to have a copy of an email asking for the same from a previous election18:05
VWI combed through all of mine with no luck18:05
apriceVW: i have a copy of the email that I can send to the UC members from the July election18:06
VWI'm happy to send it.  I just wanted to verify audience/content/etc18:07
VWwill you forward that to me and I'll get something out today18:07
apriceVW: yep18:07
VWsweet18:07
mrhillsmancool, i was off looking for a copy18:07
VW#action VW to email UC today for election chairs18:07
VWI will probably need your help aprice in arming those chairs with the mechanics of running the election18:08
VWbut we'll touch base on all that over the next couple of weeks, I'm sure18:08
mrhillsmanquite a few things in Tom's email (links)18:09
mrhillsmanfrom the February election last year as well18:09
VWyeah - I need to digest that as well.   Step one is clearly getting the officials18:09
mrhillsmanwhat will be our nomination period and voting period?18:09
mrhillsmansafe to say nomination is the week before the 18th18:10
mrhillsman11-17th?18:10
mrhillsmansorry18:10
mrhillsmanvoting18:10
shamaildont we want to annouce on 18th?18:10
shamailah ok18:10
VWyeah18:10
lsellwe might need to lean on spotz and ed leafe regarding the role of election officials, because we (foundation staff other than tom) didn't have as much visibility into that, but we can definitely help run the actual election18:10
VWwhen Matt Jarvis I were officials last Feb, he did most of the work on the poll setup etc18:11
mrhillsmanwe discussed leaving it open for community to volunteer for officials but agreed as well we will need to lean on some who have already done it18:11
mrhillsmani believe spotz and ed are quite familiar18:11
jamesmcarthurI'm talking with jbryce about this as well to make sure we're following bylaws and such.18:11
jamesmcarthurHappy to help out where I can.18:12
lsellyes, and i think spotz might want to run, but she could still help get the new election officials up to speed18:12
mrhillsmanoh, true18:12
mrhillsmani think she wanted to last time18:12
mrhillsmani think emphasizing the if you officiate you cannot run is important too18:13
VWabsolutely18:13
mrhillsmani did not realize that and almost signed up to do so last feb :)18:13
jamesmcarthurI will work on gathering the AUC list for electorate purposes.18:14
mrhillsmanit would be good for us to capture that down somewhere too18:14
VWthank you jamesmcarthur18:14
mrhillsmanthx jamesmcarthur18:14
VW#action jamesmcarthur work on AUC list for elections18:14
lsellin regards to the timeline, i would allow at least two weeks for nominations...we had to communicate about it quite a bit last year18:14
VWgood call out18:14
mrhillsmanagreed18:14
VWso, tentatively, nominations from the 28th of Jan through 9th of Feb18:15
VWelections 11 - 16th18:15
VWannounce by the 18th18:15
zioprotosounds like a plan18:15
mrhillsman++18:15
zioproto:)18:15
lselli like it except for the sundays :)18:16
VWhappy to change dates18:16
VWwe just targeted 2/18 as something to shoot for18:16
jamesmcarthurYeah, I would suggest moving to Monday18:16
jamesmcarthurJust to give people the full weekend to vote, nominate, etc...18:16
jamesmcarthurAnd puts our communications on target for first thing of the work week.18:17
VWOK, so 29th - 11th for noms18:17
VW12 - 18th for election18:17
mrhillsman++18:17
VWpublish/announce results on 19th?18:17
jamesmcarthur+118:17
VWgroovy.  We'll most likely be discussing again next week (and the weeks after), but in the spirit of getting through the agenda, anything else election related?18:18
VWwill take silence as OK to move on :)18:19
mrhillsmanwhat i can do to help is modify the links tom provided (non election official related) to be generic so they can be ready to go out18:19
VW#action mrhillsman to update links provided by Tom18:20
mrhillsmancreate a sub wiki page for how to do elections18:20
VWlove it18:20
mrhillsmanand add them to it, idk, something to make it easier next time ;)18:20
mrhillsmancool18:21
mrhillsmannothing more from me18:21
zioprotoshould this be a wiki page, or some Markdown text in the governance wiki repo ?18:21
zioprotogovernance git repo18:21
*** emagana has joined #openstack-uc18:21
mrhillsmani'll just wiki it for now until UC signs off18:21
mrhillsmanthen i think that totally makes sense zioproto18:21
zioprotook, I mean here: https://github.com/openstack/governance18:22
mrhillsmanbut UC can decide later, just want to capture it for some future proofing18:22
zioprotosure18:22
VWagreed.  OK - let's keep rolling.  Still have lots to cover.  We'll revisit elections next week18:22
VW#topic PTG goals18:23
*** openstack changes topic to "PTG goals (Meeting topic: uc)"18:23
VWdo we have any :)18:23
VWI think mrhillsman is our lone UC rep18:23
mrhillsmanunfortunately i will not make it to the ops meetup in Tokyo but will be at PTG18:23
mrhillsmanthis was tied to that but if we can/do have some for ptg, i can still push them18:24
jamesmcarthurI'm not a UC member, but I will be at the PTG if I can assist at all.18:24
mrhillsmanemagana did mention something from our meeting so i will have to go back and review18:25
jamesmcarthurHappy to represent interests if there are relevant topics to weigh in on.18:25
lsellsmall aside, there will be an in person board meeting at PTG either Sunday or Monday, so would be good to have UC representation there18:25
VWyes - that ^18:25
mrhillsmanyeah, that also18:25
jamesmcarthurOne thing I think we should consider from the UC perspective is the Release Cycle18:25
VWwould love to be present, but seriously doubt I'll talk anyone here into letting me go18:25
mrhillsmanwell, we have webex, though in person is better18:25
lsellPTG travel support deadline is January 25th!18:26
mrhillsmani can lead this piece VW since i will be present18:26
mrhillsmanspeaking of which, does UC get a complimentary ticket to the PTG?18:26
mrhillsmani got a code last time but i think it was because of atc18:27
mrhillsmanother than that i am set to be in there18:27
lsellthat's a good question. we'll check. basically the PTG is $100, but if you attend, you get a free summit code18:27
jamesmcarthurATCs don't get a free PTG pass. Otherwise, we wouldn't be able to pay for the event ;)18:27
mrhillsmanah ok, thought it was more, let me know and i will work it out :)18:28
mrhillsmanvery true jamesmcarthur18:28
mrhillsmani may have paid last time, but anywho, i'll be there18:28
mrhillsman#action mrhillsman create draft UC presentation for joint meeting at PTG18:28
mrhillsmani'll email everyone the draft and ask for feedback on extra items outside of the joint meeting18:29
VWsounds great18:29
VWok - anything else PTG related?18:30
zioprototalking about the PTG. I was shocked how the ops community pushed to keep the ops midcycle far and separated from the PTG. It looks to me it was a move to have the ops identity stronger recognized. But it is also a sign of two groups in the broader community. I just wanted to share this thought.18:30
mrhillsmanmaybe that sounded a bit much, i'll draft the initial outline based on past stuff with generic items we discuss and we can work on specifics we would like to carry18:30
mrhillsmani think that fits in next topic well zioproto18:31
VWyeah18:31
zioprotoI think something we can organize at the PTG is a session on tools for user involvement. Starting from opening a ticket correctly on Launchpad with the correct tags.18:32
zioprotoSomething that I see is missing is how devs get feedback from users in design thigs18:32
zioprotodo you see Matt Riedmann emails on :"what about if we do this"18:32
zioprotoI think a tool to collect that feedback is better then email on mailing lists18:32
zioprotoI am thinking of something like mini-survey18:33
zioprotoso when I dev is not sure if a change is really users-supported or user-important, can use this tool to get the feedback18:33
jamesmcarthurzioproto: Right, part of the problem we have now is that most users don't know how to get engaged, especially wouldn't think to come to the dev mailing list.18:33
mrhillsmantopic change?18:33
jamesmcarthurzioproto: getting them to StoryBoard (since we're moving off of launchpad) is a solid idea.18:33
mrhillsmanjust for log purposes18:34
zioprotojamesmcarthur: yes, that is a great thing. I did not into storyboard my self. Maybe I should start myself :)18:34
lsellI think this leads into the bigger strategic initiatives for the user committee and probably a bigger planning session...how can you branch out beyond the 1% of operators who are currently actively involved and reach more users, connect them and get their feedback into the community?18:34
zioproto#action: zioproto look into storyboard with the longer term goal of spreading the adoption of the tool18:35
mrhillsman#topic Including regional meet-up groups/work with Ambassadors18:35
*** openstack changes topic to "Including regional meet-up groups/work with Ambassadors (Meeting topic: uc)"18:35
zioprotoHow are we in touch with these Ambassadors ? they are all on the UC mailing list ?18:35
mrhillsmanagree 100% we definitely should have a larger/bigger planning session18:35
mrhillsmaninclude ambassadors?18:36
mrhillsmanas i understand user groups -> ambassadors -> uc should be the ideal flow in a very general sense18:36
emaganaHello! Sorry for late joining but I am finally here!18:36
apricezioproto: typically the ambassadors use the community mailing list, and we also have Sonia at the Foundation who has been working closely with the ambassadors18:37
emaganaI missed everything so far?  :-)18:37
jamesmcarthurSeems like tying these meetups to OpenStack Days is a good opportunity to catch new users and be an easy way to get regional Ambassadors there.18:37
mrhillsmanyeah we have discussed this (not just UC i mean) a few times in the past 6 months18:37
VWagreed, but how can we as a committee guide the output of those meet-up groups/regional meetings into things like forum submissions etc18:38
mrhillsman++18:38
VWI think that is such a useful way for us to bring value to those groups18:39
shamailAnd also leverage them for getting feedback on real-time topics in the upstream community18:39
mrhillsmanyep, i think that is crux18:39
VWtrue shamail18:39
VWafk for 2 minutes18:39
mrhillsmanso seems like we need to dedicate a meeting or two to this?18:39
mrhillsmanmaybe get something started in an asynchronous way so we are not limited to Monday time slots on?18:40
jamesmcarthurCould we organize a UC planning meeting at some point in the near future?18:40
emaganamrhillsman: +218:40
jamesmcarthurIf we set it up a the PTG, would that allow UC committee members easier leeway on travel?18:40
jamesmcarthurIt feels like our time at the Summit was brief and we have a lot of strategic matters to cover.18:41
mrhillsmanagree with you jamesmcarthur18:41
emaganajamesmcarthur: I think so. It helps to justify the traveling.18:41
mrhillsman^18:42
mrhillsmaneven though that window is tight right now18:42
mrhillsmanbut we should/could and if it is too late for some, zoom?18:43
jamesmcarthursure18:43
jamesmcarthurI think real life meetings are helpful...18:43
VWindeed18:43
jamesmcarthurBut I also think the timing (soon) is important18:43
mrhillsmanagreed18:43
VWand if you look at the next two agenda items, there are clearly some very strategic things we have to sort18:44
VWnot just the regional piece18:44
VWbut to roll it all up, how best can we mobilize and advocate for users across the globe - and possibly across many projects of which OpenStack is one18:45
lsell+118:46
mrhillsmanhttps://docs.google.com/document/d/19DhGbvO-WfQKG5MJEUqQ2xfVBFZYjOR8H7JvfQNHUA0/edit18:47
mrhillsmanhttps://drive.google.com/open?id=1cfXkCE1T1zYJLnkY9Heeupbpebo_Pysx < folder18:47
VWso, Time check - we have 14 minutes left.  Do we want to cover specific points of agenda items 5 and 6, or are we shifting to trying to get the band together in person - as early as the PTG18:47
mrhillsmanwe only have a ^18:47
jamesmcarthurGoogle doc is read only mrhillsamn18:47
mrhillsmanfixed, sorry18:48
jamesmcarthurnp18:48
mrhillsmanI think you summed up 4,5,and6 well with your one-liner VW18:48
* VW drops the mic18:49
mrhillsmanwhich we can carry via that document18:49
mrhillsmanlol18:49
emaganaI will discuss with my management team to make the trip to the PTG.18:50
VWOK - so, while everyone is focused on the doc now :P, I'll put on my meeting manager hat and ask if there is anything else we want to cover18:51
mrhillsmani like the key focus18:51
mrhillsmannothing more from me sir18:51
VW#topic Other Business18:51
*** openstack changes topic to "Other Business (Meeting topic: uc)"18:51
VWFoundation folks.  Any other topics you want to cover?18:52
lsellJust wanted to give a heads up that Thierry Carrez posted a blog about spectre and meltdown today and what it means for OpenStack users...if anyone here has thoughts or anything to add, I'm sure he'd welcome it, or we can incorporate into an article for Superuser magazine https://ttx.re/openstack-spectre-meltdown-faq.html18:53
mrhillsmanoh18:53
jamesmcarthurI'll just say hi and that I'll be taking on a new role as a Foundation Liason for the UC and users in general.18:53
mrhillsmanthe summary document18:53
VWargh - just when I thought I'd get through one meeting today that didn't cover that ;)18:53
lsellsorry! :)18:53
mrhillsmanshamail sent out a reminder about the yearly review doc18:54
mrhillsmanjust wanted to be sure to mention that, thx shamail18:54
emagana+118:54
jamesmcarthurI'll be assuming a lot of the duties that Tom did previously. I've already done quite a bit of work with the User Survey and assisting with AUC pieces.18:54
mrhillsmanand apologize that we missed the deadline lsell et al18:54
emaganajamesmcarthur: Thanks James! That will be very helpful for the community18:54
jamesmcarthurIf I can assist y'all in any way, please don't hesitate to reach out.18:55
zioprotolsell: we published this for our openstack users https://help.switch.ch/engines/status/meltdown-spectre/18:55
mrhillsmanreally appreciate it jamesmcarthur and looking forward to working with you more closely18:55
jamesmcarthur(and sorry that I stepped in the middle of the Spectre announcement)18:55
lsellthanks zioproto!18:55
VWno worries jamesmcarthur "stepped in it" and spectre/meltdown go together quite well :D18:56
jamesmcarthurindeed18:56
mrhillsmanhehe18:56
mrhillsmangoing to have to run to another meeting18:56
mrhillsmanttyl18:56
*** shamail has quit IRC18:56
emaganadealing with so much of spectre/meltdown recently...18:57
zioprotobye everyone, thanks for the meeting18:57
emaganawe have to patch both guest and hosts!18:57
VWme too emagana - me too18:57
VWok, I've updated the agenda for next week18:57
emaganaThank you mrhillsman zioproto shamail and VM for leading the conversation!18:57
VWspecifically to add a revisit of the planning meeting.  UC folks, can you try and he thumbs up / thumbs down for travel by then?18:58
emaganaThank you Foundation folks for attending. lsell and jamesmcarthur (I am probably missing folks)   :-(18:58
jamesmcarthuraprice :)18:58
jamesmcarthurThanks all! Happy Monday.18:58
lsellthank y'all!18:58
VWDon't forget US folks - next week is the "early" meeting18:58
VW1400 UTC18:59
mrhillsman++18:59
VWalright, well please add any other agenda items to the wiki if you would like to discuss18:59
VWotherwise, we'll be back here next Monday18:59
VW#endmeeting19:00
*** openstack changes topic to "#openstack-uc"19:00
openstackMeeting ended Mon Jan  8 19:00:08 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-01-08-18.00.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/uc/2018/uc.2018-01-08-18.00.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/uc/2018/uc.2018-01-08-18.00.log.html19:00
VWnow for lunch - finally :)19:00
mrhillsman;)19:00
mrhillsmanafter this meeting19:00
mrhillsmanjason's deli in my future19:00
*** shamail has joined #openstack-uc19:01
mrhillsmanhas anyone heard uberconference hold music?19:02
mrhillsmanit is hilarious19:02
mrhillsmani had to record it and will definitely be uploading19:02
lselljust confirmed the board meeting at the PTG will be on Monday, not Sunday19:24
*** jamesmcarthur has quit IRC19:31
*** VW_ has joined #openstack-uc20:01
*** VW__ has joined #openstack-uc20:03
*** VW_ has quit IRC20:03
*** VW has quit IRC20:05
*** jamesmcarthur has joined #openstack-uc20:38
*** openstack has quit IRC20:38
*** openstack has joined #openstack-uc20:42
*** ChanServ sets mode: +o openstack20:42
*** jamesmcarthur has quit IRC20:54
*** jamesmcarthur has joined #openstack-uc20:54
*** VW__ has quit IRC21:01
*** VW has joined #openstack-uc21:02
*** VW has quit IRC21:06
*** VW_ has joined #openstack-uc21:06
*** jamesmcarthur has quit IRC21:12
mrhillsmanthx lsell21:23
*** jamesmcarthur has joined #openstack-uc22:08
*** jamesmcarthur has quit IRC22:13
*** emagana has quit IRC22:30
*** emagana has joined #openstack-uc22:31
*** emagana has quit IRC22:32
*** emagana has joined #openstack-uc22:38
*** emagana has quit IRC22:39
*** emagana has joined #openstack-uc22:47
*** emagana has quit IRC22:51
*** VW has joined #openstack-uc22:54
*** VW_ has quit IRC22:58
*** VW has quit IRC22:59

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