MarioWiki:Proposals

Current time: Thursday, June 20th, 15:32 GMT

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. For past proposals, see the proposal archive and the talk page proposal archive.

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

1. 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}}.
2. Only registered, autoconfirmed users can create, comment in, or vote on proposals and talk page proposals. Users may vote for more than one option, but they may not vote for every option available.
3. 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.
4. 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.
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 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.
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 "(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.
7. No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
8. 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.
9. 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.
10. If a proposal with only two voting options has more than ten votes, it can only pass or fail with a margin of at least three votes, otherwise the deadline will be extended for another week as if no majority was reached at all.
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. Proposals cannot be made about promotions and demotions. Users can only be promoted and demoted by the will of the administration.
17. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
18. 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: "June 20, 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".

Talk page proposals

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.

For a list of all settled talk page proposals, see MarioWiki:Proposals/TPP archive and Category:Settled talk page proposals.

Rules

1. 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. Place {{TPP}} under the section's header, and once the proposal is over, replace the template with {{settled TPP}}.
2. 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:
3. 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.
4. The talk page proposal must pertain to the article it is posted on.
5. 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

• Merge Young Link and Toon Link info to Link's article (discuss) Deadline: June 20, 2024, 23:59 GMT
• Move Baby Donkey Kong to Baby DK (discuss) Deadline: June 21, 2024, 23:59 GMT
• Consider Grifty to be a Little Mouser (discuss) Deadline: June 22, 2024, 23:59 GMT
• Move Category:Cats to Category:Felines (discuss) Deadline: June 24, 2024, 23:59 GMT
• Consider Podley and Podler to be Beanish (discuss) Deadline: June 27, 2024, 23:59 GMT
• Decide if Gallery:Ground should be deleted (discuss) Deadline: July 2, 2024, 23:59 GMT

Unimplemented proposals

Proposals

Split Mario Kart Tour character variants into list articles, Tails777 (ended May 4, 2022)

Establish a standard for long course listings in articles for characters/enemies/items/etc., Koopa con Carne (ended June 8, 2023)

Add tabbers to race/battle course articles, GuntherBB (ended November 18, 2023)

Merge Super Mario Bros. (film) subjects with their game counterparts, JanMisali (ended April 18, 2024)

Remove profiles and certain other content related to the Super Mario Bros. Encyclopedia from the wiki, Koopa con Carne (ended April 30, 2024)

Break alphabetical order in enemy lists to list enemy variants below their base form, EvieMaybe (ended May 21, 2024)

Consider "humorous" and other related terms as frequently misused in MarioWiki:Good writing, DrippingYellow (ended May 26, 2024)

^ Note: Requires action from admins.

Discourage "([Title] for [system])" disambiguation format when "([Title])" alone is sufficient to identify the subject, JanMisali (ended June 9, 2024)

Use shorter disambiguation identifier (without subtitle) for Donkey Kong Country 2 and Donkey Kong Country 3 pages, Arend (ended June 18, 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)

Add product IDs in game infoboxes, Windy (ended March 18, 2023)

Make bestiary list pages for the Minion Quest and Bowser Jr.'s Journey modes, Doc von Schmeltwick (ended January 11, 2024)

Split Mario's Time Machine (Nintendo Entertainment System), or the Super Nintendo Entertainment version along with both console versions of Mario is Missing!, LinkTheLefty (ended April 11, 2024)

Remove non-Super Mario content from Super Smash Bros. series challenges articles, BMfan08 (ended May 3, 2024)

Split Cheep Blimp (Paper Mario: The Thousand-Year Door) and Zeeppelin from the blimp page, Doc von Schmeltwick (ended May 28, 2024)

List of Talk Page Proposals

• Rename Category:Rodents‎ to Template:Fakelink (Discuss) Deadline: October 1, 2013, 23:59 GMT
• Remove Super Smash Bros. Melee trophy descriptions in Assist Trophy (Discuss) Deadline: October 10, 2013, 23:59 GMT

Writing Guidelines

A writing guideline for Image Maps

see here for the draft.

This Writing Guideline is meant to clear thing of when and how an Image Map page should be created. It will be created under the name MarioWiki:Image Maps. These rules only apply to real articles.

All information are present in the draft, description is present here:

The Map Images must be a map sprite from the game, screenshot, or an official map artwork because it makes the Image Map looks professional. Fan-made will make the Image Map looks fake, unofficial nor professional

Templates are only for real articles, no templates for Policy pages, Help pages, or Userpages.. However, coding can go in any other page.

Image Maps are meant only for locations, or levels. It is not good to have an Image map for characters, even if the artwork was official, it won't look neat.

Image Maps are meant to help with navigation. If image is less than 8 links, it could be embedded in the page with caption description the links. Example on the right.

From left to right: "This", "is", "an", and "example".

The Image Map's any dimension must not exceed 400 pixels, and the other one must not exceed 200 pixels. The Image Map's width in the {{Worldbox}} template must never exceed 300 pixels.
I specified the sizes depending on medium sized screens, so it does not look very small, or very big. Reason includes that if maps were larger than that then the page would look very crowded.

If the map isn't going to be put into the Worldbox template, then the map should be classed as a thumbnail and aligned to the right. However, If the map is only going to be put in the Worldbox template, it must be classed as none and it must be aligned in the center. Otherwise a variable must be declared; so if it is set to infobox,it would be aligned in the center and it would be classed as none. And if it is not set, it would be classed as a thumbnail and it would be aligned to the right.

In other word, templates like {{NSMBmap}} are put inside the {{Worldbox}} and never outside, so it is classed as none and it is aligned in the center, so it looks centered and without borders in the template. Templates like {{PMTTYDmap}} are put outsise the Worldbox template and never inside, so it is classed as thumbnail and aligned to the right. However templates like {{NSMBUmap}} are put both inside and outside, so there is a variable defining if it would be put in the Worldbox template, or would be put outside.

The template must only be put where it links to (i.e If the template only links to Template:Fakelink and Template:Fakelink, it must never be put on Template:Fakelink). That's because it is unneeded on an unrelated page.

If the article is about a subject that only appeared in the Image Map's game, the template should be put under the info-box. Otherwise the template should be put as the first line in the game's section on the article.

Explaining: {{PMTTYDmap}} links to X-Naut Fortress and The Moon.. Since X-Naut Fortress only appeared in Paper Mario: The Thousand-Year Door, the template is put under the infobox, However The Moon appeared in multiple games, so the template is put in the game's section.

For the Platformer games: in the Worlds pages, the template should be put in the map parameter of the {{Worldbox}} template (using the code |map={{templatename}}). Reason includes it unneeded to crowd the page with a template, which can be put inside the infobox template.

Last three sections describe basics of creating the template.

Use the comments section below for comments and suggestions.

Proposer: Megadardery (talk)
Deadline: September 30, 2013 23:59 GMT

Support

1. Megadardery (talk)
2. Yoshi876 (talk) Per proposal. Should help those new to image maps as well.
3. Scr7 (talk) per proposal... I don't see anything bad about this, and it'd be helpful to a lot of people.
4. Sonic98 (talk) Per all
5. LeftyGreenMario (talk) ImageMaps will come in the future (until something renders it deprecated), and once more people know how to do it, the better. Knowledge is power.
6. Driftmaster130 (talk) Per all.
7. World10 (talk) I think it's a good idea, per all.
8. Icemario11 (talk) Per all.
9. Ultra Koopa (talk) Per LeftyGreenMario.

Oppose

1. Iggy Koopa Jr (talk) I personally find it unneeded.
2. Mario7 (talk) I think it is fine the way it is, and we don't need to change anything.
3. Gonzales Kart Inc. (talk) Per Mario7.

Comments

@Iggy Koopa Jr Why? Image maps are kinda complicated, they need several rules, so it does not look messy when created. Megadardery (talk)

It is because not many image maps are made on this wiki(because unneeded), and not everyone knows how to make one. I have myself not stumbled on a messy Map, so I think rules for something already done well is unneeded. Iggy Koopa Jr (talk)

The reason of not too many ImageMaps are made on wiki mostly because people don't know how to make one, hopefully this writing guideline will put standards for making the Imagemap, that's why I made it in the first place, With many games (specially 3DS games) new today, the ImageMaps will help a lot in navigation. And I can guess that's lot of ImageMaps are coming in near future. Megadardery (talk)

New features

Make Most Maintenance Categories Hidden

An idea which was willing on my mind from long time ago. The Maintenance categories should be hidden from the categories bar on the bottom of each article. The categories bar on each article is only for main categories. Some readers may just want to navigate through the categories without contributing. And for any user that does want to see them, he could just navigate to his Preferences, in Appearance tab, down at Advanced options. Check "Show hidden categories".

List: (marked with * may need some discussion)

• Category:Articles under construction
• Category:Articles with conjectural titles
• Category:Articles with long Trivia sections
• Category:Citation needed
• Category:Disambiguation -- It looks neater for Disamb pages to appear without categories
• Category:Image requested
• Category:Quality requested
• Category:Merge Requested & Category:Split Requested
• Category:Pages with broken file links
• Category:Pages with media files
• Category:Protection Change Requested
• Category:Requested for Deletion* & Category:To be deleted* & Category:Talk to be deleted*
• Category:Rewrite Requested & Category:Rewrite and Expansion Requested
• Category:Stubs & Category:Section Stubs & Category:New Stubs

Proposer: Megadardery (talk)
Deadline: October, 7 2013 23:59 GMT

Support

1. Megadardery (talk) -- Per Proposal, the categories bar should only contain real-articles related categories.
2. Gonzales Kart Inc. (talk) Per Dardery.

Oppose

1. Mario7 (talk) I think that these should be easily visible so that editors can quickly see that changes need to be made and visitors can see what the problem is, so they don't get a bad impression of this wiki

Comments

So, exactly why do we need to hide these categories? And wouldn't unchecking the hide option show categories that are hidden in the first place, adding more clutter? LeftyGreenMario (talk)

So the categories bar doesn't get crowded with categories unrelated to the subject itself.. as for the second question, I don't think I quite understand it. Megadardery (talk)

My question is that are there already hidden categories in the first place? You know, I'd like to know the amount of categories that are already hidden. LeftyGreenMario (talk)

Nope! There are no hidden categories yet! any hidden category will automatically go in Category:Hidden categories which I will create as soon this proposal pass. Megadardery (talk)

@Mario7 The problem can be easily seen by looking on the Notice Template which is mostly on the top of any page. And Editor can see them by checking the 'Show hidden Categories' option. Megadardery (talk)

Removals

None at the moment.

Changes

None at the moment.

Miscellaneous

Pokemon, Assist Trophies, and the SSB Templates

As of now, we have three templates for the three games in the Super Smash Bros. series: {{SSB}}}, {{SSBM}}, and {{SSBB}}. All of these templates have various sections for their aspects, whether they'd be items, non-playable characters, enemies, etc. However, there's always been one peculiarity that's always bothered me: none of the Poké Ball Pokémon, nor any of the Assist Trophy characters, are listed in any of templates. We've made it a point of (trying to) list all of the stage hazard characters in the templates, but everything from Andross to Weavile has simply been absent, which seems rather inconsistent. Is there really any reason for keeping them out of the templates? Yes, just about all of the Pokémon/Assist Trophies are merged into articles, but that's why we have redirects (which is also aided by the advent of anchors), and most, if not all, of the stage hazards have also been merged. Really, the only question should be whether to give them separate sections in the template or to stick them in the NPC section.

Proposer: Time Turner (talk)
Deadline: October 3, 2013, 23:59 GMT

Add a New "Pokémon"/"Assist Trophy" Section to the Appropriate Templates

1. Time Turner (talk) The NPC section would probably get too cramped if we started adding the Pokémon and the Assist Trophies.
2. Iggy Koopa Jr (talk) Seems weird that this information is not figured anywhere.
3. Mario7 (talk) Per proposal and all

Do Nothing

1. Walkazo (talk) - Nav templates are for navigating between pages: tonnes and tonnes of links to the same list page (or two) will just clutter up the templates, making them look bad and hindering navigation to the other, separate pages. Just add one link to the Pokemon list page on the templates that don't have it yet (which is an oversight and doesn't require a proposal in itself), and folks can use the TOC to navigate the lists from there.
2. Tucayo (talk) - Per Walkazo. A template linking to the same page in 90% of its entries is not exactly useful. And, as she said, adding a link to said page wouldn't even require a proposal.
3. Gonzales Kart Inc. (talk) Per Tucayo
4. Megadardery (talk) Per my comment.
5. Yoshi876 (talk) Per Walkazo.
6. Ultra Koopa (talk) - Per Walkazo.
7. Icemario11 (talk) - Per Walkazo.
8. Mario4Ever (talk) Per Walkazo.
9. Scr7 (talk) Per Walkazo

Comments

Personally, I prefer no listing Pokémons, or Assist Trophies, I feel it better when it just links to Assist Trophy and Pokémon articles. Instead of many unneeded links, just for listing. The articles has lists. And beside, I feel this does not worth a Proposal, not even a TPP.. I would stick with a {{talk}}, If I were you. Megadardery (talk)

The proposal's already up, might as well roll with it. Besides, which talk page would I post it on, the Pokemon or the Assist Trophy? Also, how exactly are they unneeded? Time Turner (talk)

You would put that on {{SSBB}}. Back with the discussing, I said unneeded because they would crowd the template with unnecessary list, while there is already an link for Assist Trophy and Pokémon, and those articles contains those lists already. Megadardery (talk)

But my template is covering multiple templates (SSB, SSBM, SSBB). Yes, Assist Trophy isn't relevant for the first two, but the Pokemon are. Why does that even matter? Besides, there's already plenty of entries there. Why not the Assist Trophies and the Pokemon charcters? Let me put it this why: why should all the characters that appeared as obstacles (if even that) for a single stage be placed in a template, but characters that can show up no matter what stage you on and contribute greatly to the fight (Goldeen aside) be simply disregarded? Time Turner (talk)