Glance Groups in Gerrit and Launchpad¶
Glance-related groups in Launchpad¶
group |
what |
who |
where |
---|---|---|---|
“Glance” team |
not sure, exactly |
an “open” team, anyone with a Launchpad account can join |
|
“Glance Bug Team” team |
can triage (change status fields) on bugs |
an “open” team, people self-nominate |
|
“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 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 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-related groups in Gerrit¶
The Glance project has total control over the membership of these groups.
group |
what |
who |
where |
---|---|---|---|
glance-ptl |
Current Glance PTL |
glance ptl |
|
glance-core |
+2 powers in Glance project code repositories |
glance core reviewers |
|
glance-specs-core |
+2 powers in glance-specs repository |
glance-core (plus others if appropriate; currently only glance-core) |
|
glance-tempest-plugin-core |
+2 powers on the glance-tempest-plugin repository |
glance-core plus other appropriate people |
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 |
NOTE: The following groups exist, but I don’t think they are used for anything anymore.
group |
where |
---|---|
glance-release |
|
glance-release-branch |
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 projectgerrit/acls
contains the config files