[PROJECT ONBOARDING] bootc

[mrbobbytables]

Welcome to CNCF Project Onboarding

Sandbox reference issue: #310

This is an issue created to help onboard your project into the CNCF after the TOC has voted to accept your project.

We would like your project to complete onboarding within one month of acceptance.

Please track your progress by using "Quote reply" to create your own copy of this checklist in an issue, so that you can update the status as you finish items.

REQUIRED BEFORE PROCEEDING WITH ONBOARDING

A "Project Contribution Agreement" must be completed and any existing trademarks MUST be transferred to the Linux Foundation BEFORE CNCF staff 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.

---

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.
• 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.
• Create a maintainer list and add it to the aggregated CNCF maintainer list via pull request.
• Provide emails for the maintainers to get access to the maintainers mailing list and Service Desk. Email them to [email protected].
• Start working on written, open governance and consider adding this to a GOVERNANCE.md file at the root of your repo.
• Start on an OpenSSF Best Practices Badge.

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.

[p5]

I am the owner of the bootc.io domain, currently used for redirecting bootc.io/ and www.bootc.io/ to GitHub Pages.

Happy to transfer ownership to the CNCF whenever you all are ready - just let me know the details!
Looking at the Jira request, I think I only need to know the "Community Stakeholder email" before I can initiate the transfer.

I'm reachable through the Fedora Matrix at @rsturla:fedora.im.

---

Note: I'm not a member of RedHat or the bootc team, just a helpful community member :)

[krook]

Welcome to the CNCF Sandbox @marrusl and the bootc team!

CNCF staff is working on the first step, which is to create and share the Contribution Agreement with you shortly.

I'll send an email to the contacts listed on the Sandbox application. The Contribution Agreement can be signed by the contributing organization listed there, or a group of individuals.

[krook]

Welcome again to the CNCF Sandbox! We're creating the Contribution Agreement document for you now and should have it to you shortly.

In the meantime, there are a few generic tasks in this checklist that you can work on that don't have a hard dependency on the CA, such as reviewing documents, documenting any governance you may already have, and preparing your maintainer lists to share.

[krook]

The Contribution Agreement has just been sent by email to the folks listed on the Sandbox application.

[krook]

I am the owner of the bootc.io domain, currently used for redirecting bootc.io/ and www.bootc.io/ to GitHub Pages.

Happy to transfer ownership to the CNCF whenever you all are ready - just let me know the details!

Thanks @p5! Once the CA is signed, we can activate the project in the LF records and then work on transferring the domain.

[cgwalters]

Please track your progress by using "Quote reply" to create your own copy of this checklist in an issue, so that you can update the status as you finish items.

Silly mechanical thing...using "quote reply" seems to corrupt the Markdown formatting, mashing together the lists into paragraphs (in addition to quoting everything). I am not seeing a way via the Github UI to get access to the raw markdown, though I could probably figure it out maybe by dropping to the API. (OK I looked, apparently it's not possible?)

This seems like a surprising papercut on Github's side. But anyways we can probably work around it - I presume the raw markdown input for this comes from a template somewhere, can you point to that template?

And we should probably update the recommendations to suggest pointing to that template?

[cgwalters]

(Followup, a quick search took me to https://github.com/cncf/sandbox/blob/a4b573c7450d532385ec4d488adce87c2067522f/.github/ISSUE_TEMPLATE/project-onboarding.md )

[krook]

@cgwalters yeah it seems like something changed with how GitHub formats checklists now. And as of today in Chrome the original checklist is oddly aligned as well.

Here's the raw issue template Markdown you can use.

[krook]

Ha. Looks like our comments were posted at the same time. Glad you found it. The raw is probably the easiest to copy from.

[cgwalters]

The followup checklist for the work on this is now at containers/bootc#897 (comment) - am I doing this right? The template says "create your own copy of this checklist in an issue" but did it mean an issue on this repo? Or is using the bootc one OK?

[krook]

Thanks @cgwalters creating a copy here as a comment or in your own repo will work. I like what you did so let's go with that and we'll sync it back here.