NOTICE: Community membership ladder update - Maintainers responsibilities merging into Subproject Owners

[Phillip Wittrock]

If you don't care about the Kubernetes Maintainers role or direct write access to the Kubernetes repo, you can stop reading now.

There is an open proposal to remove the notion of Kubernetes project Maintainers from the membership ladder, and merge the responsibilities into subproject owners.  The motivation for merging the roles responsibilities into subproject owners is as follows:

• The scope of the Kubernetes project is such that having a role for holistic maintenance of the entire project in all capacities is not practical. Scoping responsibilities to specific subprojects within the Kubernetes project is more feasible approach to managing the various areas of the project.
  
• Through automation improvements - direct write access to the kubernetes/kubernetes will no longer be necessary for routine maintenance of the project going forward.

For more on subprojects see:

• https://github.com/kubernetes/community/issues/1673
  
• https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance-requirements.md#technical-processes

PR: https://github.com/kubernetes/community/pull/1861

Cheers,

Phil

[Christoph Blecker]

+ kubernetes-maintainers@

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CAPzFYDuut-YZFm74_Go%3Dnnqv0bQ5zy4sOR9M%2BbpPMK%2B3y-1DHQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.