cncf-toc@lists.cncf.io

Re: [cncf-wg-env-sustainability] recap of WG meeting

alexis richardson

Hi folks, I don't know if it helps here but maybe try to think about "projects first". What is the project here and why? This is more important than forming committees (though they too, have a place).

Show quoted text

On Wed, 27 Jul 2022, 19:56 Leonard Pahlke via lists.cncf.io, <leonard.pahlke=googlemail.com@...> wrote:

Hello,

I am not at all happy with the state of the WG or now TAG that we are in at this moment. I don't feel like we created an environment that is good to work in. I am really concerned and a bit sad that we are at this point now.

A few months ago, Max and I were thinking about how to push the issue of sustainability in our industry, given climate change the most prominent example, which I see as the biggest existential problem of our time. Current software is not green software, a transformation has to happen in our industry too. And we need to understand that we not just build software, the requirements, the supply chain and an entire industry is needed which is built on hardware and other infrastructure things to allow us to create software and execute it.

It makes sense to start with open-source software because it is used everywhere and powers big systems, and like Kubernetes, which can manage huge systems and thus offers huge potential both horizontally (how many use Kubernetes) and in depth (huge systems that are powered by K8s). Max came up with the great idea of CNCF TAG Sustainability, which then became WG Environmental Sustainability a bit later. Max did all the organization and communication up to building the repo. I went back to UNI to get my Master's degree with a focus on green software development and have been delving into the topic bit by bit ever since.

Starting the WG as part of CNCF was something I could never have dreamed of (without sounding cheesy).

With the experience from the Kubernetes community, we were both sure that with great people we would progress quickly as a team and as a community.

Some people are signed up and joined the WG, and I am truly grateful for that and exactly what we wanted, but sadly, we are not a team. The agenda of companies (Red Hat & IBM, Intel) for this WG / TAG is to push key positions (chairs and TL) and projects (Kepler), while cleverly booting out community heroes like Max. This is not an environment where people can trust each other and work collaboratively as a community.

Problems

1. The biggest problem is the communication in the group, which mainly takes place behind closed doors.
2. Active blocking of bootstrapping PRs and discussions.
3. It seems to me that filling chairs and TL is the most important thing – it's not about anything else. It is about strategically filling certain key positions in the community.
4. the goal of environmental sustainability of the CNCF landscape and community is not pursued with everything. We are actively pushing our projects and not acting for the community. Own projects are great, and I am working on one too, but that needs to be separated, the day is not about making a project big.

Suggestions (ToC)

1. Max has worked hard on the formation of the WG / TAG, stealing his work is unbelievable. We should rename the repo and work with what we have. We even used the TAG Security repo as a template for our repo. There is no reason to create another proposal when the original (a TAG proposal) is only a few months old… (let's work smarter)
2. a couple of people have been proposed as chairs – some of them have never said a word in a WG env-sustainability meeting or worked on an open-source project, which is perfectly fine and great, but not ideal to be the as chair responsible for the TAG team / community. I would recommend including only one of the three people currently recommended, and thus only one from Intel / Red Hat / IBM, as chair – this would prevent from pushing the internal corporate agenda to promote their collaborative project Kepler.
3. questioning every line of the Code of Conduct or similar documents when forming a TAG / WG makes no sense at all, it just blocks the process. We should have a basis to agree on and then make proposals directly to the CoCC committee or others. A better starting point for TAGs/WGs needs to be defined – so I would recommend creating a template repository to facilitate the WG/TAG bootstrap process. If no one has time for this, I can take on this task, as I don't want a new WG to have to go through what we are currently experiencing.
4. Do it right or don't do it at all, consider postponing the formation of the TAG or the appointment of the chairs.

I will bring the above points to the next working group/TAG meeting to discuss with everyone. We all need to be honest with ourselves about why we are here and what we want to accomplish.

I'm sad to have to write this message, but the WG / TAG is currently going in a dysfunctional, slightly passive-aggressive direction, and we have to consider how to alleviate that and move in a collaborative direction again. Community is not easy, and I am curious what I have to learn, better influence and build a good environment in half a year or so. I hope that we can still get the group in a position to make a positive contribution to the development of sustainable software in the future at CNCF.

Leo

On Jul 27 2022, at 3:42 pm, Marlow Weston <catblade@...> wrote:
Hello Max,

I can appreciate your concerns.

The TAG proposal is in markdown, so it's best to start in the format it needs to be submitted in. Everyone should have access to the GitHub repo. Many have been actively contributing already, probably due to seeing the original mail here: https://lists.cncf.io/g/cncf-wg-env-sustainability/message/30 .
Admin has been given, on both repos, to multiple individuals (just in case). If people have issues with the hackmd, then they are welcome to use the GitHub repo.

Thank you for the links to the other documents. We have tried to include a combo of material from these and used other TAG proposals as guidelines on what to include and will add a credit section at the end.

TAG has a different process than a WG. In order to have a slot at KubeCon, I was told it was best if we submitted by early/mid August. Because there has been prior work, we should be able to leverage that to accelerate a mature proposal quickly. I have reached out to many of the individuals showing up at discussions. It would be very helpful if you would also reach out to any others you (or any others) may see as interested.

Huamin already started a TAG Chair nomination here (https://lists.cncf.io/g/cncf-wg-env-sustainability/message/31). If others would like to nominate (or be nominated), they should either add to that thread or be ready on August 3rd.

Looking forward to your contributions,
--Marlow

On Wed, Jul 27, 2022, 1:13 AM Max Koerbaecher <max@...> wrote:
Hey there,

thank you.
I would like to request to put this new proposal  in a shared Google Doc. This feels right now not very open and inviting to contribute. Also, you could be busy or your account gets locked and than no one can grant access to the doc. Furthermore, the discussions are hidden as long as the people are not be invited or don't have the right link, strong -1 therefore.

If the people for the TAG nomination needs to be part of this proposal, please add anyone from the original proposal TAG proposal https://docs.google.com/document/d/1QJlfkmM9L0dFnrIiyt9-V9zwDhNplUvkD50zWy5CBzM/edit?usp=sharing as well as from the WG charter  https://docs.google.com/document/d/1JaF7lSUmLQ2zmScmca6UF7PgbjMzSxjhhjx2LThThaY/edit?usp=sharing It would be a pity to lose all the input and especially the people who have provided this already.

I think there is no need to rush and the proposal should be well crafted. The WG got also announced even so it landed only a week before KubeCon (thanks Dave & Katie!).

Thank you for your efforts putting this document together, looking forward to have an open and vibrant discussion!

Best
Max

On Wed, Jul 27, 2022 at 00:20:22, Marlow Weston <catblade@...> wrote:
Many thanks for this, Erin!

Other notes for folks:

We've gone and started a tag proposal here:
https://github.com/catblade/wg-env-sustainability/blob/TAG-env-sustainability-proposal/documentation/EnvironmentalSustainabilityTAGProposal.md

Requests for feedback, and please join the hackmd if you can for more dynamic discussion as not all changes get pushed to that branch quickly. If you need to know how, please contact me and I'll get you set up quickly with permissions. I will need your hackmd account name.
https://hackmd.io/team/sustainability

Huamin Chen had chair recommendations that he sent to this mailing list. My understand is that chairs do need to be part of this TAG proposal, is that correct Erin?

If anyone would like others recommended for this, please do send to the group so we can discuss August 3. We would like to submit the proposal shortly after that meeting as to not lose momentum and to be able to make kubecon with the announcement, if we can get approved in time.

Many thanks,
Marlow

On Tue, Jul 26, 2022, 5:10 PM Erin Boyd <eboyd@...> wrote:
Hi Folks,
Just wanted to touch base and reiterate our position in the TOC and see if there are any questions moving forward.

The current Environmental Sustainability WG will be disbanded and formalized into a TAG.
Many of you may be asking 'why?' Let me attempt to address those concerns here:
1) Currently we don't have a governance or process structure that supports work groups unattached/affiliated with a TAG. We have formalized our documentation to reflect this and recognize our negligence in the formation of the group months ago.
2) Ensure governance, processes, etc... are consistent with the CNCF way & provide an avenue for the TAG to engage with the TOC for support/media/talks/etc...

What is next?
The TOC is looking to work with the current community to submit a proposal for the TAG along with accepting nominations for 3 leadership co-chair positions. These will be voted on by the TOC. These positions have a 2-year term limit consistent with the other TAG co-chairs.

@Richard Hartmann and I are here to help and will be serving as your TOC sponsors!
We look forward to working with you. Please let us know how we can help.

Thanks,
Erin

--
Erin A. Boyd
Director of Emerging Technologies OCTO
Distinguished Engineer
Red Hat

eboyd@...

Re: [cncf-wg-env-sustainability] recap of WG meeting

Leonard Pahlke <leonard.pahlke@...>

#7293

Hello,

I am not at all happy with the state of the WG or now TAG that we are in at this moment. I don't feel like we created an environment that is good to work in. I am really concerned and a bit sad that we are at this point now.

A few months ago, Max and I were thinking about how to push the issue of sustainability in our industry, given climate change the most prominent example, which I see as the biggest existential problem of our time. Current software is not green software, a transformation has to happen in our industry too. And we need to understand that we not just build software, the requirements, the supply chain and an entire industry is needed which is built on hardware and other infrastructure things to allow us to create software and execute it.

It makes sense to start with open-source software because it is used everywhere and powers big systems, and like Kubernetes, which can manage huge systems and thus offers huge potential both horizontally (how many use Kubernetes) and in depth (huge systems that are powered by K8s). Max came up with the great idea of CNCF TAG Sustainability, which then became WG Environmental Sustainability a bit later. Max did all the organization and communication up to building the repo. I went back to UNI to get my Master's degree with a focus on green software development and have been delving into the topic bit by bit ever since.

Starting the WG as part of CNCF was something I could never have dreamed of (without sounding cheesy).

With the experience from the Kubernetes community, we were both sure that with great people we would progress quickly as a team and as a community.

Some people are signed up and joined the WG, and I am truly grateful for that and exactly what we wanted, but sadly, we are not a team. The agenda of companies (Red Hat & IBM, Intel) for this WG / TAG is to push key positions (chairs and TL) and projects (Kepler), while cleverly booting out community heroes like Max. This is not an environment where people can trust each other and work collaboratively as a community.

Problems

1. The biggest problem is the communication in the group, which mainly takes place behind closed doors.

2. Active blocking of bootstrapping PRs and discussions.

3. It seems to me that filling chairs and TL is the most important thing – it's not about anything else. It is about strategically filling certain key positions in the community.

4. the goal of environmental sustainability of the CNCF landscape and community is not pursued with everything. We are actively pushing our projects and not acting for the community. Own projects are great, and I am working on one too, but that needs to be separated, the day is not about making a project big.

Suggestions (ToC)

1. Max has worked hard on the formation of the WG / TAG, stealing his work is unbelievable. We should rename the repo and work with what we have. We even used the TAG Security repo as a template for our repo. There is no reason to create another proposal when the original (a TAG proposal) is only a few months old… (let's work smarter)

2. a couple of people have been proposed as chairs – some of them have never said a word in a WG env-sustainability meeting or worked on an open-source project, which is perfectly fine and great, but not ideal to be the as chair responsible for the TAG team / community. I would recommend including only one of the three people currently recommended, and thus only one from Intel / Red Hat / IBM, as chair – this would prevent from pushing the internal corporate agenda to promote their collaborative project Kepler.

3. questioning every line of the Code of Conduct or similar documents when forming a TAG / WG makes no sense at all, it just blocks the process. We should have a basis to agree on and then make proposals directly to the CoCC committee or others. A better starting point for TAGs/WGs needs to be defined – so I would recommend creating a template repository to facilitate the WG/TAG bootstrap process. If no one has time for this, I can take on this task, as I don't want a new WG to have to go through what we are currently experiencing.

4. Do it right or don't do it at all, consider postponing the formation of the TAG or the appointment of the chairs.

I will bring the above points to the next working group/TAG meeting to discuss with everyone. We all need to be honest with ourselves about why we are here and what we want to accomplish.

I'm sad to have to write this message, but the WG / TAG is currently going in a dysfunctional, slightly passive-aggressive direction, and we have to consider how to alleviate that and move in a collaborative direction again. Community is not easy, and I am curious what I have to learn, better influence and build a good environment in half a year or so. I hope that we can still get the group in a position to make a positive contribution to the development of sustainable software in the future at CNCF.

Leo

Show quoted text

On Jul 27 2022, at 3:42 pm, Marlow Weston <catblade@...> wrote:

Hello Max,

I can appreciate your concerns.

The TAG proposal is in markdown, so it's best to start in the format it needs to be submitted in. Everyone should have access to the GitHub repo. Many have been actively contributing already, probably due to seeing the original mail here: https://lists.cncf.io/g/cncf-wg-env-sustainability/message/30 .
Admin has been given, on both repos, to multiple individuals (just in case). If people have issues with the hackmd, then they are welcome to use the GitHub repo.

Thank you for the links to the other documents. We have tried to include a combo of material from these and used other TAG proposals as guidelines on what to include and will add a credit section at the end.

TAG has a different process than a WG. In order to have a slot at KubeCon, I was told it was best if we submitted by early/mid August. Because there has been prior work, we should be able to leverage that to accelerate a mature proposal quickly. I have reached out to many of the individuals showing up at discussions. It would be very helpful if you would also reach out to any others you (or any others) may see as interested.

Huamin already started a TAG Chair nomination here (https://lists.cncf.io/g/cncf-wg-env-sustainability/message/31). If others would like to nominate (or be nominated), they should either add to that thread or be ready on August 3rd.

Looking forward to your contributions,
--Marlow

On Wed, Jul 27, 2022, 1:13 AM Max Koerbaecher <max@...> wrote:
Hey there,

thank you.
I would like to request to put this new proposal  in a shared Google Doc. This feels right now not very open and inviting to contribute. Also, you could be busy or your account gets locked and than no one can grant access to the doc. Furthermore, the discussions are hidden as long as the people are not be invited or don't have the right link, strong -1 therefore.

If the people for the TAG nomination needs to be part of this proposal, please add anyone from the original proposal TAG proposal https://docs.google.com/document/d/1QJlfkmM9L0dFnrIiyt9-V9zwDhNplUvkD50zWy5CBzM/edit?usp=sharing as well as from the WG charter  https://docs.google.com/document/d/1JaF7lSUmLQ2zmScmca6UF7PgbjMzSxjhhjx2LThThaY/edit?usp=sharing It would be a pity to lose all the input and especially the people who have provided this already.

I think there is no need to rush and the proposal should be well crafted. The WG got also announced even so it landed only a week before KubeCon (thanks Dave & Katie!).

Thank you for your efforts putting this document together, looking forward to have an open and vibrant discussion!

Best
Max

On Wed, Jul 27, 2022 at 00:20:22, Marlow Weston <catblade@...> wrote:
Many thanks for this, Erin!

Other notes for folks:

We've gone and started a tag proposal here:
https://github.com/catblade/wg-env-sustainability/blob/TAG-env-sustainability-proposal/documentation/EnvironmentalSustainabilityTAGProposal.md

Requests for feedback, and please join the hackmd if you can for more dynamic discussion as not all changes get pushed to that branch quickly. If you need to know how, please contact me and I'll get you set up quickly with permissions. I will need your hackmd account name.
https://hackmd.io/team/sustainability

Huamin Chen had chair recommendations that he sent to this mailing list. My understand is that chairs do need to be part of this TAG proposal, is that correct Erin?

If anyone would like others recommended for this, please do send to the group so we can discuss August 3. We would like to submit the proposal shortly after that meeting as to not lose momentum and to be able to make kubecon with the announcement, if we can get approved in time.

Many thanks,
Marlow

On Tue, Jul 26, 2022, 5:10 PM Erin Boyd <eboyd@...> wrote:
Hi Folks,
Just wanted to touch base and reiterate our position in the TOC and see if there are any questions moving forward.

The current Environmental Sustainability WG will be disbanded and formalized into a TAG.
Many of you may be asking 'why?' Let me attempt to address those concerns here:
1) Currently we don't have a governance or process structure that supports work groups unattached/affiliated with a TAG. We have formalized our documentation to reflect this and recognize our negligence in the formation of the group months ago.
2) Ensure governance, processes, etc... are consistent with the CNCF way & provide an avenue for the TAG to engage with the TOC for support/media/talks/etc...

What is next?
The TOC is looking to work with the current community to submit a proposal for the TAG along with accepting nominations for 3 leadership co-chair positions. These will be voted on by the TOC. These positions have a 2-year term limit consistent with the other TAG co-chairs.

@Richard Hartmann and I are here to help and will be serving as your TOC sponsors!
We look forward to working with you. Please let us know how we can help.

Thanks,
Erin

--
Erin A. Boyd
Director of Emerging Technologies OCTO
Distinguished Engineer
Red Hat

eboyd@...

_._,_._,_
Links:
You receive all messages sent to this group.

View/Reply Online (#37) | Reply To Group | Reply To Sender | Mute This Topic | New Topic
Your Subscription | Contact Group Owner | Unsubscribe [leonard.pahlke@...]

_._,_._,

Re: New mission for "TOC Contributors"

Lin Sun

#7292

+1 on this, it was unclear to me what TOC contributors exactly are when viewing the docs earlier today.

Best,

Lin

Show quoted text

On Jul 27, 2022, at 11:49 AM, Davanum Srinivas <davanum@...> wrote:

Hi Folks,

Once upon a time, before we had a good governance structure in TOC (like TAG(s) and WG(s)) we had "TOC Contributors" - a list of folks who can and did help with TOC business.

Now it feels like we should redirect all our energies to TAG(s) and WG(s) to strengthen them and help the TOC by the good work in these spaces. We are figuring out how/what in the following github issue:
https://github.com/cncf/toc/issues/867

As the cleanup phase of this effort, we have drafted PR(s) https://github.com/cncf/people/pull/89 and https://github.com/cncf/toc/pull/885 as well.

Thoughts please. Either here in this thread or in issue 867 or #toc on slack.

thanks,
Dims

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

Re: New mission for "TOC Contributors"

alexis richardson

#7291

As an OG member, let me say that the "TOC Contributors" concept was an
interim one, that can be deprecated for TAGs and WGs.  So I am +1 on
shifting focus onto the latter (TAG/WG) and dropping the former
(TOC/C)

alexis

Show quoted text

On Wed, Jul 27, 2022 at 4:49 PM Davanum Srinivas <davanum@...> wrote:

Hi Folks,

Once upon a time, before we had a good governance structure in TOC (like TAG(s) and WG(s)) we had "TOC Contributors" - a list of folks who can and did help with TOC business.

Now it feels like we should redirect all our energies to TAG(s) and WG(s) to strengthen them and help the TOC by the good work in these spaces. We are figuring out how/what in the following github issue:
https://github.com/cncf/toc/issues/867

As the cleanup phase of this effort, we have drafted PR(s) https://github.com/cncf/people/pull/89 and https://github.com/cncf/toc/pull/885 as well.

Thoughts please. Either here in this thread or in issue 867 or #toc on slack.

thanks,
Dims

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

New mission for "TOC Contributors"

Davanum Srinivas

#7290

Hi Folks,

Once upon a time, before we had a good governance structure in TOC (like TAG(s) and WG(s)) we had "TOC Contributors" - a list of folks who can and did help with TOC business.

Now it feels like we should redirect all our energies to TAG(s) and WG(s) to strengthen them and help the TOC by the good work in these spaces. We are figuring out how/what in the following github issue:

https://github.com/cncf/toc/issues/867

As the cleanup phase of this effort, we have drafted PR(s) https://github.com/cncf/people/pull/89 and https://github.com/cncf/toc/pull/885 as well.

Thoughts please. Either here in this thread or in issue 867 or #toc on slack.

thanks,

Dims

--

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

Re: [cncf-wg-env-sustainability] recap of WG meeting

Davanum Srinivas

#7289

Max,

I had the notion that we are way past the google doc stage and things need to be codified in github now (like usual business)? Let's please move forward with github.

thanks,

Dims

Show quoted text

On Wed, Jul 27, 2022 at 10:48 AM Max Koerbaecher <max@...> wrote:

Hey there,

thank you.
I would like to request to put this new proposal  in a shared Google Doc. This feels right now not very open and inviting to contribute. Also, you could be busy or your account gets locked and than no one can grant access to the doc. Furthermore, the discussions are hidden as long as the people are not be invited or don't have the right link, strong -1 therefore.

If the people for the TAG nomination needs to be part of this proposal, please add anyone from the original proposal TAG proposal https://docs.google.com/document/d/1QJlfkmM9L0dFnrIiyt9-V9zwDhNplUvkD50zWy5CBzM/edit?usp=sharing as well as from the WG charter  https://docs.google.com/document/d/1JaF7lSUmLQ2zmScmca6UF7PgbjMzSxjhhjx2LThThaY/edit?usp=sharing It would be a pity to lose all the input and especially the people who have provided this already.

I think there is no need to rush and the proposal should be well crafted. The WG got also announced even so it landed only a week before KubeCon (thanks Dave & Katie!).

Thank you for your efforts putting this document together, looking forward to have an open and vibrant discussion!

Best
Max

On Wed, Jul 27, 2022 at 00:20:22, Marlow Weston <catblade@...> wrote:
Many thanks for this, Erin!

Other notes for folks:

We've gone and started a tag proposal here:
https://github.com/catblade/wg-env-sustainability/blob/TAG-env-sustainability-proposal/documentation/EnvironmentalSustainabilityTAGProposal.md

Requests for feedback, and please join the hackmd if you can for more dynamic discussion as not all changes get pushed to that branch quickly. If you need to know how, please contact me and I'll get you set up quickly with permissions. I will need your hackmd account name.
https://hackmd.io/team/sustainability

Huamin Chen had chair recommendations that he sent to this mailing list. My understand is that chairs do need to be part of this TAG proposal, is that correct Erin?

If anyone would like others recommended for this, please do send to the group so we can discuss August 3. We would like to submit the proposal shortly after that meeting as to not lose momentum and to be able to make kubecon with the announcement, if we can get approved in time.

Many thanks,
Marlow

On Tue, Jul 26, 2022, 5:10 PM Erin Boyd <eboyd@...> wrote:
Hi Folks,
Just wanted to touch base and reiterate our position in the TOC and see if there are any questions moving forward.

The current Environmental Sustainability WG will be disbanded and formalized into a TAG.
Many of you may be asking 'why?' Let me attempt to address those concerns here:
1) Currently we don't have a governance or process structure that supports work groups unattached/affiliated with a TAG. We have formalized our documentation to reflect this and recognize our negligence in the formation of the group months ago.
2) Ensure governance, processes, etc... are consistent with the CNCF way & provide an avenue for the TAG to engage with the TOC for support/media/talks/etc...

What is next?
The TOC is looking to work with the current community to submit a proposal for the TAG along with accepting nominations for 3 leadership co-chair positions. These will be voted on by the TOC. These positions have a 2-year term limit consistent with the other TAG co-chairs.

@Richard Hartmann and I are here to help and will be serving as your TOC sponsors!
We look forward to working with you. Please let us know how we can help.

Thanks,
Erin

--

Erin A. Boyd

Director of Emerging Technologies OCTO
Distinguished Engineer

Red Hat

eboyd@...

--

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

Re: [cncf-wg-env-sustainability] recap of WG meeting

Erin Boyd

#7288

The chairs can be proposed outside the TAG proposal (per TOC consensus).

Erin

Show quoted text

On Tue, Jul 26, 2022 at 4:28 PM Marlow Weston <catblade@...> wrote:

Many thanks for this, Erin!

Other notes for folks:

We've gone and started a tag proposal here:
https://github.com/catblade/wg-env-sustainability/blob/TAG-env-sustainability-proposal/documentation/EnvironmentalSustainabilityTAGProposal.md

Requests for feedback, and please join the hackmd if you can for more dynamic discussion as not all changes get pushed to that branch quickly. If you need to know how, please contact me and I'll get you set up quickly with permissions. I will need your hackmd account name.
https://hackmd.io/team/sustainability

Huamin Chen had chair recommendations that he sent to this mailing list. My understand is that chairs do need to be part of this TAG proposal, is that correct Erin?

If anyone would like others recommended for this, please do send to the group so we can discuss August 3. We would like to submit the proposal shortly after that meeting as to not lose momentum and to be able to make kubecon with the announcement, if we can get approved in time.

Many thanks,
Marlow

On Tue, Jul 26, 2022, 5:10 PM Erin Boyd <eboyd@...> wrote:
Hi Folks,
Just wanted to touch base and reiterate our position in the TOC and see if there are any questions moving forward.

The current Environmental Sustainability WG will be disbanded and formalized into a TAG.
Many of you may be asking 'why?' Let me attempt to address those concerns here:
1) Currently we don't have a governance or process structure that supports work groups unattached/affiliated with a TAG. We have formalized our documentation to reflect this and recognize our negligence in the formation of the group months ago.
2) Ensure governance, processes, etc... are consistent with the CNCF way & provide an avenue for the TAG to engage with the TOC for support/media/talks/etc...

What is next?
The TOC is looking to work with the current community to submit a proposal for the TAG along with accepting nominations for 3 leadership co-chair positions. These will be voted on by the TOC. These positions have a 2-year term limit consistent with the other TAG co-chairs.

@Richard Hartmann and I are here to help and will be serving as your TOC sponsors!
We look forward to working with you. Please let us know how we can help.

Thanks,
Erin

--

Erin A. Boyd

Director of Emerging Technologies OCTO
Distinguished Engineer

Red Hat

eboyd@...

--

Erin A. Boyd

Director of Emerging Technologies OCTO

Distinguished Engineer

Red Hat

eboyd@...

Re: SPIFFE and SPIRE for Graduation: Public Comment Period thru AUG 9 2022

Andrew Martin <andy@...>

#7287

+1 nb

congratulations to the team for all the work to get here

Show quoted text

On Tue, 26 Jul 2022 at 21:06, Brandon Lum <lumjjb@...> wrote:

+1 nb

On Tue, Jul 26, 2022, 12:55 PM Lee Calcote via lists.cncf.io <lee.calcote=layer5.io@...> wrote:
+1 NB

On Jul 26, 2022, at 2:54 PM, Ken Owens <kenchristineowens@...> wrote:

+1 NB

On Tue, Jul 26, 2022 at 2:52 PM Evan Anderson via lists.cncf.io <evana=vmware.com@...> wrote:

+1 NB. Looking forward to SPIFFE "crossing the chasm" one day.

From: cncf-toc@... <cncf-toc@...> on behalf of Rahul Jadhav via lists.cncf.io <r=accuknox.com@...>
Sent: Tuesday, July 26, 2022 9:59 AM
To: Emily Fox <themoxiefoxatwork@...>
Cc: CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] SPIFFE and SPIRE for Graduation: Public Comment Period thru AUG 9 2022

⚠ External Email

+1 NB

Excited to see SPIFFE/SPIRE graduating.

Regards,

Rahul

On Tue, Jul 26, 2022 at 9:58 PM Emily Fox <themoxiefoxatwork@...> wrote:

Community,

Both the SPIFFE and SPIRE projects have applied to move from incubation to graduation. As the TOC sponsors, Justin Cormack and I would like to thank everyone for their work and patience in bringing both projects to this exciting point.

PR: https://github.com/cncf/toc/pull/778
DD: https://docs.google.com/document/d/1u6ipO6Wr06zQzOUjU92cyX1mKx8Xn9QBXkSqHugQv8Q/edit?usp=sharing
Adopter Interviews: Many interviews were done previously, two additional interviews were conducted anonymously and included in the DD below the existing user stories where previous interviews are captured.

Everyone is welcome to comment in the document, on the PR, or in reply to this thread, before we move to a TOC vote. This period of public comment will last a minimum of two weeks closing on AUG 9 2022.

Thank you.

~Emily Fox

⚠ External Email: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender.

Re: [cncf-wg-env-sustainability] recap of WG meeting

Max Koerbaecher <max@...>

#7286

Hey there,

thank you.

I would like to request to put this new proposal in a shared Google Doc. This feels right now not very open and inviting to contribute. Also, you could be busy or your account gets locked and than no one can grant access to the doc. Furthermore, the discussions are hidden as long as the people are not be invited or don't have the right link, strong -1 therefore.

If the people for the TAG nomination needs to be part of this proposal, please add anyone from the original proposal TAG proposal https://docs.google.com/document/d/1QJlfkmM9L0dFnrIiyt9-V9zwDhNplUvkD50zWy5CBzM/edit?usp=sharing as well as from the WG charter https://docs.google.com/document/d/1JaF7lSUmLQ2zmScmca6UF7PgbjMzSxjhhjx2LThThaY/edit?usp=sharing It would be a pity to lose all the input and especially the people who have provided this already.

I think there is no need to rush and the proposal should be well crafted. The WG got also announced even so it landed only a week before KubeCon (thanks Dave & Katie!).

Thank you for your efforts putting this document together, looking forward to have an open and vibrant discussion!

Best

Max

Show quoted text

On Wed, Jul 27, 2022 at 00:20:22, Marlow Weston <catblade@...> wrote:

Many thanks for this, Erin!

Other notes for folks:

We've gone and started a tag proposal here:
https://github.com/catblade/wg-env-sustainability/blob/TAG-env-sustainability-proposal/documentation/EnvironmentalSustainabilityTAGProposal.md

Requests for feedback, and please join the hackmd if you can for more dynamic discussion as not all changes get pushed to that branch quickly. If you need to know how, please contact me and I'll get you set up quickly with permissions. I will need your hackmd account name.
https://hackmd.io/team/sustainability

Huamin Chen had chair recommendations that he sent to this mailing list. My understand is that chairs do need to be part of this TAG proposal, is that correct Erin?

If anyone would like others recommended for this, please do send to the group so we can discuss August 3. We would like to submit the proposal shortly after that meeting as to not lose momentum and to be able to make kubecon with the announcement, if we can get approved in time.

Many thanks,
Marlow

On Tue, Jul 26, 2022, 5:10 PM Erin Boyd <eboyd@redhat.com> wrote:
Hi Folks,
Just wanted to touch base and reiterate our position in the TOC and see if there are any questions moving forward.

The current Environmental Sustainability WG will be disbanded and formalized into a TAG.
Many of you may be asking 'why?' Let me attempt to address those concerns here:
1) Currently we don't have a governance or process structure that supports work groups unattached/affiliated with a TAG. We have formalized our documentation to reflect this and recognize our negligence in the formation of the group months ago.
2) Ensure governance, processes, etc... are consistent with the CNCF way & provide an avenue for the TAG to engage with the TOC for support/media/talks/etc...

What is next?
The TOC is looking to work with the current community to submit a proposal for the TAG along with accepting nominations for 3 leadership co-chair positions. These will be voted on by the TOC. These positions have a 2-year term limit consistent with the other TAG co-chairs.

@Richard Hartmann and I are here to help and will be serving as your TOC sponsors!
We look forward to working with you. Please let us know how we can help.

Thanks,
Erin

--

Erin A. Boyd

Director of Emerging Technologies OCTO
Distinguished Engineer

Red Hat

eboyd@redhat.com

Re: [cncf-wg-env-sustainability] recap of WG meeting

Marlow Weston <catblade@...>

#7285

Hello Max,

I can appreciate your concerns.

The TAG proposal is in markdown, so it's best to start in the format it needs to be submitted in. Everyone should have access to the GitHub repo. Many have been actively contributing already, probably due to seeing the original mail here: https://lists.cncf.io/g/cncf-wg-env-sustainability/message/30 .

Admin has been given, on both repos, to multiple individuals (just in case). If people have issues with the hackmd, then they are welcome to use the GitHub repo.

Thank you for the links to the other documents. We have tried to include a combo of material from these and used other TAG proposals as guidelines on what to include and will add a credit section at the end.

TAG has a different process than a WG. In order to have a slot at KubeCon, I was told it was best if we submitted by early/mid August. Because there has been prior work, we should be able to leverage that to accelerate a mature proposal quickly. I have reached out to many of the individuals showing up at discussions. It would be very helpful if you would also reach out to any others you (or any others) may see as interested.

Huamin already started a TAG Chair nomination here (https://lists.cncf.io/g/cncf-wg-env-sustainability/message/31). If others would like to nominate (or be nominated), they should either add to that thread or be ready on August 3rd.

Looking forward to your contributions,

--Marlow

Show quoted text

On Wed, Jul 27, 2022, 1:13 AM Max Koerbaecher <max@...> wrote:

Hey there,

thank you.
I would like to request to put this new proposal  in a shared Google Doc. This feels right now not very open and inviting to contribute. Also, you could be busy or your account gets locked and than no one can grant access to the doc. Furthermore, the discussions are hidden as long as the people are not be invited or don't have the right link, strong -1 therefore.

If the people for the TAG nomination needs to be part of this proposal, please add anyone from the original proposal TAG proposal https://docs.google.com/document/d/1QJlfkmM9L0dFnrIiyt9-V9zwDhNplUvkD50zWy5CBzM/edit?usp=sharing as well as from the WG charter  https://docs.google.com/document/d/1JaF7lSUmLQ2zmScmca6UF7PgbjMzSxjhhjx2LThThaY/edit?usp=sharing It would be a pity to lose all the input and especially the people who have provided this already.

I think there is no need to rush and the proposal should be well crafted. The WG got also announced even so it landed only a week before KubeCon (thanks Dave & Katie!).

Thank you for your efforts putting this document together, looking forward to have an open and vibrant discussion!

Best
Max

On Wed, Jul 27, 2022 at 00:20:22, Marlow Weston <catblade@...> wrote:
Many thanks for this, Erin!

Other notes for folks:

We've gone and started a tag proposal here:
https://github.com/catblade/wg-env-sustainability/blob/TAG-env-sustainability-proposal/documentation/EnvironmentalSustainabilityTAGProposal.md

Requests for feedback, and please join the hackmd if you can for more dynamic discussion as not all changes get pushed to that branch quickly. If you need to know how, please contact me and I'll get you set up quickly with permissions. I will need your hackmd account name.
https://hackmd.io/team/sustainability

Huamin Chen had chair recommendations that he sent to this mailing list. My understand is that chairs do need to be part of this TAG proposal, is that correct Erin?

If anyone would like others recommended for this, please do send to the group so we can discuss August 3. We would like to submit the proposal shortly after that meeting as to not lose momentum and to be able to make kubecon with the announcement, if we can get approved in time.

Many thanks,
Marlow

On Tue, Jul 26, 2022, 5:10 PM Erin Boyd <eboyd@...> wrote:
Hi Folks,
Just wanted to touch base and reiterate our position in the TOC and see if there are any questions moving forward.

The current Environmental Sustainability WG will be disbanded and formalized into a TAG.
Many of you may be asking 'why?' Let me attempt to address those concerns here:
1) Currently we don't have a governance or process structure that supports work groups unattached/affiliated with a TAG. We have formalized our documentation to reflect this and recognize our negligence in the formation of the group months ago.
2) Ensure governance, processes, etc... are consistent with the CNCF way & provide an avenue for the TAG to engage with the TOC for support/media/talks/etc...

What is next?
The TOC is looking to work with the current community to submit a proposal for the TAG along with accepting nominations for 3 leadership co-chair positions. These will be voted on by the TOC. These positions have a 2-year term limit consistent with the other TAG co-chairs.

@Richard Hartmann and I are here to help and will be serving as your TOC sponsors!
We look forward to working with you. Please let us know how we can help.

Thanks,
Erin

--

Erin A. Boyd

Director of Emerging Technologies OCTO
Distinguished Engineer

Red Hat

eboyd@...

Re: Results from Sandbox Inclusion Meeting, July 26

Lin Sun

#7284

Thanks Dims, I’m so glad to see this is open for public to view. Appreciate everyone’s time in reviewing the projects!

Best,

Lin

Show quoted text

On Jul 27, 2022, at 9:21 AM, Davanum Srinivas <davanum@...> wrote:

Folks,

please see https://www.youtube.com/watch?v=G_fqXe_ssVY for the video recording of this meeting to see what exactly we debated for each project.

thanks,
-- Dims

On Tue, Jul 26, 2022 at 12:48 PM Amye Scavarda Perrin <ascavarda@...> wrote:
The TOC met today to review applications at sandbox.cncf.io.

Hexa Policy Orchestrator: passes with a majority vote of the TOC
(Please update your documentation around your projects in onboarding)
Konveyor: passes with a majority vote of the TOC
Trousseau: reapply with a more robust community, present to SIG security and/or TAG Security
YAM: incorrect Github links? reapply with correct project links
Armada: passes with a majority vote of the TOC
KubeRay: Should this stay with the Ray project? Reapply with more details around why CNCF is the right home.
Open Zero Trust security platform: reapply with correct project links and code history
SREWorks: TAG-App Delivery presentation for introduction and demo, TOC is unclear on the project's goals
BumbleBee: eBPF isn't itself a cloud native technology, even if it's packaged that way. The eBPF Foundation is likely a better fit.
CloudNativePG: Please present to TAG-App Delivery to propose a working group to improve Postgres on k8s.
dbpack: Reapply with a more robust community.
Carina: TAG-Storage presentation for introduction and demo
Multy: Reapply with a more robust community, focusing on limited use-cases to drive adoption.
External Secrets Operator: passes with a majority vote of the TOC

Next Sandbox Review Meeting: September 27th, 2022

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

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

Re: Results from Sandbox Inclusion Meeting, July 26

Davanum Srinivas

#7283

Folks,

please see https://www.youtube.com/watch?v=G_fqXe_ssVY for the video recording of this meeting to see what exactly we debated for each project.

thanks,

-- Dims

Show quoted text

On Tue, Jul 26, 2022 at 12:48 PM Amye Scavarda Perrin <ascavarda@...> wrote:

The TOC met today to review applications at sandbox.cncf.io.

Hexa Policy Orchestrator: passes with a majority vote of the TOC
(Please update your documentation around your projects in onboarding)
Konveyor: passes with a majority vote of the TOC
Trousseau: reapply with a more robust community, present to SIG security and/or TAG Security
YAM: incorrect Github links? reapply with correct project links
Armada: passes with a majority vote of the TOC
KubeRay: Should this stay with the Ray project? Reapply with more details around why CNCF is the right home.
Open Zero Trust security platform: reapply with correct project links and code history
SREWorks: TAG-App Delivery presentation for introduction and demo, TOC is unclear on the project's goals
BumbleBee: eBPF isn't itself a cloud native technology, even if it's packaged that way. The eBPF Foundation is likely a better fit.
CloudNativePG: Please present to TAG-App Delivery to propose a working group to improve Postgres on k8s.
dbpack: Reapply with a more robust community.
Carina: TAG-Storage presentation for introduction and demo
Multy: Reapply with a more robust community, focusing on limited use-cases to drive adoption.
External Secrets Operator: passes with a majority vote of the TOC

Next Sandbox Review Meeting: September 27th, 2022

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

--

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

Re: SPIFFE and SPIRE for Graduation: Public Comment Period thru AUG 9 2022

Trilok Geer

#7282

+1 NB

Show quoted text

On Tue, 26 Jul 2022 at 9:58 PM, Emily Fox <themoxiefoxatwork@...> wrote:

Community,

Both the SPIFFE and SPIRE projects have applied to move from incubation to graduation. As the TOC sponsors, Justin Cormack and I would like to thank everyone for their work and patience in bringing both projects to this exciting point.

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

DD: https://docs.google.com/document/d/1u6ipO6Wr06zQzOUjU92cyX1mKx8Xn9QBXkSqHugQv8Q/edit?usp=sharing

Adopter Interviews: Many interviews were done previously, two additional interviews were conducted anonymously and included in the DD below the existing user stories where previous interviews are captured.

Everyone is welcome to comment in the document, on the PR, or in reply to this thread, before we move to a TOC vote. This period of public comment will last a minimum of two weeks closing on AUG 9 2022.

Thank you.

~Emily Fox

CNCF Tech Writers Office Hours (July)

Nate Waddington

#7281

Hello Everyone,

On the last Wednesday of every month, we host a CNCF Tech Writers Office Hours. Projects are welcome to drop in and chat with the CNCF Tech Docs team about any documentation questions they might have.

Please note, we’ve changed the time! We’re starting two hours earlier now, 8:00AM Pacific time.

Wed July 27, 8:00am - 8:50am (PST).

https://tockify.com/cncf.public.events/detail/433/1658934000000

Hope to see you there!

Cheers,
Nate.

Re: [cncf-wg-env-sustainability] recap of WG meeting

Marlow Weston <catblade@...>

#7280

Many thanks for this, Erin!

Other notes for folks:

We've gone and started a tag proposal here:

https://github.com/catblade/wg-env-sustainability/blob/TAG-env-sustainability-proposal/documentation/EnvironmentalSustainabilityTAGProposal.md

Requests for feedback, and please join the hackmd if you can for more dynamic discussion as not all changes get pushed to that branch quickly. If you need to know how, please contact me and I'll get you set up quickly with permissions. I will need your hackmd account name.

https://hackmd.io/team/sustainability

Huamin Chen had chair recommendations that he sent to this mailing list. My understand is that chairs do need to be part of this TAG proposal, is that correct Erin?

If anyone would like others recommended for this, please do send to the group so we can discuss August 3. We would like to submit the proposal shortly after that meeting as to not lose momentum and to be able to make kubecon with the announcement, if we can get approved in time.

Many thanks,

Marlow

Show quoted text

On Tue, Jul 26, 2022, 5:10 PM Erin Boyd <eboyd@...> wrote:

Hi Folks,
Just wanted to touch base and reiterate our position in the TOC and see if there are any questions moving forward.

The current Environmental Sustainability WG will be disbanded and formalized into a TAG.
Many of you may be asking 'why?' Let me attempt to address those concerns here:
1) Currently we don't have a governance or process structure that supports work groups unattached/affiliated with a TAG. We have formalized our documentation to reflect this and recognize our negligence in the formation of the group months ago.
2) Ensure governance, processes, etc... are consistent with the CNCF way & provide an avenue for the TAG to engage with the TOC for support/media/talks/etc...

What is next?
The TOC is looking to work with the current community to submit a proposal for the TAG along with accepting nominations for 3 leadership co-chair positions. These will be voted on by the TOC. These positions have a 2-year term limit consistent with the other TAG co-chairs.

@Richard Hartmann and I are here to help and will be serving as your TOC sponsors!
We look forward to working with you. Please let us know how we can help.

Thanks,
Erin

--

Erin A. Boyd

Director of Emerging Technologies OCTO
Distinguished Engineer

Red Hat

eboyd@...

recap of WG meeting

Erin Boyd

#7279

Hi Folks,

Just wanted to touch base and reiterate our position in the TOC and see if there are any questions moving forward.

The current Environmental Sustainability WG will be disbanded and formalized into a TAG.

Many of you may be asking 'why?' Let me attempt to address those concerns here:

1) Currently we don't have a governance or process structure that supports work groups unattached/affiliated with a TAG. We have formalized our documentation to reflect this and recognize our negligence in the formation of the group months ago.

2) Ensure governance, processes, etc... are consistent with the CNCF way & provide an avenue for the TAG to engage with the TOC for support/media/talks/etc...

What is next?

The TOC is looking to work with the current community to submit a proposal for the TAG along with accepting nominations for 3 leadership co-chair positions. These will be voted on by the TOC. These positions have a 2-year term limit consistent with the other TAG co-chairs.

@Richard Hartmann and I are here to help and will be serving as your TOC sponsors!

We look forward to working with you. Please let us know how we can help.

Thanks,

Erin

--

Erin A. Boyd

Director of Emerging Technologies OCTO

Distinguished Engineer

Red Hat

eboyd@...

Re: SPIFFE and SPIRE for Graduation: Public Comment Period thru AUG 9 2022

Brandon Lum

#7278

+1 nb

Show quoted text

On Tue, Jul 26, 2022, 12:55 PM Lee Calcote via lists.cncf.io <lee.calcote=layer5.io@...> wrote:

+1 NB

On Jul 26, 2022, at 2:54 PM, Ken Owens <kenchristineowens@...> wrote:

+1 NB

On Tue, Jul 26, 2022 at 2:52 PM Evan Anderson via lists.cncf.io <evana=vmware.com@...> wrote:

+1 NB. Looking forward to SPIFFE "crossing the chasm" one day.

From: cncf-toc@... <cncf-toc@...> on behalf of Rahul Jadhav via lists.cncf.io <r=accuknox.com@...>
Sent: Tuesday, July 26, 2022 9:59 AM
To: Emily Fox <themoxiefoxatwork@...>
Cc: CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] SPIFFE and SPIRE for Graduation: Public Comment Period thru AUG 9 2022

⚠ External Email

+1 NB

Excited to see SPIFFE/SPIRE graduating.

Regards,

Rahul

On Tue, Jul 26, 2022 at 9:58 PM Emily Fox <themoxiefoxatwork@...> wrote:

Community,

Both the SPIFFE and SPIRE projects have applied to move from incubation to graduation. As the TOC sponsors, Justin Cormack and I would like to thank everyone for their work and patience in bringing both projects to this exciting point.

PR: https://github.com/cncf/toc/pull/778
DD: https://docs.google.com/document/d/1u6ipO6Wr06zQzOUjU92cyX1mKx8Xn9QBXkSqHugQv8Q/edit?usp=sharing
Adopter Interviews: Many interviews were done previously, two additional interviews were conducted anonymously and included in the DD below the existing user stories where previous interviews are captured.

Everyone is welcome to comment in the document, on the PR, or in reply to this thread, before we move to a TOC vote. This period of public comment will last a minimum of two weeks closing on AUG 9 2022.

Thank you.

~Emily Fox

⚠ External Email: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender.

Re: SPIFFE and SPIRE for Graduation: Public Comment Period thru AUG 9 2022

Lee Calcote

#7277

+1 NB

Show quoted text

On Jul 26, 2022, at 2:54 PM, Ken Owens <kenchristineowens@...> wrote:

+1 NB

On Tue, Jul 26, 2022 at 2:52 PM Evan Anderson via lists.cncf.io <evana=vmware.com@...> wrote:

+1 NB. Looking forward to SPIFFE "crossing the chasm" one day.

From: cncf-toc@... <cncf-toc@...> on behalf of Rahul Jadhav via lists.cncf.io <r=accuknox.com@...>
Sent: Tuesday, July 26, 2022 9:59 AM
To: Emily Fox <themoxiefoxatwork@...>
Cc: CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] SPIFFE and SPIRE for Graduation: Public Comment Period thru AUG 9 2022

⚠ External Email

+1 NB

Excited to see SPIFFE/SPIRE graduating.

Regards,

Rahul

On Tue, Jul 26, 2022 at 9:58 PM Emily Fox <themoxiefoxatwork@...> wrote:

Community,

Both the SPIFFE and SPIRE projects have applied to move from incubation to graduation. As the TOC sponsors, Justin Cormack and I would like to thank everyone for their work and patience in bringing both projects to this exciting point.

PR: https://github.com/cncf/toc/pull/778
DD: https://docs.google.com/document/d/1u6ipO6Wr06zQzOUjU92cyX1mKx8Xn9QBXkSqHugQv8Q/edit?usp=sharing
Adopter Interviews: Many interviews were done previously, two additional interviews were conducted anonymously and included in the DD below the existing user stories where previous interviews are captured.

Everyone is welcome to comment in the document, on the PR, or in reply to this thread, before we move to a TOC vote. This period of public comment will last a minimum of two weeks closing on AUG 9 2022.

Thank you.

~Emily Fox

⚠ External Email: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender.

Re: SPIFFE and SPIRE for Graduation: Public Comment Period thru AUG 9 2022

Ken Owens

#7276

+1 NB

Show quoted text

On Tue, Jul 26, 2022 at 2:52 PM Evan Anderson via lists.cncf.io <evana=vmware.com@...> wrote:

+1 NB. Looking forward to SPIFFE "crossing the chasm" one day.

From: cncf-toc@... <cncf-toc@...> on behalf of Rahul Jadhav via lists.cncf.io <r=accuknox.com@...>
Sent: Tuesday, July 26, 2022 9:59 AM
To: Emily Fox <themoxiefoxatwork@...>
Cc: CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] SPIFFE and SPIRE for Graduation: Public Comment Period thru AUG 9 2022

⚠ External Email

+1 NB

Excited to see SPIFFE/SPIRE graduating.

Regards,

Rahul

On Tue, Jul 26, 2022 at 9:58 PM Emily Fox <themoxiefoxatwork@...> wrote:

Community,

Both the SPIFFE and SPIRE projects have applied to move from incubation to graduation. As the TOC sponsors, Justin Cormack and I would like to thank everyone for their work and patience in bringing both projects to this exciting point.

PR: https://github.com/cncf/toc/pull/778
DD: https://docs.google.com/document/d/1u6ipO6Wr06zQzOUjU92cyX1mKx8Xn9QBXkSqHugQv8Q/edit?usp=sharing
Adopter Interviews: Many interviews were done previously, two additional interviews were conducted anonymously and included in the DD below the existing user stories where previous interviews are captured.

Everyone is welcome to comment in the document, on the PR, or in reply to this thread, before we move to a TOC vote. This period of public comment will last a minimum of two weeks closing on AUG 9 2022.

Thank you.

~Emily Fox

⚠ External Email: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender.

Re: SPIFFE and SPIRE for Graduation: Public Comment Period thru AUG 9 2022

Evan Anderson

#7275

+1 NB. Looking forward to SPIFFE "crossing the chasm" one day.

Show quoted text

From: cncf-toc@... <cncf-toc@...> on behalf of Rahul Jadhav via lists.cncf.io <r=accuknox.com@...>
Sent: Tuesday, July 26, 2022 9:59 AM
To: Emily Fox <themoxiefoxatwork@...>
Cc: CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] SPIFFE and SPIRE for Graduation: Public Comment Period thru AUG 9 2022

+1 NB

Excited to see SPIFFE/SPIRE graduating.

Regards,

Rahul

On Tue, Jul 26, 2022 at 9:58 PM Emily Fox <themoxiefoxatwork@...> wrote:

Community,

Both the SPIFFE and SPIRE projects have applied to move from incubation to graduation. As the TOC sponsors, Justin Cormack and I would like to thank everyone for their work and patience in bringing both projects to this exciting point.

PR: https://github.com/cncf/toc/pull/778
DD: https://docs.google.com/document/d/1u6ipO6Wr06zQzOUjU92cyX1mKx8Xn9QBXkSqHugQv8Q/edit?usp=sharing
Adopter Interviews: Many interviews were done previously, two additional interviews were conducted anonymously and included in the DD below the existing user stories where previous interviews are captured.

Everyone is welcome to comment in the document, on the PR, or in reply to this thread, before we move to a TOC vote. This period of public comment will last a minimum of two weeks closing on AUG 9 2022.

Thank you.

~Emily Fox