Monday, February 23, 2015

Proposal: Proposal Management

Self-killed. -RaichuKFM

Adminned at 24 Feb 2015 05:01:09 UTC

Add a new rule called “Proposal Management” which contains

If a proposal relies on a proposal that is has not been enacted then it must mention the proposal it changes or amends. (ex. If Proposal A changes something in Proposal B then Proposal must state “this proposal relies on Proposal B”)
If the required proposal is vetoed or self-killed then the dependent proposal is failed by an admin

 

I’m in the middle of writing something that may depend on this rule, and realized that their may be a conflict if the amendment is enacted but the proposal it changes is not. This hopefully provides actions that the mod can take in this event (which should happen that often, I think.)

posted by Maldor at 23 Feb 2015 23:18:00 UTC Comments (5)

Comments

Bucky:

23-02-2015 23:56:43 UTC

I think it’s a good idea to formalize dependency.  But I don’t think the appropriate response to a dependency that isn’t noticed is to immediately render it illegal.

Also, proposals rarely change other proposals, rather than the rules another proposal creates.

against

Maldor: he/him

24-02-2015 00:49:45 UTC

This proposal is mostly for adding on to proposals that have a base set of rules. One example would be a market with fixed prices, but another proposal would change it to have fluctuating prices. This would help in cases of proposal linking where three proposals depend on a single proposal and rather than having a full pending proposal queue and each proposal would voted upon even though the base proposal has been vetoed or self-killed.
That was my aproximate thinking on the subject.

RaichuKFM: she/her

24-02-2015 04:09:02 UTC

against In favor of Bucky’s Proposal.

_Fox_:

24-02-2015 04:16:06 UTC

against

Maldor: he/him

24-02-2015 04:19:54 UTC

Bucky explains it better then I did
Self kill against