#{{user|Mario jc}} Three to me is too little. I think four is at least a better minimum.
#{{user|Mario jc}} Three to me is too little. I think four is at least a better minimum.
#{{User|TheFlameChomp}} Per all.
#{{User|TheFlameChomp}} Per all.
#{{User|rollerC}} Per all.
====Five entries (keep current limit)====
====Five entries (keep current limit)====
Revision as of 14:50, August 6, 2018
Current time:
Monday, February 17th, 22:46 GMT
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 its own mini-proposal with a deadline and Support/Oppose subheadings. The rules above apply to each option as if it were a its own 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 "Oppose" wins for that option by default. A poll proposal closes after all of its options have been settled, and no action is taken until then. 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])====
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
Move Kutlass to Kutlass (enemy) (discuss) Deadline: February 17, 2025, 23:59 GMT
Resplit Birdo (species) (discuss) Deadline: February 18, 2025, 23:59 GMT
Reduce the minimum number of entries for game-specific categories
There are just too many scenarios where there are three or four game specific things: the number of levels in Donkey Kong, the number of levels in Donkey Kong Jr., the number of levels in Donkey Kong 3, the number of minigames in Mario & Luigi: Dream Team, the number of ATVs in Mario Kart 8, the number of minigames in Paper Mario: Color Splash...the list goes on. It's so big of a problem that at least the moves and minigames categories are clogged up, and the problem would have been even more prevalent if not for the franchise-specific categories. Plus, there are gaping inconsistencies all over; why do we not get to create a category on Mario Kart 8's ATVs when we can make a category on Mario Kart 8 Deluxe's ATVs? That's not to mention that other wikis, like ZeldaWiki and Bulbapedia, don't even have these kinds of limits. Therefore, I propose that we reduce the minimum number of required entries in game-specific categories from five to three, as that amount makes the most sense to me, though there's also an option for having the minimum at four instead.
And if you're wondering, Porplemontage gave the green light for this proposal.
Doc von Schmeltwick (talk) As long as it's game-specific and done to avoid major category clog, I'm fine with this. I just don't want a category for a creature species that has only 3 pages, like some wikis have, clogging everything....(Moving from 3 as this option didn't exist at the time)
Mario jc (talk) Three to me is too little. I think four is at least a better minimum.
Alex95 (talk) - I'm going to agree with the five limit minimum, as if it doesn't have that many entries, the category likely doesn't need to be made in the first place. Having less than five entries just seems too little to me and makes the use of a category unnecessary, especially if there's also a navigation template involved.
"That's not to mention that other wikis, like ZeldaWiki and Bulbapedia, don't even have these kinds of limits." - I know I've said this several times before, but what other wikis do shouldn't be taken into account for what we do. 20:49, 5 August 2018 (EDT)
That doesn't mean that what other wikis do shouldn't be examined to see if and how it fits into what we do. On another note, if you ask me, the glaring omission of Category:Mario Kart 8 ATVs feels really inconsistent. Keep in mind, this applies long-term, too, so what you see as a "solution looking for a problem" now might be the exact opposite later on. (T|C) 21:11, 5 August 2018 (EDT)
About the point regarding Mario Kart 8 and Mario Kart 8 Deluxe ATVs, why not just create a category called "Mario Kart 8 and Mario Kart 8 Deluxe ATVs"? Or actually, why do we even need the "Mario Kart 8 Deluxe ATVs" when we already have ATVs as a category? It's me, Mario! (Talk / Stalk) 15:18, 6 August 2018 (EDT)
And why is the Inkstriker not in the ATV category? Is it because it's exclusive to Mario Kart 8 Deluxe and would be redundant? If you were to pass the proposal and make the Mario Kart 8 ATV category, would you also remove those Mario Kart 8 entries too (thus the ATV category would still be too small to be its own category, having only two entries, if we're following consistency with how the Inkstriker is categorized) or add the Inkstriker in the ATV category? If not, why create a third nearly-identical category? It makes more sense to me to just have one category called "ATVs" and maybe italicize Inkstriker (if that's possible) and say that italics are exclusive to Mario Kart 8 Deluxe. If a new game comes out with new ATVs, then we can make a new category called "Mario Kart 8 / DX ATVs", something like that. It's me, Mario! (Talk / Stalk) 15:25, 6 August 2018 (EDT)
How about four? MarioJC 00:11, 6 August 2018 (EDT)
Good point. I guess this should be a multi-option proposal then. (T|C) 00:42, 6 August 2018 (EDT)
Create articles for the various status effects inflicted by Roy in Paper Mario: Color Splash
However, instead of keeping this category in a grey area, why not add information on the various status effects inflicted in the first segment of the battle with Roy? After all, Poison is one of them, which makes the omission of the other status effects really inconsistent. To break it down for you, here's a full list of the status effects inflicted by Roy:
Rage: Mario's action command speeds up.
Rhythm: Mario can't use cards with blue backgrounds. (conjectural name)
I'm curious, why have you given one of the conjectural ones the name of "Rhythm?" Doc von Schmeltwick (talk) 23:15, 5 August 2018 (EDT)
Because there isn't really a better conjectural name to give it. If you want the game's description, it's "Mario can't resist the rhythm! Get those blue cards outta here!" Do you, by any chance, happen to have a better conjectural name for it? (T|C) 00:46, 6 August 2018 (EDT)
Nope, I haven't been able to acquire the game yet. I was just curious, as the description in the proposal didn't itself seem to relate. Doc von Schmeltwick (talk) 13:24, 6 August 2018 (EDT)
Why not create an article of list of status conditions? Might make more sense if the names are conjectural. It's me, Mario! (Talk / Stalk) 15:28, 6 August 2018 (EDT)
20:49, 5 August 2018 (EDT)
(T|C) 21:11, 5 August 2018 (EDT)
It's me, Mario! (Talk / Stalk) 15:18, 6 August 2018 (EDT)
Mario JC 00:11, 6 August 2018 (EDT)
It's me, Mario! (Talk / Stalk) 15:28, 6 August 2018 (EDT)
