Re: [cncf-gb] Formation of CNCF CoC Update Working Group
I’m concerned that limiting this to TAG Leadership puts even more work on already overloaded individuals. I know that as a TAG Leader, I personally don’t have the bandwidth to attend and participate in yet another WG.
It would be much better if the TAGs could select someone who is passionate about the topic and has the relevant expertise to participate, regardless of whether they are a TAG leader. This will result better outcomes for the CoC Working Group because we can get the right people involved who have the expertise, time, and passion for the topic.
cncf-toc@... <cncf-toc@...> on behalf of Arun Gupta via lists.cncf.io <arun.gupta=gmail.com@...>
Let me provide some more color here.
This Working Group is a "bootstrap committee" approach that will layout the foundation for CNCF CoCC. The WG is intentionally designed to include a wide range of voices across many projects, not just Kubernetes. This approach is not very different from k8s CoCC bootstrapping process https://github.com/kubernetes/community/blob/master/committee-code-of-conduct/bootstrapping-process.md. The only difference is it needs to provide an equal voice to 120+ projects across the board.
More than 500 maintainers listed at https://github.com/cncf/foundation/blob/main/project-maintainers.csv (only incubation and graduated projects) will be allowed to participate in this WG. This ensures diversity and inclusion in the WG from across the community. We don't know how many maintainers will join but also want to make sure the group size is manageable. We also want to make sure that all voices are heard.
The group is critical that we'd like the TAG leadership, as opposed to a delegate, to be represented here directly.
Anybody in the community would be allowed to share their proposals by sending a PR to a GH repo. We are in the process of creating this GH repo and will report back once its done. I personally encourage everybody here that cares about this topic to submit their thoughts there.
Thanks for your patience and understanding while we work through the process.
On Thu, Jun 9, 2022 at 6:39 PM Davanum Srinivas <davanum@...> wrote: