MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
Line 166: Line 166:
#{{User|Doc von Schmeltwick}} Yes, per what I said then
#{{User|Doc von Schmeltwick}} Yes, per what I said then
#{{User|Scrooge200}} Evil Dinorsaur should say it all, really.
#{{User|Scrooge200}} Evil Dinorsaur should say it all, really.
#{{User|AlexBot2004}} Per proposal.


====Comments====
====Comments====

Revision as of 14:56, May 16, 2021

Image used as a banner for the Proposals page

Current time:
Saturday, January 11st, 04:54 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 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 {{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)
Split image categories into separate ones for assets, screenshots, and artwork, Scrooge200 (ended January 5, 2025)
Establish a consistent table format for the "Recipes" section on Paper Mario item pages, Technetium (ended January 8, 2025)

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 ongoing talk page proposals

Template:TPPDiscuss Template:TPPDiscuss

Unimplemented proposals

# Proposal User Date
1 Decide how to cover recurring events in the Mario & Sonic series BBQ Turtle (talk) July 17, 2018
2 Reorganize and split Gallery:Toys and other Merchandise galleries Results May Vary (talk) July 30, 2019
3 Split all multi-items in the Mario Kart series Archivist Toadette (talk) October 12, 2019
4 Include information on Construction Zone for the rest of the Mario vs. Donkey Kong series Koopa con Carne (talk) November 24, 2019
5 Split backwards somersault info and merge it to Backflip Doc von Schmeltwick (talk) February 26, 2020
6 Split the attacks from Paper Mario: Sticker Star and Paper Mario: Color Splash Scrooge200 (talk) July 4, 2020
7 Split the enemy variants from Wario World Koopa con Carne (talk) July 11, 2020
8 Split the item lists from Super Mario RPG: Legend of the Seven Stars Doc von Schmeltwick (talk) July 12, 2020
9 Clean up Category:Undead and Category:Deceased Pokemon (talk) August 6, 2020
10 Reorganize images in levelboxes pertaining to games with remakes, remasters, etc. DarkNight (talk) September 30, 2020
11 Create articles for minor locations in Super Mario Sunshine The Mansion (talk) October 30, 2020
12 Create an article for Cheese the Chao BBQ Turtle (talk) November 25, 2020
13 Create an article for Froggy BBQ Turtle (talk) November 25, 2020
14 Split the tour appearances of Mario Kart Tour courses Koopa con Carne (talk) March 5, 2021
15 Use indicators for pre-release images Scrooge200 (talk) March 27, 2021
16 Merge Birdo (species) with Birdo Hewer (talk) April 23, 2021
17 Split Black Shy Guy (Yoshi's Story) from Black Shy Guy Doc von Schmeltwick (talk) May 1, 2021

New features

None at the moment.

Removals

None at the moment.

Changes

Apply usual naming rules to Mario Kart course names

According to MarioWiki:Naming, this is how we handle the naming of Mario Kart courses that share a name with other subjects:

  • For Mario Kart courses, console abbreviations are used as the identifier whenever possible to match the retro course naming convention (e.g. Daisy Cruiser (GCN)).
  • Due to the Mario Kart 8/Deluxe multi-console situation, the identifier "MK8" is used until confirmation of anything else (e.g. Rainbow Road (MK8)).

The guideline enforces a compromise between our general naming rules and Nintendo's own in-game convention of affixing a console abbreviation to classic courses. In the case of Mario Kart 8 courses, it specifically requests using a game abbreviation as an identifier, whereas another rule states we should generally use the expanded form of the game's title. Neither part of this guideline appears to be justified, they contradict other rules, and read like a remnant of the wiki's bumbling pre-2010 days.

This proposal aims to make our naming rules consistent across the board, applying a "race course" or expanded game-of-origin identifier to Mario Kart course articles instead of the aforementioned. Doing this would prevent confusing situations such as the article for the Donut Plains 1 racetrack from Super Mario Kart being notated “SNES” despite the other Donut Plains 1 subject also originating from an SNES game.

Proposer: Koopa con Carne (talk)
Deadline: May 28, 2021, 23:59 GMT

Support

  1. Koopa con Carne (talk) per proposal.
  2. Archivist Toadette (talk) It wouldn't hurt to at least try. Also, using the normal identifiers for the GameCube and DS battle courses feels like it's too rigid of an exception.

Oppose

  1. Hewer (talk) I don't really see anything wrong with the way we do it right now, I think having an exception in the policy to name things like how Nintendo does is fine and I would prefer it to using generic identifiers. Also, I don't think it matters if this contradicts other rules, since the page itself addresses this by making it very clear that this is an exception aiming to match the way Nintendo does it. The way I see it, this is the least confusing because it uses terminology found in the games themselves. As for using 'MK8', I think it's a decent compromise since the games haven't given an official console identifier to those tracks yet, though I would consider changing it to 'Wii U' or something similar, or just using normal identifiers specifically for the Mario Kart 8 tracks since we're not trying to replicate Nintendo's way of doing it in that case.
  2. Keyblade Master (talk) Per Porplemontage's comment.
  3. Duckfan77 (talk) Per all.
  4. Waluigi Time (talk) Per Porplemontage. If anything, we should probably wait until MK8 retro tracks actually appear to see what Nintendo calls them to see if there really is an "inconsistency" here.

Comments

@Hewer: The current naming scheme is confusing by all accounts. The proposal was updated to address your statement. -- KOOPA CON CARNE 11:25, May 15, 2021 (EDT)

It is the way it is because Nintendo is essentially providing an identifier for us when they do retro courses. If a person is playing a newer game and look up a retro course, they will probably search how it is shown in the game (e.g. "SNES Rainbow Road") and if they see the article title as "Raindow Road (SNES)" on Google, that makes a lot of sense. "Raindow Road (Super Mario Kart)" isn't great because it doesn't match that extra piece of info Nintendo is attributing to the course, the user might not even know the title for the SNES game, and the course isn't just appearing in Super Mario Kart - it's appearing in the newer game as well. --Steve (talk) Get Firefox 11:40, May 15, 2021 (EDT)

This sounds like trying to fit a square tile into a round hole. Nintendo’s own convention isn’t compatible with our rules and trying to integrate it as such leads to situations like the Donut Plains article doublet I mentioned in the proposal. Also, the “these courses are not exclusive to one game” justification can be extended to electronic systems too; SNES Donut Plains 1 appears on SNES, DS, and mobile systems, so it’s not exclusive to one system like the identifier implies. -- KOOPA CON CARNE 13:14, May 15, 2021 (EDT)
If their conventions weren't compatible with our rules then we probably wouldn't have incorporated them into our rules. Hewer (talk · contributions · edit count) 14:17, May 15, 2021 (EDT)
And yet, here we are. -- KOOPA CON CARNE 14:36, May 15, 2021 (EDT)
One thing worth mentioning is that Nintendo GameCube (battle course) and Nintendo DS (battle course) are somehow exceptions to this rule. I still vividly remember contacting Porplemontage about this three years ago, and while his response was adequate enough (it would be "too dumb" to use "Nintendo DS (DS)"), I don't find it a good excuse to keep the policy exception. And there's also Mario Kart Live: Home Circuit race course layouts which also have their own articles; so would World 1-1 (race course) become "World 1-1 (MKLHC)"? Like Koopa con Carne keeps saying, there's too much confusion with this policy. Toadette icon CTTT.pngFont of Archivist Toadette's signature(T|C) 14:47, May 15, 2021 (EDT)
I think using normal identifiers for Mario Kart Live: Home Circuit specifically is fine, since there's nothing official to try to match there whereas there is for the other games besides Mario Kart 8. Hewer (talk · contributions · edit count) 16:02, May 15, 2021 (EDT)

I don't want to lose the "SNES" element in the article title for retro courses since I definitely consider that to be part of the official title, as well as for purposes of SEO and people finding the article they're looking for. Here is my counter-proposal: For tracks which have appeared as retro courses, move them to "SNES Donut Plains 1" format. That doesn't conflict with the level since it's a different title. For the rest, use traditional game identifiers. This creates an inconsistency from track article to track article, but I believe it is the most technically correct solution based on how Nintendo names them, and it eliminates the "MK8" guess. --Steve (talk) Get Firefox 15:23, May 15, 2021 (EDT)

I would support that, it stays consistent with how Nintendo does it and technically goes with our policy of using the most recent English name. Hewer (talk · contributions · edit count) 16:02, May 15, 2021 (EDT)

Miscellaneous

Citing WildBrain

A while ago, a proposal was made about using closed captions of the Super Mario cartoons from third-party contractors hired by WildBrain, which we opted to decline because A) WildBrain has been notorious for stealing chunks of information away from us without attribution, B) WildBrain has been entirely unprofessional with their handling of the Super Mario cartoons, and C) closed captions were unreliable compared to the actual script.

However, although we may have disallowed using the closed captions as a source, we still have areas of information that directly source themselves to WildBrain. Similar to how we prohibited using the English Super Mario Encyclopedia over similar issues, we should disallow the usage of WildBrain as a source for these reasons I listed above, and therefore our sources for the Super Mario cartoons should only pertain to the staff involved with the cartoons and DiC Entertainment themselves.

Proposer: PanchamBro (talk)
Deadline: May 23, 2021, 23:59 GMT

Allow all parts of WildBrain to be used as a source

Allow some parts of WildBrain to be used as a source

Do not allow WildBrain to be used as a source

  1. PanchamBro (talk) Per proposal.
  2. Waluigi Time (talk) Per proposal.
  3. Keyblade Master (talk) Per pretty much everything that was said in the aforementioned proposal.
  4. Power Flotzo (talk) We don't need redirects like the now-deleted "Ahehehauhe." Per all.
  5. Doc von Schmeltwick (talk) Yes, per what I said then
  6. Scrooge200 (talk) Evil Dinorsaur should say it all, really.
  7. AlexBot2004 (talk) Per proposal.

Comments

I think we should allow WildBrain's names to be redirects since the whole point of redirects is to be helpful to readers and there might be some readers who would find those redirects helpful. For example, someone might see the 'Ahehehauhe' clip on YouTube and search it up here in search of information on the clip without knowledge of the episode name. Otherwise, I understand why we decided not to cite WildBrain, but I think that we should adjust our naming policy to specify that WildBrain can't be cited after this proposal (depending on its result) like we did with the Super Mario Bros. Encyclopedia. Hewer (talk · contributions · edit count) 15:02, May 16, 2021 (EDT)

I see your point, though I do question if we have to therefore include hundreds of redirects for any particular clip made of any episode, especially since clips can named by anyone, WildBrain included. I should also point out that the 'Ahehehauhe' clip only attached 4k views on YouTube, which doesn't justify the demand for these redirects. -- PanchamBro (talkcontributions) 15:24, May 16, 2021 (EDT)
According to MW:REDIRECTS, a redirect is justified if there is a chance someone would find it helpful, which I feel there is in this case. This policy also states that redirects should only be deleted if they are too general or too silly, and redirects like 'Ahehehauhe' don't fall under either of those categories since it's clear what they're referring to and what a reader searching it is most likely looking for, and they come from a source that is, by at least one definition, official. Also note the policy says alternate names as redirects are fine. So going off of our policies there doesn't seem to be a good reason for deleting these redirects, and there's not really a downside to creating a large amount of redirects anyway. Hewer (talk · contributions · edit count) 15:43, May 16, 2021 (EDT)