Jump to: navigation, search

Project Group Management

Revision as of 02:31, 24 January 2013 by Fungi (talk) (typo)


#!wiki caution
'''Future Instructions'''

These are preview instructions for upcoming changes in the project group management process, and are not intended to be usable until 21:00 UTC on February 24, 2013 at the conclusion of the new CLA implementation maintenance window.


Group management for OpenStack and StackForge projects happens primarily in two places, Gerrit (for code review) and Launchpad (for bugs and blueprint management). These systems are not interconnected and as such there is a minimal amount of duplicate information in them.

Gerrit

There are two typical groups of users per-project who are managed in Gerrit: a core group and a drivers group. For an official OpenStack project foo Gerrit will usually have a foo-core group consisting of core contributors delegated the responsibility of merging suitable code contributions to the master branch and marking patches Work in Progress or Ready for Review, and a foo-drivers group responsible for deciding what patches are merged to the milestone-proposed branch in preparation for the next stable release. In many cases the groups for server projects are shared by corresponding client projects (for example, python-fooclient). Standardization of groups for StackForge (and non-core OpenStack) projects is somewhat less standardized, for example one might have only a core group or another might assign its drivers group the responsibility of cutting branches and tagging release commits. The configuration files corresponding to these ACLs are all managed in the openstack-infra/config repository.

Launchpad