MarioWiki:Proposals

http://i143.photobucket.com/albums/r149/Deadringerforlove/dessert1.jpg 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.

This page observes the No-Signature Policy.

How To
 * 1) Actions that users feel are appropriate to have community approval first can be added by anyone, but they must have a strong argument.
 * 2) Users then vote and discuss on the issue during that week. The "deadline" for the proposal is one week from posting at:
 * 3) *Monday to Thursday: 17:00 (5pm)
 * 4) *Friday and Saturday: 20:00 (8pm)
 * 5) *Sunday: 15:00 (3pm)
 * 6) Every vote should have a reason accompanying it.
 * 7) At any time a vote may be rejected if at least three active users believe the vote truly has no merit or was cast in bad faith. However, there must be strong reasons supporting the invalidation.
 * 8) " # " should be added under the last vote of each support/oppose section to show another blank line.
 * 9) All proposals that end up in a tie will be extended for another week.
 * 10) If a proposal has more than ten votes, it can only pass or fail by a margin of three votes. If a proposal reaches the deadline and the total number of votes for each option differ by two or less votes, the deadline will be extended for another week.
 * 11) Any proposal that has three votes or less at deadline will automatically be listed as "NO QUORUM." The original proposer then has the option to relist said proposal to generate more discussion.
 * 12) No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
 * 13) Proposals can only be rewritten or deleted by their proposer within the first three days of their creation. However, the proposer can request that their proposal be deleted by a Sysop at any time, provided they have a valid reason for it.
 * 14) 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 a Sysop, the proposer can ask for that help.
 * 15) There shouldn't be proposals about creating articles on a underrepresented or completely absent subject, unless there is major disagreement about whether the content should be included. To organize efforts about completing articles on missing subjects, try creating a PipeProject.
 * 16) Proposals can not be made about System Operator promotions and demotions. Sysops can only be promoted and demoted by the will of Bureaucrats.
 * 17) If the Sysops 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.
 * 18) No joke proposals. Proposals are serious wiki matters, and should be handled professionally. Joke proposals will be deleted on sight.

The times are in EDT (UTC -4:00), and are set so that the user is more likely to be online at those times (after work/school, weekend nights). If a proposal is added on Saturday night at 11:59 PM EDT, the deadline is the next Saturday night at 8:00 PM. If it is a minute later, the deadline is a day plus 15 hours (Sunday), as opposed to a day minus 4 hours.

CURRENTLY: , 27 2024 (EDT)

Removals
''None at the moment.

Put Waffle Kingdom and all the related places into "List of Implied Locations"
Some of you may know Waffle Kingdom. I propose this article and all the locations related to it to be merged with List of Implied Locations.

The reason is quite simple: The Waffle Kingdom is never actually visited in any game, and is therefore an implied location (duh). If that isn't enough reason, then there are plenty of other ones. It is f.e. impossible to add images to these articles and there's not much info available for them. Too few to fill a whole article. So, for the sake of fighting stubs and such, let us merge this articles.

Another thing: Since I can change this proposal within the first three days, I will use this to add another thing. Like SMB said, Princess Eclaire should also be merged with the List of Implied Characters if this proposal passes. Not sure about the Chestnut King, because this could also be a mistranslation of the Goomba King.

Proposer: Deadline: 21. November 2009, 15:00

Merge them

 * 1) - Per consistency and myself.
 * 2) Per Edofenrir, and we also would have to merge the Princess Eclair page and the Chestnut King into List of Implied Characters.
 * 3) I am Zero! Merge them, no picture and little info, belongs to implied locations. Zero signing out.
 * 4) - Per Edo. If this proposal somehow fails then I am adding an image tag!
 * 5) - PEr Edo.
 * 6) Per all.
 * 7) Per Edo.
 * 8) Per Edo.
 * 9) - Per Edo; I've always meant to make a proposal just like this for the exact same reason.
 * 10) Per all of the above.
 * 11) - Per Edofenrir, Super Mario Bros, Zero777, and Marioguy1.
 * 12) Per the 11 people above me.

Comments
Regarding the "Chestnut King", this is a mistranslation for Goomba King/Goomboss for sure, his Japanese name is always the same, while his English name changes from Goomba King to Chestnut King to Goomboss. There could still be a reference for that in the List of Implied Characters, but information about "Chestnut King" should go to the Goomboss article. --

Split "List of Glitches" into Sub-Articles
This article is almost like what the Beta Elements Article used to be. I think what is best for us is to separate it into sub articles just like what happened to Beta Elements. I consider Glitches to be just as informative as Beta Elements and should have their own sub article on the game. Besides, the list is huge, just like the Beta Elements, and I didn't even know about the glitches before typing "glitch" in the search box.

This is my first proposal, so if I did something wrong, feel free to correct me.

Proposer: Deadline: 28. November 2009, 20:00

Split Them

 * 1) per me
 * 2) - Didn't I suggest that at the old Proposal already? Hm... Unfortunately it doesn't seem to have made it into said Proposal... Well then, from scratch. I support this idea because... well, duh, consistency.
 * 3) - I was about to make this myself, but then I realized that you had already done it. Plus, if we split the second longest page on the wiki, why can't we split the longest?
 * 4) - The Beta elements and list of glitches are practically the same - they can both be made into sub-articles. Just promise me that this one will be capitalized (not Beta elements).

Add Shortcuts for Mario Kart Wii tracks
My first proposal. Add shortcuts to Mario Kart Wii tracks. This will help struggling racers get the fast staff ghosts, or beat an annoying sibling's best time. Add more spots if necessary.

Proposer: Deadline: 20 November 2009, 20:00

Add Shortcuts

 * 1) as per above, and for the people who can't find them on their own.
 * 2) If nothing else, it's more encyclopedic.

Don't add Shortcuts

 * 1) Per Coincollector and FunkyK38's comments below.
 * Ok, since the proposer didn't explain his/her intentions further, I have to conclude what it means. And judging from how the proposal is written, I think he/she wants to add mere tricks to get to the goal quickly, instead of built-in shortcuts. And as stated below, I oppose this.
 * 1) I am Zero! Like Funky said, were not a strategy wiki, and I think there are alrady shortcuts on some courses on MKWii, but only if there notable enough. Even though there is such thing as a spoiler section we don't want to spoil the player too much they end up as an ass on online play and are now roten and had to be thrown away (metaphor right there). Zero signing out.
 * 2) Much easier to look up on YouTube. ;D And per Funky's and Coin's comments below.
 * 3) The 'W' in 'SMW' stands for "Wiki," not "Walkthrough."
 * 4) Per Dodoman.
 * 5) Per all. Shortcuts should be found elsewhere, not here.
 * 6) Per my comment below.
 * Hm, yeah. This is just an info site, not a strategy guide.

Comments
What do you mean with shortcuts specificly? Are you talking about shortcuts implemented in the tracks (like secret tunnels) or just driving tricks that help you getting to the finish faster? I'd support the first and oppose the latter one. -
 * Per Edo. Also, your reasoning makes it sound like you're trying to turn those articles into game guides. :/ --
 * Aren't shortcuts already in some of the racecourse articles?

The tone of this proposal makes me to think like a joke (or a walkthrough issue, like explaining bug shortcuts or glitches, eg: the worst shortcut glitch of Grumble Volcano) and that's not a valid question to propose.
 * There's already mentioned shortcuts in articles. I think he's trying to say that he wants EVERY article with a shortcut-explanation guide.
 * We don't really have to put those on there, this isn't a strategy Wiki, we're the Mario wiki.
 * This proposal is not described well enough for me to vote. Describe it better or I will not vote.
 * Same here

Staff pages
I've noticed how we have a bunch of separate articles on the staff of video games. I believe this is fine, but why do we need stand alone articles on the staff pages? Why not just move them to subpages of the games' articles, kinda like the Beta elements sub-pages? The only page they are linked from is the game anyways (the template doesn't count).

Proposer: Deadline: 24 November 2009, 20:00

Support

 * 1) – Per proposal suggestion
 * There's no need for a stand-alone page. Making it a sub-page of the game article makes more sense. Per Knife.
 * 1) - This should actually go without saying, but of course we can't skip the proper channels...
 * 2) Per Knife.
 * 3) Per Knife's proposal.
 * 4) - Per all.
 * 5) - Sounds good :D
 * 6) - Per Knife.
 * 7) - If galleries and betas have that, why not staff?
 * 8) – Per Knife
 * 9) - Per Knife.
 * 10) - Makes sense to me.

Comments
Vini64: You seem to misunderstand the proposal. It's not about putting the staff information into the game articles themselves. Rather, they would go on a sub-page of the game articles (e.g. ), just like it's already done with the beta elements: Super Mario World/Beta elements.
 * Ohh, now I understood. Sorry about the misunderstanding.
 * No problem!

Vini64: It's not about merging those pages with the article, it's about making the standalone pages to subpages for organisatory meanings. That doesn't consume any room on the original article at all. I was too slow, so, what Time Q just said. -