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)

New Features
''None at the moment.

Removals
''None at the moment.

Split Beta Elements into Sub-Articles
We all know that the Beta Elements page is incredibly long...the second-longest page on the wiki &mdash; It's chock full of images and good information on a ton of different games, (which isn't a bad thing), but I feel the article would be better off describing what a beta element is, and then having a list at the bottom of the page that lists all of the games we have beta info on. Which leads me to the second part of my proposal. Most of the beta element sections in that page are more than long enough to constitute their own page. This would make it easier to find a specific beta element in a specific game, and it would also make it much easier to load said page(s). For example, the beta elements for Super Mario World could be found at. This page could easily be found because there would be a link on Beta Elements to that page, as well as a link to it on the Super Mario World article.


 * An example of what the 'new' Beta Elements page would look like can be found here.
 * An example of what the Super Mario World beta elements sub-page would look like can be found here.

Proposer: Deadline: October 6, 2009, 17:00

Support

 * 1) &mdash; Per my reasoning above.
 * 2) - Per Stooby
 * 3) Per Dr. Rooben.
 * 4) Yoshi! Stoobys right, it is way to long.
 * 5) Per All.
 * 6) - It's not like me to simply per without adding my opinion, but Stooben Rooben summed it up perfectly.
 * 7) - Per All. This page takes like 5 minutes to be rendered after each edit.
 * 8) - Per Stooben. It'll be nice to be able to read about beta elements without my computer crashing halfway through loading the page. Smaller articles are also easier to organize, maintain and patrol.
 * 9) I am Zero! I like this idea very much, it is big hassle to load up the entire beta element page, the whole article is packed, and soon enough there will be to many games in that article which can make it hard to load. Zero signing out.
 * 10) – Per Stooben Rooben.

Comments
I think it would be better to have a catagory with a link to the sub-pages.
 * It's still necessary for us to describe what exactly a beta element is, though; so the article should stay. That said, we could add a to those sub-pages. --

Could something similar be done for the Glitches article? Of course it's only half as big as the Beta elements article, but... that's still big. -
 * Good point. They're pretty similar in nature, so if we want to be consistent, we should probably split both pages. -
 * I completely forgot about the Glitches page. :O Yeah, it'd be a good idea to split that page too. Thanks for pointing that out! --

Changes
''None at the moment.

Miscellaneous
''None at the moment.