<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 21, 2016, at 10:38 AM, Steven Dake (stdake) <<a href="mailto:stdake@cisco.com" class="">stdake@cisco.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<div class="">Armando,</div>
<div class=""><br class="">
</div>
<div class="">I apologize if neutron does not have a limit of 2 core reviewers per company – I had heard this through the grapevine but a google search of the mailing list shows no such limitation.</div></div></div></blockquote><div><br class=""></div><div>It goes back to what Armando mentioned. If I don’t trust my fellow core reviewers, for *whatever reason*, we have much bigger problems than company affiliation.</div><div><br class=""></div><div>I was told when I joined that the same company shouldn’t +2/+2/+A, which I follow, but even then, it’s a judgement call. I mean, who cares if the same company merges proposal bot? I certainly don’t. Nor would I think ill of it even for a second for a gate fix or the like.</div><div><br class=""></div><div>It’s usually pretty obvious when one entity is trying to shove something in to the detriment of the project. And I’d rather just have a conversation with those folks at the time, and deal with the social problem, rather than trying to pass a million bureaucratic rules to cover every what-if. It’s not that I like having difficult conversations; I just like a world with a million little rules even less.</div><div><br class=""></div><div>doug</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<div class=""><br class="">
</div>
<div class="">Regards</div>
<div class="">-steve</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<span id="OLK_SRC_BODY_SECTION" class="">
<div style="font-family: Calibri; font-size: 11pt; text-align: left; border-width: 1pt medium medium; border-style: solid none none; padding: 3pt 0in 0in; border-top-color: rgb(181, 196, 223);" class="">
<span style="font-weight:bold" class="">From: </span>"Armando M." <<a href="mailto:armamig@gmail.com" class="">armamig@gmail.com</a>><br class="">
<span style="font-weight:bold" class="">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" class="">openstack-dev@lists.openstack.org</a>><br class="">
<span style="font-weight:bold" class="">Date: </span>Sunday, February 21, 2016 at 9:38 AM<br class="">
<span style="font-weight:bold" class="">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" class="">openstack-dev@lists.openstack.org</a>><br class="">
<span style="font-weight:bold" class="">Subject: </span>Re: [openstack-dev] [kolla] discussion about core reviewer limitations by company<br class="">
</div>
<div class=""><br class="">
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;" class="">
<div class="">
<div class="">
<div dir="ltr" class=""><br class="">
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On 20 February 2016 at 12:58, Steven Dake (stdake) <span dir="ltr" class="">
<<a href="mailto:stdake@cisco.com" target="_blank" class="">stdake@cisco.com</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap: break-word; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<div class="">Neutron, the largest project in OpenStack by active committers and reviewers as measured by the governance repository teamstats tool, has a limit of 2 core reviewers per company. They do that for a reason. I expect Kolla will grow over time (we are about
1/4 their size in terms of contributors and reviewers). I believe other projects follow a similar pattern besides Neutron that already have good diversity (and intend to keep it in place).</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">Where did you find this information? I do not believe this is true. I agree wholeheartedly with Joshua: I personally value the judgement of the people I trust rather than looking at affiliation. </div>
<div class=""> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap: break-word; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<div class=""><br class="">
</div>
<div class="">Regards</div>
<div class="">-steve</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<span class="">
<div style="font-family: Calibri; font-size: 11pt; text-align: left; border-width: 1pt medium medium; border-style: solid none none; padding: 3pt 0in 0in; border-top-color: rgb(181, 196, 223);" class="">
<span style="font-weight:bold" class="">From: </span>Gal Sagie <<a href="mailto:gal.sagie@gmail.com" target="_blank" class="">gal.sagie@gmail.com</a>><br class="">
<span style="font-weight:bold" class="">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank" class="">openstack-dev@lists.openstack.org</a>><br class="">
<span style="font-weight:bold" class="">Date: </span>Saturday, February 20, 2016 at 10:38 AM<br class="">
<span style="font-weight:bold" class="">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank" class="">openstack-dev@lists.openstack.org</a>><br class="">
<span style="font-weight:bold" class="">Subject: </span>Re: [openstack-dev] [kolla] discussion about core reviewer limitations by company<br class="">
</div>
<div class="">
<div class="h5">
<div class=""><br class="">
</div>
<blockquote style="BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0 0 5" class="">
<div class="">
<div class="">
<div dir="ltr" class="">I think setting these limits is wrong, some companies have more overall representation then others.
<div class="">The core reviewer job should be on a personal basis and not on a company basis, i think the PTL of each project needs</div>
<div class="">to make sure the diversity and the community voice is heard in each project and the correct path is taken even if</div>
<div class="">many (or even if all) of the cores are from the same company.</div>
<div class="">If you really want to set limits then i would go with something like 2 cores from the same company cannot +2 the same patch, but </div>
<div class="">again i am against such things personally..</div>
<div class=""><br class="">
</div>
<div class="">Disclaimer: i am not personally involved in Kolla or know how things are running there.</div>
</div>
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On Sat, Feb 20, 2016 at 7:09 PM, Steven Dake (stdake) <span dir="ltr" class="">
<<a href="mailto:stdake@cisco.com" target="_blank" class="">stdake@cisco.com</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap: break-word; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<div class="">Hey folks,</div>
<div class=""><br class="">
</div>
<div class="">Mirantis has been developing a big footprint in the core review team, and Red Hat already has a big footprint in the core review team. These are all good things, but I want to avoid in the future a situation in which one company has a majority of core
reviewers. Since core reviewers set policy for the project, the project could be harmed if one company has such a majority. This is one reason why project diversity is so important and has its own special snowflake tag in the governance repository.</div>
<div class=""><br class="">
</div>
<div class="">I'd like your thoughts on how to best handle this situation, before I trigger a vote we can all agree on.</div>
<div class=""><br class="">
</div>
<div class="">I was thinking of something simple like:</div>
<div class="">"1 company may not have more then 33% of core reviewers. At the conclusion of PTL elections, the current cycle's 6 months of reviews completed will be used as a metric to select the core reviewers from that particular company if the core review team has
shrunk as a result of removal of core reviewers during the cycle."</div>
<div class=""><br class="">
</div>
<div class="">Thoughts, comments, questions, concerns, etc?</div>
<div class=""><br class="">
</div>
<div class="">Regards,</div>
<div class="">-steve</div>
<div class=""><br class="">
</div>
</div>
<br class="">
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class="">
</blockquote>
</div>
<br class="">
<br clear="all" class="">
<div class=""><br class="">
</div>
-- <br class="">
<div class="">Best Regards ,<br class="">
<br class="">
The G. </div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</span></div>
<br class="">
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class="">
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</div>
</blockquote>
</span>
</div>
__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></body></html>