update Maintainers and Governance to link to community repo - #7023
Draft
Luap99 wants to merge 1 commit into
Draft
Conversation
With the new community repo we use that as place to define our Governance and the org wide rules. As such we should just link there to avoid duplication and drift. Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Member
Author
|
@podman-container-tools/core-maintainers PTAL |
Contributor
|
Same comments as from podman-container-tools/skopeo#2949 |
Luap99
marked this pull request as draft
August 11, 2026 10:59
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
With the new community repo we use that as place to define our Governance and the org wide rules. As such we should just link there to avoid duplication and drift.
How to verify it
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?