Bootc to be contributed to the CNCF as a Sandbox project!

[cgwalters]

We're excited to announce that bootc is submitted to the CNCF as a sandbox project!

A core goal for this project is to normalize using containers and cloud native technology all the way down to the booted host system, and CNCF includes many projects which are aligned with this at a higher level, from container-native CI/CD frameworks to KubeVirt.

With this contribution, we plan to officially join that community and participate directly - benefiting from shared support, resources and best practices in the CNCF. Red Hat has provided very significant resources in the development of this project and that will continue - this project is included as part of RHEL Image Mode. But at the same time a goal with this contribution is to provide an explicitly vendor-neutral home to extend the reach of bootc and collaborate with the other CNCF projects. We’d love to build out support for more operating systems, integrations with Kubernetes (such as update orchestrators, cluster API, etc.) as well as generic Linux environments, and in general build cloud native infrastructure with you!

More links:

• [Sandbox] bootc cncf/sandbox#310
• https://www.redhat.com/en/blog/red-hat-contribute-comprehensive-container-tools-collection-cloud-native-computing-foundation
• https://blog.podman.io/2024/11/podman-buildah-and-skopeo-and-the-cloud-native-computing-foundation/

[cgwalters]

We were accepted into sandbox! cncf/sandbox#310 (comment)

[cgwalters]

Followup tasks in cncf/sandbox#339

Sandbox reference issue: #310

REQUIRED BEFORE PROCEEDING WITH ONBOARDING

A "Project Contribution Agreement" must be completed and any existing trademarks MUST be transferred to the Linux Foundation BEFORE further project onboarding tasks can be completed.

• Review and understand the CNCF IP Policy. Ensure you are using a CNCF compatible license; inbound projects must use the Apache 2.0 license or seek approval for exceptions. Licenses for dependencies are covered separately below.
• Review and understand the LF trademark guidelines.
• Transfer any trademark and logo assets to the Linux Foundation via the Contribution Agreement. CNCF staff will send this document to the contact emails listed in the Sandbox application.

---

@cgwalters Review and understand other documents

• The Technical Leadership Principles that outlines the expected behavior for any maintainer in a leadership role.
• The project proposal process and requirements.
• The services available for your project at the CNCF.
• The dependency license allowlist.
• The online program guidelines.
• The telemetry data collection and usage policy.
• Book time with CNCF staff to understand project benefits and event resources.

@jeckersb Review and understand other documents

• The Technical Leadership Principles that outlines the expected behavior for any maintainer in a leadership role.
• The project proposal process and requirements.
• The services available for your project at the CNCF.
• The dependency license allowlist.
• The online program guidelines.
• The telemetry data collection and usage policy.
• Book time with CNCF staff to understand project benefits and event resources.

@ckyrouac Review and understand other documents

• The Technical Leadership Principles that outlines the expected behavior for any maintainer in a leadership role.
• The project proposal process and requirements.
• The services available for your project at the CNCF.
• The dependency license allowlist.
• The online program guidelines.
• The telemetry data collection and usage policy.
• Book time with CNCF staff to understand project benefits and event resources.

Contribute and transfer other materials

• Move your project to its own separate neutral GitHub organization. This will make it transferable to the CNCF's GitHub Enterprise account. If it's already in a GHE account, you will need to remove it from that first.
• Accept the invite to join the CNCF GitHub Enterprise account. We'll then add thelinuxfoundation as an organization owner to ensure neutral hosting of your project.
• Migrate your Slack channels (if any) to the Kubernetes or CNCF Slack workspace. CNCF staff can help.
• Join the #maintainers-circle Slack channel.
• Transfer your domain to the CNCF. The "LF Stakeholder email" is [email protected]. The "Project" is CNCF.
• Submit a pull request with your artwork.
• Transfer website analytics to [email protected]. CNCF staff can help.

Update and document project details

• Ensure that DCO (preferred) or CLA are enabled for all GitHub repositories of the project.
• Ensure that that the CNCF Code of Conduct (or your adopted version of it) are explicitly referenced at the project's README.md on GitHub. (@jeckersb )
• Ensure LF footer is on your website and guidelines are followed (if your project doesn't have a dedicated website, please adopt those guidelines for the README.md file). The project-specific footer text you should use will be provided in the Contribution Agreement instructions. (@jmarrero )
• Create a maintainer list and add it to the aggregated CNCF maintainer list via pull request. (@cgwalters )
• Provide emails for the maintainers to get access to the maintainers mailing list and Service Desk. Email them to [email protected]. (@gursewak1997 )
• Start working on written, open governance and consider adding this to a GOVERNANCE.md file at the root of your repo. TODO (@jmarrero REF [WIP] Add initial draft of Podman project Governance containers/podman#25398 )
• Start on an OpenSSF Best Practices Badge. (@gursewak1997 )

CNCF staff tasks to support the project

• Add the project to DevStats.
• Add the project to CLOmonitor.
• Add the project to LFX Insights. This is done by adding a read-only app to your GitHub organization once it's in CNCF GHE.
• Add the project to LFX Project Control Center.
• Add the project to the Cloud Native Landscape by updating landscape.yml following these instructions.
• Add a license scanning tool, like FOSSA or Snyk.
• Send a welcome email to confirm maintainer list access.

[cgwalters]

cc @jeckersb @ckyrouac since you are listed as maintainers along with me we all need to go through this.

[cgwalters]

I split the "review the docs" into a section for each of us

[cgwalters]

Thread on github organization

One of the biggest questions here is the Github organization. It's unfortunate that https://github.com/bootc is taken. (Heh and now that I look, so is podman). Anyways...this may partially depend on what the podman folks choose to do over in their issue.

Options:

• bootc-dev
• bootc-org

[cgwalters]

I've reserved bootc-dev. Last call for naming.

[jmarrero]

The only argument I can see for bootc-org is if we own https://bootc.org/

If not bootc-dev is OK

[jeckersb]

bootc.org isn't us, whois shows it was registered in 2010 and has nameservers for ns1.bootc.uk ns2.bootc.net, which then leads to https://www.bootc.net/ (but Chris Boot is apparently a Debian developer!)

[henrywang]

bootc.dev is available. bootc-dev makes sense.

[cgwalters]

Thread on project services

Let's discuss in this sub-thread which project services we use. I think it would make sense to have a bootc meeting on the CNCF hosted zoom.

• zoom:
• https://fossa.io/ looks like a no-brainer to use
• slack: oh yeah...hard decision here on whether to create a new channel on the CNCF slack or not...
• https://www.gitpod.io/ - maybe? Could be interesting to try out

[cgwalters]

Update: I am going to try to make some progress on this tomorrow, which would probably include the Github repository move etc.

[cgwalters]

Transfer is complete! https://github.com/bootc-dev/bootc

[cgwalters]

Followup #1180