+1

I suggest we use something closer to FESCo's current policy:

• Once a proposal is made, it must be voted on within one week.
• If at the end of one week there are at least 3 :thumbsup: on the proposal and 0 :thumbsdown:, it has passed.
• If there are any :thumbsdown:, it is added to the next meeting agenda, where a simple majority vote of those present will decide it.
• If at the end of one week there are not at least 3 :thumbsup:, it is extended one further week and requires only a single :thumbsup: to pass.
• If at the end of two weeks there are still no :thumbsup:, the proposal fails automatically and the status quo is maintained.

I think we need exact definition is who is allowed to vote. The list of members on linked wiki page seems to be outdated.

I think we need exact definition is who is allowed to vote. The list of members on linked wiki page seems to be outdated.

This seems to be covered by "removing the voting member concept" above.

As we decided on yesterday's WG meeting, I'll update the charter following langdon's proposal to ditch the voting member concept and sgallagh's voting proposal with some clarifications:

• Revise the section about "membership" in the charter, specifically remove language about named voting members/aux seats.
• Mention explicitly where votes happen, in a ticket or on the WG meeting.
• Use "votes for/against" phrasing, don't require a specific mode of casting vote (e.g. thumbs up/down, +/-1, etc.).

Here's the revised text I'll use for how votes happen:

• Once a proposal is created as a ticket in the Modularity project issue tracker, it must be voted on in the ticket within one week.
• If at the end of one week there are at least 3 votes for the proposal and 0 votes against in the ticket, it has passed.
• If there are any votes against, the proposal is added to the agenda of the next Working Group meeting, where a simple majority vote of members present will decide it. This decision will be recorded in the ticket.
• If at the end of one week there are fewer than 3 votes for the proposal in the ticket, it is extended one further week and requires only a single affirmative vote to pass.
• If at the end of two weeks there are still no votes for the proposal in the ticket, it fails automatically and the status quo is maintained.