-----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 "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: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to