Consider creating a multi-project CoC committee

[jberkus]

CNCF,

Larger projects like Kubernetes and Helm have their own committees for CoC enforcement. However, many smaller projects have difficulty staffing a diverse and balanced CoC committee because they just have too few contributors involved. That doesn't mean they don't need one, though; referring all CoC enforcement to a Linux Foundation staff member is both too much work for that staff member, and likely to result in long delays since LF staff cannot have context for the projects.

We (the Governance WG of SIG-Contributor Strategy) propose that the CNCF should consider having a "joint CoC enforcement committee" that all of the smaller projects would be allowed, at their discretion, to join, providing 1 or 2 volunteer members. This would support knowledgable CoC enforcement without requiring projects to each invest a large amount of contributor time, and it would help ensure that the CoC committee was more diverse and balanced.

cc @amye

[krook]

This has been done.

[jberkus]

Er, it's not actually done. Read the proposal again; this is in addition to the CoCC that we already have, intended to create a pipeline for new CoCC members and make the CoCC better equipped to deal with in-project disputes.

I need to flesh it out some. Now that I'm on the CoCC I was planning on tackling it more this year.

/reopen

[krook]

Got it, yes, I misunderstood when I read it before. I thought it was a proposal to create a single CoCC in general.