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.
A given user may author/co-author up to five ongoing proposals. Any additional proposals will be immediately canceled.
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. Keep in mind that we use approval voting, so all of your votes count equally regardless of preferred order.
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 subissues that can be resolved independently of each other. In a poll proposal, each option is essentially its own mini-proposal with a deadline and suboption headings. The rules above apply to each option as if it were its own proposal: users may vote 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
Reorganize and reduce the Mobs section of the Minecraft article (discuss) Deadline: April 16, 2025, 23:59 GMT
I've noticed a lot of pages with names that are technically sourced, but use unreliable sources like the Super Mario Daijiten (see: Most Wario Land enemies/bosses). Since putting a citation and marking it with refneeded could look confusing, my solution is an easy-to-understand template at the top of the page, something like this.
Proposer: Binarystep (talk) Deadline: May 11, 2015 23:59 GMT
Walkazo (talk) - It would be better to just have something like Wikipedia's "better source" template to flag iffy refs: then it could be used for situations besides just the ones affecting article titles, like how the new {{Pageneeded}} template can be used for too-vague print refs.
Comments
I have another idea for the template that says something to the effect of "Some of the sources cited on this page are unreliable, replace them with better ones if possible", would that be better? Binarystep (talk) 15:54, 4 May 2015 (EDT)
Like a {{Rewrite}}-style notice template? That idea has a bit more merit, but I feel like it's better just sticking with the {{refneeded}} system flagging the specific problems: no need to advertise twice over that we suck at citing our sources for the most part. - Walkazo (talk)
I suppose, but refneeded implies a lack of a source, while this is more "better source needed". Binarystep (talk) 16:36, 7 May 2015 (EDT)
Like I said in my vote, we should just make more templates like refneeded (rather than banner notice templates) for flagging both less-than-ideal sources and broken links, hence "refneeded system". - Walkazo (talk)
Ah, alright then. Binarystep (talk) 16:55, 7 May 2015 (EDT)
Removals
None at the moment.
Changes
None at the moment.
Miscellaneous
Stop Using the "Super Mario Daijiten" as a Source
Let me preface this by saying that the "Super Mario Daijiten (Big Dictionary)" has proved to be correct on someotheroccasions in the past. However, even a broken clock is right twice a day.
So, what is this "Big Dictionary"? To put it simply, it is us, but in Japanese: it's a compilation of everything in the Mario series (and the Donkey Kong, Yoshi, and Wario series) with some information about them. Naturally, this includes all of those obscure enemies from the older platformers, like Scubi, Bībī, Sutāzu, and many more, though these names were either taken from or changed to ones from the Daijiten. One immediate problem is noticeable: Japanese names are hard to search for. Names taken from Japanese sources are (supposed to be) written out not with a translation, but with the romanization, avoiding the problem of subjective translations. This also includes any special characters with macrons above them, and this results in links being difficult to use with them, for the simple reason that a very large portion of readers wouldn't be able to type these letters, and the wiki isn't able to recognize substitute letters, so "Sutazu" would not work as a link or a search term for "Sutāzu", and it's a tedious process to get to the article of relevance. There's also the point of English and Japanese names looking rather messy side-by-side, though that's mostly personal preference. Of course, these points are completely ignored if they're the only official names that we can find, and therein lies the problem.
As mentioned above, the site is basically us with a different language, and that includes the fact that it is a fan site, subject to all of the follies that editors can employ. If it doesn't explicitly display that the name is from an official source, listed here, it cannot be used since it could easily just be a made-up name. Even if other similar sites share the name with the Daijiten, if they don't have an official source, it doesn't count: they could have easily taken the name from each other, validating the name by virtue of lazy editing. Even besides that, however, there's no reason for all of the names for a certain game to be correct if a few of them turn out to be correct. For example, I've picked up the Prima guide for Yoshi's Island DS, and it turns out that most of the enemies from that game (on this wiki, at least) take their names from this guide - emphasis on most. Scorchit, originally "Zeus Guy", and Toober Guy, originally "Tube Guy", went under different names between the guide and the wiki, but since some of the other names were backed up with "is good is from book", all of them were thought to come from the book. This is faulty logic and using such a broad generalization really can't be healthy for the wiki.
While I understand that some of the conjectural names weren't very descriptive (Dōryī, for example, was "Plant"), I'd rather have a million "Birds" and "Crabs" than a name that is not only hard to link to and search for, but a name that has a good chance of being just as conjectural as the other names. Even for a site that's had a good track record, I feel like allowing the site to be used for all names is just opening the floodgates for name-related debacles, and I'd rather avoid that. Note: this proposal, if it succeeds, would involve removing all names that are currently "sourced" with the Daijiten, as well as renaming articles with those names to English variants.
Proposer: Time Turner (talk) Deadline: May 14, 2015, 23:59 GMT
Burningdragon25 (talk) Per TT and by the way, I'll go with him on this case!
Do not remove it
Walkazo (talk) - It would be a waste to wholesale dismiss the Daijitan as a resource and potentially move countless pages away from legitimate names to pure conjecture (and scrap dozens if not hundreds more {{foreignname}} entries) just because it's been wrong a few times. We're no better than them when it comes to making periodic mistakes, rampant eschewing of citations, and the occasional rogue user just making stuff up: we might as well tell people to ignore us as a resource too. It would be better to simply be transparent by citing them whenever we use them and marking those citations as less-than-ideal with a "better source" template, the same as we would with Wikipedia references or any other iffy, yet better-than-nothing references. The anti-Japanese arguments are meaningless: we will always have Japanese and other non-English names to deal with, mixed in with the made-up English names (and/or in the foreignname templates). Redirects get around the macrons without any grief for searchers or editors who don't want to bother copy and paste a macron from somewhere else for the link, and policy actually says redirects should be created for that reason: any macron-bearing pagename without a redirect is an oversight.
Binarystep (talk) Changing my vote, per Walkazo. Removing names that are possibly correct and replacing them with names we made up is a horrible idea.
Comments
As passing this proposal would mark many of our articles as conjectural titles, one strategy we could employ is to see the references of each page on the Super Mario Daijiten (if there is one). That way, we can see still use the Daijiten to indirectly get official information, which we can in turn cite. Andymii (talk) 16:44, 10 May 2015 (EDT)
I made the assumption that, if the Daijiten used sources, we would have used them in the first place instead of citing the Daijiten. It's a fair point to make, though, but I'm not exactly fluent enough to navigate the site, and some online translation probably won't help. Would you happen to be able to go through the site? Hello, I'm Time Turner.
Unfortunately, no. I guess it is up to our Japanese-fluent users to help us out now. However, there is a function though on Google Translate that translate whole entire websites, so that might be useful in getting the general idea, maybe even enough so we can get official information accurately without knowing much of the language. Andymii (talk) 09:50, 11 May 2015 (EDT)
Just noting here that I retracted my vote in favor of removing it. I agree with Walkazo's argument enough to change my mind, but not enough to fully cast a vote either direction now, as it hinges on a type of template that we currently (to my knowledge, at least) do not employ. -- 1337star(Mailbox SP) 14:51, 11 May 2015 (EDT)
