Update Rucio Advisory Board mandate

docs/rucio_advisory_board.md

@@ -6,30 +6,31 @@ title: Rucio Advisory Board
 ## Mandate and responsibilities of the board
 
 The primary function of the Rucio advisory board (RAB) is to provide expertise from
-representatives of Rucio communities and to advise the Rucio project leader.
-Long-term priorities and plans of communities should be discussed by the RAB in
-order to advise on the alignment of Rucio project objectives and plans. This should
+representatives of Rucio Science Communities (RSC) and to advise the Rucio project
+leader. Long-term priorities and plans of communities should be discussed by the RAB
+in order to advise on the alignment of Rucio project objectives and plans. This should
 also lead to the identification of common objectives to form common development
 efforts. The resource and person-power situation within the Rucio project, the
-discussion and identification of funding streams and collaboration on funded
-projects are also within the scope of the RAB. The Rucio project lead communicates
-the advice given by the advisory board to the development team.
+discussion and identification of funding streams and collaboration on funded projects
+are also within the scope of the RAB. The Rucio project leader communicates the advice
+given by the advisory board to the development team.
 
 The board provides non-binding strategic advice and is informal in nature.
 
 ## Composition
 
-The RAB is composed of a group of community representatives. The goal is to
-complement the expertise of the development team, and thus representatives should
-have knowledge about the long-term strategy of their community and ideally have
-responsibility for their project programme and budget.
+The RAB is composed of a group of representatives of their respective RSC. The goal is
+to complement the expertise of the development team, and thus representatives should
+have knowledge about the long-term computing strategy of their community and ideally
+have responsibility for their project programme and budget.
 
 Membership in the RAB is by invitation of the Rucio project leader. However,
 suggestions for expanding the board should ideally come from the RAB itself.
-Representatives serve a 2-year, renewable, term. Invitations to join the board
-are made to the respective community itself, which should in return nominate one,
-exceptionally two, representatives to join the board. Nominations are discussed
-with the Rucio project leader.
+Representatives serve a 2-year, renewable, term. Invitations to join the board are
+made to the legal representative of the RSC, typically the spokesperson or coordinator
+charged with the computing portfolio of the community. The RSC should in return
+nominate one representative from their community to join the board. Nominations are
+discussed with the Rucio project leader who ultimately decides on the acceptance.
 
 The Rucio project leader is an ex-officio member of the board and chairs the
 board meetings.
@@ -51,6 +52,17 @@ board meetings.
 | [ATLAS](https://atlas.cern)         | David Cameron, U Oslo | 2023-Feb to 2023-Apr |
 | [Belle II](https://www.belle2.org)  | Paul Laycock, BNL     | 2023-Feb to 2023-Jun |
 
+
+### Eligibility criteria
+
+There are no strict eligibility criteria for an RSC to be viable for having a
+representative on the RAB. However the goal of the RAB is to have all science
+communities, who utilize Rucio in production and who are significantly involved in the
+development of the system, represented on the board. Such significance involves, but
+is not limited to, long-term contributions of source-code, leadership roles as Rucio
+component-leads, participation in hackathons and Rucio workshops, community support on
+the Mattermost channel, etc.
+
 ## Organisation
 
 The RAB meets as needed, nominally twice a year. Meetings generally take place
@@ -62,4 +74,5 @@ Minutes are kept internal to the RAB.
 
 | Version                                                                         | Creation    |
 | ------------------------------------------------------------------------------- | ----------- |
+| [v1.1](https://rucio.cern.ch/documentation/files/Rucio_Advisory_Board_v1.1.pdf) | May 8, 2024 |
 | [v1.0](https://rucio.cern.ch/documentation/files/Rucio_Advisory_Board_v1.0.pdf) | Nov 7, 2022 |