You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The TOC, End User TAB, and community members have been discussing the lack of clarity in understanding what each of the maturity levels of our Matriculation process mean both for our projects, contributors, and adopters of these projects. While these levels typically align with stages of the SDLC at a very high level, not all projects reach maturity in the same fashion for all adopters and many adopters do not understand the level of diligence applied for a given level resulting in confusion, increased queries for understanding the project's maturity and stability, as well as other elements that may delay or misconstrue a project's true state.
This issue is to capture the action from yesterday's TOC call (#1491) I had mentioned and to provide the community an opportunity to assist in completing this.
Some resources from past presentations and discussions the maturity levels:
TOC keynotes at Kubecons
Notes from Take it on presentation on Chop Wood Carry Water
These levels provide other projects and potential adopters with a basic understand of how mature the project is.
Sandbox: experiments or other very early projects that can add value and build the ingredients of a successful incubation level project
Early but not too early, experimental but with potential impact and value in the ecosystem. These projects are getting underway and may experience a lot of change, such as frequency in release, governance, breaking changes, new APIs, complete redesigns, etc. These projects are reviewed by our community and TOC members to understand how they fit in cloud native, if they make sense, will they succeed or are they worth the gamble.
Incubation: projects transitioning from innovation to early adoption, confident in the core functionality and capability while building maturity and stability as the foundation for a resilient and responsive graduated project
These projects have not quite crossed the chasm, but are standing on the edge of it looking for how to cross. They’ve begun to slow in the amount of change they experience, and are becoming more stable. This is also the first stage where they’re adoption is evaluated.
Graduation: projects that continually demonstrate highly mature, evolved practices, reaching widespread adoption for their market area while providing a high degree of confidence in the guarantees of the project’s stability, performance, security, and engagement
These projects crossed the chasm. They are fairly robust and mature, what we would say as Production Ready. When Incubating projects are ready to graduate, they get a second adoption evaluation.
sandbox.cncf.io provides some information on sandbox level
The TOC, End User TAB, and community members have been discussing the lack of clarity in understanding what each of the maturity levels of our Matriculation process mean both for our projects, contributors, and adopters of these projects. While these levels typically align with stages of the SDLC at a very high level, not all projects reach maturity in the same fashion for all adopters and many adopters do not understand the level of diligence applied for a given level resulting in confusion, increased queries for understanding the project's maturity and stability, as well as other elements that may delay or misconstrue a project's true state.
This issue is to capture the action from yesterday's TOC call (#1491) I had mentioned and to provide the community an opportunity to assist in completing this.
Some resources from past presentations and discussions the maturity levels:
please add others for reference to who ever takes up this work!
The text was updated successfully, but these errors were encountered: