-
Notifications
You must be signed in to change notification settings - Fork 634
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Knative graduation proposal #1245
Conversation
Signed-off-by: Ali Ok <[email protected]>
03f01ab
to
23b67bb
Compare
@amye could you please label this as TAG Runtime and TAG App Delivery? |
(Graduation proposals don't get labeled with TAGs but this is is fine) |
@aliok In preparation for Knative to be picked up by a TOC member after the KubeCon freeze period -- and prior to TOC member assignment -- please:
|
Hi @angellk, just following up - is the Security Self Assessment necessary if we've been formally audited? See: |
I have about 10 now - waiting to hear back from 10 more. So ideally we'll have ~20 adopters to interview. I'll do the submission once I have a final list in a week or two. |
@dprotaso yes - the Security Self Assessment captures information that the Audits don't |
@dprotaso great! Please use the form to start submitting. Only 5-7 are required and more can be interviewed as the TOC member doing the due diligence feels is necessary. |
Hey everyone - I've followed the new process and created the subsequent graduation issue here - #1509 |
On behalf of the Knative Steering Committee, I would like to propose Knative to become a graduated CNCF project.
As you can see in the proposal document in this PR, we believe Knative is ready to graduate.
A TAG CS governance review request was created here: cncf/tag-contributor-strategy#578 (I believe this is not a MUST for graduation yet, as I saw the Istio example).