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
 * 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 start to discuss on the issue. 24 hours after posting the proposal (rounding up or down to the next or previous full hour, respectively, is allowed), the voting period begins. (The proposer is allowed to support their proposal right after posting.) Each proposal ends at the end of the day one week after voting start. (All times GMT).
 * 3) Every vote should have a reason accompanying it. Agreeing or seconding a previously mentioned reason given by another user is accepted.
 * 4) 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. The voter can remove or rewrite his/her own vote at any time, but the final decision to remove another User's vote lies solely with the Administrators.
 * 5) All proposals that end up in a tie will be extended for another week.
 * 6) If a proposal has more than ten votes, it can only pass or fail by a margin of three votes. If a 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.
 * 7) 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.
 * 8) No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
 * 9) Proposals can only be rewritten or deleted by their proposer within the first three days of their creation. However, the proposer can request that their proposal be deleted by a Sysop at any time, provided they have a valid reason for it.
 * 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) 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.
 * 12) Proposals cannot be made about System Operator promotions and demotions. Sysops can only be promoted and demoted by the will of Bureaucrats.
 * 13) If the Sysops 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.
 * 14) No joke proposals. Proposals are serious wiki matters, and should be handled professionally. Joke proposals will be deleted on sight.

The times are in GMT, 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 Monday night at 23:59 GMT, the deadline is the night of the Tuesday of the next week at 23:59 PM. If it is posted a minute later, the deadline is 23:59 PM of the Wednesday of the next week, since midnight is considered to be part of the next day, as 00:00 AM.

Basic Proposal and Support/Oppose Format
This is an example how your proposal should 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]". - ===[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: Voting start: [insert a voting start time here, f.e. "January 1, 2010, 14:00". Voting start times are 24 hours after the time at which the proposal was posted, as described in Rule 2 above.] Deadline: [insert a deadline here, 7 days after the voting start, at 23:59 GMT.]

====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.

How To

 * 1) All active talk page proposals must be listed below in chronological order (new proposals go at the bottom). All pages effected 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 heading.
 * 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. There is no 24 hour delay between the posting of a talk page proposal and the commencement of voting.
 * 4) Talk page proposals may be closed by the proposer if both the support and the oppose sides each have fewer than five votes.
 * 5) The talk page proposal must pertain to the article it is posted on.

List of Talk Page Proposals

 * Move Time Attack informations to the relevant games page (Discuss) Deadline: February 3, 2011 23:59 GMT.
 * Either delete Mario's Overalls or merge the article to Mario. (Discuss) Deadline: February 11, 2011 23:59 GMT.
 * Merge Lava Bubble to Podoboo (Discuss) Deadline: February 15, 2011 23:59 GMT.
 * Merge Sparky to Podoboo (Discuss) Deadline: February 15, 2011 23:59 GMT.
 * Merge Casanova Koopa to Luigi (Discuss) Deadline: February 16, 2011, 11:30 GMT.

New Features
None at the moment

Removals
None at the moment

Merge all the Super Strikes
The proposal made in front of you is to merge all the super strikes into the Super Strike article. Reasons why: one, the Mega Strikes are all in one article. Two, all of the super strikes, as their individual respected articles, are stubs. And three, to keep consistency.

Proposer: Voting start: February 1, 2011, 19:00 Deadline: February 8, 2011, 19:00

Support

 * 1) I am Zero! Per Proposal. Zero signing out.
 * 2) I agree. It's better because it gets rid of some small pages on the wiki.
 * 3) Seems reasonable
 * 4) Per NSM.
 * 5) This is a great idea. It has consistency to it, and it is like the Mega Strike article. Per proposal.
 * 6) What we currently have is inconsistent, and Super Strikes are not too different from each other than aesthetics.
 * 7) I'll agree. Merge into one Super Strike article!

Oppose

 * 1)  - I tried to add the necessary info about the moves as far as I know, including their meanings in other languages, and despite they aren't lengthy enough, I have to oppose because they have their own name and, it seems, they have all the info that can offer; the stub template shouldn't explain the current state of these articles actually. On a side note, the Mega Strikes articles is right, because the developers didn't appoint a name for each captain's MS - excluding Japan.

Comments
I agree, we don't need an article on every single of these non-significant elements of the game. Actually, only one of the articles is a stub.
 * What about Skillshots ? Would they end up being merged too?
 * M&SG: I think that skillshots would be OK, this proposal doesn't include them. That would require another proposal.

I have a question, what would we do with the names-in-other-languages sections if it is merged all?
 * ==Names in Other Languages== / ===Fire Strike=== / ===Heart Strike=== / etc. (I assume that Fire Strike and Heart Strike exist...)
 * I think that'd look bad: it'd be better to put the templates in the specific strikes' sections (we'd have to use sections instead of a chart like in Mega Strike, but when it comes to lists, I think sections are better for navigation anyway: you can redirect the old pages straight to them). -

Miscellaneous
None at the moment