MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
Line 33: Line 33:
#{{User|Demonic KB}} I'm no expert on coding, but if this is an issue, I'll support
#{{User|Demonic KB}} I'm no expert on coding, but if this is an issue, I'll support
#{{User|Walkazo}} - Sounds good. And if it doesn't work after all, it can always be removed.
#{{User|Walkazo}} - Sounds good. And if it doesn't work after all, it can always be removed.
#{{User|Yoshi K}} This seems good, and it seems like an issue that need to be fixed, Per all.


====Oppose====
====Oppose====

Revision as of 14:12, February 17, 2014

Image used as a banner for the Proposals page
Current time:
Thursday, January 2nd, 23:44 GMT
Proposals can be new features, the removal of previously-added features that have tired out, or new policies that must be approved via consensus before any action is taken.
  • Voting periods last for two weeks, but can close early or be extended (see below).
  • Any autoconfirmed user can support or oppose, but must have a strong reason for doing so.
  • All proposals must be approved by a majority of voters, including proposals with more than two options.
  • For past proposals, see the proposal archive and the talk page proposal archive.

If you would like to get feedback on an idea before formally proposing it here, you may do so on the proposals talk. For talk page proposals, you can discuss the changes on the talk page itself before creating the TPP there.

How to

If someone has 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 other users, who will then vote on whether or not they think the idea should be implemented. Proposals should include links to all relevant pages and writing guidelines. Proposals must include a link to the draft page. Any pages that would be largely affected by the proposal should be marked with {{proposal notice}}.

Rules

  1. Only autoconfirmed users may create or vote on proposals. Anyone is free to comment on proposals (provided that the page's protection level allows them to edit).
  2. Proposals conclude at the end of the day (23:59) two weeks after voting starts (all times GMT).
    • For example, if a proposal is added at any time on Monday, August 1, 2011, the voting starts immediately and the deadline is two weeks later on Monday, August 15, at 23:59 GMT.
  3. Users may vote for more than one option, but they may not vote for every option available.
  4. Every vote should have a strong, sensible reason accompanying it. Agreeing with a previously mentioned reason given by another user is acceptable (including "per" votes), but tangential comments, heavy sarcasm, and other misleading or irrelevant quips are just as invalid as providing no reason at all.
  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. Voters can remove or rewrite their own vote(s) at any time, but the final decision to remove another user's vote lies solely with the wiki staff.
    • Users can also use the comments section to bring up any concerns or mistakes in regards to the proposal itself. In such cases, it's important the proposer addresses any concerns raised as soon as possible. Even if the supporting side might be winning by a wide margin, that should be no reason for such questions to be left unanswered. They may point out any missing details that might have been overlooked by the proposer, so it's a good idea as the proposer to check them frequently to achieve the most accurate outcome possible.
  6. 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 "(blocked)" 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.
  7. Proposals cannot contradict an already ongoing proposal or overturn the decision of a previous proposal that concluded less than four weeks (28 days) ago.
  8. If one week before a proposal's initial deadline, the first place option is ahead of the second place option by eight or more votes and the first place option has at least 80% approval, then the proposal concludes early. Wiki staff may tag a proposal with "Do not close early" at any time to prevent an early close, if needed.
    • Tag the proposal with {{early notice}} if it is on track for an early close. Use {{proposal check|early=yes}} to perform the check.
  9. Any proposal where none of the options have at least four votes will be extended for another week. If after three extensions, no options have at least four votes, the proposal will be listed as "NO QUORUM." The original proposer then has the option to relist said proposal to generate more discussion.
  10. If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
  11. If a proposal reaches its deadline and the first place option is ahead of the second place option by three or more votes, then the first place option must have over 50% approval to win. If the margin is only one or two votes, then the first place option must have at least 60% approval to win. If the required approval threshold is not met, then the proposal is extended for another week.
    • Use {{proposal check}} to automate this calculation; see the template page for usage instructions and examples.
  12. Proposals can be extended a maximum of three times. If a consensus has not been reached by the fourth deadline, then the proposal fails and cannot be re-proposed until at least four weeks after the last deadline.
  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. After a proposal passes, it is added to the appropriate list of "unimplemented proposals" below and is removed once it has been sufficiently implemented.
  15. If the wiki staff deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to cancel it at any time.
  16. Proposals can only be rewritten or canceled by their proposer within the first four days of their creation. However, proposers can request that their proposal be canceled by a staff member at any time, provided they have a valid reason for it. Please note that canceled proposals must also be archived.
  17. Unless there is major disagreement about whether certain content should be included, there should not be proposals about creating, expanding, rewriting, or otherwise fixing up pages. To organize efforts about improving articles on neglected or completely missing subjects, try setting up a collaboration thread on the forums.
  18. Proposals cannot be made about promotions and demotions. Staff changes are discussed internally and handled by the bureaucrats.
  19. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
  20. Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.

Basic proposal formatting

Below is an example of what your proposal must look like. If you are unsure how to set up this format, simply copy the following and paste it into the fitting section. When updating the bracketed variables with actual information, be sure to replace the whole variable including the square brackets, so "[insert info here]" becomes "This is the inserted information" and not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but the objective(s) of each voting option must be clearly defined. Such options should also be kept to a minimum, and if something comes up in the comments, the proposal can be amended as necessary. 

===[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''': {{User|{{subst:REVISIONUSER}}}}<br>
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

====[option title (e.g. Support, Option 1)]: [brief summary of option]====
#{{User|{{subst:REVISIONUSER}}}} [make a statement indicating that you support your proposal]

====[option title (e.g. Oppose, Option 2)]: [brief summary of option]====

====Comments ([brief proposal title])====

Autoconfirmed users will now be able to vote on your proposal. Remember that you can vote on your own proposal just like the others.

To vote for an option, just insert #{{User|[your username here]}} 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 simply say "Per proposal".

Talk page proposals

Proposals concerning a single page or a limited group of pages are held on the most relevant talk page regarding the matter. All of the above proposal rules also apply to talk page proposals. Place {{TPP}} under the section's header, and once the proposal is over, replace the template with {{settled TPP}}. Proposals dealing with a large amount of splits, merges, or deletions across the wiki should still be held on this page.

All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{TPP discuss}}. Include a brief description of the proposal while also mentioning any pages affected by it, a link to the talk page housing the discussion, and the deadline. If the proposal involves a page that is not yet made, use {{fake link}} to communicate its title in the description. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links.

List of ongoing talk page proposals

Unimplemented proposals

Proposals

Break alphabetical order in enemy lists to list enemy variants below their base form, EvieMaybe (ended May 21, 2024)
Standardize sectioning for Super Mario series game articles, Nintendo101 (ended July 3, 2024)
^ NOTE: Not yet integrated for the Super Mario Maker titles, Super Mario Run, and Super Mario Bros. Wonder.
Create new sections for gallery pages to cover "unused/pre-release/prototype/etc." graphics separate from the ones that appear in the finalized games, Doc von Schmeltwick (ended September 2, 2024)
Add film and television ratings to Template:Ratings, TheUndescribableGhost (ended October 1, 2024)
Use the classic and classic link templates when discussing classic courses in Mario Kart Tour, YoYo (ended October 2, 2024)
Clarify coverage of the Super Smash Bros. series, Doc von Schmeltwick (ended October 17, 2024)
Remove all subpage and redirect links from all navigational templates, JanMisali (ended October 31, 2024)
Prioritize MESEN/NEStopia palette for NES sprites and screenshots, Doc von Schmeltwick (ended November 3, 2024)
Stop considering reused voice clips as references (usually), Waluigi Time (ended November 8, 2024)
Allow English names from closed captions, Koopa con Carne (ended November 12, 2024)
^ NOTE: A number of names coming from closed captions are listed here.
Split off the Mario Kart Tour template(s), MightyMario (ended November 24, 2024)
Split major RPG appearances of recurring locations, EvieMaybe (ended December 16, 2024)
Stop integrating templates under the names of planets and areas in the Super Mario Galaxy games, Nintendo101 (ended December 25, 2024)

Talk page proposals

Split all the clothing, Doc von Schmeltwick (ended September 12, 2021)
Split machine parts, Robo-Rabbit, and flag from Super Duel Mode, Doc von Schmeltwick (ended September 30, 2022)
Make bestiary list pages for the Minion Quest and Bowser Jr.'s Journey modes, Doc von Schmeltwick (ended January 11, 2024)
Allow separate articles for Diddy Kong Pilot (2003)'s subjects, Doc von Schmeltwick (ended August 3, 2024)
Create articles for specified special buildings in Super Mario Run, Salmancer (ended November 15, 2024)
Expand and rename List of characters by game to List of characters by first appearance, Hewer (ended November 20, 2024)
Merge False Character and Fighting Polygon/Wireframe/Alloy/Mii Teams into List of Super Smash Bros. series bosses, Doc von Schmeltwick (ended December 2, 2024)
Make changes to List of Smash Taunt characters, Hewer (ended December 27, 2024)
Merge Candy Block with Hard Block, Nintendo101 (ended December 31, 2024)
Merge ON/OFF Conveyor Belt with Conveyor Belt, PopitTart (ended January 1, 2025)

List of Talk Page Proposals

Writing Guidelines

None at the moment.

New features

Create the Category:Files with broken Aboutfile template

Most new users break the Aboutfile template, The worst thing about it, that it cannot be easily detected. I propose the following code to be added to the template. Each line of the following add the category "Category:Files with broken Aboutfile template" (to be created) to the File page if the respective variable has the default value. (i.e, the variable {{{1}}} has a value of "Subject of the image"). 

{{#ifeq: {{{1}}}|Subject of the image|[[Category:Files with broken Aboutfile template]]}}
{{#ifeq: {{{2}}}|Where you found the image|[[Category:Files with Broken Aboutfile template]]}}
{{#ifeq: {{{3}}}|Artist|[[Category:Files with Broken Aboutfile template]]}}
{{#ifeq: {{{4}}}|Describe edits, if any|[[Category:Files with Broken Aboutfile template]]}}
{{#ifeq: {{{5}}}|Other versions (use file link)|[[Category:Files with Broken Aboutfile template]]}}

adding this in the template coding will activate it (may need a cache reset for files pages with already broken Aboutfile), so any page having a misformatted aboutfile template will be automatically added to the category, therefore making it easier to maintenance.

Proposer: Dashbot (talk)
Deadline: February 21, 2014, 23:59 GMT

Support

  1. Dashbot (talk) This issue has been annoying me forever, it has to go.
  2. Demonic KB (talk) I'm no expert on coding, but if this is an issue, I'll support
  3. Walkazo (talk) - Sounds good. And if it doesn't work after all, it can always be removed.
  4. Yoshi K (talk) This seems good, and it seems like an issue that need to be fixed, Per all.

Oppose

  1. Iggy Koopa Jr (talk) I oppose, because I don't like the aboutfile template. I always remove the whole thing.

Comments

I'm not an expert on coding, but wouldn't this code require that all five sections be filled with something? Time Turner (talk)

Nope, any section filled with it's default value will add the category. Dashbot (talk)

What if users simply format it incorrectly, as with any other template? Mario (talk)

If a user formatted the {{aboutfile}} incorrectly, the category is added to the file page automatically. Dashbot (talk)
Could you demonstrate what an incorrect formatting of the template would look like? Time Turner (talk)
Dis Dashbot (talk)
So... all your code does is check to see if someone didn't fill a section in. So, if someone were to simply blank all the sections, would there be any problems? Time Turner (talk)

@Iggy, last I recall, the aboutfile template is kinda necessary for image files on this wiki, so... Lord Grammaticus (talk)

@Time Turner, first if someone blanked a section, it would disappear. Second, no one blank all the sections, they just leave it as-it. And this proposed feature fixes the "as-it" problem. Dashbot (talk) 11:51, 17 February 2014 (EST)

@Iggy Koopa Jr., no offenses, but what does any of that do with the proposed feature? You are just saying that you do not use the template. This fixes a issue (i.e [1] , [2] , [3] , [4] , [5], and even more) by adding the file page to a specified category. Just like any maintenance category. Simply saying that you do not use it, doesn't mean it isn't necessary. Please check your vote, it is lacking a reasonable reason. Dashbot (talk) 11:51, 17 February 2014 (EST)

Again, this proposed feature aims to help fixing the issue, exactly like the Category:Articles with broken file links.Dashbot (talk) 11:51, 17 February 2014 (EST)

Removals

None at the moment.

Changes

Merge articles such as Orbs and Hexes into lists with the same information

Most notably, I've seen large amounts of very small pages about things such as orbs and hexes. I think it would be more useful to merge these pages together into one large, easy to read list, as opposed to having tons of smaller pages. I believe that this will create consistency and simplicity for those who wish to view an entire page of all the orbs/hexes, and their effects, as well as compare them depending on the game. The orb list would be found on the orb page, and the hex list would be found under the hex page, etc. I think it'll be less daunting and time consuming as well.

I propose the following format, though I'm open to adjustments. Please keep in mind that this is only the prototype format, and if someone would like to suggest changes, I'd love to hear them:

Picture of Orb/Hex Name(s) of Orb/Hex Game(s) Item appear(s) in Ability/Effect Cost (if available) Other information

Making separate lists for the separate Mario Party orbs/hexes under one page is also plausible. (Different pages for orbs and hexes, in case that wasn't clear.)

Now, while I've only mentioned these two things, if there's something you'd like to see merged as well, please add it in the comments section.

Proposer: Coooool123 (talk)
Deadline: February 17, 2014, 23:59 GMT

Support

  1. Coooool123 (talk) Per proposal
  2. Demonic KB (talk) That sounds like a good idea

Oppose

  1. Time Turner (talk) Doing this would be far from consistent, will be trimming far too much information, especially when considering that a lot of the orbs require extra explanations for their uses, and really, most of the orbs/hexes don't even have small articles, unless you wanna compare them to Bowser or something. Also, these are items. They have unique descriptions, and unique appearances, and unique uses, and everything that's needed for them to be considered items. What, exactly would be consistent about merging all of the orbs and not, say, all of the RPG items? Bottom line is, nothing good will come of this.
  2. SuperYoshiBros (talk) Per Time Turner.
  3. Pinkie Pie (talk) Dr. Whooves got it. Per all.
  4. Walkazo (talk) - Per Time Turner: this would be inconsistent and/or lead to more merges, but the philosophy these days is that more little pages are better than a few big lists (such as for search traffic and whatnot). Plus, lists with too much info aren't necessarily easy to use, and can be particularly troublesome for narrow screens.
  5. Randombob-omb4761 (talk) The orbs and hexes are from completeley different games.
  6. Baby Luigi (talk) I prefer if we have a little bit of both: for example, the GCN Mario Party articles list the orbs and whatnot into a list and has a short blurb of them. If you want full information on them, well, that's what the articles are for. These orbs also can work differently in each game: ie the Goomba Capsule in Mario Party 5 switches coins while the Goomba Orb in Mario Party 6 makes the victim give coins to the person who set the orb down. It's more convenient this way, and I think it works better.
  7. Marshal Dan Troop (talk) Per TT lord of time.
  8. Mario4Ever (talk) Per Time Turner.
  9. ParaLemmy1234 (talk) Per all.
  10. Yoshi K (talk) Per Time Turner, I don't see why this is necessary.

Comments

@Time Turner - That's not necessarily true. It really depends on the layout of the page. Not to mention, we don't need as much information as we have. I've been told that conciseness is key on this wiki. If I may ask, which articles are you referring to? Most that I see are very short. It's a mess as it is, and more consistent than the method we have now. Coooool123 (talk)

Paper Mario items, for starters. It's inconsistent. We don't merge power shots from Mario Power Tennis nor Captain Abilities from Mario Strikers Charged either. Baby Luigi (talk)
Then don't merge those ones. This isn't about paper Mario items. this is about tons of tiny articles that will suffice under one page. Coooool123 (talk)
That's exactly what's wrong with your proposal: you're proposing something that will break consistency in this wiki. Another great example is Mario Kart Arcade GP items. Merge those too? No. Baby Luigi (talk)
But see, the problem with that, Baby Luigi, is that it's just going to get re-proposed later to delete it. I've seen this before, where people create lists in addition to the regular pages, and they just get deleted awhile later, then re-created. It's a vicious cycle. Whereas if we just have the one list page for orbs, they'll all be together and it'll be easier to go through them. Coooool123 (talk)
I have been here for nearly five years, and I can say that I honestly don't remember anything like that happening, especially in relation to orbs. Could you provide an example of this, preferably with a link? Time Turner (talk)
It's not the orbs. It's the lists that are the problem. People don't like having lists and individual pages. But, lists are easier to go through compared to 50 little pages with not much variation besides effect. Coooool123 (talk)
That doesn't address my question. Time Turner (talk)
Perhaps it would help if you named some of these 'people' in question. Lord Grammaticus (talk)
Here are some examples of what I'm talking about: http://www.mariowiki.com/MarioWiki:Proposals/Archive_13#Merge_or_Delete_Demo_Articles http://www.mariowiki.com/MarioWiki:Proposals/Archive_18#Categories:_List_of_Implied_... http://www.mariowiki.com/MarioWiki:Proposals/Archive_4#Article_about_.22Implied.22_subject_.282nd_nomination..29 http://www.mariowiki.com/MarioWiki:Proposals/Archive_2#Removal:_Glitch_Articles http://www.mariowiki.com/MarioWiki:Proposals/Archive_2#Merging_Wario_Treasures
I just think that it'll cycle in and out of proposals for lists, not technically this in general, and that there will always be proposals about merging items into lists, then separating them, then merging again, then deleting lists, etc. Coooool123 (talk)
The most recent proposal that you linked to was from 2009, and even then, it really doesn't have anything to do with what you're talking about. It wanted to delete a set of categories because they literally served no purpose. The articles mentioned in the proposal talking about demo articles wanted to delete them because they were only tangentially related to the Mario series. I'll give you the other ones, sure, but those are from 2007, which really doesn't illustrate your point that this kind of thing is a constant cycle. Time Turner (talk)
I'm worried that it's going to come to that. Maybe I'm wrong. But I think that people will constantly do this. Coooool123 (talk)
...Even though you've demonstrated that people haven't done this since 2007, 2009 if I'm been generous? Time Turner (talk)
It's true I haven't seen much of it. But that doesn't mean it won't happen. Coooool123 (talk)
That's a fallacious argument. If I say that the wiki will be suddenly shut down in the next five minutes, I can't back it up with "Well, it could happen." That's not even close to actual proof. Time Turner (talk)
I suppose so. Still, I like my list idea, I think it'll be useful and leave less stubs behind, even if they aren't officially stubs. Coooool123 (talk)
Stubs are not short articles. Some stubs are short articles, but not all short articles are stubs. Stubs, by wiki definition, are articles that are lacking information, and that's the only definition that should be used here. If they aren't "officially" stubs, they are not stubs. Time Turner (talk)
I feel like the only reason this whole argument has started in the first place was lack of clarity on my part regarding what I'm proposing. Coooool123 (talk)
Hmm, I've created some of the orb lists in the Mario Party articles, like, since 2010 and it still stands to this day. So what's this deletion you speak of? Baby Luigi (talk)
Delete the orb pages, and merge all of the information under 'Orbs', making a sort of table for them. Coooool123 (talk)
That's where I disagree. Orbs are official, named items and get an article in the wiki. I oppose deleting them at all, and they also vary game from game. Baby Luigi (talk)
And I respect that, but they're so small that it's just more convenient for them to be together. Coooool123 (talk)

@Coooool, I was hoping you'd understand that was a very general statement, as opposed to a standard to enforce on articles (not that I could plausibly do such here anyway). Lord Grammaticus (talk)

Nope. Apparently not. But why shouldn't we be concise under such matters? We don't need all these pages when one will do. Coooool123 (talk)
I think Baby Luigi explained well enough to start. Lord Grammaticus (talk)
I don't agree. It'll just get deleted later. Coooool123 (talk)
The orb/capsule/item lists in the Mario Party articles have been there since nearly 2010 and are not going anywhere any time soon. Baby Luigi (talk)
http://www.mariowiki.com/Category:Orbs_and_Capsules I'm just saying we take this and make it into a page, and delete the useless information. Coooool123 (talk)
Why delete it? What's the point? The category does its job, the orb/capsules/item lists in the respective Mario Party articles do their job. Making a list like that would be redundant. Baby Luigi (talk)
It's only redundant if we keep them both. Coooool123 (talk)

@Randombob-omb4761- Apologies if I wasn't clear. but I said that they would have their own separate lists. I'm not proposing we merge these together. it's 'such as' Orbs and hexes. Both would have their own pages. Coooool123 (talk)

It's a bit too late to salvage this discussion, but please remember to out new comments at the bottom, rather than sticking them in the middle using indents. Without time stamps, it really muddles up the history of the discussion. Just use Name: or "@Name:" or whatever to link to a specific comment if there were other things said in the interim. This also potentially avoids having to indent by over a dozen colons, which is less than ideal. - Walkazo (talk)

Sorry, Walkazo. I'll try to clean this up... Coooool123 (talk)

Miscellaneous

Change the order of the NIWA Main template

Change Template:NIWA Main (which is the last block on the main page) so that it lists the wikis in alphabetical order. This would make it easier to find a certain wiki, it would be more organized, and it would not be "favoring" one wiki.

Old template:

NIWA is a group of open-content encyclopedias based on Nintendo franchises.

Proposed template:

NIWA is a group of open-content encyclopedias based on Nintendo franchises.

Proposer: Mario7 (talk)
Deadline: February 20, 2014, 23:59 GMT.

Support

  1. Mario7 (talk) Per Proposal. It would be a lot easier to navigate.
  2. Demonic KB (talk) I pretty much would say the same thing as above.
  3. YoshiCookie (talk) Per all.
  4. Lord Grammaticus (talk) Per all, it's a small improvement, but substantial nonetheless.
  5. Pinkie Pie (talk) Per all.
  6. Ashley and Red (talk) Looks good. And ABC order is very organizated.
  7. Randombob-omb4761 (talk) ABC order is better than a bunch of random links. This will be easier to navigate.
  8. Iggy Koopa Jr (talk) On other wikis, it's on alphbetical.
  9. Mario (talk) I was wondering if the current order is based on the recency of each alliance, but seeing Hard Drop Tetris Wiki (the latest member) on a random spot makes me want to support this.

Oppose

Comments

Maybe you should ask Steve about this since he mainly manages the template? Baby Luigi (talk)

I just want to see what everyone else thinks first, but thanks! Mario7 (talk) 16:30, 13 February 2014 (EST)

@Pinkie How do you know we don't want an ABC, most templates follow an ABC order on the wiki. Yoshi876 (talk)

At all cases, it is not that major.. just talk to the Minecraft man (a.k.a Porplemontage) and withdraw dis. :) --Megadardery (talk) 08:32, 14 February 2014 (EST)

@Pinkie Why is your vote a "stronger oppose" and what do you mean when you say "we don't want a ABC order on the template anyway?" You are not an admin and you also haven't given a strong reason for why it should stay this way. Simply saying that you don't want it is not a strong argument. Mario7 (talk) 16:32, 14 February 2014 (EST)

Fine, but remember, I have my eye on you. Pinkie Pie (talk)
Not really sure what that means, but OK. Mario7 (talk)
Have to admit, that comment throws me as well... Lord Grammaticus (talk)
Retrieved from "https://www.mariowiki.com/index.php?title=MarioWiki:Proposals&oldid=1628151"