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.

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).
 * 5) - Per BabyLuigiOnFire and Edofenrir.
 * 6) Per Baby Luigi
 * 7) I was going to make a proposal exactly like this one xD
 * 8) Agree with BLOF
 * 9) We did this with Beta Elements, and it can out to be a big sucess! This and beta elements have many things in common, and spliting glitches with definitely work out (in my opinion). 100% on this side!!!

Keep as it is

 * 1) Lu-igi board I enjoy reading through it finding random glitches from random games. it would ruin the experience to have to browse many pages for interesting glitches
 * 2)  Per Lu-igi board
 * 3) - I agree with Lu-igi board.

Comments
Lu-igi board, I also enjoy reading through the beta elements page without clicking on those many links (and I also HATE the gallery), but sometimes, loading speed is important so I think this proposal is necessary.


 * Shouldn't you support then?

BLF, remember rule 11 "The original proposer must take action accordingly if the outcome of the proposal dictates it."


 * Yeah, I won't forget. Wait. Does it mean that I might need to split them right now?

Different Version Characters
In the Mario film and also in the Mario cartoons, there are versions of characters that are not necessarily the same characters from the character's real media. Such as:
 * The princess in the Mario film basically has all of the qualities Peach would have with a few exceptions including her name.
 * Same goes with the koopa cousins in the film, neither are actually their corresponding counterparts.
 * The infant form of the princess in the film is hardly BABY Daisy in video games.
 * The infant forms of Mario, Luigi, Peach, Toad, and Bowser are not the same as the Baby characters from video-games.

This proposal is to make it so that in the case of characters from the film, we create separate articles for the character that explains them for the film but also makes note of the connections to video game characters.

It is also to make it so that just because in some previous media there has been an infant form of a character, does not mean that it is the Baby form of the character from video-games. Infant Princess Daisy from film =/= Baby Daisy from videogames.

If there's any confusion, ask. This proposal was made from ides of numerous users on the comments of previous confusion from the original proposal made by Redstar.

Proposer: FD09 Deadline: 1 December 2009, 17:00

Support

 * 1) FD09 - Per other users suggestions and ideas. above
 * 2) - Results in article clean-up by creating more specialized articles. The better organization sounds good to me.
 * 3) - Per what is proposed there.

Comments
This is the result I originally had in mind, but failed to voice that proposal in a clear way. Under this new proposal I think special attention can be paid to both the film characters and their video game-counterparts in an equal way, satisfying all parties and make for a much more informative encyclopedia. Redstar 17:39, 24 November 2009 (EST)
 * Good to hear it. Now don't forget to add some reasoning next to your vote. If you don't explain your vote or say something like per (another username who voted) your vote is liable to be removed by a sysop that deems it incomplete. FD09

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.
 * 11) - Per all.
 * 12) - Good idea. It would be more organized to keep them all like that.
 * 13) - Honestly, I'm indifferent to the staff pages, but that sounds like it would make the Wiki a little more organized.
 * 14) - Good idea.

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. -

Merge Traps and Obstacles pages to super-article
These pages are usually quite small and would be better suited if merged to a super-article. This would allow them to be better located as well as cut down on needless articles covering every minor aspect of the games. Redstar 17:27, 24 November 2009 (EST)

Support

 * 1) Proposer

Comments
I fixed up the coding, remember to use the format ===<proposal=== when making a proposal.
 * Yeah, I'm sure there's a lot of coding I need to learn. I joined up and made some edits over a year ago, so I'm trying to jump into it again now. Thanks for the advice. Redstar 17:35, 24 November 2009 (EST)
 * Let me get this straight: You want to merge all traps and obstacles articles from everywhere into one single article? - 18:01, 24 November 2009 (EST)