MarioWiki:Proposals

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.

This page observes the No-Signature Policy.

How To Rules
 * 1) If users have an idea about improving the wiki or managing its community, but feel that they need community approval before acting upon that idea, they may make a proposal about it. They must have a strong argument supporting their idea and be willing to discuss it in detail with the other users, who will then vote about whether or not they think the idea should be used. Proposals should include links to all relevant pages and Writing Guideline proposals must include a link to the draft page.
 * 2) Anyone can comment on proposals whether logged-in or not, but only registered users can create or vote on proposals.
 * 3) Proposals end at the end of the day (23:59) one week after voting starts, except for Writing Guidelines and Talk Page Proposals, which run for two weeks. (All times GMT.)
 * 4) *For example, if a proposal is added at any time on Monday, August 1, 2011, the voting starts immediately and the deadline is one week later on Monday, August 8, at 23:59 GMT.
 * 5) Every vote should have a reason accompanying it. Agreeing with or seconding a previously mentioned reason given by another user is accepted.
 * 6) Users who feel that certain votes were cast in bad faith or which truly have no merit can address the votes in the Comments section. Users can ask a voter to clarify their position, point out mistakes or flaws in their arguments, or call for the outright removal of the vote if it lacks sufficient reasoning. Users may not remove or alter the content of anyone else's votes. Voters can remove or rewrite their own vote at any time, but the final decision to remove another user's vote lies solely with the administrators.
 * 7) If a user makes a vote and is subsequently blocked for any amount of time, their vote is removed. However, if the block ends before the proposal ends, then the user in question holds the right to re-cast their vote. If a proposer is blocked, their vote is removed and "(banned)" is added next to their name in the "Proposer:" line of the proposal, which runs until its deadline as normal. If the proposal passes, it falls to the supporters of the idea to enact any changes in a timely manner.
 * 8) No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
 * 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 that end up in a tie will be extended for another week. Proposals with more than two options must also be extended another week if any single option does not have a majority support: i.e. more than half of all votes cast must be for a single option, rather than one option simply having more votes than the other options.
 * 11) If a proposal has more than ten votes, it can only pass or fail by a margin of three votes. In other words, one option must have 50% + 3 of all votes cast. This means that if a basic two-option proposal reaches the deadline and the total number of votes for each option differ by two or less votes, the deadline will be extended for another week. Proposals with more than two options require more precise counting of votes to determine if an extension is necessary.
 * 12) Proposals can only be extended up to three times. If a consensus has not been reached by the fourth deadline, the proposal fails and can only be re-proposed after four weeks, at the earliest.
 * 13) 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 an administrator, the proposer can ask for that help.
 * 14) If the administrators deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to remove it at any time.
 * 15) Proposals can only be rewritten or deleted by their proposer within the first three days of their creation. However, proposers can request that their proposal be deleted by an administrator at any time, provided they have a valid reason for it. Please note that cancelled proposals must also be archived.
 * 16) There should not be proposals about creating articles on an 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 setting up a collaboration thread on the forums.
 * 17) Proposals cannot be made about promotions and demotions. Users can only be promoted and demoted by the will of the administration.
 * 18) No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.

Basic Proposal and Support/Oppose Format This is an example of what your proposal must look like, if you want it to be acknowledged. If you are inexperienced or unsure how to set up this format, simply copy the following and paste it into the fitting section. Then replace the [subject] - variables with information to customize your proposal, so it says what you wish. If you insert the information, be sure to replace the whole variable including the squared brackets, so "[insert info here]" becomes "This is the inserted information", not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but what each voting section is supporting must be clearly defined. - ===[insert a title for your proposal here]=== [describe what issue this proposal is about and what changes you think should be made to improve how the wiki handles that issue]

Proposer: Deadline: [insert a deadline here, 7 days after the proposal was created, at 23:59 GMT. (14 days for Writing Guidelines and Talk Page Proposals)

====Support====
 * 1) [make a statement indicating that you support your proposal]

====Oppose====

====Comments==== - Users will now be able to vote on your proposal, until the set deadline is reached. Remember, you are a user as well, so you can vote on your own proposal just like the others.

To support, or oppose, just insert " # at the bottom of the section of your choice. Just don't forget to add a valid reason for your vote behind that tag if you are voting on another user's proposal. If you are voting on your own proposal, you can just say "Per my proposal".

Talk Page Proposals All proposals dealing with a single article or a specific group of articles are held on the talk page of one of the articles in question. Proposals dealing with massive amounts of splits, merges or deletions across the Wiki should still be held on this page.


 * For a list of all settled Talk Page Proposals, see here.

Rules
 * 1) All active talk page proposals must be listed below in chronological order (new proposals go at the bottom). All pages affected must be mentioned in the brief description, with the talk page housing the discussion linked to directly via "". If the proposal involved a page that is not yet made, use to communicate its title. The Deadline must also be included in the entry. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links. Place  under the section's header, and once the proposal is over, replace the template with.
 * 2) All rules for talk page proposals are the same as mainspace proposals (see the "How To" section above), with the exceptions made by Rules 3 and 4 as follows:
 * 3) Voting in talk page proposals will be open for two weeks, not one. (All times GMT.)
 * 4) *For example, if a proposal is added at any time on Monday, August 1, 2011, it ends two weeks later on Monday, August 15, 2011, at 23:59 GMT.
 * 5) Talk page proposals may be closed by the proposer at any time if both the support and the oppose sides each have fewer than five votes.
 * 6) The talk page proposal must pertain to the article it is posted on.

List of Talk Page Proposals

 * Split Roof into separate articles. (Discuss) Deadline: March 31, 2013 23:59 GMT
 * Unmerge Leo Luster from Bluster Kong. (Discuss) Deadline: April 7, 2013 23:59 GMT
 * Merge Giant Shy Guy to Shy Guy (Discuss) Deadline: April 8, 2013 23:59 GMT
 * Rename Ice Podoboo to "Blue Lava Bubble". (Discuss) Deadline: April 8, 2013 23:59 GMT
 * Merge Star Marker with Power Star. (Discuss) Deadline: April 8, 2013 23:59 GMT
 * Create List of Nintendo Land staff article (Discuss) Deadline: April 9, 2013 23:59 GMT
 * Split off the Mario Party section in Power Star and create a new article on that section. (Discuss) Deadline: April 10, 2013 23:59 GMT
 * Delete or Merge List of Golden Bananas in Donkey Kong 64. (Discuss) Deadline: April 12, 2013 23:59 GMT

Writing Guidelines
None at the moment.

Make an iPhone/iPad app
My idea is to make an app for the iPhone or iPad that links you straight to the wiki. Since not entirely nessecary, it should be free. I got this idea because Khan Academy has the exact same thing as I'm suggesting. What's more, we'll be the FIRST wiki to do this!

Proposer: Deadline: April 1, 2013, 23:59 GMT

Make an app

 * 1) Per proposal.
 * 2) What if you want to go on the Mario wiki and you're on vacation with only your iPhone/iPad/iPhone (no laptop or computer) and had free time?  I feel it's necessary for an app.

Don't make an app

 * 1) &mdash; You yourself state that creating an app is unnecessary. Why would the Wiki garner from a completely unnecessary addition that isn't even provided by the Wiki itself, but some other second-party or alternatively third-party management getting in the way? I just don't see it improving the Wiki at all.
 * 2) It's impractical, it'll be annoying to create in the first place, and it's simply unnecessary for both the average wiki visitor and the average wiki editor.
 * 3) Per all, completely unneccesary.
 * 4) Like what the other's said
 * 5) That is just useless.
 * 6) Like Phoenix said somewhere other than here, why would we need an app when a home screen shortcut does the job?
 * 7) - Per all.
 * 8) - Per all.
 * 9) - Per all.
 * 10) Per all.
 * 11) Per all.
 * 12) Unnecessary, waste of money. Per all.
 * 13) — "…What's more, we'll be the FIRST wiki to do this!". …You probably ignored that Wikipedia has an indipendent iOS app, too. And there's Wikipanion, still for iOS, that did the already done job: you can have more than one wiki in the same app, you can jump to a specific section without going up the page, and several more features… Per all.
 * 14) Like RandomYoshi said, the proposer himself stated that an app is unnecessary. Per all.

Comments
@MortonBoo99--You can view and edit the wiki from those devices. In fact, I'm writing this from my iPod.--

Even though I oppose the app, I think a mobile site might have some use (makes it easier to edit from mobile devices). I don't know though, you'll have to bring up anything like that with .--

I agree with Mariotime11

Removals
None at the moment.

Spoiler Template
I think we should use a template for articles that states that the page contains spoilers, a lot of other wikis have them. Like for example, what if someone was thinking of buying Luigi's Mansion: Dark Moon and skimmed the article to read about it a little? The article has spoilers such as the game's ending right out in the open, so at least we should have a template we can put on SECTIONS that contain spoilers.

Proposer: Deadline: April 15, 2013 23:59 GMT

Support

 * 1) Per proposal.

Oppose

 * 1) I'm opposing for the reason that users shouldn't have to manage Spoiler templates and decide when they should be added or removed. And when people visit this site to read our articles, they don't want to see distracting notices littered around. Pages here are to be written and upheld in an encyclopedic view, and we shouldn't bend our standards and consistency just to suit certain individuals.
 * 2) Take pages such as Bowser, which scatters spoilers amongst non-spoilers like salt and pepper and blurs which is which (for example, in this day and age, is it really a spoiler that the final boss is Yoshi's Island is Giant Baby Bowser?). Take pages such as Doopliss or Shadow Queen, where the title or even mere existance of the page is a spoiler.
 * 3) - Definitely per YoshiKong. I was going to write a small text explaining the reasonings, but he said it the best.
 * 4) - Per all, and per the proposal that got rid of our original spoiler templates. There are spoilers everywhere, as is to be expected of a Mario encyclopedia; we have a disclaimer about it, but beyond that, it's the reader's responsibility to avoid spoilers, because marking them is way too much trouble and looks like crap.

Miscellaneous
None at the moment.