Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PROJECT ONBOARDING] Tratteria #329

Open
31 tasks
mrbobbytables opened this issue Jan 21, 2025 · 2 comments
Open
31 tasks

[PROJECT ONBOARDING] Tratteria #329

mrbobbytables opened this issue Jan 21, 2025 · 2 comments

Comments

@mrbobbytables
Copy link
Member

Welcome to CNCF Project Onboarding

Sandbox Reference Issue: #115

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 an 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 further project onboarding tasks can be completed.

  • 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 LF trademark guidelines.
  • 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

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 a 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.
  • Join the #maintainers-circle Slack channel.
  • Transfer your domain to the CNCF. The "LF Stakeholder email" is [email protected]. The "Project" is CNCF.
  • Submit a pull request with your artwork.
  • Transfer website analytics to [email protected]. CNCF staff can help.

Update and document project details

  • Ensure that DCO (preferred) or CLA are enabled for all GitHub repositories of the project.
  • Ensure that that the CNCF Code of Conduct (or your adopted version of it) are explicitly referenced at the project's README.md on GitHub.
  • Ensure 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). The project-specific footer text you should use will be provided in the Contribution Agreement instructions.
  • Create a maintainer list and add it to the aggregated CNCF maintainer list via pull request.
  • Provide emails for the maintainers to get access to the maintainers mailing list and Service Desk. Email them to [email protected].
  • Start working on written, open governance and consider adding this to a GOVERNANCE.md file at the root of your repo.
  • Start on an OpenSSF Best Practices Badge.

CNCF staff tasks to support the project

@tulshi
Copy link

tulshi commented Jan 21, 2025

Hi @mrbobbytables, thanks for getting this kicked off. I have one question. We have received feedback that the name "tratteria" is hard to remember and also gets autocorrected to "trattoria" anytime someone types it. We are thinking of looking for a new name for the project and rebranding it.

Would it be better to explore rebranding the project before we brought it into the CNCF Sandbox or afterwards?

@mrbobbytables
Copy link
Member Author

Ideally beforehand, there’s a lot of places where the name would have to be updated. It’d at least make trademark transfer easy - once a name is assigned can actually establish once joined

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants