CoC Language in the CNCF Graduation Criteria
Carolyn Van Slyck (CHIEF EMOJI OFFICER) <Carolyn.VanSlyck@...>
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 |
|
Santiago Torres Arias <santiago@...>
Hi, Carolyn!
toggle quoted message
Show quoted text
Apologies beforehand if this is not the place to bring this up. I don't know if there was discussion behind this, so I may be missing a lot of context. Anyway, off to the point. Your comment made me wonder if having a CNCF-wide CoC is the best approach. Alternatively, wouldn't having other options for CoCs to be adopted be ideal? In other words, I wonder if "blessing" a group of possible CoCs to adopt would be a better approach... Thank you! -Santiago On Fri, Jan 31, 2020 at 04:44:23PM +0000, Carolyn Van Slyck (CHIEF EMOJI OFFICER) via Lists.Cncf.Io wrote:
The Kubernetes Code of Conduct Committee wanted to clarify a recent change to the CNCF Graduation Criteria<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cncf_toc_blob_master_process_graduation-5Fcriteria.adoc&d=DwIFAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=y-axRZJ21v7kTm0srYiRfw&m=9SwtJLD9Y0zcAmR12HzqfjznjHWU__P2xNMXV6BvBWo&s=e-B9aRebDYmNGhZ8PtbBvaHmSNhNZHcHQTXcpEZ1PnQ&e= > doc. The change adds to the Sandbox Stage "Adopt the CNCF Code of Conduct" which is great! |
|
Dan Kohn <dan@...>
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:
|
|
Matt Farina
I don't think Kubernetes currently follows a separate Code of Conduct. If you look in https://github.com/kubernetes/community/blob/master/code-of-conduct.md you'll find a pointer to the CNCF CoC. If Kubernetes has a separate CoC it's not currently documented in either the Kubernetes/Kubernetes repo or the Kubernetes Community repo. I would be curious to know what Kubenetes wants to do differently and why. In open source it can be useful to know this and it provides transparency to the governance of the project. - Matt Farina On Fri, Jan 31, 2020, at 5:34 PM, Dan Kohn wrote:
|
|
Dan Kohn <dan@...>
Sorry, I'd forgotten some of the history. I merged the possible schism by adding the divergence in reporting to the CNCF CoC, at the same time that we retained an outside CoC expert to manage inquiries: https://github.com/cncf/foundation/commit/ab6c1296c53d91163022445f568807d904fce6ee#diff-d3030a18b089fdb1fbfabf6e75e4aef0 So, I'm not sure that any changes are currently needed. Any CNCF project could get its own CoC, but doing so would require a vote of the TOC. -- 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 6:46 PM Matt Farina <matt@...> wrote:
|
|
Carolyn Van Slyck (CHIEF EMOJI OFFICER) <Carolyn.VanSlyck@...>
Yes, having an approved alternative would be great.
Thanks, Dan!
From: Dan Kohn <dan@...>
Sent: Friday, January 31, 2020 4:35 PM To: Carolyn Van Slyck (CHIEF EMOJI OFFICER) <Carolyn.VanSlyck@...> Cc: cncf-toc@... Subject: Re: [cncf-toc] CoC Language in the CNCF Graduation Criteria
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. --
On Fri, Jan 31, 2020 at 1:28 PM Carolyn Van Slyck (CHIEF EMOJI OFFICER) via Lists.Cncf.Io <Carolyn.VanSlyck=microsoft.com@...> wrote:
|
|