From 43ac47ec517e87685888d60e6b1f45c942acd3d2 Mon Sep 17 00:00:00 2001 From: Ben Hirschberg <59160382+slashben@users.noreply.github.com> Date: Tue, 26 Nov 2024 11:39:23 +0200 Subject: [PATCH] Update GOVERNANCE.md Signed-off-by: Ben Hirschberg <59160382+slashben@users.noreply.github.com> --- GOVERNANCE.md | 61 +++------------------------------------------------ 1 file changed, 3 insertions(+), 58 deletions(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index ced05611..a26239e7 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -1,60 +1,5 @@ -# Governance of Kubescape +# Governance -## Overview +The Kubescape project manages this document in the central project repository. -The Kubescape project is an open-source initiative dedicated to improve security and best practices in Kubernetes environments. This document outlines the governance structure of the Kubescape project and provides guidance for its community contributors. - -## Code of Conduct - -The CNCF has defined its core values and norms in a [code of conduct](CODE_OF_CONDUCT.md). As a CNCF project, we require all participants in the Kubescape community to behave in line with the standards set out in that document. - -## Contributor roles - -### Community Members - -- Contribute to the project in any form. -- Participate in discussions and provide feedback. - -Anyone can become a community member by contributing to the project. This can be in the form of code contributions, documentation, or any other form of project support. - -### Committers - -Committers are community members who have made significant and consistent contributions to the project. They have the ability to merge minor pull requests if assigned by maintainers. - -- Review and merge minor pull requests. -- Assist maintainers in project tasks. -- Promote best practices within the community. - -A contributor can be proposed as a committer by any existing maintainer. The proposal will be reviewed and voted on by the existing maintainers. - -### Maintainers - -Maintainers are responsible for the smooth operation of the project. They review and merge pull requests, manage releases, and ensure the quality and stability of the codebase. - -- Ensure the quality and stability of the project. -- Resolve conflicts. -- Provide direction and set priorities for the project. - -Maintainers are chosen based on their ongoing contributions and their demonstrated commitment to the project. - -- Any committer who had at least 5 code contribution in the past 12 month can submit themselves to join the maintainer team. The maintainers will appoint members by a majority vote. -- Maintainers who have not taken part in project work (code, reviews, discussions) in the past 12 months will be considered inactive, and may be removed from the maintainer team. - -## Processes - -### Proposing Changes - -1. Open an issue on the project repository to discuss the proposed change. -2. Once there is consensus around the proposed change, create a pull request. -3. Pull requests will be reviewed by committers and/or maintainers. -4. Once the pull request has received approval, it can be merged into the main codebase. - -### Conflict Resolution - -1. In case of any conflicts, it is primarily the responsibility of the parties involved to resolve it. -2. If the conflict cannot be resolved, it will be escalated to the maintainers for resolution. -3. Maintainers' decision will be final in case of unresolved conflicts. - -## Changes to the Governance Document - -Proposed changes to this governance document should follow the same process as any other code change to the Kubescape project (see "Proposing Changes"). +Go to the [centralized GOVERNANCE.md](https://github.com/kubescape/project-governance/blob/main/GOVERNANCE.md)