yada
commented
1 year ago 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.
We thank the CNCF Technical Oversight Committee (TOC) members for their validation and the TAG App Delivery team for their invaluable support during this process.
Please see below an update regarding the actions performed:
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
β read, understood and validated.
- [x] Understand the services available for your project at CNCF https://www.cncf.io/services-for-projects/
β read, understood and validated.
- [x] Ensure your project meets the CNCF IP Policy: https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy
β read, understood and validated.
- [x] Review the online programs guidelines: https://github.com/cncf/foundation/blob/master/online-programs-guidelines.md
β read, understood and validated.
- [x] Understand the trademark guidelines: https://www.linuxfoundation.org/legal/trademark-usage
β read, understood and validated.
- [x] Understand the license allowlist: https://github.com/cncf/foundation/blob/master/allowed-third-party-license-policy.md#approved-licenses-for-allowlist
β read and understood. We have a deep assessment of our dependencies are have well known libraries using non-approved (or not listed) licenses in the Allowlist (ex: Eclipse public license): we can allow them with some assistance? Thank you for clarifications on this point.
- [x] Is your project working on written, open governance? see https://contribute.cncf.io/maintainers/governance/
β read and understood. We will work on it asap.
- [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)
β See: https://cloud-native.slack.com/messages/microcks channel ID on CNCF Slack is C05BYHW1TNJ
- [x] Is your project in its own separate neutral github organization?
β Yes
- [x] Submitted a Pull request to add your project as a sandbox project to https://landscape.cncf.io
β See: https://github.com/cncf/landscape/pull/3285
- [x] Create maintainer list + add to aggregated https://maintainers.cncf.io list by submitting a PR to it
β See: https://github.com/cncf/foundation/pull/588
- [x] Artwork: Submit a pull request to https://github.com/cncf/artwork with your artwork
β See: https://github.com/cncf/artwork/pull/416
- [x] Domain: transfer domain to the CNCF - https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/create/63
β See: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-25739
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 - project-onboarding@cncf.io is the best email to send those to
β Email sent:
from: | Yacine KheddacheΒ <yacine@microcks.io>
-- | --
to: | project-onboarding@cncf.io
cc: | Laurent Broudoux <laurent@microcks.io>,Amye Scavarda Perrin <amye@linuxfoundation.org>
date: | Jun 28, 2023, 11:18β―AM
subject: | [Microcks] 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
β read and understood. Microcks logo and trademark is owned by the community. Could you please send to the maintainers a non-corporate and non-registered agreement?
Maintainers emails available to sign are: laurent@microcks.io yacine@microcks.io
- [x] GitHub: ensure 'thelinuxfoundation' and 'caniszczyk' are added as initial org owners, this helps us make sure we have continuity of GH ownership that we will onboard to our GitHub Enterprise instance: https://github.com/enterprises/cncf
β invitation to join has been sent.
β DCO has been setup and activated.
- [x] GitHub: ensure that that 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/microcks/microcks Section "Getting Started"
- [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).
β See: https://microcks.io/
- [ ] Website: Analytics transferred to projects@cncf.io
Waiting for confirmation (see question below).
- [ ] OpenSSF Best Practices Badge: Start on an OpenSSF Best Practices Badge https://bestpractices.coreinfrastructure.org/en
WIP, see: https://bestpractices.coreinfrastructure.org/en/projects/7513
Things that the CNCF will do or help the project to do:
- [ ] Devstats: add to devstats https://devstats.cncf.io/
- [ ] 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
- [ ] Book time with the team with http://project-meetings.cncf.io
- [ ] Adopt a license scanning tool, like FOSSA or Snyk
lukaszgryglicki
lbroudoux
amye
Cmierly
RobertKielty
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:
Things that CNCF will need from the project:
Things that the CNCF will do or help the project to do: