MarioWiki:Proposals: Difference between revisions
Mario4Ever (talk | contribs) m (→Support) |
|||
| Line 183: | Line 183: | ||
#{{User|Time Turner}} Per proposal. | #{{User|Time Turner}} Per proposal. | ||
#{{User|Superchao}} Per proposal. | #{{User|Superchao}} Per proposal. | ||
#{{User|Mario4Ever}} Per proposal. | |||
====Oppose==== | ====Oppose==== | ||
Revision as of 16:51, April 2, 2018
|
|
Friday, January 3rd, 03:39 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.
|
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
- Merge Cascading Stone, vanishing platform, and moon platform with Falling Platform (discuss) Deadline: January 4, 2025, 23:59 GMT
- Rename the NES Template (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
- What to do about Wiggler Family (discuss) Deadline: January 11, 2025, 23:59 GMT
- Repurpose Template:Stub (discuss) Deadline: January 12, 2025, 23:59 GMT
- Split the Ink Bomb (discuss) Deadline: January 12, 2025, 23:59 GMT
- Split the Giant Bowser battle Refreshroom (discuss) Deadline: January 12, 2025, 23:59 GMT
- Keep or Delete File:Spiny Shell PMTTYD.png (discuss) Deadline: January 12, 2025, 23:59 GMT
- Tighten Category:Thieves (discuss) Deadline: January 14, 2025, 23:59 GMT
- Delete The Legend of Zelda (television series) (discuss) Deadline: January 16, 2025, 23:59 GMT
- Merge individual Special Shots from Mario Hoops 3-on-3 into Special Shot (Mario Hoops 3-on-3 and Mario Sports Mix) (discuss) Deadline: January 16, 2025, 23:59 GMT
- Remove “references” from the front page header (discuss) Deadline: January 16th, 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) |
| Stop integrating templates under the names of planets and areas in the Super Mario Galaxy games, Nintendo101 (ended December 25, 2024) |
Talk page proposals
| Split all the clothing, Doc von Schmeltwick (ended September 12, 2021) |
| Split machine parts, Robo-Rabbit, and flag from Super Duel Mode, Doc von Schmeltwick (ended September 30, 2022) |
| Make bestiary list pages for the Minion Quest and Bowser Jr.'s Journey modes, Doc von Schmeltwick (ended January 11, 2024) |
| Allow separate articles for Diddy Kong Pilot (2003)'s subjects, Doc von Schmeltwick (ended August 3, 2024) |
| Create articles for specified special buildings in Super Mario Run, Salmancer (ended November 15, 2024) |
| Expand and rename List of characters by game to List of characters by first appearance, Hewer (ended November 20, 2024) |
| Merge False Character and Fighting Polygon/Wireframe/Alloy/Mii Teams into List of Super Smash Bros. series bosses, Doc von Schmeltwick (ended December 2, 2024) |
| Make changes to List of Smash Taunt characters, Hewer (ended December 27, 2024) |
| Merge Candy Block with Hard Block, Nintendo101 (ended December 31, 2024) |
| Merge ON/OFF Conveyor Belt with Conveyor Belt, PopitTart (ended January 1, 2025) |
List of talk page proposals
Template:TPPDiscuss Template:TPPDiscuss Template:TPPDiscuss
Unimplemented proposals
Writing guidelines
None at the moment.
New features
None at the moment.
Removals
None at the moment.
Changes
Add a section to MarioWiki:Naming regarding technical restrictions
I'm surprised no one has talked in depth about this yet. Sure, we don't have that many technically restricted names, but we still have some, so I think we should set in stone a policy for these titles. Take the castle levels from Super Mario World as an example. "#1 Iggy's Castle" is located at "Iggy's Castle" rather than "1 Iggy's Castle"; while the former title is fine, it might still cause some initial confusion for the newer readers. Basically, what I'm proposing is that we start officially use closely-matched titles for subjects if the correct title is technically restricted.
A draft of the proposed text can be found here.
Also, if you're wondering, Porplemontage green-lighted this proposal.
Proposer: Toadette the Achiever (talk)
Deadline: April 5, 2018, 23:59 GMT
Support
- Toadette the Achiever (talk) Per proposal.
- Alex95 (talk) - Per proposal.
- YoshiFlutterJump (talk) Per proposal.
- TheFlameChomp (talk) Per proposal.
- Yoshi the SSM (talk) Per proposal.
- Doc von Schmeltwick (talk) Sounds good to me! Per proposal.
- Mister Wu (talk) Considering that we can't use the actual name, the closest match surely makes sense.
- BBQ Turtle (talk) Per all, this just seems like the sensible thing to do anyway.
- Baby Luigi (talk) Per all.
- Wildgoosespeeder (talk) The proposal is about allowing as many characters in the original title as possible, if the suggested title has technical issues. When such a case occurs, use the
{{DISPLAYTITLE}}MediaWiki Magic Word to correct the title.#in URLs are used for linking to headers in a page name, like this example. Even forcing URL encoding brings up an error. [1] I couldn't get MediaWiki to parse this normally, so a forced URL is used to demonstrate.
Oppose
Comments
So if this succeeds, what will happen to the Iggy's Castle article? (Also, remind me for when I start my own franchise, to name a character "<[[#klunk]]>''," symbols included, just to mess with the ensuing wiki.) Doc von Schmeltwick (talk) 02:04, 29 March 2018 (EDT)
- It'll be moved to "1 Iggy's Castle", with the display title unchanged so it still shows the proper title. MediaWiki doesn't like certain symbols in page titles, so have fun with that hypothetical wiki if it comes ;)
11:09, 29 March 2018 (EDT)
Just thought about it but how about a notice template for such pages? --Wildgoosespeeder (talk) (Stats - Contribs) 17:00, 29 March 2018 (EDT)
- That's not needed unless even {{DISPLAYTITLE}} cannot display the correct title.
(T|C) 10:56, 31 March 2018 (EDT)
Give the seven boss Tikis from DKCR their own articles
Because the rest of their official names have just been discovered in a datamine of the original game.
Proposer: BooDestroyer (talk)
Deadline: April 5, 2018, 23:59 GMT
Support
- BooDestroyer (talk) Need I say more?
- YoshiFlutterJump (talk) These guys are like the Seven Notorious Koopalings. Each one not only has a name, but is also a character and a boss. It’s not quite like Gary or Johnson (whose articles SHOULD be deleted) or even the Sammer Guys. The Tikis are characters—major boss characters at that, and not just minor NPCs. One of them, Kalimba, even has a Smash 4 trophy. And the fact that the Tikis only appear in a single DK game should not stop us from giving them articles.
Oppose
- Time Turner (talk) A name, in and of itself, is not enough to substantiate having separate articles (see: List of Sammer Guys). Is there another reason they should have articles?
- Alex95 (talk) - Per Time Turner. They may all have a name, but they aren't diverse enough (they all do the exact same thing) to justify individual articles.
- TheFlameChomp (talk) Per Time Turner.
- Toadette the Achiever (talk) Per all. Plus, they're not even fought normally at all, which that case would guarantee articles.
Comments
I forgot to mention, but in order, they're called: Kalimba, Maraca Gang, Gong-Oh, Banjo Bottom, Wacky Pipes, Xylobone, and Cordian. BooDestroyer (talk) 18:07, 29 March 2018 (EDT)
@YoshiFlutterJump They are different from the Koopalings in that the Koopalings are:
- A: Bosses themselves
- B: Characters with actual personality
also, why should Gary or Johnson not have articles? They deserve articles as much as Otto or Heronicus. Doc von Schmeltwick (talk) 23:05, 30 March 2018 (EDT)
- Let me tell you one thing. The Seven Notorious Koopalings (that’s what Minion Quest calls them) hardly had personalities before Paper Jam (to the extent of having NO dialogue), and we had articles for them long before then. While the Tikis are not bosses, they possess bosses and are key to the story. As for your second point...minor NPCs shouldn’t get articles just because they have names. The Tikis are not minor, though. -YFJ (talk · edits) 23:18, 30 March 2018 (EDT)
- Even just regarding Super Mario Bros. 3, the Koopalings had enough diversity to justify their own articles if the wiki was around then. They each had the same role, but different names and abilities. Regarding the SMB3 cartoon as well, they also had different personalities. The same cannot be said for these Tikis.
- Gary and Johnson, according to MarioWiki:Minor NPCs, their articles are valid. 23:23, 30 March 2018 (EDT)
- Saying the Koopalings didn't have personalities before Paper Jam is outright wrong, remember their individual speech balloons in the SMB3 manual? The depictions in the cartoons and comics? Their pre-battle behavior in NSMBW? The Tikis all act exactly the same, and are only ever on screen for like 5 seconds each, and have no dialog. Doc von Schmeltwick (talk) 23:27, 30 March 2018 (EDT)
I fail to see how character personalities is any sort of viable argument against article creation. I can get on board with their extremely minor role and their appearance, but not their personality. 
Ray Trace(T|C) 00:54, 31 March 2018 (EDT)
I should point out one thing: we don’t even have an article for them as a group. Tiki Tak Tribe just covers every enemy in the game, and is not devoted to the boss Tikis. At the very least, we need an article for them as a group. -YFJ (talk · edits) 13:19, 31 March 2018 (EDT)
Smash Bros. Articles: What Stays and What Goes?
The previous Super Smash Bros. proposal allowed us to justify previous exceptions to Smash coverage (i.e. the stage hazards and Smash Taunt characters) and paved a path for future exceptions. After the discussion on the forums, this proposal will outline exactly what further exceptions will be made, as in which pages will be merged and which pages will remain intact. With that out of the way, let's dive in!
- Fighters: No changes are planned.
- Stages: No changes are planned.
- Items: No changes are planned.
- Bosses: The inconsequential bosses of Subspace Emissary, including Duon, Galleom, Meta Ridley, Porky, Porky Statue, and Rayquaza, will be merged to a page specifically for the mode's bosses. Tabuu and Ancient Minister remain separate due to significant relevance to the story, with Tabuu also being the final boss. By that same token, Crazy Hand, Master Hand, and Master Core will remain due to also being final bosses. Separately, Ridley will stay due to multiple appearances across more than one game.
- Enemies: The Adventure Mode, Subspace Emissary, and Smash Run enemies will be merged into separate lists (i.e. "List of Smash Run enemies" and so on), exactly like the ones that existed previously.
- Stage hazards: Despite my previous comment about stage hazards being exceptions, there are exceptions to that, including Dark Emperor, Flying Man, Metal Face, and Yellow Devil. These pages will be merged to the stages that they respectively appear in.
- Assist Trophies: They will be merged to Assist Trophy, as it was previously.
- Pokémon: They will be merged to Pokémon, as it was previously.
- Moves: Special moves will be merged to the character that uses them (e.g. Mach Tornado, Drill Rush, Shuttle Loop, Dimensional Cape, and Galaxia Darkness will be merged to Meta Knight; for moves that are used by multiple fighters, the information will be split between them, such as with Shield Breaker), as it was previously.
Note that this proposal isn't completely exhaustive: there are scattered pages like List of Mii Outfits and List of bonuses in Super Smash Bros. that also deserve scrutiny, but considering the subtle differences between each of them, it'd be best to tackle those individually and not overburden this proposal. Still, there's plenty that's already being covered here. It's a lot to take in, but these are changes that should be taken for all the same reasons as before. It's disingenuous to treat the Super Smash Bros. series as if its Mario content is even close to that of existing crossovers with the franchise like Fortune Street and Mario & Sonic. The wiki should strive to reflect that.
Proposer: Time Turner (talk), with input from Superchao (talk)
Deadline: April 9, 2018, 23:59 GMT
Support
- Time Turner (talk) Per proposal.
- Superchao (talk) Per proposal.
- Mario4Ever (talk) Per proposal.
Oppose
Comments
Miscellaneous
Do not create Super Mario Odyssey sublocation pages
The current Super Mario Odyssey Kingdom nav-template has (mostly red) links for all the named locations within every kingdom in the game. I think each one of these locations getting an article is a bad idea.
While some of these locations are pretty big and unique, like the Deep Woods and Snowline Circuit, most of them are simply extentions of the main world or too small and not so relevant by themselves, and presenting them disconnected from each other would make these pages feel short on content. Island in the Sky (Bowser's Castle), Rocky Mountain Summit (Forgotten Isle), Heliport (New Donk City), Glass Palace (Bubblaine) and Salt-Pile Isle (Mount Volbono) are some examples of locations which are, at most, glorified platforms with a Checkpoint Flag on/near them. There are also three Tostarena Ruins locations, three Water Plaza locations, two Iron Path locations; having an article for each one is unnecessary as they are part of a whole rather than defined places (which is also the case of things like the Waterfall Basin and Stone Bridge in Fossil Falls and the Tostarena Northwest Reaches).
I believe there is enough space for information about these areas in the actual kingdom articles. An overview (what it is, where it is on the map, general layout, what enemies and characters are there) can be written in five lines or so. We do not have articles for Super Mario Galaxy planets, not even for the giant, named ones like the Haunted Mansion in Ghostly Galaxy. Even if (unlike the planets) the SMO locations are named in-game, they are as relevant to their game as planets are to SMG.
So, I propose:
- Do not create any Odyssey sublocation article: Put the information about these spots in the kingdom articles only.
- Create separate articles for notable sublocations only: Another possibility is to create separate pages for well-defined structures and areas which are unique within their kingdom: the Top-Hat Tower, Tostarena Town, Tostarena Ruins (as a whole), Jaxi Ruins, Inverted Pyramid, Deep Woods, Water Plaza (as a whole), Underground Power Plant, Snowline Circuit, Underground Moon Caverns keep/get their articles. An overview of every location (notable or not) would go on the main article.
- Leave everything as it is: Create articles for every Checkpoint Flag location of the game.
Proposer: Shiny K-Troopa (talk)
Deadline: April 9, 2018, 23:59 GMT
Do not create any Odyssey sublocation article
- Shiny K-Troopa (talk): Per my proposal.
Create separate articles for notable sublocations only
- Shiny K-Troopa (talk): Per my proposal (I'm fine with either).
