Hello,
Looking only at the voting mechanism:
- +1 votes are unchanged.
- -1 votes in this proposal = verbally threatening to resign, or resigning over the issue; we have a history of such resignations, so in a sense this is "nothing new"; but building them into a process makes the possibility more prominent, and perhaps implicitly more escalated.
- 0 votes in this proposal = -1 votes in our current practice
- Quorum decreased from 5 to 3
there's only one real change, decreasing the quorum: in a situation where there are 3 people supporting a proposal, 5 people against a proposal but not willing to resign over it, and no other alternative being proposed, the proposal passes. That seems really unhealthy (... well, and strange, because those 5 people could bring a counterproposal of "do nothing").
But, overall, I'd favor a much weaker mechanism for encouraging consensus-building: I do think it should be easy and painless (both for the author and the group) to propose and refuse a clearly minority opinion. Perhaps something like:
- Any proposal can be approved on a meeting if there is an unanimous agreement of the voting attendees of the meeting (including advance votes by non-attendees).
- Any proposal can be approved on a mailing list with an unanimous agreement (all 9 voting members)—or only a smaller quorum, like 7?
- All proposals can be approved with a quorum of 5 voting members 4 (5? 6?) days after they have been proposed.
i.e. giving a "cooling off" period to look for a consensus, allow quick decision making when there is a consensus, and motivating everyone to put proposals on the mailing list instead of only bringing them to the meeting (which has nothing to do with consensus, but would save time during meetings).
Mirek