opensource/podman
1
0
Fork 0
mirror of https://github.com/containers/podman.git synced 2026-03-13 08:01:19 +08:00
Code Issues Packages Projects Releases Wiki Activity

Governance: Make each role's GH permissions explicit

Browse Source 
We were going through our Github permissions to make sure they
were consistent with MAINTAINERS.md when we realized that we did
not make it explicit what each level in our contributor ladder
should receive for permissions. This fixes that oversight. We
retain some flexibility (e.g. granting Triage to anyone who is
assisting with the project, but not enough to become a Reviewer)
but core privileges are now spelled out explicitly.

Signed-off-by: Matt Heon <mheon@redhat.com>
This commit is contained in:
Matt Heon
2026-01-29 14:03:02 -05:00
parent 97a5e4ce01
commit 8b868f83af
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
GOVERNANCE.md
View File

@@ -52,6 +52,7 @@ Description: A Contributor supports the project and adds value to it. Contributi
* Privileges: * Privileges:
* Invitations to contributor events * Invitations to contributor events
* Eligible to become a Reviewer * Eligible to become a Reviewer
* For repositories hosted on Github, Contributors receive Read privileges by default. Contributors who are active in answering questions and assisting with bug reports upstream may request Triage privileges from the repository's maintainers.
### Reviewer ### Reviewer
Description: A Reviewer has responsibility for the triage of issues and review of pull requests on the Podman project or a subproject, consisting of one or more of the Git repositories that form the project. They are collectively responsible, with other Reviewers, for reviewing changes to the repository or repositories and indicating whether those changes are ready to merge. They have a track record of contribution and review in the project. Description: A Reviewer has responsibility for the triage of issues and review of pull requests on the Podman project or a subproject, consisting of one or more of the Git repositories that form the project. They are collectively responsible, with other Reviewers, for reviewing changes to the repository or repositories and indicating whether those changes are ready to merge. They have a track record of contribution and review in the project.
@@ -74,6 +75,7 @@ Reviewers have all the rights and responsibilities of a Contributor, plus:
* Has rights to approve pull requests in the Podman project or a subproject, marking them as ready for a Maintainer to review and merge * Has rights to approve pull requests in the Podman project or a subproject, marking them as ready for a Maintainer to review and merge
* Can recommend and review other contributors to become Reviewers * Can recommend and review other contributors to become Reviewers
* Has permissions to change labels on Github to aid in triage * Has permissions to change labels on Github to aid in triage
* For repositories hosted on Github, Reviewers receive Triage privileges
In repositories using an OWNERS file, Reviewers are listed as Reviewers in that file. In repositories using an OWNERS file, Reviewers are listed as Reviewers in that file.
@@ -106,6 +108,7 @@ A Maintainer must meet the responsibilities and requirements of a Reviewer, plus
* Represent the project in public as a senior project member * Represent the project in public as a senior project member
* Represent the project in interactions with the CNCF * Represent the project in interactions with the CNCF
* Have a voice, but not a vote, in Core Maintainer decision-making meetings * Have a voice, but not a vote, in Core Maintainer decision-making meetings
* For repositories hosted on Github, Maintainers receive Maintain privileges by default. If they have a legitimate reason to require Admin privileges (e.g. working on project CI systems), a Maintainer can petition a Core Maintainer to be granted these additional privileges in Github.
#### Process of becoming a maintainer: #### Process of becoming a maintainer:
1. A current reviewer must be sponsored by a Maintainer of the repository in question or a Core Maintainer. The Maintainer or Core Maintainer will open a PR against the repository and add the nominee as a Maintainer in the [MAINTAINERS.md](./MAINTAINERS.md) file. The need for a sponsor is removed for Emeritus Maintainers, who may open this pull request themselves. 1. A current reviewer must be sponsored by a Maintainer of the repository in question or a Core Maintainer. The Maintainer or Core Maintainer will open a PR against the repository and add the nominee as a Maintainer in the [MAINTAINERS.md](./MAINTAINERS.md) file. The need for a sponsor is removed for Emeritus Maintainers, who may open this pull request themselves.
@@ -130,6 +133,7 @@ Description: As the Podman project is composed of a number of subprojects, most
* Represent the project in public as a senior project member * Represent the project in public as a senior project member
* Represent the project in interactions with the CNCF * Represent the project in interactions with the CNCF
* Have a vote in Core Maintainer decision-making meetings * Have a vote in Core Maintainer decision-making meetings
* For all repositories hosted on Github, Core Maintainers receive Admin privileges.
#### Process of becoming a Core Maintainer: #### Process of becoming a Core Maintainer:
1. A current maintainer must be sponsored by Core Maintainer. The Core Maintainer will open a PR against the main Podman repository and add the nominee as a Core Maintainer in the [MAINTAINERS.md](./MAINTAINERS.md) file. 1. A current maintainer must be sponsored by Core Maintainer. The Core Maintainer will open a PR against the main Podman repository and add the nominee as a Core Maintainer in the [MAINTAINERS.md](./MAINTAINERS.md) file.
@@ -156,6 +160,7 @@ Description: Community managers are responsible for the project’s community in
* Represent the project in public * Represent the project in public
* Represent the project in interactions with the CNCF * Represent the project in interactions with the CNCF
* Have a voice, but not a vote, in Core Maintainer decision-making meetings * Have a voice, but not a vote, in Core Maintainer decision-making meetings
* For all repositories hosted on Github, Community Managers receive Triage privileges.
#### Process of becoming a Community Manager: #### Process of becoming a Community Manager:
1. Community Managers must be sponsored by a Core Maintainer. The Core Maintainer will open a PR against the main Podman repository and add the nominee as a Community Manager in the [MAINTAINERS.md](./MAINTAINERS.md) file. 1. Community Managers must be sponsored by a Core Maintainer. The Core Maintainer will open a PR against the main Podman repository and add the nominee as a Community Manager in the [MAINTAINERS.md](./MAINTAINERS.md) file.