CNCF SIG Contributor Experience Proposal


Paris Pittman <parispittman@...>
 

Hi TOC and community,

I'm watching the emails fly by re: maintainer things so figured no time like the present to send this start of a proposal along. I've been working on it for a few weeks and getting input. I think I'm a first-time poster, very-long-time lurker to this list, hello! 

I recently stepped back from my role as co-chair for Kubernetes Contributor Experience Special Interest Group that I held for 2 years. Sarah Novotny, Brian Grant, Phil Wittrock and many(!) others decided that a place for intentional contributor community building was necessary and I'm glad they did. I believe it's the secret sauce but yes - I'm bias. :)

A group like this[1] could help many stakeholders, as outlined in this work-in-progress doc, including engaging the end user community in new ways, and current cncf projects that don't have a ContribEx/CommComm (nod to nodejs). It's important to note in the out-of-scope section, this group isn't going to do the work for your project but will help you get there and learn together. I've spoken to some TOC members and many project maintainers about this. 

Notes:
  • This is a pretty broad charter that should absolutely be trimmed down after formation, discovery, and some other kick off activities. 
  • Left broad as most of the work will depend on the known gaps and the contributors/community members who step forward to help with them.

paris

[1] https://docs.google.com/document/d/1UYIp55jsEn7hSGHOh4sXXx_VnqPL0E0upsWCUZB5Tn8/edit?usp=sharing 






--

Paris Pittman

Kubernetes Community

Open Source Strategy, Google Cloud

345 Spear Street, San Francisco, 94105



Matt Klein
 

Big +1 from me. Very excited to see this SIG form as I think this is an area that many projects struggle with. The projects that don't struggle with this have some very overworked maintainers. ;)


On Fri, Jan 17, 2020 at 2:49 PM Paris Pittman via Lists.Cncf.Io <parispittman=google.com@...> wrote:
Hi TOC and community,

I'm watching the emails fly by re: maintainer things so figured no time like the present to send this start of a proposal along. I've been working on it for a few weeks and getting input. I think I'm a first-time poster, very-long-time lurker to this list, hello! 

I recently stepped back from my role as co-chair for Kubernetes Contributor Experience Special Interest Group that I held for 2 years. Sarah Novotny, Brian Grant, Phil Wittrock and many(!) others decided that a place for intentional contributor community building was necessary and I'm glad they did. I believe it's the secret sauce but yes - I'm bias. :)

A group like this[1] could help many stakeholders, as outlined in this work-in-progress doc, including engaging the end user community in new ways, and current cncf projects that don't have a ContribEx/CommComm (nod to nodejs). It's important to note in the out-of-scope section, this group isn't going to do the work for your project but will help you get there and learn together. I've spoken to some TOC members and many project maintainers about this. 

Notes:
  • This is a pretty broad charter that should absolutely be trimmed down after formation, discovery, and some other kick off activities. 
  • Left broad as most of the work will depend on the known gaps and the contributors/community members who step forward to help with them.

paris

[1] https://docs.google.com/document/d/1UYIp55jsEn7hSGHOh4sXXx_VnqPL0E0upsWCUZB5Tn8/edit?usp=sharing 






--

Paris Pittman

Kubernetes Community

Open Source Strategy, Google Cloud

345 Spear Street, San Francisco, 94105



Lee Calcote
 

+1 NB. This SIG stands to benefit all projects, and hopefully, help recognize all types of contributors (non-code). I’d like to see a contributor ladder come forth here.

- Lee

On Jan 17, 2020, at 4:48 PM, Paris Pittman via Lists.Cncf.Io <parispittman=google.com@...> wrote:

Hi TOC and community,

I'm watching the emails fly by re: maintainer things so figured no time like the present to send this start of a proposal along. I've been working on it for a few weeks and getting input. I think I'm a first-time poster, very-long-time lurker to this list, hello! 

I recently stepped back from my role as co-chair for Kubernetes Contributor Experience Special Interest Group that I held for 2 years. Sarah Novotny, Brian Grant, Phil Wittrock and many(!) others decided that a place for intentional contributor community building was necessary and I'm glad they did. I believe it's the secret sauce but yes - I'm bias. :)

A group like this[1] could help many stakeholders, as outlined in this work-in-progress doc, including engaging the end user community in new ways, and current cncf projects that don't have a ContribEx/CommComm (nod to nodejs). It's important to note in the out-of-scope section, this group isn't going to do the work for your project but will help you get there and learn together. I've spoken to some TOC members and many project maintainers about this. 

Notes:
  • This is a pretty broad charter that should absolutely be trimmed down after formation, discovery, and some other kick off activities. 
  • Left broad as most of the work will depend on the known gaps and the contributors/community members who step forward to help with them.

paris

[1] https://docs.google.com/document/d/1UYIp55jsEn7hSGHOh4sXXx_VnqPL0E0upsWCUZB5Tn8/edit?usp=sharing 






--

Paris Pittman
Kubernetes Community
Open Source Strategy, Google Cloud
345 Spear Street, San Francisco, 94105



Ricardo Aravena
 

+1 nb

I think healthy projects have to have happy maintainers and contributors to thrive long-term. Also, part of that is for them to feel genuinely welcomed and included.



On Fri, Jan 17, 2020, 6:51 PM Lee Calcote <leecalcote@...> wrote:
+1 NB. This SIG stands to benefit all projects, and hopefully, help recognize all types of contributors (non-code). I’d like to see a contributor ladder come forth here.

- Lee

On Jan 17, 2020, at 4:48 PM, Paris Pittman via Lists.Cncf.Io <parispittman=google.com@...> wrote:

Hi TOC and community,

I'm watching the emails fly by re: maintainer things so figured no time like the present to send this start of a proposal along. I've been working on it for a few weeks and getting input. I think I'm a first-time poster, very-long-time lurker to this list, hello! 

I recently stepped back from my role as co-chair for Kubernetes Contributor Experience Special Interest Group that I held for 2 years. Sarah Novotny, Brian Grant, Phil Wittrock and many(!) others decided that a place for intentional contributor community building was necessary and I'm glad they did. I believe it's the secret sauce but yes - I'm bias. :)

A group like this[1] could help many stakeholders, as outlined in this work-in-progress doc, including engaging the end user community in new ways, and current cncf projects that don't have a ContribEx/CommComm (nod to nodejs). It's important to note in the out-of-scope section, this group isn't going to do the work for your project but will help you get there and learn together. I've spoken to some TOC members and many project maintainers about this. 

Notes:
  • This is a pretty broad charter that should absolutely be trimmed down after formation, discovery, and some other kick off activities. 
  • Left broad as most of the work will depend on the known gaps and the contributors/community members who step forward to help with them.

paris

[1] https://docs.google.com/document/d/1UYIp55jsEn7hSGHOh4sXXx_VnqPL0E0upsWCUZB5Tn8/edit?usp=sharing 






--

Paris Pittman
Kubernetes Community
Open Source Strategy, Google Cloud
345 Spear Street, San Francisco, 94105



Paris Pittman <parispittman@...>
 

Thanks TOC and community members for your time today on the call and support via mailing list. 

Next steps: smooth out the charter and have interested folks step forward to help bootstrap. after, TOC vote/review later on. 
doodle poll[1] for those who are interested. looking forward to this!

paris 




On Sat, Jan 18, 2020 at 11:00 AM Ricardo Aravena <raravena80@...> wrote:
+1 nb

I think healthy projects have to have happy maintainers and contributors to thrive long-term. Also, part of that is for them to feel genuinely welcomed and included.



On Fri, Jan 17, 2020, 6:51 PM Lee Calcote <leecalcote@...> wrote:
+1 NB. This SIG stands to benefit all projects, and hopefully, help recognize all types of contributors (non-code). I’d like to see a contributor ladder come forth here.

- Lee

On Jan 17, 2020, at 4:48 PM, Paris Pittman via Lists.Cncf.Io <parispittman=google.com@...> wrote:

Hi TOC and community,

I'm watching the emails fly by re: maintainer things so figured no time like the present to send this start of a proposal along. I've been working on it for a few weeks and getting input. I think I'm a first-time poster, very-long-time lurker to this list, hello! 

I recently stepped back from my role as co-chair for Kubernetes Contributor Experience Special Interest Group that I held for 2 years. Sarah Novotny, Brian Grant, Phil Wittrock and many(!) others decided that a place for intentional contributor community building was necessary and I'm glad they did. I believe it's the secret sauce but yes - I'm bias. :)

A group like this[1] could help many stakeholders, as outlined in this work-in-progress doc, including engaging the end user community in new ways, and current cncf projects that don't have a ContribEx/CommComm (nod to nodejs). It's important to note in the out-of-scope section, this group isn't going to do the work for your project but will help you get there and learn together. I've spoken to some TOC members and many project maintainers about this. 

Notes:
  • This is a pretty broad charter that should absolutely be trimmed down after formation, discovery, and some other kick off activities. 
  • Left broad as most of the work will depend on the known gaps and the contributors/community members who step forward to help with them.

paris

[1] https://docs.google.com/document/d/1UYIp55jsEn7hSGHOh4sXXx_VnqPL0E0upsWCUZB5Tn8/edit?usp=sharing 






--

Paris Pittman
Kubernetes Community
Open Source Strategy, Google Cloud
345 Spear Street, San Francisco, 94105




--

Paris Pittman

Kubernetes Community

Open Source Strategy, Google Cloud

345 Spear Street, San Francisco, 94105



Matt Farina
 

Paris,

On the call today you suggested pairing down the scope of the SIG because there is so much proposed. It occured to me that contributing to the CNCF can mean a lot of things. To large areas are contributions to SIGs and to projects. In your opinion, should the SIG initially be limited to one area of focus (and if so which one) or to focus on both?

For those not familiar... CNCF SIGs are a little different from Kubernetes SIGs.  Kubernetes SIGs own and are responsible for code within Kubernetes. CNCF SIGs are an extension of the TOC:

The CNCF TOC Special Interest Groups scale contributions by the CNCF technical and user community, while retaining integrity and increasing quality in support of our mission.

Each project has their own governance model and contribution process. Where Kubernetes SIGs have a solid line or ownership to Kubernetes code, CNCF TOC SIGs have a dotted line relationship to CNCF Projects who own the code and governance. The dotted line relationship means that projects do work with and connect to a SIG but the ownership model is different.

Regards,
Matt

On Tue, Jan 21, 2020, at 12:09 PM, Paris Pittman via Lists.Cncf.Io wrote:
Thanks TOC and community members for your time today on the call and support via mailing list. 

Next steps: smooth out the charter and have interested folks step forward to help bootstrap. after, TOC vote/review later on. 
doodle poll[1] for those who are interested. looking forward to this!

paris 




On Sat, Jan 18, 2020 at 11:00 AM Ricardo Aravena <raravena80@...> wrote:
+1 nb

I think healthy projects have to have happy maintainers and contributors to thrive long-term. Also, part of that is for them to feel genuinely welcomed and included.



On Fri, Jan 17, 2020, 6:51 PM Lee Calcote <leecalcote@...> wrote:
+1 NB. This SIG stands to benefit all projects, and hopefully, help recognize all types of contributors (non-code). I’d like to see a contributor ladder come forth here.

- Lee

On Jan 17, 2020, at 4:48 PM, Paris Pittman via Lists.Cncf.Io <parispittman=google.com@...> wrote:

Hi TOC and community,

I'm watching the emails fly by re: maintainer things so figured no time like the present to send this start of a proposal along. I've been working on it for a few weeks and getting input. I think I'm a first-time poster, very-long-time lurker to this list, hello! 

I recently stepped back from my role as co-chair for Kubernetes Contributor Experience Special Interest Group that I held for 2 years. Sarah Novotny, Brian Grant, Phil Wittrock and many(!) others decided that a place for intentional contributor community building was necessary and I'm glad they did. I believe it's the secret sauce but yes - I'm bias. :)

A group like this[1] could help many stakeholders, as outlined in this work-in-progress doc, including engaging the end user community in new ways, and current cncf projects that don't have a ContribEx/CommComm (nod to nodejs). It's important to note in the out-of-scope section, this group isn't going to do the work for your project but will help you get there and learn together. I've spoken to some TOC members and many project maintainers about this. 

Notes:
  • This is a pretty broad charter that should absolutely be trimmed down after formation, discovery, and some other kick off activities. 
  • Left broad as most of the work will depend on the known gaps and the contributors/community members who step forward to help with them.

paris






--


Paris Pittman
Kubernetes Community
Open Source Strategy, Google Cloud
345 Spear Street, San Francisco, 94105






--


Paris Pittman

Kubernetes Community

Open Source Strategy, Google Cloud

345 Spear Street, San Francisco, 94105




alexis richardson
 

Good summary Matt!

Paris, just wanted to say thanks for your presentation today. 

A


On Tue, 21 Jan 2020, 18:17 Matt Farina, <matt@...> wrote:
Paris,

On the call today you suggested pairing down the scope of the SIG because there is so much proposed. It occured to me that contributing to the CNCF can mean a lot of things. To large areas are contributions to SIGs and to projects. In your opinion, should the SIG initially be limited to one area of focus (and if so which one) or to focus on both?

For those not familiar... CNCF SIGs are a little different from Kubernetes SIGs.  Kubernetes SIGs own and are responsible for code within Kubernetes. CNCF SIGs are an extension of the TOC:

The CNCF TOC Special Interest Groups scale contributions by the CNCF technical and user community, while retaining integrity and increasing quality in support of our mission.

Each project has their own governance model and contribution process. Where Kubernetes SIGs have a solid line or ownership to Kubernetes code, CNCF TOC SIGs have a dotted line relationship to CNCF Projects who own the code and governance. The dotted line relationship means that projects do work with and connect to a SIG but the ownership model is different.

Regards,
Matt

On Tue, Jan 21, 2020, at 12:09 PM, Paris Pittman via Lists.Cncf.Io wrote:
Thanks TOC and community members for your time today on the call and support via mailing list. 

Next steps: smooth out the charter and have interested folks step forward to help bootstrap. after, TOC vote/review later on. 
doodle poll[1] for those who are interested. looking forward to this!

paris 




On Sat, Jan 18, 2020 at 11:00 AM Ricardo Aravena <raravena80@...> wrote:
+1 nb

I think healthy projects have to have happy maintainers and contributors to thrive long-term. Also, part of that is for them to feel genuinely welcomed and included.



On Fri, Jan 17, 2020, 6:51 PM Lee Calcote <leecalcote@...> wrote:
+1 NB. This SIG stands to benefit all projects, and hopefully, help recognize all types of contributors (non-code). I’d like to see a contributor ladder come forth here.

- Lee

On Jan 17, 2020, at 4:48 PM, Paris Pittman via Lists.Cncf.Io <parispittman=google.com@...> wrote:

Hi TOC and community,

I'm watching the emails fly by re: maintainer things so figured no time like the present to send this start of a proposal along. I've been working on it for a few weeks and getting input. I think I'm a first-time poster, very-long-time lurker to this list, hello! 

I recently stepped back from my role as co-chair for Kubernetes Contributor Experience Special Interest Group that I held for 2 years. Sarah Novotny, Brian Grant, Phil Wittrock and many(!) others decided that a place for intentional contributor community building was necessary and I'm glad they did. I believe it's the secret sauce but yes - I'm bias. :)

A group like this[1] could help many stakeholders, as outlined in this work-in-progress doc, including engaging the end user community in new ways, and current cncf projects that don't have a ContribEx/CommComm (nod to nodejs). It's important to note in the out-of-scope section, this group isn't going to do the work for your project but will help you get there and learn together. I've spoken to some TOC members and many project maintainers about this. 

Notes:
  • This is a pretty broad charter that should absolutely be trimmed down after formation, discovery, and some other kick off activities. 
  • Left broad as most of the work will depend on the known gaps and the contributors/community members who step forward to help with them.

paris






--


Paris Pittman
Kubernetes Community
Open Source Strategy, Google Cloud
345 Spear Street, San Francisco, 94105






--


Paris Pittman

Kubernetes Community

Open Source Strategy, Google Cloud

345 Spear Street, San Francisco, 94105




Kris Nova <kris.nova@...>
 

Great presentation today - where can I sign up? We need this SIG ASAP. 

+1 NB


On Tue, Jan 21, 2020 at 11:19 AM alexis richardson <alexis@...> wrote:
Good summary Matt!

Paris, just wanted to say thanks for your presentation today. 

A


On Tue, 21 Jan 2020, 18:17 Matt Farina, <matt@...> wrote:
Paris,

On the call today you suggested pairing down the scope of the SIG because there is so much proposed. It occured to me that contributing to the CNCF can mean a lot of things. To large areas are contributions to SIGs and to projects. In your opinion, should the SIG initially be limited to one area of focus (and if so which one) or to focus on both?

For those not familiar... CNCF SIGs are a little different from Kubernetes SIGs.  Kubernetes SIGs own and are responsible for code within Kubernetes. CNCF SIGs are an extension of the TOC:

The CNCF TOC Special Interest Groups scale contributions by the CNCF technical and user community, while retaining integrity and increasing quality in support of our mission.

Each project has their own governance model and contribution process. Where Kubernetes SIGs have a solid line or ownership to Kubernetes code, CNCF TOC SIGs have a dotted line relationship to CNCF Projects who own the code and governance. The dotted line relationship means that projects do work with and connect to a SIG but the ownership model is different.

Regards,
Matt

On Tue, Jan 21, 2020, at 12:09 PM, Paris Pittman via Lists.Cncf.Io wrote:
Thanks TOC and community members for your time today on the call and support via mailing list. 

Next steps: smooth out the charter and have interested folks step forward to help bootstrap. after, TOC vote/review later on. 
doodle poll[1] for those who are interested. looking forward to this!

paris 




On Sat, Jan 18, 2020 at 11:00 AM Ricardo Aravena <raravena80@...> wrote:
+1 nb

I think healthy projects have to have happy maintainers and contributors to thrive long-term. Also, part of that is for them to feel genuinely welcomed and included.



On Fri, Jan 17, 2020, 6:51 PM Lee Calcote <leecalcote@...> wrote:
+1 NB. This SIG stands to benefit all projects, and hopefully, help recognize all types of contributors (non-code). I’d like to see a contributor ladder come forth here.

- Lee

On Jan 17, 2020, at 4:48 PM, Paris Pittman via Lists.Cncf.Io <parispittman=google.com@...> wrote:

Hi TOC and community,

I'm watching the emails fly by re: maintainer things so figured no time like the present to send this start of a proposal along. I've been working on it for a few weeks and getting input. I think I'm a first-time poster, very-long-time lurker to this list, hello! 

I recently stepped back from my role as co-chair for Kubernetes Contributor Experience Special Interest Group that I held for 2 years. Sarah Novotny, Brian Grant, Phil Wittrock and many(!) others decided that a place for intentional contributor community building was necessary and I'm glad they did. I believe it's the secret sauce but yes - I'm bias. :)

A group like this[1] could help many stakeholders, as outlined in this work-in-progress doc, including engaging the end user community in new ways, and current cncf projects that don't have a ContribEx/CommComm (nod to nodejs). It's important to note in the out-of-scope section, this group isn't going to do the work for your project but will help you get there and learn together. I've spoken to some TOC members and many project maintainers about this. 

Notes:
  • This is a pretty broad charter that should absolutely be trimmed down after formation, discovery, and some other kick off activities. 
  • Left broad as most of the work will depend on the known gaps and the contributors/community members who step forward to help with them.

paris






--


Paris Pittman
Kubernetes Community
Open Source Strategy, Google Cloud
345 Spear Street, San Francisco, 94105






--


Paris Pittman

Kubernetes Community

Open Source Strategy, Google Cloud

345 Spear Street, San Francisco, 94105





--
Kris Nova
Chief Open Source Advocate


85 2nd Street
San Francisco, CA 94105


Gerred Dillon
 

+1 NB this is the most important SIG in Kubernetes. I know this isn't the right thread for my followup, but since chairs are confirmed by the TOC I immediately +1 Paris as a co-chair, if she is nominated, as a chair for this SIG. In short, she kicks the llama's ass (I haven't asked the WinAMP llama how they feel about this) and not only is the best person for this role, will also find fantastic successors to this role. Thanks, Paris, for driving this.

On Tue, Jan 21, 2020 at 2:26 PM Kris Nova <kris.nova@...> wrote:
Great presentation today - where can I sign up? We need this SIG ASAP. 

+1 NB

On Tue, Jan 21, 2020 at 11:19 AM alexis richardson <alexis@...> wrote:
Good summary Matt!

Paris, just wanted to say thanks for your presentation today. 

A


On Tue, 21 Jan 2020, 18:17 Matt Farina, <matt@...> wrote:
Paris,

On the call today you suggested pairing down the scope of the SIG because there is so much proposed. It occured to me that contributing to the CNCF can mean a lot of things. To large areas are contributions to SIGs and to projects. In your opinion, should the SIG initially be limited to one area of focus (and if so which one) or to focus on both?

For those not familiar... CNCF SIGs are a little different from Kubernetes SIGs.  Kubernetes SIGs own and are responsible for code within Kubernetes. CNCF SIGs are an extension of the TOC:

The CNCF TOC Special Interest Groups scale contributions by the CNCF technical and user community, while retaining integrity and increasing quality in support of our mission.

Each project has their own governance model and contribution process. Where Kubernetes SIGs have a solid line or ownership to Kubernetes code, CNCF TOC SIGs have a dotted line relationship to CNCF Projects who own the code and governance. The dotted line relationship means that projects do work with and connect to a SIG but the ownership model is different.

Regards,
Matt

On Tue, Jan 21, 2020, at 12:09 PM, Paris Pittman via Lists.Cncf.Io wrote:
Thanks TOC and community members for your time today on the call and support via mailing list. 

Next steps: smooth out the charter and have interested folks step forward to help bootstrap. after, TOC vote/review later on. 
doodle poll[1] for those who are interested. looking forward to this!

paris 




On Sat, Jan 18, 2020 at 11:00 AM Ricardo Aravena <raravena80@...> wrote:
+1 nb

I think healthy projects have to have happy maintainers and contributors to thrive long-term. Also, part of that is for them to feel genuinely welcomed and included.



On Fri, Jan 17, 2020, 6:51 PM Lee Calcote <leecalcote@...> wrote:
+1 NB. This SIG stands to benefit all projects, and hopefully, help recognize all types of contributors (non-code). I’d like to see a contributor ladder come forth here.

- Lee

On Jan 17, 2020, at 4:48 PM, Paris Pittman via Lists.Cncf.Io <parispittman=google.com@...> wrote:

Hi TOC and community,

I'm watching the emails fly by re: maintainer things so figured no time like the present to send this start of a proposal along. I've been working on it for a few weeks and getting input. I think I'm a first-time poster, very-long-time lurker to this list, hello! 

I recently stepped back from my role as co-chair for Kubernetes Contributor Experience Special Interest Group that I held for 2 years. Sarah Novotny, Brian Grant, Phil Wittrock and many(!) others decided that a place for intentional contributor community building was necessary and I'm glad they did. I believe it's the secret sauce but yes - I'm bias. :)

A group like this[1] could help many stakeholders, as outlined in this work-in-progress doc, including engaging the end user community in new ways, and current cncf projects that don't have a ContribEx/CommComm (nod to nodejs). It's important to note in the out-of-scope section, this group isn't going to do the work for your project but will help you get there and learn together. I've spoken to some TOC members and many project maintainers about this. 

Notes:
  • This is a pretty broad charter that should absolutely be trimmed down after formation, discovery, and some other kick off activities. 
  • Left broad as most of the work will depend on the known gaps and the contributors/community members who step forward to help with them.

paris






--


Paris Pittman
Kubernetes Community
Open Source Strategy, Google Cloud
345 Spear Street, San Francisco, 94105






--


Paris Pittman

Kubernetes Community

Open Source Strategy, Google Cloud

345 Spear Street, San Francisco, 94105





--
Kris Nova
Chief Open Source Advocate


85 2nd Street
San Francisco, CA 94105


Roger Klorese
 

Yes please! +1 NB

Roger B.A. Klorese (they/them or he/him)
Senior Product Manager
SUSE

255 King Street Suite 800
Seattle WA 98104
(P)+1 206.217.7432
(M)+1 425.444.5493
roger.klorese@...
Schedule a meeting: https://doodle.com/RogerKlorese
GPG Key: D567 F186 A6AE D244 067E  95E4 E67D 019F 0670 D9CC


On Jan 21, 2020, at 11:46 AM, Gerred Dillon <hello@...> wrote:


+1 NB this is the most important SIG in Kubernetes. I know this isn't the right thread for my followup, but since chairs are confirmed by the TOC I immediately +1 Paris as a co-chair, if she is nominated, as a chair for this SIG. In short, she kicks the llama's ass (I haven't asked the WinAMP llama how they feel about this) and not only is the best person for this role, will also find fantastic successors to this role. Thanks, Paris, for driving this.

On Tue, Jan 21, 2020 at 2:26 PM Kris Nova <kris.nova@...> wrote:
Great presentation today - where can I sign up? We need this SIG ASAP. 

+1 NB

On Tue, Jan 21, 2020 at 11:19 AM alexis richardson <alexis@...> wrote:
Good summary Matt!

Paris, just wanted to say thanks for your presentation today. 

A


On Tue, 21 Jan 2020, 18:17 Matt Farina, <matt@...> wrote:
Paris,

On the call today you suggested pairing down the scope of the SIG because there is so much proposed. It occured to me that contributing to the CNCF can mean a lot of things. To large areas are contributions to SIGs and to projects. In your opinion, should the SIG initially be limited to one area of focus (and if so which one) or to focus on both?

For those not familiar... CNCF SIGs are a little different from Kubernetes SIGs.  Kubernetes SIGs own and are responsible for code within Kubernetes. CNCF SIGs are an extension of the TOC:

The CNCF TOC Special Interest Groups scale contributions by the CNCF technical and user community, while retaining integrity and increasing quality in support of our mission.

Each project has their own governance model and contribution process. Where Kubernetes SIGs have a solid line or ownership to Kubernetes code, CNCF TOC SIGs have a dotted line relationship to CNCF Projects who own the code and governance. The dotted line relationship means that projects do work with and connect to a SIG but the ownership model is different.

Regards,
Matt

On Tue, Jan 21, 2020, at 12:09 PM, Paris Pittman via Lists.Cncf.Io wrote:
Thanks TOC and community members for your time today on the call and support via mailing list. 

Next steps: smooth out the charter and have interested folks step forward to help bootstrap. after, TOC vote/review later on. 
doodle poll[1] for those who are interested. looking forward to this!

paris 




On Sat, Jan 18, 2020 at 11:00 AM Ricardo Aravena <raravena80@...> wrote:
+1 nb

I think healthy projects have to have happy maintainers and contributors to thrive long-term. Also, part of that is for them to feel genuinely welcomed and included.



On Fri, Jan 17, 2020, 6:51 PM Lee Calcote <leecalcote@...> wrote:
+1 NB. This SIG stands to benefit all projects, and hopefully, help recognize all types of contributors (non-code). I’d like to see a contributor ladder come forth here.

- Lee

On Jan 17, 2020, at 4:48 PM, Paris Pittman via Lists.Cncf.Io <parispittman=google.com@...> wrote:

Hi TOC and community,

I'm watching the emails fly by re: maintainer things so figured no time like the present to send this start of a proposal along. I've been working on it for a few weeks and getting input. I think I'm a first-time poster, very-long-time lurker to this list, hello! 

I recently stepped back from my role as co-chair for Kubernetes Contributor Experience Special Interest Group that I held for 2 years. Sarah Novotny, Brian Grant, Phil Wittrock and many(!) others decided that a place for intentional contributor community building was necessary and I'm glad they did. I believe it's the secret sauce but yes - I'm bias. :)

A group like this[1] could help many stakeholders, as outlined in this work-in-progress doc, including engaging the end user community in new ways, and current cncf projects that don't have a ContribEx/CommComm (nod to nodejs). It's important to note in the out-of-scope section, this group isn't going to do the work for your project but will help you get there and learn together. I've spoken to some TOC members and many project maintainers about this. 

Notes:
  • This is a pretty broad charter that should absolutely be trimmed down after formation, discovery, and some other kick off activities. 
  • Left broad as most of the work will depend on the known gaps and the contributors/community members who step forward to help with them.

paris






--


Paris Pittman
Kubernetes Community
Open Source Strategy, Google Cloud
345 Spear Street, San Francisco, 94105






--


Paris Pittman

Kubernetes Community

Open Source Strategy, Google Cloud

345 Spear Street, San Francisco, 94105





--
Kris Nova
Chief Open Source Advocate


85 2nd Street
San Francisco, CA 94105


Nicola Marco Decandia
 

+1 NB

 

Thanks

 

--- 

/var/folders/t9/633c27117zl1dfcw0dkx1cw00000gn/T/com.microsoft.Outlook/Content.MSO/814E4D66.tmp 

Nicola Marco Decandia
Desotech S.r.l.

+39.0803105224 | +39.3404191066 | n.decandia@...

https://www.desotech.it

Altamura - Roma - Milano

 


Leonardo Di Donato
 

+1 nb
L.


On Wed, Jan 22, 2020 at 3:20 PM Nicola Marco Decandia <n.decandia@...> wrote:

+1 NB

 

Thanks

 

--- 

/var/folders/t9/633c27117zl1dfcw0dkx1cw00000gn/T/com.microsoft.Outlook/Content.MSO/814E4D66.tmp 

Nicola Marco Decandia
Desotech S.r.l.

+39.0803105224 | +39.3404191066 | n.decandia@...

https://www.desotech.it

Altamura - Roma - Milano

 


Jeremy Rickard
 

+1 NB, this is great! 

On Fri, Jan 17, 2020 at 2:49 PM Paris Pittman via Lists.Cncf.Io <parispittman=google.com@...> wrote:
Hi TOC and community,

I'm watching the emails fly by re: maintainer things so figured no time like the present to send this start of a proposal along. I've been working on it for a few weeks and getting input. I think I'm a first-time poster, very-long-time lurker to this list, hello! 

I recently stepped back from my role as co-chair for Kubernetes Contributor Experience Special Interest Group that I held for 2 years. Sarah Novotny, Brian Grant, Phil Wittrock and many(!) others decided that a place for intentional contributor community building was necessary and I'm glad they did. I believe it's the secret sauce but yes - I'm bias. :)

A group like this[1] could help many stakeholders, as outlined in this work-in-progress doc, including engaging the end user community in new ways, and current cncf projects that don't have a ContribEx/CommComm (nod to nodejs). It's important to note in the out-of-scope section, this group isn't going to do the work for your project but will help you get there and learn together. I've spoken to some TOC members and many project maintainers about this. 

Notes:
  • This is a pretty broad charter that should absolutely be trimmed down after formation, discovery, and some other kick off activities. 
  • Left broad as most of the work will depend on the known gaps and the contributors/community members who step forward to help with them.

paris


Stephen Augustus
 

Huge +1 to the proposal and echoing Gerred's sentiment for Paris as a Chair if/when this forms.

SIG ContribEx is _one of_ the most important SIGs in Kubernetes and Paris has been an absolute force there.

We'd be lucky to have her affecting change on the CNCF SIG level! :)

-- Stephen

On Tue, Jan 21, 2020, 14:45 Gerred Dillon <hello@...> wrote:
+1 NB this is the most important SIG in Kubernetes. I know this isn't the right thread for my followup, but since chairs are confirmed by the TOC I immediately +1 Paris as a co-chair, if she is nominated, as a chair for this SIG. In short, she kicks the llama's ass (I haven't asked the WinAMP llama how they feel about this) and not only is the best person for this role, will also find fantastic successors to this role. Thanks, Paris, for driving this.

On Tue, Jan 21, 2020 at 2:26 PM Kris Nova <kris.nova@...> wrote:
Great presentation today - where can I sign up? We need this SIG ASAP. 

+1 NB

On Tue, Jan 21, 2020 at 11:19 AM alexis richardson <alexis@...> wrote:
Good summary Matt!

Paris, just wanted to say thanks for your presentation today. 

A


On Tue, 21 Jan 2020, 18:17 Matt Farina, <matt@...> wrote:
Paris,

On the call today you suggested pairing down the scope of the SIG because there is so much proposed. It occured to me that contributing to the CNCF can mean a lot of things. To large areas are contributions to SIGs and to projects. In your opinion, should the SIG initially be limited to one area of focus (and if so which one) or to focus on both?

For those not familiar... CNCF SIGs are a little different from Kubernetes SIGs.  Kubernetes SIGs own and are responsible for code within Kubernetes. CNCF SIGs are an extension of the TOC:

The CNCF TOC Special Interest Groups scale contributions by the CNCF technical and user community, while retaining integrity and increasing quality in support of our mission.

Each project has their own governance model and contribution process. Where Kubernetes SIGs have a solid line or ownership to Kubernetes code, CNCF TOC SIGs have a dotted line relationship to CNCF Projects who own the code and governance. The dotted line relationship means that projects do work with and connect to a SIG but the ownership model is different.

Regards,
Matt

On Tue, Jan 21, 2020, at 12:09 PM, Paris Pittman via Lists.Cncf.Io wrote:
Thanks TOC and community members for your time today on the call and support via mailing list. 

Next steps: smooth out the charter and have interested folks step forward to help bootstrap. after, TOC vote/review later on. 
doodle poll[1] for those who are interested. looking forward to this!

paris 




On Sat, Jan 18, 2020 at 11:00 AM Ricardo Aravena <raravena80@...> wrote:
+1 nb

I think healthy projects have to have happy maintainers and contributors to thrive long-term. Also, part of that is for them to feel genuinely welcomed and included.



On Fri, Jan 17, 2020, 6:51 PM Lee Calcote <leecalcote@...> wrote:
+1 NB. This SIG stands to benefit all projects, and hopefully, help recognize all types of contributors (non-code). I’d like to see a contributor ladder come forth here.

- Lee

On Jan 17, 2020, at 4:48 PM, Paris Pittman via Lists.Cncf.Io <parispittman=google.com@...> wrote:

Hi TOC and community,

I'm watching the emails fly by re: maintainer things so figured no time like the present to send this start of a proposal along. I've been working on it for a few weeks and getting input. I think I'm a first-time poster, very-long-time lurker to this list, hello! 

I recently stepped back from my role as co-chair for Kubernetes Contributor Experience Special Interest Group that I held for 2 years. Sarah Novotny, Brian Grant, Phil Wittrock and many(!) others decided that a place for intentional contributor community building was necessary and I'm glad they did. I believe it's the secret sauce but yes - I'm bias. :)

A group like this[1] could help many stakeholders, as outlined in this work-in-progress doc, including engaging the end user community in new ways, and current cncf projects that don't have a ContribEx/CommComm (nod to nodejs). It's important to note in the out-of-scope section, this group isn't going to do the work for your project but will help you get there and learn together. I've spoken to some TOC members and many project maintainers about this. 

Notes:
  • This is a pretty broad charter that should absolutely be trimmed down after formation, discovery, and some other kick off activities. 
  • Left broad as most of the work will depend on the known gaps and the contributors/community members who step forward to help with them.

paris






--


Paris Pittman
Kubernetes Community
Open Source Strategy, Google Cloud
345 Spear Street, San Francisco, 94105






--


Paris Pittman

Kubernetes Community

Open Source Strategy, Google Cloud

345 Spear Street, San Francisco, 94105





--
Kris Nova
Chief Open Source Advocate


85 2nd Street
San Francisco, CA 94105


Igor Mameshin
 

+1 NB

Thank you,
Igor

--
Igor Mameshin · CTO · Agile Stacks, Inc · Mobile: 858.229.7358 · igor@...



On Wed, Jan 22, 2020 at 9:00 PM Stephen Augustus <Stephen@...> wrote:
Huge +1 to the proposal and echoing Gerred's sentiment for Paris as a Chair if/when this forms.

SIG ContribEx is _one of_ the most important SIGs in Kubernetes and Paris has been an absolute force there.

We'd be lucky to have her affecting change on the CNCF SIG level! :)

-- Stephen

On Tue, Jan 21, 2020, 14:45 Gerred Dillon <hello@...> wrote:
+1 NB this is the most important SIG in Kubernetes. I know this isn't the right thread for my followup, but since chairs are confirmed by the TOC I immediately +1 Paris as a co-chair, if she is nominated, as a chair for this SIG. In short, she kicks the llama's ass (I haven't asked the WinAMP llama how they feel about this) and not only is the best person for this role, will also find fantastic successors to this role. Thanks, Paris, for driving this.

On Tue, Jan 21, 2020 at 2:26 PM Kris Nova <kris.nova@...> wrote:
Great presentation today - where can I sign up? We need this SIG ASAP. 

+1 NB

On Tue, Jan 21, 2020 at 11:19 AM alexis richardson <alexis@...> wrote:
Good summary Matt!

Paris, just wanted to say thanks for your presentation today. 

A


On Tue, 21 Jan 2020, 18:17 Matt Farina, <matt@...> wrote:
Paris,

On the call today you suggested pairing down the scope of the SIG because there is so much proposed. It occured to me that contributing to the CNCF can mean a lot of things. To large areas are contributions to SIGs and to projects. In your opinion, should the SIG initially be limited to one area of focus (and if so which one) or to focus on both?

For those not familiar... CNCF SIGs are a little different from Kubernetes SIGs.  Kubernetes SIGs own and are responsible for code within Kubernetes. CNCF SIGs are an extension of the TOC:

The CNCF TOC Special Interest Groups scale contributions by the CNCF technical and user community, while retaining integrity and increasing quality in support of our mission.

Each project has their own governance model and contribution process. Where Kubernetes SIGs have a solid line or ownership to Kubernetes code, CNCF TOC SIGs have a dotted line relationship to CNCF Projects who own the code and governance. The dotted line relationship means that projects do work with and connect to a SIG but the ownership model is different.

Regards,
Matt

On Tue, Jan 21, 2020, at 12:09 PM, Paris Pittman via Lists.Cncf.Io wrote:
Thanks TOC and community members for your time today on the call and support via mailing list. 

Next steps: smooth out the charter and have interested folks step forward to help bootstrap. after, TOC vote/review later on. 
doodle poll[1] for those who are interested. looking forward to this!

paris 




On Sat, Jan 18, 2020 at 11:00 AM Ricardo Aravena <raravena80@...> wrote:
+1 nb

I think healthy projects have to have happy maintainers and contributors to thrive long-term. Also, part of that is for them to feel genuinely welcomed and included.



On Fri, Jan 17, 2020, 6:51 PM Lee Calcote <leecalcote@...> wrote:
+1 NB. This SIG stands to benefit all projects, and hopefully, help recognize all types of contributors (non-code). I’d like to see a contributor ladder come forth here.

- Lee

On Jan 17, 2020, at 4:48 PM, Paris Pittman via Lists.Cncf.Io <parispittman=google.com@...> wrote:

Hi TOC and community,

I'm watching the emails fly by re: maintainer things so figured no time like the present to send this start of a proposal along. I've been working on it for a few weeks and getting input. I think I'm a first-time poster, very-long-time lurker to this list, hello! 

I recently stepped back from my role as co-chair for Kubernetes Contributor Experience Special Interest Group that I held for 2 years. Sarah Novotny, Brian Grant, Phil Wittrock and many(!) others decided that a place for intentional contributor community building was necessary and I'm glad they did. I believe it's the secret sauce but yes - I'm bias. :)

A group like this[1] could help many stakeholders, as outlined in this work-in-progress doc, including engaging the end user community in new ways, and current cncf projects that don't have a ContribEx/CommComm (nod to nodejs). It's important to note in the out-of-scope section, this group isn't going to do the work for your project but will help you get there and learn together. I've spoken to some TOC members and many project maintainers about this. 

Notes:
  • This is a pretty broad charter that should absolutely be trimmed down after formation, discovery, and some other kick off activities. 
  • Left broad as most of the work will depend on the known gaps and the contributors/community members who step forward to help with them.

paris






--


Paris Pittman
Kubernetes Community
Open Source Strategy, Google Cloud
345 Spear Street, San Francisco, 94105






--


Paris Pittman

Kubernetes Community

Open Source Strategy, Google Cloud

345 Spear Street, San Francisco, 94105





--
Kris Nova
Chief Open Source Advocate


85 2nd Street
San Francisco, CA 94105


Pengfei Ni
 

+1 NB


Best regards.


---
Pengfei Ni



Igor Mameshin <igor@...> 于2020年1月23日周四 下午1:07写道:

+1 NB

Thank you,
Igor

--
Igor Mameshin · CTO · Agile Stacks, Inc · Mobile: 858.229.7358 · igor@...



On Wed, Jan 22, 2020 at 9:00 PM Stephen Augustus <Stephen@...> wrote:
Huge +1 to the proposal and echoing Gerred's sentiment for Paris as a Chair if/when this forms.

SIG ContribEx is _one of_ the most important SIGs in Kubernetes and Paris has been an absolute force there.

We'd be lucky to have her affecting change on the CNCF SIG level! :)

-- Stephen

On Tue, Jan 21, 2020, 14:45 Gerred Dillon <hello@...> wrote:
+1 NB this is the most important SIG in Kubernetes. I know this isn't the right thread for my followup, but since chairs are confirmed by the TOC I immediately +1 Paris as a co-chair, if she is nominated, as a chair for this SIG. In short, she kicks the llama's ass (I haven't asked the WinAMP llama how they feel about this) and not only is the best person for this role, will also find fantastic successors to this role. Thanks, Paris, for driving this.

On Tue, Jan 21, 2020 at 2:26 PM Kris Nova <kris.nova@...> wrote:
Great presentation today - where can I sign up? We need this SIG ASAP. 

+1 NB

On Tue, Jan 21, 2020 at 11:19 AM alexis richardson <alexis@...> wrote:
Good summary Matt!

Paris, just wanted to say thanks for your presentation today. 

A


On Tue, 21 Jan 2020, 18:17 Matt Farina, <matt@...> wrote:
Paris,

On the call today you suggested pairing down the scope of the SIG because there is so much proposed. It occured to me that contributing to the CNCF can mean a lot of things. To large areas are contributions to SIGs and to projects. In your opinion, should the SIG initially be limited to one area of focus (and if so which one) or to focus on both?

For those not familiar... CNCF SIGs are a little different from Kubernetes SIGs.  Kubernetes SIGs own and are responsible for code within Kubernetes. CNCF SIGs are an extension of the TOC:

The CNCF TOC Special Interest Groups scale contributions by the CNCF technical and user community, while retaining integrity and increasing quality in support of our mission.

Each project has their own governance model and contribution process. Where Kubernetes SIGs have a solid line or ownership to Kubernetes code, CNCF TOC SIGs have a dotted line relationship to CNCF Projects who own the code and governance. The dotted line relationship means that projects do work with and connect to a SIG but the ownership model is different.

Regards,
Matt

On Tue, Jan 21, 2020, at 12:09 PM, Paris Pittman via Lists.Cncf.Io wrote:
Thanks TOC and community members for your time today on the call and support via mailing list. 

Next steps: smooth out the charter and have interested folks step forward to help bootstrap. after, TOC vote/review later on. 
doodle poll[1] for those who are interested. looking forward to this!

paris 




On Sat, Jan 18, 2020 at 11:00 AM Ricardo Aravena <raravena80@...> wrote:
+1 nb

I think healthy projects have to have happy maintainers and contributors to thrive long-term. Also, part of that is for them to feel genuinely welcomed and included.



On Fri, Jan 17, 2020, 6:51 PM Lee Calcote <leecalcote@...> wrote:
+1 NB. This SIG stands to benefit all projects, and hopefully, help recognize all types of contributors (non-code). I’d like to see a contributor ladder come forth here.

- Lee

On Jan 17, 2020, at 4:48 PM, Paris Pittman via Lists.Cncf.Io <parispittman=google.com@...> wrote:

Hi TOC and community,

I'm watching the emails fly by re: maintainer things so figured no time like the present to send this start of a proposal along. I've been working on it for a few weeks and getting input. I think I'm a first-time poster, very-long-time lurker to this list, hello! 

I recently stepped back from my role as co-chair for Kubernetes Contributor Experience Special Interest Group that I held for 2 years. Sarah Novotny, Brian Grant, Phil Wittrock and many(!) others decided that a place for intentional contributor community building was necessary and I'm glad they did. I believe it's the secret sauce but yes - I'm bias. :)

A group like this[1] could help many stakeholders, as outlined in this work-in-progress doc, including engaging the end user community in new ways, and current cncf projects that don't have a ContribEx/CommComm (nod to nodejs). It's important to note in the out-of-scope section, this group isn't going to do the work for your project but will help you get there and learn together. I've spoken to some TOC members and many project maintainers about this. 

Notes:
  • This is a pretty broad charter that should absolutely be trimmed down after formation, discovery, and some other kick off activities. 
  • Left broad as most of the work will depend on the known gaps and the contributors/community members who step forward to help with them.

paris






--


Paris Pittman
Kubernetes Community
Open Source Strategy, Google Cloud
345 Spear Street, San Francisco, 94105






--


Paris Pittman

Kubernetes Community

Open Source Strategy, Google Cloud

345 Spear Street, San Francisco, 94105





--
Kris Nova
Chief Open Source Advocate


85 2nd Street
San Francisco, CA 94105


Richard Hartmann
 

+1 NB

On Sat, Jan 18, 2020 at 1:43 AM Matt Klein <mattklein123@gmail.com> wrote:

Big +1 from me. Very excited to see this SIG form as I think this is an area that many projects struggle with. The projects that don't struggle with this have some very overworked maintainers. ;)
*cough* and *cough*


Geri Jennings
 

+1 NB. I look forward to seeing the evolution of CNCF with this SIG in place.

On 1/23/20, 8:11 AM, "cncf-toc@lists.cncf.io on behalf of Richard Hartmann" <cncf-toc@lists.cncf.io on behalf of richih@richih.org> wrote:

+1 NB

On Sat, Jan 18, 2020 at 1:43 AM Matt Klein <mattklein123@gmail.com> wrote:

> Big +1 from me. Very excited to see this SIG form as I think this is an area that many projects struggle with. The projects that don't struggle with this have some very overworked maintainers. ;)

*cough* and *cough*






----------------------------------------------------------------------
_______________________________________________
This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure.
If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error.


Kiran Mova
 

+1 NB. Thank you! 


On Thu, Jan 23, 2020 at 7:39 PM Geri Jennings <geri.jennings@...> wrote:
+1 NB. I look forward to seeing the evolution of CNCF with this SIG in place.

On 1/23/20, 8:11 AM, "cncf-toc@... on behalf of Richard Hartmann" <cncf-toc@... on behalf of richih@...> wrote:

    +1 NB

    On Sat, Jan 18, 2020 at 1:43 AM Matt Klein <mattklein123@...> wrote:

    > Big +1 from me. Very excited to see this SIG form as I think this is an area that many projects struggle with. The projects that don't struggle with this have some very overworked maintainers. ;)

    *cough* and *cough*






----------------------------------------------------------------------
_______________________________________________
This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure.
If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error.




Alena Prokharchyk
 

+1 NB, this is awesome

-alena

On Jan 23, 2020, at 6:09 AM, Geri Jennings <geri.jennings@cyberark.com> wrote:

+1 NB. I look forward to seeing the evolution of CNCF with this SIG in place.

On 1/23/20, 8:11 AM, "cncf-toc@lists.cncf.io on behalf of Richard Hartmann" <cncf-toc@lists.cncf.io on behalf of richih@richih.org> wrote:

+1 NB

On Sat, Jan 18, 2020 at 1:43 AM Matt Klein <mattklein123@gmail.com> wrote:

Big +1 from me. Very excited to see this SIG form as I think this is an area that many projects struggle with. The projects that don't struggle with this have some very overworked maintainers. ;)
*cough* and *cough*






----------------------------------------------------------------------
_______________________________________________
This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure.
If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error.