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}}}} [make a statement indicating that you support your 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".
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 {{TPP discuss}}. 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
Add the Nintendo Kids Club games to the list of games (discuss) Deadline: January 24, 2025, 23:59 GMT
Update the Manual of Style to discourage contractions on the wiki
First of all, I'm aware this proposal might sound pedantic. It's perfectly fine to use contractions in every day speech and writing because it's easier than to use the whole structure when it doesn't matter that much; see, I just did that four times now. However, they do sound unprofessional on a site that is treated as an encyclopedia. Using structures such as "it's" and "don'ts" in main space sentences create the impression of a personal addressing to the reader, much like the use of "you's" would. Therefore, I propose that the manual of style be updated to simply state that contractions are not really welcome on the wiki, and that current instances should be expanded to their full forms when spotted. I'm not saying the manual should downright enforce writing without contractions because that would be a colossal maintanance undertaking. But really, what you do when you contract a structure is basically replace one letter with an apostrophe. I don't think omitting one letter reduces the effort, and frankly, sometimes it'sannoying to see that so aggressively put in practice.
Proposer: Super Radio (talk) Deadline: October 27, 2018, 16:45 GMT
Do it
Super Radio (talk) This can't, I mean cannot be accepted much longer.
Syncro263892XL (talk) I agree. It should not be 'Mario can't do it'. It must be 'Mario cannot do it.'
Toadette the Achiever (talk) As long as it's enforced on the same line as how we already enforce proper usage of italics (see comment below), I'm for this. Per Super Radio.
Alex95 (talk) - I've been writing like this anyway when it comes to content pages, so I guess I've already agreed.
TheFlameChomp (talk) I’ve recently been removing some contractions when preforming maintenance edits to articles, so I do not have a problem with doing this.
Yoshi the SSM (talk) I know we aren't (are not) Wikipedia. However, it does do this. And if it works there, it should work here too. As long as it doesn't effect official contractions (quotes and article titles), I am ok with this. Even though, I am part of the problem thus far. So, I per the proposal.
Doomhiker (talk) This change would definitely improve the overall quality of the writing on the wiki, and saying Donkey kong did not do it sounds a lot better than Donkey kong didn't do it, in my opinion.
Baby Luigi (talk) Contractions are a type of slang, which already contradict most style guides anyway. Support.
MarioManiac1981 (talk) While I'm not entirely against this proposal, I feel that, as Super Radio mentioned before, it is huge maintenance to remove contractions, and monitor their use on this wiki. It is somewhat contradictory to enforce a rule against the usage of contractions, because the manual of style uses contractions quite a lot for its explanations. We just need to discuss when contractions will not be tolerated, and when they're just fine to use.
Scrooge200 (talk) I think contractions are fine. I do agree that they can get out of hand sometimes, but it's better to just fix a few small instances of contraction overdose than discourage contractions entirely.
WeirdDave13 (talk) Changing vote, as this seems unnecessary.
MeritC (talk) I seriously do not see why our not being able to use contractions whenever necessary would be unprofessional. The only thing that's a definite standard is not using the word "you" in mainspace articles since this is to be treated like an "encyclopedia site". So I'm voting no here.
Comments
While I certainly agree, I don't think we should draw a hard line on using contractions, just notify users when they use them, like what we already do for users who forget to use proper italics. (T|C) 13:01, 13 October 2018 (EDT)
True, maybe I should have worded my proposal this way... -- -- KOOPACONCARNE 13:04, 13 October 2018 (EDT)
@MarioManiac1981: The proposal only addresses content in main space articles (Super Mario Bros., Princess Peach, Super Mushroom etc.), not talk pages and project pages, like this one or the guidelines. -- -- KOOPACONCARNE 15:18, 13 October 2018 (EDT)
@Yoshi the SSM: Don't be so harsh on yourself :) -- -- KOOPACONCARNE 16:46, 13 October 2018 (EDT)
(T|C) 13:01, 13 October 2018 (EDT)
