[boegel]

This is a change to EESSI governance, so requires two-thirds majority of EESSI Steering Committee (see EESSI Governance section 6.3.9).

I would like to organize the vote on this fully electronically, which requires all (4) current members of the EESSI Steering Committee to join the vote (see EESSI Governance section 6.3.7):

Overview of votes:

• @boegel: ✅
• @hvelab: ❓
• @bedroge: ❓
• @casparvl: ❓

This PR only adds a security policy as a new section 1 in https://eessi.io/docs/governance/policies/ (there was no section 1 yet, only 2 & onwards...), and makes some minor tweaks throughout the page, like fixing the subsection levels so a menu with subsections in shown on the right of the page, and adding anchor labels to each section.
Beyond that, no other changes are made to the contents of existing subsections.

[boegel]

I approve of this proposed security policy for EESSI in its current form (commit d0081c6).

[boegel]

If when this is merged, next step would be to create a very minimal SECURITY.md in the existing EESSI/.github GitHub repository, which should make it pop up in all EESSI GitHub repositories...

Contents of that SECURITY.md could be as simple as:

# EESSI security policy

See <https://eessi.io/docs/governance/policies/#security-policy>