On 7/8/22 03:59, Davanum Srinivas wrote: Monday July 11th is the deadline for elected community member Approver! Please send in your nomination if you are interested in helping lead the work group efforts. What's the deadline for TAG-appointed approvers? I don't think I've seen one yet. -- -- Josh Berkus Kubernetes Community Architect OSPO, OCTO
|
|

Davanum Srinivas
Folks,
Monday July 11th is the deadline for elected community member Approver! Please send in your nomination if you are interested in helping lead the work group efforts.
thanks, -- Dims
toggle quoted message
Show quoted text
On Tue, Jun 28, 2022 at 1:02 PM Davanum Srinivas < davanum@...> wrote: Hi All, just reminding you that we are accepting nominations for the elected community member Approver for the Code of Conduct Working Group. If you are an active Incubating or Graduated Maintainer[1] and would like to run for the elected community member Approver, please notify Taylor Waggoner (twaggoner AT linuxfoundation.org) by July 11, 2022. As explained in more detail in our recent blog post regarding the new working group structure[2], the runner up will serve as an alternate Approver with eligibility to be promoted to primary Approver. Additionally, Incubating & Graduated Maintainers are also welcome to serve as Reviewers. Thanks, Dims [1] https://maintainers.cncf.io/ [2] https://www.cncf.io/blog/2022/06/23/new-structure-for-cncf-code-of-conduct-update-project/On Thu, Jun 23, 2022 at 10:59 AM Davanum Srinivas < davanum@...> wrote: Folks,
Please see the 2 blog posts that went public just now, Many thanks to all the folks who helped shape both the Interim CoCC structure (for the short term) and the shape of the new WG for CoCC updates (for the longer term)
We welcome feedback on both from everyone for sure (possibly cncf-toc mailing list would be a good place to have our public back-and-forth as needed). But feel free to reach out publicly or privately to folks involved.
Thanks, CNCF TOC Chair and CNCF GB Chair
PS: I am posting this as Arun is on a plane! Bon voyage Arun. PPS: apologies for posting to a mix of public and private lists!
--
--
|
|

Davanum Srinivas
Hi All, just reminding you that we are accepting nominations for the elected community member Approver for the Code of Conduct Working Group. If you are an active Incubating or Graduated Maintainer[1] and would like to run for the elected community member Approver, please notify Taylor Waggoner (twaggoner AT linuxfoundation.org) by July 11, 2022. As explained in more detail in our recent blog post regarding the new working group structure[2], the runner up will serve as an alternate Approver with eligibility to be promoted to primary Approver. Additionally, Incubating & Graduated Maintainers are also welcome to serve as Reviewers. Thanks, Dims [1] https://maintainers.cncf.io/ [2] https://www.cncf.io/blog/2022/06/23/new-structure-for-cncf-code-of-conduct-update-project/
toggle quoted message
Show quoted text
On Thu, Jun 23, 2022 at 10:59 AM Davanum Srinivas < davanum@...> wrote: Folks,
Please see the 2 blog posts that went public just now, Many thanks to all the folks who helped shape both the Interim CoCC structure (for the short term) and the shape of the new WG for CoCC updates (for the longer term)
We welcome feedback on both from everyone for sure (possibly cncf-toc mailing list would be a good place to have our public back-and-forth as needed). But feel free to reach out publicly or privately to folks involved.
Thanks, CNCF TOC Chair and CNCF GB Chair
PS: I am posting this as Arun is on a plane! Bon voyage Arun. PPS: apologies for posting to a mix of public and private lists!
--
|
|
Thanks Dim and everyone in the TOC and at the foundation for listening to the community and taking our feedback. Sent from a teeny tiny device screen, please excuse brevity and typos.
toggle quoted message
Show quoted text
On Jun 23, 2022, at 6:37 PM, Davanum Srinivas <davanum@...> wrote:
Paris,
We now have a service desk ticket to get the interim cocc group for the upcoming otter tech workshop! Thanks for the nudge.
-- Dims On Thu, Jun 23, 2022 at 1:29 PM Erin Boyd < eboyd@...> wrote:
Yes we will be handling incidents in the queue during the interim period. I would greatly appreciate any information you can share with us! Thank you, Paris!!! Erin thanks to folks stepping up.
will the interim committee work on incidents in the pipeline or start fresh from this date on? where do folks report incidents/get in contact with this new body?
ottertech and consent academy have trainings that folks on the interim cocc can utilize for this work if you are new to a body like this. we’ve used ottertech with new k8s cocc folks in the past. On Thu, Jun 23, 2022 at 10:03 AM Jessie Adams-Shore < jessie@...> wrote: Thanks, Phil. The year has been updated :)
On Thu, Jun 23, 2022 at 12:47 PM Phil Estes < estesp@...> wrote: Thanks Dims and others who have worked on this. Very minor typo in blog #2; a date is listed as July 11, 2020; I assume that is 2022 :)
Thanks! - Phil
On Thu, Jun 23, 2022 at 10:59 AM Davanum Srinivas < davanum@...> wrote: Folks,
Please see the 2 blog posts that went public just now, Many thanks to all the folks who helped shape both the Interim CoCC structure (for the short term) and the shape of the new WG for CoCC updates (for the longer term)
We welcome feedback on both from everyone for sure (possibly cncf-toc mailing list would be a good place to have our public back-and-forth as needed). But feel free to reach out publicly or privately to folks involved.
Thanks, CNCF TOC Chair and CNCF GB Chair
PS: I am posting this as Arun is on a plane! Bon voyage Arun. PPS: apologies for posting to a mix of public and private lists!
--
--
Jessie Adams ShorePR | Cloud Native Computing Foundation 707-337-1958
--
Erin A. Boyd
Director of Emerging Technologies OCTO Distinguished Engineer
Red Hat
eboyd@...
--
|
|

Davanum Srinivas
Paris,
We now have a service desk ticket to get the interim cocc group for the upcoming otter tech workshop! Thanks for the nudge.
-- Dims
toggle quoted message
Show quoted text
On Thu, Jun 23, 2022 at 1:29 PM Erin Boyd < eboyd@...> wrote:
Yes we will be handling incidents in the queue during the interim period. I would greatly appreciate any information you can share with us! Thank you, Paris!!! Erin thanks to folks stepping up.
will the interim committee work on incidents in the pipeline or start fresh from this date on? where do folks report incidents/get in contact with this new body?
ottertech and consent academy have trainings that folks on the interim cocc can utilize for this work if you are new to a body like this. we’ve used ottertech with new k8s cocc folks in the past. On Thu, Jun 23, 2022 at 10:03 AM Jessie Adams-Shore < jessie@...> wrote: Thanks, Phil. The year has been updated :)
On Thu, Jun 23, 2022 at 12:47 PM Phil Estes < estesp@...> wrote: Thanks Dims and others who have worked on this. Very minor typo in blog #2; a date is listed as July 11, 2020; I assume that is 2022 :)
Thanks! - Phil
On Thu, Jun 23, 2022 at 10:59 AM Davanum Srinivas < davanum@...> wrote: Folks,
Please see the 2 blog posts that went public just now, Many thanks to all the folks who helped shape both the Interim CoCC structure (for the short term) and the shape of the new WG for CoCC updates (for the longer term)
We welcome feedback on both from everyone for sure (possibly cncf-toc mailing list would be a good place to have our public back-and-forth as needed). But feel free to reach out publicly or privately to folks involved.
Thanks, CNCF TOC Chair and CNCF GB Chair
PS: I am posting this as Arun is on a plane! Bon voyage Arun. PPS: apologies for posting to a mix of public and private lists!
--
--
Jessie Adams ShorePR | Cloud Native Computing Foundation 707-337-1958
--
Erin A. Boyd
Director of Emerging Technologies OCTO Distinguished Engineer
Red Hat
eboyd@...
|
|

Davanum Srinivas
toggle quoted message
Show quoted text
is there a mailing list i can use to reach out to the group about details?
how will you all handle conflicts of interest if and when they arise? On Thu, Jun 23, 2022 at 10:29 AM Erin Boyd < eboyd@...> wrote:
Yes we will be handling incidents in the queue during the interim period. I would greatly appreciate any information you can share with us! Thank you, Paris!!! Erin thanks to folks stepping up.
will the interim committee work on incidents in the pipeline or start fresh from this date on? where do folks report incidents/get in contact with this new body?
ottertech and consent academy have trainings that folks on the interim cocc can utilize for this work if you are new to a body like this. we’ve used ottertech with new k8s cocc folks in the past. On Thu, Jun 23, 2022 at 10:03 AM Jessie Adams-Shore < jessie@...> wrote: Thanks, Phil. The year has been updated :)
On Thu, Jun 23, 2022 at 12:47 PM Phil Estes < estesp@...> wrote: Thanks Dims and others who have worked on this. Very minor typo in blog #2; a date is listed as July 11, 2020; I assume that is 2022 :)
Thanks! - Phil
On Thu, Jun 23, 2022 at 10:59 AM Davanum Srinivas < davanum@...> wrote: Folks,
Please see the 2 blog posts that went public just now, Many thanks to all the folks who helped shape both the Interim CoCC structure (for the short term) and the shape of the new WG for CoCC updates (for the longer term)
We welcome feedback on both from everyone for sure (possibly cncf-toc mailing list would be a good place to have our public back-and-forth as needed). But feel free to reach out publicly or privately to folks involved.
Thanks, CNCF TOC Chair and CNCF GB Chair
PS: I am posting this as Arun is on a plane! Bon voyage Arun. PPS: apologies for posting to a mix of public and private lists!
--
--
Jessie Adams ShorePR | Cloud Native Computing Foundation 707-337-1958
--
Erin A. Boyd
Director of Emerging Technologies OCTO Distinguished Engineer
Red Hat
eboyd@...
|
|
is there a mailing list i can use to reach out to the group about details?
how will you all handle conflicts of interest if and when they arise?
toggle quoted message
Show quoted text
On Thu, Jun 23, 2022 at 10:29 AM Erin Boyd < eboyd@...> wrote:
Yes we will be handling incidents in the queue during the interim period. I would greatly appreciate any information you can share with us! Thank you, Paris!!! Erin thanks to folks stepping up.
will the interim committee work on incidents in the pipeline or start fresh from this date on? where do folks report incidents/get in contact with this new body?
ottertech and consent academy have trainings that folks on the interim cocc can utilize for this work if you are new to a body like this. we’ve used ottertech with new k8s cocc folks in the past. On Thu, Jun 23, 2022 at 10:03 AM Jessie Adams-Shore < jessie@...> wrote: Thanks, Phil. The year has been updated :)
On Thu, Jun 23, 2022 at 12:47 PM Phil Estes < estesp@...> wrote: Thanks Dims and others who have worked on this. Very minor typo in blog #2; a date is listed as July 11, 2020; I assume that is 2022 :)
Thanks! - Phil
On Thu, Jun 23, 2022 at 10:59 AM Davanum Srinivas < davanum@...> wrote: Folks,
Please see the 2 blog posts that went public just now, Many thanks to all the folks who helped shape both the Interim CoCC structure (for the short term) and the shape of the new WG for CoCC updates (for the longer term)
We welcome feedback on both from everyone for sure (possibly cncf-toc mailing list would be a good place to have our public back-and-forth as needed). But feel free to reach out publicly or privately to folks involved.
Thanks, CNCF TOC Chair and CNCF GB Chair
PS: I am posting this as Arun is on a plane! Bon voyage Arun. PPS: apologies for posting to a mix of public and private lists!
--
--
Jessie Adams ShorePR | Cloud Native Computing Foundation 707-337-1958
--
Erin A. Boyd
Director of Emerging Technologies OCTO Distinguished Engineer
Red Hat
eboyd@...
|
|
Yes we will be handling incidents in the queue during the interim period. I would greatly appreciate any information you can share with us! Thank you, Paris!!! Erin
toggle quoted message
Show quoted text
thanks to folks stepping up.
will the interim committee work on incidents in the pipeline or start fresh from this date on? where do folks report incidents/get in contact with this new body?
ottertech and consent academy have trainings that folks on the interim cocc can utilize for this work if you are new to a body like this. we’ve used ottertech with new k8s cocc folks in the past. On Thu, Jun 23, 2022 at 10:03 AM Jessie Adams-Shore < jessie@...> wrote: Thanks, Phil. The year has been updated :)
On Thu, Jun 23, 2022 at 12:47 PM Phil Estes < estesp@...> wrote: Thanks Dims and others who have worked on this. Very minor typo in blog #2; a date is listed as July 11, 2020; I assume that is 2022 :)
Thanks! - Phil
On Thu, Jun 23, 2022 at 10:59 AM Davanum Srinivas < davanum@...> wrote: Folks,
Please see the 2 blog posts that went public just now, Many thanks to all the folks who helped shape both the Interim CoCC structure (for the short term) and the shape of the new WG for CoCC updates (for the longer term)
We welcome feedback on both from everyone for sure (possibly cncf-toc mailing list would be a good place to have our public back-and-forth as needed). But feel free to reach out publicly or privately to folks involved.
Thanks, CNCF TOC Chair and CNCF GB Chair
PS: I am posting this as Arun is on a plane! Bon voyage Arun. PPS: apologies for posting to a mix of public and private lists!
--
--
Jessie Adams ShorePR | Cloud Native Computing Foundation 707-337-1958
--
Erin A. Boyd
Director of Emerging Technologies OCTO Distinguished Engineer
Red Hat
eboyd@...
|
|
thanks to folks stepping up.
will the interim committee work on incidents in the pipeline or start fresh from this date on? where do folks report incidents/get in contact with this new body?
ottertech and consent academy have trainings that folks on the interim cocc can utilize for this work if you are new to a body like this. we’ve used ottertech with new k8s cocc folks in the past.
toggle quoted message
Show quoted text
On Thu, Jun 23, 2022 at 10:03 AM Jessie Adams-Shore < jessie@...> wrote: Thanks, Phil. The year has been updated :)
On Thu, Jun 23, 2022 at 12:47 PM Phil Estes < estesp@...> wrote: Thanks Dims and others who have worked on this. Very minor typo in blog #2; a date is listed as July 11, 2020; I assume that is 2022 :)
Thanks! - Phil
On Thu, Jun 23, 2022 at 10:59 AM Davanum Srinivas < davanum@...> wrote: Folks,
Please see the 2 blog posts that went public just now, Many thanks to all the folks who helped shape both the Interim CoCC structure (for the short term) and the shape of the new WG for CoCC updates (for the longer term)
We welcome feedback on both from everyone for sure (possibly cncf-toc mailing list would be a good place to have our public back-and-forth as needed). But feel free to reach out publicly or privately to folks involved.
Thanks, CNCF TOC Chair and CNCF GB Chair
PS: I am posting this as Arun is on a plane! Bon voyage Arun. PPS: apologies for posting to a mix of public and private lists!
--
--
Jessie Adams ShorePR | Cloud Native Computing Foundation 707-337-1958
|
|
Jessie Adams-Shore <jessie@...>
Thanks, Phil. The year has been updated :)
toggle quoted message
Show quoted text
On Thu, Jun 23, 2022 at 12:47 PM Phil Estes < estesp@...> wrote: Thanks Dims and others who have worked on this. Very minor typo in blog #2; a date is listed as July 11, 2020; I assume that is 2022 :)
Thanks! - Phil
On Thu, Jun 23, 2022 at 10:59 AM Davanum Srinivas < davanum@...> wrote: Folks,
Please see the 2 blog posts that went public just now, Many thanks to all the folks who helped shape both the Interim CoCC structure (for the short term) and the shape of the new WG for CoCC updates (for the longer term)
We welcome feedback on both from everyone for sure (possibly cncf-toc mailing list would be a good place to have our public back-and-forth as needed). But feel free to reach out publicly or privately to folks involved.
Thanks, CNCF TOC Chair and CNCF GB Chair
PS: I am posting this as Arun is on a plane! Bon voyage Arun. PPS: apologies for posting to a mix of public and private lists!
--
-- Jessie Adams ShorePR | Cloud Native Computing Foundation 707-337-1958
|
|

Phil Estes
Thanks Dims and others who have worked on this. Very minor typo in blog #2; a date is listed as July 11, 2020; I assume that is 2022 :)
Thanks! - Phil
toggle quoted message
Show quoted text
On Thu, Jun 23, 2022 at 10:59 AM Davanum Srinivas < davanum@...> wrote: Folks,
Please see the 2 blog posts that went public just now, Many thanks to all the folks who helped shape both the Interim CoCC structure (for the short term) and the shape of the new WG for CoCC updates (for the longer term)
We welcome feedback on both from everyone for sure (possibly cncf-toc mailing list would be a good place to have our public back-and-forth as needed). But feel free to reach out publicly or privately to folks involved.
Thanks, CNCF TOC Chair and CNCF GB Chair
PS: I am posting this as Arun is on a plane! Bon voyage Arun. PPS: apologies for posting to a mix of public and private lists!
--
|
|
On 6/23/22 07:59, Davanum Srinivas wrote: Please see the 2 blog posts that went public just now, Many thanks to all the folks who helped shape both the Interim CoCC structure (for the short term) and the shape of the new WG for CoCC updates (for the longer term)
Thank you for incorporating all of the community input into this plan. -- -- Josh Berkus Kubernetes Community Architect OSPO, OCTO
|
|
I confess to reading this as "Arun is on a planet" .. and became concerned that we may be over-reaching...
Thank you all very much for doing this work
alexis
toggle quoted message
Show quoted text
On Thu, Jun 23, 2022 at 3:59 PM Davanum Srinivas <davanum@...> wrote: Folks,
Please see the 2 blog posts that went public just now, Many thanks to all the folks who helped shape both the Interim CoCC structure (for the short term) and the shape of the new WG for CoCC updates (for the longer term)
Blog post #1 : This one talks about who is in the Interim CoCC (including alternates/policies) - https://www.cncf.io/blog/2022/06/23/cncfs-interim-cncf-code-of-conduct-committee-has-launched/
Blog post #2 : We had earlier published a blog post on June 6th and we got a lot of feedback from our overall community, so we incorporated the feedback to be more open/inclusive, this WG will help draft what/how of the CoCC in the longer term - https://www.cncf.io/blog/2022/06/23/new-structure-for-cncf-code-of-conduct-update-project/
We welcome feedback on both from everyone for sure (possibly cncf-toc mailing list would be a good place to have our public back-and-forth as needed). But feel free to reach out publicly or privately to folks involved.
Thanks, CNCF TOC Chair and CNCF GB Chair
PS: I am posting this as Arun is on a plane! Bon voyage Arun. PPS: apologies for posting to a mix of public and private lists!
-- Davanum Srinivas :: https://twitter.com/dims
|
|

Davanum Srinivas
Folks,
Please see the 2 blog posts that went public just now, Many thanks to all the folks who helped shape both the Interim CoCC structure (for the short term) and the shape of the new WG for CoCC updates (for the longer term)
We welcome feedback on both from everyone for sure (possibly cncf-toc mailing list would be a good place to have our public back-and-forth as needed). But feel free to reach out publicly or privately to folks involved.
Thanks, CNCF TOC Chair and CNCF GB Chair
PS: I am posting this as Arun is on a plane! Bon voyage Arun. PPS: apologies for posting to a mix of public and private lists!
--
|
|