| |
@@ -0,0 +1,33 @@
|
| |
+ = D&I Team Decision Making Process
|
| |
+
|
| |
+ This page describes the decision process followed within the Fedora D&I team.
|
| |
+
|
| |
+ [[process]]
|
| |
+ == Process
|
| |
+
|
| |
+ **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.
|
| |
+
|
| |
+ **Who are the eligible Members to vote?**
|
| |
+ Fedora link:Diversity#Team_Members[Diversity and Inclusion Team member] are eligible to vote.
|
| |
+
|
| |
+ **Which approval process should be followed and when?**
|
| |
+ Lazy approval will be followed for tasks which already have a defined process in D&I Team and when all prior steps for this task have been completed with just the ticket-based approval remaining.
|
| |
+ For example, translation of an article, sponsoring a new membership etc.
|
| |
+
|
| |
+ Full consensus is needed for approving new processes, additional improvements to an existing process and tasks requiring D&I funding.
|
| |
+ For example - proposal for event guidelines for Fedora event organizers, for the decisions related to D&I team presence at Flock, full consensus process will be followed.
|
| |
+
|
| |
+ [[links]]
|
| |
+ == Links
|
| |
+ 1. Pagure Ticket - https://pagure.io/fedora-diversity/issue/98
|
| |
I'm not sure what page we are linking here. Currently this is a 404 link when I test locally: http://localhost:8080/diversity-inclusion/decision-process/Diversity#Team_Members
Maybe it is better to not include a link here? I'm not sure where we publish a list of team members other than FAS.