14:08:04 <nikhil_k> #startmeeting Glance Drivers'
14:08:05 <openstack> Meeting started Tue Jun 23 14:08:04 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:08:07 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:08:10 <openstack> The meeting name has been set to 'glance_drivers_'
14:08:24 <sigmavirus24> o/
14:08:40 <nikhil_k> #topic agenda
14:08:43 <nikhil_k> #link https://etherpad.openstack.org/p/glance-drivers-meeting-agenda
14:09:34 <nikhil_k> As we are a bit late, may be we can quickly discuss "Who we are?" part
14:09:56 <nikhil_k> Otherwise, I have listed 3 specs that need our attn soon
14:10:09 <nikhil_k> #topic Identity
14:10:25 <nikhil_k> #info current Glance Drivers: Brian Rosmaita, Ian Cordasco, Flavio Percoco, Nikhil Komawar
14:10:58 <nikhil_k> I have listed interests to gather some feedback on whether we need all features covered
14:11:34 <nikhil_k> Guess there was some feedback to merge drivers and core, that may cover this aspect
14:11:52 <nikhil_k> My questions are:
14:12:03 <sigmavirus24> Yeah, I'm not 100% sold on merging cores and drivers, but I don't think more drivers will hurt
14:12:35 <nikhil_k> 1. How do we ensure that Drivers are actually driving the project forward
14:12:44 <nikhil_k> 2. How we do balance assignments?
14:13:03 <nikhil_k> 3. Does merging them not add overhead to the responsibility and restrict scaling up cores?
14:13:41 <nikhil_k> 4. With growing interest of glance_Store in community, how do we ensure that cores in that repo are actually drivers for glance?
14:13:50 <nikhil_k> (we will have separate list anyways)
14:14:54 <nikhil_k> 5. Who would take action items for specific features and take to other meetings? Do liaisons fit more there? Should we include active liaisons in drivers in that case (and not all cores) ?
14:15:10 <nikhil_k> </done_for_now>
14:15:54 <sigmavirus24> 1. By removing drivers who aren't actually driving the project forward?
14:16:12 <sigmavirus24> 2. Round-robin assignment if no one steps up to drive that spec
14:16:35 <sigmavirus24> 3. Yes it does. But I think we need more sub-team cores anyway. I'm not sure if we want sub-team drivers too though.
14:16:53 <sigmavirus24> 4. I think that is why we don't want all cores to always be drivers for Glance
14:17:41 <sigmavirus24> In general, the way I see Keystone behaving, is that drivers are people who are both active in the community and can understand the needs of users really well
14:18:17 <sigmavirus24> I think for a long time Brad Topol was just a driver and was working with CERN, IBM, Rackspace, etc. to determine the needs that Keystone users have
14:18:35 <sigmavirus24> Other drivers worked with the projects to determine what was necessary
14:19:00 <sigmavirus24> I'm not sure we need to emulate that exactly, but I think it's clear that it's worked well for Keystone
14:19:15 <nikhil_k> makes sense
14:19:20 <nikhil_k> .. Users, operators, developers, interest & contributing companies et. al. right?
14:19:54 <nikhil_k> (or a sub set of the above)
14:20:41 <nikhil_k> I guess that moves us smoothly into next topic
14:20:44 <nikhil_k> #topic How to get involved?
14:21:12 <flaper87> ah damn, so, we're having the meeting
14:21:15 <nikhil_k> #info 1. Provide feedback on specs, code, releases, bugs
14:21:26 <nikhil_k> flaper87: :) I thought your name woud be hilighted
14:21:41 <nikhil_k> (vs. nick)
14:22:41 <sigmavirus24> nikhil_k: perhaps we need to add some documentation around how drivers get involved and are selected based on these minutes :D
14:22:47 <nikhil_k> #info 2. Attend meetings, show up on irc once in a while to answer quetsions, provide feedback on ML
14:22:58 <nikhil_k> sigmavirus24: absoultely :)
14:23:15 <nikhil_k> I was hoping to get some intial feedback and then work on wiki like Nova has
14:24:00 <sigmavirus24> ah, nice
14:24:02 <nikhil_k> #info 3. Contribute to code, documentation, etc enhancements
14:24:22 * flaper87 will like to discuss the core+drivers thing again, we can do that in our next meeting
14:24:27 <flaper87> would likE*
14:24:47 <flaper87> +1 for documenting how to get involved
14:24:49 <nikhil_k> flaper87: sure, I am not around. we can discuss the week after? and in the mini-summit (with all remote folks)?
14:25:01 <flaper87> nikhil_k: sounds perfect
14:25:04 <nikhil_k> cool
14:25:27 <nikhil_k> any more input on the currently set topic?
14:25:42 <nikhil_k> please \#info it
14:26:09 <flaper87> #info discuss specs in the open/m-l to get people interested
14:26:18 <nikhil_k> ++
14:26:21 <flaper87> I didn't enumerate it
14:26:27 <nikhil_k> np
14:26:34 <flaper87> :(
14:26:37 * flaper87 likes numbers
14:26:41 <flaper87> :P
14:26:43 <sigmavirus24> #info Review existing specs and provide useful feedback
14:26:53 * sigmavirus24 doesn't enumerate his so flaper87 doesn't seem like an outcast
14:27:06 * flaper87 hughs sigmavirus24
14:27:18 <flaper87> hugs
14:27:20 <sigmavirus24> I like the qualifier of useful mostly because someone could just +1 each spec and say "Looks godo to me!"
14:27:23 <sigmavirus24> You can Hugh me too
14:27:32 <flaper87> :D
14:27:47 <nikhil_k> #info Pick up any backlog items and help project move forward in that direction
14:27:53 <sigmavirus24> I think we want drivers who can notice architecture burdens/problems
14:28:04 <sigmavirus24> Yep
14:28:07 <nikhil_k> nice
14:28:18 <sigmavirus24> I tried to go through a bunch of old specs on the plane to Liberty
14:28:24 <nikhil_k> :)
14:28:32 <flaper87> "on the plane to liberty"
14:28:37 <sigmavirus24> Didn't want to just abandon things though
14:28:41 <sigmavirus24> *to the liberty summit
14:28:58 <sigmavirus24> flaper87: are you happy now hugh?
14:29:00 * flaper87 will forward that to sigmavirus24's wife (or future wife)
14:29:07 <sigmavirus24> flaper87: lol
14:29:21 <nikhil_k> I will move on in the interest of time
14:29:24 <sigmavirus24> is this what you're going to use to blackmail me into working on zaqar or rust?
14:29:25 <nikhil_k> #topic Priority Specs
14:29:35 <nikhil_k> #action review https://review.openstack.org/#/c/192926/
14:29:42 <flaper87> sigmavirus24: damn, you're smart! :S
14:29:43 <nikhil_k> #action review https://review.openstack.org/#/c/191542/
14:29:50 <nikhil_k> #action review https://review.openstack.org/#/c/188050/
14:29:55 <sigmavirus24> Oh yeah, I need to finish that
14:29:57 <sigmavirus24> :X
14:30:36 <nikhil_k> We should revisit them next week to ensure that e are actually making progress there
14:30:46 <nikhil_k> and I guess we are out of time for today
14:30:46 <sigmavirus24> Agreed
14:30:51 <sigmavirus24> Thanks nikhil_k !
14:30:53 <flaper87> roger
14:30:55 <flaper87> !
14:30:57 <flaper87> thanks
14:30:59 <nikhil_k> Thanks all!
14:31:02 <nikhil_k> #endmeeting