From b0c219b21e1828fd2c5cae5946356c514561883c Mon Sep 17 00:00:00 2001 From: Tom Kerkhove Date: Tue, 17 Mar 2020 18:15:36 +0100 Subject: [PATCH 1/2] Provide project governance Signed-off-by: Tom Kerkhove --- GOVERNANCE.md | 41 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+) create mode 100644 GOVERNANCE.md diff --git a/GOVERNANCE.md b/GOVERNANCE.md new file mode 100644 index 00000000000..7505fc405f0 --- /dev/null +++ b/GOVERNANCE.md @@ -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 a scaler, sample or other contribution 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. From 8c779b96fc3a5ae51bdc1c70171c8b1d7a737b60 Mon Sep 17 00:00:00 2001 From: Tom Kerkhove Date: Tue, 17 Mar 2020 19:10:26 +0100 Subject: [PATCH 2/2] Update sections Signed-off-by: Tom Kerkhove --- GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 7505fc405f0..5016521a6a6 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -33,7 +33,7 @@ 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 a scaler, sample or other contribution must +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.