Proposals can be new features (such as an extension), the removal of previously-added features that have tired out, or new policies that must be approved via consensus before any action is taken.
"Vote" periods last for one week.
Any user can support or oppose, but must have a strong reason for doing so (not, e.g., "I like this idea!").
All proposals must be approved by a majority of voters, including proposals with more than two options.
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}}.
How to
Rules
If users have 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 the other users, who will then vote about whether or not they think the idea should be used. 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}}.
Only registered, autoconfirmed users can create, comment in, or vote on proposals and talk page proposals. Users may vote for more than one option on proposals with more than two choices.
Proposals end at the end of the day (23:59) one week after voting starts, except for writing guidelines and talk page proposals, which run for two weeks (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 one week later on Monday, August 8, at 23:59 GMT.
Every vote should have a strong, sensible reason accompanying it. Agreeing with a previously mentioned reason given by another user is accepted (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 at any time, but the final decision to remove another user's vote lies solely with the administrators.
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 "(banned)" 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.
No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
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.
All proposals that end up in a tie will be extended for another week. Proposals with more than two options must also be extended another week if any single option does not have a majority support: i.e. more than half of the total number of voters must appear in a single voting option, rather than one option simply having more votes than the other options.
If a proposal with only two voting options has more than ten votes, it can only pass or fail by a margin of three votes, otherwise the deadline will be extended for another week as if no majority was reached at all.
Proposals can only be extended up to three times. If a consensus has not been reached by the fourth deadline, the proposal fails and can only be re-proposed after four weeks, at the earliest.
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.
If the administrators 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.
Proposals can only be rewritten or deleted by their proposer within the first three days of their creation (six days for talk page proposals). However, proposers can request that their proposal be deleted by an administrator 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. Users can only be promoted and demoted by the will of the administration.
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 and support/oppose format
This is an example of what your proposal must 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]". Proposals presenting multiple alternative courses of action can have more than two voting options, but what each voting section is supporting 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|[enter your username here]}}<br>
'''Deadline''': [insert a deadline here, 7 days after the proposal was created (14 for writing guidelines and talk page proposals), at 23:59 GMT, in the format: "May 2, 2024, 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".
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.
All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{TPPDiscuss}}. 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. Place {{TPP}} under the section's header, and once the proposal is over, replace the template with {{SettledTPP}}.
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:
Voting in talk page proposals will be open for two weeks, not one (all times GMT).
For example, if a proposal is added at any time on Monday, August 1, 2011, it ends two weeks later on Monday, August 15, 2011, at 23:59 GMT.
The talk page proposal must pertain to the article it is posted on.
When a talk page proposal passes, it should be removed from this list and included in the list under the "Unimplemented proposals" section until the proposed changes have been enacted.
List of ongoing talk page proposals
Delete all Super Smash Bros. challenges pages (discuss) Deadline:April 19, 2024, 23:59 GMTApril 26, 2024, 23:59 GMT May 3, 2024, 23:59 GMT
Consider Beanies and Octoombas to be related to Goombas rather than direct variants of them (for consistency with Galoomba et al.) (discuss) Deadline: May 10, 2024, 23:59 GMT
Split "Baby Fat" from Baby Yoshi (discuss) Deadline: May 10, 2024, 23:59 GMT
In Template:Species infobox, expand "Relatives" guidelines to include variant-type relationships with significant differences between species (discuss) Deadline: May 12, 2024, 23:59 GMT
Well, i saw a user who got warned because he/she ingored these templates. However, the templates don't say that a user can get a warning for ingoring them; and {{reminder}} has a setence: "If the action continues, than a warning will be issued", so i believe it's acceptable to put this in these two templates as well.
Here's what i want it to look like:
Hello, Proposals. Good job on your recent uploads. But when uploading files, keep in mind that you must correctly use the {{aboutfile}} template. What you were doing looks like this, and it is an inconvenience for other users to fix up the template. It is simple to learn how to format it correctly. The pre-loaded coding is shown below.
{{aboutfile
|1=Subject of the image
|2=Where you found the image
|3=Artist
|4=Describe edits, if any
|5=Other versions (use file link)
}}
Just replace the necessary parts with that corresponding information, and remove the entire line of the variable(s) you don't use. If you do not wish to use the template at all, then it is acceptable to simply remove it before you upload the file. Please consider the above information before uploading more files. If you continue using {{aboutfile}} incorrectly, then a warning will be issued. Thank you for reading, and keep contributing.
Hello, Proposals. Good job on your recent uploads. But when uploading files, keep in mind that you must correctly categorize the file. It is simple to learn how to correctly do so. Just search for the correct category by starting with the following groups:
When uploading, copy the full title of the category with square brackets, and insert it into the summary text box (below the {{aboutfile}} template), replacing the {{uncategorized}} template. For example, files related to the game Super Mario World would use:
[[Category:Super Mario World Images]]
or
[[Category:Super Mario World Media Files]]
Please consider the above information before uploading more files. Keep in mind some files can belong to multiple categories. Don't put images into media categories and vise-versa. If you continue uploading files without categorizing them correctly, then a warning will be issued. Thank you for reading, and keep contributing.
Proposer: YoshiEgg1990 (talk) Deadline: July 16, 2018, 23:59 GMT
TheFlameChomp (talk) Makes sense to me, since both are types of reminders. I have seen both warnings and reminders given out before, so it should help with consistency in what is received.
Mister Wu (talk) Definitely better to specify what are the consequences of ignoring the reminders.
Oppose
Comments
Perhaps {{warning}} can be linked to? 14:52, 13 July 2018 (EDT)
I doon't think so. The point of this is basiclly to let people know that they will get warned if they continue; i don't think it's necesary to say how excatly they will be warned. YoshiEgg1990 15:19, 13 July 2018 (EDT)
Change the way that recurring Mario & Sonic events are handled, round 2
After the no quorum result of the last attempt at this proposal, I've taken on board the comments from last time and changed the proposal to reflect this. So, at the moment, there's an issue in the way that events that appear in more than one of the Mario & Sonic games are handled, as events that share the same or similar names across games are all put together on the same article, despite the fact that they are very different between games, using different controls, scoring systems, characters, etc.. This isn't only a problem between Wii/Wii U and DS/3DS instalments, which would obviously and understandably have very different controls and slightly modified gameplay, but also between games on similar consoles, for example, the Trampoline event in the first DS game required certain patterns to be drawn with the stylus to perform various moves and the player to slide up with the stylus to jump, whereas in the 2012 3DS game moves are performed automatically and the player must use the circle pad to keep their character within a certain area, pressing the A button to jump. This means that infoboxes are overloaded with excessive information, defeating their purpose, and that the articles are a complete mess of headers and sections. 100m Dash and 100m Freestyle are examples of this, and please keep in mind that they still have a considerable amount of missing information, particularly from the later games. Part of the reason that all of the events are sharing one page seems to have apparently stemmed from the fact that they're currently being treated as generic subjects, which is not really how they should be viewed. They should be treated in a similar way to minigames, with each getting an individual article, even if they share a name, a few controls or subject that they're based on. Just because they're based on a real world subject, it doesn't mean that they should be covered like one (And any that currently have generic subject-like articles will be changed in the future, to give them more of a minigame-like focus, similar to 100m Breaststroke). Additionally, several Dream Events also share this issue (Including Dream Race, Dream Long Jump and Dream Bobsleigh), which are in no way affected by the generic subjects policy, and should be treated as separate minigames, but are currently all placed on the same page for being similar. These should also be split, in the same way as the regular events, as the two are treated as the same thing within the games.
Therefore, I'm proposing that we split each game's version of the event into its own unique article, which only covers the event's appearance in the one game. Only the controls, missions, playable characters, etc. for one game's version of the event would be included on that page, and an About template would be added to the top of name-sharing articles with a link to the disambiguation page for the other events or the events with a similar name. An identifier would be added to any articles with shared names, and I'm currently thinking that it would specify only the game if it only appears in one of the instalments for a specific year (Such as "Pole Vault (Mario & Sonic at the London 2012 Olympic games)", which appears in the 3DS version but not the Wii one), or both the game and console if it appears in more than one version (Such as "BMX (Mario & Sonic at the Rio 2016 Olympic Games (Nintendo 3DS))" and "BMX (Mario & Sonic at the Rio 2016 Olympic Games (Wii U))"). This is just how I think the identifiers would work from what I can piece together from here, but unfortunately, it's not really designed to help out in cases like this thanks to naming in the Mario & Sonic series, so any other suggestions for identifiers are more than welcome. Any shared names would be turned into disambiguation pages, listing all of the separate articles and any with similar names, such as 100m and 100m Dash. If an event has a slightly different name in one or more instalments, it will use that name instead of the similar one that all the other events are named after with an identifier, but will still have the about template and so on. Events such as Balance Beam that only appear in one game will not be affected by this and will remain at the one name.
So, in summary, each version of an event from each game is split and given game-specific identifiers (Or some other form of identifier if a better one is suggested), the shared title is turned into a disambiguation page and About templates are added, events with different names between versions go to the unique names and events that only appear once remain unchanged.
Proposer:BBQ Turtle (talk) Deadline: July 17, 2018, 23:59 GMT
@SeanWheeler: Yep, that's the plan, things like Archery (event) would be turned into disambiguation pages, and ones that already share a name like Football will be added onto the existing one. BBQ Turtle (talk) 05:25, 11 July 2018 (EDT)
Actually, Archery (event) should undergo a page move instead to preserve page histories, and the Archery page should instead list the two events. (T|C) 13:11, 11 July 2018 (EDT)
That's a good idea, alright, so we'll move the current Archery to Archery (class), Archery (event) to the now empty Archery, convert that into the disambiguation page, and have the separate games' information split off onto the separate pages, which is linked to from the disambiguation page along with the class. If I find any other pages with the same names as their classes, the same thing will happen there too. BBQ Turtle (talk) 14:27, 11 July 2018 (EDT)
Additionally, for the Archery events in particular, I'd suggest using Archery (Nintendo DS) and Archery (Wii). For the other cases (such as one event sharing its name with another event on a different release of the same game and with yet two other events on different releases of a different game), talk to Porplemontage and he might know what to do. (T|C) 19:50, 11 July 2018 (EDT)
Well, the thing is, Archery is one of those awkward ones- it is appears in every game except 2012 for Wii, even 2016 Arcade. There's not a problem with 2012 3DS, as it's listed as Archery (Individual) and Archery (Team), so it'd go to those names, but if we named the 2016 3DS one that, things might start getting confusing. 100m Freestyle would only be worse too, as it appears in every instalment, and I don't think the name changes at all unlike 100m and Javelin. I don't know really, naming's hard with this lot, the determining the identifier thing doesn't really cover this case. BBQ Turtle (talk) 16:38, 12 July 2018 (EDT)
Maybe Porplemontage would like to look at this case. (T|C) 11:15, 13 July 2018 (EDT)
Split the levels exclusive to the Wii U version of Captain Toad: Treasure Tracker from their Super Mario 3D World counterparts
Waluigi Time (talk) Per my comments, these seem to be the same levels just with minor differences to account for the new control scheme.
7feetunder (talk) The comments have covered just about everything. These are not different levels, they have the same name, appearance, and design, just with slight alterations so Captain Toad can traverse them.
TheFlameChomp (talk) Per the comments. These seem to be the same levels, with minor differences to make them work as Captain Toad levels, unlike the Super Mario Odyssey kingdom levels, which all have their own names and are redesigned as miniature versions.
Mario jc (talk) Per all, there's a much bigger difference between the Captain Toad Odyssey levels and the original Odyssey kingdoms than in the Captain Toad 3D World levels and the original 3D World levels.
Comments
Aren't they still basically the same level though? I don't see what them being replaced with Odyssey-based levels has to do with whether the pages are split or not. --Too Bad!WaluigiTime! 12:00, 13 July 2018 (EDT)
@Waluigi Time: Read my second point. It's my main reason for proposing this. (T|C) 12:44, 13 July 2018 (EDT)
I think the key difference between those examples and these is that those are similar levels/worlds with the same name, while these are the same levels with minor changes to account for Captain Toad's different controls. I'd also like to point out that we have the worlds from NSMBU/NSLU merged, which seems more similar to the case of the Captain Toad levels than the ones you listed. --Too Bad!WaluigiTime! 14:46, 13 July 2018 (EDT)
That's also another case, as the main article refers to the location itself, while the Odyssey level is split because... well, it's a specific level in Odyssey. Bowser's Castle and Luigi's Mansion are both split into several articles for similar reasons. --Too Bad!WaluigiTime! 16:03, 13 July 2018 (EDT)
The Super Mario Odyssey-based levels aren't "same level with maybe a ladder or two added," and from what I gather that's roughly what the Super Mario 3D World-based levels are. Doc von Schmeltwick (talk) 17:41, 13 July 2018 (EDT)
The layout in both versions of these levels is the exact same with slightly different elements to accommodate the gameplay. Splitting them would mean copy-pasting, which is against one of the site's rules: Once and Only Once. On the other hand, levels from Donkey Kong Country 2, while sharing the same names as those in Donkey Kong Land 2, have different layouts as if they were new levels. Also, Jumpy Jungle from MvDKMLM is an attraction in an amusement park, while Jumpy Jungle from MvDKTS is not, making them fundamentally different--plus, it's only good to keep them separate like that for continuity. -- -- KOOPACONCARNE 12:44, 14 July 2018 (EDT)
Yet we don't split Mario Kart racetracks based on the versions they appear in. The Captain Toad levels are the same case as those. -- -- KOOPACONCARNE 15:26, 14 July 2018 (EDT)
To put this point in perspective, the original Cheese Land seems to be on the moon. But when it reappeared in the MK8 DLC, it's based off of the Utah desert instead. A similar situation exists with Ribbon Road. Doc von Schmeltwick (talk) 18:11, 15 July 2018 (EDT)
@TheFlameChomp: Actually, the English version of the Japanese Captain Toad: Treasure Tracker Switch trailer translated that bit as "miniature." Sure sounds like that when I listened to it and my suspicions were right. – Owencrazyboy9 (talk) 18:12, 15 July 2018 (EDT)
Split Switch/3DS ports with substantial new content
This is an inconsistency on the wiki that's been bothering me for a while now. Currently, Donkey Kong Country: Tropical Freeze on Switch is merged with the Wii U version, Captain Toad: Treasure Tracker on Switch and 3DS are merged with the Wii U version, and the upcoming Luigi's Mansion remake for DS is merged with the Gamecube version. After inquiring about this, I was told that games like this are only split if the title is different, or if there are big gameplay differences like the Mario & Sonic games.
However, I think this is silly and arbitrary. Tropical Freeze has a new mode with a new playable character that has his own unique mechanics and Treasure Tracker has new levels while also removing some others, yet somehow these games aren't considered worthy of their own article while a game like Mario Kart 8 Deluxe, Super Mario Maker for Nintendo 3DS, Donkey Kong Country Returns 3D, or Poochy & Yoshi's Woolly World is, simply because they have the same name as the original. Obviously, this should be decided on a case-by-case basis, because if a port/remake doesn't have any new features, it probably wouldn't warrant an article.
If this proposal passes, the following articles will be split and a precedent will be set for the future:
Donkey Kong Country: Tropical Freeze (Nintendo Switch)
Tails777 (talk) I personally support this. Even if the game hasn't changed that much, Poochy and Yoshi's Woolly World hasn't changed that much either. P&YWW adds some additional costumes and, like Tropical Freeze on the Switch, an easy mode. What makes Woolly World's port more notable than Tropical Freeze's port?
Oppose
YoshiFlutterJump (talk) Per my comments below. We need more discussion about this. I honestly think merging is a better idea here than splitting.
Comments
I was just going to propose the opposite: merge standard ports. I'd still propose keeping the deluxe ports separate, though. I feel like we need more discussion on this matter before proposing this. I think that these ports should stay merged, but we also merge stuff like Poochy & Yoshi's Woolly World and Super Mario Maker for 3DS. That would give us fewer stubby articles to worry about. But I feel like we need more discussion before proposing something like this or my idea. -YFJ (talk · edits) 17:15, 16 July 2018 (EDT)
These articles wouldn't be stubs though. If an article has all the information about its subject, then it's not a stub. --Too Bad!WaluigiTime! 20:28, 16 July 2018 (EDT)
14:52, 13 July 2018 (EDT)
Yoshi Egg 1990 
15:19, 13 July 2018 (EDT)
(T|C) 13:11, 11 July 2018 (EDT)
Too Bad! Waluigi Time! 12:00, 13 July 2018 (EDT)
Too Bad! Waluigi Time! 14:46, 13 July 2018 (EDT)
Yoshi the SSM (talk) 14:00, 14 July 2018 (EDT)
