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

Provide project governance #690

Merged
merged 2 commits into from
Mar 23, 2020
Merged

Provide project governance #690

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b0c219b
Provide project governance
tomkerkhove Mar 17, 2020
8c779b9
Update sections
tomkerkhove Mar 17, 2020
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
41 changes: 41 additions & 0 deletions GOVERNANCE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
# Governance

## Project Maintainers

[Project maintainers](MAINTAINERS.md) are responsible for activities around
maintaining and updating the KEDA. Final decisions on the features
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.

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 potential maintainer may be nominated by an
existing maintainer. A vote is conducted in private between the current
maintainers over the course of a one week voting period. At the end of the week,
votes are counted and a pull request is made on the repo adding the new
maintainer to the [MAINTAINERS](MAINTAINERS.md) file.

A maintainer may step down by submitting an
[issue](https://github.com/kedacore/keda/issues/new) stating their intent.

Changes to this governance document require a pull request with approval from a
[super-majority](https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote) of
the current maintainers.

## Managing Projects

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

Contributors who want to donate an add-on scaler, sample or donate a repo must
create an issue explaining what the benefit would be for KEDA after which the
maintainers will vote and require a [super-majority](https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote)
of the current maintainers.

When KEDA wants to archive an existing project, maintainers have to take vote where a [super-majority](https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote) of the current maintainers agrees to archive the project with a clear indication of why it is being archived. We must not delete projects to avoid customer confusion.