toc
toc copied to clipboard
cncf
[SANDBOX PROJECT ONBOARDING] External Secrets Operator
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
- [x] 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] Marketing: update relevant intro + slide decks
- [x] Events: update CFP + Registration + CFP Area forms
- [ ] ServiceDesk: confirm maintainers have read https://www.cncf.io/services-for-projects/
- [ ] CNCF Welcome Email Sent to confirm maintainer list access, welcome email has monthly project sync details
- [ ] 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
Hey there! We're thrilled about this! :tada: :partying_face: We've created the above :point_up_2: linked issue to assign/track the work on our end. I'm sure there will be questions, we'll post them here.
Do you want us to post a proof of something when we've finished some piece of work: E.g. a screenshot of adding the LF footer to the website or a screenshot of GitHub Org ownership?
Hey all! Some questions came up to this one:
[ ] Website: Analytics transferred to [email protected]
Is it enough to add [email protected] to owner in our google analytics, or does transfer mean a different thing here? If it means a different thing, can anyone point us to the direction on how to? :smile:
Try the first one and I'll check it for you
Thanks for your help! Just added to our analytics!
Another Question, we have an Opencollective sponsoring page, with individual contributors and Organisation contributors. Is there a problem with keeping it? Is there any action items related to that that we are not aware of?
Regarding the slack channel, we wanted to check if we could get admin rights in the channel that we already have in K8S slack space? We have a lot of movement there, I think we would confuse some users migrating to a new space.
About the domain, we have it in Google Domains. Is it enough to add that email as owner? Or do we have to go through the actual transfer to the other service?
Emails from maintainers :)
Lucas Severo Alves, knelasevero, [email protected] Moritz johner, moolen, [email protected] Gustavo Fernandes de Carvalho, gusfcarvalho, [email protected]
@gusfcarvalho @moolen do you think we should add more emails here? We have more people as emeritus approvers, etc.
Hello! some questions regarding the trademark transfer (non registered): Paragraph 3.a As Container Solutions, are we allowed to still refer to eso logo? What are the rules for that? (e.g. running meetups, social media content, blog posts)
ESO is a joint community project. In so, Container Solutions does not own any top level domain bound to the ESO Logo. How would Paragraph 3.b apply in this case? Do we need extra sign offs from the other people/organizations that own these resouurces?
Is there any legal team we can forward our questions to, either on a call or via email?
Short answer: https://www.linuxfoundation.org/trademarks/ Longer answer: The project is still allowed to use the logo, we at CNCF/LF just hold the logo as part of the neutral home for IP. If you don't have a domain, that's fine.
Short answer: https://www.linuxfoundation.org/trademarks/ Longer answer: The project is still allowed to use the logo, we at CNCF/LF just hold the logo as part of the neutral home for IP. If you don't have a domain, that's fine.
Thanks for the answer, but something is still not clear! the project does have a domain, but it is not owned by the organization that owns the logos (since this project was really community-driven ever since from the beginning, different people got responsible for different things). The domain is owned personally by another maintainer and would be donated anyways. The question would be: do we need the maintainer that owns the domain to also sign a separate document? Or just the one from Container Solutions (the org owning the logos) would be enough?
Sorry for these questions - they are been asked by our legal teams here, and I am not that versed on the theme, unfortunately 😅
Hello!
Regarding the ongoing process for onboarding, there are only two points that we remaing to do, and we still some help on them:
-
the first one is regarding the domain transfer to the CNCF. We currently have our domain in Google Domains, and we would like to know if it would be enough to add owner permissions there, or if a domain transfer would really be necessary
-
The second one is more tricky, it is regarding about transfering logo assets over to the LF. The logos for the project are from the company where I work at (Container Solutions), but the domain itself is from another maintainer which is not part of Container Solutions (this project was really built up from the community, so multiple people own different things). When I showed the non-trademark agreement to our legal team, they became a little bit uncertain about clause 3.b - basically because since Container Solutions does not own the domain where the logo is applied, we as a company would not be able to conform to this clause. What I thought about doing is to have the maintainer sign that documentation together with Container Solutions (which would cause a change to the agreement as written), so I wanted to see if that would be acceptable for CNCF.
Any help would be appreciated!
Hello!
Regarding the ongoing process for onboarding, there are only two points that we remaing to do, and we still some help on them:
- the first one is regarding the domain transfer to the CNCF. We currently have our domain in Google Domains, and we would like to know if it would be enough to add owner permissions there, or if a domain transfer would really be necessary
We'll need to have that transferred, it's part of the assets for the project overall. https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/create/63 is the best place to start.
- The second one is more tricky, it is regarding about transfering logo assets over to the LF. The logos for the project are from the company where I work at (Container Solutions), but the domain itself is from another maintainer which is not part of Container Solutions (this project was really built up from the community, so multiple people own different things). When I showed the non-trademark agreement to our legal team, they became a little bit uncertain about clause 3.b - basically because since Container Solutions does not own the domain where the logo is applied, we as a company would not be able to conform to this clause. What I thought about doing is to have the maintainer sign that documentation together with Container Solutions (which would cause a change to the agreement as written), so I wanted to see if that would be acceptable for CNCF.
What we've done in the past is have the group of maintainers who contributed the project over, is that the group that's listed in your PR for maintainers.cncf.io?
Any help would be appreciated!
We internally arranged a transfer of the domain to Container Solutions, so our legal team was comfortable with signing the agreement -> Assignment - Signed by CS.pdf. Is it enough to upload it here?
We will need to review this, please send this to [email protected]
Done!
We're also done with these following items:
- [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 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/ 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
- [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] [Under Review by CNCF, sent email to [email protected]]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
We didn't yet receive any invitation to the maintainers.cncf.io, so probably this still needs to be added. The maintainer emails are:
- Lucas Severo Alves, knelasevero, [email protected]
- Moritz johner, moolen, [email protected]
- Gustavo Fernandes de Carvalho, gusfcarvalho, [email protected]
Not seeing a domain transfer or Github, can you check for me? Invites have been sent to maintainers lists and Service desk.
Domain transfer: https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-24483 :)
What specifically about github?
This is done and verifiable at any PR: https://github.com/external-secrets/external-secrets/pull/1537
- [x] GitHub: ensure 'thelinuxfoundation' and 'caniszczyk' are added as initial org owners, this helps us make sure we have continuity of GH ownership
Oh, caniszczyk is added, checking now it seems linuxfoundation recevied the invitation but that account let it expire:
We just re-sent to thelinuxfoundation account.
Taken care of! Do you want a space on community.cncf.io?
Yes please 😁
https://community.cncf.io/external-secrets-operator-community/ is live, who should get access?
@amye
Lucas Severo Alves, knelasevero, [email protected] Moritz johner, moolen, [email protected] Gustavo Fernandes de Carvalho, gusfcarvalho, [email protected]
Us 3 I think. @moolen @gusfcarvalho anybody else?
Thank you! I've added FOSSA integration and identified a couple of issues with usage of MPL-2.0 (hashicorp libs). I'm tracking a investigation here: https://github.com/external-secrets/external-secrets/issues/1820. I'm probably gonna open an issue in cncf/foundation to request a exemption for the remaining two libraries.