<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Mar 6, 2015 at 11:40 AM, Ian Cordasco <span dir="ltr"><<a href="mailto:ian.cordasco@rackspace.com" target="_blank">ian.cordasco@rackspace.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I like that idea. Can you start it out with Nova or Neutron’s guidelines?<br>
<span class=""><br></span></blockquote><div>FYI, the core reviewer guidelines for Neutron are in-tree now [1], along with all of our other policies around operating in Neutron [2].<br><br>[1] <a href="https://github.com/openstack/neutron/blob/master/doc/source/policies/core-reviewers.rst">https://github.com/openstack/neutron/blob/master/doc/source/policies/core-reviewers.rst</a><br>[2] <a href="https://github.com/openstack/neutron/tree/master/doc/source/policies">https://github.com/openstack/neutron/tree/master/doc/source/policies</a><br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">
On 3/5/15, 17:38, "Mikhail Fedosin" <<a href="mailto:mfedosin@mirantis.com">mfedosin@mirantis.com</a>> wrote:<br>
<br>
>I think yes, it does. But I mean that now we're writing a document called<br>
>Glance Review Guidelines<br>
><br>
><a href="https://docs.google.com/document/d/1Iia0BjQoXvry9XSbf30DRwQt--ODglw-ZTT_5R" target="_blank">https://docs.google.com/document/d/1Iia0BjQoXvry9XSbf30DRwQt--ODglw-ZTT_5R</a><br>
>JabsI/edit?usp=sharing<br>
</span>><<a href="https://docs.google.com/document/d/1Iia0BjQoXvry9XSbf30DRwQt--ODglw-ZTT_5" target="_blank">https://docs.google.com/document/d/1Iia0BjQoXvry9XSbf30DRwQt--ODglw-ZTT_5</a><br>
>RJabsI/edit?usp=sharing> and it has a section "For cores". It's easy to<br>
<div><div class="h5">>include some concrete rules there to<br>
>add<br>
>more clarity.<br>
><br>
>2015-03-05 17:46 GMT+03:00 Ihar Hrachyshka<br>
><<a href="mailto:ihrachys@redhat.com">ihrachys@redhat.com</a>>:<br>
><br>
>-----BEGIN PGP SIGNED MESSAGE-----<br>
>Hash: SHA1<br>
><br>
>On 03/05/2015 11:35 AM, Mikhail Fedosin wrote:<br>
>> Yes, it's absolutely right. For example, Nova and Neutron have<br>
>> official rules for that:<br>
>> <a href="https://wiki.openstack.org/wiki/Nova/CoreTeam" target="_blank">https://wiki.openstack.org/wiki/Nova/CoreTeam</a> where it says: "A<br>
>> member of the team may be removed at any time by the PTL. This is<br>
>> typically due to a drop off of involvement by the member such that<br>
>> they are no longer meeting expectations to maintain team<br>
>> membership".<br>
><a href="https://wiki.openstack.org/wiki/NeutronCore" target="_blank">https://wiki.openstack.org/wiki/NeutronCore</a><br>
><<a href="https://wiki.openstack.org/wiki/NeutronCore" target="_blank">https://wiki.openstack.org/wiki/NeutronCore</a>> "The PTL<br>
>> may remove a member from neutron-core at any time. Typically when a<br>
>> member has decreased their involvement with the project through a<br>
>> drop in reviews and participation in general project development,<br>
>> the PTL will propose their removal and remove them. Members who<br>
>> have previously been core may be fast-tracked back into core if<br>
>> their involvement picks back up" So, as Louis has mentioned, it's a<br>
>> routine work, and why should we be any different? Also, I suggest<br>
>> to write the same wiki document for Glance to prevent these issues<br>
>> in the future.<br>
>><br>
><br>
>Does the rule belong to e.g. governance repo? It seems like a sane<br>
>requirement for core *reviewers* to actually review code, no? Or are<br>
>there any projects that would not like to adopt such a rule formally?<br>
><br>
>/Ihar<br>
>-----BEGIN PGP SIGNATURE-----<br>
>Version: GnuPG v1<br>
><br>
>iQEcBAEBAgAGBQJU+GxdAAoJEC5aWaUY1u579mEIAMN/wucsahaZ0yMT2/eo8t05<br>
>rIWI+lBLjNueWJgB+zNbVlVcsKBZ/hl4J0O3eE65RtlTS5Rta5hv0ymyRL1nnUZH<br>
>g/tL3ogEF0SsSBkiavVh3klGmUwsvQ+ygPN5rVgnbiJ+uO555EPlbiHwZHbcjBoI<br>
>lyUjIhWzUCX26wq7mgiTsY858UgdEt3urVHD9jTE2WNszMRLXQ7vsoAik9xDfISz<br>
>E0eZ8WVQKlNHNox0UoKbobdb3YDhmY3Ahp9Fj2cT1IScyQGORnm0hXV3+pRdWNhD<br>
>1M/gDwAf97F1lfNxPpy4JCGutbe5zoPQYLpJExzaXkqqARxUnwhB1gZ9lEG8l2o=<br>
>=lcLY<br>
>-----END PGP SIGNATURE-----<br>
><br>
>__________________________________________________________________________<br>
>OpenStack Development Mailing List (not for usage questions)<br>
>Unsubscribe:<br>
><a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
</div></div>><<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<div class=""><div class="h5">><br>
><br>
><br>
><br>
><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>