39 min | Lockdown standards ratification | group | Nick proposed to the group that we live edit Standards Ratification Process Discussion proceeded to discussion on the proposed voting procedure on use cases within the Use Case WG. Saori contextualized that this was voting just specific to the use cases approval process (implication that this is not necessarily the voting procedure/voter criteria that should be used for a wider group) Nick: My concern that is the administrative overhead of this is too complicated and if things won't just sort them out without this rule. Rob mentioned that: JT: said that when you reject, you have to also have a reason Do we want
Notes from Aaron W re voting for reference and consideration: Here are my thoughts on voting procedure for working groups. Generally, any voting procedure is fine so long as it clearly defines:
What is the outcome being voted on Who is eligible to vote A clear time period during which votes may be cast How to cast a vote The quorum (if any) required for a binding vote The threshold required for a vote to pass
Here are some options for 2 - 5:
Who is eligible to vote Anyone who has attended X out of the last Y meetings Anyone who attended the meeting where the issue was discussed and the vote called Anyone who is subscribed to the WG mailing list (but beware heckler votes/uninformed voters)
A clear time period during which votes may be cast How to cast a vote "Yea/Yes/Approve/Agree" or "Nay/No/Disapprove/Disagree" aloud during meeting "+1" (approve), "-1" (disapprove), or "0" (abstain) over email or Symphony chat
The quorum required for a binding vote The threshold required for a vote to pass
I'd say the least complicated route is to announce each vote via an email to the mailing list, allow a week or two for votes to be cast, require voting via email, and make the threshold a majority of votes cast. However, if there is concern over disengaged or bad-faith voters, they should consider a minimum participation requirement for eligibility.
Discussion proceeded on
|