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.
Please follow our code of conduct in all of your interactions within the project.
- 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.
- Maintainers are chosen based on their ongoing contributions and their demonstrated commitment to the project.
- Everyone who had at least 5 code contribution in the last 12 month can submit her/himself for joining the maintainer team
- Maintainers who have not taken part in the project work (code, reviews, discussions) for 12 month are automaticaly removed from the maintainer team
- Maintainers are approved by a simple majority of the existing maintainer team on the quaterly maintainer meeting
- Triagers are contributors who assist the maintainers with project management and backlog organization.
- They keep the backlog in order: applying labels and milestones, assigning issues and pull requests, closing and reopening them, requesting reviews, and asking clarifying questions on new reports.
- Triagers do not merge pull requests. Merging remains the responsibility of the maintainers.
- Triagers are granted the GitHub Triage permission on the repositories under governance.
- A contributor can be proposed as a triager by any existing maintainer. The proposal will be reviewed and voted on by the existing maintainers.
- Everyone who has been performing triage work (organizing the backlog, responding to new issues, reproducing bugs) for at least one month can submit her/himself for joining the triager team
- Triagers who have not taken part in the project work (triage, code, reviews, discussions) for 12 month are automatically removed from the triager team
- Triagers are approved by a simple majority of the existing maintainer team on the quarterly maintainer meeting
- 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.
- Open an issue on the project repository to discuss the proposed change.
- Once there is consensus around the proposed change, create a pull request.
- Pull requests will be reviewed by the maintainers. Triagers may assist by applying labels, assigning reviewers and asking clarifying questions.
- Once the pull request has received approval, it can be merged into the main codebase.
- In case of any conflicts, it is primarily the responsibility of the parties involved to resolve it.
- If the conflict cannot be resolved, it will be escalated to the maintainers for resolution.
- Maintainers' decision will be final in case of unresolved conflicts.
- Ensure the quality and stability of the project.
- Resolve conflicts.
- Provide direction and set priorities for the project.
- Organize the issue and pull request backlog with labels, milestones and assignees.
- Respond to new issues and pull requests, asking clarifying questions and reproducing reported bugs.
- Assist maintainers in project tasks.
- Promote best practices within the community.
- Contribute to the project in any form.
- Participate in discussions and provide feedback.
- Respect the code of conduct and governance of the project.
Proposed changes to this governance document should follow the same process as any other code change to the Kubescape project (see "Proposing Changes").
We hold maintainer meetings every second Monday every three month (for example, 9th of December 2024 then 10th of March 2025 and etc). These meetings are not public, but OFC resolutions and the meeting document is.