MarioWiki:Proposals

Proposals can be new features (such as an extension), removal of a previously added feature that has tired out, or new policies that must be approved via consensus before any action(s) are done. Any user can support or oppose, but must have a strong reason for doing so, not, e.g., "I like this idea!" "Vote" periods last for one week. All past proposals are archived.

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 {{User|User name}}.

This page observes the No-Signature Policy.

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 start to discuss on the issue. 24 hours after posting the proposal (rounding up or down to the next or previous full hour, respectively, is allowed), the voting period begins. (The proposer is allowed to support their proposal right after posting.) Each proposal ends at the end of the day one week after voting start. (All times GMT).
3. Every vote should have a reason accompanying it. Agreeing or seconding a previously mentioned reason given by another user is accepted.
4. Users who feel that certain votes were cast in bad faith or which truly have no merit can address the votes in the Comments section. Users can ask a voter to clarify their position, point out mistakes or flaws in their arguments, or call for the outright removal of the vote if it lacks sufficient reasoning. Users may not remove or alter the content of anyone else's votes. The voter can remove or rewrite their own vote at any time, but the final decision to remove another User's vote lies solely with the Administrators.
5. All proposals that end up in a tie will be extended for another week.
6. If a proposal has more than ten votes, it can only pass or fail by a margin of three votes. If a proposal reaches the deadline and the total number of votes for each option differ by two or less votes, the deadline will be extended for another week.
7. 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.
8. No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
9. Proposals can only be rewritten or deleted by their proposer within the first three days of their creation. However, the proposer can request that their proposal be deleted by a Sysop at any time, provided they have a valid reason for it.
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. There shouldn't be proposals about creating articles on an underrepresented or completely absent subject, unless there is major disagreement about whether the content should be included. To organize efforts about completing articles on missing subjects, try creating a PipeProject.
12. Proposals cannot be made about Sysop promotions and demotions. Sysops can only be promoted and demoted by the will of Bureaucrats.
13. If the Sysops deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to remove it at any time.
14. No joke proposals. Proposals are serious wiki matters, and should be handled professionally. Joke proposals will be deleted on sight.

The times are in GMT, 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 Monday night at 23:59 GMT, the deadline is the night of the Tuesday of the next week at 23:59 PM. If it is posted a minute later, the deadline is 23:59 PM of the Wednesday of the next week, since midnight is considered to be part of the next day, as 00:00 AM.

Basic Proposal and Support/Oppose Format

This is an example of what your proposal should look like, if you want it to be acknowledged. If you are inexperienced or unsure how to set up this format, simply copy the following and paste it into the fitting section. Then replace the [subject] - variables with information to customize your proposal, so it says what you wish. If you insert the information, be sure to replace the whole variable including the squared brackets, so "[insert info here]" becomes "This is the inserted information", not "[This is the inserted information]".

---

===[insert a title for your Proposal here]===
[describe what issue this Proposal is about and what changes you think should be made to improve how the Wiki handles that issue]

'''Proposer''': {{User|[enter your username here]}}<br>
'''Voting start''': [insert a voting start time here, f.e. "January 1, 2010, 14:00". Voting start times are 24 hours after the time at which the proposal was posted, as described in Rule 2 above.]<br>
'''Deadline''': [insert a deadline here, 7 days after the voting start, at 23:59 GMT.]

====Support====
#{{User|[enter your username here]}} [make a statement indicating that you support your proposal]

====Oppose====

====Comments====

---

Users will now be able to vote on your Proposal, until the set deadline is reached. Remember, you are a user as well, so you can vote on your own Proposal just like the others.

To support, or oppose, just insert "#{{User|[add your username here]}} at the bottom of the section of your choice. Just don't forget to add a valid reason for your vote behind that tag if you are voting on another user's Proposal. If you are voting on your own Proposal, you can just say "Per my Proposal".

Talk Page Proposals

All proposals dealing with a single article or a specific group of articles are held on the talk page of one of the articles in question. Proposals dealing with massive amounts of splits, merges or deletions across the Wiki should still be held on this page.

How To

1. All active talk page proposals must be listed below in chronological order (new proposals go at the bottom). All pages affected must be mentioned in the brief description, with the talk page housing the discussion linked to directly via "(Template:Fakelink)". If the proposal involved a page that is not yet made, use {{fakelink}} to communicate its title. The Deadline must also be included in the entry. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links. Place {{TPP}} under the heading.
2. All rules for talk page proposals are the same as mainspace proposals (see the "How To" section above), with the exceptions made by Rules 3 and 4 as follows:
3. Voting in talk page proposals will be open for two weeks, not one. There is no 24 hour delay between the posting of a talk page proposal and the commencement of voting.
4. Talk page proposals may be closed by the proposer if both the support and the oppose sides each have fewer than five votes.
5. The talk page proposal must pertain to the article it is posted on.

List of Talk Page Proposals

• Merge Giant Kirby to Kirby (Discuss) Passed
• Merge Template:Fakelink to Bowser (Discuss) Passed
• Merge Mt. Molten with Melty Molten Galaxy (Discuss) Deadline: March 11, 2011 23:59 GMT
• Change the title of Piranha Plant in the Generator to Template:Fakelink (Discuss) Deadline: March 13, 2011, 23:59 GMT
• Split Behemoth King from Behemoth (Discuss) Deadline: March 13, 2011 23:59 GMT
• Merge Ultimate Chimera with New Pork City (Discuss) Deadline: March 13, 2011 23:59 GMT
• Merge Trampoline into Spring and use the "Springboard" title instead. (Discuss) Deadline: March 14, 2011, 23:59 GMT
• Split Ridley into Ridley and Meta Ridley (Discuss) Deadline: March 3, 2011, 23:59 GMT Extended: March 10, 2011, 23:59 GMT, March 17, 2011, 23:59 GMT

New Features

None at the moment

Removals

None at the moment

Changes

Make second to last warnings, only warnings and state the reason a last warning was issued

I think this Wiki should have these three. A second-to-last warning would look like this.

This is a warning to stop your inappropriate behavior (reason put here). The next time you do this, a last warning will be issued.

An only warning would look like this. They are given out when it is your first and last warning.

This is your only warning to stop your inappropriate behavior (reason put here). The next time you do this, you will be blocked from editing this site.

The last warning should look like this (I assume you get one for insulting other users)

This is your last warning. The next time you insult other users, you will be blocked from editing this site.

Proposer: DK and Diddy Kong vs Bowser and Bowser Jr.
Voting start: March 6, 2011 13:00 GMT
Deadline: March 13, 2011 23:59 GMT

Support

1. DK and Diddy Kong vs Bowser and Bowser Jr. (talk) I'm looking at this

Oppose

1. Edofenrir (talk) - The system is actually pretty easy to grasp. You get a reminder for very minor offenses, as well as possibly unintentional ones. You get a warning for any solid offense or repeated rule infractions. A last warning is what you get if you're a really notorious rule breaker and you keep ignoring policies. You can get banned if you either keep stacking up warnings or do something extremely idiotic, like blanking/spamming pages, uploading profane material, blackmailing, etc., the duration of the ban depending on the severity of the offense. It's a fairly simple system once you get behind it, and it doesn't need to be made more complicated. Moderating is no automatized process, you know.
2. Walkazo (talk) - As Edo said, the system is fine the way it is. Two new warning templates would be unnecessarily complicated: the system's already flexible enough. And like I said in the comments, if we wanted to make it more explicitly within regulations to give one warning and then block someone for certain types of infractions, we'd just add that to the policy pages.
3. Marioguy1 (talk) - I'm going to make a reference to baseball here; three strikes and you're out (...if it was gonna be a deep reference I would have said "metaphor"). We don't need a redundant fourth and fifth strike to know that this guy can't play the game properly.
4. MrConcreteDonkey (talk) - Per all. The current system is much better.
5. Bowser's luma (talk) If a proposal to fix a currently good system takes two tries just to understand, we say no in a fashion similar to this.
6. Fawfulfury65 (talk) Per all.
7. Reversinator (talk) Per all.
8. Bop1996 (talk) Per the fact that it makes the sysop's already laborious job harder.
9. DKPetey99 (talk) Per all and it kind of discards Sysops' jobs.
10. Phoenix (talk) I just don't think it's necessary...
11. BabyLuigiOnFire (talk) I wouldn't fix something that isn't broken, and this system is definitely not broken. The current one is particularly easy to grasp and the proposer's system takes me two read-throughs for me to understand. I find it completely unnecessary; the system is fine the way it is.
12. LeftyGreenMario (talk) The only thing flawed about this system is how vague the last reminder is.
13. TheBreakshift (talk) Per Walkazo.

Comments

A second to last warning already exists (the last warning) and we could just use {{lastwarn}} to give them an only warning. Fawfulfury65 (talk)

Okay, I'm confused; currently, it goes: reminder --> warning --> lastwarn --> block, right? So in your proposal, are you suggesting that we keep that the way it is, and then implement "only warnings" in place of reminders, warnings, and last warnings, leading directly to a block after, or are you saying that it should become: reminder --> warning --> last warning or only warning --> block, or do you want only warnings to be a completely separate entity from the normal cycle, to be used only in extreme situations...or am I just drastically overthinking this...? Phoenix (talk) 12:55, 5 March 2011 (EST)

What I'm thinking he wants = reminder > warning > sec-to-last warning > last warning > block, or only warning > block. That means either adding an extra warning, or skipping one (and reminder), depending on the situation and user (so, what the user does). Arend (talk)

Also, He may want to add a reasons thing to the Last Warning template, just like the reminder and normal warning Arend (talk)

I like the idea of only having to give out one warning for certain offences (i.e. making spam-ish edits, or other probable cases of vandalism), but I think it'd be better to just add provisions for admins to do so on the appropriate policy pages (i.e. MarioWiki:Blocking Policy), rather than confusing the issue with a whole different template. Plus, outlining exactly what offences are "one strike and you're out" situations on the policy pages will safeguard against the Only Warning template from being misused. I also think a second-to-last template is unnecessary: three chances is enough (and besides, people often get more than that, between multiple warnings for slightly different offences and informal reminders before the templates are broken out at all; all things considered, we hardly need to be more lenient). - Walkazo (talk)

Well, honestly, I really don't think we need a second-to-last warning in between a warning and a last warning, I mean, by this point, the user must obviously realize they've done something wrong, and if its gotten to this point there's really no need to sugar coat it, so why not just cut out the middle man and leave it the way it is...? Phoenix (talk) 23:17, 5 March 2011 (EST)

Miscellaneous

None at the moment