Skip to content

Commit

Permalink
define all process steps
Browse files Browse the repository at this point in the history
  • Loading branch information
OriolAbril committed Apr 12, 2024
1 parent b1c486b commit 6c55e86
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 4 deletions.
8 changes: 5 additions & 3 deletions governance/community_architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand All @@ -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
Expand Down
2 changes: 1 addition & 1 deletion governance/processes.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 6c55e86

Please sign in to comment.