The requirement for CNCF projects to adopt the CNCF Code of Conduct (CoC) was in the original version of the graduation criteria adopted by the TOC in December 2016: https://github.com/cncf/toc/commit/9037c28e86977fb4c85578859db78c4b3e1628b8#diff-fc153d49a24a66d7f3ba90c3d144ab19R26

In December 2017, Kubernetes switched from the CNCF CoC to its own: https://github.com/kubernetes/kubernetes/commit/5fe3d9dd13d76230ce584ec1f265c6b7b3e76717#diff-d3030a18b089fdb1fbfabf6e75e4aef0

This was implicitly understood by at least some members of TOC since they are also Kubernetes Steering Committee members. But, it seems worthwhile now to 1) have the TOC approve modifying the graduation criteria to *either* be the CNCF CoC *or* an approved alternative and 2) approve the K8s alternative CoC.

--

Dan Kohn <dan@...> +1-415-233-1000

Executive Director, Cloud Native Computing Foundation cncf.io

dankohn.com or book on my calendar: dankohn.com/c

On Fri, Jan 31, 2020 at 1:28 PM Carolyn Van Slyck (CHIEF EMOJI OFFICER) via Lists.Cncf.Io <Carolyn.VanSlyck=microsoft.com@...> wrote:

The Kubernetes Code of Conduct Committee wanted to clarify a recent change to the CNCF Graduation Criteria doc. The change adds to the Sandbox Stage “Adopt the CNCF Code of Conduct” which is great!

 

It does inadvertently tie our committee’s hands a bit to perform our duties though. We have been discussing updating the K8s CoC and address gaps that we have run into during our term.

 

I’ll submit a PR next week that tweaks the wording back so that the Kubernetes Code of Conduct Committee may continue to manage our Code of Conduct as we have so far.

 

Carolyn Van Slyck

Kubernetes Code of Conduct Committee