toc
toc copied to clipboard
[SANDBOX PROJECT ONBOARDING] sealer
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:
- [ ] Understand the project proposal process and reqs: https://github.com/cncf/toc/blob/main/process/project_proposals.adoc#introduction
- [ ] Understand the services available for your project at CNCF https://www.cncf.io/services-for-projects/
- [ ] Ensure your project meets the CNCF IP Policy: https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy
- [ ] Review the online programs guidelines: https://github.com/cncf/foundation/blob/master/online-programs-guidelines.md
- [ ] Understand the trademark guidelines: https://www.linuxfoundation.org/en/trademark-usage/
- [ ] Understand the license allowlist: https://github.com/cncf/foundation/blob/master/allowed-third-party-license-policy.md#approved-licenses-for-allowlist
- [ ] 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
- [ ] Have added your project to https://github.com/cncf/contribute
- [ ] 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
- [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).
- [ ] 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
@fanux - We're in here! It's great to see you all! First things: landscape and maintainers.cncf.io is a great place to start!
Thanks, I got it~
Test DevStats page added.
Prod DevStats page added, ETA for adding new project to All CNCF is tomorrow (same with adding it to `Project(s) Health).
Maintainers https://github.com/alibaba/sealer/blob/main/MAINTAINERS.md https://github.com/cncf/foundation/pull/335 added.
New project added to All CNCF instance and Projects Health.
'thelinuxfoundation' and 'caniszczyk' are added as initial org owners: https://github.com/sealerio
How to enable CLA for a GitHub repositories? @amye DCO already enabled.
DCO is fine, I'll mark that off. We only need one, not both.
@amye add maintainers PR done: https://github.com/cncf/foundation/pull/335 add contribute PR done: https://github.com/cncf/contribute/pull/107
contribute landscape logo done: https://github.com/cncf/landscape/pull/2572
@amye how to transfer Analytics to you? And we have already done some work, could you mark them off?
Checking back in here, I don't yet have emails for you all! Drop an email to [email protected] and we'll get you taken care of!
@amye
I have sent an email including sealer maintainers' email address to [email protected], and all those email addresses could be also found at https://github.com/sealerio/sealer/blob/main/MAINTAINERS.md
- [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 that hat the CNCF Code of Conduct (or your adopted version of it) are explicitly referenced at the project's README on GitHub. see https://github.com/sealerio/sealer#code-of-conduct
- [x] CII: Start on a CII best practices badge https://bestpractices.coreinfrastructure.org/en. Done, see https://bestpractices.coreinfrastructure.org/en/projects/5205
- [x] Adopt a license scanning tool, like FOSSA or Snyk. Done, see https://app.fossa.com/projects/git%2Bgithub.com%2Fsealerio%2Fsealer/refs/branch/main/304fda7ce4801f97ed992cc8cde375ae2f1539eb/preview
All the above are done. Please help to check and mark. Thanks.
Marking off as done, invites are out for servicedesk and maintainers lists!
Marking off as done, invites are out for servicedesk and maintainers lists!
We have received the invitation of servicedesk and maintainers lists.
- [ ] Trademarks: transfer any trademark and logo mark assets over to the LF - https://github.com/cncf/foundation/tree/master/agreements has agreements
- [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).
@amye These two have been completed
Trademarks: transfer any trademark and logo mark assets over to the LF - https://github.com/cncf/foundation/tree/master/agreements has agreements -- we'll need a fully executed copy from both sides. I don't have anything in the project onboarding inbox? [email protected] is a great place to put that.
Hi @allencloud and @fanux ! My name is Crystal and I am the new project coordinator in charge of onboarding sandbox projects!
I'm checking in to see if you had a chance to see Amye's response. Did you have any questions or concerns regarding trademark and logo mark asset transfer? I would be happy to help in any way I can!
@Cmierly Maybe something went wrong somewhere and we re-signed the agreement. Before the official agreement is approved, I would like to confirm with you whether there is any problem with the content of the agreement.
So is it convenient for you to provide a suitable way? I will send the draft agreement to you for preliminary review. THX. 😄
@Cmierly Maybe something went wrong somewhere and we re-signed the agreement. Before the official agreement is approved, I would like to confirm with you whether there is any problem with the content of the agreement.
So is it convenient for you to provide a suitable way? I will send the draft agreement to you for preliminary review. THX. 😄
Not sure what the issue is? I don't have a signed copy of either registered or non-registered.
@amye The agreement needs to be approved before it can be used, and this approval process is not easy. Therefore, before going through the approval process, we want to confirm whether there is a problem with the content.
I wonder if it is appropriate for me to send a draft version to [email protected] and look forward to confirmation feedback on the agreement content
@amye The agreement needs to be approved before it can be used, and this approval process is not easy. Therefore, before going through the approval process, we want to confirm whether there is a problem with the content.
I wonder if it is appropriate for me to send a draft version to [email protected] and look forward to confirmation feedback on the agreement content
We only have two agreements - non-registered trademark and registered trademarks. If you want something different, we'll need to work with Legal on our end.
@amye We have not applied for any trademark regarding sealer even if for word mark, design, and logo marks. So we couldn't sign the agreement as assignor. I wonder if we have any good suggestions?
@amye Now, we can only sign the aggrement(no reg trademarks) as the owner of the SEALER domain name. And I have sent a draft version to [email protected], please help to confirm that whether the content meets the requirements.
Responded with more details, but I think we can take trademarks offline from here. Happy to help with other onboarding tasks!