[openstack-dev] [Glance] Core nominations.

Ian Cordasco ian.cordasco at RACKSPACE.COM
Fri Mar 6 17:40:21 UTC 2015

I like that idea. Can you start it out with Nova or Neutron’s guidelines?

On 3/5/15, 17:38, "Mikhail Fedosin" <mfedosin at mirantis.com> wrote:

>I think yes, it does. But I mean that now we're writing a document called
>Glance Review Guidelines
>RJabsI/edit?usp=sharing> and it has a section "For cores". It's easy to
>include some concrete rules there to
>more clarity.
>2015-03-05 17:46 GMT+03:00 Ihar Hrachyshka
><ihrachys at redhat.com>:
>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> "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?
>Version: GnuPG v1
>OpenStack Development Mailing List (not for usage questions)
>OpenStack-dev-request at lists.openstack.org?subject:unsubscribe

More information about the OpenStack-dev mailing list