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.

Worlds and levels
YBB again, Im noticing that some games have all of the levels of a world on the world's page, like 7-1, 7-2, 7-3, and 7-4 are all on the same page as World 7, but with other games, worlds just have links to level pages, like Chocolate Island and Chocolate Secret. Should we merge them all together, or split them apart? Note that this is relevant to pipeprojects.

Proposer: Deadline: April 2, 2009, 17:00

Merge

 * 1) - Yes, one big stub is no better than lots of little stubs, but this isn't about stubs - it's about organization: the real question is whether the same amount of info should be covered by tens of big articles or hundreds of smaller ones. Merging the levels would not cut down on the amount of information that could be included, it just rearranges it. Whether or not an aspect of a game has its own article shouldn't matter to how important it is in the grand scheme of things; not every named thing needs its own article to tell the readers what they need to know. Bloc Partier's Mt. Teapot is a good example of a world article that negates the need for individual level articles because it essentially has all the important information right there (though I'll admit that "importance" is in the eyes of the beholder). Other world articles need work, such as Desert Land, which has around the same amount of info as all of Chocolate Island's subsidiary stubs put together. However, expanding the former as a whole and expanding the latter stub-by-stub would essentially be the same thing, with only the organization differing (as is the inconsistent case now).
 * 2) - Per Walkazo. It is much easier to see all the information on one page than splitting it and needing to click back and forth between pages just to view all the levels and whatnot.

Split

 * 1) - Levels are independently named, even if only by number.  Each level contains a WEALTH of information - to cut down on stubs people should actually expand these level articles instead of creating one-sentence articles for the sake of creating one-sentence articles.  Merging the levels doesn't solve the stub problem, as the world article would still lack A LOT of information and would just be a stub of a larger size.  Level articles can then be linked by a profile template similar to the ones already in use by Donkey Kong Country and Yoshi's Island level articles in order to organize the different level articles.
 * 2) Sos has a good point.
 * 3) - Per SoS.
 * Per SoS. We can't just merge all levels into their world articles.
 * 1) Per all Lu-igi board 15:21, 28 March 2009 (EDT)

Comments
Ugh, this would destroy all my hard work to make Mt. Teapot Featured. But unfortunately it's a good idea. Blech. I'm not voting.

Changes
None at the moment.

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
 * 3) - This can make extra pages.Extra Pages = better example for guests = MOAR users = better articles.
 * 4) - Great idea, but we better put the beta enemies to the Beta Element page. Also, I've recently seen the name of the beta Blooper enemy of Mario and Luigi: Partners in Time on TMK.

Do Not Make Beta Enemy Page

 * 1) I'd prefer to see Beta Elements sorted by game. To me, it seems a largely arbitrary distinction to separate beta enemies from the rest of the main beta article. Especially so when considering that all the other information on that page would remain as it is. A subsection under the relevant game's section of the page would work equally well.
 * 2) - Per Twentytwofiftyseven. Keeping all the beta information pertaining to each game together in one place is the most effective way at presenting the info to the readers. Also, if the enemies get their own seperate page, why not beta items, beta characters and beta locations? Regardless of how much info there is about them, enemies are no more important than anything else on that beta elements page, so separating them and nothing else seems wrong.
 * 3) Per all Lu-igi board 15:22, 28 March 2009 (EDT)

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?


 * Yes, that looks better

Arend: Are you sure you voted under the right header? Supporting means the enemies will get a page separate from the Beta Elements, but it sounds like you want them as part of the main Elements page only (which is the current policy, as far as I know)... -


 * To Arend (and Walkazo as well): There is no policy (I believe) regarding how the Beta Elements page should be organized. Currently it lacks a Beta Enemies section, but that does not mean it can't have one.  This proposal is specifically about creating a separate article about Beta Enemies.  If that's what you want Arend, that's fine, but I think several of us are confused by your vote, which would suggest you don't want this page to be created. --

I have AR codes for a beta Red Koopa in Sm64ds!Not to mention beta hat boxes.Too bad my AR broke....