MarioWiki:Proposals

 http://img33.picoodle.com/img/img33/9/9/17/f_propcopym_9045f2d.png A proposal section works like a discussion page: comments are brought up and replied to using indents (colons, such as : or ::::) and all edits are signed using the code. Signing with the signature code (~) is not allowed due to technical issues.

How To
 * 1) Actions that users feel are appropriate to have community approval first can be added by anyone, but they must have a strong argument.
 * 2) Users then vote and discuss on the issue during that week. The "deadline" for the proposal is one week from posting at:
 * 3) Monday to Thursday: 17:00 (5pm)
 * 4) Friday and Saturday: 20:00 (8pm)
 * 5) Sunday: 15:00 (3pm)
 * 6) Every vote should have a reason accompanying it.
 * 7) At any time a vote may be rejected if at least three active users believe the vote truly has no merit or was cast in bad faith. However, there must be strong reasons supporting the invalidation.
 * 8) " # " should be added under the last vote of each support/oppose section to show another blank line.
 * 9) Any proposal that has three votes or less at deadline will automatically be listed as "NO QUORUM." The original proposer then has the option to relist said proposal to generate more discussion.
 * 10) All proposals are archived. The original proposer must take action accordingly if the outcome of the proposal dictates it. If it requires the help of a sysop, the proposer can ask for that help.
 * 11) Proposals can not be made about System Operator promotions and demotions. Sysops can only be promoted and demoted by the will of Bureaucrats.

The times are in EDT, and are set so that the user is more likely to be online at those times (after work/school, weekend nights). If a proposal is added on Saturday night at 11:59 PM EDT, the deadline is the next Saturday night at 8:00 PM. If it is a minute later, the deadline is a day plus 15 hours (Sunday), as opposed to a day minus 4 hours.

CURRENTLY: , 27 2024 (EST)

New Features
None at the moment.

The Partroller Rank.
Should we really restore this rank or get rid of it for good. Sor far this power has return but no user has done a proposal to restore it, Because we had a past proposal to get rid of the rank for certain reasons, and that proposal has won.

Proposer: Deadline: January 20, 2009, 17:00

Get rid

 * 1) I say we remove this rank. And I can think six reasons why. 1 You have to got to special edits then Patroll Edits just to revert something and that just takes to long if a vandal is on the loose. 2 When you are on Patroll edit it show one edit that a random user did which really suck (You can skip it be then it shows another user's edit). 3 You can't block trolls. 4 Patrollers can't even patroll pages. 5 You can't see the red ! like the sysop can. 6. Patrollers can't acess the Block IP special page. That's all I have to say.

Keep it

 * 1) It's actually really good if you think about it. It shows how a user handles more power. It also helps because it gives a user practice for being a sysop in case they become one. If the Sysops thought it was really useless, then they wouldn't have restored it.
 * 2) - Per my comment below.
 * 3) Per Toadette
 * 4) - Per all. Peachycakes: please sign with   .

Comments
This is my first proposal so I'am sorry if it looks bad.

It was removed in the past. But now the sysop and 'Crat are trying to bring it back.


 * I'm having trouble deciding. I think the rank would be useful given the chance to work correctly. However, there are currently too many technical difficulties. Convince me one way, please. PS: You did a fine job, Grapes. ;)

Thanks =3

For the record, there was a proposal a long time ago in which keeping the Patrollers won (see here). I tried to find the archive for the more recent proposal (late March, 2008) that vetoed the rank, but without success. Anyway, I don't even see the point of having Users vote on administrative decisions - like promotions and demotions, I think that should be left to the Administrators. Users have a say in Wiki content and the policies that concern them, but Patrollers will not change the content of the Wiki, nor is reestablishing them a change in Wiki policy. If the higher-ups think it's a good idea to bring back Patrollers, who are we to argue? -

Here's my take on the original Patroller status:
 * Patrollers are considered a step in between users and Sysops. They have the ability to use rollback, they have the ability to mark articles 'as patrolled', and they also have the ability to block vandals that are attacking the wiki. Basically, Patrollers are here to help out the Sysops protect the wiki and keep it clean. They're pretty much an 'assistant' to Sysops, as they have the ability to stop spam, but they have to look up to their superiors – Sysops and Bureaucrats – in order to delete and spam pages created. They also require Sysops to use checkuser to see if someone is a sockpuppet of a vandal or whatever. As such, Patrollers are not useless, and are in fact helpful to the wiki.
 * Patrollers are promoted based on activity and trust. Yes, we promote Sysops for the same reason, but users that are promoted to Patroller instead are promoted to that position for a reason. If we feel that a user has done good work on the wiki, is ready for a promotion, but isn't ready to get the full-blown Sysop package, then we give them Patroller powers. Once promoted to Patroller, they have a shot to get promoted to Sysop if they handle the job exceptionally well. Being a Patroller is the perfect trial period to see how a contributive user handles having more power under their belt. Should they take on the responsibility notably well, keep contributing as always, and manage their powers well, then they may get nominated for Sysop. Once again, this is only if they handle the job well. Wouldn't you rather us promote a user to Patroller, where power is increased but still limited, in order to see how they handle having more power, rather than giving them all of the privileges of a Sysop?

Now, I'm going to talk to Steve about giving Patrollers a more convenient way of using rollback, (through a page's history), and give them the ability to block users, just as they had before, it will be seen that Patrollers are more useful and can conveniently use their powers to help stop a problem.

Next, I'd like to note that the "Patroller Power!" proposal of March 2008 did not propose that we get rid of the Patroller position, but rather that we give them more power. I won't lie: I supported giving Patrollers more power back then; the reason why I did so was that Pokemon DP told me I was a nominee for Patroller. My vote was clearly biased, but I later found out that I was never a nominee for Patroller. The reason why the Patroller ranking was revoked was because it was proposed that Patrollers gain the ability to delete pages. With a discussion between the higher-ups, the Patroller ranking was removed because the proposal that passed &mdash; supporting Patrollers to be able to delete pages &mdash; pretty much stated that Patrollers have all the abilities of Sysops with the exception of checkuser and page protection.

Lastly, I find that decisions pertaining to promotions, demotions, and the insertion/removal of positions should be decided solely by the Administrative Staff &mdash; the Sysops and Bureaucrats, as Walkazo pointed out. Users should be more concerned with the encyclopedic aspect of the MarioWiki, not the Administrative aspect.

To Toadette: The Sysops didn't bring Patrolers back, Steve did, abruptly.

To all: Generally speaking, proposals that are on topics that are considered administrative (usergroups, policies, etc.) are removed, as administrative subjects should be discussed by the administrative team. However, since the community seems to clearly divided on the subject, I'm inclined to leave the proposal as is to see how things play out (if any other sysops disagree with this, please, do what you feel needs to be done). --

Splits & Merges
None at the moment.

Changes
None at the moment.

Miscellaneous
None at the moment.