docs: add governance and code of conduct requirements to maturity stages#3
docs: add governance and code of conduct requirements to maturity stages#3dsterz wants to merge 1 commit intoneonephos:mainfrom
Conversation
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 <opensource@davidsterz.de>
| ##### 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 |
There was a problem hiding this comment.
The project must maintain a public GOVERNANCE.md file that explicitly defines the project's decision-making and committer processes
Strictly speaking, the Project Charter of each NeoNephos project defines the project's decision making and committer processes. Imho, a more appropriate wording would be something like:
The project must maintain a public GOVERNANCE.md file that provides references to the project's decision-making and committer processes and lists the TSC members.
There was a problem hiding this comment.
I'd recommend just linking to the OpenSSF best practices badge requirement ( https://www.bestpractices.dev/en/criteria?details=true&rationale=true#1.governance ), so that you are more tightly aligned to OSS best practices.
| ##### 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 |
There was a problem hiding this comment.
NeoNephos has a reference code of conduct. Maybe change to:
If the project wants to adopt its own Code of Conduct, it must be in a form acceptable to the NeoNephos Foundation.
There was a problem hiding this comment.
I would like to avoid custom code of conducts. Is there really a requirement for this across projects already?
There was a problem hiding this comment.
Yes - the default CoC in the project charter is https://linuxfoundation.eu/policies/code-of-conduct. I would agree that projects without a CoC already stick with that, but if a project coming in has a CoC it could be LF Europe approved ( see 4b in the Technical Charter for any of the NeoNephos projects )
There was a problem hiding this comment.
Hmmm.... To me this reads like it is not required and all Projects could adopt the NeoNephos CoC.
4 participants
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.