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.

casparvl · 2025-06-19T09:49:49Z

docs/governance/code_of_conduct.md

+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the EESSI Steering Committee via direct message to one of the


Note that I've changed a few "community leaders" into "EESSI Steering Committee". I think when it comes to reporting abuse, it should be very clear to whom that should be reported, and community leaders is extremely vague.

In other places, I feel 'community leaders' is a more appropriate term, e.g. where it comes to stating that community leaders have the right toe remove or edit commits that break the code of conduct - in this context, the community leader would be someone with a maintainer role.

TODO: change to inidivdual mail addresses + add mail addresses steering committee members in the steering_committee.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.

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

docs/governance/charter.md

+
+## 1. Mission
+<!-- Describe the project's purpose and the problem it addresses. Include a short mission statement. -->
+The EESSI project aims to build a common software stack that is:


Spell out EESSI in full the first time you use it + make it link to EESSI homepage?

Maybe also include logo on top of the page

docs/governance/charter.md

boegel · 2025-06-19T10:26:59Z

docs/governance/charter.md

+- Cross-platform (laptop, Cloud VM, HPC Cluster)
+- Ready-to-use (served over the internet, just mount-and-go)
+- Optimized for a wide range of hardware architectures (CPU, GPU, interconnects)
+- Easily extendable


Should clarify what this means? Maybe also "customizable" (cfr. host injections)

Extra bullet for focus on Linux systems/VMs? (no native macOS/Windows)

boegel · 2025-06-19T10:27:16Z

docs/governance/charter.md

+## 2. Scope
+<!-- Define what is within the scope of the project and what is explicitly out of scope. -->
+EESSI will focus on creating a repository of software installations (software.eessi.io). This requires:
+- code to build and deploy new software into the repository


Needs empty line above to fix formatting + capitalize bullet points

Suggested change

- code to build and deploy new software into the repository

- Scripts to automate the process of building and deploying additional software installations in `software.eessi.io`

boegel · 2025-06-19T10:28:38Z

docs/governance/charter.md

+
+## 2. Scope
+<!-- Define what is within the scope of the project and what is explicitly out of scope. -->
+EESSI will focus on creating a repository of software installations (software.eessi.io). This requires:


repository is common technical terminology that usually means "package repository" (like RPMs), but actually means something else for us (CernVM-FS repository), so let's avoid that term (or be explicit), something like:

Suggested change

EESSI will focus on creating a repository of software installations (software.eessi.io). This requires:

EESSI focuses on creating a shared stack of software installations (`software.eessi.io`) that is distributed through a [CernVM-FS](https://cernvm.cern.ch/fs/) repository.

This requires:

docs/governance/governance.md

boegel · 2025-06-19T10:58:50Z

docs/governance/governance.md

+
+System administrators of systems providing EESSI are administrators of systems (such as, but not limited to cloud and HPC systems) that make the EESSI software stack available to their users.
+
+System administrators of systems providing EESSI are responsible for making sure that their system does not put any disproportional load on the public EESSI CernVM-FS infrastructure. Typically, this means that they are responsible for provisioning proper caching for their system, such as a private CernVM-FS Stratum 1, a proxy, and/or a properly sized local cache.


I'm not sure we can hold sysadmins responsible for anything.

How do they know that by making EESSI available they're agreeing to being responsible for this?

Also, how can they know that they've overloading EESSI's public infra? Will we notify them?

boegel · 2025-06-19T10:59:53Z

docs/governance/governance.md

+
+### 2.8 End-Users
+
+End-Users are individuals that use any of the software provided by the EESSI software stack.


We should link to our terms of use here?

casparvl · 2025-06-19T11:07:07Z

docs/governance/governance.md

+
+The Steering Committee is made up of community members with sustained and recognized contributions over time. Members take part in the Steering Committee as private individuals (i.e. they do not represent their employer(s)).
+
+Members will be removed from the committee if they resign. Furthermore, if a Member is inactive for 6 Months and does not reply to communication from the rest of the Steering Committee, the Member may be voted out by the other Steering Committee members (regular voting rules, as per section 6.3, apply). Finally, a Member may be voted out. In this case, the vote needs to be unanimous between the other Members.


Suggested change

Members will be removed from the committee if they resign. Furthermore, if a Member is inactive for 6 Months and does not reply to communication from the rest of the Steering Committee, the Member may be voted out by the other Steering Committee members (regular voting rules, as per section 6.3, apply). Finally, a Member may be voted out. In this case, the vote needs to be unanimous between the other Members.

Membership of the Steering Committe 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.

- If a Member is inactive for 6 Months and does not reply to communication from the rest of the Steering Committee, the Member may be voted out by the other Steering Committee members. In this case, regular voting rules, as per section 6.3, apply.

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

Add code of conduct to the website tree

90c26e7

boegel reviewed Jun 19, 2025

View reviewed changes

boegel requested changes Jun 19, 2025

View reviewed changes

casparvl commented Jun 19, 2025

View reviewed changes

Caspar van Leeuwen added 9 commits June 23, 2025 14:19

Processed Kenneth's comments and suggestions

1757d52

Processed Kenneths comments

9b42ba0

Add initial terms of use

18334ad

Add date to terms of use

6862260

Revise section 2 of terms of use

e7fac73

Take out SBOM policy, replace with what we _can_ promise

9db6ece

Fix typos

e1e4f77

Fix typos

b24cbaf

Make overview page and redirect original governance page there

4db5a89

	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

	- code to build and deploy new software into the repository
	- Scripts to automate the process of building and deploying additional software installations in `software.eessi.io`


		System administrators of systems providing EESSI are administrators of systems (such as, but not limited to cloud and HPC systems) that make the EESSI software stack available to their users.

		System administrators of systems providing EESSI are responsible for making sure that their system does not put any disproportional load on the public EESSI CernVM-FS infrastructure. Typically, this means that they are responsible for provisioning proper caching for their system, such as a private CernVM-FS Stratum 1, a proxy, and/or a properly sized local cache.


		### 2.8 End-Users

		End-Users are individuals that use any of the software provided by the EESSI software stack.


		The Steering Committee is made up of community members with sustained and recognized contributions over time. Members take part in the Steering Committee as private individuals (i.e. they do not represent their employer(s)).

		Members will be removed from the committee if they resign. Furthermore, if a Member is inactive for 6 Months and does not reply to communication from the rest of the Steering Committee, the Member may be voted out by the other Steering Committee members (regular voting rules, as per section 6.3, apply). Finally, a Member may be voted out. In this case, the vote needs to be unanimous between the other Members.

-Members will be removed from the committee if they resign. Furthermore, if a Member is inactive for 6 Months and does not reply to communication from the rest of the Steering Committee, the Member may be voted out by the other Steering Committee members (regular voting rules, as per section 6.3, apply). Finally, a Member may be voted out. In this case, the vote needs to be unanimous between the other Members.
+Membership of the Steering Committe 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.
+- If a Member is inactive for 6 Months and does not reply to communication from the rest of the Steering Committee, the Member may be voted out by the other Steering Committee members. In this case, regular voting rules, as per section 6.3, apply.

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!

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!

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!

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!

casparvl Jun 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

casparvl Jun 19, 2025 •

edited

Loading