cncf
[PROJECT ONBOARDING] CloudNativePG
Welcome to CNCF Project Onboarding
Sandbox reference issue: https://github.com/cncf/sandbox/issues/128
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.
- [x] 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
- [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
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.
- [x] Join the #maintainers-circle Slack channel.
- [x] Transfer your domain to the CNCF. The "LF Stakeholder email" is [email protected]. The "Project" is CNCF.
- [x] 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. - [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.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].
- [x] Start working on written, open governance and consider adding this to a
GOVERNANCE.mdfile at the root of your repo. - [x] 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.
- [x] 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.
- [x] Add a license scanning tool, like FOSSA or Snyk.
- [ ] Send a welcome email to confirm maintainer list access.
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 further project 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.
- [X] 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
Tracked in https://github.com/cloudnative-pg/governance/issues/7
- [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
- [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
thelinuxfoundationas 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.
- [X] Transfer your domain to the CNCF. The "LF Stakeholder email" is [email protected]. The "Project" is CNCF.
- [x] Submit a pull request with your artwork.
- [x] 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. - [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.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].
- [X] Start working on written, open governance and consider adding this to a
GOVERNANCE.mdfile at the root of your repo. - [X] 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.
- [x] 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.
- [x] Add the project to the Cloud Native Landscape by updating landscape.yml following these instructions.
- [x] Add a license scanning tool, like FOSSA or Snyk.
- [x] Send a welcome email to confirm maintainer list access.
Welcome to the CNCF Sandbox @gbartolini and the CloudNativePG 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.
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.
Awesome, Thanks! Looking forward to it!
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.
Now that your project is in the CNCF GitHub Enterprise account we're going to do these two tasks on our side:
- Add
thelinuxfoundationas an an organization owner, if it's not already one. - Use that id to install the "LFX CM" GitHub app which will feed read-only, public activity to LFX Insights.
Contribution agreement done. For CNPG see this: https://github.com/cloudnative-pg/cloudnative-pg/commit/5c51b9aa3942db2cae133884dcd17b56de56f65d
The project is setup on both FOSSA and Snyk! 8 repos imported into both.
Great to meet you @sxd today and thank you for your igenuity on getting your Snyk access resolved ;)
Here again, is the 3rd Party License policy that you need to comply with
https://github.com/cncf/foundation/blob/main/allowed-third-party-license-policy.md
which you can use to guide you as you work thru the small number of reported issues.
- Add
thelinuxfoundationas an an organization owner, if it's not already one.- Use that id to install the "LFX CM" GitHub app which will feed read-only, public activity to LFX Insights.
This has now been done by CNCF staff.
Thanks @krook
I was searching into LFX Insights, but I can't find the project, I'm guessing it will take some time to load everything and load the project right ?
Regards,
Hi @krook
Looks like the only thing that we're missing is the Slack migration but has been a bit hard to decide which Slack to use CNCF or Kubernetes, but besides that, no, is this mandatory to close this issue? I think it's something we can handle in the next few days
Regards,
Hi @krook
Thanks to @RobertKielty we can say that we already created the Slack channels in the CNCF slack, we can now move forward and start moving the community so it's a done check.
The missing part it's the welcome email I think, and that's all =)
Thank you!!
Web analytics are now moved in the CNCF:
- https://github.com/cloudnative-pg/cloudnative-pg.github.io/issues/276
- https://github.com/cloudnative-pg/cloudnative-pg.github.io/issues/279
Created two public Slack Channels for CloudNativePG on the cloud-native workspace
cloudnativegp-users cloudnativegp-dev
All registered CloudNativePG maintainers are Channel Managers.
Created cloudnativegp-maintainers as a private channel for the maintainers.
(I uploaded Peggie as an emoticon from https://github.com/cloudnative-pg/artwork/blob/main/portrait)
We also created the "cloudnative-www" channel for documentation, websites and resources.
@krook @mrbobbytables We believe we have completed all steps for the onboarding process. Thank you so much! We're excited to be on board.
@krook @mrbobbytables We believe we have completed all steps for the onboarding process. Thank you so much! We're excited to be on board.
Wonderful! And we've completed all the tasks on our side as well, welcome onboard!