krkn/GOVERNANCE.md

The governance model adopted here is heavily influenced by a set of CNCF projects, especially drew reference from Kubernetes governance. For similar structures some of the same wordings from kubernetes governance are borrowed to adhere to the originally construed meaning.

Principles

• Open: Krkn is open source community.
• Welcoming and respectful: See Code of Conduct.
• Transparent and accessible: Work and collaboration should be done in public. Changes to the Krkn organization, Krkn code repositories, and CNCF related activities (e.g. level, involvement, etc) are done in public.
• Merit: Ideas and contributions are accepted according to their technical merit and alignment with project objectives, scope and design principles.

Code of Conduct

Krkn follows the CNCF Code of Conduct. Here is an excerpt:

As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.

Maintainer Levels

Contributor

Contributors contribute to the community. Anyone can become a contributor by participating in discussions, reporting bugs, or contributing code or documentation.

Responsibilities:

Be active in the community and adhere to the Code of Conduct.

Report bugs and suggest new features.

Contribute high-quality code and documentation.

Member

Members are active contributors to the community. Members have demonstrated a strong understanding of the project's codebase and conventions.

Responsibilities:

Review pull requests for correctness, quality, and adherence to project standards.

Provide constructive and timely feedback to contributors.

Ensure that all contributions are well-tested and documented.

Work with maintainers to ensure a smooth and efficient release process.

Maintainer

Maintainers are responsible for the overall health and direction of the project. They are long-standing contributors who have shown a deep commitment to the project's success.

Responsibilities:

Set the technical direction and vision for the project.

Manage releases and ensure the stability of the main branch.

Make decisions on feature inclusion and project priorities.

Mentor other contributors and help grow the community.

Resolve disputes and make final decisions when consensus cannot be reached.

Owner

Owners have administrative access to the project and are the final decision-makers.

Responsibilities:

Manage the core team of maintainers and approvers.

Set the overall vision and strategy for the project.

Handle administrative tasks, such as managing the project's repository and other resources.

Represent the project in the broader open-source community.

Credits

Sections of this document have been borrowed from Kubernetes governance