I vote Yes on 306. Not that it matters, except for point value.
Thanks, Little Nemo and davidm, for the further suggestions. davidm, I like your second paragraph, but I’ve always taken “submitting a proposal” to basically mean “call for votes” since it seems that submitting a proposal implies that it’s therefore ready to be voted on. Am I right here?
Perhaps we could say “has put a proposal forth for discussion but has not called for a vote within n hours after the commencement of discussion”? That would limit the debate period, though.
Instead, if we allowed, say 96 hours between the last player voting on the previous proposal and the submission of the new proposal, that would give us minimum four days for debate. That period could even be longer if the proposal was tentatively brought up before voting had closed on the prior proposal.
Sort of like what I’m doing with this one, I guess. Here’s what I’m thinking for the variables:
x (time waiting for a vote) = 72 hours
y (time waiting for a proposal) = 96 hours
Thoughts?
At first, I had reservations about tying the last person voting on the prior proposal and the closing of votes for the next proposal. However, the way Treviathan describes it above works for me.
Bumping this back to the front page.
I realize I haven’t yoted for this current one, and since it won’t make a difference anyway, I vote NO.
I vote YES on 306.
We’re still waiting for two votes on 306 before proceeding.
Zev Steinhardt
Still waiting on one vote…
Zev Steinhardt
I’m moving this weekend and won’t be on line until about next Wednesday or Thursday. May I elect to have an in absentia ‘yes’ vote counted for whatever comes up meanwhile? I figure since things still need to be unanimous to pass, I will trust the majority.
I’m wondering if we’re not addressing this problem in the wrong way. Maybe instead of defining who has to vote and by how many votes a proposal has to recieve to go on, maybe instead we just “force” votes.
For example, suppose we allow that after a proposal has been proposed, players have X hours to cast their votes. Any player who does not cast his vote by then is said to have cast an “ABSTAIN” vote which is not counted for purposes of determining a majority or uninamity. We could also require a minimum percentage of votes (a quorom) in order for any measure to pass. Furthermore, we can determine that after Y number of “ABSTAIN” votes, the player is dropped from the list of active players. Lastly, we could define the close of voting as when X hours have passed or when the last vote is received. This gives us some flexibility:
a. It allows people time to debate and change thier votes if they want to (up to the close of voting).
b. It will prevent any single player (or even the majority) from holding us up in terms of voting on proposals.
c. It will prevent long-term absentee players from holding us up too (because eventually they’ll be dropped).
Zev Steinhardt
All right, I think I’ve got my proposal hammered out. Like capybara I’m moving this weekend, too, but I should be able to post it sometime Saturday (assuming we’ve heard from MarkofT by then).
Please place your fingers on the voting buzzers.
How about a straw poll first? Is there anyone who plans on voting against Treviathan’s proposal? And if so, what are your objections?
I vote yes on 306. I had thought I would have better net access this weekend.
Bleh.
BTW, can we make a rule that affects outside the game? Something like “All players are hencefore banned from utilizing UHaul.” It will be a good thing. Trust me.
Okay, since we’ve heard from the last remaining voter, I’d like to propose the following for Rule 307:
Eligibility:
“A player becomes ineligible to vote for the current proposal under all circumstances if that player does not vote within 72 hours after the author of a proposal calls for votes. They remain ineligible for all future proposals until they attempt to vote on a proposal within that proposal’s 72 hour voting period. When that occurs, the vote is counted and they return to eligible status.”
“If it is a player’s turn to make a proposal and the player does not officially submit his/her proposal (by declaring a call for votes) within 96 hours after the final eligible player has submitted his/her vote on the previous proposal, then: (1) the proposing player’s turn is skipped for the current round, (2) he/she is rendered ineligible for voting according to the terms established in the previous paragraph, and (3) play proceeds to the next player, who has 96 hours to make his/her new proposal (commencing at the time the previous player is declared ineligible).”
“This rule supercedes Rule 303 (formerly Rule 105) where they conflict.”
(Cue campaign speech) I think we need some sort of framework in place in case someone drops out of the game. If there’s disagreement on the time limits I’ve proposed, could we perhaps amend them later and not strike down this much-needed rule?
Oh, and Zev, I think that aside from your quorum suggestion we’re pretty much on the same track. Being declared “ineligible” is sort of like having an “abstain” as your default vote, right?
I like Leviathan’s proposal. I vote YES on 307.
re: “ineligibile” vs. “abstain”
I think that declaring a voter ineligible would make a difference to scoring, since a proposer’s score would be increased by
# yes instead of # yes
yes + no yes + no + abstain
Rather, that fraction is applied to the number obtained via rule 202. anyway, my point is that player’s scores will be greater by declaring non-voters ineligible instead of having votes for abstention.
Voting yes on 307.
C’mon people, let’s all work together and enact a new rule.
I agree, Little Nemo. I’ll vote yes.
I vote YES on 307.
I vote YES on 307.