Post via forum by datahead <cjj_009@xxxxxxxxxx>:
It is perfectly possible to design the voting process in such a way
votes for the different issues can be given in a single message.
it would have to be "For issue #1 I vote yes, for issue #2
I vote no, and for issue #3 I vote option 3"
This is what I meant. Thank you for clarifying, though.
I would instead suggest to incorporate the [team addition] votings
into the outstanding General Discussion.
My concern here is that if a full two thirds of the new team members do not make it to the
general discussion for any
reason, we will be frozen on both team additions and on changing the voting rules
Furthermore, we already have a good sized list of topics, which will result in a long
meeting as it is.
My suggestion would be to start the vote well before the team meeting (maybe even a month
before) by email and then, if
we aren't getting the needed responses, finish the vote during the IRC meeting.
There currently are 10 team members. (2.0 / 3.0) * 10 =~ 6.66. This normally rounds to 7
people. It would be within reason that we could have a little difficulty reaching as many
as 3 people by email. It would be even more likely this many or more could miss the IRC
We could also concurrently vote on the voting rules changes by email, in order to get the
full team votes for this as well.
Somebody who doesn’t vote doesn’t mean
to vote "against", so it would be an error to speak of him as being
"against" the issue voted about.
This is very true. Unfortunately, the voting result is still the same as a no vote. That
is all I was trying to say.
it is our fault that there only is such a small number of levels
Aside from assigning new music tracks to levels, we might start thinking about whether to
add any recent level submissions to the new release.
Sent by Chessboard.