Date   

[VOTE] Keptn for incubation

Amye Scavarda Perrin
 

Keptn has applied to move to the incubation level.

PR: https://github.com/cncf/toc/pull/670

Due Diligence doc: https://docs.google.com/document/d/14qFAc6kxhWX_JLMUKddgELcymaRw6jmhsq0OYxrHtc0

Lei Zhang is now the TOC sponsor for this project, has called for public comment and has approved a call for a public vote. (https://lists.cncf.io/g/cncf-toc/message/6851)

Please vote (+1/0/-1) by replying to this thread.

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!
--
Amye Scavarda Perrin | Director of Developer Programs, CNCF | amye@...


[VOTE] Kyverno for incubation

Amye Scavarda Perrin
 

Kyverno has applied to move to the incubation level.

PR: PR: https://github.com/cncf/toc/pull/784

Due Diligence doc: https://docs.google.com/document/d/18dWgOd2MUQz3RXI1R9vKntL3ULyZhOD1HEtijGOeaWg/edit?usp=sharing

Davanum Srinivas is the TOC sponsor for this project, has called for public comment and has approved a call for a public vote. (https://lists.cncf.io/g/cncf-toc/message/6859)

Please vote (+1/0/-1) by replying to this thread.

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Amye Scavarda Perrin | Director of Developer Programs, CNCF | amye@...


Re: CNCF Code of Conduct Community of Practice?

Vincent Batts
 

Big agree. The spirit of this proposal was very alive in the community members that showed up for the CoC BoF talk at KubeCon EU last week. Particularly and currently, to ensure a fair process.

Expecting that pay-to-play GB roles will handle this in the same spirit as communities already do seems to be at a disconnect. Don't get me wrong, I <3 so many of the GB members, but this is a distinct and sensitive topic that is normal for communities.

I am happy to support and even bootstrap this effort.


Post-Kubecon (was Re: [cncf-toc] CNCF Code of Conduct Community of Practice?)

Davanum Srinivas
 

Folks,
Got back home last evening, To get us all started Arun, Joanna and myself are meeting today to "Discuss CNCF CoC Update Working Group" to get us rolling. Will drop an update after that.

Thanks,
Dims

PS: please see a twitter thread from Laura Santamaria that kind of mirrors Paris' first email on this thread - https://threadreaderapp.com/thread/1529206806714757121.html


On Mon, May 23, 2022 at 10:03 AM Davanum Srinivas via lists.cncf.io <davanum=gmail.com@...> wrote:
Folks,


Crossing Streams!!!

image.png

On Mon, May 23, 2022 at 3:13 PM Divya Mohan <divya.mohan0209@...> wrote:
Just catching up on emails after the event, but a huge +1 to this effort and I'd be happy to help/contribute in any way I can :)

Regards,
Divya

On Sat, 21 May, 2022, 7:35 pm Scott Rigby, <scott@...> wrote:
a few days late to the party...
Paris, 💯 to this
Dims, 👍 to designing in collaboration with the community
xo

On Thu, May 19, 2022 at 1:08 AM Davanum Srinivas <davanum@...> wrote:
Joanna,

Quick note on something I touched on when we chatted at dinner.

Here's the relevant section as pointed out by Paris below (pasting the same url here for your reference):
https://github.com/cncf/foundation/blob/main/charter.md#13-code-of-conduct

The text as it stands today says two things:
Point #1 -  "All participants agree to abide by The Linux Foundation Code of Conduct available at https://events.linuxfoundation.org/code-of-conduct."
Point #2 - "The TOC may vote to adopt its own code of conduct for the CNCF community."

Our Charter clearly puts "code of conduct for the CNCF community" in the hands of the TOC (says so right there!), just writing one is not enough and any Code of Conduct needs to be enforced for it to have any effect, So we will look at options to design this properly in collaboration with the community which this Code of Conduct will end up governing!

thanks,
Dims

On Tue, May 17, 2022 at 12:40 PM Paris Pittman <paris.pittman@...> wrote:

Hi TOC and community,


 I believe we are at a point where a CNCF code of conduct community of practice will serve us well. I sat on the first Kubernetes Code of Conduct committee and many of the below ideas stemmed from my experiences there. Whether this is a body, community of practice, incident management team, etc is all up for discussion.


Would it be possible to put this on the next TOC agenda? If folks are interested in this work and at KubeCon, give a shout; even if you’re virtual, I’m hanging on CNCF Slack. 


-paris 


To help get the ball rolling for discussion, here are some rough ideas:

https://github.com/cncf/foundation/blob/main/charter.md#13-code-of-conduct


Purpose

Create a community of practice around code of conduct matters at the CNCF Community level. This community of practice could be bootstrapped by an independant committee, a working group of TAG Contributor Strategy, or another organizational design that TOC thinks would position this group for success with the ultimate goal of an independent body. This doc is not intended to be implementation details but the establishment of such a community.

Goals

  • community members creating policy and carrying out enforcement
  • creating a safe space for reporters
  • Focus on mediation rather than ligitation. goals of having a community member/body take reports vs CNCF staff and lawyers. 
  • cncf community members, project contributors, toc, ambassadors, and cncf staff would have this as a resource
  • build trust via community involvement and transparency reporting 

NonGoals

  • require changes to projects that already have defined code of conduct systems in place that aren’t LF support; eg Kubernetes Code of Conduct Committee

Knowns

  • Kubernetes has a code of conduct committee. It was created independently due to scale, our values, and desire for a community run program. https://github.com/kubernetes/community/blob/master/committee-code-of-conduct/bootstrapping-process.md
  • OpenTelemetry’s GC acts as a CoCC.
  • All other projects, which are governed by CNCF staff, go to Chris A or Priyanka as first step
  • CNCF Staff consults with laywers to enforce their code of conduct; this is seen as a power differential in the community; “a business approach”
  • Most CoC language on LF sites are geared towards events and not other situations or related conduct matters
  • There have been issues in the past with community members confused on where to file issues, who enforces, and where/when at cloud native related events. Example: If its “kubecon” does that mean conduct@...?

Responsibilities and Composition

  • Nominations from TOC and community; TOC shortlist for qualifications; community votes
  • everyone gets training
  • initial group bootstraps the function
    • build out policies and procedures that fit with the ecosystem
    • create roles and teams
    • create a charter

Opportunities

  • Allows CNCF staff to focus on project operations and membership vs mediating community challenges and incidents. Instead puts mediation and enforcement into the community. 
  • focus on mediation vs litigation.
  • incident management and transparecy reporting //build out an incident management team
  • projects can plug into this with better incident reporting structures than contact someone an attorney at Linux Foundation
  • projects can have liasion reps which can then feed into staffing for incident response groups

Next Steps

  • Discuss at a TOC meeting
  • Bring in current and emeritus Kubernetes CoCC to help formulate and bootstrap discussions
  • Bring in project maintainers from CNCF projects; possiby create a special Maintainers Circle for this topic

Open Questions

  • We would need this to be an independent body. Where would that sit?
  • can an overarching committee have sufficient visibility into project-specific context to offer quality outcomes around restoration after an incident?
  • Does a CoC action taken in one project affect a contributor’s ability to participate in other CNCF projects?
  • Escalation path for events?
  • Liability coverage for Committee decisions




--
Davanum Srinivas :: https://twitter.com/dims



--
Davanum Srinivas :: https://twitter.com/dims



--
Davanum Srinivas :: https://twitter.com/dims


CNCF Tech Writers Office Hours Cancelled this month (May)

Nate Waddington
 

Hello Everyone,

Generally, on the last Wednesday of every month, we host a CNCF Tech Writers Office Hours; however, this month, this lands the week after KubeCon, and we have several folks out on vacation. As we have no one to facilitate this month, I’ll be canceling the office hours. Sorry for any inconvenience.

I hope to see you next month for the June Tech Writers Office Hours!

Cheers,
Nate.


Re: CNCF Code of Conduct Community of Practice?

Davanum Srinivas
 

Folks,


Crossing Streams!!!

image.png

On Mon, May 23, 2022 at 3:13 PM Divya Mohan <divya.mohan0209@...> wrote:
Just catching up on emails after the event, but a huge +1 to this effort and I'd be happy to help/contribute in any way I can :)

Regards,
Divya

On Sat, 21 May, 2022, 7:35 pm Scott Rigby, <scott@...> wrote:
a few days late to the party...
Paris, 💯 to this
Dims, 👍 to designing in collaboration with the community
xo

On Thu, May 19, 2022 at 1:08 AM Davanum Srinivas <davanum@...> wrote:
Joanna,

Quick note on something I touched on when we chatted at dinner.

Here's the relevant section as pointed out by Paris below (pasting the same url here for your reference):
https://github.com/cncf/foundation/blob/main/charter.md#13-code-of-conduct

The text as it stands today says two things:
Point #1 -  "All participants agree to abide by The Linux Foundation Code of Conduct available at https://events.linuxfoundation.org/code-of-conduct."
Point #2 - "The TOC may vote to adopt its own code of conduct for the CNCF community."

Our Charter clearly puts "code of conduct for the CNCF community" in the hands of the TOC (says so right there!), just writing one is not enough and any Code of Conduct needs to be enforced for it to have any effect, So we will look at options to design this properly in collaboration with the community which this Code of Conduct will end up governing!

thanks,
Dims

On Tue, May 17, 2022 at 12:40 PM Paris Pittman <paris.pittman@...> wrote:

Hi TOC and community,


 I believe we are at a point where a CNCF code of conduct community of practice will serve us well. I sat on the first Kubernetes Code of Conduct committee and many of the below ideas stemmed from my experiences there. Whether this is a body, community of practice, incident management team, etc is all up for discussion.


Would it be possible to put this on the next TOC agenda? If folks are interested in this work and at KubeCon, give a shout; even if you’re virtual, I’m hanging on CNCF Slack. 


-paris 


To help get the ball rolling for discussion, here are some rough ideas:

https://github.com/cncf/foundation/blob/main/charter.md#13-code-of-conduct


Purpose

Create a community of practice around code of conduct matters at the CNCF Community level. This community of practice could be bootstrapped by an independant committee, a working group of TAG Contributor Strategy, or another organizational design that TOC thinks would position this group for success with the ultimate goal of an independent body. This doc is not intended to be implementation details but the establishment of such a community.

Goals

  • community members creating policy and carrying out enforcement
  • creating a safe space for reporters
  • Focus on mediation rather than ligitation. goals of having a community member/body take reports vs CNCF staff and lawyers. 
  • cncf community members, project contributors, toc, ambassadors, and cncf staff would have this as a resource
  • build trust via community involvement and transparency reporting 

NonGoals

  • require changes to projects that already have defined code of conduct systems in place that aren’t LF support; eg Kubernetes Code of Conduct Committee

Knowns

  • Kubernetes has a code of conduct committee. It was created independently due to scale, our values, and desire for a community run program. https://github.com/kubernetes/community/blob/master/committee-code-of-conduct/bootstrapping-process.md
  • OpenTelemetry’s GC acts as a CoCC.
  • All other projects, which are governed by CNCF staff, go to Chris A or Priyanka as first step
  • CNCF Staff consults with laywers to enforce their code of conduct; this is seen as a power differential in the community; “a business approach”
  • Most CoC language on LF sites are geared towards events and not other situations or related conduct matters
  • There have been issues in the past with community members confused on where to file issues, who enforces, and where/when at cloud native related events. Example: If its “kubecon” does that mean conduct@...?

Responsibilities and Composition

  • Nominations from TOC and community; TOC shortlist for qualifications; community votes
  • everyone gets training
  • initial group bootstraps the function
    • build out policies and procedures that fit with the ecosystem
    • create roles and teams
    • create a charter

Opportunities

  • Allows CNCF staff to focus on project operations and membership vs mediating community challenges and incidents. Instead puts mediation and enforcement into the community. 
  • focus on mediation vs litigation.
  • incident management and transparecy reporting //build out an incident management team
  • projects can plug into this with better incident reporting structures than contact someone an attorney at Linux Foundation
  • projects can have liasion reps which can then feed into staffing for incident response groups

Next Steps

  • Discuss at a TOC meeting
  • Bring in current and emeritus Kubernetes CoCC to help formulate and bootstrap discussions
  • Bring in project maintainers from CNCF projects; possiby create a special Maintainers Circle for this topic

Open Questions

  • We would need this to be an independent body. Where would that sit?
  • can an overarching committee have sufficient visibility into project-specific context to offer quality outcomes around restoration after an incident?
  • Does a CoC action taken in one project affect a contributor’s ability to participate in other CNCF projects?
  • Escalation path for events?
  • Liability coverage for Committee decisions




--
Davanum Srinivas :: https://twitter.com/dims



--
Davanum Srinivas :: https://twitter.com/dims


Re: CNCF Code of Conduct Community of Practice?

Divya Mohan
 

Just catching up on emails after the event, but a huge +1 to this effort and I'd be happy to help/contribute in any way I can :)

Regards,
Divya

On Sat, 21 May, 2022, 7:35 pm Scott Rigby, <scott@...> wrote:
a few days late to the party...
Paris, 💯 to this
Dims, 👍 to designing in collaboration with the community
xo

On Thu, May 19, 2022 at 1:08 AM Davanum Srinivas <davanum@...> wrote:
Joanna,

Quick note on something I touched on when we chatted at dinner.

Here's the relevant section as pointed out by Paris below (pasting the same url here for your reference):
https://github.com/cncf/foundation/blob/main/charter.md#13-code-of-conduct

The text as it stands today says two things:
Point #1 -  "All participants agree to abide by The Linux Foundation Code of Conduct available at https://events.linuxfoundation.org/code-of-conduct."
Point #2 - "The TOC may vote to adopt its own code of conduct for the CNCF community."

Our Charter clearly puts "code of conduct for the CNCF community" in the hands of the TOC (says so right there!), just writing one is not enough and any Code of Conduct needs to be enforced for it to have any effect, So we will look at options to design this properly in collaboration with the community which this Code of Conduct will end up governing!

thanks,
Dims

On Tue, May 17, 2022 at 12:40 PM Paris Pittman <paris.pittman@...> wrote:

Hi TOC and community,


 I believe we are at a point where a CNCF code of conduct community of practice will serve us well. I sat on the first Kubernetes Code of Conduct committee and many of the below ideas stemmed from my experiences there. Whether this is a body, community of practice, incident management team, etc is all up for discussion.


Would it be possible to put this on the next TOC agenda? If folks are interested in this work and at KubeCon, give a shout; even if you’re virtual, I’m hanging on CNCF Slack. 


-paris 


To help get the ball rolling for discussion, here are some rough ideas:

https://github.com/cncf/foundation/blob/main/charter.md#13-code-of-conduct


Purpose

Create a community of practice around code of conduct matters at the CNCF Community level. This community of practice could be bootstrapped by an independant committee, a working group of TAG Contributor Strategy, or another organizational design that TOC thinks would position this group for success with the ultimate goal of an independent body. This doc is not intended to be implementation details but the establishment of such a community.

Goals

  • community members creating policy and carrying out enforcement
  • creating a safe space for reporters
  • Focus on mediation rather than ligitation. goals of having a community member/body take reports vs CNCF staff and lawyers. 
  • cncf community members, project contributors, toc, ambassadors, and cncf staff would have this as a resource
  • build trust via community involvement and transparency reporting 

NonGoals

  • require changes to projects that already have defined code of conduct systems in place that aren’t LF support; eg Kubernetes Code of Conduct Committee

Knowns

  • Kubernetes has a code of conduct committee. It was created independently due to scale, our values, and desire for a community run program. https://github.com/kubernetes/community/blob/master/committee-code-of-conduct/bootstrapping-process.md
  • OpenTelemetry’s GC acts as a CoCC.
  • All other projects, which are governed by CNCF staff, go to Chris A or Priyanka as first step
  • CNCF Staff consults with laywers to enforce their code of conduct; this is seen as a power differential in the community; “a business approach”
  • Most CoC language on LF sites are geared towards events and not other situations or related conduct matters
  • There have been issues in the past with community members confused on where to file issues, who enforces, and where/when at cloud native related events. Example: If its “kubecon” does that mean conduct@...?

Responsibilities and Composition

  • Nominations from TOC and community; TOC shortlist for qualifications; community votes
  • everyone gets training
  • initial group bootstraps the function
    • build out policies and procedures that fit with the ecosystem
    • create roles and teams
    • create a charter

Opportunities

  • Allows CNCF staff to focus on project operations and membership vs mediating community challenges and incidents. Instead puts mediation and enforcement into the community. 
  • focus on mediation vs litigation.
  • incident management and transparecy reporting //build out an incident management team
  • projects can plug into this with better incident reporting structures than contact someone an attorney at Linux Foundation
  • projects can have liasion reps which can then feed into staffing for incident response groups

Next Steps

  • Discuss at a TOC meeting
  • Bring in current and emeritus Kubernetes CoCC to help formulate and bootstrap discussions
  • Bring in project maintainers from CNCF projects; possiby create a special Maintainers Circle for this topic

Open Questions

  • We would need this to be an independent body. Where would that sit?
  • can an overarching committee have sufficient visibility into project-specific context to offer quality outcomes around restoration after an incident?
  • Does a CoC action taken in one project affect a contributor’s ability to participate in other CNCF projects?
  • Escalation path for events?
  • Liability coverage for Committee decisions




--
Davanum Srinivas :: https://twitter.com/dims


Re: CNCF Code of Conduct Community of Practice?

Scott Rigby
 

a few days late to the party...
Paris, 💯 to this
Dims, 👍 to designing in collaboration with the community
xo


On Thu, May 19, 2022 at 1:08 AM Davanum Srinivas <davanum@...> wrote:
Joanna,

Quick note on something I touched on when we chatted at dinner.

Here's the relevant section as pointed out by Paris below (pasting the same url here for your reference):
https://github.com/cncf/foundation/blob/main/charter.md#13-code-of-conduct

The text as it stands today says two things:
Point #1 -  "All participants agree to abide by The Linux Foundation Code of Conduct available at https://events.linuxfoundation.org/code-of-conduct."
Point #2 - "The TOC may vote to adopt its own code of conduct for the CNCF community."

Our Charter clearly puts "code of conduct for the CNCF community" in the hands of the TOC (says so right there!), just writing one is not enough and any Code of Conduct needs to be enforced for it to have any effect, So we will look at options to design this properly in collaboration with the community which this Code of Conduct will end up governing!

thanks,
Dims

On Tue, May 17, 2022 at 12:40 PM Paris Pittman <paris.pittman@...> wrote:

Hi TOC and community,


 I believe we are at a point where a CNCF code of conduct community of practice will serve us well. I sat on the first Kubernetes Code of Conduct committee and many of the below ideas stemmed from my experiences there. Whether this is a body, community of practice, incident management team, etc is all up for discussion.


Would it be possible to put this on the next TOC agenda? If folks are interested in this work and at KubeCon, give a shout; even if you’re virtual, I’m hanging on CNCF Slack. 


-paris 


To help get the ball rolling for discussion, here are some rough ideas:

https://github.com/cncf/foundation/blob/main/charter.md#13-code-of-conduct


Purpose

Create a community of practice around code of conduct matters at the CNCF Community level. This community of practice could be bootstrapped by an independant committee, a working group of TAG Contributor Strategy, or another organizational design that TOC thinks would position this group for success with the ultimate goal of an independent body. This doc is not intended to be implementation details but the establishment of such a community.

Goals

  • community members creating policy and carrying out enforcement
  • creating a safe space for reporters
  • Focus on mediation rather than ligitation. goals of having a community member/body take reports vs CNCF staff and lawyers. 
  • cncf community members, project contributors, toc, ambassadors, and cncf staff would have this as a resource
  • build trust via community involvement and transparency reporting 

NonGoals

  • require changes to projects that already have defined code of conduct systems in place that aren’t LF support; eg Kubernetes Code of Conduct Committee

Knowns

  • Kubernetes has a code of conduct committee. It was created independently due to scale, our values, and desire for a community run program. https://github.com/kubernetes/community/blob/master/committee-code-of-conduct/bootstrapping-process.md
  • OpenTelemetry’s GC acts as a CoCC.
  • All other projects, which are governed by CNCF staff, go to Chris A or Priyanka as first step
  • CNCF Staff consults with laywers to enforce their code of conduct; this is seen as a power differential in the community; “a business approach”
  • Most CoC language on LF sites are geared towards events and not other situations or related conduct matters
  • There have been issues in the past with community members confused on where to file issues, who enforces, and where/when at cloud native related events. Example: If its “kubecon” does that mean conduct@...?

Responsibilities and Composition

  • Nominations from TOC and community; TOC shortlist for qualifications; community votes
  • everyone gets training
  • initial group bootstraps the function
    • build out policies and procedures that fit with the ecosystem
    • create roles and teams
    • create a charter

Opportunities

  • Allows CNCF staff to focus on project operations and membership vs mediating community challenges and incidents. Instead puts mediation and enforcement into the community. 
  • focus on mediation vs litigation.
  • incident management and transparecy reporting //build out an incident management team
  • projects can plug into this with better incident reporting structures than contact someone an attorney at Linux Foundation
  • projects can have liasion reps which can then feed into staffing for incident response groups

Next Steps

  • Discuss at a TOC meeting
  • Bring in current and emeritus Kubernetes CoCC to help formulate and bootstrap discussions
  • Bring in project maintainers from CNCF projects; possiby create a special Maintainers Circle for this topic

Open Questions

  • We would need this to be an independent body. Where would that sit?
  • can an overarching committee have sufficient visibility into project-specific context to offer quality outcomes around restoration after an incident?
  • Does a CoC action taken in one project affect a contributor’s ability to participate in other CNCF projects?
  • Escalation path for events?
  • Liability coverage for Committee decisions




--
Davanum Srinivas :: https://twitter.com/dims


Re: [cncf-gb] Update on Code of Conduct process improvements

Brandon Lum
 

This is awesome and going to be really helpful! Looking forward to this!


On Thu, May 19, 2022, 9:50 PM Davanum Srinivas <davanum@...> wrote:
Folks,

FYI, This is happening!!! yay!

thanks,
Dims

---------- Forwarded message ---------
From: Gupta, Arun <arun.gupta@...>
Date: Thu, May 19, 2022 at 4:39 PM
Subject: [cncf-gb] Update on Code of Conduct process improvements
To: cncf-gb <cncf-gb@...>


Governing Board members,

 

A collaborative effort is underway to improve and better document our processes for responding to Code of Conduct incidents across all projects within CNCF.  We're committed to ensuring that incidents are resolved in a clear, consistent, fair, equitable, and transparent manner. Today we want to provide you all with an update on how we intend to move forward.

 

Members of The Linux Foundation staff, The Cloud Native Computing Foundation staff, CNCF Governing Board and Technical Oversight Committee, the Kubernetes Steering, and Kubernetes Code of Conduct Committees met today to discuss lessons learned from past incidents and proposed improvements to the CNCF code of conduct incident response processes.

 

Today's conversation is only a preliminary step.  We have a lot of work ahead of us, and we'll provide updates to the community on a regular basis.  Be on the lookout for more information in the weeks ahead, including opportunities to review and provide feedback on the proposals we're working on.  We want to make sure all voices are heard.

 

Thank you all for your patience with us.  We are all growing and learning together, and are committed to supporting community health and safety as we continue on this journey together.

 

Sincerely,

CNCF Governing Board & Technical Oversight Committee

 



--
Davanum Srinivas :: https://twitter.com/dims


[cncf-gb] Update on Code of Conduct process improvements

Davanum Srinivas
 

Folks,

FYI, This is happening!!! yay!

thanks,
Dims

---------- Forwarded message ---------
From: Gupta, Arun <arun.gupta@...>
Date: Thu, May 19, 2022 at 4:39 PM
Subject: [cncf-gb] Update on Code of Conduct process improvements
To: cncf-gb <cncf-gb@...>


Governing Board members,

 

A collaborative effort is underway to improve and better document our processes for responding to Code of Conduct incidents across all projects within CNCF.  We're committed to ensuring that incidents are resolved in a clear, consistent, fair, equitable, and transparent manner. Today we want to provide you all with an update on how we intend to move forward.

 

Members of The Linux Foundation staff, The Cloud Native Computing Foundation staff, CNCF Governing Board and Technical Oversight Committee, the Kubernetes Steering, and Kubernetes Code of Conduct Committees met today to discuss lessons learned from past incidents and proposed improvements to the CNCF code of conduct incident response processes.

 

Today's conversation is only a preliminary step.  We have a lot of work ahead of us, and we'll provide updates to the community on a regular basis.  Be on the lookout for more information in the weeks ahead, including opportunities to review and provide feedback on the proposals we're working on.  We want to make sure all voices are heard.

 

Thank you all for your patience with us.  We are all growing and learning together, and are committed to supporting community health and safety as we continue on this journey together.

 

Sincerely,

CNCF Governing Board & Technical Oversight Committee

 



--
Davanum Srinivas :: https://twitter.com/dims


Re: LFX Mentorship '22 Summer Semester

Nate Waddington
 

Hello everyone,

just to follow up on this conversation, here is the timeline update announcement: https://github.com/cncf/mentoring/discussions/632#discussioncomment-2782420

This reopens the summer semester for project ideas: https://github.com/cncf/mentoring/tree/main/lfx-mentorship/2022/02-Summer - please open a PR if you'd like your project to participate!

Cheers,
Nate.


Re: LFX Mentorship '22 Summer Semester

Nate Waddington
 

Hi Oleg,

Sorry for my delayed response. I'm open to extending the key dates here.

If we extend the cut-off date (which is already well past), I think we should also extend the application cut-off date to give folks a chance to reconsider their applications.

Suggested timeline updates:
    •    mentorships available on LFX Mentorship: May 8th, 2021 (no change)
    •    proposals cutoff May 24th
    •    applications open: May 9th - May 29th
    •    application review/admission decisions/HR paperwork: May 31st - June 3rd

I don't want this update to push out the end date of the term; I think it's likely OK to have a slightly shorter term if it means we can have more projects participating.

Cheers,
Nate


Re: CNCF Code of Conduct Community of Practice?

Davanum Srinivas
 

Joanna,

Quick note on something I touched on when we chatted at dinner.

Here's the relevant section as pointed out by Paris below (pasting the same url here for your reference):
https://github.com/cncf/foundation/blob/main/charter.md#13-code-of-conduct

The text as it stands today says two things:
Point #1 -  "All participants agree to abide by The Linux Foundation Code of Conduct available at https://events.linuxfoundation.org/code-of-conduct."
Point #2 - "The TOC may vote to adopt its own code of conduct for the CNCF community."

Our Charter clearly puts "code of conduct for the CNCF community" in the hands of the TOC (says so right there!), just writing one is not enough and any Code of Conduct needs to be enforced for it to have any effect, So we will look at options to design this properly in collaboration with the community which this Code of Conduct will end up governing!

thanks,
Dims

On Tue, May 17, 2022 at 12:40 PM Paris Pittman <paris.pittman@...> wrote:

Hi TOC and community,


 I believe we are at a point where a CNCF code of conduct community of practice will serve us well. I sat on the first Kubernetes Code of Conduct committee and many of the below ideas stemmed from my experiences there. Whether this is a body, community of practice, incident management team, etc is all up for discussion.


Would it be possible to put this on the next TOC agenda? If folks are interested in this work and at KubeCon, give a shout; even if you’re virtual, I’m hanging on CNCF Slack. 


-paris 


To help get the ball rolling for discussion, here are some rough ideas:

https://github.com/cncf/foundation/blob/main/charter.md#13-code-of-conduct


Purpose

Create a community of practice around code of conduct matters at the CNCF Community level. This community of practice could be bootstrapped by an independant committee, a working group of TAG Contributor Strategy, or another organizational design that TOC thinks would position this group for success with the ultimate goal of an independent body. This doc is not intended to be implementation details but the establishment of such a community.

Goals

  • community members creating policy and carrying out enforcement
  • creating a safe space for reporters
  • Focus on mediation rather than ligitation. goals of having a community member/body take reports vs CNCF staff and lawyers. 
  • cncf community members, project contributors, toc, ambassadors, and cncf staff would have this as a resource
  • build trust via community involvement and transparency reporting 

NonGoals

  • require changes to projects that already have defined code of conduct systems in place that aren’t LF support; eg Kubernetes Code of Conduct Committee

Knowns

  • Kubernetes has a code of conduct committee. It was created independently due to scale, our values, and desire for a community run program. https://github.com/kubernetes/community/blob/master/committee-code-of-conduct/bootstrapping-process.md
  • OpenTelemetry’s GC acts as a CoCC.
  • All other projects, which are governed by CNCF staff, go to Chris A or Priyanka as first step
  • CNCF Staff consults with laywers to enforce their code of conduct; this is seen as a power differential in the community; “a business approach”
  • Most CoC language on LF sites are geared towards events and not other situations or related conduct matters
  • There have been issues in the past with community members confused on where to file issues, who enforces, and where/when at cloud native related events. Example: If its “kubecon” does that mean conduct@...?

Responsibilities and Composition

  • Nominations from TOC and community; TOC shortlist for qualifications; community votes
  • everyone gets training
  • initial group bootstraps the function
    • build out policies and procedures that fit with the ecosystem
    • create roles and teams
    • create a charter

Opportunities

  • Allows CNCF staff to focus on project operations and membership vs mediating community challenges and incidents. Instead puts mediation and enforcement into the community. 
  • focus on mediation vs litigation.
  • incident management and transparecy reporting //build out an incident management team
  • projects can plug into this with better incident reporting structures than contact someone an attorney at Linux Foundation
  • projects can have liasion reps which can then feed into staffing for incident response groups

Next Steps

  • Discuss at a TOC meeting
  • Bring in current and emeritus Kubernetes CoCC to help formulate and bootstrap discussions
  • Bring in project maintainers from CNCF projects; possiby create a special Maintainers Circle for this topic

Open Questions

  • We would need this to be an independent body. Where would that sit?
  • can an overarching committee have sufficient visibility into project-specific context to offer quality outcomes around restoration after an incident?
  • Does a CoC action taken in one project affect a contributor’s ability to participate in other CNCF projects?
  • Escalation path for events?
  • Liability coverage for Committee decisions




--
Davanum Srinivas :: https://twitter.com/dims


Re: CNCF Code of Conduct Community of Practice?

Joe Beda
 

I want to echo my support for this effort. Thank you for introducing it, Paris.  Setting community standards and enforcing them is a key part of making our ecosystem work and I believe it is critical that this happens from the community itself.  In doing so, we can hold all parties in the community to the same standard.

Joe

On Wed, May 18, 2022 at 12:47 AM Davanum Srinivas <davanum@...> wrote:
Paris,

thanks for the note to the TOC and the community. 

+1 to the principles behind it for sure. Let's figure out how to work together and get ideas/consensus from multiple folks and ensure that this works for all of us.

We will happily set aside time on the TOC agenda for sure to get the ball rolling when we get back from kubecon.

Thanks
-- Dims
(wearing TOC chair hat)

On Tue, May 17, 2022 at 12:40 PM Paris Pittman <paris.pittman@...> wrote:

Hi TOC and community,


 I believe we are at a point where a CNCF code of conduct community of practice will serve us well. I sat on the first Kubernetes Code of Conduct committee and many of the below ideas stemmed from my experiences there. Whether this is a body, community of practice, incident management team, etc is all up for discussion.


Would it be possible to put this on the next TOC agenda? If folks are interested in this work and at KubeCon, give a shout; even if you’re virtual, I’m hanging on CNCF Slack. 


-paris 


To help get the ball rolling for discussion, here are some rough ideas:

https://github.com/cncf/foundation/blob/main/charter.md#13-code-of-conduct


Purpose

Create a community of practice around code of conduct matters at the CNCF Community level. This community of practice could be bootstrapped by an independant committee, a working group of TAG Contributor Strategy, or another organizational design that TOC thinks would position this group for success with the ultimate goal of an independent body. This doc is not intended to be implementation details but the establishment of such a community.

Goals

  • community members creating policy and carrying out enforcement
  • creating a safe space for reporters
  • Focus on mediation rather than ligitation. goals of having a community member/body take reports vs CNCF staff and lawyers. 
  • cncf community members, project contributors, toc, ambassadors, and cncf staff would have this as a resource
  • build trust via community involvement and transparency reporting 

NonGoals

  • require changes to projects that already have defined code of conduct systems in place that aren’t LF support; eg Kubernetes Code of Conduct Committee

Knowns

  • Kubernetes has a code of conduct committee. It was created independently due to scale, our values, and desire for a community run program. https://github.com/kubernetes/community/blob/master/committee-code-of-conduct/bootstrapping-process.md
  • OpenTelemetry’s GC acts as a CoCC.
  • All other projects, which are governed by CNCF staff, go to Chris A or Priyanka as first step
  • CNCF Staff consults with laywers to enforce their code of conduct; this is seen as a power differential in the community; “a business approach”
  • Most CoC language on LF sites are geared towards events and not other situations or related conduct matters
  • There have been issues in the past with community members confused on where to file issues, who enforces, and where/when at cloud native related events. Example: If its “kubecon” does that mean conduct@...?

Responsibilities and Composition

  • Nominations from TOC and community; TOC shortlist for qualifications; community votes
  • everyone gets training
  • initial group bootstraps the function
    • build out policies and procedures that fit with the ecosystem
    • create roles and teams
    • create a charter

Opportunities

  • Allows CNCF staff to focus on project operations and membership vs mediating community challenges and incidents. Instead puts mediation and enforcement into the community. 
  • focus on mediation vs litigation.
  • incident management and transparecy reporting //build out an incident management team
  • projects can plug into this with better incident reporting structures than contact someone an attorney at Linux Foundation
  • projects can have liasion reps which can then feed into staffing for incident response groups

Next Steps

  • Discuss at a TOC meeting
  • Bring in current and emeritus Kubernetes CoCC to help formulate and bootstrap discussions
  • Bring in project maintainers from CNCF projects; possiby create a special Maintainers Circle for this topic

Open Questions

  • We would need this to be an independent body. Where would that sit?
  • can an overarching committee have sufficient visibility into project-specific context to offer quality outcomes around restoration after an incident?
  • Does a CoC action taken in one project affect a contributor’s ability to participate in other CNCF projects?
  • Escalation path for events?
  • Liability coverage for Committee decisions




--
Davanum Srinivas :: https://twitter.com/dims


Re: CNCF Code of Conduct Community of Practice?

Davanum Srinivas
 

Paris,

thanks for the note to the TOC and the community. 

+1 to the principles behind it for sure. Let's figure out how to work together and get ideas/consensus from multiple folks and ensure that this works for all of us.

We will happily set aside time on the TOC agenda for sure to get the ball rolling when we get back from kubecon.

Thanks
-- Dims
(wearing TOC chair hat)


On Tue, May 17, 2022 at 12:40 PM Paris Pittman <paris.pittman@...> wrote:

Hi TOC and community,


 I believe we are at a point where a CNCF code of conduct community of practice will serve us well. I sat on the first Kubernetes Code of Conduct committee and many of the below ideas stemmed from my experiences there. Whether this is a body, community of practice, incident management team, etc is all up for discussion.


Would it be possible to put this on the next TOC agenda? If folks are interested in this work and at KubeCon, give a shout; even if you’re virtual, I’m hanging on CNCF Slack. 


-paris 


To help get the ball rolling for discussion, here are some rough ideas:

https://github.com/cncf/foundation/blob/main/charter.md#13-code-of-conduct


Purpose

Create a community of practice around code of conduct matters at the CNCF Community level. This community of practice could be bootstrapped by an independant committee, a working group of TAG Contributor Strategy, or another organizational design that TOC thinks would position this group for success with the ultimate goal of an independent body. This doc is not intended to be implementation details but the establishment of such a community.

Goals

  • community members creating policy and carrying out enforcement
  • creating a safe space for reporters
  • Focus on mediation rather than ligitation. goals of having a community member/body take reports vs CNCF staff and lawyers. 
  • cncf community members, project contributors, toc, ambassadors, and cncf staff would have this as a resource
  • build trust via community involvement and transparency reporting 

NonGoals

  • require changes to projects that already have defined code of conduct systems in place that aren’t LF support; eg Kubernetes Code of Conduct Committee

Knowns

  • Kubernetes has a code of conduct committee. It was created independently due to scale, our values, and desire for a community run program. https://github.com/kubernetes/community/blob/master/committee-code-of-conduct/bootstrapping-process.md
  • OpenTelemetry’s GC acts as a CoCC.
  • All other projects, which are governed by CNCF staff, go to Chris A or Priyanka as first step
  • CNCF Staff consults with laywers to enforce their code of conduct; this is seen as a power differential in the community; “a business approach”
  • Most CoC language on LF sites are geared towards events and not other situations or related conduct matters
  • There have been issues in the past with community members confused on where to file issues, who enforces, and where/when at cloud native related events. Example: If its “kubecon” does that mean conduct@...?

Responsibilities and Composition

  • Nominations from TOC and community; TOC shortlist for qualifications; community votes
  • everyone gets training
  • initial group bootstraps the function
    • build out policies and procedures that fit with the ecosystem
    • create roles and teams
    • create a charter

Opportunities

  • Allows CNCF staff to focus on project operations and membership vs mediating community challenges and incidents. Instead puts mediation and enforcement into the community. 
  • focus on mediation vs litigation.
  • incident management and transparecy reporting //build out an incident management team
  • projects can plug into this with better incident reporting structures than contact someone an attorney at Linux Foundation
  • projects can have liasion reps which can then feed into staffing for incident response groups

Next Steps

  • Discuss at a TOC meeting
  • Bring in current and emeritus Kubernetes CoCC to help formulate and bootstrap discussions
  • Bring in project maintainers from CNCF projects; possiby create a special Maintainers Circle for this topic

Open Questions

  • We would need this to be an independent body. Where would that sit?
  • can an overarching committee have sufficient visibility into project-specific context to offer quality outcomes around restoration after an incident?
  • Does a CoC action taken in one project affect a contributor’s ability to participate in other CNCF projects?
  • Escalation path for events?
  • Liability coverage for Committee decisions




--
Davanum Srinivas :: https://twitter.com/dims


Re: CNCF Code of Conduct Community of Practice?

Dan Shaw
 

This is great, Paris.

Seems like the right time to put this in place.

Dan Shaw
@dshaw


On Tue, May 17, 2022 at 3:40 AM Paris Pittman <paris.pittman@...> wrote:

Hi TOC and community,


 I believe we are at a point where a CNCF code of conduct community of practice will serve us well. I sat on the first Kubernetes Code of Conduct committee and many of the below ideas stemmed from my experiences there. Whether this is a body, community of practice, incident management team, etc is all up for discussion.


Would it be possible to put this on the next TOC agenda? If folks are interested in this work and at KubeCon, give a shout; even if you’re virtual, I’m hanging on CNCF Slack. 


-paris 


To help get the ball rolling for discussion, here are some rough ideas:

https://github.com/cncf/foundation/blob/main/charter.md#13-code-of-conduct


Purpose

Create a community of practice around code of conduct matters at the CNCF Community level. This community of practice could be bootstrapped by an independant committee, a working group of TAG Contributor Strategy, or another organizational design that TOC thinks would position this group for success with the ultimate goal of an independent body. This doc is not intended to be implementation details but the establishment of such a community.

Goals

  • community members creating policy and carrying out enforcement
  • creating a safe space for reporters
  • Focus on mediation rather than ligitation. goals of having a community member/body take reports vs CNCF staff and lawyers. 
  • cncf community members, project contributors, toc, ambassadors, and cncf staff would have this as a resource
  • build trust via community involvement and transparency reporting 

NonGoals

  • require changes to projects that already have defined code of conduct systems in place that aren’t LF support; eg Kubernetes Code of Conduct Committee

Knowns

  • Kubernetes has a code of conduct committee. It was created independently due to scale, our values, and desire for a community run program. https://github.com/kubernetes/community/blob/master/committee-code-of-conduct/bootstrapping-process.md
  • OpenTelemetry’s GC acts as a CoCC.
  • All other projects, which are governed by CNCF staff, go to Chris A or Priyanka as first step
  • CNCF Staff consults with laywers to enforce their code of conduct; this is seen as a power differential in the community; “a business approach”
  • Most CoC language on LF sites are geared towards events and not other situations or related conduct matters
  • There have been issues in the past with community members confused on where to file issues, who enforces, and where/when at cloud native related events. Example: If its “kubecon” does that mean conduct@...?

Responsibilities and Composition

  • Nominations from TOC and community; TOC shortlist for qualifications; community votes
  • everyone gets training
  • initial group bootstraps the function
    • build out policies and procedures that fit with the ecosystem
    • create roles and teams
    • create a charter

Opportunities

  • Allows CNCF staff to focus on project operations and membership vs mediating community challenges and incidents. Instead puts mediation and enforcement into the community. 
  • focus on mediation vs litigation.
  • incident management and transparecy reporting //build out an incident management team
  • projects can plug into this with better incident reporting structures than contact someone an attorney at Linux Foundation
  • projects can have liasion reps which can then feed into staffing for incident response groups

Next Steps

  • Discuss at a TOC meeting
  • Bring in current and emeritus Kubernetes CoCC to help formulate and bootstrap discussions
  • Bring in project maintainers from CNCF projects; possiby create a special Maintainers Circle for this topic

Open Questions

  • We would need this to be an independent body. Where would that sit?
  • can an overarching committee have sufficient visibility into project-specific context to offer quality outcomes around restoration after an incident?
  • Does a CoC action taken in one project affect a contributor’s ability to participate in other CNCF projects?
  • Escalation path for events?
  • Liability coverage for Committee decisions



Re: CNCF Code of Conduct Community of Practice?

Libby Meren
 

This is great, love it! I’d like to help too.

Sent from a teeny tiny device screen, please excuse brevity and typos.

On May 17, 2022, at 8:41 AM, Carolyn Van Slyck via lists.cncf.io <carolyn.vanslyck=microsoft.com@...> wrote:

+1 This is a great idea, and I'd like to help if I can

-----Original Message-----
From: cncf-toc@... <cncf-toc@...> On Behalf Of Josh Berkus via lists.cncf.io
Sent: Tuesday, May 17, 2022 9:27 AM
To: Paris Pittman <paris.pittman@...>; CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] CNCF Code of Conduct Community of Practice?


I believe we are at a point where a CNCF code of conduct community
of practice will serve us well. I sat on the first Kubernetes Code of
Conduct committee and many of the below ideas stemmed from my
experiences there. Whether this is a body, community of practice,
incident management team, etc is all up for discussion.
TAG-CS is, of course, happy to support.

Personally, I would be particularly interested in figuring out some kind of CoCC support for smaller projects.

--
-- Josh Berkus
Kubernetes Community Architect
OSPO, OCTO











Re: CNCF Code of Conduct Community of Practice?

Carolyn Van Slyck
 

+1 This is a great idea, and I'd like to help if I can

-----Original Message-----
From: cncf-toc@... <cncf-toc@...> On Behalf Of Josh Berkus via lists.cncf.io
Sent: Tuesday, May 17, 2022 9:27 AM
To: Paris Pittman <paris.pittman@...>; CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] CNCF Code of Conduct Community of Practice?


 I believe we are at a point where a CNCF code of conduct community
of practice will serve us well. I sat on the first Kubernetes Code of
Conduct committee and many of the below ideas stemmed from my
experiences there. Whether this is a body, community of practice,
incident management team, etc is all up for discussion.
TAG-CS is, of course, happy to support.

Personally, I would be particularly interested in figuring out some kind of CoCC support for smaller projects.

--
-- Josh Berkus
Kubernetes Community Architect
OSPO, OCTO


Re: CNCF Code of Conduct Community of Practice?

Davanum Srinivas
 

CC'ing CNCF-GB

I love it when plans from folks come together!

-- Dims


On Tue, May 17, 2022 at 12:40 PM Paris Pittman <paris.pittman@...> wrote:

Hi TOC and community,


 I believe we are at a point where a CNCF code of conduct community of practice will serve us well. I sat on the first Kubernetes Code of Conduct committee and many of the below ideas stemmed from my experiences there. Whether this is a body, community of practice, incident management team, etc is all up for discussion.


Would it be possible to put this on the next TOC agenda? If folks are interested in this work and at KubeCon, give a shout; even if you’re virtual, I’m hanging on CNCF Slack. 


-paris 


To help get the ball rolling for discussion, here are some rough ideas:

https://github.com/cncf/foundation/blob/main/charter.md#13-code-of-conduct


Purpose

Create a community of practice around code of conduct matters at the CNCF Community level. This community of practice could be bootstrapped by an independant committee, a working group of TAG Contributor Strategy, or another organizational design that TOC thinks would position this group for success with the ultimate goal of an independent body. This doc is not intended to be implementation details but the establishment of such a community.

Goals

  • community members creating policy and carrying out enforcement
  • creating a safe space for reporters
  • Focus on mediation rather than ligitation. goals of having a community member/body take reports vs CNCF staff and lawyers. 
  • cncf community members, project contributors, toc, ambassadors, and cncf staff would have this as a resource
  • build trust via community involvement and transparency reporting 

NonGoals

  • require changes to projects that already have defined code of conduct systems in place that aren’t LF support; eg Kubernetes Code of Conduct Committee

Knowns

  • Kubernetes has a code of conduct committee. It was created independently due to scale, our values, and desire for a community run program. https://github.com/kubernetes/community/blob/master/committee-code-of-conduct/bootstrapping-process.md
  • OpenTelemetry’s GC acts as a CoCC.
  • All other projects, which are governed by CNCF staff, go to Chris A or Priyanka as first step
  • CNCF Staff consults with laywers to enforce their code of conduct; this is seen as a power differential in the community; “a business approach”
  • Most CoC language on LF sites are geared towards events and not other situations or related conduct matters
  • There have been issues in the past with community members confused on where to file issues, who enforces, and where/when at cloud native related events. Example: If its “kubecon” does that mean conduct@...?

Responsibilities and Composition

  • Nominations from TOC and community; TOC shortlist for qualifications; community votes
  • everyone gets training
  • initial group bootstraps the function
    • build out policies and procedures that fit with the ecosystem
    • create roles and teams
    • create a charter

Opportunities

  • Allows CNCF staff to focus on project operations and membership vs mediating community challenges and incidents. Instead puts mediation and enforcement into the community. 
  • focus on mediation vs litigation.
  • incident management and transparecy reporting //build out an incident management team
  • projects can plug into this with better incident reporting structures than contact someone an attorney at Linux Foundation
  • projects can have liasion reps which can then feed into staffing for incident response groups

Next Steps

  • Discuss at a TOC meeting
  • Bring in current and emeritus Kubernetes CoCC to help formulate and bootstrap discussions
  • Bring in project maintainers from CNCF projects; possiby create a special Maintainers Circle for this topic

Open Questions

  • We would need this to be an independent body. Where would that sit?
  • can an overarching committee have sufficient visibility into project-specific context to offer quality outcomes around restoration after an incident?
  • Does a CoC action taken in one project affect a contributor’s ability to participate in other CNCF projects?
  • Escalation path for events?
  • Liability coverage for Committee decisions




--
Davanum Srinivas :: https://twitter.com/dims


Re: CNCF Code of Conduct Community of Practice?

Josh Berkus
 

 I believe we are at a point where a CNCF code of conduct community of practice will serve us well. I sat on the first Kubernetes Code of Conduct committee and many of the below ideas stemmed from my experiences there. Whether this is a body, community of practice, incident management team, etc is all up for discussion.
TAG-CS is, of course, happy to support.

Personally, I would be particularly interested in figuring out some kind of CoCC support for smaller projects.

--
-- Josh Berkus
Kubernetes Community Architect
OSPO, OCTO

201 - 220 of 7197