Skip to content

Add governance document in the repository - #3710

Draft
ekouts wants to merge 3 commits into
reframe-hpc:developfrom
ekouts:governance
Draft

Add governance document in the repository#3710
ekouts wants to merge 3 commits into
reframe-hpc:developfrom
ekouts:governance

Conversation

@ekouts

@ekouts ekouts commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@ekouts
ekouts requested review from gppezzi, victorusu and vkarak August 20, 2026 15:03
@ekouts ekouts self-assigned this Aug 20, 2026
@codecov

codecov Bot commented Aug 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.93%. Comparing base (780c2c4) to head (b203ae0).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #3710      +/-   ##
===========================================
- Coverage    91.97%   91.93%   -0.04%     
===========================================
  Files           62       62              
  Lines        13788    13788              
===========================================
- Hits         12681    12676       -5     
- Misses        1107     1112       +5     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment thread GOVERNANCE.md Outdated
Comment thread GOVERNANCE.md Outdated
ekouts and others added 2 commits August 26, 2026 16:05
Co-authored-by: Guilherme <gppezzi@users.noreply.github.com>
Co-authored-by: Guilherme <gppezzi@users.noreply.github.com>
Comment thread GOVERNANCE.md
Most decisions happen in pull requests.
A pull request needs the approval of at least one maintainer other than the author, passing CI and documentation for any user-facing change.

Bigger changes (new major features, architectural changes, changes to the public API or the configuration syntax, deprecations, release planning) are discussed in a GitHub issue first, in the development meetings or on Slack.

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.

Suggested change
Bigger changes (new major features, architectural changes, changes to the public API or the configuration syntax, deprecations, release planning) are discussed in a GitHub issue first, in the development meetings or on Slack.
Bigger changes (such as new major features, architectural changes, changes to the public API or the configuration syntax, deprecations, release planning) are discussed in a GitHub issue first, in the development meetings or on Slack.

Comment thread GOVERNANCE.md
We decide by consensus.
If we cannot agree, the leadership team votes and a simple majority wins.

Changes to this document, to the license, or removing a maintainer need a 2/3 vote of the leadership team.

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.

Suggested change
Changes to this document, to the license, or removing a maintainer need a 2/3 vote of the leadership team.
Changes to this document needs a 2/3 vote of the leadership team.

Comment thread GOVERNANCE.md
- Eirini Koutsaniti ([@ekouts](https://github.com/ekouts)), CSCS
- Guilherme Peretti-Pezzi ([@gppezzi](https://github.com/gppezzi)), CSCS

Members are added by a majority vote of the leadership team and removed by a 2/3 vote.

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.

Suggested change
Members are added by a majority vote of the leadership team and removed by a 2/3 vote.
Members are added by an absolute majority vote of the leadership team and removed by a 2/3 absolute majority.
The member to be removed is notified about the reasons and given the opportunity to respond.

Comment thread GOVERNANCE.md

Members are added by a majority vote of the leadership team and removed by a 2/3 vote.

A "majority" means more than half of the current leadership team members, regardless of how many participate in the vote. A 2/3 vote is calculated the same way — two thirds of the current team, not just those who vote.

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.

Suggested change
A "majority" means more than half of the current leadership team members, regardless of how many participate in the vote. A 2/3 vote is calculated the same way — two thirds of the current team, not just those who vote.
An "absolute majority" means more than half of the current leadership team members, regardless of how many participate in the vote.

Comment thread GOVERNANCE.md
Comment on lines +32 to +33
A member who has been inactive for more than 6 months may be removed by a 2/3 vote. Before the vote, the member is notified and given an opportunity to respond.
A member who has been inactive for more than 6 months can be removed by vote.

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.

Suggested change
A member who has been inactive for more than 6 months may be removed by a 2/3 vote. Before the vote, the member is notified and given an opportunity to respond.
A member who has been inactive for more than 6 months can be removed by vote.

Comment thread GOVERNANCE.md
The current list is in [MAINTAINERS.md](MAINTAINERS.md).

Any maintainer can propose a contributor as a new maintainer.
The leadership team decides.

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.

Suggested change
The leadership team decides.
The leadership team decides on an absolute majority basis.

Comment thread GOVERNANCE.md
We look for a track record of good contributions, a good understanding of the code base and constructive participation in reviews and discussions.

Maintainers can step down at any time.
A maintainer who has been inactive for more than a year may be removed by the leadership team. Before a vote, the maintainer is notified and given an opportunity to respond. The leadership team decides by majority vote.

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.

Suggested change
A maintainer who has been inactive for more than a year may be removed by the leadership team. Before a vote, the maintainer is notified and given an opportunity to respond. The leadership team decides by majority vote.
Maintainers can also be removed by the leadership team with an absolute majority vote.
The maintainer to be removed is notified about the reasons and given the opportunity to respond.

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.

3 participants