Wednesday, May 22, 2019

Proposal: Bidding on a Queue x2

popular 4 to 0. Enacted by Derrick.

Adminned at 22 May 2019 19:48:43 UTC

If this proposal passes, the proposal “Ready Surveyor One” has no effect. If it has already passed, its changes are retroactively removed.

Add a new subrule to the rule drops called “Bidding Queue” with the text:-

The Bidding Queue is a comma separated list of the names of all active Architects, stored at the top of the wiki page “Moon Sites”. When an Architect joins or unidles, their name is appended to the end of the Bidding Queue.

Also, replace “If no Drop post exists, any Architect (or the Supervisor) may make a blog post” with:-

If no Drop post exists, the Architect who’s name is first in the Bidding Queue (or the Supervisor) may make a blog post”

Add after the sentence “Such a blog post is known as a Drop post.” the following:-

Whenever an Architect makes a drop post, they must move their name to the end of the Bidding Queue.

When this proposal passes, the Admin who

Comments

card:

22-05-2019 02:51:49 UTC

What do the admins do?

Axemabaro:

22-05-2019 02:55:00 UTC

They should initialize the Bidding Queue.

Farsight:

22-05-2019 05:16:07 UTC

[Axemabaro] Just to be clear, there is no mechanism to alter the queue order in this proposal? (like in the previous “Bidding on a Queue” proposal?)

Kevan: he/him

22-05-2019 08:18:13 UTC

for Good solution.

I think it works even with that unfinished admin instruction: per the appendix, the list of names will default to alphabetical if no order is specified.

Axemabaro:

22-05-2019 13:33:49 UTC

[Farsight] That’s right, but it’s because a list is much more easy to manipulate than the other thing, without messing it up.

derrick: he/him

22-05-2019 18:50:41 UTC

for

naught:

22-05-2019 19:45:02 UTC

for