glance/doc/source/contributor/glance-groups.rst
Abhishek Kekane e1e8e9de40 Doc: Glance group management
Change-Id: If8798525aff5195e77f451dfce6c45cfaf16eaf4
2022-05-30 14:44:12 +00:00

4.2 KiB

Glance Groups in Gerrit and Launchpad

group what who where
"Glance" team not sure, exactly an "open" team, anyone with a Launchpad account can join Glance Launchpad
"Glance Bug Team" team can triage (change status fields) on bugs an "open" team, people self-nominate Glance Bug Team
"Glance Drivers" team not sure, exactly Anyone who is interested in doing some work, has a Launchpad account, and is approved by the current members Glance Drivers Team
"Glance Release" team Maintains the Launchpad space for Glance, glance_store, python-glanceclient, and glance-tempest-plugin Anyone who is interested in doing some work, has a Launchpad account, and is approved by the current members Glance Release Team
"Glance Core security contacts" team can see and work on private security bugs while they are under embargo subset of glance-core (the OpenStack Vulnerablity Management Team likes to keep this team small), so even though the PTL can add people, you should propose them on the mailing list first. Glance Security Team

The Glance project has total control over the membership of these groups.

group what who where
glance-ptl Current Glance PTL glance ptl Glance PTL
glance-core +2 powers in Glance project code repositories glance core reviewers Glance Core Team
glance-specs-core +2 powers in glance-specs repository glance-core (plus others if appropriate; currently only glance-core) Glance Specs Core Team
glance-tempest-plugin-core +2 powers on the glance-tempest-plugin repository glance-core plus other appropriate people Glance Tempest Plugin Core Team

The Glance project shares control over the membership of these groups. If you want to add someone to one of these groups who doesn't already have membership by being in an included group, be sure to include the other groups or individual members in your proposal email.

group what who where
glance-stable-maint +2 powers on backports to stable branches subset of glance-core (subject to approval by stable-maint-core) plus the stable-maint-core team Glance Stable Core Team

NOTE: The following groups exist, but I don't think they are used for anything anymore.

group where
glance-release Glance Release
glance-release-branch Glance Stable Release Team

How Gerrit groups are connected to project repositories

The connection between the groups defined in gerrit and what they can do is defined in the project-config repository: https://opendev.org/openstack/project-config

  • gerrit/projects.yaml sets the config file for a project
  • gerrit/acls contains the config files