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
None at the moment.

Writing Guidelines
None at the moment.

Identification in user pages
My idea is that there should be a identification in user pages, like the star identifying Featured Articles. The idea of having colored usernames is a good way to identify who is the proprietor, administrators, bureaucrats and patrollers, but you need to find the username in the Who's Online template or in the history of an article. Also, some users haven't confirmed their accounts, but their usernames doesn't appear colored. To solve this, something like the star in featured articles appear in patrollers, etc. user pages and in non confirmed users, it appear in their talk page. The icon should be a mushroom for patrollers, a fire flower for administrators, a star for bureaucrats, a poisonous mushroom for unconfirmed users, something like that. If someone put the cursor above the icon, a text in a white box saying "This user is a XXX. Click for more information." or "This user didn't confirmed his account." appear, and if someone click in the icon he will be redirected to the Patrollers, Patrollers, etc. page. To unconfirmed users, nothing happens when someone click in the icon.

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

Support

 * 1) We don't have to go to the history of an article or wait to the user be online to see who is bureaucrats, administrators and patrollers. This also make easy to see who is confirmed and who isn't confirmed.

Oppose

 * 1) - I don't think this is necessary, seeing as there are links on the recent changes to the Patrollers, Administrators, and Bureaucrats pages on the line "Wiki staff".
 * 2) - Per TPY.
 * 3) Per TPY.
 * 4) - Per TPY.
 * 5) – There's the name coloring based on the group the users are in to simplify the things, but to be honest I don't like them…
 * 6) - Honestly, I find this to be an unneeded feature; we already have this implement in the "Who's Online" list, as someone stated earlier.
 * 7) Per TPY. In addition, most of the admins currently have userboxes on their pages indicating the position they hold (with a link to the appropriate page).
 * 8) Per Mario4Ever.
 * 9) - Per all.

Comments
Some user may not see these links in the Wiki staff, because it's colored in orange, purple, green and light blue, and other links are in dark blue.
 * Well, I do agree that it's kinda hard to see that those are links, but I still don't think the icon system is necessary - it could be done in a much simpler way. ---

Removals
None at the moment

Change the "The Identifiers of Articles" policy to be decided on a case-by-case basis
I recently left this comment about article identifiers and brought it up a few days later in the chatroom. Glowsquid and Marshal Dan Troop informed me that would be going against what this proposal has laid out. This effectively means edits like these, which were made by the creator of the original proposal, are violating policy right now. I propose we change this policy so that it encourages users to move pages based on common sense, not an unclear one-size-fits-all rule.

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

Support

 * 1) - Per proposal. A policy page for this (instead of just remembering it and enforcing it that way) would be helpful as well.
 * 2) Per Turboo. Consistency is usually desired, but game identifiers aren't always the most suitable for article titles.
 * 3) Per Turboo.
 * 4) - Per all.
 * 5) - Per Turb.
 * 6) Per all.

Comments
About the policy page, I think it's best to outline the guidelines at Naming. -- 03:17, 22 February 2013 (EST)

I think we can nail this down into a formula. If an identifier is needed, the text in parenthesis is determined by: -- 03:38, 22 February 2013 (EST)
 * 1) What the thing is. For example: Dribble & Spitz (souvenir) is correct.
 * 2) If the same type of thing appears in multiple games, use the game title. For example, World 1-1 (New Super Mario Bros. 2) and World 1-1 (New Super Mario Bros. Wii) are both levels from different games. We cannot use World 1-1 (level) for obvious reasons because we need to differentiate between games.
 * 3) If just the game identifier is misleading as to what the thing is, use the game title followed by what the thing is. For example, assume there is a "Dribble & Spitz" souvenir in two WarioWare games. We would use Dribble & Spitz (WarioWare: Twisted! souvenir) and Dribble & Spitz (WarioWare: Smooth Moves souvenir) because without the added "souvenir" text, no one would guess the article was about a souvenir and not Dribble & Spitz themselves.


 * I agree with these guidelines. -- 03:57, 22 February 2013 (EST)

Quick question: can I ask why the three articles you mentioned in violation of the policy?


 * I originally thought they weren't, but the two admins I mentioned in my proposal (Glowsquid and Marshal Dan Troop) told me that they were violating policy by not following the one-size-fits-all rule. -
 * " I know that some of these need to be done in a case-by-case basis, but the vast majority of these are quite simple". I indicated in my proposal that I knew that a all-encompassing rule wouldn't work, but the exceptions are much more rare than the ones that follow the rule. It seems kind of unnecessary to create this proposal, in my opinion.
 * Pretty sure I said that following it as if it was an one-size-fits-all rule would be asinine.--Glowsquid (talk) 15:22, 22 February 2013 (EST)
 * I wasn't entirely sure about that, sorry. I do think Shoey said that it would be a violation, though, so uh... I guess asking other admins for their opinion would be good? I see the identifier suggestions were already implemented on MarioWiki:Naming, so I don't know if this proposal still serves a lot of use. -
 * I don't see how they'd be a violation either: just having game names would be confusing, and as GreenDistaster pointed out, the proposal has a nice built-in allowance for case-by-case exceptions to the rule for situations just like those articles. -

Miscellaneous
None at the moment.