From: armando-migliaccio Date: Mon, 19 Oct 2015 19:57:29 +0000 (-0700) Subject: Update notes about the Neutron teams X-Git-Url: https://review.fuel-infra.org/gitweb?a=commitdiff_plain;h=bf22a33e895c7899d8136e08a6fa0d98dd01f45c;p=openstack-build%2Fneutron-build.git Update notes about the Neutron teams Provide links to who belongs to what team, and rename the section to better reflect its content. Add the Neutron drivers team, which apparently was missing and only captured on the wiki.o.o. Change-Id: Ica1de55b11f9c9f3ad24fa5bfa431548499951e8 --- diff --git a/doc/source/policies/index.rst b/doc/source/policies/index.rst index 219f71c33..a8dd24149 100644 --- a/doc/source/policies/index.rst +++ b/doc/source/policies/index.rst @@ -29,7 +29,7 @@ Policies blueprints bugs contributor-onboarding - core-reviewers + neutron-teams gate-failure-triage code-reviews thirdparty-ci diff --git a/doc/source/policies/core-reviewers.rst b/doc/source/policies/neutron-teams.rst similarity index 88% rename from doc/source/policies/core-reviewers.rst rename to doc/source/policies/neutron-teams.rst index 5c699fb37..6f55e8622 100644 --- a/doc/source/policies/core-reviewers.rst +++ b/doc/source/policies/neutron-teams.rst @@ -1,9 +1,8 @@ Neutron Core Reviewers ====================== -The `Neutron Core Reviewer Team -`_ is responsible -for many things related to Neutron. A lot of these things include mundane +The `Neutron Core Reviewer Team `_ +is responsible for many things related to Neutron. A lot of these things include mundane tasks such as the following: * Ensuring the bug count is low @@ -174,15 +173,16 @@ reviewers: queries, and closing gate bugs. * Triaging bugs for the specific areas. -Neutron Core Reviewer Teams -=========================== +Neutron Teams +============= Given all of the above, Neutron has the following core reviewer teams with responsibility over the areas of code listed below: Neutron Core Reviewer Team -------------------------- -Neutron core reviewers have merge rights to the following git repositories: +`Neutron core reviewers `_ have +merge rights to the following git repositories: * `openstack/neutron `_ * `openstack/python-neutronclient `_ @@ -193,22 +193,22 @@ evolve into an area of specialization. Neutron FWaaS Core Reviewer Team -------------------------------- -Neutron FWaaS core reviewers have merge rights to the following git -repositories: +Neutron `FWaaS core reviewers `_ +have merge rights to the following git repositories: * `openstack/neutron-fwaas `_ Neutron LBaaS Core Reviewer Team -------------------------------- -Neutron LBaaS core reviewers have merge rights to the following git -repositories: +Neutron `LBaaS core reviewers `_ +have merge rights to the following git repositories: * `openstack/neutron-lbaas `_ Neutron VPNaaS Core Reviewer Team --------------------------------- -Neutron VPNaaS core reviewers have merge rights to the following git -repositories: +Neutron `VPNaaS core reviewers `_ +have merge rights to the following git repositories: * `openstack/neutron-vpnaas `_ @@ -228,23 +228,40 @@ arise. Neutron Specs Core Reviewer Team -------------------------------- -Neutron specs core reviewers have merge rights to the following git -repositories: +Neutron `specs core reviewers `_ +have +2 rights to the following git repositories: * `openstack/neutron-specs `_ -The Neutron specs core reviewer team is responsible for reviewing and merging -specs into the neutron-specs repository. For the Liberty release, the Specs -core reviewer team will review specs targeted to all neutron git repositories. - -It's worth noting specs reviewers have the following attributes which are -potentially different than code reviewers: +The Neutron specs core reviewer team is responsible for reviewing specs targeted to +all Neutron git repositories (Neutron + Advanced Services). It is worth noting that +specs reviewers have the following attributes which are potentially different than +code reviewers: * Broad understanding of cloud and networking technologies * Broad understanding of core OpenStack projects and technologies * An understanding of the effect approved specs have on the teams development capacity for each cycle +Specs core reviewers may match core members of the above mentioned groups, but +the group can be extended to other individuals, if required. + +Drivers Team +------------ + +The `drivers team `_ is +the group of people who have full rights to the specs repo. This team, which matches +`Launchpad Neutron Drivers team `_, is +instituted to ensure a consistent architectural vision for the Neutron project, and +to continue to disaggregate and share the responsibilities of the Neutron PTL. +The team is in charge of reviewing and commenting on +`RFEs `_, +and working with specification contributors to provide guidance on the process +that govern contributions to the Neutron project as a whole. The team +`meets regularly `_ +to go over RFE's and discuss the project roadmap. Anyone is welcome to join +and/or read the meeting notes. + Code Merge Responsibilities ===========================