toc
toc copied to clipboard
cncf
[SANDBOX PROJECT ONBOARDING] Hexa
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/
- [ ] 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
- [ ] 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
- [ ] GitHub: ensure DCO or CLA are enabled for all GitHub repositories of the project
- [ ] 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).
- [ ] Website: Analytics transferred to [email protected]
- [ ] 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)
- [ ] Adopt a license scanning tool, like FOSSA or Snyk
- [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
Hi @amye , here are some more updates for you:
- [x] Is your project working on written, open governance? see https://contribute.cncf.io/maintainers/governance/
- [x] Is your project in its own separate neutral github organization?
- [x] Create maintainer list + add to aggregated https://maintainers.cncf.io/ list by submitting a PR to it
@amye, here is the latest batch of updates... can we have a call to discuss the remaining open items?
- [x] Submitted a Pull request to add your project as a sandbox project to https://landscape.cncf.io/
- [x] Have added your project to https://github.com/cncf/contribute (apparently this is superseded by the landscape pull request)
- [x] Artwork: Submit a pull request to https://github.com/cncf/artwork with your artwork
- [x] Provide emails for the maintainers added to https://maintainers.cncf.io/ in order to get access to the maintainers mailing list and ServiceDesk
- [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 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] ServiceDesk: confirm maintainers have read https://www.cncf.io/services-for-projects/
Let me catch up on these, if we have your project maintainer emails at [email protected] or [email protected], we'll be able to communicate through your maintainer lists.
[amye deleted a comment because wrong associated org] - but Trademarks - https://github.com/cncf/foundation/tree/main/agreements has both registered and non-registered trademarks.
https://github.com/hexa-org is the right org and the main repo is https://github.com/hexa-org/policy-orchestrator
@amye Does CNCF share a license for FOSSA or snyk or does the project get its own license?
Let me catch up on these, if we have your project maintainer emails at [email protected] or [email protected], we'll be able to communicate through your maintainer lists.
Checking back in on this -- we don't have your emails yet so we can't communicate with you!
@amye Hi - can we work together on completing some of these other tasks? I'm not sure which ones are no longer needed given the new procedures, but do need help with things like slack, FOSSA, etc.
The 'contribute' now pulls from Landscape, that's the biggest change here. Slack: Create a channel in Kubernetes or CNCF slack
Github should be pretty straightforward, here's what I see outstanding: GitHub: ensure 'thelinuxfoundation' and 'caniszczyk' are added as initial org owners, this helps us make sure we have continuity of GH ownership GitHub: ensure DCO or CLA are enabled for all GitHub repositories of the project 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
Hi @ggebel ! My name is Crystal and I am the new project coordinator in charge of onboarding sandbox projects!
Following up on Amye's previous post, have you had a chance to complete any further tasks? Did you have any questions or concerns that I could help with?
Please don't hesitate to reach out at any time!
Hello @Cmierly! It would be great to chat with you and get all of these tasks reviewed/completed. Can we do that on a conference call some time next week?
I'm happy to help, take a look at project-meetings.cncf.io and let me know if there are times that suit!
