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.

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.

SM64 Sub Levels
Hello wiki users. This will be my first proposal so wish me luck. Anyways, the problem I found was within levels in Super Mario 64. Many levels contain sub levels (not the secret levels). Examples are like the Volcano in Lethal Lava Land and the Pyramid in Shifting Sand Land. Now in the first case, the two locations are in seperate articles but the latter has the Pyramid within the mother level. Now should the articles be split or combined?

Deadline: Thursday Feb 26th 17:00 (5pm) Proposer:

Merge Sub level with main level

 * 1) I am the creator and also see my comments
 * 2) Per MC Hammer Bro, as they're part of the levels, it would be like saying the places Mario go through the pipes were another levels
 * 3) - Most of them are not officially named... but what it comes down to is that they are very minor.  Just as I wouldn't like to see Toad Town split into a different article for each "screen," (ie Southern Toad Town), I would hope that the information about each part of these worlds would stay on the same page.
 * 4) Why in the world are those pages there in the first place? Per MC Hammer Bro.
 * 5) I too belive that these sub levels should be on the same page,under a sub heading or something.(No joke intended)
 * 6) They should definitely be merged.  After all, sub areas such as the pyramid's interior are part of each course as a whole.
 * 7) - Per All. Plus it makes it easier than having to link to all of the seperate pages.
 * 8) - Per all.
 * 9) - Per all
 * 10) - Per all.
 * 11) - I agree the articles are too small by themselves.

Comments
I think the sub articles are too small to be alone and are better off merged as they contain items (stars and coins) vital to completing the levels. It would also lengthen some of the shorter articles and prevent repeated info as the star missions would end up sorta repeated.

Hazy Maze Metal Switch cave? Is that a different level? It leads into the castle grounds...


 * Yes, that would be a separate level as its stars are not part of the main level's missions. --


 * Exactly. That's what I had ment when I said except for secret levels. Plus the places like the Hazy Maze Switch cave actually has a different level title when you pause the game. Unlike if you were in the Volcano in lethal Lava land, pausing the screen would still say you were in lethal lava land.


 * Cool. Make sense. --

Monobook.css
Did anyone notice besides me that editing this wiki is very very slow? It takes a long time to save once you press the save button. And I think its our very extensive MediaWiki:Monobook.css. Loading Userpedia is a lot faster than loading the MarioWiki, which could be due to the fact that they have nothing placed in Monobook.css. So I propose we blank or shorten our Monobook.css page.

Deadline: February 27, 2009 Proposer:

Shorten it

 * 1) - Per above
 * 2) - Per Yoshario!  I agree entirely!

Keep it how it is

 * 1) PATIENCE IS A VIRTUE! You just have to just be patient when you press Save Page.It is a bit of a long waiting time,but I don't think it needs changing.Wobbuffet is a patient Pokemon! (I'll hit Save Page now and WAIT!)
 * 2) - There is nothing wrong, it's just that the server is sometimes screwed up, and makes pages load slower, or not at all. Pages with DPL load slower because DPL calculates all the data at a slow rate, such as on my Userpage. So no, everything is fine as it is.
 * 3) - Per all.

Comments
I think this will help our wiki load alot faster. And by shorten it I mean take out the verdana font and the search bar modifications, but maybe keep the mario thing in the edit box because it symbolizes that our subject is Mario.
 * OK, totally against blanking it. I'm somewhat against shortening it as well. It signifies who we are. Perhaps we could make the images lower quality, but shortening it would be ineffective, I believe. I might totally be wrong, but I think that the monobook has little nothing to do with the loading speeds. Also, the font makes no difference whatsoever. I'd like to see how the proposal pans out, though.


 * It isnt slow for me

Miscellaneous
None at the moment.