[openstack-dev] [neutron] What does being a neutron-core member mean? [WAS: Re: [neutron] I am pleased to propose two new Neutron API/DB/RPC core reviewers!]

Russell Bryant rbryant at redhat.com
Fri Aug 14 15:25:43 UTC 2015


While this includes me, I'm really not taking this personally.  I'm
thinking about it in the general sense.

On 08/14/2015 11:03 AM, Kyle Mestery wrote:
>> I'd argue the system is built on a web of trust. If you trust me, and I
>> trust Russell and Brandon, then you should likely trust Russell and
>> Brandon as well. This is EXACTLY what the Lieutenant system was meant to
>> convey, though I now feel like perhaps people missed this key ingredient
>> of the new world we find ourselves in.

This is a huge and important point.  The N to N trust model we've been
operating under doesn't scale.  Neutron is trying to move to a different
trust model that has proven to scale much further than we've been able
to do within a single OpenStack project so far.

If Kyle and others leading a section of Neutron trust me, I'm happy to
jump in and do more reviews.  If they trust me, I'd hope others not as
familiar with me or my work can trust by proxy.  The same applies to
Brandon.  I honestly don't know Brandon very well, but I have a high
level of trust for Kyle.  Kyle trusts him, so +1 from me.

Kyle has a tough role here.  It means he gives up some control, but it's
the way the project will scale.  Kyle doesn't have to develop a close
trust relationship with everyone merging code into the main neutron
repo, much less all the other repos.  He can delegate some of that.  It
only works if everyone buys into this way of thinking.

-- 
Russell Bryant



More information about the OpenStack-dev mailing list