Monday, January 28, 2013

Proposal: Unary consent

Times out and fails 5-9. -scshunt

Adminned at 29 Jan 2013 19:10:41 UTC

Add a subrule to rule 2.2 ““Unanimous” Consent”, call it “Fast Veto” and give it the text:

If there exists a comment from the Speaker on a given pending Proposal that contains both the ARROW arrow and VETO veto icons, then that Proposal may be failed by any Admin.

Comments

Patrick:

28-01-2013 01:34:57 UTC

for  arrow

RaichuKFM: she/her

28-01-2013 02:00:16 UTC

for  arrow I like how it only works if the Speaker wants it to; he could just never use it.

Skju:

28-01-2013 02:18:26 UTC

for  arrow
I’ve decided I like it.

Larrytheturtle:

28-01-2013 02:41:33 UTC

for  arrow

Josh: Observer he/they

28-01-2013 08:47:41 UTC

against It may lose my credibility but I will never vote for the speedy veto. Read my lips: no speedy veto!

Kevan: he/him

28-01-2013 08:50:00 UTC

against Per Josh and precedent.

Purplebeard:

28-01-2013 09:26:17 UTC

against Never!

RaichuKFM: she/her

28-01-2013 11:24:31 UTC

I wouldn’t have voted for it, but we already have fast passing and failing.

Josh: Observer he/they

28-01-2013 11:36:25 UTC

Yeah, and that mechanism applies to vetoes as well. It’s sufficient; I don’t want the emperor deciding to hand proposal slots back by fiat.

Skju:

28-01-2013 12:57:18 UTC

But remember that the speaker no longer has a vote before 48 hours. Opinion could still be expressed this way.

Josh: Observer he/they

28-01-2013 14:24:23 UTC

Vetoes aren’t restricted in the same way as other votes.

nqeron:

28-01-2013 15:25:24 UTC

against per Kevan

Cpt_Koen:

28-01-2013 16:48:23 UTC

for  arrow (explicit arrow casting)

I’m usually against fast veto, but as RaichuKFM said, we already have fast thing, and I don’t like having to cast a vote on a Proposal that has been vetoed already.

Klisz:

28-01-2013 18:24:44 UTC

for  arrow

quirck: he/him

28-01-2013 18:49:36 UTC

for

Clucky: he/him

28-01-2013 19:44:25 UTC

against the fast passing thing is bad enough. please no speedy veto.

Murphy:

28-01-2013 23:25:00 UTC

against  arrow

Patrick:

29-01-2013 01:21:03 UTC

CoV against

RaichuKFM: she/her

29-01-2013 01:42:55 UTC

I don’t want to have to vote on a proposal that’s going to fail anyway to avoid losing credibility; I’m not supporting this for automatic slot return; I usually don’t expend my allotted slots. I’m in favor of the clearing of the cache aspect. Again, I would not usually support this, but in a dynasty that is focusing on messing with core mechanics, especially voting, I think this is appropriate.

Clucky: he/him

29-01-2013 06:30:35 UTC

oh wait, you’ve realized that punishing people who vote against passing proposals is *also* a bad idea?

I like how “Lets have a dynasty that messes with the voting mechanics” has turned into “lets try to add every single terrible way to mess with voting mechanics we can”

Spitemaster:

29-01-2013 16:27:23 UTC

against If it’s vetoed, nobody loses Credibility anyway.

RaichuKFM: she/her

29-01-2013 20:52:13 UTC

Speaking of which, a sizable amount of us are looking at a loss of Credibility. But I’m going down with this ship!

scshunt:

29-01-2013 22:20:08 UTC

against since the 48-hour limit is coming up.

Skju:

30-01-2013 03:07:16 UTC

against
Fail now?