MarioWiki:Proposals
|
|
Tuesday, March 11st, 16:56 GMT |
|
|
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. 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 essentially its own mini-proposal with a deadline and Support/Oppose subheadings. The rules above apply to each option as if it were a its a 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 the status quo 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])====
A poll proposal is archived after all of its options have settled, and it is listed as one single proposal in the archive. The proposal is considered to have "passed" if one or more options were approved by voters (resulting in a change from the status quo), and it is considered to have "failed" if all options were rejected by voters and no change in the status quo was made.
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
- Split Ossan from Captain Rainbow (discuss) Deadline: March 12, 2025, 23:59 GMT
- Split Super Mario Maker helmets from Buzzy Shell and Spiny Shell (red) (discuss) Deadline: March 12, 2025, 23:59 GMT
- Increase the maximum amount of personal images to 10 per user (discuss) Deadline: March 12, 2025, 23:59 GMT
- Consider the POW Block item in Mario + Rabbids Sparks of Hope to be a Red POW Block (discuss) Deadline: March 12, 2025, 23:59 GMT
- Properly define Brown Yoshi (discuss) Deadline: March 13, 2025, 23:59 GMT
- Split the Giant Mushroom/Refreshroom from BIS that is merged with the normal Mushroom into its own article (discuss) Deadline: March 13, 2025, 23:59 GMT
- Determine what memes should be on the Internet references page (discuss) Deadline: March 15, 2025, 23:59 GMT
- Move the Adobe Flash version of Donkey Konga 2 to the "Windows" section of the list of games page (discuss) Deadline: March 15, 2025, 23:59 GMT
- Split rejected pitches and titles that never began development on the list of unreleased media into a list of proposed media (discuss) Deadline: March 16, 2025, 23:59 GMT
- Remove information on Super Mario Maker series big Para-Beetles from Heavy Para-Beetle (discuss) Deadline: March 18, 2025, 23:59 GMT
- New subsections for games in the Super Mario series (discuss) Deadline: March 18, 2025, 23:59 GMT
- Split Sal Out (WarioWare: Touched!) from Sal Out (discuss) Deadline: March 19, 2025, 23:59 GMT
- Split Space Mine from Mikey Mine (discuss) Deadline: March 19, 2025, 23:59 GMT
- Split Small Cosmic Clone from Cosmic Clone (discuss) Deadline: March 22, 2025, 23:59 GMT
- Create an article for the cat enemies in Bowser's Fury (discuss) Deadline: March 22, 2025, 23:59 GMT
- Split the enemy/obstacle ice block of Yoshi's Woolly World from Ice Block (discuss) Deadline: March 22, 2025, 23:59 GMT
- Split the Sleepy Sheep Mistake from the "normal" Mistake (discuss) Deadline: March 23, 2025, 23:59 GMT
- Split Toad (Mario Party 4) from Toad (discuss) Deadline: March 23, 2025, 23:59 GMT
- Move Big Fire Piranha to Big Fire Piranha Plant (discuss) Deadline: March 23, 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 and Super Mario Run.
| 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) |
| Use the classic and classic link templates when discussing classic courses in Mario Kart Tour, YoYo (ended October 2, 2024) |
| 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) |
| Split Mario & Luigi badges and remaining accessories, Camwoodstock (ended February 1, 2025) |
| Merge Chef Torte and Apprentice (Torte), Camwoodstock (ended February 3, 2025) |
| Merge intro/outro sections, rename Gameplay section to "Overview" for Mario Party minigame articles, ToxBoxity64 (ended March 1, 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) |
| 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) |
| Merge Wiggler Family to Dimble Wood, Camwoodstock (ended January 11, 2025) |
| Split the Ink Bomb, Camwoodstock (ended January 12, 2025) |
| Create a catch-all Poltergust article, Blinker (ended January 21, 2025) |
| Give the Cluck-A-Pop Prizes articles, Camwoodstock (ended January 31, 2025) |
| Reverse the proposal to trim White Shy Guy, Waluigi Time (ended February 8, 2025) |
| Split Animal Crossing (game), Kaptain Skurvy (ended February 12, 2025) |
| Split the modes in the Battles page, Mario (ended February 15, 2025) |
| Count ongoing serialized comics for latest appearances, Rykitu (ended March 2, 2025) |
| Split Toad wearing headphones off from Jammin' Toad, PrincessPeachFan (ended March 7, 2025) |
List of ongoing talk page proposals
Template:TPPDiscuss Template:TPPDiscuss
Unimplemented proposals
Writing guidelines
Remove non-Mario characters from the trophies, Assist Trophy, stickers, and Spirit pages
The Mario Wiki's Super Smash Bros. coverage always has been, and likely always will be, one of the most consistently controversial aspects of the wiki. In my opinion, instead of trying to solve any of these coverage issues with one large, sweeping proposal, it would be better to handle individual topics in smaller-scale proposals. This is one of them.
Basically, the longest page on this wiki as of this proposal is List of trophies in Super Smash Bros. for Wii U - something about a game which isn't even part of the Mario franchise. That's pretty insane. We have several lists, such as the Spirit page, the Assist Trophy page, the Sticker page, and the lists of trophies in _ game, which give coverage to each and every single collectable that is a part of their respective groups, even if they have absolutely nothing to do with the franchise. We don't need this. It unnecessarily bloats the pages with information not related to the wiki itself, and would make it harder for readers to access the information actually pertinent to the franchise and in turn, the wiki. No one would go to the Mario Wiki to find out what Ghirahim's spirit does. If they did, they would just go to a Smash Wiki. Basically, this non-Mario related list content just makes these pages filled to the brim with non-pertinent info that would just make a page harder to load for those who want to find actual Mario related info on a Mario Wiki, and not info about a million other gaming franchises. In short, what I propose is the following:
That any list information that isn't pertinent to the Mario or related franchises would be removed. This will affect the following pages, under this proposal:
- Assist Trophy
- Any of the "List of trophies in _" Super Smash Bros. game (will not affect Trophy (Super Smash Bros. series).
- List of Smash Run enemies
- Spirit (Super Smash Bros. Ultimate).
- Sticker (Super Smash Bros. Brawl).
This will not affect:
- The Pokémon page. The page is entirely filled with non-Mario information. Wether or not this page should be deleted is a discussion for a different proposal.
- The intro of any of these pages. The spirit page, for example, will still inform the reader about what a spirit is.
- Any fighter pages. Even if the trophy/list pages have non-Mariocontent removed, any spirit or trophy info on any fighter's page will still remain. Wether or not we should even have pages on fighters which never appeared in the Mario franchise is for another proposal.
- Any of the Super Smash Bros. game pages will remain mostly unaffected. Any changes that should be made to these is again, a subject for another another proposal.
Additional notes:
- Some redirects, such as Bonkers, may have to be deleted if they become useless after this proposal is enforced, if it passes.
- This will not remove any list info directly pertinent to the franchise (such as any Mario, Wario, Yoshi, or DK trophies).
- I have included the option to support the removal all non-Mario thing on these lists except for fighter trophies, spirits, etc for those who would rather that outcome.
- MarioWiki:Coverage will be slightly modified to reflect any changes with how we handle this content.
- This will be enforced simply by removing any parts of the list that aren't pertinent to the franchise. For example, the info about Akira's Assist will be removed from the Assist Trophy page, though the info on say, Waluigi's, or Klaptrap's Assist, will remain.
- Some of the pages affected by the proposal are featured articles. Wether or not they will still be worthy of their featured status is something to be considered after the proposal is enforced.
Proposer: Doomhiker (talk)
Deadline: March 14, 2021, 23:59 GMT
Support (including the removal of non-Mario fighter spirits, trophies, etc)
- Doomhiker (talk) Per proposal.
- TheDarkStar (talk) - per proposal
Support (excluding the removal of non-Mario fighter spirits, trophies, etc)
Oppose
- Waluigi Time (talk) Traditionally our reduction in Smash Bros. coverage has always been to reduce the prominence of information, rather than outright remove it. I don't really feel comfortable going farther. (And actually I do find myself using the Spirit page here for all of them in general, I find it more helpful that they're on one page which afaik SmashWiki doesn't have)
Comments
@Waluigi Time We shouldn't not do something because another wiki is lacking. In addition, I do see any reason to stop at removing info if there's no reason for the info to be on this wiki in the first place, and it's not like we haven't removed swaths of non-pertinent info in the past (like with how we previously had a ton of Banjo content). Doomhiker (talk)
17:19, February 28, 2021 (EST)
New features
None at the moment.
Removals
None at the moment.
Changes
None at the moment.
Miscellaneous
Split the tour appearances of every Mario Kart Tour course
Mario Kart Tour course pages currently house information related to the individual tour appearances of their respective courses such as their order of appearance in cups and their case-by-case highlighted drivers, karts and gliders. With the large number of tours that have been released and will continue to release, these pages end up having an excessive amount of highly-reccurent or similar information that may increase load times and make them uncomfortable to scroll through. To solve this issue, I propose that we split said tour appearances into separate pages related to every course. These new pages can be named something like "List of SNES Mario Circuit 1 tour appearances in Mario Kart Tour", with the console of origin mentioned beside the title as in-game, though if there are objections against this particular preference I'm adding a separate option to have the console mentioned in brackets and only for courses that share a name such as Rainbow Road (SNES) and Rainbow Road (3DS).
Proposer: Koopa con Carne (talk)
Deadline: March 5, 2021, 23:59 GMT
Support (format course titles with console prefixes like in the game)
- Koopa con Carne (talk) I prefer this option as it seems more consistent.
- Waluigi Time (talk) Per proposal.
- Doomhiker (talk) Per proposal.
- Ray Trace (talk) Per proposal.
Oppose
Comments
While I do support doing this to courses with many tour appearances, I do think that there should be a certain amount of tours that a course would have to be in to split. This is because splitting the page when the course has only appeared in one or two courses is silly: doing it only after it appeared in four or more tours would make more sense. Doomhiker (talk) 19:27, February 25, 2021 (EST)
- I think two appearances can constitute the minimum for a page. Silly as it may seem, a list with only two entries is still a list, and these pages are expected to grow steadily over time. -- KOOPA CON CARNE 19:37, February 25, 2021 (EST)
I feel like we'd run into the same problem, but on a different page. Using the Mario Circuit 1 example, there are fourteen charts with many images on them. I realize the point of this is to move the load times (which don't seem that bad) off the main Mario Circuit 1 page, but I don't feel like there's enough content to really justify doing so. Not like how Gallery:Mario was split, which is just... really large no matter what you do with it.
Regardless, if it does get to that point, we already have a policy page that agrees with you. 
00:30, February 26, 2021 (EST)
- The article size guideline specifies that pages with more than 100kb of code should “almost certainly be divided”, and going by Special:LongPages, there are already quite a few course pages that exceed that size, including but not limited to Yoshi Circuit, Waluigi Pinball (DS) and Shy Guy Bazaar. It’s evident these articles are largely occupied by charts, so naturally these should be split off before anything else; the resulting pages exceeding 100kb themselves at some point is not relevant since the article size guideline doesn’t apply to lists. This proposal aims for a consistent treatment between all course pages, so if the three aforementioned pages are to be split, the other MKT-relevant course pages should follow suit. -- KOOPA CON CARNE 01:00, February 26, 2021 (EST)
I'd get rid of the "show" collapsibility, too. We don't do that for tables and it just forces users to click on an extra link, especially unnecessary on a page dedicated to tour appearances. Unless this was already in mind. 
Mario JC 06:36, February 26, 2021 (EST)
- I find the collapsibility option to be useful at the moment as it increases the readability of an article, but I do agree it should be removed if the charts are split to different pages since they would then form about 2/3 of the content in each page and would thus require an expanded focus. -- KOOPA CON CARNE 09:48, February 26, 2021 (EST)
