[UMBRELLA] CNCF Sandbox project onboarding

[maxgio92]

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:

• Review and expand the open governance. See CNCF governance - Expand the open governance #901
• Move the GitHub repository in its own separate neutral GitHub organization (ensure 'thelinuxfoundation' and 'caniszczyk' are added as initial org owners)
• Move documentation to MkDocs - Move documentation to open doc framework #821
• Ensure DCO or CLA are enabled for all GitHub repositories of the project
• Ensure that hat the CNCF Code of Conduct (or your adopted version of it) are explicitly referenced at the project's README on GitHub
• CII: Start on a CII best practices badge https://bestpractices.coreinfrastructure.org/en
• Adopt a license scanning tool, like FOSSA or Snyk

Additional informations

Related to: cncf/toc#971

[prometherion]

DCO has been enabled for the Capsule projects, such as:

• clastix/capsule
• clastix/capsule-proxy

[prometherion]

License scanning has been introduced with #810 by @ptx96

[prometherion]

CII has been addressed with #816.

[prometherion]

Adhering to CNCF ToC is addressed with #817 by @maxgio92 .

[oliverbaehler]

@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?

[prometherion]

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! ❤️

[MaxFedotov]

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

[oliverbaehler]

@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

[prometherion]

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 capsule-proxy, or any other project using github.com/clastix/capsule.