openstack/neutron
Code Issues Proposed changes

stadium: Separate proprietary interface projects.

Browse Source 
There has been a lot of discussion about how the current "Neutron
stadium" is working out.  Consensus seems to be that it has grown
quickly beyond what makes sense as a single official OpenStack team.
The first step for scaling things back is agreeing on some additional
inclusion criteria that helps with drawing the line for what should be
an independent OpenStack project.  See the following thread on the
mailing list for detailed discussion about this:

http://lists.openstack.org/pipermail/openstack-dev/2015-December/080865.html

This patch applies the first piece of criteria that can be used to decide if a
sub-project should be a separate OpenStack Project team.  It also applies
the criteria against existing repos under Neutron.

Change-Id: I2f0198ba3174aacbe6b3098074f8c03cffd49438
Signed-off-by: Russell Bryant <rbryant@redhat.com>
This commit is contained in:
Russell Bryant 2016-02-04 16:35:28 -05:00
parent 3c04a8bd50
commit 846a528735
2 changed files with 38 additions and 30 deletions
doc/source
policies
neutron-teams.rst
stadium
sub_projects.rst

8
doc/source/policies/neutron-teams.rst

@ -118,8 +118,6 @@ updating the core review team for the sub-project's repositories.
+------------------------+---------------------------+----------------------+
| networking-calico | Neil Jerram | neiljerram |
+------------------------+---------------------------+----------------------+
| networking-infoblox | John Belamaric | johnbelamaric |
+------------------------+---------------------------+----------------------+
| networking-l2gw | Sukhdev Kapur | sukhdev |
+------------------------+---------------------------+----------------------+
| networking-midonet | Ryu Ishimoto | ryu25 |
@ -140,16 +138,10 @@ updating the core review team for the sub-project's repositories.
+------------------------+---------------------------+----------------------+
| networking-ovn | Russell Bryant | russellb |
+------------------------+---------------------------+----------------------+
| networking-plumgrid | Fawad Khaliq | fawadkhaliq |
+------------------------+---------------------------+----------------------+
| networking-sfc | Cathy Zhang | cathy |
+------------------------+---------------------------+----------------------+
| networking-vshpere | Vivekanandan Narasimhan | viveknarasimhan |
+------------------------+---------------------------+----------------------+
| octavia | German Eichberger | xgerman |
+------------------------+---------------------------+----------------------+
| vmware-nsx | Gary Kotton | garyk |
+------------------------+---------------------------+----------------------+
Existing Core Reviewers
-----------------------

60
doc/source/stadium/sub_projects.rst

@ -75,11 +75,27 @@ Inclusion Criteria
As mentioned before, the Neutron PTL must approve the inclusion of each
additional repository under the Neutron project. That evaluation will be
primarily based on the new project requirements used for all new OpenStack
projects for the criteria that is applicable:
initially based on the new project requirements used for all new OpenStack
projects for the criteria that is applicable. If there's any question about
this, the review should be deferred to the TC as a new OpenStack project team.
http://governance.openstack.org/reference/new-projects-requirements.html
Including *everything* related to Neutron under the Neutron project team has not
scaled well, so some Neutron related projects are encouraged to form a new
OpenStack project team. The following list of guidelines are not hard rules.
There may be exceptions. Instead, they serve as criteria that may influence the
decision one way or the other.
These criteria are designed around how easy it would be for members of the
loosely defined "Neutron team" to jump in and help fix or even take over a given
repository if needed.
* Neutron stays quite busy developing and maintaining open source
implementations for features. Any sub-project that serves as an interface to
proprietary technology should most likely be a separate project team. This
imposes a barrier on access to the technology for dev/test and CI integration.
Official Sub-Project List
-------------------------
@ -123,24 +139,12 @@ functionality.
+-------------------------------+-----------------------+
| kuryr_ | docker |
+-------------------------------+-----------------------+
| networking-ale-omniswitch_ | ml2 |
+-------------------------------+-----------------------+
| networking-arista_ | ml2,l3 |
+-------------------------------+-----------------------+
| networking-bagpipe_ | ml2 |
+-------------------------------+-----------------------+
| networking-bgpvpn_ | vpn |
+-------------------------------+-----------------------+
| networking-calico_ | ml2 |
+-------------------------------+-----------------------+
| networking-cisco_ | core,ml2,l3,fw,vpn |
+-------------------------------+-----------------------+
| networking-fujitsu_ | ml2 |
+-------------------------------+-----------------------+
| networking-hyperv_ | ml2 |
+-------------------------------+-----------------------+
| networking-infoblox_ | ipam |
+-------------------------------+-----------------------+
| networking-l2gw_ | l2 |
+-------------------------------+-----------------------+
| networking-midonet_ | core,ml2,l3,lb,fw |
@ -153,14 +157,8 @@ functionality.
+-------------------------------+-----------------------+
| networking-ovn_ | core |
+-------------------------------+-----------------------+
| networking-plumgrid_ | core |
+-------------------------------+-----------------------+
| networking-powervm_ | ml2 |
+-------------------------------+-----------------------+
| networking-sfc_ | sfc |
+-------------------------------+-----------------------+
| networking-vsphere_ | ml2 |
+-------------------------------+-----------------------+
| neutron_ | base,l2,ml2,core,l3 |
+-------------------------------+-----------------------+
| neutron-lbaas_ | lb,dashboard |
@ -177,8 +175,6 @@ functionality.
+-------------------------------+-----------------------+
| python-neutron-pd-driver_ | pd |
+-------------------------------+-----------------------+
| vmware-nsx_ | core |
+-------------------------------+-----------------------+
Affiliated projects
@ -191,20 +187,40 @@ capabilities of Neutron, the Neutron API, or a combination of both.
+-------------------------------+-----------------------+
| Name | Functionality |
+===============================+=======================+
| networking-ale-omniswitch_ | ml2 |
+-------------------------------+-----------------------+
| networking-arista_ | ml2,l3 |
+-------------------------------+-----------------------+
| networking-bigswitch_ | ml2,core,l3 |
+-------------------------------+-----------------------+
| networking-brocade_ | ml2,l3 |
+-------------------------------+-----------------------+
| networking-cisco_ | core,ml2,l3,fw,vpn |
+-------------------------------+-----------------------+
| networking-edge-vpn_ | vpn |
+-------------------------------+-----------------------+
| networking-fujitsu_ | ml2 |
+-------------------------------+-----------------------+
| networking-hyperv_ | ml2 |
+-------------------------------+-----------------------+
| networking-infoblox_ | ipam |
+-------------------------------+-----------------------+
| networking-mlnx_ | ml2 |
+-------------------------------+-----------------------+
| networking-nec_ | core |
+-------------------------------+-----------------------+
| networking-plumgrid_ | core |
+-------------------------------+-----------------------+
| networking-powervm_ | ml2 |
+-------------------------------+-----------------------+
| nuage-openstack-neutron_ | core |
+-------------------------------+-----------------------+
| networking-ovs-dpdk_ | ml2 |
+-------------------------------+-----------------------+
| networking-vsphere_ | ml2 |
+-------------------------------+-----------------------+
| vmware-nsx_ | core |
+-------------------------------+-----------------------+
.. _networking-ale-omniswitch: