Monday, 2018-03-19

*** jamesmcarthur has quit IRC00:00
*** jamesmcarthur has joined #openstack-uc00:37
*** VW has joined #openstack-uc01:59
*** ChanServ sets mode: +o VW01:59
*** jamesmcarthur has quit IRC02:20
*** jamesmca_ has joined #openstack-uc02:21
*** VW_ has joined #openstack-uc03:01
*** VW has quit IRC03:03
*** jamesmca_ has quit IRC03:15
*** jamesmcarthur has joined #openstack-uc03:25
*** jamesmcarthur has quit IRC05:13
*** VW_ has quit IRC12:01
*** SnowCrash631 has joined #openstack-uc12:04
*** VW has joined #openstack-uc12:53
*** ChanServ sets mode: +o VW12:53
VWhappy Monday, all13:09
spotzhey WV14:28
*** VW has quit IRC14:43
*** VW has joined #openstack-uc14:43
*** ChanServ sets mode: +o VW14:43
*** VW has quit IRC15:06
*** thingee has quit IRC15:27
*** VW has joined #openstack-uc15:28
*** ChanServ sets mode: +o VW15:28
*** VW_ has joined #openstack-uc15:35
*** VW_ has quit IRC15:35
*** VW_ has joined #openstack-uc15:36
mrhillsmano/15:38
*** VW has quit IRC15:38
*** VW__ has joined #openstack-uc15:38
*** VW_ has quit IRC15:38
*** ChanServ sets mode: +o mrhillsman15:39
spotzhey mrhillsman15:39
*** VW has joined #openstack-uc15:45
*** ChanServ sets mode: +o VW15:45
*** VW__ has quit IRC15:45
*** VW has quit IRC16:22
*** VW has joined #openstack-uc16:22
*** ChanServ sets mode: +o VW16:22
*** VW has quit IRC16:23
*** VW has joined #openstack-uc16:24
*** ChanServ sets mode: +o VW16:24
*** VW has quit IRC16:28
*** VW has joined #openstack-uc16:38
*** ChanServ sets mode: +o VW16:38
*** VW_ has joined #openstack-uc16:39
*** VW_ has quit IRC16:39
*** VW_ has joined #openstack-uc16:39
*** VW has quit IRC16:43
*** VW_ has quit IRC16:47
*** VW has joined #openstack-uc16:48
*** ChanServ sets mode: +o VW16:48
*** VW has quit IRC16:48
*** VW has joined #openstack-uc16:49
*** ChanServ sets mode: +o VW16:49
*** jamesmcarthur has joined #openstack-uc16:55
VWhey folks - I have a video meeting at work that is conflicting with the first 30 minutes of ours that I can't move or get out of17:35
VWI'll be a bit silent for the first half of the UC meeting17:35
*** VW_ has joined #openstack-uc17:43
*** VW_ has quit IRC17:44
*** VW_ has joined #openstack-uc17:44
*** VW has quit IRC17:46
*** Ingenium844 has joined #openstack-uc17:48
spotzno prob VW17:51
*** leong has joined #openstack-uc17:57
*** ChanServ sets mode: +o leong17:57
*** ashferg has joined #openstack-uc18:00
apriceo/18:01
mrhillsmano/18:02
spotzhey18:02
mrhillsman#startmeeting uc18:02
openstackMeeting started Mon Mar 19 18:02:08 2018 UTC and is due to finish in 60 minutes.  The chair is mrhillsman. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
jamesmcarthuro/18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: uc)"18:02
openstackThe meeting name has been set to 'uc'18:02
mrhillsman#chair VW zioproto spotz leong18:02
openstackWarning: Nick not in channel: VW18:02
openstackCurrent chairs: VW leong mrhillsman spotz zioproto18:02
mrhillsmanthx VW_18:02
mrhillsmansorry for being so abrupt :)18:02
mrhillsman#topic RollCall18:03
*** openstack changes topic to "RollCall (Meeting topic: uc)"18:03
spotzo/18:03
*** VW_ is now known as VW18:03
mrhillsmanAgenda #link https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee18:03
VWo/ (sort of)18:03
mrhillsmanwill give a minute or two more for others18:04
leongo/18:04
apriceo/18:05
ashfergo/18:05
leongi have to drop in 30 mins for another meeting.. my apoloyg.18:05
leongsorry that i can't attend last week meeting...18:05
mrhillsmanthx leong18:06
mrhillsman#topic User Survey Changes18:06
*** openstack changes topic to "User Survey Changes (Meeting topic: uc)"18:06
mrhillsmandid you have anything you wanted to cover aprice18:06
apricenot right now - I am working on an email to you all about the changes. jamesmcarthur and I will be working through some of the changes this week18:07
mrhillsmanawesome, thx18:07
apriceso that we can begin promoting in April - I will keep the group updated as we move forward :)18:07
apriceone thing....18:07
apriceat the end of the User Survey, we have PTL specific questions and lsell thought it would be a good idea to get feedback around extended maintenance adn release cycle.18:08
spotzThat would be a good ides18:08
apriceSo we will share a draft of that question with the UC before including, but wanted to give yall a heads up since that has been a big topic lately.18:08
apricebut other than me needing to send yall info, there's nothing new to cover :)18:09
mrhillsmancool18:09
mrhillsmanthere is a TC resolution pretty close to being ratified re EM18:09
mrhillsmanwill be interesting to see responses18:09
apriceoh cool18:09
mrhillsman#link https://review.openstack.org/#/c/548916/18:10
mrhillsmanin case anyone does not have18:10
leongWe probably should send out that link to UC-mailling list to encourage operator feedback on that gerrit18:11
mrhillsmanit has gone out at least 3 times18:11
mrhillsmanthierry once, myself twice18:12
mrhillsmancan definitely do it again though18:12
mrhillsmanespecially since it looks like thierry called for a formal-vote18:12
mrhillsmanafter discussion has been taking place for a couple weeks18:13
mrhillsmananything else on the User Survey?18:13
apricethat's all from me18:13
mrhillsman#topic Formalize UC position on Ops Meet-ups based on PTG discussion output18:14
*** openstack changes topic to "Formalize UC position on Ops Meet-ups based on PTG discussion output (Meeting topic: uc)"18:14
mrhillsmani do not remember what this was re specifically18:14
jamesmcarthurSo...18:14
jamesmcarthurI can probably address this. We're talking about co-locating the Ops Meetup at the PTG.. However, we need to get buy-in from the folks that manage these meetups.18:15
mrhillsmanah ok18:15
jamesmcarthurAnne Bertucio went as a Foundation rep and there is a lot of resistance to the idea.18:15
mrhillsmani remember that discussion :)18:15
jamesmcarthurA lot of it is simply a language issue - like it's called teh PTG, not the Ops/PTG meetup18:16
jamesmcarthurI'm currently working on an email that I was going to float to mrhillsman and VW for review18:16
mrhillsman++18:16
spotzPTG was always a strange name though18:16
jamesmcarthurAnd I'd like to put it in front of a handful of ops to see if we can get buyin.18:16
VWsounds good18:16
jamesmcarthurI don't think we're quite ready to post to the operators list yet, but that would be the ultimate goal.18:17
jamesmcarthurThe only real catch here is, we need a decision pretty quickly for the September PTG. We have to have a decision by April 4.18:17
leongwasn't there a comment that the schedule can be very squeezy if both Ops and PTG are on the same week?18:17
VWyeah jamesmcarthur - we can definitely start socialize it with the Meetup team when you are ready18:17
jamesmcarthurleong: yes, it was discussed. I think there is enough downtime later in the week that we can void that.18:18
jamesmcarthurThe idea would be that Ops and Devs meet in separate rooms, with only a day overlap between the two.18:18
jamesmcarthuravoid not void18:18
mrhillsmani think from talking with VW that keeping the days events and local meetups as primary places of general discussion, "PTG" as place to work on stuff and have space/overlap to socialize18:18
leongi think there are always good and bad to collocate Ops and PTG , but the logistic might be tough..18:18
jamesmcarthurleong: i think it's wroth trying in an effort to bridge the divide b/w Ops and Devs18:19
spotzLarger numbers would reduce the overhead for both things though18:19
leongmy undestanding is the core-developers will be busy with their Project and cross-project discussion.. not sure how another Ops session can fit into their already-packed schedule within that week18:19
jamesmcarthursometimes just people sharing dinner and laughs goes a long way to helping build community18:19
spotz+118:19
aprice++18:19
leongjamesmcarthur: i totally agree... i am not opposing:-)18:19
mrhillsmanin my experience i look at a thing like monitoring - i have said this more than one :) - as discussion that happens at midcycle, but no actual "work" for the ops/end-users/app-devs at large comes out of it18:19
jamesmcarthurleong: I don't think the current Ops meetups really get any (or very very few) core developers18:19
jamesmcarthurSo this would at least put them in reach18:20
leongi am just thinking how is that going to structure..definitely need to bridge ops and devs18:20
VWyeah - the logistics get a little dicy18:20
VWbut the PTG could use a few more folks to help pay for it18:20
mrhillsman++18:20
VWand the Ops mid-cycle could use more love from the Foundation18:20
jamesmcarthurVW: leong: the good news here is we get the advantage of using our super smooth Events team from the Foundation :)18:20
leongi would like to give that a try... and see how to improve that...18:20
VWso practically speaking, this helps both issues18:20
spotzI think it'll come down to how it's presented and what it's called18:21
VWI was one of the folks who originally opposed, but I have come around ;)18:21
jamesmcarthurIt might be a dramatic failure, but I have a feeling, based on attending 2 PTGs, that it would be a successful event.18:21
VWtrue spotz18:21
VWwords are hard18:21
jamesmcarthurspotz: ++18:21
mrhillsmanspotz: ^18:22
jamesmcarthurI'm currently writing an encyclopedia to send out to explain it18:22
VWcool18:22
VWhappy to review whenever you think it's ready for that18:22
mrhillsmanfrom a practical perspective i know there are devs at the PTG who would love to work on ops things18:22
mrhillsmanwe tend to get some excited parties after the midcycle18:22
mrhillsmanit has gone down imho from the first one i attended18:23
leongso is that something aiming to collocate PTG/Ops in 2019? or the next PTG?18:23
spotzI haven't made it to a PTG yet:(18:23
jamesmcarthurleong: ideally the next PTG, but it's really up to the Ops organizers18:23
jamesmcarthurWhich kind of brings up a side point...18:23
jamesmcarthurThat IMHO, the UC should consider what its involvement is in these meetups.18:24
jamesmcarthurRight now, they exist outside of governance. I'm not saying they must be governed, but based on all the other items we've been discussing...18:24
jamesmcarthurit's worth considering how we structure these things, along with Ambassadors, User Group Leaders, and OpenStack Days18:25
ashfergand we’re also planning a Forum session for all of these groups18:26
ashfergWe’re also planning to hold a 90-minute session at the Forum with User Group Leaders and Ambassadors to shape goals for the next year. I created an etherpad to collect ideas and topics for the session, so please feel free to contribute, and I’ll follow up with exact timing, because it would be great to have UC representation there.18:26
ashferg#link https://etherpad.openstack.org/p/YVR-UG-Ambassador18:27
spotzThanks ashferg I'll definitely try to get there18:27
VW"because it would be great to have UC representation there" - s/great/damn near required :)18:27
mrhillsman^18:27
aprice:)18:27
ashferg++ :)18:27
leongashferg: i will try to be there if my "travel document" is approved :)18:27
apriceVW: subtlety ya know :)18:28
mrhillsmanpreface - words are hard (VW) - but essentially it is the basis of my concern - trying to be pragmatic about things18:28
VWtotally18:28
mrhillsmanboiling down to some very simple deliverables and avoid complexity18:28
* leong got to drop..will check irc logs offline18:28
mrhillsmanthx leong18:28
*** leong has left #openstack-uc18:29
spotzI think it'll be another summit where the only presentation I make it to are those I'm giving or supporting from the audience:)18:29
VWI just think the UC see has so much opportunity to create a repeatable way to get user discussion turned in to changes in software behavior18:29
mrhillsman^18:29
jamesmcarthur++18:29
mrhillsmanand additional tooling18:29
VWand the more we commit ourselves to all of these things, the better we will be at that18:29
spotzAnd there's so much stuff that can be shared between groups which probably isn't18:29
jamesmcarthuryes!18:29
VWyeah - spots - I gave up on summit talks in lieu of design/forum sessions a long time ago.  So much work to be done... :)18:30
mrhillsmando/can we have any action items today?18:30
VWsorry spotz not spots18:30
mrhillsmansame here VW18:30
spotzhehe VW, it's ok one of the spotted wonders is asleep on my fet18:31
mrhillsmanoh, speaking of forum, we need to hound people about sessions :)18:31
*** leong has joined #openstack-uc18:31
*** ChanServ sets mode: +o leong18:31
VWI think at least you and I have to be ready to quickly review and provide feedback on jamesmcarthur's encyclopedia18:31
mrhillsmanthe formal tool according to the schedule should open today18:31
mrhillsmanneed to checking with mike p18:31
mrhillsmans/checking/check18:31
spotzI emailed and got an etherpad going for the Diversity WG, I'll see about getting one going for WoO too18:31
mrhillsmaneyes and fingers are ready jamesmcarthur18:32
jamesmcarthurok - my editors are reviewing mrhillsman ;)18:32
spotzJust be nice to ops, we tend to feel second class:(18:32
jamesmcarthurspotz: yeah, we're trying hard to focus on that18:33
mrhillsmananything else here? i think we essentially are going to wait for the output from jamesmcarthur and review then circulate and everyone understands the discussion/concern18:34
spotzI think we're good18:35
VWwhat's interesting spotz, is the foundation has been pushing for some time now to have Ops/users drive much more of the priority.  No one is really first/second class, but the reality is that we have gone from a world where "hey this is a cool project to dev on" to "hey, people use this @#$% and we should listen to what they have to say about it"18:35
mrhillsman++18:36
spotzThat's why I think combining is a great idea, get the people in the same room18:36
VWyes, but we also need to make sure we honor the intent for the type of work18:37
VWthe forum is still the best place to get everyone in the same room and have them focus on WHAT the software should do18:37
mrhillsmanagreed spotz - personally i think we want to help reduce talking to working ratio18:37
mrhillsman++ VW18:37
VWwe need to keep some dev focused activities at the PTG (or what ever we call it) so they can focus on HOW to make the code do that18:37
mrhillsmanForum, OpenStack Days, Local User Groups18:38
VWbut having the ops and devs in the location at the "PTG" can still reap many bennifits18:38
spotzWe just need to get the groups to submit topics!18:38
mrhillsman"PTG" (newly named/branded) - work :)18:38
spotzOpenStack Community Working Midcycle!18:38
mrhillsmanand we can help there too spotz18:38
spotzKeywords added for travel approvals:)18:39
VWmrhillsman: you can action me to go over the little bit of feedback from Tokyo to see if there is a "quick win" for submitting something to the Vancouver forum18:39
mrhillsmanlast year i reached out to a lot of the local user groups18:39
VWBerlin is still our main goal for the "new" process, but I'd love to score some quick points and advertise the heck out of it if we can18:39
mrhillsman#action VW go over Tokyo feedback for some Forum "quick wins"/sessions18:39
VW"hey Ops - you talked about X.  Look - we are turning that into action..."18:39
mrhillsmani think also we may end up finding sessions we need to have use more than one slot18:40
spotzYeah if we can turnaround and get something in from Tokyo I think it would be a big win18:40
VWand ashferg, it would be great if we could help set the agenda, topics for the big session you described above18:41
mrhillsmancould be worthwhile considering the format/planning of the Forum as well at some point18:41
ashfergVW absolutely. would love y’all’s help with that18:41
mrhillsmanlike wrap up sessions for x project(s) at the end in prep for "ptg" or "x event"18:42
VWyeah - but that to me will depend on a lot on the overall plan for number of events per year - summits and ptgs - which all sounds very TBD after the fall18:42
jamesmcarthurVW: we're definitely planning ot provide a framework for these discussions. I would consider them separate from normal forum sessions And we're also planning on doing the same sessions in Berlin.18:42
VWtotally jamesmcarthur18:42
mrhillsman#topic Open Discussion18:44
*** openstack changes topic to "Open Discussion (Meeting topic: uc)"18:44
mrhillsmanso we have 15 minutes left :)18:44
mrhillsmanopen mic18:44
jamesmcarthurI just flew in from LA and boy are my arms tired.18:46
mrhillsmanlol18:46
spotzoh boy....18:46
mrhillsmanso on jamesmcarthur's bad joke18:46
mrhillsmanseems like we can reclaim some time?18:47
spotzYeah18:47
mrhillsman#endmeeting18:47
*** openstack changes topic to "Open Discussion (Meeting topic: uc)"18:47
openstackMeeting ended Mon Mar 19 18:47:32 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/uc/2018/uc.2018-03-19-18.02.html18:47
mrhillsmanthx everyone!18:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/uc/2018/uc.2018-03-19-18.02.txt18:47
openstackLog:            http://eavesdrop.openstack.org/meetings/uc/2018/uc.2018-03-19-18.02.log.html18:47
*** leong has quit IRC18:48
*** jamesmcarthur has quit IRC18:48
*** ashferg has quit IRC18:48
*** VW has quit IRC18:58
*** VW has joined #openstack-uc18:58
*** ChanServ sets mode: +o VW18:58
*** VW has quit IRC19:00
*** VW has joined #openstack-uc19:00
*** ChanServ sets mode: +o VW19:00
*** VW has quit IRC19:01
*** VW has joined #openstack-uc19:02
*** ChanServ sets mode: +o VW19:02
*** VW has quit IRC19:40
*** VW has joined #openstack-uc20:00
*** ChanServ sets mode: +o VW20:00
*** VW has quit IRC20:34
*** VW has joined #openstack-uc20:35
*** ChanServ sets mode: +o VW20:35
*** VW has quit IRC20:35
*** VW has joined #openstack-uc20:35
*** ChanServ sets mode: +o VW20:35
*** VW has quit IRC22:15
*** VW has joined #openstack-uc22:16
*** ChanServ sets mode: +o VW22:16
*** VW_ has joined #openstack-uc22:18
*** VW has quit IRC22:21
*** VW_ has quit IRC22:23

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