Adding Knative proposal for incubation

[spencerdillard]

Description of the PR

Hello TOC and CNCF community,
Today we are proposing that Knative become a CNCF project at Incubation level.

What is Knative?

Knative is a set of serverless APIs that provides higher level abstractions to enable developers to be more productive by simplifying and extending the Kubernetes interfaces for common stateless application patterns.
Knative consists of two sets of APIs – Serving and Eventing – and includes a reference implementation and conformance tests for both the Serving and Eventing components. Developers can use either or both of these components to accelerate their development and build powerful applications quickly and efficiently.

Why are we choosing the CNCF?

Knative has been an active project since 2018, with involvement from a diverse group of individual developers and companies, including Google, IBM, Red Hat, VMWare, TriggerMesh, SAP and many more. It has had over 1800 contributors since its inception and is used both directly and as part of product offerings from multiple companies.
When Google began the project, the intent was to develop a serverless experience that reduced the complexity of getting started on Kubernetes and focused on helping developers be productive. As the project has matured, it has been used widely in production and has thousands of end users. With the recent achievement of releasing Knative 1.0, we believe that donating the project to a vendor-neutral home is a key next step in enabling the project to continue to grow and allow the community to truly self-govern itself. We believe that the CNCF is that vendor-neutral entity that will meet the growing needs of the Knative community. We strived to provide clear API specifications, reliable reference implementations, and a complete test infrastructure, in addition to clear governance practices. All of these are in place today, making the transition to CNCF a clear next step in the maturation and governance of the project.

This transition to CNCF will also bring our Knative community closer to other cloud native projects in the ecosystem, including all the projects it builds on. This will help to establish a virtuous cycle of feedback and features over time for all these projects.

Spencer Dillard,

On behalf of the Knative project leadership

[dprotaso]

To learn more visit https://knative.dev/docs/

[dzolotusky]

As noted in the above assignment by Amye. I've volunteers to co-sponsor this along with Harry.

[dims]

@dzolotusky that would make 3 of us! https://github.com/cncf/toc/pull/762/files#diff-61bbb035b875cc5486138f3f0b356f3e657d80872ad27e202f1c798fbfbef81bR25

[dzolotusky]

@dims I'm happy to get out of your way on this one. I'm not sure that we need 3, but you tell me. I'm also very happy to help out here.

[raravena80]

Great to see a lot of interest. I think the more eyes on the DD the better.

[amye]

Ok! @dims is taking the lead on this one, with @resouer and @dzolotusky supporting as needed. Marking official assignments. :)

[thisisnotapril]

Thank you all!

[dims]

@spencerdillard @thisisnotapril @aijamalnk Please see https://github.com/cncf/toc/blob/main/process/project_proposals.adoc for the overall process. Let's start with the Due Diligence doc. Please see the docs for some of the recent graduations (or in progress work) - examples LitmusChaos / ChaosMesh / Volcano etc. Do ping me on CNCF slack if you can't find them and i'll track it down for you. We are fortunate to have @dzolotusky and @resouer interested as well, so we can try to keep them in the loop as we do things. A couple of other things that take time we can get started soon-ish would be

• security posture : talk to TAG security about current state of things and what could be done going forward (audit? self-assessment? documentation of security processes etc?)
• engage with TAG runtime and discuss state of affairs, upcoming plans etc
• set up some calls/interviews with end users of knative (not vendors who bundle knative) to get a sense of how they use knative and their interactions with the community etc.

there's more things to do :) let's start here.

thanks!

[dims]

@caniszczyk please fill us in on the status of the legal side of things as they progress as well. thanks!

[aijamalnk]

Thank you @dims, @dzolotusky, @resouer. We will start working on the three items you laid out!

[evankanderson]

It looks like we need to create a Due Diligence doc to start filling out the answers... has anyone started one yet, or should I kick one off (probably early next week at this point).

[caniszczyk]

@evankanderson for due diligence, you can look at some previous examples to get started https://docs.google.com/document/d/1tb3mK5cJmaQLO8xR__9NaH2GMrdn3WPjAZFBJYsXrxY/edit

Usually the submitting project does the majority of the work here in tandem with the TOC members who end up doing user interviews

@dims re: legal, we're all set here and have agreements in place

[dims]

thanks for confirming @caniszczyk !

[evankanderson]

Due Diligence document -- if you need edit, feel free to request (world-commentable, stored in Knative.Team GDrive)

Anonymous read access here

[jasonsmithio]

Excited to see this. If there is anything I can do to help, please let me know!

[dims]

Public review opened up today - https://lists.cncf.io/g/cncf-toc/message/6551

[sebgoa]

As the co-founder of TriggerMesh I am delighted to see this. We support it 100%. We are both users and contributors to knative, being part of CNCF would help the knative project align better with the overall cloud-native community.

+1

[jasonsmithio]

I am really excited to see this happen. Have been a huge supporter of Knative and I believe that it's inclusion in the CNCF will be mutually beneficial to the growth of serverless in the Cloud Native space!

…

On Mon, Jan 31, 2022 at 12:06 PM Davanum Srinivas ***@***.***> wrote: Public review opened up today - https://lists.cncf.io/g/cncf-toc/message/6551 — Reply to this email directly, view it on GitHub <#762 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB4J343MUPEIAB4U6TRFCN3UY3TT3ANCNFSM5JCLQQSQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[cathyhongzhang]

I am excited to see this too. Having worked in the serverless area for several years, I am happy to see Knative being hosted as a CNCF project, which will help build a larger open source serverless ecosystem and speed up the adoption of serverless technology.