14:02:42 <mrhillsman> #startmeeting uc
14:02:43 <openstack> Meeting started Mon May 14 14:02:42 2018 UTC and is due to finish in 60 minutes.  The chair is mrhillsman. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:02:44 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:02:46 <openstack> The meeting name has been set to 'uc'
14:03:02 <aprice> o/
14:04:30 <mrhillsman> #topic Roll Call
14:04:44 <mrhillsman> agenda btw #link https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Meeting_Agenda.2FPrevious_Meeting_Logs
14:06:18 <mrhillsman> guess everyone is here :)
14:06:33 <jamesmcarthur> Hi :)
14:06:33 <mrhillsman> did we need to add anything else to the agenda?
14:07:05 <aprice> I can cover user survey stuff in other business
14:07:31 <mrhillsman> let's do that first ;)
14:07:46 <mrhillsman> #topic User Survey
14:08:07 <aprice> spotz put it on the ML last week - thank you!
14:08:14 <mrhillsman> ++
14:08:29 <aprice> It is now open until early August so as you meet folks next week, please encourage them to take it
14:08:46 <aprice> If there’s any feedback, please let me and jamesmcarthur know
14:08:57 <aprice> That’s really it - just wanted to close the loop on that.
14:09:07 <aprice> Thank you all for testing!
14:09:53 <mrhillsman> Awesome
14:10:26 <mrhillsman> Thanks again to you and all the folks who maintain and improve this very important tool
14:10:41 <aprice> Np!
14:11:04 <mrhillsman> #topic User Committee Update Deck
14:11:10 <mrhillsman> #link https://docs.google.com/presentation/d/1-xQApxg3xY3jBagID3PO1MCJiFYPaAw8yHmFdtMj8Pc
14:11:32 <mrhillsman> So we have to get this to the team organizing the joint meeting today
14:12:00 <mrhillsman> eumel8 added some items for the last slide
14:12:37 <mrhillsman> it can definitely use more, but if we can quickly review all the others for any obvious issues and fix right now that would be great.
14:13:46 <VW> heyo!
14:13:48 <VW> sorry I'm late
14:13:51 <zioproto> hello
14:13:58 <mrhillsman> hey guys
14:14:06 <spotz> Hey!
14:14:19 <mrhillsman> we are looking at #link https://docs.google.com/presentation/d/1-xQApxg3xY3jBagID3PO1MCJiFYPaAw8yHmFdtMj8Pc
14:14:28 <aprice> One thing on the AUC piece - since the ops midcycle will be integrated into the ptg, should we update that?
14:14:45 <zioproto> sorry I was also late, I opened the link right now
14:14:45 <mrhillsman> first doing a quick glance over to see if there are any glaring issues/changes
14:15:32 <mrhillsman> is that better aprice ?
14:15:52 <mrhillsman> PTG Ops sessions attendees instead of just session moderators (~50)
14:16:02 <aprice> mrhillsman: yeah I think that’s better
14:16:12 <aprice> We can work with the events team on how we want to track that
14:16:21 <mrhillsman> cool
14:17:57 <aprice> I think on the committee goals, next to office hours, you could put that this would make the UC more accessible to new operators or those with questions.
14:18:11 <mrhillsman> so one thing while it is on my brain, i think it would be good to have something folks can easily visualize by berlin on a few of these key things
14:18:19 <aprice> So it can show the why
14:18:30 <aprice> ++
14:18:50 <spotz> +1
14:19:27 <mrhillsman> agreed
14:19:56 <mrhillsman> i was thinking about that, can we qualify some of these
14:20:16 <VW> tweaked a few things on slide 12 and 13
14:22:09 <spotz> vw on 13 I think it should be feedback, PTG, or but I'm not sure if you wanted feedback and ptg grouped
14:22:34 <spotz> aha:)
14:22:53 <VW> thanks!
14:23:37 <spotz> One thing we could do by Berlin which would definitely be visual and meet some of the earlier goals is work with the x,y and z to increase the number of AUC
14:23:44 <mrhillsman> what do you all think about something easily visual...
14:24:12 <mrhillsman> was not sure that comment was caught
14:24:59 <spotz> The 1-3 forum talks is also visual
14:26:09 <VW> yep :)
14:26:13 <spotz> Basically we need stuff that is either quantitative or is us in their face type stuff
14:26:20 <mrhillsman> ++
14:26:52 <jamesmcarthur> Ideally we could measure this by how many UC goals make it into a release cycle
14:27:09 <aprice> The user survey report will be live by Berlin so that can be the source of some content as well as goals / places the UC can help
14:27:11 <jamesmcarthur> But since this is the first time we are doing this, we might have to wait a cycle.
14:27:51 <spotz> yeah this sounds like a building cycle, some progress shown in Berlin and then more of a finished product
14:27:59 <mrhillsman> both of those sound good
14:28:50 <aprice> spotz: ++
14:29:03 <VW> yeah jamesmcarthur - goal one is turn user feedback IN TO priorities in the dev cycle
14:29:18 <VW> step 2 is tracking their completion
14:29:21 <VW> :)
14:29:26 <jamesmcarthur> Aye
14:29:53 <spotz> And each cycle if we can add 1-2 feedbacks and work them through the process
14:30:31 <VW> ++++++++!
14:31:58 <jamesmcarthur> Like this.
14:33:22 <josephrsandoval> +1
14:34:56 <aprice> I honestly think that the combination of the ops midcycle into the ptg is a good first step
14:35:15 <aprice> And a good example to call out in Vancouver
14:35:34 <spotz> Yeah I'm excited to be going especially with the combined groups
14:35:46 <mrhillsman> good note aprice
14:36:24 <spotz> That'd be nice to get slipped into a keynote that the groups will both be at PTG....
14:37:03 <mrhillsman> i was trying to think of what we could do with committee goals slide since it is kind of a bit of what we look at today and what we have been looking at
14:37:23 <zioproto> I have a proposal for goals
14:37:35 <mrhillsman> maybe we could use two columns
14:37:53 <mrhillsman> Current | Identified ?
14:38:19 <spotz> In Progress | Identified?
14:38:23 <mrhillsman> Shrink it down, and add some detail where appropriate, hope that makes sense
14:38:27 <zioproto> Community Emails metrics https://usercontent.irccloud-cdn.com/file/rO7vR5cW/Screen%20Shot%202018-05-14%20at%2016.25.37.png
14:38:28 <mrhillsman> Even better
14:39:07 <zioproto> Looking at Stackalytics it looks like the mailing list are losing people. A goal for the future would be to keep the community interaction above a certain level.
14:39:28 <zioproto> btw, metrics for 2018 for emails seems to be broken or not updated yet
14:39:36 <zioproto> Also bugs graphic is interesting
14:39:41 <mrhillsman> yeah, i think broken maybe
14:40:01 <mrhillsman> i don't recall where but thierry has some numbers re it
14:40:03 <zioproto> Resolved Bugs graph https://usercontent.irccloud-cdn.com/file/0yccOkQ2/Resolved%20Bugs%20graph
14:40:21 <mrhillsman> oh yeah, it is a forum session
14:40:57 <mrhillsman> https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21747/opsdevs-one-community
14:41:32 <zioproto> btw what I want to say is that from the data is clear that the community is facing a moment of decrease in numbers, so as UC we could try to keep the graph at least stable. If the question was what is the posible goal for next year
14:41:33 <mrhillsman> he put this on one of the ML and had some numbers around ML
14:41:34 <spotz> zioproto: I think the only way to appropriately do that is as a percent of emails to the number of active people? Not sure we have the data
14:42:34 <zioproto> spotz: I mean, all metrics are going down. Reviews, commits, emails. It is an indicator that the community is getting smaller. As goal of the UC we should try to keep the community together
14:42:49 <zioproto> I did not want to comment a specific graph
14:42:59 <zioproto> I wanted to give the general idea, supported by numbers
14:43:27 <mrhillsman> ++
14:43:54 <mrhillsman> just a time check, we have about 15 minutes left
14:43:58 <zioproto> I dont know if the contribution to the User Survey is stable as number of people filling the survey, or we have a + or - ?
14:44:16 <aprice> zioproto: in 2017 we had an increase
14:44:52 <aprice> We just opened it for 2018 so that’s why I want to make sure we encourage everyone to complete it - particularly at events where new users may be attending
14:45:35 <spotz> aprice: I'll wear my user survey shirt one day, it's bright orange:)
14:46:02 <VW> there are user shirts?
14:46:04 <aprice> spotz: user survey shirt?!
14:46:06 <VW> :P
14:46:10 <aprice> How have I not seen this? Lol
14:46:23 <spotz> I got in in barcelona for doing the survey:)
14:46:28 <zioproto> aprice: great ! it means that when we push something to the community we get feedback
14:46:44 <spotz> aprice: I'll take a pic and text you it
14:46:51 <zioproto> aprice: I am a little bit more worried about the closed bugs metrics for example :)
14:46:56 <aprice> spotz: nice!
14:47:38 <aprice> zioproto: that makes sense
14:48:05 <mrhillsman> zioproto maybe this is something we can have data on by Berlin?
14:48:26 <zioproto> I guess so
14:48:28 <mrhillsman> so we could work on particular metrics we want to try to gather and report on by then?
14:48:47 <jamesmcarthur> Zoo zioproto
14:48:51 <jamesmcarthur> Doh
14:49:06 <mrhillsman> we can provide what we think are the metrics we should look at and track in vancouver?
14:49:13 <aprice> I think that’s a good idea and will help the board see the tangible results in Berlin
14:49:26 <jamesmcarthur> Zioproto: I think this also plays into the email Thierry sent this morning regarding large scale community goals instead of project specific goals
14:50:03 <spotz> I'm going to have to unpack from Sydney to find it I think:)
14:50:13 <mrhillsman> additionally i believe there may be some insight from the TC as i know Thierry has had some data at least partially relevant to what you are saying
14:50:35 <mrhillsman> in past meetings and i believe Chris Dent does as well
14:51:24 <mrhillsman> i also agree with this being part of community-wide goals and the forum session i mentioned, as well as the item we have about community-wide goals not having user input are related to this possibly
14:51:36 <VW> Yes, jamesmcarthur, we are at a stage where everyone needs to share larger vision for OpenStack as a whole
14:51:49 <mrhillsman> so we can set the stage during the meeting in that regard
14:51:50 <VW> and the individual projects should form their plans around how they help achieve that goal
14:53:35 <mrhillsman> i believe overall zioproto that is essentially what the meeting will entail at a high level
14:53:44 <mrhillsman> there is quite a bit of time dedicated to strategy
14:54:11 <mrhillsman> i think the key is how user community is part of strategy
14:54:42 <spotz> +1
14:54:58 <mrhillsman> commits is more directly tied to tc wheelhouse but we should definitely consider how it ties into ours and bubble that up
14:55:21 <zioproto> +1
14:55:38 <VW> at some point, we should be able to track the number of commits driven by user feedback
14:55:42 <VW> but we have a lot to build to get there
14:55:49 <mrhillsman> i think we can achieve this possibly by doing things like working with ^
14:56:04 <VW> so our goals should be focused on achieving each of the necessary steps along that path
14:56:44 <mrhillsman> ++
14:57:01 <zioproto> looks like we have an idea of possible goals for the future :)
14:57:07 <mrhillsman> we only have a few minutes left
14:57:35 <mrhillsman> i was looking at this the other day #link https://wiki.openstack.org/wiki/ProductTeam
14:57:42 <mrhillsman> which i think is quite relevant to this conversation
14:58:01 <VW> #homework ?
14:58:10 <mrhillsman> in particular #link https://wiki.openstack.org/wiki/ProductTeam/Development_Proposals
14:58:37 <mrhillsman> i think this was viewed bad but could be quite relevant to this context
14:58:59 <mrhillsman> which is what some of the discussions in the product team hinged on before it as shut down
14:59:10 <mrhillsman> i'll go ahead and stop the meeting :)
14:59:15 <mrhillsman> #endmeeting