Do we also want to consider Project Kuryr part of this? We already started sending Kuryr spec to the Neutron repository and I think it would make sense to manage it as part of Neutron spec process.
Any opinions on that? Gal. On Tue, Oct 20, 2015 at 11:10 PM, Armando M. <arma...@gmail.com> wrote: > Hi folks, > > During revision of the Neutron teams [1], we made clear that the > neutron-specs repo is to be targeted by specs for all the Neutron projects > (core + *-aas). > > For this reason I made sure that the neutron-specs-core team +2 right was > extended to all the core teams. > > Be mindful, use your +2 rights with care: if you are core on a *-aas > project, you should exercise that vote only for specs that pertain the > project you're core of. > > If I could use this email as a reminder also of the core hierarchy and > lieutenant system we switched to in Liberty ([3]): if you have been made > core by a lieutenant of a sub-system, please use your +2/+A only within > your area of comfort and reach out for help if in doubt. > > Reviews are always welcome though! > > Cheers, > Armando > > [1] https://review.openstack.org/#/c/237180/ > [2] https://review.openstack.org/#/admin/groups/314,members > [3] > http://docs.openstack.org/developer/neutron/policies/neutron-teams.html#core-review-hierarchy > > __________________________________________________________________________ > 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 > > -- Best Regards , The G.
__________________________________________________________________________ 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