[Governance] Add subproject notion and new roles
Marvin Beckers
Dear kcp community,
As per our governance process, I would like to propose an update
to our governance document. You can find the pull request with
changes here: https://github.com/kcp-dev/kcp/pull/3505.
As kcp is evolving, the project is both growing in scope and
contributor basis. We are already hosting several projects that
are directly related to kcp, but not part of the core kcp code. As
such, I am proposing we add the formal notion of "subprojects" to
our governance structure. The current subproject list would be:
- https://github.com/kcp-dev/kcp-operator
- https://github.com/kcp-dev/multicluster-provider
- https://github.com/kcp-dev/api-syncagent
- https://github.com/kcp-dev/generic-controlplane (maybe?)
In addition, I am proposing new roles in the project structure to
allow for long-term contributors to take up responsibilities and
provide them with a progression ladder within the project decision
making process. As such, I am proposing the following two new
roles:
- Subproject maintainers: Trusted community members that have contributed significantly to specific projects and are allowed to steer a subproject by reviewing code changes and participating in maintainer votes concerning the subproject.
- Approvers: Trusted community members that have contributed or gained in-depth knowledge of a specific area of the (subproject) code base. They are generally not allowed to approve any PRs but only ones for specific folders that they've been made approvers of. Approvers do not have voting rights (yet).
If you are a current maintainer of kcp and agree with those
changes, please either leave a comment on this mailing list thread
or a LGTM on the pull request changing our governance document
that is linked above. As this is a change to our governance
document, it requires a 2/3 majority from current maintainers.
Best regards,
Marvin Beckers (@embik)