MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
Line 137: Line 137:
#{{User|Icemario11}} - Per Walkazo.
#{{User|Icemario11}} - Per Walkazo.
#{{User|Mario4Ever}} Per Walkazo.
#{{User|Mario4Ever}} Per Walkazo.
#{{User|Scr7}} Per Walkazo


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

Revision as of 16:13, September 30, 2013

Image used as a banner for the Proposals page
Current time:
Sunday, December 22nd, 10:44 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 accepted (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)

Talk page proposals

Split all the clothing, Doc von Schmeltwick (ended September 12, 2021)
Split machine parts, Robo-Rabbit, and flag from Super Duel Mode, Doc von Schmeltwick (ended September 30, 2022)
Make bestiary list pages for the Minion Quest and Bowser Jr.'s Journey modes, Doc von Schmeltwick (ended January 11, 2024)
Allow separate articles for Diddy Kong Pilot (2003)'s subjects, Doc von Schmeltwick (ended August 3, 2024)
Create articles for specified special buildings in Super Mario Run, Salmancer (ended November 15, 2024)
Expand and rename List of characters by game to List of characters by first appearance, Hewer (ended November 20, 2024)
Determine how to handle the Tattle Log images from Paper Mario: The Thousand-Year Door (Nintendo Switch), Technetium (ended November 30, 2024)
Merge False Character and Fighting Polygon/Wireframe/Alloy/Mii Teams into List of Super Smash Bros. series bosses, Doc von Schmeltwick (ended December 2, 2024)

List of Talk Page Proposals

Writing Guidelines

A writing guideline for Image Maps

see here for the draft.

This Writing Guideline is meant to clear thing of when and how an Image Map page should be created. It will be created under the name MarioWiki:Image Maps. These rules only apply to real articles.

All information are present in the draft, description is present here:

The Map Images must be a map sprite from the game, screenshot, or an official map artwork because it makes the Image Map looks professional. Fan-made will make the Image Map looks fake, unofficial nor professional

Templates are only for real articles, no templates for Policy pages, Help pages, or Userpages.. However, coding can go in any other page.

Image Maps are meant only for locations, or levels. It is not good to have an Image map for characters, even if the artwork was official, it won't look neat.

Image Maps are meant to help with navigation. If image is less than 8 links, it could be embedded in the page with caption description the links. Example on the right.

From left to right: "This", "is", "an", and "example".

The Image Map's any dimension must not exceed 400 pixels, and the other one must not exceed 200 pixels. The Image Map's width in the {{Worldbox}} template must never exceed 300 pixels.
I specified the sizes depending on medium sized screens, so it does not look very small, or very big. Reason includes that if maps were larger than that then the page would look very crowded.

If the map isn't going to be put into the Worldbox template, then the map should be classed as a thumbnail and aligned to the right. However, If the map is only going to be put in the Worldbox template, it must be classed as none and it must be aligned in the center. Otherwise a variable must be declared; so if it is set to infobox,it would be aligned in the center and it would be classed as none. And if it is not set, it would be classed as a thumbnail and it would be aligned to the right.

In other word, templates like {{NSMBmap}} are put inside the {{Worldbox}} and never outside, so it is classed as none and it is aligned in the center, so it looks centered and without borders in the template. Templates like {{PMTTYDmap}} are put outsise the Worldbox template and never inside, so it is classed as thumbnail and aligned to the right. However templates like {{NSMBUmap}} are put both inside and outside, so there is a variable defining if it would be put in the Worldbox template, or would be put outside.

The template must only be put where it links to (i.e If the template only links to Template:Fakelink and Template:Fakelink, it must never be put on Template:Fakelink). That's because it is unneeded on an unrelated page.

If the article is about a subject that only appeared in the Image Map's game, the template should be put under the info-box. Otherwise the template should be put as the first line in the game's section on the article.

Explaining: {{PMTTYDmap}} links to X-Naut Fortress and The Moon.. Since X-Naut Fortress only appeared in Paper Mario: The Thousand-Year Door, the template is put under the infobox, However The Moon appeared in multiple games, so the template is put in the game's section.

For the Platformer games: in the Worlds pages, the template should be put in the map parameter of the {{Worldbox}} template (using the code |map={{templatename}}). Reason includes it unneeded to crowd the page with a template, which can be put inside the infobox template.

Last three sections describe basics of creating the template.

Use the comments section below for comments and suggestions.

Proposer: Megadardery (talk)
Deadline: September 30, 2013 23:59 GMT

Support

  1. Megadardery (talk)
  2. Yoshi876 (talk) Per proposal. Should help those new to image maps as well.
  3. Scr7 (talk) per proposal... I don't see anything bad about this, and it'd be helpful to a lot of people.
  4. Sonic98 (talk) Per all
  5. LeftyGreenMario (talk) ImageMaps will come in the future (until something renders it deprecated), and once more people know how to do it, the better. Knowledge is power.
  6. Driftmaster130 (talk) Per all.
  7. World10 (talk) I think it's a good idea, per all.
  8. Icemario11 (talk) Per all.
  9. Ultra Koopa (talk) Per LeftyGreenMario.

Oppose

  1. Iggy Koopa Jr (talk) I personally find it unneeded.
  2. Mario7 (talk) I think it is fine the way it is, and we don't need to change anything.
  3. Gonzales Kart Inc. (talk) Per Mario7.

Comments

@Iggy Koopa Jr Why? Image maps are kinda complicated, they need several rules, so it does not look messy when created. Megadardery (talk)

It is because not many image maps are made on this wiki(because unneeded), and not everyone knows how to make one. I have myself not stumbled on a messy Map, so I think rules for something already done well is unneeded. Iggy Koopa Jr (talk)

The reason of not too many ImageMaps are made on wiki mostly because people don't know how to make one, hopefully this writing guideline will put standards for making the Imagemap, that's why I made it in the first place, With many games (specially 3DS games) new today, the ImageMaps will help a lot in navigation. And I can guess that's lot of ImageMaps are coming in near future. Megadardery (talk)

New features

Make Most Maintenance Categories Hidden

An idea which was willing on my mind from long time ago. The Maintenance categories should be hidden from the categories bar on the bottom of each article. The categories bar on each article is only for main categories. Some readers may just want to navigate through the categories without contributing. And for any user that does want to see them, he could just navigate to his Preferences, in Appearance tab, down at Advanced options. Check "Show hidden categories".


List: (marked with * may need some discussion)

Proposer: Megadardery (talk)
Deadline: October, 7 2013 23:59 GMT

Support

  1. Megadardery (talk) -- Per Proposal, the categories bar should only contain real-articles related categories.
  2. Gonzales Kart Inc. (talk) Per Dardery.

Oppose

  1. Mario7 (talk) I think that these should be easily visible so that editors can quickly see that changes need to be made and visitors can see what the problem is, so they don't get a bad impression of this wiki

Comments

So, exactly why do we need to hide these categories? And wouldn't unchecking the hide option show categories that are hidden in the first place, adding more clutter? LeftyGreenMario (talk)

So the categories bar doesn't get crowded with categories unrelated to the subject itself.. as for the second question, I don't think I quite understand it. Megadardery (talk)
My question is that are there already hidden categories in the first place? You know, I'd like to know the amount of categories that are already hidden. LeftyGreenMario (talk)
Nope! There are no hidden categories yet! any hidden category will automatically go in Category:Hidden categories which I will create as soon this proposal pass. Megadardery (talk)


@Mario7 The problem can be easily seen by looking on the Notice Template which is mostly on the top of any page. And Editor can see them by checking the 'Show hidden Categories' option. Megadardery (talk)

Removals

None at the moment.

Changes

None at the moment.

Miscellaneous

Pokemon, Assist Trophies, and the SSB Templates

As of now, we have three templates for the three games in the Super Smash Bros. series: {{SSB}}}, {{SSBM}}, and {{SSBB}}. All of these templates have various sections for their aspects, whether they'd be items, non-playable characters, enemies, etc. However, there's always been one peculiarity that's always bothered me: none of the Poké Ball Pokémon, nor any of the Assist Trophy characters, are listed in any of templates. We've made it a point of (trying to) list all of the stage hazard characters in the templates, but everything from Andross to Weavile has simply been absent, which seems rather inconsistent. Is there really any reason for keeping them out of the templates? Yes, just about all of the Pokémon/Assist Trophies are merged into articles, but that's why we have redirects (which is also aided by the advent of anchors), and most, if not all, of the stage hazards have also been merged. Really, the only question should be whether to give them separate sections in the template or to stick them in the NPC section.

Proposer: Time Turner (talk)
Deadline: October 3, 2013, 23:59 GMT

Add a New "Pokémon"/"Assist Trophy" Section to the Appropriate Templates

  1. Time Turner (talk) The NPC section would probably get too cramped if we started adding the Pokémon and the Assist Trophies.
  2. Iggy Koopa Jr (talk) Seems weird that this information is not figured anywhere.
  3. Mario7 (talk) Per proposal and all

Add the Pokémon/Assist Trophies to the Non-Playable Character section

Do Nothing

  1. Walkazo (talk) - Nav templates are for navigating between pages: tonnes and tonnes of links to the same list page (or two) will just clutter up the templates, making them look bad and hindering navigation to the other, separate pages. Just add one link to the Pokemon list page on the templates that don't have it yet (which is an oversight and doesn't require a proposal in itself), and folks can use the TOC to navigate the lists from there.
  2. Tucayo (talk) - Per Walkazo. A template linking to the same page in 90% of its entries is not exactly useful. And, as she said, adding a link to said page wouldn't even require a proposal.
  3. Gonzales Kart Inc. (talk) Per Tucayo
  4. Megadardery (talk) Per my comment.
  5. Yoshi876 (talk) Per Walkazo.
  6. Ultra Koopa (talk) - Per Walkazo.
  7. Icemario11 (talk) - Per Walkazo.
  8. Mario4Ever (talk) Per Walkazo.
  9. Scr7 (talk) Per Walkazo

Comments

Personally, I prefer no listing Pokémons, or Assist Trophies, I feel it better when it just links to Assist Trophy and Pokémon articles. Instead of many unneeded links, just for listing. The articles has lists. And beside, I feel this does not worth a Proposal, not even a TPP.. I would stick with a {{talk}}, If I were you. Megadardery (talk)

The proposal's already up, might as well roll with it. Besides, which talk page would I post it on, the Pokemon or the Assist Trophy? Also, how exactly are they unneeded? Time Turner (talk)
You would put that on {{SSBB}}. Back with the discussing, I said unneeded because they would crowd the template with unnecessary list, while there is already an link for Assist Trophy and Pokémon, and those articles contains those lists already. Megadardery (talk)
But my template is covering multiple templates (SSB, SSBM, SSBB). Yes, Assist Trophy isn't relevant for the first two, but the Pokemon are. Why does that even matter? Besides, there's already plenty of entries there. Why not the Assist Trophies and the Pokemon charcters? Let me put it this why: why should all the characters that appeared as obstacles (if even that) for a single stage be placed in a template, but characters that can show up no matter what stage you on and contribute greatly to the fight (Goldeen aside) be simply disregarded? Time Turner (talk)
Retrieved from "https://www.mariowiki.com/index.php?title=MarioWiki:Proposals&oldid=1557884"