Skip to content

docs: reinstate baseline adopter counts for growth and graduated stages#2

Open
dsterz wants to merge 1 commit intoneonephos:mainfrom
dsterz:pr-adopter-counts
Open

docs: reinstate baseline adopter counts for growth and graduated stages#2
dsterz wants to merge 1 commit intoneonephos:mainfrom
dsterz:pr-adopter-counts

Conversation

@dsterz
Copy link
Copy Markdown

@dsterz dsterz commented Mar 27, 2026

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.

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>
@dsterz dsterz requested a review from a team March 27, 2026 13:42
##### 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
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants