sandbox

KO | EN

gitlite — search

#javascript #python #ai #typescript #llm #rust #macos #nodejs #windows #cli #vue #security #mcp #open-source

(★ 193)

Applications for Sandbox go here! ⏳📦🧪

파일 탐색기

최종 버전 다운로드 (.zip)

- - application.yml
  - config.yml
  - project-onboarding.md
- - contribution-agreement-label-commands.yml
  - contribution-agreement-signed-onboarding.yml
  - onboarding-monitor.yml
  - README.md
  - sandbox-application-review.yml
  - vote-monitor.yml
- create-onboarding-issue.js
- onboarding-progress-monitor.js
- sandbox-application-review-prompt.md
- sandbox-application-review.js
.gitvote.yml
LICENSE
README.md

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Sandbox

![CNCF Sandbox](https://raw.githubusercontent.com/cncf/artwork/main/other/cncf-sandbox/horizontal/color/cncf-sandbox-horizontal-color.png)

This repository is designed to allow projects seeking to join the CNCF as a :package: [Sandbox](https://github.com/cncf/toc/blob/main/process/README.md) :package: project to submit their applications. It is still a work in progress and we welcome PRs on this repo to automate assignments, improve the process, etc.  If you have any questions, please reach out in the [TOC Slack Channel](https://cloud-native.slack.com/archives/C0MP69YF4) or file an [issue](https://github.com/cncf/sandbox/issues/new) on the repo.

For information on the sandbox process please check out the [details on our sandbox application process below](#how-applications-are-reviewed).

> [!NOTE]  
> Projects which are primarily [Operators](https://www.cncf.io/blog/2022/06/15/kubernetes-operators-what-are-they-some-examples/) enabling another open source project to be Cloud Native should first contact that project about joining it as a subproject. If that isn't possible, please consider alternative foundations for membership as well, such as CommonHaus, SPI, or language based foundations such as the Rust Foundation.

## How to apply

Applying is as easy as 1-2-3!

1. Open a new [Sandbox Application](https://github.com/cncf/sandbox/issues/new?assignees=&labels=New&projects=&template=application.yml&title=%5BSandbox%5D+%3CProject+Name%3E) using the linked issue form.
1. Complete all sections of the form.
1. Submit the issue.

> [!CAUTION]
> The TOC MUST vote to approve your application and a [Contribution Agreement](https://github.com/cncf/foundation/blob/main/agreements/Sample%20Contribution%20Agreement%20(2025).pdf) MUST be signed before your project can be considered an official CNCF project. You can not represent your project as "donated" or "contributed" until those steps are completed. Please read more below.

### Before you apply: Common reasons applications are closed

Many applications are closed without TOC review due to not meeting basic eligibility criteria. Review these requirements before applying to avoid wasted effort:

**✅ License Compliance**
- Must use Apache 2.0
- License must be compliant **before** acceptance (promises to "convert after acceptance" are not accepted)
- BSL (Business Source License) and GPL family licenses are not acceptable
- Dependencies must follow the [CNCF IP Policy](https://github.com/cncf/foundation/blob/main/charter.md#11-ip-policy) or have an existing [blanket license exception granted](https://github.com/cncf/foundation/blob/main/policies-guidance/allowed-third-party-license-policy.md#cncf-allowlist-license-policy)
- **License exceptions:** If you believe your project is a good fit despite using a non-allowlist license, you may [request a license exception](https://contribute.cncf.io/projects/submit-license-exception-request/) from the CNCF Governing Board. Note: exceptions are rarely granted and require Governing Board approval.

**✅ MAINTAINERS File**
- Must provide direct link to MAINTAINERS.md or MAINTAINERS file (GitHub `/blob/` or GitLab path)
- Cannot link to contributors graph, external website, or say "N/A" / "will be added"
- File must contain table with: Name, ID, **Company/Organization** columns

**✅ Organization Diversity** *(not a requirement, but considered during review)*
- The TOC considers maintainer employer diversity when evaluating applications
- "Organization" = employer/company, NOT GitHub/GitLab organization memberships
- Being members of different GitHub orgs does not count as organization diversity

**✅ Subproject Separation**
- If your project is under another project's GitHub/GitLab organization, you must provide a link to a **public issue** in the parent project's repository showing maintainer consensus to split into separate CNCF project
- Applies to ANY parent project (not just CNCF projects)

**✅ Project vs Reference Architecture**
- CNCF Sandbox accepts reusable projects, not reference architectures or implementations
- If your project shows how to wire together existing tools (not building new tool), submit to [CNCF Reference Architectures](https://architecture.cncf.io/)

For detailed requirements and examples, review the [application form](https://github.com/cncf/sandbox/issues/new?assignees=&labels=New&projects=&template=application.yml&title=%5BSandbox%5D+%3CProject+Name%3E) which includes inline guidance.

## What's next?

Your project's application is placed in the backlog for triaging. You can view the status of your application and others at anytime by checking out our [Project Board](https://github.com/orgs/cncf/projects/14).

As we approach Sandbox application review meetings, CNCF staff will move applications to the "upcoming" column on the Project Board (number dependent on how many can be reviewed in a given meeting). At this point, the TOC will ask questions, seek to learn more, and make a decision on project inclusion. Projects which applied may also field questions from interested community members beyond TOC questions.

> [!NOTE]
> TAG Leads and members of the [TOC Project Reviews Subproject](https://github.com/cncf/toc/tree/main/toc_subprojects/project-reviews-subproject) may optionally support applications by conducting a General Technical Review up until two weeks before a TOC Sandbox review session to allow time for the project maintainers to respond to any questions. Any comments, questions or clarifications during a review are to remain on the Sandbox application issue and not in separate meetings or channels aside from the Project Reviews Subproject slack channel and the Maintainers Circle channel. Such reviews are voluntary and provide additional technical context to assist the TOC, but are not a required step in the process. For details on how the review is conducted, see the [Sandbox Review Guide](https://github.com/cncf/toc/blob/main/toc_subprojects/project-reviews-subproject/sandbox-review-guide.md).

### Community Comments on Applications

The TOC welcomes and appreciates community members' support and exploration in surfacing items for technical consideration as part of sandbox applications; it allows the TOC to have a more comprehensive perspective on each project's potential.

In keeping with the [Technical Leadership Principles](https://github.com/cncf/toc/blob/main/PRINCIPLES.md#technical-leadership-principles), community members providing comments and questions should [be welcoming and curious in their comments](https://github.com/cncf/toc/blob/main/PRINCIPLES.md#be-welcoming), [provide feedback with courtesy](https://github.com/cncf/toc/blob/main/PRINCIPLES.md#provide-feedback-and-appreciation-appropriately), and [foster respectful resolution](https://github.com/cncf/toc/blob/main/PRINCIPLES.md#foster-respectful-resolution).  Embodying the technical leadership principles as you comment on these applications directly contributes to sustaining the open, community-oriented nature of CNCF.

### The TOC's sandbox review meeting

When the TOC meets to review applications, more details on [frequency here](#frequency), your application will be pulled up and discussed. Your application may receive one of several statuses:

* `New` - It is a brand new application and is in the backlog for an upcoming review.
* `Approved` - The application has been reviewed and been approved by the TOC. The issue will be closed.
* `Declined` - The application has been reviewed and been declined by the TOC. The comments on the issue will reflect the TOC decision and the issue will be closed.
* `Need-Info` - The application has been reviewed and requires more information in order for the TOC to further discuss the application.  For instructions on what to do, please jump down to [Need-Info](#need-info).
* `Postponed` - The application has been reviewed and the TOC has determined the project (as it exists at time of review) is not ready for inclusion within the CNCF. For instructions on what to do, please jump down to [Postponed](#postponed)
* `Returning` - The application has been reviewed previously, was affixed a `Need-Info` label, and that work has been completed and is ready for re-review.  For instructions on what to do, please jump down to [Returning](#returning).

### Label statuses defined

Removing, updating, and adding labels as well as updating the project board are the responsibility of the TOC and CNCF staff.

#### New

The application is new and placed in the backlog.

#### Approved

The application has been approved.

#### Declined

The application has been declined.

#### Need Info

If your project is assigned a `Need-Info` label, the TOC will comment on the issue with the specific additional information needed.  It will then be placed in the `Waiting` status of the [Project Board](https://github.com/orgs/cncf/projects/14).

Please provide the additional information requested as a comment on the issue with links as appropriate. Once you have done this, please add the below text to your comment so the TOC and staff know to update the issue:
`Completed info, project is Returning`

This lets the TOC know the project is ready to be reviewed again. A TOC member or staff will remove the `Need-Info` label and affix `Returning` where it will then be removed from the `Waiting` status and placed in the `Upcoming` status for discussion at the next meeting.

#### TAG Leads – Optional General Technical Review

TAGs no longer conduct formal project reviews as part of the sandbox application process. However, TAG Leads and members of the [TOC Project Reviews Subproject](https://github.com/cncf/toc/tree/main/toc_subprojects/project-reviews-subproject) may optionally support applicants by performing a **General Technical Review**. The process for such reviews is described in the [Sandbox Review Guide](https://github.com/cncf/toc/blob/main/toc_subprojects/project-reviews-subproject/sandbox-review-guide.md). Such reviews must be completed up until two weeks prior to a TOC Sandbox Review session in order to give project maintainers time to respond. These reviews are intended to provide additional technical context to the TOC. They do not result in a label or a required action for applicants.

> [!NOTE]
> Projects may still reach out to the relevant TAG(s) directly for technical input, guidance, or feedback on their application at any time.

#### Postponed

If the issue has been affixed with the `Postponed` label it will be closed as the TOC has determined the project at the time of discussion is not ready for inclusion into the CNCF. There will be a comment on the issue that annotates the expectations in order for the project to be re-reviewed by the TOC. Depending on the status and details, there are a few options to be re-reviewed. For information on review ordering for postponed projects, plese refer to the [Review Order section](#review-order).

##### Returning for review after being postponed

a. If the project has had substantial changes to the original information provided, open a new issue and link to the previous issue in the `Additional information` question (last question on the form). The project will be reviewed as if it were a new project applying but retain the historical context of the previous review to assist in evaluation.

b1. If the project has had *no* substantial changes, the originator of the issue may reopen it and provide a brief status update that addresses the TOC closure comments with a comment `Revisit Ready`. The TOC or staff will apply the `Returning` label and place the issue in the `Upcoming` status for discussion at the next meeting.

b2. If the individual seeking to reopen the issue is NOT the originator of the issue AND the project has had no substantial changes, provide a brief status update that addresses the TOC closure comments. The TOC or staff will reopen the issue and apply the `Returning` label and place the issue in the `Upcoming` status for discussion at the next meeting.

#### Returning

Issues affixed with the `Returning` label are placed in the `Upcoming` status on the [Project Board](https://github.com/orgs/cncf/projects/14) for an updated discussion at the next Sandbox Application meeting.

## How applications are reviewed

### Frequency

The TOC reviews sandbox applications approximately **every two months** as of June 2020 in a non-public meeting; referred to as "session" hereafter.

### Quantity

The TOC attempts to work through approximately 7-10 applications per session. How many are actually reviewed in a session varies greatly between each session. Every project is unique and may warrant different areas of attention to be elevated for more in-depth discussion, depending on the nature and function of the project.

Each TOC member prepares for these sessions by performing an independent review of those projects scheduled for discussion at the next session prior to that session. They'll keep their notes on hand for when the project is up for discussion.

### Review order

Sandbox applications are traditionally reviewed in a First In, First Out (FIFO) ordering as they appear on the **🏗 Upcoming** Column of the [Sandbox Application Board](https://github.com/orgs/cncf/projects/14/views/1) by their corresponding issue number. The only exception is where projects are `Returning` for review. Projects that are `Returning` are prioritized for re-review as they had previously been subject to a review and have completed their outstanding asks. In cases where a project was `Postponed` and has substantial changes since last review, a new issue is opened, linked to the previous, and reviewed as a new application. Refer to the [Postponed label definition for more information](#postponed).

Applications are moved from `New` to `Upcoming` approximately two weeks prior to the next scheduled session by the TOC or support staff.

### Discussions and decision

During the course of the session, the TOC will actively discuss the project based on the information provided in the issue as well as other observations the TOC has about the project. Those observations vary greatly and may be subject to each TOC member's area of domain expertise, personal experience, community feedback, or other factors. During the course of active discussion, the TOC may identify areas the project needs to work on, complete, or allow to happen that could inhibit its acceptance into the CNCF. These areas will be captured succinctly and affixed the corresponding label ([see Label statuses defined](#label-statuses-defined) for more information). The issue will also receive a comment that details the additional areas that correspond with the label. The TOC comment may be formatted as a checklist or may be presented as text.

#### Examples

All project and organization names in the examples are fictional and are not intended to reflect any existing project past or present.

##### Baggywrinkle

The TOC reviews and discusses Baggywrinkle. The TOC determines Baggywrinkle doesn't have sufficiently clear direction or indicators on what the project does or how it does it. The TOC will summarize the items that need to be addressed on the issue as checkbox items and affix the `Need-Info` label. The application is then moved to the **⏲ Waiting** Column of the [Sandbox Application Board](https://github.com/orgs/cncf/projects/14/views/1). Baggywrinkle incorporates the requested clarity into the project information and updates the application issue with a comment. They then provide the `Completed info, project is Returning` comment and the TOC or staff will remove the previous labels, affix the `Returning` label, and place the issue in the **🏗 Upcoming** Column of the [Sandbox Application Board](https://github.com/orgs/cncf/projects/14/views/1) so it is included at the next session.

##### Isobars

The TOC reviews and discusses Isobars. The TOC determines that Isobars is a *very* early project; having existed less than 6 months, and doesn't appear to clearly decoupled from the sponsoring company's flagship product. The TOC affixes the `Postponed` label and comments on the issue the need for greater maturity, more distinguished separation of the project from the product, and an estimated timeframe to reopen the issue for re-review. The issue is then closed. The project maintainers work for several months to decouple the project from the product and during that time the project fills out its documentation, use cases, and begins growing its community. The maintainers then reopen the issue, edit the content of the issue to reflect the changes or comment with updates and add the comment `Revisit Ready`. The TOC or staff will add the `Returning` label and remove the `Postponed` label. Isobars is then placed on the **🏗 Upcoming** Column of the [Sandbox Application Board](https://github.com/orgs/cncf/projects/14/views/1) by the TOC or staff so it is included at the next session.

## Acceptance

Once projects are accepted into the Sandbox, CNCF staff will open a project onboarding issue for the project based on [project onboarding template](https://github.com/cncf/sandbox/blob/main/.github/ISSUE_TEMPLATE/project-onboarding.md) - this may take a few days to get created. If you would like to start looking at the items on that list now, then you will be ready when for when the issue is opened.

---

## Automation

This repository includes GitHub Actions workflows to automate the sandbox onboarding process:

- **Vote Monitor:** Automatically creates onboarding issues when applications pass voting
- **Contribution Agreement Signed Onboarding:** Creates onboarding issues when a sandbox application transitions from `contribution-agreement/unsigned` to `contribution-agreement/signed` (and will not create a duplicate onboarding issue if one already exists, open or closed)
- **Onboarding Progress Monitor:** Tracks onboarding progress and creates health issues in the TOC repository

For detailed documentation, see [Workflows README](.github/workflows/README.md).

sandbox

파일 탐색기

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

sandbox

파일 탐색기

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README