sandbox
sandbox copied to clipboard
cncf
[PROJECT ONBOARDING] Podman Desktop
Welcome to CNCF Project Onboarding
Sandbox reference issue: https://github.com/cncf/sandbox/issues/308
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
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
- [ ] 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.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. - [x] Create a maintainer list and add it to the aggregated CNCF maintainer list via pull request.
- [x] 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.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.
Welcome to the CNCF Sandbox @benoitf and the Podman Desktop 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.
hello @krook AFAIK I have not yet received the Contribution Agreement. Is there an ETA ? Thanks.
hello @krook AFAIK I have not yet received the Contribution Agreement. Is there an ETA ? Thanks.
Hi @benoitf they should be sent this week
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.
Thanks, I already sent the email and provided the PR for maintainers here https://github.com/cncf/foundation/pull/937
And yes we're looking at the whole checklist
The Contribution Agreement has just been sent by email to the folks listed on the Sandbox application.
@benoitf are there any other tasks we can check off? It's OK to continue doing those until we complete the CA.
these one can be checked
Contribute and transfer other materials
-
[x] 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.
-
[x] 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.
-
[x] Migrate your Slack channels (if any) to the Kubernetes or CNCF Slack workspace. CNCF staff can help.
-
[x] Join the #maintainers-circle Slack channel.
and also
and
- [x] 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.
and
- [x] Start on an OpenSSF Best Practices Badge.
can see the result there: https://www.bestpractices.dev/en/projects/9966
on the CNCF side, when are you planning to add the license scanning tool, like FOSSA or Snyk. ?
on the CNCF side, when are you planning to add the license scanning tool, like FOSSA or Snyk. ?
@RobertKielty can send the invites
The Landscape entry (together with the Podman tools) - https://github.com/cncf/landscape/pull/4333
@benoitf I have sent out FOSSA invitations to all of the registered maintainers.
Three maintainers were already registered on a different FOSSA instance and their inviations failed to go out.
Once one of the succesfully sent out invitations are accepted I need to add you the Podman Desktop I have setup for the team.
Then that team member can start impotring project repos into FOSSA for licesne scanning.
@benoitf reached out to me on Slack and has logged a call with FOSSA Support to have their exiting account transferred over to the CNCF Podman Desktop team.
The following maintainers have accepted their invitations to join CNCF FOSSA and I have added them to the team.
@cbr7 @odockal and @gastoner
Generate an intial license report by following the Quick Import instructions to import project repos into FOSSA.
https://docs.fossa.com/docs/quick-import
As the remainaing maintainers accept their invitaions, @cbr7, @odockal and @gastoner as Team Admins will be able to add their colleagues to their team.
@benoitf are there any other tasks we can mark complete while we await the Contribution Agreement review?
Many tasks are are just document reviews.
Hello @krook I am from podman-desktop team. I wanted to check with you , what tasks would be needed to be complete before we can manage our community meeting ( hosted on the CNCF calendar). At this point i was told in the service desk request that the project pcc calendar is not available publicly, and can be done so when its active in PCC. Not sure what PCC stood for . Appreciate your help!
At this point i was told in the service desk request that the project pcc calendar is not available publicly, and can be done so when its active in PCC.
Hi @rujutashinde. Correct, to be activated in the Project Control Center the Contribution Agreement must be signed. The LF has sent Red Hat a minor edit to it to add https://podman-desktop.io/ to the list of names/domains to include there so that it can be finalized.
I'll bump this with @jberkus in the email thread.
@benoitf are there any other tasks we can mark complete while we await the Contribution Agreement review?
Many tasks are are just document reviews.
Bumping this @benoitf. Any "Review and understand" tasks we can mark complete?
Ok, the Contribution Agreement has been signed 🎉
Many of the remaining tasks here are just acknowledgements that documents have been read.
Are there any of them we can check off @slemeur, @benoitf, @rujutashinde?
Yep, domains have been transferred.
Most of the other tasks are just document reviews. Anything else started or that can be marked complete @slemeur, @benoitf, @rujutashinde?
@krook Spoke with the team about the remaining reviewing tasks . We have a todo to get these reviewed by a list of people before marking them as complete. Considering a lot of folks are on PTO will update this issues again in a couple of weeks(mid of aug). Two of the listed tasks below, the links are not working- getting 404, do we have the corrected links? The dependency license allowlist.
The online program guidelines.
Thanks for the update @rujutashinde. I fixed the links in the checklist above. We had refactored the repo, apologies for that.
Considering a lot of folks are on PTO will update this issues again in a couple of weeks(mid of aug).
Thanks @rujutashinde. Just checking in again to see if anything can be checked off. Most are just doc reviews.