MarioWiki:Proposals

Proposals can be new features (such as an extension), removal of a previously added feature that has tired out, or new policies that must be approved via consensus before any action(s) are done. Any user can support or oppose, but must have a strong reason for doing so, not, e.g., "I like this idea!" "Vote" periods last for one week. All past proposals are archived. 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 {{user|User name}}. Signing with the signature code ~~~(~) is not allowed due to technical issues. How To Actions that users feel are appropriate to have community approval first can be added by anyone, but they must have a strong argument. Users then vote and discuss on the issue during that week. The "deadline" for the proposal is one week from posting at: Monday to Thursday: 17:00 (5pm) Friday and Saturday: 20:00 (8pm) Sunday: 15:00 (3pm) Every vote should have a reason accompanying it. 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. "# " should be added under the last vote of each support/oppose section to show another blank line. 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. 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. Proposals can not be made about System Operator promotions and demotions. Sysops can only be promoted and demoted by the will of Bureaucrats. 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. 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: 05:31, 30 May 2024 (EST) New Features None at the moment. Removals None at the moment. Splits & Merges 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: YourBuddyBill (talk) Deadline: April 2, 2009, 17:00 Merge Walkazo (talk) - 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). Bloc Partier (talk) - 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. Sonic64 (talk) - Per Walkazo and Bloc Partier. Plus, one article per world per game is more organized than one article per level. The Great Gonzales (talk) - Per Walkazo. It makes much more sense to have one umbrella world article than a ton of little one-level articles floating around. Super Mario Bros. (talk) - I think that we should. It is more organized and efficient to use when some are already meged and some are not. Split Son of Suns (talk) - 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. YourBuddyBill (talk) Sos has a good point. Paper Yoshi (talk) - Per SoS. Time Q (talk): Per SoS. We can't just merge all levels into their world articles. 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. Bloc Partier (talk) Kombatgod (talk) I think it is wrong thinking of merging or splitting everything. Like any other section in every page, if a section about a zone is too large, it'll need an article, if it fits well in the page of the world it'll remain a section. It is fool to have lots of stub pages just because we decided to split them all, or to have incredibly large articles just because we decided to merge. I think the only point is how long should a zone section be to become an article? Changes None at the moment. Miscellaneous None at the moment.