MarioWiki:Proposals

Image used as a banner for the Proposals page

Current time:
Wednesday, December 25^th, 18:31 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

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).
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

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

Move "Rare Ltd." to "Rareware" or "Rare" (discuss) Deadline: December 25, 2024, 23:59 GMT
Make changes to List of Smash Taunt characters (discuss) Deadline: December 27, 2024, 23:59 GMT
Tighten Category:Deceased characters (discuss) Deadline: December 27, 2024, 23:59 GMT
Merge Cascading Stone, vanishing platform, and moon platform with Falling Platform (discuss) Deadline: December 28, 2024, 23:59 GMT
Add to-do tasks on the Main Page (discuss) Deadline: January 1, 2025, 23:59 GMT
Rename the NES Template (discuss) Deadline: January 4, 2025, 23:59 GMT
Merge the list of show hosts in All Night Nippon: Super Mario Bros. (discuss) Deadline: January 4, 2025, 23:59 GMT
Split the theme songs from the list of Donkey Kong Country (television series) songs (discuss) Deadline: January 5, 2025, 23:59 GMT
Rename Mario & Sonic (series) to Mario & Sonic at the Olympic Games (series) (discuss) Deadline: January 6, 2025, 23:59 GMT
Rename Shadow to Shadow (enemy), and rename either Shadow (character) or Shadow (disambiguation) to Shadow (discuss) Deadline: January 6, 2025, 23:59 GMT
Decide what to do with Category:Siblings and Category:Twins (discuss) Deadline: January 7, 2025, 23:59 GMT
Merge Candy Block with Hard Block (discuss) Deadline: January 7, 2025, 23:59 GMT
Merge ON/OFF Conveyor Belt with Conveyor Belt, or expand to cover all reversible conveyor belts (discuss) Deadline: January 8, 2025, 23:59 GMT

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)

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)

Determine how to handle the Tattle Log images from Paper Mario: The Thousand-Year Door (Nintendo Switch), Technetium (ended November 30, 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)

Writing guidelines

None at the moment.

New features

Create articles for Glohm enemies or merge them with their normal counterparts

Based on the vote so far, this proposal may be eligible to close one week early. Please use {{proposal check|early=yes}} on November 28 at 23:59 GMT and close the proposal if applicable.

I'm currently contributing to Mario & Luigi: Brothership content, and I'm currently creating articles for enemies in the game. It has been brought to my attention that Glohm enemies are basically stronger versions of preexisting enemies, although they have unique characteristics.

This proposal aims to determine whether or not Glohm enemies get their own articles. So, there are two choices for when Glohm enemy coverage eventually occurs:

1. Glohm enemies get their own articles. They get their own dedicated pages.

2. Glohm enemy coverage is limited to the articles for their normal counterparts. This means all Glohm related information for them is explained for the normal versions of the enemies.

Let's see what happens!

Proposer: Sparks (talk)
Deadline: December 5, 2024, 23:59 GMT

Create new articles for Glohm enemies

Sparks (talk) My preferred choice. Sure it could get repetitive and redundant, but it's worth it to document the abilities of these Glohm enemies.
Camwoodstock (talk) We give articles to other stronger RPG enemy and boss variants, so why should Brothership be any different?
Tails777 (talk) They are stronger variants with different stats to their originals, no different from every example Camwoodstock gave. Per proposal.
DryBonesBandit (talk) Per all.
Zootalo (talk) The Shiny Paper versions of enemies from Paper Jam have their own articles as well; this is no different. Per all.
Nightwicked Bowser (talk) Probably best for overall consistancy with a game like this one.
Technetium (talk) Per all.
Cheat-master30 (talk) Given that some of them have specific differences in attack patterns, it seems like they should probably get unique articles.

Include Glohm enemy coverage on their normal counterparts' articles without creating new articles for them

Comments

@Zootalo The Paper Jam shiny enemies are not split, but the Sticker Star ones are.
— The preceding unsigned comment was added by Nightwicked Bowser (talk).

Kinda torn to be honest. I voted yes because some of them have specific differences from their regular counterparts (Glohm Floopfly Rs and Glohm Soreboars always explode once defeated for example), but then we've got the weird situation of trying to figure out what exactly you'd include on a page for the enemies without these things, like the Glohm Palookas (which as far as I know, look and act almost identically to their standard counterparts). --Cheat-master30 (talk) 22:30, November 23, 2024 (EST)

In fairness, this could also be said about many other stronger variants of enemies. The only real difference between a Goomba and Gloomba are the color schemes, in a similar way to how the only difference between a Palooka and a Glohm Palooka is the darker coloration and Glohmy aura. It's kinda just a natural thing for most stronger variants (not all mind you, but most).

Tails777 Talk to me!

Create a template to crop images on-the-fly without having to tamper with the base file's dimensions

So Wildgoosespeeder (talk) shared this nifty template that TCRF has: tcrf:Template:CSS image crop, which allows images to be displayed in mainspace at a cut-out size from how they are on the image files themselves. This has two utilities: one is shrinking to a relevant entity in group textures such as this oneMedia:M&SatL2012OG Wii audience.png, and the other is to avoid blank space without having to crop the raw graphic parameters - thus allowing best-of-both-worlds for the previous proposal I attempted (and failed), as it satisfies the OCD itch of avoiding bad and/or inconsistent crops on the base files without taking up unnecessary space where the images are actually used. It also removes a lot of unnecessary work actually cropping/uncropping images since you don't have to save them to a machine/web address to upload a new version - you can just put in the parameters you want and go from there.

Proposer: Doc von Schmeltwick (talk)
Deadline: December 11, 2024, 23:59 GMT

C-S-Yes

Doc von Schmeltwick (talk) - Goes without saying I think this is a good idea.
Super Mario RPG (talk) Sounds like a reasonable compromise.
Jdtendo (talk) It's better to crop an existing image programmatically than having to upload a cropped version for a specific use case.

No new template

Comments on CSS image crop

This appears to be similar to a template I have made in order to crop images to perfectly squared off icons for uses on pages such as Pipe Frame (e.g. displaying Mii Racing Suit icons in the same table as other character icons); however, the version you're presenting seems to include more options. I'm not gonna vote yet, but so far I don't see the harm to have this other template too. rend (talk) (edits) 06:42, November 27, 2024 (EST)

Create an article named "MarioWiki:Staff"

I'd like there to be an article on the staff. It should say like, the current admins, the current patrollers, the former admins and patrollers, the 'Shroom staff, the former 'Shroom staff, the forum staff and the former forum staff. I's just like to keep in mind who contributes to this wiki. I mean, like, who "officially" contributes, you know? Weegie baby (talk) 05:44, November 28, 2024 (EST)
Proposer: Weegie baby (talk)
Deadline: December 12, 2024, 23:59 GMT

Support

Oppose

Altendo (talk) We already have dedicated staff pages for patrollers, administrators, bureaucrats, and the proprietor. No need for this page to be made unless all of these pages are consolidated here.