cncf / tag-contributor-strategy

CNCF Technical Advisory Group on Contributor Strategy -- maintainer relations, building up contributors, governance, graduation, and more.
https://contribute.cncf.io/
Apache License 2.0
178 stars 121 forks source link

[Governance Review]: Kyverno #696

Open JimBugwadia opened 3 months ago

JimBugwadia commented 3 months ago

Project Name

Kyverno

Project Website

https://kyverno.io/

Contact Details 1

@JimBugwadia

Contact Details 2

@realshuting

Links to communication channels

https://slack.k8s.io/#kyverno

Reason for governance review request

Application for moving levels from Incubation to Graduation

Are there any sub-projects, plugins, and related?

Governance model

We were not aware of these, but our model seems very similar to the Maintainer Council Governance template.

https://github.com/kyverno/community/blob/main/GOVERNANCE.md

Governance documents

https://github.com/kyverno/community/blob/main/GOVERNANCE.md#summary-of-roles

https://github.com/kyverno/community/blob/main/GOVERNANCE.md#project-roles

https://github.com/kyverno/community/blob/main/GOVERNANCE.md#code-of-conduct

https://github.com/kyverno/community/blob/main/CONTRIBUTING.md

https://main.kyverno.io/community/#community-meeting

https://github.com/kyverno/community/blob/main/SECURITY.md

The main project and sub-projects have code owners file:

(some are missing, we will add these)

Governance Execution Examples

We have not held any public votes, but typically use the maintainer's meetings and slack channels to make and advertise decisions.

Governance Evolution

No significant changes, but we did move all governance related docs to a central repository:

https://github.com/kyverno/community/tree/main

Any specific aspects of your governance structure are you seeking feedback on?

We are wondering how our roles and contributor ladder aligns with other projects, and if any areas should be adjusted.

Do you have any concerns or specific areas where you feel your governance could be improved?

We recently lost several maintainers due to inactivity, change of jobs, and other reasons. We would love for our end users to engage, but are wondering if the bar is too high. Any advice on that would be much appreciated.

Additional notes and resources

No response