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

 * Create separate articles for the Adventure Mode enemies (Discuss) Deadline: May 2, 2013 23:59 GMT
 * Rename Big Red Balloon to (Discuss) Deadline: May 2, 2013 23:59 GMT
 * Rename GAME & WARIO (WarioWare: D.I.Y. Showcase) to GAME & WARIO (Discuss) Deadline: May 8, 2013, 23:59 GMT
 * Split Photo Together with Super Mario (Discuss) Deadline: May 13, 2013 23:59 GMT
 * Delete the List of chronological references page (Discuss) Deadline: May 15, 2013 23:59 GMT
 * Delete Count Bleck's Army (Discuss) Deadline: May 15, 2013, 23:59 GMT

Writing Guidelines
None at the moment.

Merge Mario-related controversies into a single page.
After extensively searching both the Wiki and the Forums, I've concluded that the Wiki does not include a page that lists controversies that involve the Mario series, nor has any proposal been made towards creating one. Being Nintendo's flagship franchise, it is apparent that the series has dealt with controversy, with examples such as the Mario Party 8, Tanooki Suit and Ashley's Song controversies coming to mind. Should these issues be detailed in their own article akin to the one on Bulbapedia, or should they continue to be listed in separate articles as sections? The new article would also allow for expansion on these topics, and the inclusion of additional controversies related to Mario that are unmentioned on the Wiki (such as PETA's recent KFC campaign).

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

Support

 * 1) Personally, I believe that there aren't enough controversies to compose a really long article. However, I also believe that this article could include smaller examples such as the satanic references in Super Mario Bros. 3, Birdo's gender, and lawsuits against Nintendo that pertain to its systems, thus giving it more depth and making it a significant contribution to the Wiki. Plus, the Wiki lists the inclusions of Mario in both positive (main appearances) and neutral (cameos and the like) perspectives, but why doesn't it list the inclusions of Mario in a publicly negative perspective? I created this proposal because the idea has never been raised before, which is really surprising to me. Anyway, I support the merge of these controversies to form a new article.
 * 2) Seems like a good idea, the page could be laid out like the List of Mario references in various forms of media.
 * 3) - I feel this sort of content can be really attractive for readers, and having them all together in one place would be convenient. However, as a fellow staff member had mentioned in earlier discussions, we have to be really cautious not to be biased. A page like this requires to be absolutely objective, stating only the facts and not going into speculation; it's up to each reader to draw his conclusions on subjects like this.
 * 4) Per Tucayo.
 * 5) Per Tucayo.
 * 6) - A "List of controversies in the Mario series" page is a good idea, for all the reasons proposed (although "merge" is a bit of a misnomer, as the info shouldn't be moved from the individual articles, just copied). Also, to elaborate on the point Tucayo alluded to, this sort of article will need to have references for every single point (direct quotations from the games works), to ensure that we're keeping our facts straight, our writing unbiased, and our credibility high.
 * 7) Per all.
 * 8) &mdash; Per GBAToad, Tucayo, and Walkazo. I especially agree with the notions that this isn't a proper "merge" and that the content should be completely based on references to avoid bias and misleading "facts."
 * 9) - Per SMB.
 * 10) - Per Walkazo's support reasons.
 * 11) Per all. I don't see why not.
 * 12) Per SMB.

Removals
None at the moment.

Accurate titles for files
I have noticed files with, , and. Not only does this decrease professionalism and violate the image policy, but it also makes it more difficult to search for files (e.g. a search for filenames containing "toad" would leave out results if an undescriptive title was used). Even if these images are "only used once or twice", a descriptive title is still more useful.

I am proposing that we go back and rename files used in mainspace/gallery/etc. ('Shroom and userspace would be exempt from this, basically) articles that are breaking the policy, as well as enforcing a standard based and possibly expanding on what is written in the image policy I linked beforehand. I would not be opposed to going back and helping with the work, assuming this proposal passes.

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

Support

 * 1) - Per proposal.
 * 2) - Per proposal.
 * 3) - Per proposal.
 * 4) - Per proposal, because names should be more clear and appropriate.
 * 5) - I agree, specifically with the part about searching for files. Having fun is good and nice, but when functionality is compromised, that is when priorities must be set.
 * 6) - Per all.
 * 7) Per all.
 * 8) Per all. I used to like uploading retarded file names, but now, I don't.
 * 9) While I don't agree with the "professionalism" part (it can be both fun and presentable), we need standard and to-the-point file names instead of creative ones. I stopped making up my own file names a while ago. Also, per Walkazo's comment.
 * 10) Per all.
 * 11) Per all.
 * 12) Per proposal.
 * 13) Per proposal.
 * 14) &mdash; Per proposal, and Turboo and Kibago specifically.
 * 15) Per proposal.
 * 16) - Per SMB.
 * 17) - Per all.
 * 18) Per all. "Happy Fatty"? That's some serious BJAODN right there!
 * 19) Oh god, "Babypeachyushee'seyelandeees". I cringe at the thought of doing that. I'm  glad to god I decided to stop that while I had the chance. Per all.
 * 20) Per all. I think to move 530.jpg to Koopa Bros Bowser Castle.jpg.

Comments
At PidgiWiki, we have a standard which works well. What we do is put the subject of the image first, followed by a hyphen, and then the game/event is comes from.

For example: "Bowser Artwork - Super Mario Bros." If there is an alternative image, we use "Bowser Artwork (alt) - Super Mario Bros.", "Bowser Artwork (alt 2) - Super Mario Bros.", etc. This could be a good way to go.-- 05:17, 28 April 2013 (EDT)
 * I don't really like an idea of a naming standard, since that means we have to rename every single file in this wiki to match the standard. I think the best way to go is to at least make sure the image is descriptive, professional, and follows the image use policy. We don't need a single standard for this.
 * If this proposal passes, we're going to be renaming all of the files anyways. I wouldn't be opposed to a standard naming convention, as long as it isn't too convoluted.
 * I don't think we should rename all the images, just the ones that seem to be in violation of policy. While YK's suggestion could work as a guideline placed on the image policy page (even then, like Walkazo said, we should focus on keeping names straightforward), I don't think we need to enforce it, especially since a lot of filenames work even if they're simply the name of the character or the location. - Turboo (talk) 18:46, 28 April 2013 (EDT)

If we were the impose the standard, we should eliminate the "having fun part" since there is a degree where you may have fun uploading images, and it all depends on the user's personal idea what "fun" is. I know I might sound a wee bit sarcastic here since I did this crap in the past, but if we were to have more functional image files, we need to be as serious as writing articles on this.
 * Removing the "fun" clause has actually come up in admin discussions before, but we never went back and actually got rid of it, but yeah, I'd agree that it'd be better without such a subjective point. As for the overall standard, I think making a rigid formula we have to follow or else would be a bad idea: as long as we can tell what the images are of, if there's some variety, it's not the end of the world. We could add more specific requests to the current "meaningful name" parameter, such as having the name of the game (or an abbreviation), what kind of image it is (profile art, screenshot, boxart, whatever), and what the image is of (name of the character in the profile, name of the level a screenshot it of and maybe some info about the shot, etc.). However, there should also be emphasis on making the names straightforward: I'd argue that "Bowser art SMB" and "Bowser art 2 SMB" would be preferable to the ones YoshiKong suggested, since they're shorter and don't mess around with punctuation (brackets, dashes) and extra words ("alt"). Similarly, even if a screenshot contains Bowser, Mario and a Podoboo, something like "SMB screenshot end of 1-4" would be easier to use than "SMB screenshot 1-4 Bowser, Mario and a Podoboo"; or if a screenshot is of Mario and a Whacka, "PM screenshot Whacka" would be fine, since the Whacka's the important part. But again, most image names are fine even if they don't follow this sort of "what/kind/game" standard, and renaming them would be excessive and annoying, so even requesting those three things should be more of a guideline than a hard rule. -

At the My Little Pony: Friendship is Magic, they also don't use names like File:HappyFatty 9.png. At that wiki, they use descriptive names for photos like
 * We don't follow wikias. Nevertheless, I think putting the description IN the file name is a bit unwieldly. I prefer the description to be reserved for the aboutfile.
 * Yeah. Otherwise, the filename is too much of a mouthful. :P.

Miscellaneous
None at the moment.