docs: reinstate baseline adopter counts for growth and graduated stages#2
docs: reinstate baseline adopter counts for growth and graduated stages#2dsterz wants to merge 1 commit intoneonephos:mainfrom
Conversation
To provide a clear signal of stability to enterprise adopters, I recommend we reinstate the baseline adopter metrics we previously agreed upon. This directly serves the NeoNephos mission, which states that our projects "are intended for serious use in production and mission critical environments". By defining strict adopter counts, the TAC can ensure that Graduated projects have proven their real-world reliability, fulfilling our promise to provide high-quality, production-ready building blocks for cloud and edge stacks. Signed-off-by: David Sterz <opensource@davidsterz.de>
| ##### Acceptance Criteria | ||
|
|
||
| The TAC has not yet defined requirements for the Growth Stage. | ||
| * The project must document that it is being used successfully in production by at least two independent organisations, which, in the TAC’s judgement, are of adequate quality and scope |
There was a problem hiding this comment.
nit: production can be defined extremely differently based on context and size of deployment of a tool. Thus I would heed caution here and we should maybe make it more defined
| ##### Acceptance Criteria | ||
|
|
||
| The TAC has not yet defined requirements for the Growth Stage. | ||
| * The project must document that it is being used successfully in production by at least two independent organisations, which, in the TAC’s judgement, are of adequate quality and scope |
There was a problem hiding this comment.
What about this? It adds a bit more precision.
The project must demonstrate to the TAC that it is being used successfully in production, or adopted as a dependency in a released product or open-source project, by at least two independent organisations or projects. The TAC will assess whether the evidence presented is adequate in quality and scope, taking into account the nature of the project. Where specific usage details cannot be disclosed, a brief written attestation from each such organisation or project confirming its use will suffice.
| ##### Acceptance Criteria | ||
|
|
||
| The TAC has not yet defined requirements for the Graduated Stage. | ||
| * The project must verify production use by at least 5 independent organisations, subject to formal TAC due diligence |
There was a problem hiding this comment.
See comment above - just with five usages.
3 participants
To provide a clear signal of stability to enterprise adopters, I recommend we reinstate the baseline adopter metrics we previously agreed upon.
This directly serves the NeoNephos mission, which states that our projects "are intended for serious use in production and mission critical environments".
By defining strict adopter counts, the TAC can ensure that Graduated projects have proven their real-world reliability, fulfilling our promise to provide high-quality, production-ready building blocks for cloud and edge stacks.