Skip to content
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

Jump to bottom

Add a GOVERNANCE file #92

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+11 −0
Open

Add a GOVERNANCE file #92

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
11 changes: 11 additions & 0 deletions GOVERNANCE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
# Governance

## Project Maintainers

[Project maintainers](CODEOWNERS) are responsible for activities around maintaining and updating CNAB-TO-OCI, a library for the [CNAB spec](https://github.com/cnabio/cnab-spec). Final decisions on the project reside with the project maintainers.

Maintainers MUST remain active. If they are unresponsive for >3 months, they will be automatically removed unless a [super-majority](https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote) of the other project maintainers agrees to extend the period to be greater than 3 months.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I realize that we probably copied this from elsewhere, but "automatically" implies that there is an automated process which I don't believe we have.

It may be a good idea to spell out who does the removing. For example, "If they are unresponsive for >3 months, another maintainer may submit a pull request to remove them from CODEOWNERS requiring X approvers unless ..." where X is the usual number of approvers for any other PR.

Otherwise, in my experience people really never get removed because it's awkward and no one knows how to go about it because it's not spelled out.


New maintainers can be added to the project by a [super-majority](https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote) vote of the existing maintainers.

A maintainer may step down by submitting an [issue](https://github.com/cnabio/cnab-to-oci/issues/new) stating their intent.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In practice, I have seen that we have been having maintainers submit a pull request removing themselves from CODEOWNERS and then having the normal number of reviewers (not a supermajority) approve the PR.