MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
m (→‎List of Talk Page Proposals: Settled and failed)
Line 113: Line 113:
#{{User|Burningdragon25}} Per both on this case!
#{{User|Burningdragon25}} Per both on this case!
#{{User|Magikrazy}} per
#{{User|Magikrazy}} per
#{{User|Stonehill}} Per Binarystep.


====Oppose====
====Oppose====

Revision as of 10:52, April 22, 2015

Image used as a banner for the Proposals page
Current time:
Sunday, January 5th, 05:10 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 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

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 ON/OFF Conveyor Belt with Conveyor Belt, PopitTart (ended January 1, 2025)

List of Talk Page Proposals

Writing Guidelines

None at the moment.

New features

Create Template:organization-infobox

I've noticed that pages on organizations or groups either don't use infoboxes, or use Template:species-infobox (Snowmad and Tiki Tak Tribe were the pages I first noticed this on), listing species employed by the organization as sub-species, which looks...odd. Besides, we have infoboxes for other things, like locations, organizations aren't any less important.

Proposer: Binarystep (talk)
Deadline: April 23, 2015, 23:59 GMT

Support

  1. Binarystep (talk) Who opposes their own proposal?

Oppose

Comments

We already have one.--Vommack (talk) 17:18, 16 April 2015 (EDT)

That's for RL companies, so it wouldn't be an even worse fit. Although in all honesty, as long as people aren't stupid and only use the "first/latest appearances" and "notable members" headers and not the ones that make no sense, {{species-infobox}} works fine. But I also suppose a different template wouldn't hurt, seeing as we also have {{character-infobox}}, {{item-infobox}}, {{location-infobox}} and even {{form-infobox}}, among others. But what exactly do you (Binarystep) want as the new template? It's not good enough to just ask us to approve something without even a vague clue about what you have in mind. - Walkazo 17:23, 16 April 2015 (EDT)
Oh. Yeah, that makes more sense than what I was thinking. The species infobox still work alright though.--Vommack (talk) 17:24, 16 April 2015 (EDT)
Maybe we should use the same template as the one which is used by the Koopalings for the Tiki Tak Tribe, but for the snowmad, I'm not sure...--LudwigVon Sig.png(TALK) 17:27, 16 April 2015 (EDT)

I'm not good enough at HTML to make an example, but here are the parameters I'd want it to have:

  • leader - the character in charge of the organization (e.g. Bowser for Koopa Troop)
  • members - notable characters employed by the organization (e.g. Bashmaster for Snowmads)
  • employed_species (probably needs a better name) - species frequently employed by the organization (e.g. the various Tikis for the Tiki Tak Tribe)
  • first_appearance - self-explanatory
  • latest_appearance - self-explanatory

Binarystep (talk) 17:35, 16 April 2015 (EDT)

"member_species" might be a better name. Also, for "leader", what happens if leadership changes over the course of a game or going from backstory to a game? And I don't mean things like Bowser getting temporarily usurped but getting back control of the Koopa Troop by the end - more like odd situations like the Shroobs where Princess Shroob was more of an interim leader for the majority of the game, or coups that actually stick. Would both leaders get listed, with parenthesis saying "(first)"/"(former)"/"(current)"/"interim", etc.? And in which case, should that header perhaps read "leader(s)" (but still be coded "leader" for simplicity)? - Walkazo (talk)
Either list the most recent leader only, or list multiple ones with brackets to clarify. Binarystep (talk) 20:10, 16 April 2015 (EDT)

Use "wide image" templates for level maps and the like

In pages about levels or worlds such as this, this and this, since the images showing the maps are wide, they are displayed in a very small size, making them hard to see clearly unless you click the image.

Well, Wikipedia has a {{Wide image}} template, which can be useful for cases like these. We could use both the 100% wide and 45% (or another size) wide variations, depending on the case.

Proposer: Mr. Ice Bro. (talk)
Deadline: April 25, 2015, 23:59 GMT.

Support

  1. Mr. Ice Bro. (talk) My proposal.
  2. Binarystep (talk) Per Mr. Ice Bro.
  3. Walkazo (talk) - Per proposal: scrollboxes for images can be pretty handy.
  4. Andymii (talk) I love this idea! It makes it so one does not have to click on an image to enlarge it; plus, you get a clearer image.
  5. Burningdragon25 (talk) A great idea indeed! I'll approve this proposal with a per all!

Oppose

Comments

Removals

None at the moment.

Changes

Merge post-Special Zone enemies or Split Goomba (SMW:SMA2) and Pokey (SMW:SMA2)

It seems a little incongruous that the Super Mario World enemy skins are split but the Super Mario Advance 2-exclusive ones are not. At the same time, besides the alternate names in the SNES version, there isn't any real sign to consider these different enemies. I think the case for merging is stronger, but I'll leave the option to instead split the rest of them.

Proposer: LinkTheLefty (talk)
Deadline: April 24, 2015, 23:59 GMT

Merge post-Special Zone enemies to original enemy articles

  1. LinkTheLefty (talk) It was always an aesthetic difference to begin with, and merging eliminates at least one conjectural-titled article.
  2. Time Turner (talk) It's true that some sources individualize them, namely the SMW credits and the Mario Mania guide, but these are nothing more than reskins. There are absolutely no differences between them besides the way they look. Also, if them being recognized as individual enemies is what we use as our justification, that'd be quite a slippery slope to follow, considering other enemies that are also individually recognized (case in point, the Green/Red Koopas).
  3. Burningdragon25 (talk) I'm going to approve this one because they are part of the original enemies so, per all!
  4. SuperYoshiBros (talk) I was actually planning on proposing this a while ago, but never got around to it. Per all.
  5. Binarystep (talk) Per all.

Split Goomba (SMW:SMA2) from Galoomba and Pokey (SMW:SMA2) from Pokey

Leave alone

Comments

Exactly how many articles are being affected here? Merging a lot of uniquely-titled and different-looking things could potentially lose us search traffic... And please provide links, instead of expecting everyone to run around searching for the relevant pages and sections themselves: it's literally part of Rule 1 at the top of the page. - Walkazo (talk)

I don't think the search traffic argument holds water in this case. People aren't googling en-masse for obscure enemies sprite-swaps featured in one game, and if they do, they're very likely to have heard of the wiki through other means. --Glowsquid (talk) 22:36, 17 April 2015 (EDT)
@Time Turner - Mario Mania is kind of vague about it, although it does imply that a bit with the "A New Cast" heading at the end.
@Walkazo - If we go with the first option, the following articles are affected: Jumping Pumpkin Plant, Pidgit Bill, Mask Koopa, and Para Mask Koopa (the latter being the conjectural one I mentioned). If we go with the second option, it will keep these pages split and also add the enemies changed in the Game Boy Advance port - the sunglasses "Goomba" (as it was called) and its derivatives, and the stone-like Pokey. The third option, which I've mistakenly left out before, just keeps everything the way it is. LinkTheLefty (talk) 23:02, 17 April 2015 (EDT)

Staying neutral for now... On one hand, they look different and are officially named. On the other hand, the guide that named them is the same guide that acted like every behavior of Chargin' Chuck was its own species. If these are going to be merged, shouldn't the different types of Boo Buddies (except Block, as it does something other than move differently) be merged as well? Binarystep (talk) 23:37, 17 April 2015 (EDT)

Chargin' Chucks and Boo Buddies could also probably be addressed at some point as they might be considered another example of incongruity, but this proposal is specifically about the enemies whose graphics change by completing the Funky course, not including ones given separate identification in guide material. It's not quite the same thing, especially since Chargin' Chucks and Boo Buddies have different interactions with the player. LinkTheLefty (talk) 00:02, 18 April 2015 (EDT)

Stop Listing Sub-Species on Generic Real-World Species Pages

I've noticed that a lot of species pages (like Cooligan or Snaps to give two examples) are listed as "sub-species" of generic real-world species (e.g. Bee, Crab, Penguin), instead of being labeled independent species. At first, this makes sense, as they're clearly based on said species, but if you consider that we don't call Koopas a sub-species of Turtle or Goombas a sub-species of Mushroom, it starts to look inconsistent. I've also noticed the reverse happening, where real-world species articles have long sub-species sections consisting of every species that resembles it, even though that is literally not what "sub-species"/"species origin" means at all. While I'm not saying we should delete all real-world species pages (though the ones that consist of "background thing what looks like species" should probably be removed), I don't think we should list species from the games as being directly related to them, as there's a difference between a real-life inspiration and an in-universe relation.

tl;dr not everything has to be a subspecies of something, infoboxes don't have a minimum length.

Proposer: Binarystep (talk)
Deadline: May 3, 2015, 23:59 GMT

Support

  1. Binarystep (talk) Per my proposal.
  2. Time Turner (talk) Per Binary.
  3. Burningdragon25 (talk) Per both on this case!
  4. Magikrazy (talk) per
  5. Stonehill (talk) Per Binarystep.

Oppose

Comments

Note that real-world species could still have "Related Species" sections, and list species based on them there. Binarystep (talk) 20:03, 19 April 2015 (EDT)

Miscellaneous

None at the moment.

Retrieved from "https://www.mariowiki.com/index.php?title=MarioWiki:Proposals&oldid=1826914"