EESSI Governance #456

casparvl · 2025-05-07T09:43:31Z

To be agreed on by the Steering Committee. I think the most practical is if we keep iterating / wait until every one of us has given an approving review

…olicy

… May 2025

…we can do that in follow up PRs

bedroge · 2025-05-07T11:35:07Z

@casparvl I've fixed some typos in casparvl#1 and casparvl#2.

fix typo

fix some more typos

casparvl · 2025-05-07T14:11:22Z

Oh yeah, thanks, merged!

ocaisa · 2025-06-18T19:40:09Z

docs/governance/governance.md

+
+### 5.2 Removing Team Members
+<!-- Describe under what conditions someone may be removed (e.g., inactivity, conduct). -->
+Teams decide themselves decide the procedure to remove new Team members. As for the procedure of adding Team Members, the procedure to remove Team Members should reflect the sensitivity of the position.


Suggested change

Teams decide themselves decide the procedure to remove new Team members. As for the procedure of adding Team Members, the procedure to remove Team Members should reflect the sensitivity of the position.

Teams themselves decide the procedure to remove Team members. As for the procedure of adding Team Members, the procedure to remove Team Members should reflect the sensitivity of the position.

ocaisa · 2025-06-18T19:48:32Z

docs/governance/governance.md

+TODO: This project follows the [Contributor Covenant](https://www.contributor-covenant.org/) Code of Conduct.
+
+## 8. Contribution Agreement
+TODO: Should refer to some Contribution Agreement. Is contributing only possible after signing this agremeent? If so, that should be stated here


Linux projects have a standard approach here which doesn't involve signing a CA

Suggested change

TODO: Should refer to some Contribution Agreement. Is contributing only possible after signing this agremeent? If so, that should be stated here

TODO: Should refer to some Contribution Agreement. Is contributing only possible after signing this agreement? If so, that should be stated here

Hm, that sounds attractive, since it means we don't need a lawyer to draw up something for us :)

carefully hand-crafted ... aehm copiloted ... policies

…SSI softwares stack versions and individual software. Remove some duplicate statements

casparvl · 2025-06-19T09:30:39Z

docs/governance/policies.md

+
+- EESSI is committed to providing a complete SBOM for all deployed software.
+- The SBOM should include versioning, licensing, and dependency information.
+- Preferred formats include SPDX or CycloneDX.


I'm not sure if we can already meet the latter two points. If not, does it make sense to include them? I don't think so. Or at least we should make clear it's not currently the case, but is a long term goal.

docs/governance/code_of_conduct.md

boegel · 2025-06-19T10:21:07Z

mkdocs.yml

+    - Governance: governance/governance.md
+    - EESSI Policies: governance/policies.md
+    - Code of Conduct: governance/code_of_conduct.md
+    - Current Steering Committee: governance/steering_committee.md


We should either set up an auto-redirect for eessi.io/docs/governance to the moved steering_comittee URL, or set up a simple index.md in /governance with bullets that points to the subpages.

tweaks to governance (sections 3-9), charter, policies

Co-authored-by: Kenneth Hoste <[email protected]>

… is meant to resolve

docs/governance/charter.md

Co-authored-by: Kenneth Hoste <[email protected]>

docs/governance/governance.md

Co-authored-by: Bob Dröge <[email protected]>

docs/governance/governance.md

bedroge · 2025-08-07T13:36:38Z

docs/governance/governance.md

+### 2.6 Ingestors
+Ingestors are those individuals that have permissions to ingest a tarball into the EESSI CernVM-FS repository, i.e. they are essentially responsible for step 3 as it is described in the [Builders](#builders) Section.
+
+Ingestors have merge permissions on the (private) `EESSI/staging` GitHub repository.
+
+Ingestors should check the contents of the tarball as it is reported in the pull requests in the `EESSI/staging` repository. This essentially provides a second check (next to that done by Deployers) on the contents of the tarball.


I was just making a github team for a new staging repo, and was wondering which name you used for this role. While using it, I started wondering if it shouldn't be ingesters. According to an AI friend:

Both ingester and ingestor are correct and commonly used, though "ingester" is the more widely accepted and preferred term, according to Wiktionary. Both words refer to something that ingests, whether it's a person, an animal, or a machine. While "ingestor" is also a valid word, "ingester" is more frequently encountered in contemporary usage, particularly in technical contexts

Suggested change

### 2.6 Ingestors

Ingestors are those individuals that have permissions to ingest a tarball into the EESSI CernVM-FS repository, i.e. they are essentially responsible for step 3 as it is described in the [Builders](#builders) Section.

Ingestors have merge permissions on the (private) `EESSI/staging` GitHub repository.

Ingestors should check the contents of the tarball as it is reported in the pull requests in the `EESSI/staging` repository. This essentially provides a second check (next to that done by Deployers) on the contents of the tarball.

### 2.6 Ingesters

Ingesters are those individuals that have permissions to ingest a tarball into the EESSI CernVM-FS repository, i.e. they are essentially responsible for step 3 as it is described in the [Builders](#builders) Section.

Ingesters have merge permissions on the (private) `EESSI/staging` GitHub repository.

Ingesters should check the contents of the tarball as it is reported in the pull requests in the `EESSI/staging` repository. This essentially provides a second check (next to that done by Deployers) on the contents of the tarball.

branfosj · 2025-08-20T13:29:29Z

docs/governance/governance.md

+- The Steering Committee ideally consists of an odd number of Members;
+- No more than 30% of the Members should be employed by commercial entities;
+- The number of Members working for the same company should be limited to 1;
+- The number of Members from the same country should be limited to 2;


Which of these does 'from' refer too?

place of birth

nationality

residence

place of work

I'm thinking the third is meant here.

No, country of affiliation (company/institution), I'd say. But should be clarified, indeed.

verdurin · 2025-08-20T13:35:33Z

docs/governance/charter.md

@@ -0,0 +1,49 @@
+<!-- 
+A project charter discusses _what it is and why it exists_, a governance discusses _how it operates_.


Oughtn't this to be just "governance"? I don't understand what "a governance" is.

verdurin · 2025-08-20T13:37:37Z

docs/governance/code_of_conduct.md

+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our


The definitions of "members", "contributors", and "leaders" need to be provided.
In particular, we have a statement in the preceding file that there are no members...

verdurin · 2025-08-20T13:39:29Z

docs/governance/governance.md

@@ -0,0 +1,238 @@
+<!-- 
+A project charter discusses _what it is and why it exists_, a governance discusses _how it operates_.


A "statement of governance principles" or similar?

verdurin · 2025-08-20T13:41:47Z

docs/governance/governance.md

+<!-- Optional section to state high-level principles like openness, meritocracy, consensus, etc. -->
+The value of EESSI grows exponentially with two things: the amount of systems that make EESSI available, and the amount of software that is available in EESSI. Thus, the first goal of this governance is to make sure everyone in the community feels sufficiently included so that they are willing to contribute to EESSI (rather than build their own solution).
+
+The second goal of this governance is to make clear how and by whom decisions in EESSI are taken. This is because trust in this process is important, both to infrastructure providers making the EESSI software stack is available on their systems, as well as by end-users of the software. Note that this concerns both large decisions, such as which architectures are supported in EESSI, as well as small decisions, such as making a specific software package available in EESSI.


Suggested change

The second goal of this governance is to make clear how and by whom decisions in EESSI are taken. This is because trust in this process is important, both to infrastructure providers making the EESSI software stack is available on their systems, as well as by end-users of the software. Note that this concerns both large decisions, such as which architectures are supported in EESSI, as well as small decisions, such as making a specific software package available in EESSI.

The second goal of this governance is to make clear how and by whom decisions in EESSI are taken. This is because trust in this process is important, both to infrastructure providers making the EESSI software stack available on their systems, as well as for end-users of the software. Note that this concerns both large decisions, such as which architectures are supported in EESSI, as well as small decisions, such as making a specific software package available in EESSI.

verdurin · 2025-08-20T13:42:32Z

docs/governance/governance.md

+
+### 2.1 Owners of the `EESSI` GitHub organization & repositories
+<!-- Define who contributors are and what they can do (e.g., file issues, submit PRs). -->
+The owners of the [EESSI GitHub organization](https://github.com/EESSI) & repositories are those individuals with `owner` rights on the EESSI GitHub organization or one of it's associated repositories.


Suggested change

The owners of the [EESSI GitHub organization](https://github.com/EESSI) & repositories are those individuals with `owner` rights on the EESSI GitHub organization or one of it's associated repositories.

The owners of the [EESSI GitHub organization](https://github.com/EESSI) & repositories are those individuals with `owner` rights on the EESSI GitHub organization or one of its associated repositories.

verdurin · 2025-08-20T13:48:41Z

docs/governance/governance.md

+Membership of the Steering Committee can terminate in three ways:
+
+- A Member can resign
+- A Member may be voted out. In this case, the vote needs to be unanimous between the other Members. This procedure is intended to provide a mechanism for addressing extraordinary circumstances where a members behavior or actions are deemed severely detrimental to the committee's function or reputation, and/or to the EESSI project.


Suggested change

- A Member may be voted out. In this case, the vote needs to be unanimous between the other Members. This procedure is intended to provide a mechanism for addressing extraordinary circumstances where a members behavior or actions are deemed severely detrimental to the committee's function or reputation, and/or to the EESSI project.

- A Member may be voted out. In this case, the vote needs to be unanimous between the other Members. This procedure is intended to provide a mechanism for addressing extraordinary circumstances where a member's behavior or actions are deemed severely detrimental to the committee's function or reputation, and/or to the EESSI project.

verdurin · 2025-08-20T13:49:35Z

docs/governance/governance.md

+- The number of Members from the same country should be limited to 2;
+- The composition of the Steering Committee should reflect the EESSI community;
+
+Note that if Members change jobs, or move to another country, some of the above criteria that were taken into account during selection may no longer be satisfied. It is up to the Steering Committee to decide if this is problematic, and if so, try to restore balance by requesting someone to resign.


Suggested change

Note that if Members change jobs, or move to another country, some of the above criteria that were taken into account during selection may no longer be satisfied. It is up to the Steering Committee to decide if this is problematic, and if so, try to restore balance by requesting someone to resign.

Note that if Members change jobs, or move to another country, some of the above criteria that were taken into account during selection may no longer be satisfied. It is up to the Steering Committee to decide if this is problematic, and if so, try to restore balance by requesting someone's resignation.

verdurin · 2025-08-20T13:53:14Z

docs/governance/policies.md

+
+## 4. Transparency and Traceability
+
+EESSI aims to be transparent regarding how software was build. A combination of the git history, EasyBuild logs, as well as the `easybuild` subdirectory within every installation (which provides the easyconfig and patch files, easyblock, and any hooks used at installation time) provide a detailed description of how software was configured and built.


Suggested change

EESSI aims to be transparent regarding how software was build. A combination of the git history, EasyBuild logs, as well as the `easybuild` subdirectory within every installation (which provides the easyconfig and patch files, easyblock, and any hooks used at installation time) provide a detailed description of how software was configured and built.

EESSI aims to be transparent regarding how software was built. A combination of the git history, EasyBuild logs, as well as the `easybuild` subdirectory within every installation (which provides the easyconfig and patch files, easyblock, and any hooks used at installation time) provide a detailed description of how software was configured and built.

verdurin · 2025-08-20T13:53:57Z

docs/governance/policies.md

+## 5. Platform Prioritization
+
+**HPC compatibility and performance are prioritized**,
+in cases where technical choices must be made between HPC, Cloud, or PC environments,


Maybe end-user or local rather than "PC"?

verdurin · 2025-08-20T13:54:19Z

docs/governance/policies.md

+
+# EESSI Team Policies
+
+There are currently no Team Policies yet.


Suggested change

There are currently no Team Policies yet.

There are no Team Policies yet.

boegel · 2025-08-20T14:12:35Z

docs/governance/governance.md

+
+Note that if Members change jobs, or move to another country, some of the above criteria that were taken into account during selection may no longer be satisfied. It is up to the Steering Committee to decide if this is problematic, and if so, try to restore balance by requesting someone to resign.
+
+All new Members will appoint an alternate that may represent them and vote on their behalf in case they are unavailable. If a Member resigns or is voted out from the Steering Committee, their alternate immediately loses any rights they had as an alternate.


Maybe we should make this optional, and even leave the door open for temporary alternate (for 1 meeting)?

Caspar van Leeuwen and others added 12 commits February 18, 2025 22:50

Initial work on governance structure

cd35a98

Add some more notes

f83bc59

Fix comment

79d5b58

Added remaining items

adce82e

Moved Governance to a subdir. Now separate charter, governance, and p…

4d91f0f

…olicy

Added some more suggestions

7a340ba

Add current steering committee

135ee3c

fix typo

5032192

fix some more typos

f526460

Update charter.md

91aa468

Update charter.md

393248e

Modified charter and governance after Steering Committee meeting of 6…

cc84b9f

… May 2025

casparvl changed the title ~~Governance~~ EESSI Governance May 7, 2025

Make policies.md page reflect that we're not defining policies yet - …

005d2b7

…we can do that in follow up PRs

casparvl added 3 commits May 7, 2025 16:08

Merge pull request #1 from bedroge/patch-1

4cddbb5

fix typo

Merge branch 'governance' into patch-2

573ed87

Merge pull request #2 from bedroge/patch-2

5a52291

fix some more typos

Caspar van Leeuwen and others added 2 commits June 18, 2025 16:37

Fix typos

63ca7cf

carefully hand-crafted ... aehm copiloted ... policies

e29464f

ocaisa reviewed Jun 18, 2025

View reviewed changes

casparvl and others added 2 commits June 19, 2025 10:17

Merge pull request #3 from trz42/policy_draft

ca4fd63

carefully hand-crafted ... aehm copiloted ... policies

Update policies to include deprecation. Make a distinction between EE…

383d455

…SSI softwares stack versions and individual software. Remove some duplicate statements

casparvl commented Jun 19, 2025

View reviewed changes

Add code of conduct

83b7e4b

casparvl commented Jun 19, 2025

View reviewed changes

docs/governance/code_of_conduct.md Show resolved Hide resolved

Add code of conduct to the website tree

90c26e7

boegel reviewed Jun 19, 2025

View reviewed changes

boegel and others added 8 commits August 4, 2025 11:29

small tweaks to policies

9e48b26

Merge pull request #4 from boegel/governance

cd1435f

tweaks to governance (sections 3-9), charter, policies

Fix typo

217369f

Changed references to sections into links

ea9647a

Changes based on @boegel's review

50f5678

Apply suggestions from code review

10d4c9d

Co-authored-by: Kenneth Hoste <[email protected]>

Fix grammar

9522c00

Clarify what the procudure of removing members through unanimous vote…

f182390

… is meant to resolve

bedroge reviewed Aug 4, 2025

View reviewed changes

docs/governance/charter.md Outdated Show resolved Hide resolved

Apply suggestions from code review

88e5bd4

Co-authored-by: Kenneth Hoste <[email protected]>

boegel reviewed Aug 4, 2025

View reviewed changes

docs/governance/governance.md Outdated Show resolved Hide resolved

casparvl commented Aug 4, 2025

View reviewed changes

docs/governance/governance.md Outdated Show resolved Hide resolved

Apply suggestions from code review

e920332

Co-authored-by: Bob Dröge <[email protected]>

casparvl commented Aug 4, 2025

View reviewed changes

docs/governance/governance.md Outdated Show resolved Hide resolved

casparvl and others added 12 commits August 4, 2025 15:31

Apply suggestions from code review

de709ae

Fix anchors

842b0ce

Add changelog

4ad0af3

Clarify that commercial use _is_ permitted

fb0e8e6

Changed Contact point to the docs page about support

edb7325

Add contact details

3bd2970

Change index, see if this resolves @boegels loading issue

955a9f9

Merge branch 'main' into governance

6a371eb

Fix anchor

c868b76

Fix links

351e935

Fix external links

555dcfe

Remove redirect

2e21fd7

bedroge reviewed Aug 7, 2025

View reviewed changes

branfosj reviewed Aug 20, 2025

View reviewed changes

verdurin suggested changes Aug 20, 2025

View reviewed changes

boegel reviewed Aug 20, 2025

View reviewed changes

	Teams decide themselves decide the procedure to remove new Team members. As for the procedure of adding Team Members, the procedure to remove Team Members should reflect the sensitivity of the position.
	Teams themselves decide the procedure to remove Team members. As for the procedure of adding Team Members, the procedure to remove Team Members should reflect the sensitivity of the position.

	TODO: Should refer to some Contribution Agreement. Is contributing only possible after signing this agremeent? If so, that should be stated here
	TODO: Should refer to some Contribution Agreement. Is contributing only possible after signing this agreement? If so, that should be stated here

		@@ -0,0 +1,49 @@
		<!--
		A project charter discusses _what it is and why it exists_, a governance discusses _how it operates_.


		## Our Pledge

		We as members, contributors, and leaders pledge to make participation in our

		@@ -0,0 +1,238 @@
		<!--
		A project charter discusses _what it is and why it exists_, a governance discusses _how it operates_.

	The owners of the [EESSI GitHub organization](https://github.com/EESSI) & repositories are those individuals with `owner` rights on the EESSI GitHub organization or one of it's associated repositories.
	The owners of the [EESSI GitHub organization](https://github.com/EESSI) & repositories are those individuals with `owner` rights on the EESSI GitHub organization or one of its associated repositories.

	- A Member may be voted out. In this case, the vote needs to be unanimous between the other Members. This procedure is intended to provide a mechanism for addressing extraordinary circumstances where a members behavior or actions are deemed severely detrimental to the committee's function or reputation, and/or to the EESSI project.
	- A Member may be voted out. In this case, the vote needs to be unanimous between the other Members. This procedure is intended to provide a mechanism for addressing extraordinary circumstances where a member's behavior or actions are deemed severely detrimental to the committee's function or reputation, and/or to the EESSI project.

	Note that if Members change jobs, or move to another country, some of the above criteria that were taken into account during selection may no longer be satisfied. It is up to the Steering Committee to decide if this is problematic, and if so, try to restore balance by requesting someone to resign.
	Note that if Members change jobs, or move to another country, some of the above criteria that were taken into account during selection may no longer be satisfied. It is up to the Steering Committee to decide if this is problematic, and if so, try to restore balance by requesting someone's resignation.


		## 4. Transparency and Traceability

		EESSI aims to be transparent regarding how software was build. A combination of the git history, EasyBuild logs, as well as the `easybuild` subdirectory within every installation (which provides the easyconfig and patch files, easyblock, and any hooks used at installation time) provide a detailed description of how software was configured and built.


		# EESSI Team Policies

		There are currently no Team Policies yet.

	There are currently no Team Policies yet.
	There are no Team Policies yet.


		Note that if Members change jobs, or move to another country, some of the above criteria that were taken into account during selection may no longer be satisfied. It is up to the Steering Committee to decide if this is problematic, and if so, try to restore balance by requesting someone to resign.

		All new Members will appoint an alternate that may represent them and vote on their behalf in case they are unavailable. If a Member resigns or is voted out from the Steering Committee, their alternate immediately loses any rights they had as an alternate.

EESSI Governance #456

Are you sure you want to change the base?

EESSI Governance #456

Uh oh!

Conversation

casparvl commented May 7, 2025

Uh oh!

bedroge commented May 7, 2025

Uh oh!

casparvl commented May 7, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!