Decision-making process

This page describes how the Fedora D&I team makes decisions.

Process

Members of the Fedora Diversity and Inclusion Team FAS group are eligible to vote.

Lazy Approval

This means general consent is assumed unless valid objections are raised within a specific period of time i.e. 5 days along with minimum two positive vote (+1) and no -1’s. Votes can be cast by any approved member of diversity team. This process is used for decisions with short-term consequences and which can be easily reversed. Any team member can ask for the deadline to be extended or the decision escalated to require full consensus.

Full Consensus

More significant decisions are made through a process of full consensus. In order to pass, these decisions need three positive votes (+3) and no negative votes (-1) within a specific period of time i.e. 14 days. The votes can be cast by any of the approved members in the FAS group for the Diversity and Inclusion Team. A negative vote immediately halts the process and requires discussion. Therefore, in order to remain valid, negative votes must be supported with a specific concern about the proposal, and suggestions for what could be changed in order to make the proposal acceptable.

Choosing a process

Lazy approval is followed for tasks with a defined process in D&I Team. When all prior steps for a task are completed with just the ticket-based approval remaining. For example, translating an article or proposing a Flock session fit in this model.

Full consensus is required to approve new processes, make changes to existing team policies, and tickets requiring D&I budget. For example, proposing new event guidelines for events, changing the decision-making process, and voting on Outreachy budget allocation requires full consensus.

References