-
Notifications
You must be signed in to change notification settings - Fork 631
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
Comments
Thanks @michelleN , it's much clearer for the SIG to continue the process now. |
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:
Additionally, of the examples provided for the CNCF Sandbox process, our areas of experimentation fulfill the following early stage areas:
@michelleN, @resouer, What are the expectations currently on me to help SIG App Delivery provide a recommendation? |
Should work on this one: #344 |
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 |
Working on that PR now. |
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.
The text was updated successfully, but these errors were encountered: