+1 !! K

+1 binding From: <cncf-toc@...> on behalf of "Katie Gamanji via lists.cncf.io" <gamanjie=gmail.com@...> Reply-To: "gamanjie@..." <gamanjie@...> Date: Wednesday, August 26, 2020 at 2:30 AM To:

+1 NB Johan Tordsson Den 2020-09-30 kl. 18:00, skrev Amye Scavarda Perrin: -- Johan Tordsson, PhDCTO & Co-founderwww.elastisys.com

+1 NB

+1 nb Best Regards, Magno Rodrigues @magnologan

It may just be me, but there seems to be a lot of focus on the possibility of "bad actors" and mitigating the possible harm that they can cause. When we build tools like surveys, questionnaires,

+1 - Emily Fox @TheMoxieFox (personal handle)

+1 nb

The Open Policy Agent project has applied for graduation from incubation to graduated. (https://github.com/cncf/toc/pull/520) The due diligence document can be found here:

Matt Thanks. A few quick comments (topline for speed). CNCF Incubation tests for production use and technical DD. It has a high bar. Graduation is oriented towards sustainability including some

The start of your original email was clear, but the addition of the word "plan" did make it a bit less so. Thank you for the clarification! I've taken the liberty to re-format the thread below to

We talked about requiring three things from projects reaching Graduated level: 1. A sustainability/longevity plan 2. A process for community feedback on the roadmap 3. Requiring "contributor ladder"

https://github.com/cncf/sig-contributor-strategy/blob/master/resources.md we have been building this for our research and references for the guidance we are creating. the foss governance library is an

Nothing outside of the PDF, but it's been on the TODO list to convert it to markdown and put it somewhere. I'll look at getting this done though if people find it useful. -- Chris Aniszczyk (@cra) |

Is there a referencable online version of that paper? -- -- Josh Berkus Kubernetes Community Red Hat OSPO

I think my wording could be better - the graduation requirement should be for functional community control of the project roadmap (not merely a plan for a community-controlled roadmap)

"Projects struggling to get maintainers when the owning entity is unwilling to give up control to the community" This mostly does not happen. Although due to some bad actors, it can. Mostly projects

What would the mechanism used to be sure that a “plan” for a community controlled roadmap becomes a reality? At present, holding graduation as the milestone for that is, imho, one of the most

I wish to note that it was @cra's idea. I just wrote about it and then talked about it a lot.

Thanks everyone who came to the TOC call today - with extra thanks to Alexis for initiating the idea in the first place. I've tried to capture the key points: Problem statement summary: projects that