Community amendment 1 - Githubissues

Rendered View

PR to address a bunch of changes that need to be made to the community team's governance and structure.

A summary of the changes made within this amendment follows:

Keyholders are explicitly no longer members of the Community Team, but they're still welcome to oversee the community team's decisions and processes and provide feedback and insight if they wish. This also means they're no longer considered to be voting members.
It's no longer required that all Community Team members are moderators. While the majority of the Community Team should be moderation and management staff, there's also room for event managers, organisational supports, and so on.
Trainee Community Moderators have been defined, and new Community Moderators must go through a training period before they can graduate and become Community Moderators. Trainee Community Moderators do not vote on internal polls, and are not expected to handle difficult situations.
The process for handling internal votes has been separated out from the rest of the processes, and standardized. This allows for a consistent voting process regardless of what's being voted on, while still allowing for extra closing, failing and passing conditions as required. Failing conditions also override passing conditions, instead of the other way around.
The voting process now takes abstentions into account, both explicitly (where the voting member states they're abstaining) and implicitly (where the voting member simply doesn't vote).
Admins are no longer considered to be voting members unless they're part of the Community Team, or consensus for a vote cannot be reached.
For Community Team elections, the interview now comes before the vote, rather than the other way around.
A new process to be followed when existing Community Team members wish to switch their role or take on new roles has been written.

QuiltMC / rfcs

Community amendment 1 #29