From 3ae43d2c4fdf3ec1fa5e2116e942f5de09a30bc3 Mon Sep 17 00:00:00 2001 From: David Sterz Date: Fri, 27 Mar 2026 13:31:19 +0100 Subject: [PATCH] docs: add governance and code of conduct requirements to maturity stages I propose we restore this requirement, as it serves as an uncontroversial and established open-source baseline. More importantly, this directly supports our core NeoNephos goal that "Neutral governance is central". Our foundation explicitly states that projects should be "governed by the community that builds and maintains them, not by individual companies". By mandating a GOVERNANCE.md and a Code of Conduct, we can ensure a meritocratic, welcoming environment that actively enforces this community-driven model. Signed-off-by: David Sterz --- lifecycle-policy/project-lifecycle-policy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lifecycle-policy/project-lifecycle-policy.md b/lifecycle-policy/project-lifecycle-policy.md index a271772..995e996 100644 --- a/lifecycle-policy/project-lifecycle-policy.md +++ b/lifecycle-policy/project-lifecycle-policy.md @@ -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 GOVERNANCE.md file that explicitly defines the project's decision-making and committer processes ##### Approval Process @@ -158,7 +158,7 @@ Graduated Stage projects are expected to participate actively in TAC proceedings ##### Acceptance Criteria -The TAC has not yet defined requirements for the Graduated Stage. +* The project must have adopted a Code of Conduct in a form acceptable to the NeoNephos Foundation, and maintain publicly accessible documentation of its release and governance processes ##### Approval Process