Thursday, August 11, 2016

Proposal: And another thing…

Self-killed. -RaichuKFM

Adminned at 11 Aug 2016 16:34:44 UTC

Enact a Rule “Deliberations”, containing the following text:

Any Hunter may submit a Deliberation to alter the text of any pending Proposal or Deliberation by posting an entry in the “Deliberation” category that describes those changes (unless the Hunter already has a Deliberation pending or has already submitted 3 Votable Matters that day, or the target Proposal or Deliberation has already been targeted by a Deliberation pending in the last 12 hours).
Deliberations are Votable Matters and as such are governed by Rule 1.5 (“Votable Matters”). Deliberations cannot be Vetoed or Self-Killed. Any pending Deliberation may be enacted by any Admin if any of the following are true:
It has been open for voting for at least 12 hours and has a number of FOR Votes that exceed or equal Quorum.
It has been open for voting for at least 24 hours, it has more than 1 valid Vote cast on it, and more valid Votes cast on it are FOR than are AGAINST.
It has been open for voting for at least 6 hours, has a number of FOR Votes that exceed or equal Quorum, and has no AGAINST votes.
Any pending Deliberation may be failed by any Admin, if any of the following are true:
It could not be Enacted without either one of the Votes AGAINST it being changed, or the set of Scribe being changed, or by awaiting the passage of time.
It has been open for voting for at least 48 hours and cannot be Enacted.
Its target Proposal or Deliberation has been resolved.
When a Deliberation enacts, the enacting Admin shall update its target Votable Matter (if it’s still pending) to reflect the changes specified in that Deliberation.
If a Deliberation includes the word “CRUCIAL” (all caps), then its target Proposal or Deliberation cannot be failed until it has been pending for at least 48+F-A hours, where F is the number of FOR votes on the Deliberation and A is the number of AGAINST votes on the Deliberation, if F-A > 0.

Not mine, but I would like to see more of this.

Comments

RaichuKFM: she/her

11-08-2016 01:13:15 UTC

Note: “Re-enact"ing a Rule is of unclear meaning; I’d just edit this proposal to add a new rule to the ruleset, that has the text of Deliberations, already altered to read Hunter(s) instead of Scribe(s), outright.

Matt:

11-08-2016 01:19:46 UTC

imperial

Sci_Guy12:

11-08-2016 01:20:39 UTC

:Boom. Also, I started writing before Matt voted, so this is not illegal. I think.

Aft3rwards:

11-08-2016 01:22:07 UTC

imperial

RaichuKFM: she/her

11-08-2016 01:25:59 UTC

It’s illegal, if the comment was posted before the edit was made, whenever you started writing.

I checked the revision history, however, and the edit time wasn’t given seconds, and they seem to be at the same minute; of course, that’s possibly EE being dumb about timestamps?

Larrytheturtle:

11-08-2016 01:27:02 UTC

It is by when you posted the edit, not when you started typing. The revision is time stamped at 1:19 and the comment is 1:19:46. I don’t think there is a way to tell the second on revisions so the legality is impossible to prove one way or the other?

Larrytheturtle:

11-08-2016 01:27:43 UTC

And Raichu beat me to it, well point stands.

Clucky: he/him

11-08-2016 01:36:23 UTC

against

this rule was fine when procedural mechanisms were the core mechanic of the dynasty (or when ‘hodgepodge of old stuff’ was a core mechanic of the dynasty), but there is a reason this rule isn’t part of the core rules

Larrytheturtle:

11-08-2016 01:43:05 UTC

For the record, I support this being in the core rules. Would rather see it added there then as a dynastic rule.

RaichuKFM: she/her

11-08-2016 01:49:39 UTC

As the last Dynasty showed, Notes kinda cannibalized fix Deliberations; with Deliberations only used when Notes: failed, for some reason.

They both have their own flaws; Notes can ward off early voting, which can be Bad, while Deliberations lead to a certain kind of shenanigans that doesn’t fit in every Dynasty.

I’m going to have an explicit abstention. imperial

Sci_Guy12:

11-08-2016 01:51:20 UTC

for

Clucky: he/him

11-08-2016 02:02:15 UTC

If a proposal is flawed, people should just vote it down. This creates scenarios where you can’t vote for a proposal you like because a deliberation you dislike could negatively affect it.

It can make fun game play, sure, but it doesn’t make good core game play

Sci_Guy12:

11-08-2016 02:10:14 UTC

Think about it though. Wouldn’t the same be said for a preposal that had mostly good parts, but one bad? AND, dliberations could solve that. From my point of view, we would be trading a small amount of risk for a large amount of corrective power.

Clucky: he/him

11-08-2016 02:44:39 UTC

Deliberations don’t solve that though. Because proposals can still pass while a deliberation is pending, you can’t vote FOR a bad proposal that is fixed by a deliberation until the deliberation passes.

If a proposal is good minus a few parts, just propose it a second time. Blognomic doesn’t move fast enough that the increased time it takes to get your proposal passed is a big deal. A little patience solves this problem much better

Clucky: he/him

11-08-2016 02:56:43 UTC

Also: Deliberations allow you to bypass the proposal queue. Which is generally not a good idea.

Were this a rule, someone could say, add a deliberation on Ships in the Night that changes the name of “Barque” to “Frigate”. If that deliberation passes, suddenly Aft3rwards’s proposal doesn’t work.

(even if he writes “If there is a sub rule called ‘Barque’ append ‘Speed: 3’”, the deliberation would still break the rule because Frigate would have no speed)

Not having to future proof your proposals against stuff that hasn’t been written yet is incredibly important.

Kevan: he/him

11-08-2016 08:56:27 UTC

against Per Clucky.

Sci_Guy12:

11-08-2016 12:11:17 UTC

against  point.

qwertyu63:

11-08-2016 12:48:25 UTC

against

Matt:

11-08-2016 13:06:12 UTC

against I’ve been convinced.