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.
 * 7) When a talk page proposal passes, replace its deadline with "Passed" but do not remove it from the list below until the proposed changes have been enacted.

List of talk page proposals

 * Delete (Discuss) Deadline: May 27, 2013, 23:59 GMT
 * Create a BJAODN subpage for levels (Discuss) Deadline: May 29, 2013, 23:59 GMT

Writing guidelines
None at the moment.

New features
None at the moment.

Removals
None at the moment.

Change Main page rotation to Mondays
The Main Page is very important on the wiki, so why is it that we rotate every Sat.? Mondays are better I think because of the fact it's the beginning of the week. This makes for easier remembering to rotate items.

Proposer: Deadline: May 31, 2013, 23:59 GMT

Support

 * 1) Per above.

Oppose

 * 1) How do you think people remember stuff better on Mondays? Kinda unnessecary (tell me if I misspelled that.)
 * 2) This change is unnecessary and the reasoning for the change is pretty weak. It all boils down to preference, and I don't think we need to change anything here. Sunday, Monday, Tuesday...it doesn't matter at all.
 * 3) And what's the difference? Unnessecary.
 * 4) I see no logical reason for this, it is perfectly fine the way it is.
 * 5) No point.
 * 6) - Well, I don't think it would make that much of a difference, so yeah, per all.
 * 7) I don't think it matters.

Remakes
I think something needs to be done about the way we treat remake games. We have articles for games such as Super Mario 64 DS and Donkey Kong Country Returns 3D, but the whole Super Mario Advance series are all merged with their original games. While those remakes aren't nearly as different as their original games, they still have their differences and should still be treated as other remakes are in the wiki. I propose that we either split all remakes from their original games and give them their own articles or merge all remakes into their original games.

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

Split all remakes into individual articles

 * 1) I say split

Comments
Sorry, it's already an official policy. It just hasn't been enforced everywhere yet. -- 09:53, 25 May 2013 (EDT)


 * So remakes already get their own pages?

Yes, they should. But not all of them have as of yet, as there's quite a bit of work involved. Splitting the article does not just mean to create a separate page. There are individual categories that need to be created, character/enemy history entries to add, templates and (many) links to update. And the article can't just be a cut-paste of the "#Remakes" section of the original article. -- 10:02, 25 May 2013 (EDT)


 * Alright, then I guess I should withdrawal this proposal since there's already the policy.

Note that SMA games are more ports than remakes. A general term would be "reissues" (but that doesn't really matter). 13:55, 25 May 2013 (EDT)


 * Yeah, withdrawing would be best: it's early enough that you can remove/archive it yourself. -

Write "Glitches" Section for levels
I think that if a person knows of a level glitch, but forgot how to do it, they should not have to go down an incredibly long list to find it. This would make the process a lot less tedious as well.

Proposer: Deadline: May 28, 2013, 23:59 GMT

Support

 * 1) Per reasons above.

Oppose

 * 1) Why is this restricted only for levels? Doing so breaks consistency for the rest of the articles. Besides, if they're searching for a glitch, they should use Crtl + F and keywords. All glitches should stay on their respective pages.
 * 2) That would be pointless; there are already glitch pages for almost every game, and as Baby Luigi said, you can just user the "Find" tool to look for certain glitches.
 * 3) Per all. And what if a particular glitch appears in many levels, not just one?
 * 4) Per all.
 * 5) Per all.
 * 6) Per all.
 * 7) - Per all.
 * 8) • Just type "Glitches of " in the serch box and click Search. It's not that hard.
 * 9) Per Once and Only Once it will be found on the level and on the glitches page, and per Baby Luigi.

Comments
I have to say I am in no sides on this one, it sounds like a great idea, but baby luigi IS right, every computer can use ctrl+f to find glitches. Robecuba (talk)

@YoshiKong: Then it would be put in as ex.: this glitch also appears in [insert level(s) where glitch appears here]. MegaDigga3 (talk)

We can add a "See [insert glitches link here] for glitches" or something like that.-- 10:42, 25 May 2013 (EDT)