toc
toc copied to clipboard
cncf
[SANDBOX PROJECT ONBOARDING] ko
Welcome to CNCF Project Onboarding! 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 to complete onboarding within one month of acceptance.
From the project side, please ensure that you:
- [x] Understand the project proposal process and reqs: https://github.com/cncf/toc/blob/main/process/project_proposals.md#introduction
- [x] Understand the services available for your project at CNCF https://www.cncf.io/services-for-projects/
- [x] Ensure your project meets the CNCF IP Policy: https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy
- [x] Review the online programs guidelines: https://github.com/cncf/foundation/blob/master/online-programs-guidelines.md
- [x] Understand the trademark guidelines: https://www.linuxfoundation.org/en/trademark-usage/
- [x] Understand the license allowlist: https://github.com/cncf/foundation/blob/master/allowed-third-party-license-policy.md#approved-licenses-for-allowlist
- [x] Is your project working on written, open governance? see https://contribute.cncf.io/maintainers/governance/
- [x] Slack: Are your slack channels migrated to the Kubernetes or CNCF Slack? (see https://slack.com/help/articles/217872578-Import-data-from-one-Slack-workspace-to-another for more details)
- [x] Is your project in its own separate neutral github organization?
- [x] Submitted a Pull request to add your project as a sandbox project to https://landscape.cncf.io
- [x] Create maintainer list + add to aggregated https://maintainers.cncf.io list by submitting a PR to it
- [x] Have added your project to https://github.com/cncf/contribute
- [x] Artwork: Submit a pull request to https://github.com/cncf/artwork with your artwork
- [x] Domain: transfer domain to the CNCF - https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/create/63
Things that CNCF will need from the project:
- [x] Provide emails for the maintainers added to https://maintainers.cncf.io in order to get access to the maintainers mailing list and ServiceDesk
- [ ] Trademarks: transfer any trademark and logo mark assets over to the LF - https://github.com/cncf/foundation/tree/master/agreements has agreements
- [x] GitHub: ensure 'thelinuxfoundation' and 'caniszczyk' are added as initial org owners, this helps us make sure we have continuity of GH ownership
- [x] GitHub: ensure DCO or CLA are enabled for all GitHub repositories of the project
- [x] GitHub: ensure that hat the CNCF Code of Conduct (or your adopted version of it) are explicitly referenced at the project's README on GitHub
- [x] Website: ensure LF footer is there and website guidelines followed (if your project doesn't have a dedicated website, please adopt those guidelines to the README file of your project on GitHub).
- [x] Website: Analytics transferred to [email protected]
- [x] CII: Start on a CII best practices badge https://bestpractices.coreinfrastructure.org/en
Things that the CNCF will do or help the project to do:
- [x] Devstats: add to devstats https://devstats.cncf.io/
- [x] Insights: add to LFX Insights https://insights.v3.lfx.linuxfoundation.org/
- [x] Marketing: update relevant intro + slide decks
- [x] Events: update CFP + Registration + CFP Area forms
- [x] ServiceDesk: confirm maintainers have read https://www.cncf.io/services-for-projects/
- [x] CNCF Welcome Email Sent to confirm maintainer list access, welcome email has monthly project sync details
- [x] Create space for meetings/events on https://community.cncf.io, e.g., https://community.cncf.io/pravega-community/ - (https://github.com/cncf/communitygroups/blob/main/README.md#cncf-projects)
- [x] Adopt a license scanning tool, like FOSSA or Snyk
Checklisting:
From the project side, please ensure that you:
- [x] Understand the project proposal process and reqs: https://github.com/cncf/toc/blob/main/process/project_proposals.md#introduction
- [x] Understand the services available for your project at CNCF https://www.cncf.io/services-for-projects/
- [x] Ensure your project meets the CNCF IP Policy: https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy
- [x] Review the online programs guidelines: https://github.com/cncf/foundation/blob/master/online-programs-guidelines.md
- [x] Understand the trademark guidelines: https://www.linuxfoundation.org/en/trademark-usage/
- [x] Understand the license allowlist: https://github.com/cncf/foundation/blob/master/allowed-third-party-license-policy.md#approved-licenses-for-allowlist
- [x] Is your project working on written, open governance? see https://contribute.cncf.io/maintainers/governance/
- [x] Slack: Are your slack channels migrated to the Kubernetes or CNCF Slack? (see https://slack.com/help/articles/217872578-Import-data-from-one-Slack-workspace-to-another for more details)
- [x] Is your project in its own separate neutral github organization?
- yes, https://github.com/ko-build
- [x] Submitted a Pull request to add your project as a sandbox project to https://landscape.cncf.io
- https://github.com/cncf/landscape/pull/2958
- [x] Create maintainer list + add to aggregated https://maintainers.cncf.io list by submitting a PR to it
- [x] Have added your project to https://github.com/cncf/contribute
- https://github.com/cncf/tag-contributor-strategy/pull/293
- [x] Artwork: Submit a pull request to https://github.com/cncf/artwork with your artwork
- no official artwork
- [x] Domain: transfer domain to the CNCF - https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/create/63
- https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-25058
Things that CNCF will need from the project:
- [x] Provide emails for the maintainers added to https://maintainers.cncf.io in order to get access to the maintainers mailing list and ServiceDesk
- https://github.com/cncf/foundation/pull/490
- [ ] Trademarks: transfer any trademark and logo mark assets over to the LF - https://github.com/cncf/foundation/tree/master/agreements has agreements
- no trademarks or logo mark assets
- [x] GitHub: ensure 'thelinuxfoundation' and 'caniszczyk' are added as initial org owners, this helps us make sure we have continuity of GH ownership
- [x] GitHub: ensure DCO or CLA are enabled for all GitHub repositories of the project
- enabled LF EasyCLA
- [x] GitHub: ensure that hat the CNCF Code of Conduct (or your adopted version of it) are explicitly referenced at the project's README on GitHub
- [x] Website: ensure LF footer is there and website guidelines followed (if your project doesn't have a dedicated website, please adopt those guidelines to the README file of your project on GitHub). (https://github.com/ko-build/ko/pull/920)
- [x] Website: Analytics transferred to [email protected]
- no analytics to transfer
- [x] CII: Start on a CII best practices badge https://bestpractices.coreinfrastructure.org/en
- https://bestpractices.coreinfrastructure.org/en/projects/6885
Trademarks: transfer any trademark and logo mark assets over to the LF - https://github.com/cncf/foundation/tree/master/agreements has agreements no trademarks or logo mark assets
You'll want to use the 'no registered trademark' agreement.
Trademarks: transfer any trademark and logo mark assets over to the LF - https://github.com/cncf/foundation/tree/master/agreements has agreements no trademarks or logo mark assets
You'll want to use the 'no registered trademark' agreement.
I might be dumb, but what am I supposed to do with these PDFs? Download and edit to fill in the project name, etc., and sign it as... myself? Should I attach it back to this issue?
Trademarks: transfer any trademark and logo mark assets over to the LF - https://github.com/cncf/foundation/tree/master/agreements has agreements no trademarks or logo mark assets You'll want to use the 'no registered trademark' agreement.
I might be dumb, but what am I supposed to do with these PDFs? Download and edit to fill in the project name, etc., and sign it as... myself? Should I attach it back to this issue?
You will want to reach out to your Legal team for the entity to sign this, I can give you editable versions.
Trademarks: transfer any trademark and logo mark assets over to the LF - https://github.com/cncf/foundation/tree/master/agreements has agreements no trademarks or logo mark assets You'll want to use the 'no registered trademark' agreement.
...
You will want to reach out to your Legal team for the entity to sign this, I can give you editable versions.
Oh okay, thanks. In that case, @mchmarny can you be responsible for getting this signed off by Google legal? There aren't any trademarks for ko, so this is hopefully just a formality.
Just a quick update, the domain transfer is complete, and it looks like the only remaining item is Google affirming that there are no trademarks to transfer. @mchmarny says he's passed that along to Google legal to finish up.
Hi @imjasonh ! My name Crystal Mierly and I will be taking over assisting new sandbox projects with the onboarding process! It looks like all you need to be done on your end is to:
- [ ] Trademarks: transfer any trademark and logo mark assets over to the LF - https://github.com/cncf/foundation/tree/master/agreements has agreements
- [ ] Adopt a license scanning tool, like FOSSA or Snyk
If you have any questions on these last two tasks, please let me know!
- [ ] Trademarks: transfer any trademark and logo mark assets over to the LF - https://github.com/cncf/foundation/tree/master/agreements has agreements
That would have to be acknowledged by someone still at Google, I think. Unfortunately anyone I know at Google associated with the project has since left.
If it helps, ko has no trademarks at all, so there's nothing to transfer.
I've imported the ko repos into FOSSA and they're waiting to be scanned:
Thank you for the update @imjasonh ! If ko has no trademarks to transfer, we do have a no registered trademarks document that will need to be signed and sent over to us
That makes sense. Can I sign it? Or does someone still at Google need to sign it?
That makes sense. Can I sign it? Or does someone still at Google need to sign it?
Check with your legal department about who should sign.
That makes sense. Can I sign it? Or does someone still at Google need to sign it?
Hi @imjasonh ! Did you manage to make progress on getting the trademark signed over?
@Cmierly did we manage to finish the trademark agreement? That seems like the last step.