MarioWiki:Proposals

Writing guidelines
None at the moment.

New features
None at the moment.

Remove rule 4 of the talk page proposals
4. Talk page proposals may be closed by the proposer at any time if each voting option has fewer than five votes.

...Why? Why are proposers given the right of closing their proposals based solely on the number of votes? What purpose does this serve when proposers already have the option of closing their proposal within the first six days? If a proposal hasn't received many votes, why is the solution to completely scrap it rather than try to promomte it? What situation would even exist that would require this rule to be invoked (less than five votes on all sides and more than six days have passed), and even then, why not let an admin close it if there's a valid reason for it? If there's no valid reason for closing the proposal, why let proposers close it at any moment they want? Why only five votes in the first place, and not some other arbitrary number? Why do talk page proposals even have a rule that isn't applied to regular proposals?

This rule is pointless in all circumstances and should be promptly scrapped.

Proposer: Deadline: October 14, 2017, 23:59 GMT Extended: October 21, 2017, 23:59 GMT Extended: October 28, 2017, 23:59 GMT

Support

 * 1) Per proposal.
 * 2) Per proposal.
 * 3) So you want to remove it. Why haven't you? (it's basically rhetorical.) Per proposal.
 * 4) No reasoning was provided for why the rule was added, and it's pointless anyways (no one uses it), so per proposal.
 * 5) - As per general proposal rules, every proposer gets three days in which they may alter or remove proposals. That's already a sufficient window to realize if your proposal is sensible and you want to stick with it.
 * 6) Per all.
 * 7) Ridiculous rule. Per all
 * 8) Per proposal.
 * 9) Per all, especially Toadette the Achiever and Gabumon.
 * 10) per
 * 11) I always found this rule very annoying.  Per all.
 * 12) Per all.
 * 13) - Per TT and Edo.

Oppose

 * 1) I think it's better to give the proposer complete control over the proposal, and this rule does just that.
 * 2) - I don't really see a point to remove it. If there's too few votes, it's usually a no quorum anyhow, so rather than just feebly wait, the proposer might just say "forget it" and close it.
 * 3) I don't really see any actual benefit to this it seems like doing something just to do it.
 * 4) Per all.
 * 5) Per all. There just doesn't seem to be a point to removing it. Maybe I want to put a proposal no one cares about out of its misery?
 * 6) When the proposal passes/fails, a month of waiting is needed between proposals (rule #7). That means 6 weeks of total waiting (if rule #10 doesn't apply). If the proposer has a right to withdraw with less than five votes, rule #7 can be skipped, meaning a refreshed proposal can happen within 0-6 weeks. This can allow tweaks and maybe allowing the proposal to be proposed at a better time where more people are active.
 * 7) Per all. It's entirely optional, if you don't like it, don't do it.
 * 8) Per all.
 * 9) - Per all.

Comments
OK, can anyone tell me the difference between talk page proposals and regular proposals? I know that one type specializes in game-related information and that one type specializes in regular wiki-related stuff, but can anyone tell me which is which? I'd really like to know. 02:40, 8 October 2017 (EDT)
 * Talk page proposals go on talk pages and usually only deal with a handful of pages or sometimes even just one page. Regular proposals go on this page and handle a broader amount of pages or other details that would directly affect policy. 11:56, 8 October 2017 (EDT)

@Lcross: Can you elaborate on what you mean by "complete control"? Would you allow a proposer to make major changes to their proposal the day that it ends? 11:56, 8 October 2017 (EDT)

@Camwood: Is there a point in keeping it around, then? And keep in mind that a proposal only needs four votes total to go into effect; in theory, a proposer could easily cancel a proposal simply because they don't like that a majority of users are voting for something that they don't want. That really doesn't seem fair to me. 12:01, 8 October 2017 (EDT)
 * Usually, by the point they could cancel a proposal simply because people don't vote for something they want/people vote for something they don't want, they wouldn't be able to cancel the proposal by this since the consensus would be above that they could cancel the vote by. And if it were lower, there would still be a no quorum. Really, either way, not allowing this does nothing, and removing this just helps delay votes that have a pretty inevitable no quorum. And before you bring up the "isn't 4 possibly enough votes to pass but they can still cancel?", don't worry. However, I think that's an entire other debacle that I think would be more appropriately addressed in another vote after this one, if this vote to remove rule 4 fails and any purpose in doing so isn't rendered moot by rule 4 simply not existing.  ~Camwood777  (talk)  15:19, 10 October 2017 (EDT)
 * A proposal with 3 votes on one side and 4 votes on the other side would be subject to this rule, and that seems like an adequate amount of votes to reach a legitimate consensus. The rule's especially problematic with proposals that have multiple options, since that naturally thins out the number of votes. Also, who are you to say that a consensus is inevitable? New information can come in at any moment, which could easily lead to new votes or people switching their votes. At the very least, if the information comes in too late, the proposer can ask the admins to cancel it and they have a perfectly valid reason to do so. Cancelling proposals early just because you feel like it only stifles productive debate. In short, keeping this rule could easily cause more harm than good. 23:12, 10 October 2017 (EDT)

@TimeTurner: Thanks for the info. It was really helpful. As for "complete control", I'm saying that the proposer should be able to decide if he/she wants to remove it, and removing rule 4 would restrict them from doing that. If they realized immediately that the said action was done for a reason and that the proposal would go against the action, then they should remove the proposal. If you still don't understand, then do you remember my proposal about merging the Hot Monster article with the Red Monster article that completely failed? I thought they were the same thing, but I immediately learned they weren't. I decided to keep the proposal anyway, because I just wanted to see how it would turn out in the end. 16:09, 8 October 2017 (EDT)
 * There's already a rule that allows you to cancel your proposal without a reason early on, especially with this recently passed proposal. If you learn "immediately" that your proposed change wasn't a good idea, then you're free to cancel it. 00:35, 9 October 2017 (EDT)

@Chester: The danger is that this rule could be used to cancel a proposal solely because the proposer doesn't like the outcome, and not because they had any sort of legitimate reason. If they did, they can inform an admin and close it that way. This is not the kind of power that needs to be given to proposers. Besides, spring cleaning is always good; why bog down the list with a pointless rule? 00:35, 9 October 2017 (EDT)

@Doc: What gives you the right to decide that nobody cares about your proposal? I'll reiterate that it only takes more than three votes for a proposal to pass, making it possible for you to cancel a proposal even if people are participating in it, but regardless, if nobody participates in your proposal and it ends in a no quorum, then the logical reason for that is because the proposed issue was too complex and wide-reaching or the proposal itself was confusing, and that's valuable information in and of itself. Besides, it's entirely possible to people to join in with new information at any point, and that could easily get the ball rolling. I'll also reiterate that it's possible for admins to close a proposal early if there's a valid reason for it; what are you doing, cancelling a proposal without a valid reason? 09:20, 10 October 2017 (EDT)
 * The fact that it's been utterly ignored for 8-10 days? Doc von Schmeltwick (talk) 00:43, 20 October 2017 (EDT)

@Wildgoosespeeder: One, that rule doesn't apply to no quorum proposals, and two, the rule exists for a reason. What's the point of rule 7 if it's so easily circumvented? 00:32, 11 October 2017 (EDT)
 * No quorum proposals is 3 or less votes total (rule #8), or if the three extensions on top of the one/two weeks and no margin of three was reached by the end (rule #11). I think rule #7 was for protections involving very active participation, not for any proposal, even proposals with little voting activity. -- 16:13, 11 October 2017 (EDT)

@Chat Man: You called the rule optional. Rules are not something you can pick and choose from to follow. They are what you must try to follow as best as you can. I say that because we are all human. Sometimes we can't follow the rules. But in no wise it is optional. And if you don't like the rule, then why did you oppose? And you're perring other votes which have things you should read as well. Also, I am just trying to cover all points, but I will let you decide to change it or keep it the same. 21:54, 15 October 2017 (EDT)

Make "Bestiary" its own namespace
Sure, we have a namespace for galleries, but I don't see why we can't do the same for bestiaries. It's the same kind of "special" article that I would define galleries as as well. Therefore, I propose that we rename every instance of  to.

Proposer: Deadline: October 26, 2017, 23:59 GMT Extended to November 2, 2017, 23:59 GMT

Support

 * 1) Per proposal.
 * 2) Per proposal.
 * 3) Per proposal.
 * 4) Per proposal.  Why not?
 * 5) This is (similar to?) one of the things Zeldawiki does that I think we should too.
 * 6) Per all.
 * 7) Per all.
 * 8) Switch sides again, Per Toadette's comment.
 * 9) - Just because we've got fewer bestiaries than galleries doesn't really give much an excuse. This helps keep the wiki more organized than it would be, and that's more than a good enough reason IMO.

Oppose

 * 1) - For galleries it made sense because most major articles had one (there are currently 319); for bestiaries, I don't see the point at all. There are 12 proper bestiaries, I don't think this warrants a namespace by any means.
 * 2) Per Tucayo. I also don't see the benefit of this; it seems like more hassle then it's worth for little payoff when considering the few bestiaries on the page.
 * 3) Per Tucayo.
 * 4) - Originally supported, but considering the number of bestiaries there are, per Tucayo.
 * 5) I don't think we have enough pages of this thing to make it into a separate namespace. Per all.
 * 6) Per my comment below and Tucayo.
 * 7) Per all. I see what's trying to be done here, but it seems overly fiddly considering what is being effected, making this extra work for little reward.
 * 8) Per all.
 * 9) Really?! Per all.

Comments

 * I might just be a bit dumb, but I don't fully understand what this means or what the difference is. Could you give an example?-- 12:15, 20 October 2017 (EDT)
 * For example, Mario & Luigi: Superstar Saga bestiary would become if this were to pass. -- 12:18, 20 October 2017 (EDT)
 * I can only see one problem with this. On every enemy page where the enemy template is placed, transcluding its info from the bestiary page, they look like this:
 * The bolded part is where we're going to get into some issues. It'll be a simple fix, but we'd have to change the link for EVERY page with an enemy template.-- 12:54, 20 October 2017 (EDT)
 * Sounds like bot work. 12:56, 20 October 2017 (EDT)
 * The bolded part is where we're going to get into some issues. It'll be a simple fix, but we'd have to change the link for EVERY page with an enemy template.-- 12:54, 20 October 2017 (EDT)
 * Sounds like bot work. 12:56, 20 October 2017 (EDT)


 * Could we keep the current names as redirects until all of the transclusions are fixed?
 * 14:05, 20 October 2017 (EDT)
 * @Ultimate Mr. L: Isn't that a standard measure? @Alex95: That was my exact plan for fixing those pages. 17:37, 20 October 2017 (EDT)

@Tucayo: "There's too little" is not an argument in and of itself. It's so that normal readers don't get confused into thinking it's an actual article. 18:00, 23 October 2017 (EDT)
 * They are articles, though?? What makes them any different from quote pages, lists of badges, recipes, assist trophies, etc.? Bold + italics doesn't make it true. -- 22:01, 23 October 2017 (EDT)
 * Those are actual list articles. Bestiaries are not technically list articles; they are rather pages that are there to have individual sections be transcluded onto actual articles. 22:07, 23 October 2017 (EDT)
 * But they are still articles by themselves. I truly fail to see the point here. -- 22:09, 23 October 2017 (EDT)
 * Again, why do you think that they're actual articles? They are not meant to be. 08:25, 24 October 2017 (EDT)

If we gonna have them as separate namespaces I honestly think the category should expand to all list articles since they are the very similar to bestiaries. I honestly think having a separate namespace for just 12 pages for something very specific is inconsistent and unprofessional.
 * @NSY: Again, bestiaries ARE NOT technically list articles; they are relevant sections of a page transcluded onto other articles, and having too few does not make too much of a difference. Also, could you please elaborate on the "inconsistency" argument? I understand it less so than Tucayo's arguments. 15:10, 24 October 2017 (EDT)
 * Well according to dictionary.com a list is defined as "a series of names or other items written or printed together in a meaningful grouping or sequence so as to constitute a record". Pretty certain an article that has a record of every enemy and their stats falls under that. It's inconsistent because these would the only list articles that got their own namespace, what about the articles listing all the mini games in a Mario Party game, would they also get their own namespace.
 * No, because that's an actual list:
 * Balloon Burst
 * Bombs Away
 * Crazy Cutter
 * Where as the bestiaries are tables:
 * {| class="wikitable"

! Name !! Location !! HP !! Items
 * Bowser || Castle || 100 || Key
 * Goomba || Plains || 3 || Mushroom
 * Koopa Troopa || Mountains || 12 ||N/A
 * }
 * We don't list out the enemies on a bestiary like we do for every single list on this site. The lists are spilt up into categories, like the Species list, and they only have a name that links to it's main article, ONLY. Nothing else about that link exists on the page.-- 17:32, 26 October 2017 (EDT)
 * However, there are some "list" articles such as List of enemy formations in Paper Mario that are tables, so the lists are not always simply just a name that links to its main article. I agree that bestiaries are like list articles. -- 17:36, 26 October 2017 (EDT)
 * Didn't know that existed. Is that article necessary? If so, seems like that should be integrated into the Paper Mario bestiary.-- 17:40, 26 October 2017 (EDT)
 * I feel that there is enough information for it to remain separate (a proposal to merge it could be created though). Even if that and the Thousand-Year Door version were merged with their bestiaries, there are still other list articles that are more than just simply names (see Category:Lists for more examples). -- 17:55, 26 October 2017 (EDT)
 * There is also List of Sammer Guys. The only reason why it is kept separate from Super Paper Mario bestiary is that it is a list of Sammer Guys fought in an optional thing (though the first 20 are required) and they are too similar to each other. As for another this bestiaries are, they are compendiums which is "a collection of concise but detailed information about a particular subject, especially in a book or other publication (not really relevant to these bestiaries, but I am quoting this word for word)" -- definition found by searching compendiums on Bing. The list of enemy formations and others listed here may be the only exceptions, though.
 * Didn't know that existed. Is that article necessary? If so, seems like that should be integrated into the Paper Mario bestiary.-- 17:40, 26 October 2017 (EDT)
 * I feel that there is enough information for it to remain separate (a proposal to merge it could be created though). Even if that and the Thousand-Year Door version were merged with their bestiaries, there are still other list articles that are more than just simply names (see Category:Lists for more examples). -- 17:55, 26 October 2017 (EDT)
 * There is also List of Sammer Guys. The only reason why it is kept separate from Super Paper Mario bestiary is that it is a list of Sammer Guys fought in an optional thing (though the first 20 are required) and they are too similar to each other. As for another this bestiaries are, they are compendiums which is "a collection of concise but detailed information about a particular subject, especially in a book or other publication (not really relevant to these bestiaries, but I am quoting this word for word)" -- definition found by searching compendiums on Bing. The list of enemy formations and others listed here may be the only exceptions, though.

Okay, this just doesn't make any sense at all. How and why in the world would we make this thing its own namespace if there are only twelve of it on the market right now? I don't get it. 17:49, 27 October 2017 (EDT)
 * Because it's not really an article. Its main purpose is infoboxes to transclude onto articles. Because it is more than just an article, I feel it warrants its own namespace. It doesn't matter how few of them there are.
 * 19:48, 28 October 2017 (EDT)
 * But why does it need a separate namespace to exemplify that fact? 20:00, 28 October 2017 (EDT)

Make a new, separate "delete" template for pages with unique talk pages
As it stands, our current delete template urges for the talk page to be deleted as well, presumably assuming that it's from a move redirect. However, in the case of merges or outright page deletions, this is a bad thing, as it could cause the loss of why those events occurred in the first place. I propose we make a new, separate one for such eventualities. "deletenottalk" perhaps? I'm not sure if this belongs in "changes" or "new features," so I'm putting it here.

Proposer: Deadline: October 29, 2017, 23:59 GMT

Support

 * 1) Per proposal.
 * 2) Good idea doc.

Oppose

 * 1) I would love to see a mock-up before I even consider supporting this.
 * 2) Per Wildgoose and Mr. L in the comments.
 * 3) - Per all.
 * 4) Per Ultimate Mr. L in the comments.
 * 5) Per Wildgoosespeeder in the voting section, and Ultimate Mr. L in the comments.
 * 6) Per myself down there.
 * 7) Per the Green Thunder, and per all.

Comments
I think we should add an option to the current template that removes that text, something like:  It may also be a good plan to delete that text altogether and just let the admins decide whether or not to delete the talk page. They know what they're doing. 14:42, 22 October 2017 (EDT)


 * This is exactly what I was thinking. 22:13, 22 October 2017 (EDT)

@Time Turner: Guess what? I don't know how to make templates, so I can't make an example! But it would be like the current one, but replacing the "Please delete any accompanying talk pages as well" with "please do not delete the accompanying talk page. And @Ultimate Mr. L, the solution is not "Make your current template convoluted." Doc von Schmeltwick (talk) 01:34, 23 October 2017 (EDT)
 * @Doc von Schmeltick: Yes it is. That's why one user merged with . (Well, you have to admit, it is a similar scenario.)  02:05, 23 October 2017 (EDT)
 * And it has confounded me multiple times, because it doesn't come with a use manual easy at hand, and I have to search for and hopefully find it within the nightmare that is our "templates" category for any direction at all. Doc von Schmeltwick (talk) 02:54, 23 October 2017 (EDT)
 * If you don't know how to make a template, ask someone to help you. I don't think it's unreasonable to ask to see a mock-up of a new template. Also, I'm perring other people, why are you singling 'me out? 07:21, 23 October 2017 (EDT)
 * Because I was half asleep (and quite frankly you're normally the one who gives me the most resistance it seems, so it's almost reflexive). I meant to @WildGooseSpeeder. Doc von Schmeltwick (talk) 07:28, 23 October 2017 (EDT)
 * You've used the excuse that you're tired on several other occasions. If your level of tiredness affects your editing to the point where your comments can be confused, don't edit when you're tired. 07:45, 23 October 2017 (EDT)
 * I needed to answer the question though. And I re-read it several times. The problem was I had skimmed over the list while somewhat tired, so my backup checks didn't work. Doc von Schmeltwick (talk) 08:02, 23 October 2017 (EDT)
 * There was not an immediate need for you to respond to the opposition votes. Proposals last for a week; you have plenty of time to come back when you're not tired. I'm also going to caution you to actually do that, considering the number of tiredness-based hiccups you've had. 08:07, 23 October 2017 (EDT)

Maybe we could change the outline color to green for quick differentiation. Doc von Schmeltwick (talk) 14:20, 23 October 2017 (EDT)

Want to add that deleting talk pages with content is already optional, as per Deletion policy. The sysops don't usually delete talk pages if the content there is relevant already, such as a proposal determining the deletion of its main page. The talk page is kept, due to the proposal, but the main page is deleted. However, I will agree to a rewording, such as "Unless there is content that shouldn't be deleted on the talk page, please delete the corresponding talk page as well." 21:13, 25 October 2017 (EDT)
 * I got worried on that front after Talk:School of Fish got deleted...admittedly, it was subsequently restored, but still, if the only reason why the corresponding talk page would be deleted would be for moving pages, why have the template say that at all? Doc von Schmeltwick (talk) 21:26, 25 October 2017 (EDT)

Move "Rewrite-expand" to "Incomplete"
I propose we should rename for such eventualities. "" perhaps? I'm not sure if this belongs in "changes" or "new features," so I'm putting it here.

Perhaps this template should say:  This is incomplete. You can help by rewriting and expanding it

Proposer: (blocked) Deadline: October 31, 2017, 23:50 GMT

Oppose

 * 1) - That's just the text for .  is sort of a mix between stub and, the information needs to be rewritten, but also needs to be expanded. Saves having more than one template in a single section.
 * 2) Curse you, edit conflicts! Anyway... I really don't see any benefit to this.  doesn't necessarily mean that the article is unfinished; more often, means that it doesn't go into enough detail. All this is doing is using more words and being more specific than the template should be. Per Alex95.
 * 3) Per Alex95.
 * 4) While I'd consider proposing the making of a new "To do" template like what TCRF has, we don't need to change the name of this one, particularly when what it says doesn't really appear to be any different.
 * 5) Per Alex.
 * 6) The  template is actually specific about how to fix the article other than filling in a bunch of nonsense or just stuff. Per all.
 * 7) I thought this would get mass opposition. Anyway... Per all.
 * 8) WHY?! we have the under construction template, so this will be confusing.

Comments
@Woodchuck You forgot to Support your own proposal. 20:03, 24 October 2017 (EDT)

Wow, you literally copied the last sentence of my proposal above. Just noting that.... Doc von Schmeltwick (talk) 20:08, 24 October 2017 (EDT)

Hey, hello, did you forget to support your own proposal or are you just doing that on purpose? Please don't take offense if you find this annoying, this is just a simple reminder, because I thought you forgot about it. 21:19, 24 October 2017 (EDT)

Decide if Nintendo Badge Arcade constitutes a guest appearance
Following Coverage, a proposal must be formed before an article can be created for a guest appearance. Nintendo Badge Arcade already has a page, but better late than never, right? Besides adhering to policy, it's important to decide on this game's coverage status for another reason: the Arcade Bunny. With every guest appearance on the wiki (SSX on Tour, Captain Rainbow, Minecraft, etc.), only the game itself receives a page, while everything of note is merely inserted onto the page. However, Arcade Bunny flies in the face of that, receiving an individual page even though it hasn't made any substantial appearances within the Mario franchise itself (and no, Costume Mario doesn't count, unless you want to have pages about Nisekoi characters and Babymetal due to what is nothing more than a reskin). The page itself doesn't have anything particularly novel, either, and it could easily be inserted into the game's page. If Nintendo Badge Arcade is considered a guest appearance, then the Arcade Bunny page is deleted and all is resolved. The game is definitely a guest appearance and not a crossover, by the way: though numerous Mario sections appear, they are 100% superficial, contributing nothing of value to the game itself, no more than the furniture in the Animal Crossing games. You could have cut-outs of Danny DeVito's head instead of Mario and nothing would be different. There's just enough Mario stuff to warrant the game's coverage on the wiki, but at the same time, there isn't enough to call it a crossover.

Let's nip this one in the bud and clean up the conundrums.

Proposer: Deadline: November 4, 2017, 23:59 GMT

Support

 * 1) Per proposal.
 * 2) - Per proposal and comments below.
 * 3) Per all. In all honesty, I don't know. I think this page has something worth classifying it as more than a guest appearance, but seeing as how the Arcade Bunny gets a page even though he has almost nothing to do with the Mario franchise, I think this is the logical option.
 * 4) Per proposal.

Comments
@Lcrossmk8: The "status quo" directly goes against policy and was instated without anything official. We are deciding the status quo now. 22:51, 27 October 2017 (EDT)
 * I am guessing that "support" means it should be constituted as a guest appearance and that "oppose" means it should not be constituted as a guest appearance. Feel free to correct me if I am wrong. And anyway, why did nobody take a look at this before? I'm thinking we should just delete the Arcade Bunny article and not constitute Nintendo Badge Arcade as a guest appearance. 22:56, 27 October 2017 (EDT)
 * If Nintendo Badge Arcade isn't a guest appearance, what is it? 22:59, 27 October 2017 (EDT)

Thing is that several different Mario games appear in this. How would we go about listing that? 23:01, 27 October 2017 (EDT)
 * What are you referring to? Everything that's related to Mario is already noted on the game's page. 23:03, 27 October 2017 (EDT)
 * I say that it is a mix between a crossover and a guest appearance. It crosses over multiple games but doesn't really make an impact, or...wait a minute. How in the world does this thing even matter? I don't know. All I know is that something's up with the Arcade Bunny. I don't know why, but he weirdly reminds me of the Energizer rabbit, you know, the one that appears in the commercials. I don't know, but something tells me we should not delete him. 23:05, 27 October 2017 (EDT)
 * what 23:10, 27 October 2017 (EDT)
 * If the Nintendo Badge Arcade article is deleted, would we stick "This game's artwork/sprites/whatever appeared in Nintendo Badge Arcade." in relevant articles? I'll admit the page is excessive, going into detail were it shouldn't really. 23:07, 27 October 2017 (EDT)
 * This proposal is not about deleting the Nintendo Badge Article. It is about whether or not the game is a guest appearance. At most, Arcade Bunny would be deleted. 23:10, 27 October 2017 (EDT)
 * Ah, I see. Yeah, this and Arcade Bunny can go more in depth on the Nintendo Wiki. 23:13, 27 October 2017 (EDT)

@Lcrossmk8: I do not believe you can vote for multiple options if the proposal does not have more than two options. -- 08:34, 28 October 2017 (EDT)