Formalize voting process

[pmolodo]

Description

One function of the Build Interest Group is to provide a "unified voice" to advocate (or implement) certain build-related issues. However, in order to claim to represent a diverse group, there needs to be some way to demonstrate that what we're advocating for really is what the GROUP wants.

To do that, I think we need to formalize our voting process, so there's a clear record of how votes are conducted, AND an auditable log of exactly what the vote was.

A few notes:

• Though I speak of "formalizing" this process, it should be noted that from an AOUSD governing perspective, an interest group is not authorized to vote on official AOUSD matters. As such, all votes are non-official and non-binding. (So by "formal", I just mean, we've followed the rules we agreed on - but this still gives no weight in any official / legal / binding capacity as far as the AOUSD is concerned.)
• Votes should be conducted on a one-company, one-vote basis (not per-person)
  • This need is part of the motivation for formalizing this process

Now, a few proposals:

• Votes can take two forms:
  • An in-meeting vote
  • A longer vote held over a fixed period of time

For in-meeting votes:

• There must be a quorom of at least 50% of all companies present at the meeting to hold a vote
• The vote needs > 50% of the companies present in order to pass
• Any company that does not vote is counted as a "no change" or "does not approve" vote

For longer votes:

• Greater than 50% of companies must affirmatively vote to pass

Champion

• Paul Molodowitch pmolodowitch@nvidia.com - @pmolodo

Pull Requests and Issues