Skip to content
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

KUDO proposal for sandbox #380

Closed
michelleN opened this issue Mar 4, 2020 · 5 comments · Fixed by #261
Closed

KUDO proposal for sandbox #380

michelleN opened this issue Mar 4, 2020 · 5 comments · Fixed by #261

Comments

@michelleN
Copy link
Member

KUDO has submitted a proposal for sandbox in PR #261 and has done a presentation to SIG App Delivery (recording here).

There was some talk of KUDO moving into Operator Framework as a subproject here. That ended up not happening but @gerred, a KUDO maintainer, is now involved in the governance of operator framework which is a great step forward. The outcome of that discussion is posted here.

Given that, we'll move forward with the sandbox process for KUDO, and the next step for this project is for the SIG App Delivery folks to send over their recommendation for the project as outlined in the sandbox process.

@michelleN michelleN linked a pull request Mar 4, 2020 that will close this issue
@resouer
Copy link
Contributor

resouer commented Mar 4, 2020

Thanks @michelleN , it's much clearer for the SIG to continue the process now.

@gerred
Copy link
Contributor

gerred commented Mar 4, 2020

Thanks @michelleN. I was given a document by @bryanl for due diligence. This document is here: https://docs.google.com/document/d/1QOumLAXaET8nkZinsok8oIUfnmPyHQsvpsDvERUW_N0/edit I've made a copy while I work on it. However, based on the guidelines, it looks like we are pre-DD. We can meet the Sandbox Project requirements as shown, and I think in our last talk discussed the areas we intend to do experimentation.

KUDO is also:

  • Ready to work to get sandbox sponsors if we need more. I have spoken with multiple members of the TOC and have received a lot of very helpful feedback and support and want to enter into this continuing to receive that feedback for the project from our sponsors.
  • Has adopted a Code of Conduct similar (if not exactly matching to) the CNCF Code of Conduct
  • Is able and willing to adhere to the CNCF IP Policy
  • Is able and willing to list our CNCF Sandbox status on our repositories and website.

Additionally, of the examples provided for the CNCF Sandbox process, our areas of experimentation fulfill the following early stage areas:

New projects that are designed to extend one or more CNCF projects with functionality or interoperability libraries. In the case of Kubernetes, the Sandbox is intended as a home for projects that would previously have started in the Kubernetes Incubator.

Independent projects that fit the CNCF mission and provide potential for a novel approach to existing functional areas (or are an attempt to meet an unfulfilled need)

Any project that realistically intends to join CNCF Incubation in future and wishes to lay the foundations for that

@michelleN, @resouer, What are the expectations currently on me to help SIG App Delivery provide a recommendation?

@resouer
Copy link
Contributor

resouer commented Mar 4, 2020

Should work on this one: #344

@caniszczyk
Copy link
Contributor

re: sig recommendation, I'd do something that just puts the rec in the repo like SIG Network is doing for SMI, e.g., cncf/tag-network#3

@gerred
Copy link
Contributor

gerred commented Mar 4, 2020

Working on that PR now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants