MarioWiki:Proposals

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
Image used as a banner for the Proposals page
Current time:
Sunday, January 5th, 10:59 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.
  • For past proposals, see the proposal archive and the talk page proposal archive.

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.

How to

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

  1. Only autoconfirmed users may create or vote on proposals. Anyone is free to comment on proposals (provided that the page's protection level allows them to edit).
  2. 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.
  3. Users may vote for more than one option, but they may not vote for every option available.
  4. 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.
  5. 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.
  6. 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.
  7. Proposals cannot contradict an already ongoing proposal or overturn the decision of a previous proposal that concluded less than four weeks (28 days) ago.
  8. 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.
  9. 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.
  10. If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
  11. 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.
  12. 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.
  13. 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.
  14. After a proposal passes, it is added to the appropriate list of "unimplemented proposals" below and is removed once it has been sufficiently implemented.
  15. 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.
  16. 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.
  17. 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.
  18. Proposals cannot be made about promotions and demotions. Staff changes are discussed internally and handled by the bureaucrats.
  19. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
  20. Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.

Basic proposal formatting

Below is an example of what your proposal must look like. If you are unsure how to set up this format, simply copy the following and paste it into the fitting section. When updating the bracketed variables with actual information, 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 header, 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

Unimplemented proposals

Proposals

Break alphabetical order in enemy lists to list enemy variants below their base form, EvieMaybe (ended May 21, 2024)
Standardize sectioning for Super Mario series game articles, Nintendo101 (ended July 3, 2024)
^ NOTE: Not yet integrated for the Super Mario Maker titles, Super Mario Run, and Super Mario Bros. Wonder.
Create new sections for gallery pages to cover "unused/pre-release/prototype/etc." graphics separate from the ones that appear in the finalized games, Doc von Schmeltwick (ended September 2, 2024)
Add film and television ratings to Template:Ratings, TheUndescribableGhost (ended October 1, 2024)
Use the classic and classic link templates when discussing classic courses in Mario Kart Tour, YoYo (ended October 2, 2024)
Clarify coverage of the Super Smash Bros. series, Doc von Schmeltwick (ended October 17, 2024)
Remove all subpage and redirect links from all navigational templates, JanMisali (ended October 31, 2024)
Prioritize MESEN/NEStopia palette for NES sprites and screenshots, Doc von Schmeltwick (ended November 3, 2024)
Stop considering reused voice clips as references (usually), Waluigi Time (ended November 8, 2024)
Allow English names from closed captions, Koopa con Carne (ended November 12, 2024)
^ NOTE: A number of names coming from closed captions are listed here.
Split off the Mario Kart Tour template(s), MightyMario (ended November 24, 2024)
Split major RPG appearances of recurring locations, EvieMaybe (ended December 16, 2024)
Stop integrating templates under the names of planets and areas in the Super Mario Galaxy games, Nintendo101 (ended December 25, 2024)

Talk page proposals

Split all the clothing, Doc von Schmeltwick (ended September 12, 2021)
Split machine parts, Robo-Rabbit, and flag from Super Duel Mode, Doc von Schmeltwick (ended September 30, 2022)
Make bestiary list pages for the Minion Quest and Bowser Jr.'s Journey modes, Doc von Schmeltwick (ended January 11, 2024)
Allow separate articles for Diddy Kong Pilot (2003)'s subjects, Doc von Schmeltwick (ended August 3, 2024)
Create articles for specified special buildings in Super Mario Run, Salmancer (ended November 15, 2024)
Expand and rename List of characters by game to List of characters by first appearance, Hewer (ended November 20, 2024)
Merge False Character and Fighting Polygon/Wireframe/Alloy/Mii Teams into List of Super Smash Bros. series bosses, Doc von Schmeltwick (ended December 2, 2024)
Make changes to List of Smash Taunt characters, Hewer (ended December 27, 2024)
Merge ON/OFF Conveyor Belt with Conveyor Belt, PopitTart (ended January 1, 2025)

List of Talk Page Proposals

Writing Guidelines

Change the MarioWiki:Signature rules

See: Draft

I'm proposing a change to the current Signature policy, the changes help reading and reduce the distracting signature does. The following are the rules that got changed, all other rules are unchanged..

First of any thing: Reduce the height of the signatures, The current signature is awfully very tall (See this for example: User:Dashbot/Sandbox). I'm proposing this for multiple reasons, the strongest reason is that signatures higher than 20px in height disrupt the normal spacing between rows of text. Adding ugly unnecessary spacing. This applies for text and images, thus you cannot use any html tags that increase the text size, including but not limited to <big>, <br> and <div>. The second reason I'm proposing this is that the bigger the signature is, the much more it would be disruptive catching the eye out of the message itself.

Second: You want to use image, as you wish.. but don't use mainspace images, simple! Just use any external or any personal image. That is because the unnecessary linking in the file page.

Third: Use whichever font you want, as long as it is not higher than normal font. It must be easily readable, also.

Fourth: A minor change, you are now required to link to your talk page, instead of requiring you to link to your userpage. 98% of the time I click on a signature is to visit the talk page. You still can have links to your userpage, contributions, etc

Fifth: Another minor change, You are no longer allowed to link to real articles directly.. Most of you guys are already not doing that, just adding that for the record. If you really must link to a real article, use an external link.

Sixth: No External Links such as advertising or any other websites are allowed, Use your userpage for such things. Like the current system, you are allowed for maximum of five word links.

Last and most importantly: Don't make your signature very disruptive.

You can use disruptive, long, anything signature as raw code in other user's talk pages, ONLY if they say okay. If this passes, there will be a week-to-month time until {{sigfix}} get issued.

Proposer: Dashbot (talk)
Deadline: April 5, 2014, 23:59 GMT.

Support

  1. Dashbot (talk) We are an encyclopedia, we don't host fancy signatures. Signature should only be used for personality identifications, However, you can still have some good designs, if you adhere to those rules.

Oppose

  1. Epic Rosalina (talk) I'm fine with everything except the height rule; it seems okay as it is and you would hardly be able to see the pictures of Rosalina in my signature if you made the height requirement tighter.
  2. Randombob-omb4761 (talk) I don't think this would be great, many people will receive a sigfix warning. Per Epic Rosalina.
  3. Tails777 (talk) I think the rules are fine the way they are.
  4. Walkazo (talk) - While I am somewhat irritated by how spacing gets screwed up by sigs, I just shrug it off as something that can't be helped. Making images (and text) no taller than 12pt font is too draconian, and given how long the old dimensions have been established for, it's a bit late to try and change them now. Besides, we're an encyclopedia: messy talk pages aren't the end of the world as long as the mainspace and policy pages are solid. And on that note, the proposed MW:SIG draft is way too bulky; even if some things get changed to the policy down the road, the page should stay nice and compact like it is now.
  5. Ashley and Red (talk)Awful. The rules are good as they are. Also, why not use mainspace images?
  6. TVTrash (talk) Per Why Bother.
  7. driftmaster130 (talk) Per all, it would be a hassle to get everyone to fix their signatures quickly.
  8. Mario (talk) I strongly disagree with the second rule. I like the appearance of my signature very much, and I don't want to waste potential personal image slots and possible go over it just because of that rule. And using external links is not the best idea because you can't resize them. In all, this proposal creates more problems than it solves, I don't really hate the spacing and such. I just kind of ignore it.
  9. World10 (talk) I think the current rules are fine and I don't see any problems with the spacing.

Comments

I agree with parts, but I see no reason for why mainspace images can't be used. Yoshi876 (talk)

I agree that our current signature policy could probably stand a to be reviewed in some parts, and I do like some of your suggestions. However, this isn't like moving an article or banning something everyone is sick of, this is a site wide policy that a large section of our userbase takes advantage of. I feel that the proposals section is the wrong venue for this, you're not going to get the level of discussion really needed for a change of this scale here. More likely, it's going to fail because it only has a week get it's point across (and this is a fairly involved point) and proposals function less like discussions and more like "yes or no" affairs. My suggestion? Move this to the General Discussion forums (perhaps even the Wiki Collaborations sub-forum), get a discussion rolling. Once it's been narrowed down what people like, don't like and the compromises therein, bring it back to proposals as "yes or no" type of thing. -- Ghost Jam (talk)

Actually, writing guideline proposals last for two weeks, however, seeing as they can only be rewritten within the first three days and there are probably a few points that need to be ironed out and as Ghost Jam said the discussion for that probably wouldn't happen within that timeframe it would probably be best to discuss then propose. Yoshi876 (talk)
Even at two weeks, I'd put money on this snowballing to the "nope" side. Ghost Jam (talk)

I don't see why we can't use Mainspace Images, i don't see anything wrong with them. ~~ Boo4761

Look at the file usage for File:Booboo.gif, you can still normally use an external link by using something like http://www.mariowiki.com/images/a/ad/Booboo.gif Booboo.gif --
User:MegadarderyUser talk:MegadarderyDashbot signature
 04:59, 22 March 2014 (EDT)

@Ghost Jam: That's a pretty good idea, I think.. When this proposal reaches the deadline, We will have four weeks to discuss and settle this..
@Epic Rosalina: If you used another image, maybe this, this, if cropped, or this. It would appear better.
@Walkazo: The draft can be changed anytime. While it can be too draconian as you said, the talk pages are pretty disrupting, catching my eye out of the main message. The spacing looks ugly, I can't just throw this idea out myself.

--
User:MegadarderyUser talk:MegadarderyDashbot signature
 04:59, 22 March 2014 (EDT)

New features

None at the moment.

Removals

None at the moment.

Changes

None at the moment.

Miscellaneous

Split caps/emblems articles onto only one

Articles like "Mario Cap", "Luigi Cap", "Wario Cap", "Peach Crown", "Daisy Crown, and similar articles should be listed in only one article called "Cap"/"Hat". The same applies to emblems from sports games. In case of other character's using the emblems of another ones (e.i Toads using Peach's crown as an emblem in SMG), should be listed in trivoa of the charcter's theirselves. I also suggests that an gallery shoild be created. It would do the article better.

Proposer: Ashley and Red (talk)
Deadline: March 30, 2014, 23:59 GMT

Support

  1. Ashley and Red (talk) Per Proposal.
  2. bluetoad63 (talk) How about "Headwear"?

Oppose

Removal of Opposes

Comments

Retrieved from "https://www.mariowiki.com/index.php?title=MarioWiki:Proposals&oldid=1651587"