This document defines governance policies for the Kyverno project.
- Principles
- Code of Conduct
- Meetings
- Roles and Process in the Kyverno Community
- Conflict Resolutions
- Changes
- Credits
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.
Kyverno follow the Code of Conduct, which is aligned with the CNCF Code of Conduct.
Kyverno community meetings follow a defined schedule.
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.
The Kyverno project welcomes all contributors and has well-defined roles specified at Project Roles.
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.
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.
Sections of this document have been borrowed from the CoreDNS and fluxcd projects.