sandbox
sandbox copied to clipboard
cncf
[PROJECT ONBOARDING] Podman Container Tools
Welcome to CNCF Project Onboarding
Sandbox reference issue: https://github.com/cncf/sandbox/issues/309
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.
- [x] 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.
- [x] 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
- [x] The Technical Leadership Principles that outlines the expected behavior for any maintainer in a leadership role.
- [x] The project proposal process and requirements.
- [x] The services available for your project at the CNCF.
- [x] The dependency license allowlist.
- [x] The online program guidelines.
- [x] The telemetry data collection and usage policy.
- [x] 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
thelinuxfoundationas 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
- [x] Ensure that DCO (preferred) or CLA are enabled for all GitHub repositories of the project.
- [x] Ensure that that the CNCF Code of Conduct (or your adopted version of it) are explicitly referenced at the project's
README.mdon 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.mdfile). 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].
- [x] Start working on written, open governance and consider adding this to a
GOVERNANCE.mdfile at the root of your repo. - [ ] Start on an OpenSSF Best Practices Badge.
CNCF staff tasks to support the project
- [x] Add the project to DevStats.
- [x] 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.
- [x] 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.
One of the biggest decisions here is the Github organization I think. Has there been any thoughts about that?
Welcome to the CNCF Sandbox @marrusl @cgwalters and the Podman Container Tools 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.
One of the biggest decisions here is the Github organization I think. Has there been any thoughts about that?
@cgwalters The Youki team ran into a similar issue when moving out of the containers org into their own separate org. It may be helpful to connect with them.
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.
The Contribution Agreement has just been sent by email to the folks listed on the Sandbox application.
FWIW the way I chose to handle this for bootc was to add it to a github discussion on our repo. See the link from https://github.com/cncf/sandbox/issues/339#issuecomment-2628554869 (which also has some useful information on what I needed to do to copy the issue template). In the discussion I made sub-threads for different topics.
I'm still quite interested in the podman decision on the github org among other things, as it may influence what we do for bootc.
The Landscape URL is added - https://github.com/cncf/landscape/pull/4333
Hi @mheon I created and made you a channel manager on both these channels.
Hi @meheon, recap on yesterday's work: FOSSA Team has been Setup for Podman Containers Tools, invitations were sent out, I added @mehon as a Team admin and I can see that you added five other maintainers to the team. Thank you!
https://app.fossa.com/account/settings/organization/teams/76719
The next step is for you as a project to import your code repos as FOSSA projects.
Work on FOSSA integration into CI via Github Action is in progress for the Podman, Buildah, Skopeo repos
Hi @mheon just checking in on the license scanning.
I want to let you know that a quick import is good enough for us to mark this task complete for now.
https://docs.fossa.com/docs/quick-import
Leaving an item here for the CI infrastructure.
We need to have higher level discussions on this but since Equinix was sunset we're kind of in a holding pattern so we'll have to table that part for now.
The LF footer has been updated in https://github.com/containers/podman.io/pull/409
Import of containers/podman, containers/buildah, containers/skopeo into Fossa is complete
I believe we have checked all the boxes we are able to until the CI/CD move
- https://github.com/containers/podman/issues/25329
On Mon, Aug 11, 2025 at 1:47 PM Matt Heon @.***> wrote:
mheon left a comment (cncf/sandbox#338) https://github.com/cncf/sandbox/issues/338#issuecomment-3176092245
Import of containers/podman, containers/buildah, containers/skopeo into Fossa is complete
— Reply to this email directly, view it on GitHub https://github.com/cncf/sandbox/issues/338#issuecomment-3176092245, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFAGSWKX35ROIJE7YKZWAU33NDJMTAVCNFSM6AAAAABVSZ7SKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZWGA4TEMRUGU . You are receiving this because you commented.Message ID: @.***>
-- Neil Smith (he, him, his) Senior Manager, Container Tools
@.*** | 917-721-4167
We have nothing we are currently using to monitor website analytics.
Neil
On Mon, Aug 11, 2025 at 4:17 PM Daniel Krook @.***> wrote:
krook left a comment (cncf/sandbox#338) https://github.com/cncf/sandbox/issues/338#issuecomment-3176759355
Thanks folks. Checked that off. Amy website analytics and o transfer?
— Reply to this email directly, view it on GitHub https://github.com/cncf/sandbox/issues/338#issuecomment-3176759355, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFAGSWLKWTVR7WPU6VJORHL3ND257AVCNFSM6AAAAABVSZ7SKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZWG42TSMZVGU . You are receiving this because you commented.Message ID: @.***>
-- Neil Smith (he, him, his) Senior Manager, Container Tools
@.*** | 917-721-4167
Awesome. So that does indeed just leave us with the GitHub Enterprise stuff.
@castrojo is there anything we can use from Oracle or Akamai/Linode to replace Equinix?
@krook @castrojo As requested I invited the thelinuxfoundation account to the podman, buildah, skopeo repos just now.
@krook @castrojo As requested I invited the
thelinuxfoundationaccount to the podman, buildah, skopeo repos just now.
Thanks @Luap99. I've given the team that owns that id a heads up to accept the invite. Please make sure it's also set as an Owner.
Yes I set it up as admin of the repos, the Owner role only exists for the whole org level which we don't want to give access to until we move the repos into their own org where all projects are part of CNCF.
Thanks @Luap99. I've pinged LF IT to make sure they accept the invite if they haven't already. Also, you should now have access to Oracle Cloud Infrastructure to test out your CI/CD needs.
@krook It still shows as pending invite on our repo so it is not yet accepted.
I did successfully created the oracle account, thanks. We will test it with cirrus CI and see how it works for us. From what I can tell they don't offer an fedora or debian images out of the box but it seems possible to use custom qcow2 images so that should work I guess. Biggest problem seems to be no option to run macos for the mac testing, but if we can use it for the rest that would already be very good.