Skip to content

docs: mandate public adopters list for growth stage projects #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dsterz wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −1
Open

docs: mandate public adopters list for growth stage projects #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion lifecycle-policy/project-lifecycle-policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,7 +127,7 @@ Projects in the Growth stage are generally expected to move out of the Growth st

##### Acceptance Criteria

The TAC has not yet defined requirements for the Growth Stage.
* The project must maintain a public list of project adopters for at least the primary repository (e.g., via an ADOPTERS.md file or prominently displayed logos on the project website).
Copy link
Copy Markdown
Member

@jakobmoellerdev jakobmoellerdev Mar 27, 2026

Choose a reason for hiding this comment

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

The "primary" repository is undefined. I believe since we anyhow request a web presence (https://github.com/neonephos/guidelines-development/pull/5/changes#diff-d581ac8f08d67c132fa72c8c07f2b40c58ad6d723a299c43784623b3a08b9256R57) we could make them force adoption there?

On top of this I believe we need to define very clearly what adoption means, and at which point a project counts as adopted (I believe you have something correlated in a separate pr here #4)

Copy link
Copy Markdown
Contributor

@fmui fmui Apr 10, 2026

Choose a reason for hiding this comment

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

IMO, this should be a SHOULD requirement for all projects. We can define the specifics in the project guidelines to be more flexible. The policy may elevate it to a MUST for projects in the Growth and Graduated stages.


##### Approval Process

Expand Down