Note: These are moving in-tree. You can find most of these now available here.
This page tracks all policies and procedures for working within the OpenStack Neutron Project.
Information on BPs can be found in-tree here.
It's worth noting that at the start of each cycle, any BP which did not make it in the release will need to be resubmitted and approved for the next cycle.
A detailed description of the Neutron bug processes, including the mention of the current Neutron Bug Czar, is maintained in-tree here.
All information for new contributors is documented in-tree here.
Information on existing cores, becoming a core, removing a core, and core expectations is available in-tree here.
Gate Failure Triage
Gate failure triage is documented in-tree here.
The Neutron team and sub-teams make extensive use of IRC for meetings. The current list of meetings can be found here. Most sub-teams have weekly meetings, with rollup status reporting back to the weekly Neutron team meeting.
Policies around both code and specification reviews for Neutron are maintained in-tree here.
The NeutronSubTeams page details all of the various sub-teams which operate under Neutron. These sub-teams are responsible for chunks of Neutron. Neutron is a large project, and there are many faucets involved. Having sub-teams is a way to delegate roles and responsibilities around the operational and development aspects of Neutron. The role of a sub-team is as follows:
- Triage, track and close bugs in the sub-team area.
- Report status back to the weekly Neutron meeting.
- Drive BPs in the sub-team area.
- [rkukura] Can we include a somewhat formal pre-review responsibility, where subteam members need to get some number of +1s on each patch before the core reviewers are asked to review the patches?
Third Party Testing
Please see the NeutronThirdPartyTesting page for details.