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.
 * 2) - I think it would be crazy to merge these together, because they really are two different things. I mean, wouldn't it be confusing if you clicked rainbow ride on a template trying to get to the ssbm level, but went to the sm64 world instead? Of course you would have it on that page, but not as the main thing, but as a side subject. I say we Split 'em up.

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.
 * 5) - Per SoS.
 * 6) - Per SoS.
 * 7) - Per Sos. It's a great idea and I guess there are more articles with this delemas than I though.
 * 8) .-i think merge for the same reasons as SoS but also some articles are very small and even if we merge all of their realated articles it still wont be nealy as song as say... mario's article so yes MERGE!! DEFINATELY MEEEEERRGE!!!
 * 9) - Per SoS.
 * 10) - Per SoS.
 * 11) - I think that we should merge all articles on the same topic. However, we should not go as far as merging Rainbow Ride with Rainbow Road, only articles on things with little to no notable differences, like the Mario Circuits.
 * 12) - Per Son of Suns.
 * 13) - i like sos's idea. per above.

Comments
Zafum: It will take you to both things, so i dont see whats wrong


 * Also, links can be directed to sections, instead of the top of the article. So say you specifically want to link to the Luigi's Mansion in Super Smash Bros. Brawl.  You simply turn the link into Luigi's Mansion and you will go straight to the Smash Bros. info, passing by the other sections. --

Idk, it just seems......as a "bad example" to new users.Who knows, probanly they'll say, "OMG y don't they put seperate articles 4 it!ZOMG they suck!!!lol.I'm leaving." or something like that.
 * Well that would be their loss, now wouldn't it? You can't always get what you want, and if you storm off just because you disagree with some policy somewhere then you're gonna be unhappy for a very long time; it's better to just be flexible. -

Allow funny/creative title sections in articles
Since the wiki had set the rules for quality standards, specially for the history of a character in every game, I was noticing that all the titles were changed to the name of the game. Maybe it sounds personal, but I see that in many pages that would look redundant and too technichal. My proposal consists so about changing those titles and make ones creative like those used for the Wario article. Sure, the change will follow the current quality standards, avoiding points of views and ambiguities.

Proposer:

Allow Them

 * 1) - You got above.

Beta Enemies
I dont know where to put this but here goes.

I propose we create a page for all beta enemies, including stats, behavior, psychopath thoughts etc. and redirect drill bit (the only beta enemy with a page bcause it was accidentaly left in a cutscene (smithy! reember your blood pressure!)) to this page we could add a link 2 drill bit on the page AND if possible, the action replay codes used to access some of these beta enemies. Im sure interested in anything beta. Rite nao, the info is scattered about the beta elements page and pages of similar enemies.

Proposer: Deadline: 17:00 Monday, March 31, 2009

Make Beta Enemy Page

 * 1) YourBuddyBill- Ill take out the part about drill bit. we could just add alink to the page to drill bit
 * 2) - per ybb

Do Not Make Beta Enemy Page

 * 1)  - I oppose redirecting Drill Bit to any page.  It's a character that appeared in the game and should keep its own article.
 * 2)  - Per Son of Sons, they are still enemies.

Comments
Fixed. ;) And I would like to know all the stuff about them too, but separate pages for each enemy is rather tedious, in my opinion. Maybe not, but I would like it if we could know more about them.

Did Son of Suns vote in the wrong place? He said he wanted to keep separate pages; yet voted in do not make separate pages. Or am I reading it wrong? --


 * Oh, never mind, I read it twice, and I understand now. =D


 * The proposal states we should create one page for all enemies. Bloc Partier labeled the sections incorrectly.  (Not his fault, original proposer did not format anything right.)  I fixed it--

sorry, the directions are a bit complicated 4 me


 * If you remove the Drill Bit part of proposal, leaving it as its own page and linking to it, I will remove my oppose. --

I do think that YBB has a point, though, since it does have to do with the beta enemy being notable or not. Plus, a list is always good as an easy directory for articles. Then again, a category would do that job also.

thing is, not every one HAS an article. theyre just meshed together on the beta elements page with tidbits on other pages

Yoshario, I believe YBB is proposing to create ONE page to cover all Beta enemies, which right now have content in different places, not their own articles (nor is YBB proposing to give them each articles). Drill Bit is unique for being an enemy that appeared in the game but is also a beta enemy, as it was given stats but never used in battle. Hope that clears things up. --

So its not just a list, but an article that has the information on Beta Enemies instead of separate articles? I think that would be good. But then, would we still cover unused Drill Bit information in that article? --
 * OOps, I did read it wrong. The poor grammar threw me off. :P But yeah, one page sounds great.


 * To Yoshario - yep, one Beta Enemies page (there are no separate articles). Drill Bit would probably have a section with a "main article" link to Drill Bit.  The Drill Bit article should cover everything, while the Drill Bit entry in a proposed Beta Enemies page would give a summary of the subject Drill Bit as related to the article subject - Beta Enemies. --

Alright, I like that idea, better remove my oppose.

Instead of creating another page, how about having a sub section in the Beta Elements page? They would classify in that category, but would things get a little too complicated?