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