Skip to content

Governance: better define github permission setup #28840

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Luap99 merged 2 commits into from
Jun 4, 2026
+12 −7
Merged

Governance: better define github permission setup #28840

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8ba16c8
Governance: better define github permission setup
Luap99 Jun 2, 2026
394af2e
Governance: rename Github -> GitHub
Luap99 Jun 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 12 additions & 7 deletions GOVERNANCE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ Before submitting an application to the Core Maintainers, the project in conside

## Removing Subprojects

In some cases, subprojects will become inactive or unmaintainable, or wish to separate from Podman Container Tools. Any Core Maintainer may propose the removal of a subproject on these grounds. Additionally, the Maintainers of any subproject may request removal of their subproject by a publicly visible majority vote (for example, via Github issue). The Core Maintainers must confirm removals with a majority vote. The subproject will be removed as from the list of subprojects in the [Subprojects](#subprojects) section above.
In some cases, subprojects will become inactive or unmaintainable, or wish to separate from Podman Container Tools. Any Core Maintainer may propose the removal of a subproject on these grounds. Additionally, the Maintainers of any subproject may request removal of their subproject by a publicly visible majority vote (for example, via GitHub issue). The Core Maintainers must confirm removals with a majority vote. The subproject will be removed as from the list of subprojects in the [Subprojects](#subprojects) section above.

Subprojects which still have contributors will then be moved to a repository in their own namespace. Projects which have ceased all activity will be kept in the same namespace but archived.

Expand Down Expand Up @@ -74,7 +74,7 @@ Description: A Contributor supports the project and adds value to it. Contributi
* Privileges:
* Invitations to contributor events
* 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.
* For repositories hosted on GitHub, Contributors receive no special 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
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.
Expand All @@ -96,8 +96,9 @@ Reviewers have all the rights and responsibilities of a Contributor, plus:
* Additional privileges:
* 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
* Has permissions to change labels on Github to aid in triage
* For repositories hosted on Github, Reviewers receive Triage privileges
* Has permissions to change labels on GitHub to aid in triage
* For repositories hosted on GitHub, Reviewers receive Triage privileges by being added to the `<repo-name>-reviewers` team.
They also will be invited to the `podman-container-tools` GitHub organization as member.

#### The process of becoming a Reviewer is:
1. The contributor must be sponsored by a Maintainer. That sponsor will open a PR against the appropriate repository, which adds the nominee to the [MAINTAINERS.md](./MAINTAINERS.md) file as a reviewer.
Expand Down Expand Up @@ -126,7 +127,8 @@ 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 interactions with the CNCF
* 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.
* For repositories hosted on GitHub, Maintainers receive Maintain privileges by default by being added to the `<repo-name>-maintainers` team and removed from the `<repo-name>-reviewers` teams.
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:
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.
Expand All @@ -151,7 +153,10 @@ 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 interactions with the CNCF
* Have a vote in Core Maintainer decision-making meetings
* For all repositories hosted on Github, Core Maintainers receive Admin privileges.
* For all repositories hosted on GitHub, Core Maintainers receive Admin privileges by being added as `podman-container-tools` GitHub organization Owner.
* For all repositories hosted on GitHub, Core Maintainers will be added to *all* `<repo-name>-maintainers` teams. Separate from the permissions granted
above, this ensures that Core Maintainers receive pings meant for repository maintainers, as part of their responsibility to assist in code review
and decision making in all repositories.

#### 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.
Expand All @@ -178,7 +183,7 @@ Description: Community managers are responsible for the project’s community in
* Represent the project in public
* Represent the project in interactions with the CNCF
* Have a voice, but not a vote, in Core Maintainer decision-making meetings
* For all repositories hosted on Github, Community Managers receive Triage privileges.
* For all repositories hosted on GitHub, Community Managers receive Triage privileges.

#### 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.
Expand Down