Prepare RV council elections

.readthedocs.yml

@@ -4,7 +4,11 @@ sphinx:
     configuration: conf.py
     fail_on_warning: true
 
+build:
+  os: ubuntu-22.04
+  tools:
+    python: "3.11"
+
 python:
-   version: "3.8"
    install:
    - requirements: sphinx/requirements.txt

conf.py

@@ -37,7 +37,8 @@
 
 # -- Options for extensions
 
-myst_enable_extensions = ["colon_fence", "deflist", "dollarmath", "amsmath"]
+myst_enable_extensions = ["colon_fence", "deflist", "dollarmath", "amsmath", "attrs_block", "linkify"]
+myst_linkify_fuzzy_links = False
 
 
 # -- Options for HTML output

elections/ArviZ_2024.md

@@ -0,0 +1,21 @@
+# Election 2024
+## Summary of process
+This is the 2nd election to happen for the ArviZ project.
+The election process should now be stabilized and described
+at {ref}`council_selection`.
+
+## Process details
+### Nominations for the RV Council (April 12th)
+A GitHub issue within the [arviz-project](https://github.com/arviz-devs/arviz-project)
+repository has been created for nominations to take place: https://github.com/arviz-devs/arviz-project/issues/49
+
+### First round election (TBD)
+Around April 26th (and no earlier than that) nominations will close and
+the {ref}`first round of the election <initial_voting_election>` will start.
+
+### Tie breaking election (if necessary) (TBD)
+If necessary, a {ref}`tie breaking election <run_off_election>` will be held after the initial one.
+
+### Election result (TBD)
+Once the whole process ends, election results will be posted on the
+same GitHub issue used for nominations and registered here too.

elections/README.md

@@ -4,5 +4,6 @@ Historical log of ArviZ elections.
 :::{toctree}
 :maxdepth: 1
 
-ArviZ_2020.md
+ArviZ_2020
+ArviZ_2024
 :::

governance/community_architecture.md

@@ -10,6 +10,7 @@ Anyone working with ArviZ has the responsibility to personally uphold
 the Code of Conduct. Core Contributors have the additional responsibility
 of _enforcing_ the Code of Conduct to maintain a safe community.
 
+{#team_member_definition}
 The terms "ArviZ team" and "ArviZ team members" are used to refer everyone
 who is either recurrent or core contributor.
 
@@ -19,11 +20,12 @@ Recurrent Contributors are those individuals who contribute recurrently to the
 project and can provide valuable insight on the project.
 They are therefore actively consulted and can participate in the same communication
 channels as Core Contributors. However, unlike Core Contributors,
-Recurrent Contributors don't have voting, managing or writing rights.
+Recurrent Contributors only vote in elections and don't have managing or writing rights.
 
 In practice, this translates in participating from private team discussions
-(i.e. in Slack or live meetings) but not being able to vote in elections
-for the Random Variables Council members nor having commit rights on GitHub.
+(i.e. in Slack or live meetings) but having commit rights on GitHub,
+nor admin rights on other services, nor being eligible as candidates for the
+Random Variables council.
 
 The Recurrent Contributor position will often be an intermediate step for people
 in becoming Core Contributors once their contributions are frequent enough

governance/processes.md

@@ -116,7 +116,7 @@ issue, but must recuse themselves from voting on the issue.
   Each voter can vote zero or more times, once per each candidate. As this is not about
   ranking but about capabilities, voters vote on a yes/neutral/no basis
   per candidate -- “would I trust this person to lead ArviZ?”.
-  - All core contributors can vote in an election.
+  - All {ref}`ArviZ team members <team_member_definition>` can vote in an election.
 * Candidates are evaluated independently, each candidate having 60% or more of
   yes votes _and_ less or equal than 20% of no votes is chosen.
   If the council resulting from all accepted candidates matches all conditions