-
Notifications
You must be signed in to change notification settings - Fork 637
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
Clarify TAG work/services in relation to moving levels #1145
Comments
+1 Also want to call out that TAGs help with reviewing and providing feedback for projects that want to enter the CNCF through the sandbox process as well. |
Add to the TAG/TOC meeting agenda at KCCN Chicago |
Perhaps we can explicitly have TAGs focus on the technical and engineering principles and diligence that we carry out. We could clarify that they're responsible for technical parts of Due Diligence, sandbox submissions and annual reviews, while governance, compliance, etc. are handled by other groups. |
Closing this issue as completed through the DTR work and subsequent discussions. Additional areas of TAG involvement are under discussion at the outcome of the KCCN NA SLC 2024 TOC offsite and TOC TAG meeting at KCCN |
Background
The TOC often gets questions regarding what the TAGs do, or what services and functions they provide or perform that support and assist projects and the broader ecosystem. This is most frequently occurring when projects seek to move levels.
Need
Many of our TAGs not only facilitate presentations about CNCF projects, but also have various programs, reviews, and activities that are designed to support projects across a variety of domains as they mature.
The TOC repo, or another discoverable location, should outline what these are and how projects may leverage as they grow and mature within the landscape. Doing so may help reduce the ambiguity and lack of clarity we experience today, most notably the difference in a TAG Security Assessment and a CNCF Project Security Audit.
The text was updated successfully, but these errors were encountered: