MarioWiki:Proposals
|
Friday, November 15th, 21:23 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.
|
A proposal section works like a discussion page: comments are brought up and replied to using indents (colons, such as : or ::::) and all edits are signed using the code {{User|User name}}.
How to
Rules
- If users have 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 the other users, who will then vote about whether or not they think the idea should be used. 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}}.
- Only autoconfirmed users may create or vote on proposals and talk page proposals. While only autoconfirmed users can comment on proposals, anyone is free to comment on talk page proposals.
- Proposals end 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 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.
- 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 "(banned)" 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.
- No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
- 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 the {{proposal check}} tool 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 can only be re-proposed after four weeks (at the earliest).
- 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.
- If the wiki staff deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to remove it at any time.
- Proposals can only be rewritten or canceled by their proposer within the first six 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 and support/oppose format
This is an example of what your proposal must look like, if you want it to be acknowledged. If you are inexperienced or unsure how to set up this format, simply copy the following and paste it into the fitting section. Then replace the [subject] - variables with information to customize your proposal, so it says what you wish. If you insert the information, be sure to replace the whole variable including the squared brackets, so "[insert info here]" becomes "This is the inserted information", not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but what each voting section is supporting 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|[enter your username here]}}<br>
'''Deadline''': [insert a deadline here, 14 days after the proposal was created, at 23:59 GMT, in the format: "November 15, 2024, 23:59 GMT"]
====Support====
#{{User|[enter your username here]}} [make a statement indicating that you support your proposal]
====Oppose====
====Comments====
Users will now be able to vote on your proposal, until the set deadline is reached. Remember, you are a user as well, so you can vote on your own proposal just like the others.
To support, or oppose, just insert "#{{User|[add 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 just say "Per my 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. Proposals dealing with a large amount of splits, merges, or deletions across the wiki should still be held on this page.
- For a list of all settled talk page proposals, see MarioWiki:Proposals/TPP archive and Category:Settled talk page proposals.
Rules
- 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. Place {{TPP}} under the section's header, and once the proposal is over, replace the template with {{settled TPP}}.
- All rules for talk page proposals are the same as for proposals (see the "How to" section above), with the exceptions made by the additional rules below:
- The talk page proposal must pertain to the subject page of the talk page it is posted on.
- When a talk page proposal passes, it should be removed from this list and included in the list under the "Unimplemented proposals" section until the proposed changes have been enacted.
List of ongoing talk page proposals
- Merge Orbs that share names with pre-existing Mario Party series items with those items (discuss) Deadline: November 14, 2024, 23:59 GMT
- Create a number of articles for special buildings in Super Mario Run (discuss) Deadline: November 15, 2024, 23:59 GMT
- Consider Deep Cheeps' appearance in the Super Mario Maker series a design cameo rather than a full appearance (without Blurps being affected) (discuss) Deadline: November 15, 2024, 23:59 GMT
- Merge Mushroom, Dash Mushroom, and most of Super Mushroom (discuss) Deadline: November 18, 2024, 23:59 GMT
- Expand and rename List of characters by game (discuss) Deadline: November 20, 2024, 23:59 GMT
- Decide whether to create articles for Ashita ni Nattara and Banana Tengoku and/or include them on List of Donkey Kong Country (television series) songs (discuss) Deadline: November 23, 2024, 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) |
Split articles for the alternate-named reskins from All Night Nippon: Super Mario Bros., Doc von Schmeltwick (ended October 3, 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.
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) |
Split Banana Peel from Banana, Doc von Schmeltwick (ended September 18, 2024) |
Merge Spiked Thwomp with Thwomp, Blinker (ended November 2, 2024) |
Split Cursed Mushroom from Poison Mushroom, Pseudo (ended November 12, 2024) |
List of Talk Page Proposals
- Delete List of Adventure Mode enemies (Discuss) Deadline: February 20, 2014, 23:59 GMT
- Delete Holerö. (Discuss) Deadline: February 24, 2014, 23:59 GMT
- Merge Fly with Fly (move). (Discuss) Deadline: February 24, 2014, 23:59 GMT
- Delete Dimension. (Discuss) Deadline: February 24, 2014 GMT, 23:59 GMT
- Delete All worlds. (Discuss) Deadline: February 24, 2014, 23:59 GMT
- Merge Template:RPG Attacks with the relevant templates. (Discuss) Deadline: February 25, 2014, 23:59 GMT
Writing Guidelines
None at the moment.
New features
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
Oppose
- 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.
- Pinkie Pie (talk) Only Featured Articles' votes can be removed, not the proposal. Proposals' votes can't be removed. Per Time Turner.
- Randombob-omb4761 (talk) Per Pinkie Pie
- 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.
- Yoshi876 (talk) Per TT and Mario.
- Mr. Guye (talk) My case is in the comments section of this proposal.
- KP (talk) Per all.
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. sorry, I meant a NIWA wiki, not this one
Proposer: Koopa The Quick (talk)
Deadline: February 17, 2014, 23:59 GMT
Support
Oppose
- Mario (talk) I don't get what's the point of this proposal. We're a Mario encyclopedia that has policies strictly against having fanon content. You'll have to make a really convincing argument to include fangames and romhacks in this wiki. So far, there's nothing convincing.
- KP (talk) So what? You are creating a proposal for having fanon content on the wiki, and every second there is something new in Mario fanon. We are not a wiki for fanon content, and we never will be. If we were, we would have more articles than Wikipedia, that is scary. It would be utter chaos here.
- Pinkie Pie (talk) STRONGER OPPOSE: Why? Just why? The wiki isn't a fanon wiki. If you want a fanon wiki, go to a fanon wiki. Per all. See that is the kind of silliness for a proposals. Proposals are suppose to improve the wiki, the writing, and the content. Plenty of users can vote and they can agree or disagree.
- Baby Luigi (talk) You're in the wrong site if you're expecting Mario fanon, buddy. Leave your fan stuff to your own pages.
- Yoshi876 (talk) Per all.
- Lord Grammaticus (talk) Per all.
- Randombob-omb4761 (talk) This is not a place for fanon, go to Fantendo if you want fanon. Or put it on your userpage.
- SeanWheeler (talk) Fanon should be separate from official content, otherwise we would confuse people and this site would be the most unreliable Mario site. Bad to add fanon to the coverage of a wiki that used information from the official games for years. Very. Strongly. Oppose.
- Magikrazy (talk) If you want to make a Mario fanon wiki, go right ahead. This isn't that wiki, though. This wiki is for official stuff. Per the rest.
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)
Shouldn't this be appeal? Pinkie Pie (talk) 20:47, 10 February 2014 (EST)
- Yes, this should Ashley and Red (talk)
Removals
None at the moment.
Changes
Merge articles such as Orbs and Hexes into lists with the same information
Most notably, I've seen large amounts of very small pages about things such as orbs and hexes. I think it would be more useful to merge these pages together into one large, easy to read list, as opposed to having tons of smaller pages. I believe that this will create consistency and simplicity for those who wish to view an entire page of all the orbs/hexes, and their effects, as well as compare them depending on the game. The orb list would be found on the orb page, and the hex list would be found under the hex page, etc. I think it'll be less daunting and time consuming as well.
I propose the following format, though I'm open to adjustments. Please keep in mind that this is only the prototype format, and if someone would like to suggest changes, I'd love to hear them:
Picture of Orb/Hex | Name(s) of Orb/Hex | Game(s) Item appear(s) in | Ability/Effect | Cost (if available) | Other information |
---|
Making separate lists for the separate Mario Party orbs/hexes under one page is also plausible. (Different pages for orbs and hexes, in case that wasn't clear.)
Now, while I've only mentioned these two things, if there's something you'd like to see merged as well, please add it in the comments section.
Proposer: Coooool123 (talk)
Deadline: February 17, 2014, 23:59 GMT
Support
- Coooool123 (talk) Per proposal
- Demonic KB (talk) That sounds like a good idea
Oppose
- Time Turner (talk) Doing this would be far from consistent, will be trimming far too much information, especially when considering that a lot of the orbs require extra explanations for their uses, and really, most of the orbs/hexes don't even have small articles, unless you wanna compare them to Bowser or something. Also, these are items. They have unique descriptions, and unique appearances, and unique uses, and everything that's needed for them to be considered items. What, exactly would be consistent about merging all of the orbs and not, say, all of the RPG items? Bottom line is, nothing good will come of this.
- SuperYoshiBros (talk) Per Time Turner.
- Pinkie Pie (talk) Dr. Whooves got it. Per all.
- Walkazo (talk) - Per Time Turner: this would be inconsistent and/or lead to more merges, but the philosophy these days is that more little pages are better than a few big lists (such as for search traffic and whatnot). Plus, lists with too much info aren't necessarily easy to use, and can be particularly troublesome for narrow screens.
- Randombob-omb4761 (talk) The orbs and hexes are from completeley different games.
Comments
@Time Turner - That's not necessarily true. It really depends on the layout of the page. Not to mention, we don't need as much information as we have. I've been told that conciseness is key on this wiki. If I may ask, which articles are you referring to? Most that I see are very short. It's a mess as it is, and more consistent than the method we have now. Coooool123 (talk)
- Paper Mario items, for starters. It's inconsistent. We don't merge power shots from Mario Power Tennis nor Captain Abilities from Mario Strikers Charged either. Baby Luigi (talk)
- Then don't merge those ones. This isn't about paper Mario items. this is about tons of tiny articles that will suffice under one page. Coooool123 (talk)
- @Coooool, I was hoping you'd understand that was a very general statement, as opposed to a standard to enforce on articles (not that I could plausibly do such here anyway). Lord Grammaticus (talk)
- Nope. Apparently not. But why shouldn't we be concise under such matters? We don't need all these pages when one will do. Coooool123 (talk)
@Randombob-omb4761- Apologies if I wasn't clear. but I said that they would have their own separate lists. I'm not proposing we merge these together. it's 'such as' Orbs and hexes. Both would have their own pages. Coooool123 (talk)
Miscellaneous
None at the moment.