MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
Line 107: Line 107:
====Comments====
====Comments====
...What? {{User|Time Turner}}
...What? {{User|Time Turner}}
To my knowledge: 1) There is no need for an on wiki proposal for off-wiki content, and 2) such a wiki likely already exists, for all we know. {{User|Lord Grammaticus}}


==Removals==
==Removals==

Revision as of 20:13, February 10, 2014

Image used as a banner for the Proposals page
Current time:
Saturday, December 21st, 10:03 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

None at the moment.

New features

Create an [unconfirmed glitch] template

Collab Link

While navigating through glitches pages, I came across several glitches which I was unable to perform, nor did I managed to find any proof that this glitch is real or fake. So instead of removing all unsourced glitches, we would simply add a small notice like this[unconfirmed glitch]. This way we will still have the information, while avoiding any bogus glitches (because the reader would be already aware that this glitch was not tested, unproved).

I already aware that there is a template called {{refneeded}}. However this is a different thing: not every glitch need a reference. they need just an screenshot, a video, or in some cases, discussion on the talk page may be very enough if provided with some proof. Also having a different template and a different category is better for organizing, this way we can look in the category to find all glitches pages only which contains glitches need confirmation.

Draft: 

<sup class="noprint">[''unconfirmed glitch'']</sup><includeonly>[[Category:Glithes need confirmation]]</includeonly><noinclude>[[Category:Formatting Templates|{{PAGENAME}}]]</noinclude>

Proposer: Megadardery (talk)
Deadline: February 3, 2014, 23:59 GMT, Extended: February 10, 2014, 23:59 GMT

Support

  1. Megadardery (talk)
  2. Baby Luigi (talk) Per Meggy
  3. Randombob-omb4761 (talk) Per proposal
  4. Mario7 (talk) Per proposal. I think this would be a great idea.
  5. Green 6017 King Of The Slowpoke (talk) Per all. This is a great idea, especialy for a glitch hunter like me.
  6. Robecuba (talk) Per proposal
  7. Ashley and Red (talk)Per all. I couldn't mind that :)

Oppose

  1. Walkazo (talk) - Just use {{refneeded}}: an unconfirmed glitch is no different from any other unconfirmed bit of info, and needs to be backed up by the exact same kind of sources. Furthermore, the template would just categorize the whole list page, not the specific glitch: in all likelihood, every long page will end up languishing in the category, probably from multiple templates (not that you could tell from looking at the category), which isn't useful: better to just use the collab to keep track of things.
  2. Pinkie Pie (talk) Per all.
  3. Lord Grammaticus (talk) - Per Walkazo, this proposal looks to me like it's basically founded on a bunch of semantic issues.
  4. Mario (talk) Uploading a screenshot and a video should be enough to remove both templates, so the proposed template will be pretty much redundant.
  5. driftmaster130 (talk) Per all.
  6. Yoshi876 (talk) Per all.
  7. Marshal Dan Troop (talk) Per all.
  8. Mario4Ever (talk) Per all.
  9. Jazama (talk) Per all
  10. Demonic KB (talk) Per all

Comments

Screenshots and videos are references, and citing discussions isn't ideal even for glitches (although citing discussions beats no citations at all, of course). And what do you mean by "scrawny" "sourcing thing"? Citations are used all over the wiki, and so they should: they lend credibility to the database. Whoever told you references are only for upcoming games and beta elements is grievously mistaken. - Walkazo (talk)

Sorry, I was mistaken. After reading MarioWiki:Citation_Policy in depth again, I knew that information can be taken directly from the game without the need of external resources. Whatever, I guess this proposed feature should be separated from the {{refneeded}}, this way the category will contain all the pages that weren't tested by our users thus they aren't confirmed. About the citing discussion, take Flip'd-up Mario 1 as an example, a user confirmed this on the talk pages even describing it more, another user confirmed the glitch and confirmed his description (both users do not have capture cards), thus the glitch is confirmed, BUT it needs a reference. so replacing the {{UnconfirmedGlitch}} with the {{refneeded}}. Take Bananaport Glitch as an example, it does have an image, however I started a discussion on the talk page saying that it never happened for me, some more users said so. The {{UnconfirmedGlitch}} get added to the glitch, even when it really has an image (a reference. Megadardery (talk)
You can still use {{refneeded}} in cases where some evidence is provided but more is needed. And more than anything, the story about "Flip'd-up Mario 1" just proves that the differences in use between the established template and the proposed addition is splitting hairs and adding unnecessary complications to the straightforward process of confirming glitches (nothingrefneeded -> disucssion-but-no-hard-proofcite talk page so readers can decide for themselves if they trust us -> hard-evidencecite that and be happy). - Walkazo (talk)
A new template sounds redundant, but maybe {{refneeded}} could be modified to read "unconfirmed glitch" or something? driftmaster130 (talk)
Sorry, but I don't quite understand you.Megadardery (talk)
Which part? - Walkazo (talk)
"(nothingrefneeded -> disucssion-but-no-hard-proofcite talk page so readers can decide for themselves if they trust us -> hard-evidencecite that and be happy)"Megadardery (talk)
@Walkazo Like this: [unconfirmed glitch, citation needed]; and it could be modified like {{Userspace}} was for double usage. I don't know if that seems redundant or not but at least it highlights glitches more. driftmaster130 (talk)
But don't you think that's getting a wee bit long and unseemly? Anyway, what I meant was that first, if someone adds a glitch with no refs or anything, you can just label it with {{refneeded}}. Then maybe it gets discussed on the talk page and people convincingly vouch for its existence - then you cite the discussion, and it's up to the readers to look at the citation and decide whether they believe our info despite us not having any hard evidence. Then you do find some hard evidence and can cite that instead, and when readers see that, they won't have any reason to doubt us (i.e. everybody's happy). No need for a clunky extra template or template parameter: you either have a reference, or ya don't. It also just occurred to me that if you really want to keep track of unconfirmed glitches and don't trust a list on the wiki collabs board, why not use {{talk}} or a template spun off of that to put on the talk pages? You'd still get the useless category problem, but at least the templates will draw attention to the appropriate sections on the talk page once folks wander in. - Walkazo (talk)

XX supports= Remove XX opposes freely

While I did my first Feature Nomination, I discovered that to remove opposes we need three users' votes and one from an admin. I think that this is an injustice. If an FA (or even a Proposal) have, for example, 10 supports, and only one oppose, then the rule should be different. Using the same sample: By each 10 supports, one ( or more,maybe) should be ignoted/ removed. I mind that, at least, by each 7 supports, we can remove one( the first) oppose freely.

Proposer: Ashley and Red (talk)
Deadline: February 15, 2014 23:59 GMT

Support

  1. Ashley and Red (talk)

Oppose

  1. Time Turner (talk) Especially when it comes to articles featuring prominent characters, there are always quite a few users who flood a nomination with support votes simply due to the fact that they like the character while ignoring any flaws that the article actually has. If this proposal were to pass, this could, in turn, lead to featured articles being more of a popularity vote than anything else, which is completely against the spirit of featured articles. Though there certainly isn't a guarantee that this will occur, I do not want to take the chance of it happening.
  2. Pinkie Pie (talk) Only Featured Articles' votes can be removed, not the proposal. Proposals' votes can't be removed. Per Time Turner.
  3. Randombob-omb4761 (talk) Per Pinkie Pie
  4. Mario (talk) While the current system of requiring a patroller or higher to remove an oppose vote is flawed (often, they simply don't vote), this proposed rules will create much more problems than it solves. We do not feature on the quantity of votes, but rather, no oppose votes. If there is a single oppose vote that is isn't disputed, then it should remain.
  5. Yoshi876 (talk) Per TT and Mario.
  6. Mr. Guye (talk) My case is in the comments section of this proposal.

Comments

Shouldn't this be appeal? Pinkie Pie (talk) 20:14, 7 February 2014 (EST)

Ashley and Red, you should look how this proposal failed: http://www.mariowiki.com/MarioWiki:Proposals/Archive_37#Allow_Removal_of_Support.2FOppose_in_Proposals Randombob-omb4761 (talk)


The MarioWiki:Featured Articles Section "How to Nominate" states:

If you object, please supply concrete reasons for doing so and how it can be improved [emphasis mine]. Please cite which rule your objection falls under. Failure to do so will result in your objection being considered invalid. Users may vote for the removal of an oppose vote if they feel it is invalid or not specific enough, but have to give reasons for their choice. Three users, including an administrator, are required for the removal of an oppose vote.

Objection cannot be 'valid' without reason and and a method of improvement. If nominators, supporters, administration, et cetera are unable to ameliorate whatever obstacle or flaw to satisfy the objector's demands then:

A) the article should not have been nominated in the first place because it does not meet the previously written standards, or
B) the objector's arguments are fallacious and the three user + one administrative vote will quickly dispatch of the objection.

In the case of scenario B, the voters + admin will be more than delighted to remove the objection. For these reasons, I oppose. Mr. Guye (talk)

Good oppose :) Ashley and Red (talk)

Fanon wiki NOT like Pikipedia Fanon

I love mario fanon, and the sure is a lot of it! I wish there was a wiki for fangames/romhacks like SMBX.

Support

--Koopa The Quick (talk) 20:06, 10 February 2014 (EST)

Oppose

Comments

...What? Time Turner (talk)

To my knowledge: 1) There is no need for an on wiki proposal for off-wiki content, and 2) such a wiki likely already exists, for all we know. Lord Grammaticus (talk)

Removals

None at the moment.

Changes

None at the moment.

Miscellaneous

None at the moment.

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