mirror of
https://github.com/kyverno/kyverno.git
synced 2024-12-15 17:51:20 +00:00
dfd478f22c
Signed-off-by: Abhishek Kumar <abhishek22512@gmail.com> Co-authored-by: Chip Zoller <chipzoller@gmail.com>
39 lines
No EOL
2.5 KiB
Markdown
39 lines
No EOL
2.5 KiB
Markdown
# Kyverno Governance
|
|
|
|
This document defines governance policies for the Kyverno project.
|
|
|
|
- [Principles](#principles)
|
|
- [Code of Conduct](#code-of-conduct)
|
|
- [Meetings](#meetings)
|
|
- [Roles and Process in the Kyverno Community](#roles)
|
|
- [Conflict Resolutions](#conflict-resolutions)
|
|
- [Changes](#changes)
|
|
- [Credits](#credits)
|
|
|
|
## Principles
|
|
The Kyverno project community adheres to the following principles:
|
|
|
|
- Open: The Kyverno community strives to be open, accessible and welcoming to everyone. Anyone may contribute, and contributions are available to all users according to open source values and licenses.
|
|
- Transparent and accessible: Any changes to the Kyverno source code and collaborations on the project are publicly accessible (GitHub issues, PRs, and discussions).
|
|
- Merit: Ideas and contributions are accepted according to their technical merit and alignment with project objectives, scope, and design principles.
|
|
|
|
|
|
## Code of Conduct
|
|
Kyverno follow the [Code of Conduct](CODE_OF_CONDUCT.md), which is aligned with the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
|
|
|
|
## Meetings
|
|
Kyverno community meetings follow a defined [schedule](https://kyverno.io/community/#community-meetings).
|
|
|
|
The maintainers will also have closed meetings in order to discuss security reports or Code of Conduct violations. Such meetings should be scheduled by any maintainer on receipt of a security issue or CoC report. All current Maintainers must be invited to such closed meetings, except for any maintainer who is accused of a CoC violation.
|
|
|
|
## Roles
|
|
The Kyverno project welcomes all contributors and has well-defined roles specified at [Project Roles](https://kyverno.io/community/#project-roles).
|
|
|
|
## Conflict Resolutions
|
|
Typically, it is assumed that disputes will be resolved amicably by those involved. However, if the situation becomes more serious, conflicts will be resolved through a voting process. A supermajority of votes from project maintainers is required to make a decision, and the project lead has the final say in the ruling.
|
|
|
|
## Changes
|
|
This Project Governance is a living document. All key project changes including changes in project governance can be proposed by a GitHub PR and then reviewed and voted on by project maintainers.
|
|
|
|
## Credits
|
|
Sections of this document have been borrowed from the [CoreDNS](https://github.com/coredns/coredns/blob/master/GOVERNANCE.md) and [fluxcd](https://github.com/fluxcd/community/blob/main/GOVERNANCE.md) projects. |