alciregi / centos / centos.org

Forked from centos/centos.org a year ago
Clone

Blame about/governance/voting.md

401d07
---
401d07
title: "CentOS Governance - Voting"
d66007
layout: aside
401d07
---
401d07
401d07
The voting system used by all SIGs and the Governing Board uses a
401d07
[consensus-based decision
401d07
model](/about/governance/appendix-glossary/#consensus-decision-making) except
401d07
where noted.
401d07
401d07
Except where noted, decisions require 3 yes votes (+1) and no objections (-1's)
401d07
and, except as noted below, votes should be left open for at least 72 hours.
401d07
Any Board member may cast a vote in any SIG vote and it is considered binding
401d07
(counted against the vote). If a vote is held on a public list (e.g., to test
401d07
the broader consensus of a group) only the votes of the Board members for Board
401d07
votes or SIG committers or Board members for SIG votes are considered binding.
401d07
All other votes are just considered as valuable data in the decision process.
401d07
Board business may be conducted on a private or public list, whichever is more
401d07
appropriate for the issue at hand.
401d07
401d07
All -1s votes require reason/ explanation, -1's with no substantiation may be
401d07
overturned. 
401d07
401d07
## When do votes need to be called?
401d07
401d07
Votes need to be called for all substantial business. Votes need to be left
401d07
open for a reasonable period (not less than 72 hours) if members of the Board
401d07
are not available to participate in the vote; provided that for votes/matters
401d07
that have been deemed time or business critical by Red Hat, as noted below,
401d07
voting must be held open until the Liaison has voted.
401d07
401d07
_Lazy consensus_ may be used for non-substantial business. Lazy consensus is
401d07
defined as asking for objections as opposed to calling for a vote. Any
401d07
objection on lazy consensus is considered the same as a -1 on a vote. There is
401d07
no minimum +1 vote requirement.
401d07
401d07
## Role of the Liaison
401d07
401d07
The Liaison also has the role of dealing with issues such as security, export,
401d07
or items that have a direct legal or other Red Hat business connection for the
401d07
Project, and on issues of such business may have an additional role as defined
401d07
by the following:
401d07
401d07
A. If a decision/solution cannot be found on an issue that is deemed time
401d07
and/or business critical by Red Hat then, after a reasonable time, the Liaison
401d07
may be requested by the Chair to seek assistance from Red Hat in making the
401d07
decision, obtaining additional input from Red Hat executives, engineers, and
401d07
stakeholders.
401d07
401d07
B.  The Liaison may, in exceptional circumstances, make a decision on behalf of
401d07
the Board if a consensus has not been reached on an issue that is deemed time
401d07
or business critical by Red Hat if:  (1) a board quorum (i.e., a majority) is
401d07
present or a quorum of Board members has cast their votes; or (2) after 3
401d07
working days if a Board quorum is not present at a meeting or a quorum has not
401d07
cast their votes (list votes); provided that the Chair may (or at the request
401d07
of the Liaison, will) call a meeting and demand that a quorum be present.  
401d07
779af6
Unless the Liaison specifically indicates on a specific issue that they are
779af6
acting in their official capacity as Liaison, either prior to a vote or later
401d07
(e.g., after an issue has been deemed time or business critical), the Liaison's
401d07
voice and vote is treated the same as any other member of the Board. Decisions
401d07
indicated as Liaison decisions made on behalf of the Board by the Liaison may
401d07
not be overturned.