-
Notifications
You must be signed in to change notification settings - Fork 236
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
Fill out CNCF Due Diligence document #864
Comments
Let's go ahead and divvy up the work, so some of these sections are clearly owned by, say Steering, by TOC, or something else. They seem to have some natural lines of division, but I think it would be good to assign them explicitly, so we can keep track of the "sub" work. |
In the section "Architectural, design and feature overview" Serving and Eventing is described. Would it make sense to add an additional "Client" subsection or is this too small and we should add client aspects to the individual Serving and Eventing sections, respectively? |
I think it would be fine to add the client if you want! |
/assign |
This is pretty much done /close |
@evankanderson: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
https://docs.google.com/document/d/1qPMyIBZ1tBk6WpEMPuLtTrjA6lvbrQ7DvCZb22S0llo/edit#
See cncf/toc#762 for the CNCF side of this
The text was updated successfully, but these errors were encountered: