Merge branch 'rc_req' into 'main'

RC: add requirements for first shift

See merge request !95

docs/software-infrastructure/release-coordinators/index.md

@@ -7,7 +7,12 @@ coordinator is concerned with. It is assumed that you are familiar with the
 general workflow for ATLAS Offline software development as summarised in the
 [Workflow Quick Reference](/{{locations.athena_git}}/workflow-quick.md).
 Having an overview of the tasks of the software review shifters as well as
-knowing basics of git is also helpful.
+a good knowledge of git is also required.
+
+Requirements before your first shift:
+
+- You are a member of the [atlas-release-coordinators](https://gitlab.cern.ch/groups/atlas-release-coordinators/-/group_members) GitLab group.
+- You are subscribed to the [atlas-sw-athena-release-coord](https://e-groups.cern.ch/e-groups/Egroup.do?egroupName=atlas-sw-athena-release-coord) e-group.
 
 ## Checking the status of the release
 Before accepting new MRs, you should check the status of the latest nightly. The first priority of a release coordinator should be to make sure that the release is in good shape, and obviously existing problems should usually be fixed before adding more MRs (though as release coordinator you should always feel free to use your judgement).