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) If anyone has an idea about improving the wiki or managing its community, but feels 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.
 * 2) The voting period begins 24 hours after the proposal is posted (rounding up or down to the next or previous full hour, respectively, is allowed). The proposer is allowed to support their proposal immediately, but all other users may only edit the Comments section during that initial 24 hours. Each proposal ends at the end of the day one week after voting start. (All times GMT).
 * 3) *For example, if a proposal is added on Monday night at 22:22 GMT, the voting starts at 22:22, 22:00 or 23:00 on Tuesday and the deadline is the night of the Tuesday of the next week at 23:59 PM.
 * 4) Every vote should have a reason accompanying it. Agreeing with or seconding a previously mentioned reason given by another user is accepted.
 * 5) 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 their own vote at any time, but the final decision to remove another user's vote lies solely with the Administrators.
 * 6) All proposals that end up in a tie will be extended for another week.
 * 7) 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.
 * 8) 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.
 * 9) No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
 * 10) 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.
 * 11) 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.
 * 12) There shouldn't 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 creating a PipeProject.
 * 13) Proposals cannot be made about sysop promotions and demotions. Sysops can only be promoted and demoted by the will of bureaucrats.
 * 14) 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.
 * 15) 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 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 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 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

 * Split Ashley and Red (Discuss) Passed
 * Merge Whispy Woods to Green Greens and Dream Land (Discuss) Deadline: March 29, 2011, 23:59 GMT
 * Split the SSBB section of Mario Circuit into its own article as (Discuss) Deadline: March 29, 2011, 23:59 GMT
 * Merge Squarp Hole to Squirps (Discuss) Deadline: March 31, 2011, 23:59 GMT
 * Merge Giant Donkey Kong to Donkey Kong (Discuss) Deadline: 2 April 2011 23:59 (GMT)
 * Merge Giant Bowser to Bowser (Discuss) Deadline: April 3, 2011 23:59 GMT
 * Split Arcade game from Arcade (Discuss) Deadline: April 4, 2011, 23:59 GMT
 * Delete Climbing Koopa (Discuss) Deadline: April 4, 2011, 23:59 GMT
 * Merge L33t Hamm3r Broz. to Hammer Bros (Discuss) Deadline: April 5, 2011, 23:59 GMT
 * Split Gramma Red and Gramma Green into two separate articles. (Discuss) Deadline: April 5, 2011 23:59 GMT
 * Split Young Cricket and Master Mantis into two separate articles. (Discuss) Deadline: April 6, 2011, 24:00 GMT
 * Split Krochead into Red Krochead and Green Krochead. (Discuss) Deadline: April 8, 2011 24:00 GMT

New Features
None at the moment.

Remove Spoiler Templates
These templates ( and ) are pointless and ugly, and they should have been scrapped years ago. A database about the Mario series is obviously going to have Mario spoilers: people shouldn't need us to tell them that, and common sense can easily replace the way we're using the templates now. If you don't want ending details, stop reading once you get past the parts you already know in the story section of the game/movie/etc. page, and don't read the pages of characters (or whatever) from the game/etc. that you haven't encountered yet on your own. As for the Histories of recurring characters, almost every section is a spoiler (or has the potential to be one), but we can't possibly put templates everywhere - that'll look silly, which is probably why it hasn't been done (i.e. Bowser's page has a grand total of two sentences roped off). On these template-less articles, common sense is the only thing keeping readers from spoiling all the other games/etc. whenever they go there, and it seems to work just fine: the same principle can easily be applied to the entire database. The only times readers can be ambushed by spoilers is in sections dealing with multiple sources at one time (namely Trivia sections, but also things like "Powers and Abilities", "Personality" and even introductions), and for the most part, spoilers aren't even put on these parts! Fat lot of good that does the readers, but trying to change that would look just as bad as putting dozens of spoilers throughout History sections: the templates break up the flow of our articles badly enough as is. Putting spoilers right at the tops of pages looks bad too.

Simply put, everything is a spoiler to some extent, so we'd be wiser to wash out hands of the entire template nonsense and simply make a blanket statement on About warning people that they're reading at their own risk. There's no need to put it on the Main Page: everyone should realize that the Super Mario Wiki, "with 11,389 articles on the complete Mario series", will have Mario spoilers - our coverage wouldn't be complete if that wasn't the case. It's our job to present our readers with all the info we can: how they actually go about reading it (or not) is their responsibility, not ours.

Proposer: Voting start: March 19, 2011 2:00 GMT Deadline: March 26, 2011 23:59 GMT

Support

 * 1) - Per my proposal. I've wanted those templates removed since 2009.
 * 2) - I agree that most things are spoilers. I've seen many spoilers that don't have the spoiler template.
 * 3) - Per proposal, except I think that a spoiler statement should be put on the main page.
 * 4) I am Zero! At first I thought it will be a bad idea since some people may overread, but your argument is a good, complete reason, per proposal. Zero signing out.
 * 5) – I agree with Walkazo. Having spoiler templates on pages is just unnecessary. As was mentioned, we are a wiki that boasts about complete coverage of the Mario-series; it should be known that our articles will contain spoilers.
 * 6) Spoilers are all over this Wiki; we shouldn't fill articles with a worthless template that warns people about spoilers when they already should be aware that there are spoilers on a site about the entire Mario series. Putting the warning on a single page such as About would work just fine, since new users are expected to read that page when they join. Per proposal.
 * 7) - Per all. Perhaps we can mention it in the sitenotice ("it" being the removal of the spoiler tags).
 * 8) Per MCD. Something like that works quite well on other wikis (eg. Zelda Wiki).
 * 9) - Per all.
 * 10) - Per all.
 * 11) - Per all. I mean I don't like the templete, and if your reading the storyline of a game, you know it'll give out spoilers.
 * 12) - We are an encyclopedia. Our job is to cover all information available, and people should be smart enough to realize that "all information available" really does include all information available. We don't need to disrupt the formatting of our articles with templates that state the obvious. It looks unprofessional. Giving out a general warning on a high-traffic page is totally sufficient.
 * 13) Per proposer.
 * 14) Per Edo.
 * 15) - Per Walkazo, FF65 and Edo.
 * 16) Per all.
 * 17) I was with you in the start, so I wouldn't change my opinions. Per all.
 * 18) I had an epiphany last night about the whole reason I was opposing this. I was comparing us to Bulbapedia, where they have spoiler templates. But there, they are only on articles about anime episodes or movies. Here, they aren't necessary because we're dealing with games. Sorry about all of my indecisiveness and lack of consistant logic to all, but especially myself.
 * 19) Per Fawfulfury65 and Super Mario Bros.
 * 20) But I think that the NIWA Metroid wiki has it right when they have a warning at the top of the page warning of spoilers, not where the spoilers are. "This article contains various irremovable spoilers. Read at your own risk!" warnings are also only on the new game articles. I think those would be more appropriate.
 * 21) I've often read articles on games I was currently playing and I'll be honest, it's not hard to realize when you should stop reading.
 * 22) -Per all.
 * 23) I wholeheartedly agree with you Walkazo! It took me a while, but I finally came around to your way of seeing things; the spoiler templates are obtrusive and unnecessary. If you wanna get rid of them, I'm on your side. :)
 * 24) Per all.
 * 25) Per all.
 * 26) - My conditions have been satisfied, now I reiterate that the spoiler templates are ugly and annoying; they never fit where you want them to and are just horrible for page placement. Anyone who cares enough will check the, now readily-accessible, about page.

Oppose
No offense Walkazo, but when I read this proposal I thought it was a joke at first because I thought that it was so obvious that spoiler warnings are necessary. First off, yes, we will have spoilers, but when going through articles, people don't want to see what is going to happen at the end of a game. Putting something in the About page is a good idea, but removing the spoiler templates is unnecessary. To be honest, what guest here reads About before getting information from one article on what they need to know? The spoilers keep people, and remember there are younger kids here as well, from finding out what happens in the end/climax of whatever will be spoiled. Removing those templates would also mean that we have to go to every article around with them and remove them, which is very tedious. This isn't necessary enough to pass and require people to do that much work, and I believe it is a common courtesy to anyone who reads the articles here to have a small warning before reading anything that may spoil the end/climax of a game for them that they do not want to find out. Also, the fact that everything does contain spoilers doesn't warrant that we remove the templates because some are much bigger than others, and I know we are all smart enough to deem what is currently worthy of said templates and what is not. If it bothers you that much that we have two gray boxes about a centimeter big in some places on certain articles so that people don't complain that we ruined it for them, I don't know what to tell you. - I don't think that putting the spoiler warning in an obscure place like About is a very good idea. Putting a notice on the main page or in the sitenotice would be fine; people actually read those. But I forgot MarioWiki:About even existed before today. The place for important information that all viewers should know could be on the article itself, it could be on the main page of the entire website, it could be in a header above every single page, there are many places it can be, but a place it can't be is on an out-of-way page that is often forgotten, ESPECIALLY a page that doesn't even have a link from the Main Page. While the template is ugly and annoying, it gets across an important point and if this proposal is going to hide that important point away on a no-traffic page, I can't support it.
 * 1) - Per all except KKR (because I really don't understand the last part). Many people - such as I - often look at pages on the Wiki just to check out certain things on certain games. Yet the spoiler templates keep me from reading ahead in the game so that it doesn't spoil the game for me! My point is that not all articles are going to have spoilers, but some articles will have more major spoilers in one section then it does in others. Although we should all know that pretty much every article will have spoilers, its a nice reminder for some of us that want to not be spoiled at very important secretive information. I really think that without those spoilers, people who want to not be spoiled on major things would end up reading to far ahead because they wouldn't know when the major spoilers actually comes in.
 * 2) Per Baby Mario Bloops, but if the proposal WERE to pass, I would suggest to add a warning to not only About but the main page as well, since most people will come to the main page.

Comments
So basically, you are proposing to remove "spoiler" tags because we're a complete Mario encyclopedia and people should know that since we are complete, they already know that they are warned? I'm with you. I think the title text on the main page: '''Welcome to the Super Mario Wiki! with (insert number here) articles on the complete Mario series''' should be enough to warrant a spoiler warning to anyone.
 * Yep, that's exactly what I'm saying. -

Would something similar to what Zelda Wiki does, such as at the top, a notice saying "this wiki contains spoilers, read at your own risk" be a good idea? I get what your saying, just trying to clear up any ambiguity.

Although I support the rant that I previously ranted up there, I apologize for the length and unclearness of it.


 * @Bop1996 (although it applies to other people's comments/votes too): We'll have a message like that on About, but I don't think it's necessary to put it on the Main Page or on the SiteNotice (although I've already talked to the other Sysops and we are going to put a temporary notice about spoilers and the removal of the templates if this proposal passes, but that'll only be until SiteNotice is needed for something else). Zelda Wiki's warning is rather tongue-in-cheek; obviously their database will have spoilers of they want to cover the full series and they probably know that it's a bit ridiculous that they need to spell it out for people. Same thing applies here, but I think no warning would be better than a sarcastic one. Of course, if everyone wants a warning on the Main Page or something, another proposal can always be made; where the wiki-wide warning goes is a secondary aspect of this proposal - my main concern is the templates. To that end, if anyone wants to vote against the proposal just because of the "Main Page or MW:About" question, they should really reconsider. There will be time to move the alert before the SiteNotice changes, so the "out-of-way" locale won't ever be the readers' only resource (I'd personally be fine if another proposal just about the warning is made before the 4-week grace period is over, since it won't really be overturning this one, just modifying it a little). (On a side note, MarioGuy1: technically, MW:About is linked to on every page, including the Main Page, and I personally have checked About pages when visiting new wikis from time to time, although I realize I'm probably an aberration.)
 * @Bowser's luma: First of all, your argument about forcing people to do a lot of work isn't applicable, because I'm willing to remove every single template myself. That kind of gnomework is my speciality: I don't want any help. Secondly, it's not really our place to decide what's a "big" spoiler or not: that's making value judgements, but an encyclopedia should just present the facts; it's also subjective and can be different for different people. Obviously it wouldn't be the end of the world for people to know that SMB has a happy ending, but what about other side-scrollers? YIDS has a few twists and turns, yet it's not marked on Baby Bowser's article, nor is M&L:PiT, which is an RPG: you'd think these at least should be marked. And how about other media? In my opinion, the kicker of Super Mario Bros.: Peach-hime Kyushutsu Dai Sakusen! is much bigger spoiler than Bowser's battle tactics and his ending size in the finale of SMG2, and yet the latter is the one with the template. Why? Who decided that? What's the criteria they used? Fact is, there is no criteria, and that is not how we run this wiki. That's my main beef with these templates: if they were only eyesores (which they're not: they just wreck the flow and look out-of-place in an encyclopedia), I could live with them, but they're inconsistent, unofficial and ineffective. It's a broken system, and people would be better off regulating themselves than relying on it anyway. Like I said in the proposal, it's not that hard to avoid spoilers on your own. For example, I've avoided spoiling M&L:BIS's ending details for the last two years simply by not reading certain pages and sections - not once has a spoiler template helped me do that (Bowser's page doesn't even have one, yet I've been able to browse it dozens of times: I just skip that section). I'm sure even little kids can figure out when to stop reading too: kids are smart (or at least the ones I know are). Anyone who blames us for their own lack of self control and common sense isn't worth fussing over.

I think it would be fine to take the spoiler templates away, but why not just put a "This wiki contains spoilers" note on the main page? I know it's kind of obvious, but it really can't hurt, and it seems like the more considerate thing to do.
 * But where would it go? The only place I can see it being appropriate would be in the "Welcome to the Super Mario Wiki!" part, but how? Expanding the second line? "with 11,392 articles on the complete Mario series including spoilers"? That sounds really lame; people will read that and think "well, duh". Looking at pikipedia:, skipping a line and then adding the warning would also look bad, and it'd mess up the spacing with the link box. So yes, it could hurt, and while it's considerate, I don't think it's worth it: people should know better than to not expect spoilers here. Not all wikis feel the need for spoilers or warnings on the main page: I couldn't find anything on smashwiki: or dkwiki:. Wikipedia's got a policy page and a notice template explaining why they don't fuss about spoiler alerts and consider the section headers of the articles themselves and their content disclaimer to be fair enough warning. -
 * To be completely honest, I think what Pikipedia did there doesn't look that bad. I wouldn't have a problem with a line like that in that position. -
 * I think that most of the debate now is about what to replace the templates with. I agree that it could just as easily be done with another proposal, but I'm not sure what is the best way to replace them. I agree that it seems a little obvious that we'd have spoilers, but it would clear up a lot of potential confusion if we had a warning where everyone would see it. The argument about Mariowiki:About makes a good point. I count myself among the people who read about the wiki before using it, and on ZeldaWiki they just link to their about page on in big bold letters, and that seems to work well. Would having an "about us" link on the main page under the "Welcome to the Super Mario Wiki" heading be a bad idea?
 * I think linking to our about page would be a very good idea: there's room in that last line of links for one more (making it "Anniversary | Sandbox | Help | About Us"), so it wouldn't mess up any spacing, unlike adding an entire spoiler warning line like Pikipedia. You're also right that the debate is mostly about what to replace the templates with, which is why I think voting because of that should be left for another proposal (but of course we can still discuss it here in the Comments): there could be voting options for "on the Main page" or "on MW:About", and maybe some other solution (like making it the default SiteNotice for when we have nothing else to say). I actually thought about including multiple headers in this proposal (one for my preferred MW:About solution and one for the Main Page compromise), but decided against it, as it'd dilute the support for the main issue of removing the templates. -

Guys, it is pointless to utilize the sitenotice to warn people about spoilers. The sitenotice is strictly user-specific, meaning that guests cannot see it anyway.-- 12:52, 19 March 2011 (EDT)

@Walkazo: I too favor having it on MW:About, what I'm wondering is, do we need a new proposal afterwards to decide or should we just change it now? Because if the templates are removed, we need a solution as soon as possible. Also, is there a way to modify the spoiler templates so that they add the article to a category for tracking down all the templates?
 * When the proposal passes, I'll add a small little section to MW:About concerning spoilers immediately, before I even start taking template down (I'll write it ahead of time and put it in my userspace to make sure the other admins are cool with it). A second proposal would be to change that initial arrangement, but no matter what, there will be a warning somewhere. As for the link to MW:About from the Main Page, we probably don't need a proposal: I was planning on simply asking Steve to add one / let us add one sometime this week. And finally, there's no need to alter the templates: if you look in the toolbox on the sidebar, there's a link to Special:WhatLinksHere, which can be used to find every page containing or linking to the page you're on. I use it all the time for maintenance work just like this. -
 * That sounds like a good solution, I should have remembered the "what links here" feature though *facepalms*.
 * However, I am on the disagreeing side on putting it in MarioWiki:About. I'm pretty sure the majority of guests who want to look up information wouldn't give two hoots about viewing MarioWiki:About.
 * BLOF: Yes, and most of the people who come here looking casually that don't read the about page probably wouldn't be upset about reading spoilers. If they were worried about spoilers, they would probably go to the About page and see that we have spoilers. Then they would know and avoid the sections they thought might spoil the game for them. Putting the About page on the Main Page with the rest of the links will prevent a lot of cases where people didn't know how to find the About page.

I knew I would get a lot of flak for this. The spoiler templates are apparently not needed, and I don't feel too up to getting in an argument about this anymore. I'm gonna stay neutral and watch this from the sidelines now.

King K Rool, your vote isn't making much sense. Nobody is going to remove any information from anything. This proposal merely deals with the removal of a few templates that add nothing to the page. Please reread what is proposed here. -

Hey y'all, I'm fine with removing the various warnings all around the wiki, but we should at least throw a little warning on the Main Page that says something along the lines of "this wiki has spoilers, bro." Not sure if anyone already said this (I didn't read the whole conversation), but I think it would be a nice, little, professional warning that could apply to the whole wiki. lulz, probably should have read the whole convo before posting this. Have a nice day! :) -

Now that I have changed my vote, you (Marioguy1 and Kaptain K. Rool) should change yours becuase they reference the now nonexistant vote of mine.
 * They don't have to change them: in the past (although I don't remember the specific proposal), we've kept disowned votes like yours around in slashed-out form. I think we moved the vote to the bottom last time, since it messed up the numbering, but since yours is at the top, rather than in the middle, it can probably stay there. If a vote's per'd by someone or discussed in the comments, it's best to keep them around for the record, or the things talking about them won't make sense. Like, if someone re-reads this proposal in a couple years and sees me arguing over points that were made in a vote you never apparently made, they'd get confused (or they'd think I'm crazy, and I obviously don't want that to happen either :P ). You don't need to remove your comments in this section either; you can't go back in time and un-say your old opinion if someone changed your mind about an issue over the course of a RL discussion, but the important thing is what you currently believe, and I think it's good to have a record of how you came to that final opinion. I know I've changed how I felt about a couple proposals in the past, and I don't mind having the earlier statements still on record. You can always slash the comments out like Bloc Partier, if you want. -
 * When removing a vote, take out your vote and then place strikes in all other votes that reference it (of course only put the strikes through the offending parts of the votes, for example, see what I did to King K Rool's vote).
 * Where is it said that we should do that, exactly? I've checked, and the closest I've come is this proposal, which says "If a vote is determined invalid, whether it is a support vote or an oppose vote, it does not get removed. Instead, it gets striked out with tags." As far as I know, that proposal was never revoked. With that in mind (as well as the reasons I brought up in my last comment), I really think the way I was dealing with the vote should be maintained. -
 * I didn't mean they should change their votes to support, just that they should make it not reference mine.
 * I knew you didn't mean they should support, but they don't have to stop "per"ing your old vote if they still believe in what you said before you changed your mind. -
 * Okay, I think I can summary my vote down here now. I don't think that spoiler templates are necesary, but I think that it should be on major sections like final boss information in game pages or major plot settings that happens that affected the story completely!
 * Ok. I've confused myself so much with this proposal and all the contradictory comments that I don't even know what's going on anymore.
 * @BL: We are probably going to pass this proposal, and when it passes, a link to MarioWiki:About will be added in the row on the main page under the "Welcome to the Mario Wiki" header in the row with Anniversary and Sandbox links, and an update to the MarioWiki about page will be added stating that we have spoilers. This is as far as I understand it.

Allow autoconfirmed users edit other users' userpages
Recently I have seen red links, redirect links, etc. on other peoples userpages along with deleted images and I was wondering if us autoconfirmed users can edit their userpages for errors, etc. It really doesn't make sense that only sysops get to edit this so I set up this proposal. Also, on Wikia we get to edit others' userpages along with most other wikis.

Proposer: Voting start: March 19, 2011 14:30 GMT Deadline: March 26, 2011 3:30 GMT

Support

 * 1) - Because I made this proposal.

Oppose

 * 1) Sysops only edit userpages if they need to. This would let almost anybody put anything on your user page. It's just pointless anyway.
 * 2) - I agree with Yoshiwaker.
 * 3) - Per all. You shouldn't be allowed to mess with other people's userpages.
 * 4) I am Zero! Per all. Zero signing out.
 * 5) Per all
 * 6) Yes, let us support vandalism.
 * 7) - Ask a sysop to fix it. I believe the "Keep Your Hands to Yourself" extension was added to the wiki by Porple because vandals were messing with user pages. It makes complete sense that only sysops and the user that owns the user space gets to edit it. And nobody cares if you can edit others' user pages on Wikia, as we aren't Wikia.
 * 8) No way, I'm sorry, but there's really no reason...
 * 9) Imagine a vandal coming onto your userpage and replacing all of your personal information with fake, unnecessary and inappropriate information that could be offensive to you. This is why only sysops can edit other peoples' userpages. If there's a problem with a userpage, you are expected to ask a sysop to remove it. It only takes a minute to ask.
 * 10) - Per all. Only Sysops can be trusted with these powers. In my opinion, you've made just another proposal to suit your personal wants.
 * 11) Per all. I like how you have control of your userspace and I don't want a vandal messing up my page, even if I can revert it later.
 * 12) I don't want some random person editing my userpage.
 * 13) Per all.
 * 14) - Per all.
 * 15) Per all.
 * 16) Ummmm editing another person's page? Most users are autoconfirmed, and you never know when someone could VANDILIZE!
 * 17) - None of your points is significant enough to outweight the benefits this extention provides.
 * 18) I've just imagined how my userpage was edited…that's……:(
 * 19) I think once a vandal moved a sysops userpage.
 * 20) - Per all.
 * 21) - Per all.
 * 22) - Per Bowser's luma and Yoshidude99.
 * 23) Per all.
 * 24) Only if we autoconfirmed users can ONLY have the ability to remove fake new message boxes, but this is all or nothing, so I say nothing. Per all.
 * 25) - Where to begin...hmmm...oh yes, no! There is too much vandals around the wiki to even let this happen. Not only that, but some users don't want other users putting crap on their page.
 * 26) - Per my comment below and the rest above.
 * 27) - Per all. Plus, why give normal "everyday" users (I guess you could say that) access to editing other users' own pages? If you ask me, that makes no sense.
 * 28) I like my userpage and don't want anyone editing my page.
 * 29) Okay, so if your proposal passes, I'll erase everything and put on it "?". You could lose a lot of data that way. Per all.
 * 30) Aren't talk page messages enough to offer help? "Your link to [Mario]] should really be Mario . Glad I could help." Or would it be better to have your entire user page destroyed except for that one correct Mario link.
 * 31) - Per all.
 * 32) per all
 * 33) Definitely opposing. Having people wreck up your own userpage isn't fun. Why don't inform them about the error on their talk page instead?
 * 34) I hardly have anything on my page but I still don't want someone making changes to it.

Comments
@Yoshiwaker: We can revert vandalism if they do put junk on our userpages and we do need to help the community too.
 * @Kaptain: Is there ever any really good reason to edit someone else's userpage?
 * Err yes... to replace images and fix red links.
 * I don't think that's a very good reason, but I'll just stop arguing because this would go on forever.
 * @Kaptain K. Rool - Well, that may be true, but what happens when some vandal whams your userpage? I mean, do you really want to be constantly looking over your shoulder and reverting edits every other day...? 15:52, 18 March 2011 (EDT)

I think we would need to talk to Steve about this even if the proposal did pass...
 * Also, on Wikia we get to edit others' userpages along with most other wikis
 * How many of these edits are actually good edits? About 1 in 10, I say. Judging from my userpage at Kirby Wikia, those who have edited it besides me have only inserted derogatory remarks or just complete rubbish on it.

Imagine a vandal coming onto your userpage and replacing all of your personal information with fake, unnecessary and inappropriate information that could be offensive to you.

This. What if people go to my user page and say "I hate (insert any Nintendo character here)!"? It offends me a lot when Kirby or Diddy Kong gets insulted.

Basically, if a user page has any red links, let the Sysops handle that stuff. That's why the Sysops are here; if you want a user page fixed, just contact me or any other Sysop.

@Kaptain K. Rool - Adding on to what I said above: you say we need to "help out the community" by "removing red links, redirect links...along with deleted images," but technically, userpages are not really part of the community in this context. Pretty much the whole point of it being your userpage is that it's, well, your userpage. If other people start editing it left and right, then it's not really just yours anymore is it? That's the one thing that sets userpages apart from every other article on this wiki. In your argument, it seems to me that you're almost saying that the prospect of complete (and possibly recurring) userpage obliteration is better than some of the fairly minor problems you list above. Long story short: the only part of the wiki that we are responsible for improving is the articles. 17:48, 19 March 2011 (EDT)
 * Look you're just embarrassing yourself with this proposal. It's not going to pass by any means.

I can see it possibly working if you could lock off sections of a page. Which would be FANTASTIC! for many articles. E.g. All of the stuff like release dates for past games that aren't going to change could be locked off. But until then...No.
 * Once upon a time, I used Wikia. And a tale from my past would have to be when I was trolled there. How was I trolled? Well, a user went to my userpage and repeatedly replaced it with insults.

Caw?

Merge all of King Koopa's alter egos into one article
On The Super Mario Bros. Super Show! King Koopa has many alter egos. These alter egos are just him in a different costume. The costumes don't give him any extra abilities, they are only seen for one episode, and while wearing the costumes, King Koopa is no different from when he's not wearing the costumes. Thus, I propose to merge the alter-egos of King Koopa that currently have an article (Al Koopone, Captain Koopa, Emperor Augustus Septemberus Octoberus Koopa,Kid Koopa, Koopa Khan, Koopa Klaus (alter ego), Moon Man Koopa, and Robo Koopa (alter ego)) into a single article. I'd prefer merging them to King Koopa's alter egos, but I'll also add a section to merge them to Bowser.

Proposer: Voting start: March 20, 2011, 15:50 Deadline: March 27, 2011, 23:59 GMT

Merge to King Koopa's alter egos

 * 1) Per my proposal.
 * 2) - Per Reversinator.
 * 3) - Per above.
 * 4) - Per all!
 * 5) Per Bloc Partier.
 * 6) Per all.
 * 7) If they give no special powers and only appear in one episode, then why have separate articles in the first place?
 * 8) Per Reversinator
 * 9) - Alter egos really don't need their own articles.
 * 10) Per Mariomario64.
 * 11) PER ALL
 * 12) MergemergemergemergemergemergeMERGE! Per all (merge).
 * 13) - Per Reversinator's comment below (the one after mine).
 * 14) good idea. per all. Because they were a separate article to begin with. We can do this now, and then allow another proposal if people really want the page to be part of Bowser.
 * 15) D'accordo
 * 16) per all
 * 17) Per all.
 * 18) I am Zero! what the heck happen to my original vote Per all. Zero signing out.
 * 19) Per all except M&SG
 * 20) per all

Merge to Bowser

 * 1) I honestly think this idea is better. Per a- There's no one above me!
 * 2) Bowser is no different than the alter egos, thus, it should merge to Bowser.
 * 3) Per all? Yeah... but even better you can just add a link that redirects to the alter ego page.

Comments
I agree. Just as how the Super Strikes and Mega Strikes were merged together, these alter egos should be merged together.

How are you planning on merging? Are you going to add a new column to the table, or do something altogether different.
 * I was planning on adding a new column and giving a short description of the alter-ego's role.

Before merging King Koopa, I suggest that you merge Robo Koopa to Robo Suit, because I feel that information belongs there rather than being deleted. Also, what are we going to do with the Featured Article status on Robo Koopa if this proposal passes?
 * The powers of the suit should go there, and like I said before, I'll give a brief summary on King Koopa's alter egos. And if it's merged, there's no point in keeping the FA status.

Although I believe the pages have enough information to stand by themselves, I'll stay open to any opinions before voting, as I never watched The Super Mario Bros. Super Show!.
 * Most of the info is basically the plot of the episode.


 * Will this proposal unfeature Robo Koopa? I'm not sure the articles that will be merged will be the same quality.

While this is going on, how about merging all of the pages on the (sort of borrowing my brother's idea here, please don't add a megabyte of protests to my userpage, again) Super Paper Mario people, and other single-appearance things?


 * @Mpeng What the heck are you even talking about? King Koopa (Or just Bowser) has nothing to do with Super Paper Mario.


 * @UltraMario3000 - Didn't say he was. I guess this isn't the time or place.

I think Robo Koopa should keep its own article, and FA status - if it's long enough and good enough, what's the point of merging and losing a great article. Instead, we can just use. If we merge it, we're bound to lose some information and that's not good for the Wiki.
 * But that would be inconsistent. Besides, all the information can easily be saved. Robo Koopa (episode) already has a complete record of events, so shortening the alter ego's History into a summary isn't an issue. The Trivia about the RoboCop and Terminator reference can also go into the episode page, and the Powers and Abilities chart can go into Robo Suit (along with the other Trivia point about the "destroy you miserable little meddlers" button). So the only thing we'd be losing is an entry in out list of FAs, but that's a small price to pay for a much more efficient and consistent organization of Koopa's 30+ alter egos. -

Split Category:Donkey Kong Levels into Separate Categories
This is my first proposal. There are many games in the Donkey Kong series. The category, Donkey Kong Levels, there is too much content. It has about 5 different games in one category. I think we should make categories for each game. For example,  Category:Donkey Kong Country Levels , etc. It would be easier to find levels and it wouldn't take up 2 pages! We should make one for every game such as Donkey Kong Country 2, DKC3, DK: King of Swing, etc. It just seems easier to navigate levels. We should also delete the original one if we make other categories. I will add a section for making new categories and I will add one for keep the original one as is.

Proposer: Voting start: March 23, 2011 24:00 Deadline: March 31, 2011, 24:00 GMT

Make a New Category

 * 1) - It is my proposal and I think it would help the wiki and other users by making it simple to navigate levels by games.
 * 2) - That sounds like a good idea.
 * 3) - Per M&SG.
 * 4) Per Kaptain K. Rool.
 * 5) Love it! Per SW and Kaptain K. Rool!
 * 6) Per all.
 * 7) That'd make it more simple. Per all.
 * 8) We don't have all the Mario games in one category.

Keep Original Category

 * 1) - Just use the games' navigation templates: they're supposed to have all the levels listed, and generally they'll be arranged by world, which is a much better way to organize the levels than the alphabetical categories. It's better if all games, DK or otherwise, simply have general categories for all their subjects.
 * 2) Per Walkazo. I don't see why this is necessary.
 * 3) - Per Walkazo and Fawfulfury65's comment below (although FF65 hasn't voted yet).
 * 4) - Is this really necessary? It's sort of like going to the characters catagory and complaining about how they don't have a catagory for just characters from cirtian games. I mean, if you know your alphabet, it should be pretty easy.
 * 5) - per Walkazo and isnt Donkey Kong technically it's own franchise
 * 6) - per all.
 * 7) Per all.
 * 8) - Per Walkazo above and Fawfulfury65 below.

Comments
We shouldn't delete the Donkey Kong levels category because it can be useful in finding many DK levels. Also, if we really want to find information about a Donkey Kong Country 2 level or something, why can't we just look in Category:Donkey Kong Country 2: Diddy's Kong Quest, or the category for any other game? There's also templates that you can use to easily find levels in one of those games.

MS&G: You know your vote is invalid. You can't simply say, "Good idea" if you want to support.

BabyLuigionfire why can't you just because you have nothing new to add doesnt mean it isnt valid other wise like 20 votes from other propsals that say per all


 * If anyone has an idea about improving the wiki or managing its community, but feels 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. Simply saying "Good idea!" is NOT a strong argument. And please don't backsass me like that, it's very rude.


 * @Iggykoopa it doesn't matter that it has its own Franchise, the categories should be made into games

Baby luigi on fire the rules state that Every vote should have a reason accompanying it. Agreeing with or seconding a previously mentioned reason given by another user is accepted.

Merge Minor NPCs with their locationd
I have seen many articles for minor NPCs in RPGs that are extremely small and/or stubs. I think we should merge them all with the location where they are. This would get rid of many stubs and generally make it look better.

Proposer: Voting start: March 27, 1:00 GMT Deadline: April 3, 23:59 GMT

Support

 * 1) - Per my proposal.

Comments
I hate the trigger-happy people on this wiki that shout "MERGE!" to all stubs. First of all, at least three hundred articles on this wiki, if not more, are minor characters. That's a lot of articles. Second, while they are minor, they are still characters, and they are officially named, and thus, they deserve an article. Third, how would this be better? I mean, a lot of the minor character articles are actually decently sized, and merging them would require some trimming, thus reducing quality. Fourth, why their location? Considering the amount of minor NPCs in a town, the articles would look cluttered.
 * Also, small articles are not automatically bad: they might not even be stubs if all the information we could possibly find has been added (stubs are pages lacking info). It makes sense to merge characters who are attached at the hip (it cuts down on repetition and may boost comprehensiveness if all the info is together), and sometimes it is done for the sake of organization and consistency (like King Koopa's alter egos), but none of that is applicable to minor NPCs. -
 * I agree with you 100%, though I do find it funny that you made a proposal to merge all the minor Mario Golf characters into one article and now you're against merging minor characters. --Reversinator 22:32, 25 March 2011 (EDT)
 * Really? That must've been a while ago, because I can't remember doing that at all... -
 * Archive 18. I made a mistake though, you only supported it. You were the only one though, aside from Zero. --Reversinator 22:42, 25 March 2011 (EDT)
 * Ah, that makes more sense; I was a big supporter of making big lists of stuff back them, but I was pretty sure I hadn't made any proposals about it (the closest I came to one had something to do with Keys, iirc). Anyway, 2009's ancient history now: I'm not nearly as zealous about merging these days (well, depending on the situation, at least). -

@Reversinator: It's not just because they're stubs, but also that they are EXTREMELY minor. Most of them just say a couple of lines and do nothing else.
 * Walkazo: Didn't you co-write that with SMB? Anyways, to all users, if you see an article marked as a stub and it's off a (as this guy puts it) "minor NPC" then, unless the article has like two sentences or something like that, remove the template. It is the easiest way to get rid of stubs. When I'm bored and looking for something to do, I go to this page and just click random things on the list and get rid of any unnecessary stub templates.
 * Yeah, we were working together on it together, but I didn't think we ever came forward with a proposal, in the end: I got swamped by RL stuff, or something. Anyway, like you said, Stub templates are definitely put on things that aren't stubs all the time and fixing that is a very good thing to do, but I'd like to emphasize that people should look at them on a case-by-case basis (like most things on the wiki, really). One paragraph is probably fine for a lot of NPCs (or whatever), but some "minor" characters could have a lot of random info attached to them, and in those cases, a paragraph might indeed be short-changing the readers, in which case it would be a legitimate stub. Or at least, that's how I look at it. (Also, "minor NPC" has been a term around the wiki for years: this guy didn't come up with it.) -
 * "working together on it together"? Aaanyways, do you think we could make a list of Minor NPCs? It wouldn't (necessarily) have to be in a mainspace article, but I think I'd like a list telling me what is and what isn't a minor NPC.