Project Moving Levels Checklist: KServe joining CNCF at Incubation level

[riaankleinhans]

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 your project to complete onboarding within one month of acceptance.

Please track your progress by using "Quote reply" to create your own copy of this checklist in the issue, so that you can update the status as you finish items.

REQUIRED BEFORE PROCEEDING WITH ONBOARDING

A "Project Contribution Agreement" must be completed and any existing trademarks MUST be transferred to the Linux Foundation BEFORE the CNCF staff onboarding tasks can be completed. Other tasks can be done by projects themselves in the meantime.

• Review and understand the CNCF IP Policy. Ensure you are using a CNCF compatible license; inbound projects must use the Apache 2.0 license or seek approval for exceptions. Licenses for dependencies are covered separately below.
• Review and understand the CNCF Third Party License Policy. This policy governs the licenses used by third party libraries in your project. CNCF FOSSA or CNCF Snyk are configured to check that projects are in compliance with this policy. Let us know which service you would prefer to use.
• Review and understand the LF trademark guidelines. Let the TOC know if you plan to change your project name.
• Transfer any trademark and logo assets to the Linux Foundation via the Contribution Agreement. CNCF staff will send this document to the contact emails listed in the Sandbox application.

---

Review and understand other documents

• The Technical Leadership Principles that outline the expected behavior for any maintainer in a leadership role.
• The project proposal process and requirements.
• The services available for your project at the CNCF.
• The online program guidelines.
• The telemetry data collection and usage policy.
• Optional: Book time with CNCF staff to understand CNCF resources available to you, to work through onboarding tasks together, or ask other questions.

Contribute and transfer other materials

• Move your project to its own separate neutral GitHub organization. This will make it transferable to the CNCF's GitHub Enterprise account. If it's already in another GHE account, you will need to remove it from that first.
• Accept the invite to join the CNCF GitHub Enterprise account. We'll then add thelinuxfoundation as an organization owner to ensure neutral hosting of your project.
• Migrate your Slack channels (if any) to the Kubernetes or CNCF Slack workspace. CNCF staff can help. This allows project communities to be more discoverable, allows the CNCF to enforce its Code of Conduct, and enables unlimited message retention.
• Join the #maintainers-circle Slack channel to find and share knowledge with other project teams.
• Transfer your domain(s) to the CNCF if they exist. The "LF Stakeholder email" is projects@cncf.io. The "Project" is CNCF.
• Submit a pull request with your artwork if it exists. If you don't have artwork, CNCF can help design some. Add KServe Project artwork artwork#593
• Transfer website analytics if they exist. Make projects@cncf.io an admin of your existing Google Analytics org account so that we can move it to a CNCF-managed account.

Update and document project details

• Create a maintainer list and add it to the aggregated CNCF maintainer list via pull request.
• Provide maintainer emails to get access to the mailing list and Service Desk. Send them to project-onboarding@cncf.io. These aren't shared publicly in the spreadsheet above which is why they must be emailed to us.
• Ensure that DCO are enabled for all GitHub repositories of the project. You may also choose to use a CLA.
• Ensure that that the CNCF Code of Conduct (or your adopted version of it) are explicitly referenced in the project's README.md on GitHub.
• Ensure the LF footer is on your website and guidelines are followed (if your project doesn't have a dedicated website, please adopt those guidelines for the README.md file).
• Start working on written, open governance and consider adding this to a GOVERNANCE.md file at the root of your repo.
• Start working on a security policy and consider adding this to a SECURITY.md file at the root of your repo.
• Start working on an OpenSSF Best Practices Badge.
• Import all project repos into your chosen license scanning service (CNCF FOSSA of CNCF Snyk).

CNCF staff tasks to support the project

• Add the project to DevStats.
• Add the project to CLOmonitor.
• Add the project to LFX Insights.
• Add the project to the Cloud Native Landscape.
• Activate the project in the LFX Project Control Center.
• Add the maintainers team to a license scanner service, either, CNCF FOSSA or CNCF Snyk.
• Create groups.io project maintainer list in PCC.
• Add project's groups.io maintainer list to maintainers@cncf.io
• Add project's groups.io cncf-sandbox-projects list to cncf-sandbox-projects@cncf.io
• Send a welcome email to confirm maintainer list access.

Project Incubation level check list

Administrative Checklist

• TOC vote passed [Incubation] KServe Incubation Application #1367
• Moving levels PR merged Add KServe Incubation Due Diligence Report #1862
• Send email to Formation team to move project level in PCC.
  • Confirmation from Formation team and checked in PCC
  • Update CNCF/Calendar
• Move the project in Google Group mailing lists from its current group to the new one (e.g., from cncf-sandbox-projects to cncf-incubating-projectsto cncf-graduated-projects).
• Update the project's level and maintainer list in the aggregated CNCF maintainer list
• Move the project to its new level on the CNCF Landscape Bump kserve to incubating landscape#4532
• Update CNCF Maintainer List spreadsheet
• Send email to cncf-foo-maintainers@lists.cncf.io & pr@cncf.io to announce the new level
• Update DevStats instance

[terrytangyuan]

Since KServe was hosted under LF AI and Data, we may need to include some onboarding tasks as well.

[lukaszgryglicki]

It's not clear for me, there is no separate KServe project in DevStats and this request is to update Knative DevStats instance.

Can I have some clarifications? Maybe this project was renamed from something else and I need to update some existing DevStats instance (but I don't think it's Knative) or maybe it was split out from another project - 1st as Sandbox and now this moves to Incubating - but then I need to know from which project it was split? So I can update both projects configurations.

Ideally LMK when this project was accepted/split/renamed into Sandbox so I can create a DevStats instance accordingly.

cc @riaankleinhans @krook @caniszczyk

[yuzisun]

It's not clear for me, there is no separate KServe project in DevStats and this request is to update Knative DevStats instance.

Can I have some clarifications? Maybe this project was renamed from something else and I need to update some existing DevStats instance (but I don't think it's Knative) or maybe it was split out from another project - 1st as Sandbox and now this moves to Incubating - but then I need to know from which project it was split? So I can update both projects configurations.

Ideally LMK when this project was accepted/split/renamed into Sandbox so I can create a DevStats instance accordingly.

cc @riaankleinhans @krook @caniszczyk

@lukaszgryglicki the project was moved from LFAI to CNCF incubating project, we did not went through the sandbox process.

[lukaszgryglicki]

OK, so from CNCF POV it will be like a new project that joins already at the Incubation level, right?

[terrytangyuan]

Yes, we need to include new project onboarding tasks.

[riaankleinhans]

Ah! I missed that. I will add the Sandbox on-boarding tasks to the checklist today as well.

[riaankleinhans]

• Submit a pull request with your artwork if it exists.
  Removed artwork from LF AI & Data - Remove KServe project lfai/artwork#40
  Added artwork to CNCF Artwork - Add KServe Project artwork artwork#593