-
Notifications
You must be signed in to change notification settings - Fork 155
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
[UMBRELLA] CNCF Sandbox project onboarding #812
Comments
DCO has been enabled for the Capsule projects, such as:
|
License scanning has been introduced with cncf/toc#810 by @ptx96 |
CII has been addressed with cncf/toc#816. |
Adhering to CNCF ToC is addressed with cncf/toc#817 by @maxgio92 . |
@prometherion @maxgio92 @MaxFedotov Do we also need to create a new organisation on artifacthub? I would like to start with trivial stuff in the CLO Monitor like Artifacthub Badges etc. Should I create an organisation and add all the maintiners? |
It makes definitely sense. I just created the organization on Artifact Hub, please, share your usernames (publicly, or privately) so I can add you there: thanks for the heads up, @oliverbaehler! ❤️ |
Hey! Mine is the same as here, MaxFedotov |
@prometherion should we still make changes against the current capsule repostories or should we qait until its moved to the new organisation? Mine is also oliverbaehler, thanks. I will start working on a draft for a new release path, including sboms etc to satisfy clo |
The new organization has been created, and Chris Aniszczyk from CNCF accepted the invitation. I would move the project once any reference from the documentation is pointing to the new organization: does it make sense, @oliverbaehler? I never moved a repository hosting a Go module, wondering if this will break all the third-party dependencies too, such as |
General
This is an umbrella issue to track the status of all the required points that need to be addressed in the Git repository and GitHub:
Additional informations
Related to: cncf/sandbox#166
The text was updated successfully, but these errors were encountered: