v1.6, previously "project proposal process v1.5"
This document provides high level information for projects to understand the project lifecycle, criteria, and the moving levels process for to demonstrate their completion of a defined criteria set.
CNCF Projects experience a project lifecycle that conveys their completion of a defined set of criteria. These criteria are cumulative, building upon the previous maturity level criteria to enable cloud native projects to become highly maturity, secure, production ready projects for adopters.
The TOC defines 4 stages of the project lifecycle:
- Sandbox - experimental or innovative projects that are early in their life
- Incubation - growing maturity projects that are on the precipice of "crossing the chasm"
- Graduated - highly mature, robust projects whose adopters have demonstrated their production-readiness by their deployment to production environments
- Archived - inactive or low activity projects that are no longer supported by the TOC or are not recommended for use due to a variety of factors (project specific)
Projects may enter the CNCF either by applying as a sandbox project or applying directly for incubation. As project navigates their maturity journey, their completion of a given level's criteria is evaluated by the TOC in a process called Due Diligence to ensure the project's implementation of the criteria meets the desired outcome, intent, and expectations set forth by the TOC.
Evaluting projects against the criteria does take some time and the TOC has recently modified the Due Diligence process to reduce duplication of work, streamline handoffs, and provide better transparency to the project and its adopters about its conformance and implementation of the criteria.
The TOC, with support from the Technical Advisory Groups, have a wide variety of resources available to assist projects. Current and aspiring maintainers of cloud native projects can find a lot of information and templates on contribute.cncf.io/maintainers. The TOC also maintains project Guide Posts - a collection of guiding points that have assisted cloud native projects as they grow and mature in the ecosystem. These are not requirements for moving levels, those may be found in the respective application issue templates (Incubation, Graduation). The Guide Posts are a resources for projects to leverage that is beneficial in meeting or exceeding the criteria defined.
Note: The TOC has changed the sandbox application process to a more transparent and streamlined workflow within the 📦 Sandbox Applications repository 📦.
Projects apply for sandbox through the Sandbox Repo's Issue Form. More information on this process is found on the main Sandbox repo page. All exceptions and "declined" or "postponed" outcomes are handled by the TOC. Projects may be encouraged to re-apply after addressing areas called out in the application comments on the corresponding issue. Please refer to the instructions in the Sandbox repo README for more details on re-application.
While the details of the process are described in detail further for Incubating and Graduting proposals, the high level steps that occur when a project moves levels are as follows:
Applications to move levels are done by submitting an incubation or graduation application issue on the TOC repo
Who: Project
- Projects seeking to move to incubation should submit the Incubation Application issue and detail how they meet the incubation level criteria, existing incubating projects seeking to move to graduation should submit the Graduation Application issue and detail how they meet the graduation level criteria.
- As prior applications are closed, the TOC selects the next project from the backlog.
A TOC sponsor(s) is assigned and the project is moved to 'Due Diligence' or 'Active Review' on the project boards depending on which level is proposed.
Who: TOC
Who: TOC Sponsor(s) and Project
- The TOC will schedule time with the project to set expectations and layout out the process. The TOC will use the meeting notes document to capture blockers, recommendations, and other findings as they review the issue and the project's respositories, channels, release process, metrics, governance, and other sources of information that support the project's completion of the criteria. The TOC member will refer back to these notes to support their forumlation of the Due Diligence PR. The project is asked to identify 5-7 adopters for interviews.
- If the TOC sponsor(s) finds that the project is not yet ready to move levels, they will re-engage with the project to discuss next steps, detail specific blockers that prevent the project from moving, and any actions that need to be completed but are non-blocking. The Application issue is updated with this summary once the project is discussed.
Who: TOC Sponsor(s)
- Once all recommendations, blockers, and other findings are resolved, the TOC member will begin crafting the Due Diligence PR that provides their evaluation of the project's completion of the criteria, any compensating mechanisms in place, or other notables that may influnce the TOC's decision to move the project to the next level.
Who: TOC Sponsor(s) and Adopters
- Depending on the freshness of prior interviews the TOC may choose to not conduct further interviews or conduct others to ensure coverage by a variety of adopters to explore all facets of the project. The project is updated on the project board.
- The TOC will reach out to adopters to inform them of how interviews are conducted and to address any anonomity or other concerns they may have. The TOC will ensure adopters have final approval of any published summaries of the interviews that are included in the due diligence PR.
- If multiple TOC members are sponsoring, they will conduct their own individual reviews and then coordinate with each other on overall observations, findings, and next steps.
Who: TOC Sponsor(s) and TOC
- Assuming all outstanding issues are resolved, the TOC opens an internal comment period, about 1 week, for other TOC members to perform an independent review and verify all areas of the project have been evaluated.
- The TOC sponsor may choose to share a WIP PR with the TOC for review and comment internally. If no further issues are identified, the TOC sponsor(s) will finalize and submit the PR to open the public comment period. A message is announced on the toc mailing list.
The project is updated on the project board to 'Public Comment' and the public comment period is open for two weeks.
Who: TOC Sponsor(s)
Who: Initiate - CNCF Support Staff for the TOC, Voting - TOC and community members
- Provided no additional items are identified during the public comment period, the TOC opens voting on the PR using gitvote shortly thereafter (usually about 2 days subject to availability). The project is updated on the project board to 'In Voting'.
- TOC members and the community may cast votes and show support by using emoji voting on the gitvote initiating comment.
Who: CNCF Support Staff for the TOC
- If the vote passes (2/3 supermajority vote of the TOC), the results are emailed and the project is placed in the 'Done' state on the project board.
- An announcement is made conveying the project name and its new level status.
Projects can find the criteria for Incubation by reviewing the Incubation application template.
Projects can find the criteria for Graduation by reviewing the Graduation application template.
The TOC makes no guarantees on if or when a project will join the CNCF or move levels. Projects apply for moving levels when they feel they are ready. However, what is ready for one project is not the same for another nor is each project’s adoption and maturity measurable against one another. For some projects it may be a long journey with the TOC to bring them to maturity for the kind of project they are and for others it may be shorter - it all depends on the individual project, their readiness, and the availability of the individuals responsible for various tasks in moving levels.
When projects apply for moving levels, they do not move levels on a first-in first-out (FIFO) basis. Some projects join the Foundation when they are already far along in their journey and others join very early. They will approach maturity guide posts differently - at different times and in ways similar or different from others. We do our best to support projects moving levels, in some cases engaging with them frequently to ensure they are making progress on our initial findings but leaving the application open. In other cases, we review the project and finding nothing disparaging, only needing to refresh the content of the previous due diligence, evaluate against the next level of criteria, and move it forward.
For sandbox proposals, applications are reviewed in the order the TOC chooses, most commonly returning applications first and then from oldest application to newest every two months. The TOC may not have time to get through every application each meeting as different project applications carry varying considerations and discussion topics to ensure enough information is discovered and explored to make an informed decision. The up to date list can be found here and will be carried over from meeting to meeting if not every project is reviewed.
For moving levels to incubation or graduation, projects should plan on at least 3 months once a TOC member steps forward to sponsor the project's application (assigns themselves to the issue).
Due to the increased community demands around KubeCon + CloudNativeCon (KCCN), the scheduling and production of content, and reduced availability of individuals involved in moving levels, the TOC leverages a freeze for projects in process for moving levels. Even if a project is approved to move levels 3 weeks before this event, projects should not expect to receive benefits beyond those afforded for the level they were previously at. For example, if a sandbox project is approved to move to incubation 3 weeks prior to the event, the project and the event staff will not have enough time to record, edit, and produce an incubating project update to have it included within the keynote stage reel.
For KubeCon + CloudNativeCon's (KCCN) Europe and North America — the following freeze is applied:
Within 4 weeks of the event
- TOC members will not take on new sponsorship of applications for moving levels
- Many activities occur before, during, and after KCCN. Postponing new sponsorship until after KCCN reduces the likelihood that kicking off the process is overcome by such activities.
- Public Comment will not open
- We want to ensure community members, adopters, and other stakeholders have time to participate in the public comment of projects, the 2 weeks leading up to the event are typically very busy for many individuals involved in the moving levels process.
- Voting for projects will not open
- Voting is an opportunity for community members to show support for projects, it is also the time when the TOC determines if the due diligence and state of the project support its promotion to the next level. As such it is essential for TOC members to have time to not only cast votes, but to consider any comments raised during the public comment period. The TOC is just as busy as any other attendee or speaker for KCCN, it is easy to miss the timeframes for voting and we want to ensure projects receive the attention in a vote they deserve.
- Open voting is paused
- While community members may continue to show support for projects, the TOC will officially pause our voting.
- No project announcements
- Even if a project has passed a vote, if they have not announced and officially moved levels, they will not be included as an incubating or graduated project.
2nd week following the event
- Voting for projects who completed public comment may open and commence.
- The week immediately following KCCN is commonly reserved as a recovery and digest period for attendees, event staff, community members, and TOC.
The above freeze only applies to KCCN NA and EU. Other events will be subject to the TOC members' availability who are expected to regularly check in with the projects. TOC members may choose to continue working with projects on due diligence within the weeks before and after KCCN subject to their and others' availability. Projects should take all of this into account when planning completion of their due diligence. We ask projects to be understanding and considerate of our availability constraints around KCCN and remind everyone that the TOC is not a full-time body, we have primary work commitments in addition to our involvement on the TOC and any projects, TAGs, or community groups we are involved in.
As the CNCF chooses to create new standalone occurrences of KCCN, this freeze should be reviewed to ensure ample time is available to conduct activities to support project moving levels. It may include restricting to just two freezes a year, or a complete re-evaluation of the freeze in light of whatever changes have transpired.
Q: Why doesn't the TOC get through the sandbox list every meeting? A: There are currently many projects that want to be a part of the CNCF and it is the TOC's job to carefully consider if they are the right fit for the foundation. This deliberation takes time and there are only so many applications that the TOC can get through each meeting. If anything, a delay from one meeting to the next is a benefit for the project because it allows more time to build community support.
Q: Exactly how long will it take my project to move levels once my application is in? A: Just like in open source, it will get done when the work is done. This can range from 5 months to 15 months please coordinate with your TOC sponsor to keep everything on track.
Q: Can my project still apply to move levels within 4 weeks of KubeCon? A: Yes, though getting a TOC sponsor, conducting any due diligence, and any other steps of the process will be delayed until after KubeCon.
Q: Why can't public comment periods or votes launch within 4 weeks of a KubeCon? A: Undergoing due diligence is a non-insignificant amount of work. Conducting adopter interviews takes time and scheduling becomes increasingly difficult the closer to each KCCN we get. Being able to successfully complete due diligence to launch the public part of the process becomes very difficult as many community members have additional responsibilities related to the conference. By removing KCCN as a goal post for brand new requests to move levels, we hope to not burn out adopters, TOC, maintainers, and other community members.
Q: I meet the criteria, why am I not graduating? A: There could be a number of reasons why a project is not yet ready to graduate but appears to meet the criteria. The TOC has increased the clarity and desired outcomes the criteria should achieve for projects but require evaluation on a case-by-case basis for each project to understand the implications of their implementation. The TOC has final discretion but endevours to be transparent and enable projects to successfully and sustatinably achieve Graduation status while balancing the needs and expectations of adopters and CNCF members.
Q: How can I ensure my project is on the right path to the next level? A: Projects are strongly encouraged to meet with their TAG to receive feedback on changes, improvements, recommendations to assist the project to the next maturity level. Some of these may be domain specific recommendations to ensure a more robust project, or they may be more high level items and encompass engineering principles that need codified within the project. TOC members sponsoring a project will reach out to the project's TAG to understand more about the project and ensure they incorporate the TAG's recommendations, notes, and observations within the Due Diligence PR.