[LEVEL CHANGE] Tekton To Incubation

[riaankleinhans]

This issue contain both the Sandbox on-boarding and changing levels checklist to make sure we do not miss any steps bringing Tekton in to the CNCF

Project Moving Levels Checklist - (Changing level step)

This template outlines the administrative steps required when a project moves from one maturity level to another (e.g., Sandbox to Incubating, Incubating to Graduated).

• Project Name: Tekton
• New Maturity Level: Incubation
• Project moving levels PR: Add Tekton Incubation Due Diligence Report #2050

---

Administrative Checklist

• TOC vote passed
• Moving levels PR merged
• Email Formation team to move the project's level in PCC.
• Ensure the project is in Google Group mailing lists maintainers@cncf.io
• 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.
• Move the project to the new level in Clomonitor
• Move the project to the new level in Devstats
• Move artwork in cncf/artwork
• Move project in maintainer spreadsheet
• Sent email to CNCF PR team for marketing the change
• Run CNCF Calendar update automation

Welcome to CNCF Project Onboarding (Sandbox on-boarding list, to make sure we do not miss any steps)

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. 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.
• 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 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 or 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 LFX Slug (lfx_slug) in the landscape configuration. The slug can be found in LFX Project Control Center app in Project Definition section of the corresponding project.
• 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
• Send a welcome email to confirm maintainer list access.

[vdemeester]

@riaankleinhans I'll add comments to this issues on the items we "control" (we being the tekton maintainers)

REQUIRED BEFORE PROCEEDING

• Review and understand the CNCF IP Policy

All Tekton repos use Apache 2.0. Reviewed by me (@vdemeester), cc @afrittoli @enarha @dibyom @abayer for confirmation.

• Review and understand the CNCF Third Party License Policy

Reviewed by me (@vdemeester), cc @afrittoli @enarha @dibyom @abayer for confirmation.

• Review and understand the LF trademark guidelines

Reviewed by me (@vdemeester), cc @afrittoli @enarha @dibyom @abayer for confirmation.

Contribute and transfer other materials

• Move your project to its own separate neutral GitHub organization.

tektoncd org is a standalone GitHub organization with thelinuxfoundation as an org owner.

• Accept the invite to join the CNCF GitHub Enterprise account.

thelinuxfoundation is already an owner of both the tektoncd and tektoncd-catalog orgs. Billing is still under Google LLC — does this need to be transferred as well? Also, is having tektoncd-catalog as a separate org a problem, or is it fine as long as thelinuxfoundation is an owner there too?

• Migrate Slack channels to the Kubernetes or CNCF Slack workspace.

Tekton currently has its own Slack workspace and a #tekton channel on the CNCF Slack workspace. We plan to run a community poll to decide where the official channels should live (Kubernetes Slack or CNCF Slack). All existing workspaces/channels will remain active during the transition.

Update and document project details

• Ensure that DCO or CLA are enabled for all GitHub repositories.

EasyCLA is active on all tektoncd and tektoncd-catalog repos.

• Ensure that the CNCF Code of Conduct is explicitly referenced in the project.

Adopted in tektoncd/community/code-of-conduct.md. Does this also need to be referenced in each individual repo's README, or is the community repo sufficient?

• Ensure the LF footer is on your website and guidelines are followed.

tekton.dev includes CNCF logo, LF copyright, and trademark notice.

• Start working on written, open governance.

tektoncd/community/governance.md documents the Tekton Governance Committee, election process, and decision-making.

• Start working on an OpenSSF Best Practices Badge.

Passing for Pipeline, Chains, CLI, Triggers, Dashboard, and Operator. In progress for Results. We are aiming to cover the remaining active repos: pipelines-as-code, catalog, community, plumbing, and website.

[afrittoli]

Thanks @vdemeester - I reviewed all relevant docs as well.

@riaankleinhans Tekton is already a LF project, it used to be hosted by CDF, it's now hosted by CNCF. From an LFX point of view, the project needs to be migrated from CDF to CNCF. For EasyCLA I'm not sure if it can stay as it is or if it needs to be migrated as well from CDF to CNCF. We have a combination of ICLA and CCLA, please let us know if there is any action needed from our side.

• Move artwork in cncf/artwork

The Tekton artwork today is hosted at https://github.com/cdfoundation/artwork/tree/main/former_project_logos/tekton

[vdemeester]

@riaankleinhans @afrittoli created pull requests for the artwork (imported from the cdfoundation/artwork) and the maintainers list.