Jump to: navigation, search

Difference between revisions of "Nova/CoreTeam"

(Created page with "= nova-core = The [https://launchpad.net/~nova-core nova-core] team is responsible for reviewing all changes proposed to the following repositories: * openstack/nova * opens...")
 
(Membership Expectations)
Line 14: Line 14:
  
 
= Membership Expectations =
 
= Membership Expectations =
 +
 +
Membership in the nova-core team is a significant commitment and should not be taken lightly.  Team members are expected to participate in code reviews on a regular (near daily) basis. Members are also expected to stay on top of discussions happening within the project, primarily on the openstack-dev mailing list.  These activities are critical to be able to provide high quality reviews based on the current state of the project that are consistent with the reviews being done by others on the team.

Revision as of 20:50, 24 July 2013

nova-core

The nova-core team is responsible for reviewing all changes proposed to the following repositories:

  • openstack/nova
  • openstack/python-novaclient
  • openstack-doc/compute-api

Adding or Removing Members

A new member may be proposed on the openstack-dev list at any time. A proposal can come from anyone, but typically comes from the project's PTL or an existing member of the core team. Once a proposal has been made, five existing members of the core team must respond with a +1. If any existing member of the team objects, they may respond to the proposal with a -1 to veto the nomination.

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.

Membership Expectations

Membership in the nova-core team is a significant commitment and should not be taken lightly. Team members are expected to participate in code reviews on a regular (near daily) basis. Members are also expected to stay on top of discussions happening within the project, primarily on the openstack-dev mailing list. These activities are critical to be able to provide high quality reviews based on the current state of the project that are consistent with the reviews being done by others on the team.