Skip to content

Add SCS-0005-v2 project governance standard - #1029

Merged
fkr merged 6 commits into
mainfrom
scs-0005-v2-project-governance
Dec 7, 2025
Merged

Add SCS-0005-v2 project governance standard#1029
fkr merged 6 commits into
mainfrom
scs-0005-v2-project-governance

Conversation

@berendt

@berendt berendt commented Dec 1, 2025

Copy link
Copy Markdown
Contributor

Add version 2 of the project governance standard. Compared to v1, this version adds the "Conflict of Interest and Organizational Diversity" section which ensures:

  • No more than one board seat may be held by individuals from the same organization
  • Rules for handling multiple top-ranked candidates from the same organization in elections
  • Process for resolving conflicts when board members change their organizational affiliation during their term

@berendt
berendt force-pushed the scs-0005-v2-project-governance branch 3 times, most recently from d4c6a0a to dee2faf Compare December 1, 2025 15:26
@fkr

fkr commented Dec 1, 2025

Copy link
Copy Markdown
Member

@berendt Imho this makes sense. Can we merge this effort with #1030 ?

Comment thread Standards/scs-0005-v2-project-governance.md
Comment thread Standards/scs-0005-v2-project-governance.md Outdated
@berendt

berendt commented Dec 1, 2025

Copy link
Copy Markdown
Contributor Author

@berendt Imho this makes sense. Can we merge this effort with #1030 ?

Yes, that was also Jan's suggestion. I just wasn't sure how best to work on it. I'm still working on your comments. If the content here is okay, I would suggest we add #1030 here as a commit afterwards and close #1030?

@berendt
berendt force-pushed the scs-0005-v2-project-governance branch 4 times, most recently from befe6b7 to 426a435 Compare December 1, 2025 16:36
@jklare
jklare force-pushed the scs-0005-v2-project-governance branch from 426a435 to 1ec5ecc Compare December 2, 2025 08:01
Comment thread Standards/scs-0005-v2-project-governance.md Outdated
Comment thread Standards/scs-0005-v2-project-governance.md Outdated
@mbuechse

mbuechse commented Dec 2, 2025

Copy link
Copy Markdown
Contributor

I noticed two points:

  • If a change of affiliation happens and the affected members can not agree on who is to stay and who is to go, it seems like a major crisis to me, and I'm not sure if the board still has the necessary trust to proceed;
  • According to the text, if one spot is vacated and cannot be filled, that seems fine, but if it happens a second time, an extraordinary election is triggered. I think it should depend more on the size of the board, because it can be fewer people to begin with, depending on the number of nominees.

@berendt
berendt requested a review from garloff December 2, 2025 11:12
@berendt

berendt commented Dec 2, 2025

Copy link
Copy Markdown
Contributor Author

@fkr @garloff Any further change requests from you? I would like to put everything that still needs to be adjusted into a commit.

@fkr

fkr commented Dec 2, 2025

Copy link
Copy Markdown
Member

@fkr @garloff Any further change requests from you? I would like to put everything that still needs to be adjusted into a commit.

@berendt: @mbuechse raised couple points in his comment.

@berendt

berendt commented Dec 2, 2025

Copy link
Copy Markdown
Contributor Author

@fkr @garloff Any further change requests from you? I would like to put everything that still needs to be adjusted into a commit.

@berendt: @mbuechse raised couple points in his comment.

Yes. Do you have anything else? I would like to make one commit with all the changes at once.

@berendt

berendt commented Dec 3, 2025

Copy link
Copy Markdown
Contributor Author

I noticed two points:

  • If a change of affiliation happens and the affected members can not agree on who is to stay and who is to go, it seems like a major crisis to me, and I'm not sure if the board still has the necessary trust to proceed;
  • According to the text, if one spot is vacated and cannot be filled, that seems fine, but if it happens a second time, an extraordinary election is triggered. I think it should depend more on the size of the board, because it can be fewer people to begin with, depending on the number of nominees.

I tried to incorporate some of the feedback in the last commit.

@berendt
berendt requested review from jklare and mbuechse December 3, 2025 16:19

@mbuechse mbuechse left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks Christian, I like the changes. They address my original concerns. I approve this, but my confidence here is rather low, so I hope others will approve as well.

@fkr
fkr force-pushed the scs-0005-v2-project-governance branch from f976450 to 2bd0103 Compare December 3, 2025 20:47

@jklare jklare left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

berendt and others added 6 commits December 7, 2025 13:32
Signed-off-by: Christian Berendt <berendt@osism.tech>
Add version 2 of the project governance standard. Compared to v1, this version adds the
"Conflict of Interest and Organizational Diversity" section which ensures:

- No more than one board seat may be held by individuals from the same organization
- Rules for handling multiple top-ranked candidates from the same organization in elections
- Process for resolving conflicts when board members change their organizational
  affiliation during their term

Co-authored-by: Kurt Garloff <kurt@garloff.de>
Signed-off-by: Christian Berendt <berendt@osism.tech>
* extend description for v2
* add version history to summarize changes between versions

Signed-off-by: Jan Klare <klare@osism.tech>
Clarify resignation reasons as non-exhaustive list and improve readability
of the announcement section.

Co-authored-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Christian Berendt <berendt@osism.tech>
- Use objective criteria (election vote count) instead of board vote
  for affiliation conflict resolution to avoid trust issues
- Replace fixed "second vacancy" rule with minimum quorum of 3 elected
  members to account for varying board sizes
- Minor language improvements (inclusive pronouns, grammar)

Signed-off-by: Christian Berendt <berendt@osism.tech>
@fkr
fkr force-pushed the scs-0005-v2-project-governance branch from 2bd0103 to 1721d5d Compare December 7, 2025 12:32
@fkr
fkr requested review from jschoone and matofeder December 7, 2025 12:32
@fkr
fkr merged commit 8366912 into main Dec 7, 2025
9 of 10 checks passed
@fkr
fkr deleted the scs-0005-v2-project-governance branch December 7, 2025 16:08
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.

6 participants