docs: define multi-organisational maintainer minimums and vendor neutrality cap#4
Open
dsterz wants to merge 1 commit intoneonephos:mainfrom
Open
docs: define multi-organisational maintainer minimums and vendor neutrality cap#4dsterz wants to merge 1 commit intoneonephos:mainfrom
dsterz wants to merge 1 commit intoneonephos:mainfrom
Conversation
…rality cap To ensure the long-term sustainability of our projects, we need to mitigate the "bus factor"—the risk that a project might stall if a single leader or company withdraws. I propose we restore the requirement for cross-organisational collaboration, which aligns nicely with open-source best practices. This requirement is crucial for fulfilling NeoNephos goal of prioritizing "independence from proprietary components and from single vendor owned open source projects". Mandating a diverse, multi-organisational maintainer base guarantees that "contribution and proven technical leadership matter more than company affiliation," helping us prevent vendor lock-in and uphold European digital sovereignty. Signed-off-by: David Sterz <opensource@davidsterz.de>
Member
jakobmoellerdev
left a comment
jakobmoellerdev
left a comment
There was a problem hiding this comment.
love this suggestion!
| ##### Acceptance Criteria | ||
|
|
||
| The TAC has not yet defined requirements for the Growth Stage. | ||
| * The project must demonstrate a substantial ongoing flow of commits and merged contributions, driven by a minimum of three active maintainers from at least two different organisations |
Member
There was a problem hiding this comment.
substantial is relative and should be put into absolute terms
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
To ensure the long-term sustainability of our projects, we need to mitigate the "bus factor"—the risk that a project might stall if a single leader or company withdraws.
I propose we restore the requirement for cross-organisational collaboration, which aligns nicely with open-source best practices.
This requirement is crucial for fulfilling NeoNephos goal of prioritizing "independence from proprietary components and from single vendor owned open source projects".
Mandating a diverse, multi-organisational maintainer base guarantees that "contribution and proven technical leadership matter more than company affiliation," helping us prevent vendor lock-in and uphold European digital sovereignty.