Proposals can be new features, the removal of previously-added features that have tired out, or new policies that must be approved via consensus before any action is taken.
Voting periods last for two weeks, but can close early or be extended (see below).
Any autoconfirmed user can support or oppose, but must have a strong reason for doing so.
All proposals must be approved by a majority of voters, including proposals with more than two options.
If you would like to get feedback on an idea before formally proposing it here, you may do so on the proposals talk. For talk page proposals, you can discuss the changes on the talk page itself before creating the TPP there.
If someone has an idea about improving the wiki or managing its community, but feel that they need community approval before acting upon that idea, they may make a proposal about it. They must have a strong argument supporting their idea and be willing to discuss it in detail with other users, who will then vote on whether or not they think the idea should be implemented. Proposals should include links to all relevant pages and writing guidelines. Proposals must include a link to the draft page. Any pages that would be largely affected by the proposal should be marked with {{proposal notice}}.
Rules
Only autoconfirmed users may create or vote on proposals. Proposals can be created by one user or co-authored by two users.
Anyone is free to comment on proposals (provided that the page's protection level allows them to edit).
Proposals conclude at the end of the day (23:59) two weeks after voting starts (all times GMT).
For example, if a proposal is added at any time on Monday, August 1, 2011, the voting starts immediately and the deadline is two weeks later on Monday, August 15, at 23:59 GMT.
Users may vote for more than one option, but they may not vote for every option available.
Every vote should have a strong, sensible reason accompanying it. Agreeing with a previously mentioned reason given by another user is acceptable (including "per" votes), but tangential comments, heavy sarcasm, and other misleading or irrelevant quips are just as invalid as providing no reason at all.
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. Voters can remove or rewrite their own vote(s) at any time, but the final decision to remove another user's vote lies solely with the wiki staff.
Users can also use the comments section to bring up any concerns or mistakes in regards to the proposal itself. In such cases, it's important the proposer addresses any concerns raised as soon as possible. Even if the supporting side might be winning by a wide margin, that should be no reason for such questions to be left unanswered. They may point out any missing details that might have been overlooked by the proposer, so it's a good idea as the proposer to check them frequently to achieve the most accurate outcome possible.
If a user makes a vote and is subsequently blocked for any amount of time, their vote is removed. However, if the block ends before the proposal ends, then the user in question holds the right to re-cast their vote. If a proposer is blocked, their vote is removed and "(blocked)" is added next to their name in the "Proposer:" line of the proposal, which runs until its deadline as normal. If the proposal passes, it falls to the supporters of the idea to enact any changes in a timely manner.
Proposals cannot contradict an already ongoing proposal or overturn the decision of a previous proposal that concluded less than four weeks (28 days) ago.
If one week before a proposal's initial deadline, the first place option is ahead of the second place option by eight or more votes and the first place option has at least 80% approval, then the proposal concludes early. Wiki staff may tag a proposal with "Do not close early" at any time to prevent an early close, if needed.
Tag the proposal with {{early notice}} if it is on track for an early close. Use {{proposal check|early=yes}} to perform the check.
Any proposal where none of the options have at least four votes will be extended for another week. If after three extensions, no options have at least four votes, the proposal will be listed as "NO QUORUM." The original proposer then has the option to relist said proposal to generate more discussion.
If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
If a proposal reaches its deadline and the first place option is ahead of the second place option by three or more votes, then the first place option must have over 50% approval to win. If the margin is only one or two votes, then the first place option must have at least 60% approval to win. If the required approval threshold is not met, then the proposal is extended for another week.
Use {{proposal check}} to automate this calculation; see the template page for usage instructions and examples.
Proposals can be extended a maximum of three times. If a consensus has not been reached by the fourth deadline, then the proposal fails and cannot be re-proposed until at least four weeks after the last deadline.
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 an administrator, the proposer can ask for that help.
After a proposal passes, it is added to the appropriate list of "unimplemented proposals" below and is removed once it has been sufficiently implemented.
If the wiki staff deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to cancel it at any time.
Proposals can only be rewritten or canceled by their proposer within the first four days of their creation. However, proposers can request that their proposal be canceled by a staff member at any time, provided they have a valid reason for it. Please note that canceled proposals must also be archived.
Unless there is major disagreement about whether certain content should be included, there should not be proposals about creating, expanding, rewriting, or otherwise fixing up pages. To organize efforts about improving articles on neglected or completely missing subjects, try setting up a collaboration thread on the forums.
Proposals cannot be made about promotions and demotions. Staff changes are discussed internally and handled by the bureaucrats.
No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.
Basic proposal formatting
Copy and paste the formatting below to get started; your username and the proposal deadline will automatically be substituted when you save the page. Update the bracketed variables with actual information, and be sure to replace the whole variable including the square brackets, so "[insert info here]" becomes "This is the inserted information" and not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but the objective(s) of each voting option must be clearly defined. Such options should also be kept to a minimum, and if something comes up in the comments, the proposal can be amended as necessary.
===[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|{{subst:REVISIONUSER}}}}<br>
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT
====[option title (e.g. Support, Option 1)]: [brief summary of option]====
#{{User|{{subst:REVISIONUSER}}}} Per proposal.
====[option title (e.g. Oppose, Option 2)]: [brief summary of option]====
====Comments ([brief proposal title])====
Autoconfirmed users will now be able to vote on your proposal. Remember that you can vote on your own proposal just like the others.
To vote for an option, just insert #{{User|[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 simply say "Per proposal."
Poll proposal formatting
As an alternative to the basic proposal format, users may choose to create a poll proposal when one larger issue can be broken down into multiple sub-issues that can be resolved independently of each other. In a poll proposal, each option is essentially its own mini-proposal with a deadline and Support/Oppose subheadings. The rules above apply to each option as if it were a its a two-option proposal: users may vote Support or Oppose on any number of options they wish, and individual options may close early or be extended separately from the rest. If an option fails to achieve quorum or reach a consensus after three extensions, then the status quo wins for that option by default. If all options fail, then nothing will be done.
To create a poll proposal, copy and paste the formatting below to get started; your username and the option deadlines will automatically be substituted when you save the page. Update the bracketed variables with actual information, and be sure to replace the whole variable including the square brackets, so "[insert info here]" becomes "This is the inserted information" and 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|{{subst:REVISIONUSER}}}}
====[option title (e.g. Option 1)]: [brief summary of option]====
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT
;Support
#{{User|{{subst:REVISIONUSER}}}} Per proposal.
;Oppose
====[option title (e.g. Option 2)]: [brief summary of option]====
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT
;Support
#{{User|{{subst:REVISIONUSER}}}} Per proposal.
;Oppose
====[option title (e.g. Option 3)]: [brief summary of option]====
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT
;Support
#{{User|{{subst:REVISIONUSER}}}} Per proposal.
;Oppose
====Comments ([brief proposal title])====
For the purposes of the ongoing proposals list, a poll proposal's deadline is the latest deadline of any ongoing option(s). A poll proposal is archived after all of its options have settled, and it is listed as one single proposal in the archive. It is considered to have "passed" if one or more options were approved by voters (resulting in a change from the status quo), and it is considered to have "failed" if all options were rejected by voters and no change in the status quo was made.
Talk page proposals
Proposals concerning a single page or a limited group of pages are held on the most relevant talk page regarding the matter. All of the above proposal rules also apply to talk page proposals. Place {{TPP}} under the section's heading, and once the proposal is over, replace the template with {{settled TPP}}. Proposals dealing with a large amount of splits, merges, or deletions across the wiki should still be held on this page.
All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{ongoing TPP}}. Include a brief description of the proposal while also mentioning any pages affected by it, a link to the talk page housing the discussion, and the deadline. If the proposal involves a page that is not yet made, use {{fake link}} to communicate its title in the description. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links.
List of ongoing talk page proposals
Properly define Brown Yoshi (discuss) Deadline: March 27, 2025, 23:59 GMT
Split Pokeynut from Big Pokey (discuss) Deadline: April 1, 2025, 23:59 GMT
Split Pipe Cannon from Bill Blaster (discuss) Deadline: April 1, 2025, 23:59 GMT
Split Piscatory Pete from Cheep Cheep (discuss) Deadline: April 1, 2025, 23:59 GMT
Split Super Luigi subjects into a dedicated list article (discuss) Deadline: April 3, 2025, 23:59 GMT
Rename Papa Mario to a generic title (e.g. "Mario's father") and refocus the article to talk about the overall concept of the character as opposed to a single established being (discuss) Deadline: April 4, 2025, 23:59 GMT
Split Kongo Bongo Island and the Jungle Kingdom from Donkey Kong Island (discuss) Deadline: April 6, 2025, 23:59 GMT
Deciding the fate of the "lost" Mario arcade machines (discuss) Deadline: April 6, 2025, 23:59 GMT
I put forward this proposal to determine a minimum number of glitches for the creation of "List of glitches" articles. That way, there is consistency between games with the same number of documented glitches. Additionally, if new glitches are documented later that brings the total number over this minimum, a new page can easily be created without the need for a proposal, as the editor can cite this proposal.
Option 1
The minimum number of glitches should be 3. "List of glitches" pages would be created for Mario vs. Donkey Kong, Paper Mario: The Thousand-Year Door (Nintendo Switch), and Wario Land 3 to match that of Wario Land 4.
Option 2
The minimum number of glitches should be 4. List of Wario Land 4 glitches would be deleted and its glitches merged into the main game's article. "List of glitches" pages would be created for Super Mario World: Super Mario Advance 2, Donkey Kong Country: Tropical Freeze, Donkey Kong Land, and Mario + Rabbids Kingdom Battle.
There should be no concrete minimum, and whether glitches should be split or not should be discussed on a game-by-game basis.
I could continue with 6, 7, etc., but I feel once this point is reached there is enough to warrant separate "List of glitches" articles, especially since game articles are typically long and images are usually needed to showcase glitches, taking up more space.
Proposer: Technetium (talk) Deadline: August 29, 2024, 23:59 GMT
Technetium (talk) First choice. I am a bit torn between Options 2 and 3, but I prefer this one as I feel 4 glitches can easily fit on a game's page, as seen with the examples above.
Do nothing
Comments
From what I can tell, articles on this wiki are usually split based on size, not the number of headings. It's why List of Fortune Street quotes is split into Dragon Quest characters (A-J / K-Z) and Super Mario characters (A-M / N-Z) and why the number of headings in these articles is inconsistent. I think it'd be weird to split lists of glitches based strictly on the number of sections rather than the amount of text since that could lead to very short articles that only list a few very minor glitches that can be described in just a few sentences. DiveRocketLauncher 22:50, August 15, 2024 (EDT)
Yeah, I'm aware of that. It just feels different here because glitch descriptions tend to be around the same length. If you look at the examples I discussed in the proposal, you'll find there really isn't a noticeable size difference between the pages that have their glitches merged vs separate. Truth be told, I was originally going to just make a talk page proposal to merge List of Wario Land 4 glitches, but the discrepancies with the pages with 4 glitches led to me coming up with this. I'd be happy to hear anyone else's ideas on how to make things more consistent, because the way things are currently is frankly bugging me. --Technetium (talk) 23:02, August 15, 2024 (EDT)
New features
None at the moment.
Removals
None at the moment.
Changes
Shorten disambiguation identifiers "(Super) Nintendo Entertainment System" to "(S)NES"
The console names "Nintendo Entertainment System" and "Super Nintendo Entertainment System" are way too long and clunky, so much so that the abbreviations "NES" and "SNES" are commonly used in the body of articles throughout the wiki, even though we usually don't use abbreviations. And yet, we still use the full console names in the disambiguation identifiers of article names:
The identifiers are so long that they take up more than half of the article name and are less immediately legible than their respective abbreviations. This is particularly jarring on the Mario is Missing! disambiguation page because the abbreviations are used on the page (e.g., "Mario is Missing!, the NES game") but it links to articles with names containing the full console names ("Mario is Missing! (Nintendo Entertainment System)").
That's why I propose to shorten "Nintendo Entertainment System" and "Super Nintendo Entertainment System" to "NES" and "SNES" respectively in disambiguation identifiers of article names:
Mario is Missing! (NES)
Mario is Missing! (SNES)
Wario's Woods (NES)
Wario's Woods (SNES)
Please note that there is already an article which uses an abbreviated identifier: "Building World (Mario's Early Years! Fun with Letters for SNES)", although if we decide to keep the full identifiers, maybe we should rename it to "Building World (Mario's Early Years! Fun with Letters for Super Nintendo Entertainment System)" for consistency?
Proposer: Jdtendo (talk) Deadline: August 20, 2024, 23:59 GMT
Hewer (talk) I don't see much of a problem with long names, and I'd rather go without the inconsistency created by these being the only shortened console names. And yes, I suppose we should move the Building World page too, like how "Beach Volleyball (Mario & Sonic at the London 2012 Olympic Games for 3DS)" got moved to "Beach Volleyball (Mario & Sonic at the London 2012 Olympic Games for Nintendo 3DS)".
Camwoodstock (talk) Per Hewer. While these shortened versions do make for fine redirects (and honestly, I kinda hope these do get made for other games in the form of redirects, but that's neither here nor there), we probably shouldn't be enforcing these as being the default name unless it's a part of a global move to abbreviate the console names for the articles of every game--not just one random edutainment game.
Comments (Mario's Early Years! Fun with Letters for SNES)
now there's a bit of a grey area here, what about consoles like Nintendo 64, Nintendo Switch and so on? It'd feel somewhat weird to abbreviate one but not the others, there'd be an inconsistency. - YoYo (Talk) 09:33, August 13, 2024 (EDT)
The thing with those is that the "Nintendo" part is needed or else it could just be confused as a random number (64) or word (switch). They also just aren't as long. Technetium (talk) 09:57, August 13, 2024 (EDT)
Besides, as I said in the proposal, the abbreviations "NES" and "SNES" are commonly used in the body of articles, but other console names are not abbreviated as frequently. For example, here is an extract of the LodgeNet article: "for the SNES, Nintendo 64, and Nintendo GameCube"; note how only the Super Nintendo Entertainment System's name is abbreviated whereas the other console names are written in full. Jdtendo(T|C) 10:09, August 13, 2024 (EDT)
I think the shortening of N64, GCN, GBA, etc. could use another propasal. SeanWheeler (talk) 21:30, August 13, 2024 (EDT)
...Not to burst your bubble, but we actually had a proposal to move it to its current name last month. Prior to that, the article was merely titled "The Old Psychic Lady", which from what I can tell was actually never actually used like that in the episode. She introduced herself by the full title of "The Old Psychic Lady with the Evil Eye Who Reads Fortunes and Knows Everything Before It Happens" (whether it used capital letters or not is unknown), and the Marios simply refer her to as the "crazy lady" or "that psycho lady" since they can't properly remember such a long name. Since "The Old Psychic Lady" never was used as one of the official names, and the wiki refers to her by her full name anyway, it was proposed to move the article to the lady's full title (I mean, at least "NES" and "SNES" are officially used abbreviations by Nintendo themselves and their full names were not created for comedic purposes). rend(talk)(edits) 20:50, August 14, 2024 (EDT)
Arguments about the name being "ridiculous" or "too long" were used in the proposal linked to by Arend, and much like with those arguments, you haven't substantiated the claim very well. Why is a long page name "ridiculous" when it's just accurately referring to the subject? Why should we sacrifice accuracy in favour of a shorter page name? What about long page names is in any way disadvantageous? Hewer (talk · contributions · edit count) 05:37, August 15, 2024 (EDT)
Tbh, I'd merge the two Building Worlds together if it were up to me, they're still both represented by the same icon in the map screen and differences can easily be mentioned in the article, it'd also be consistent with the rest of the Mario's Early Years Worlds. Ray Trace(T|C) 20:09, August 15, 2024 (EDT)
Dive Rocket Launcher 22:50, August 15, 2024 (EDT)
(Talk) 09:33, August 13, 2024 (EDT)
rend (talk) (edits) 20:50, August 14, 2024 (EDT)
Ray Trace(T|C) 20:09, August 15, 2024 (EDT)
