MarioWiki:Proposals

 http://img33.picoodle.com/img/img33/9/9/17/f_propcopym_9045f2d.png 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. Signing with the signature code (~) is not allowed due to technical issues.

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) 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.
 * 10) 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.
 * 11) Proposals can not be made about System Operator promotions and demotions. Sysops can only be promoted and demoted by the will of Bureaucrats.
 * 12) 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.
 * 13) No proposal can overturn the decision of a previous proposal that is less than sixty (60) days old.

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 (EST)

New Features
''None at the moment.

Removals
''None at the moment.

Courses based on Courses
Hey everyone it's User:MC Hammer Bro. again. This time I've noticed things like Super Smash Bros. stages and Mario Kart courses that share names with courses in games that they are based off of. Mainly I noticed how Article: Tick Tock Clock, course 14 in Super Mario 64 is seperate from Tick Tock Clock (course) but...Rainbow Ride from Super Mario 64 and Rainbow ride (Rainbow cruise) stage from Super Smash Bros. Melee are in the same articel. So my question is show the articles be merged or seperated?

Proposer: Dedline: March 26, 2009, 17:00

Split 'em up

 * 1) Courses of the same name from different games should stay split because, well, they have their own qualities.Besides, SSB stages are usually a "very rough" version of the real stage.

Merge 'em together

 * 1) - I say merge, beacuse they're supposed to be the same place
 * 2) - I would merge article titles that have the same name.  As we now seperate history sections by appearances, articles could have section titles for each game the topic appears in.  For example, Luigi's Mansion could have a section under the title "Luigi's Mansion," then a section titled "Mario Kart series" with the Luigi's Mansion from Mario Kart, which would then state the differences between the original and the MK versions.  Finally, the article could have a "Mario Tennis" section for the mansion's appearance in Mario Power Tennis.
 * 3) - Per SoS.
 * 4) - Per SoS.

Comments
Honestly, at the moment I am undecided. I would like to hear other opinions first.

Changes
''None at the moment.

Miscellaneous
''None at the moment.