MarioWiki:Proposals

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
Image used as a banner for the Proposals page

Current time:
Tuesday, May 21st, 05:17 GMT

Proposals can be new features (such as an extension), the removal of previously-added features that have tired out, or new policies that must be approved via consensus before any action is taken.
  • "Vote" periods last for one week.
  • Any user can support or oppose, but must have a strong reason for doing so (not, e.g., "I like this idea!").
  • 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.

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 {{User|User name}}.

How to

Rules

  1. If users have an idea about improving the wiki or managing its community, but feel that they need community approval before acting upon that idea, they may make a proposal about it. They must have a strong argument supporting their idea and be willing to discuss it in detail with the other users, who will then vote about whether or not they think the idea should be used. Proposals should include links to all relevant pages and writing 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}}.
  2. Only registered, autoconfirmed users can create, comment in, or vote on proposals and talk page proposals. Users may vote for more than one option, but they may not vote for every option available.
  3. Proposals end at the end of the day (23:59) one week after voting starts, except for writing guidelines and talk page proposals, which run for two weeks (all times GMT).
    • For example, if a proposal is added at any time on Monday, August 1, 2011, the voting starts immediately and the deadline is one week later on Monday, August 8, at 23:59 GMT.
  4. Every vote should have a strong, sensible reason accompanying it. Agreeing with a previously mentioned reason given by another user is accepted (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 at any time, but the final decision to remove another user's vote lies solely with the administrators.
    • 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 "(banned)" is added next to their name in the "Proposer:" line of the proposal, which runs until its deadline as normal. If the proposal passes, it falls to the supporters of the idea to enact any changes in a timely manner.
  7. No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
  8. 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.
  9. All proposals that end up in a tie will be extended for another week. Proposals with more than two options must also be extended another week if any single option does not have a majority support: i.e. more than half of the total number of voters must appear in a single voting option, rather than one option simply having more votes than the other options.
  10. If a proposal with only two voting options has more than ten votes, it can only pass or fail with a margin of at least three votes, otherwise the deadline will be extended for another week as if no majority was reached at all.
  11. Proposals can only be extended up to three times. If a consensus has not been reached by the fourth deadline, the proposal fails and can only be re-proposed after four weeks, at the earliest.
  12. 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.
  13. If the administrators deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to remove it at any time.
  14. Proposals can only be rewritten or deleted by their proposer within the first three days of their creation (six days for talk page proposals). However, proposers can request that their proposal be deleted by an administrator at any time, provided they have a valid reason for it. Please note that canceled proposals must also be archived.
  15. 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.
  16. Proposals cannot be made about promotions and demotions. Users can only be promoted and demoted by the will of the administration.
  17. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
  18. Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.

Basic proposal and support/oppose format

This is an example of what your proposal must look like, if you want it to be acknowledged. If you are inexperienced or unsure how to set up this format, simply copy the following and paste it into the fitting section. Then replace the [subject] - variables with information to customize your proposal, so it says what you wish. If you insert the information, be sure to replace the whole variable including the squared brackets, so "[insert info here]" becomes "This is the inserted information", not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but what each voting section is supporting must be clearly defined. 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|[enter your username here]}}<br>
'''Deadline''': [insert a deadline here, 7 days after the proposal was created (14 for writing guidelines and talk page proposals), at 23:59 GMT, in the format: "May 21, 2024, 23:59 GMT"]

====Support====
#{{User|[enter your username here]}} [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 "#{{User|[add 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 just say "Per my proposal".

Talk page proposals

All proposals dealing with a single article or a specific group of articles are held on the talk page of one of the articles in question. Proposals dealing with massive amounts of splits, merges or deletions across the wiki should still be held on this page.

For a list of all settled talk page proposals, see MarioWiki:Proposals/TPP archive and Category:Settled talk page proposals.

Rules

  1. All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{TPPDiscuss}}. 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. Place {{TPP}} under the section's header, and once the proposal is over, replace the template with {{SettledTPP}}.
  2. All rules for talk page proposals are the same as mainspace proposals (see the "How to" section above), with the exceptions made by Rules 3 and 4 as follows:
  3. Voting in talk page proposals will be open for two weeks, not one (all times GMT).
    • For example, if a proposal is added at any time on Monday, August 1, 2011, it ends two weeks later on Monday, August 15, 2011, at 23:59 GMT.
  4. The talk page proposal must pertain to the article it is posted on.
  5. When a talk page proposal passes, it should be removed from this list and included in the list under the "Unimplemented proposals" section until the proposed changes have been enacted.

List of ongoing talk page proposals

Unimplemented proposals

Proposals

Merge the Wrecking Crew and VS. Wrecking Crew phases into list articles, Axis (ended February 24, 2022)
Do not consider usage of classic recurring themes as references to the game of origin, Swallow (ended March 9, 2022)
Split Mario Kart Tour character variants into list articles, Tails777 (ended May 4, 2022)
Enforce WCAG Level AA standards to mainspace and template content, PanchamBro (ended May 29, 2022)
Change how RPG enemy infoboxes classify role, Doc von Schmeltwick (ended September 18, 2022)
Trim away detailed special move information for all non-Mario fighters, Koopa con Carne (ended January 30, 2023)
Classify the Just Dance series as a guest appearance, Spectrogram (ended April 27, 2023)
Establish a standard for long course listings in articles for characters/enemies/items/etc., Koopa con Carne (ended June 8, 2023)
Consider filenames as sources and create redirects, Axis (ended August 24, 2023)
Add tabbers to race/battle course articles, GuntherBB (ended November 18, 2023)
Remove elemental creatures categories from various Super Mario RPG enemies, Swallow (ended January 11, 2024)
Standardize the formatting of foreign and explanatory words and phrases in "Names in other languages" tables, Annalisa10 (ended February 7, 2024)
Merge Super Mario Bros. (film) subjects with their game counterparts, JanMisali (ended April 18, 2024)
Remove profiles and certain other content related to the Super Mario Bros. Encyclopedia from the wiki, Koopa con Carne (ended April 30, 2024)
Trim Mario Kart course galleries of excess Tour stuff, Shadow2 (ended May 18, 2024)

Talk page proposals

Split all the clothing, Doc von Schmeltwick (ended September 12, 2021)
Split the various reissues of Mario Bros., Doc von Schmeltwick (ended April 22, 2022)
Split machine parts, Robo-Rabbit, and flag from Super Duel Mode, Doc von Schmeltwick (ended September 30, 2022)
Expand source priority exception to include regional English differences, LinkTheLefty (ended January 14, 2023)
Add product IDs in game infoboxes, Windy (ended March 18, 2023)
Remove the list of Super Smash Bros. series objects, Axis (ended May 10, 2023)
Split Special Shot into separate articles by game, Technetium (ended September 30, 2023)
Convert the lists of episode appearances for television series characters into categories, Camwoodstock (ended November 22, 2023)
Change the Super Mario 64 DS level section to include more specific character requirements, Altendo (ended December 20, 2023)
Split the Jungle Buddies from Animal Friends, DrippingYellow (ended December 22, 2023)
Make bestiary list pages for the Minion Quest and Bowser Jr.'s Journey modes, Doc von Schmeltwick (ended January 11, 2024)
Merge the ghost Bats and Mice from Luigi's Mansion to their respective organic counterparts from the later games, Doc von Schmeltwick (ended January 20, 2024)
Split Strobomb from Robomb, Doc von Schmeltwick (ended January 20, 2024)
Split the NES and SNES releases of Wario's Woods, SONIC123CDMANIA+&K(B&ATSA) (ended March 27, 2024)
Merge Mii Brawler, Mii Swordfighter, and Mii Gunner to Mii, TheUndescribableGhost (ended March 28, 2024)
Split Mario's Time Machine (Nintendo Entertainment System), or the Super Nintendo Entertainment version along with both console versions of Mario is Missing!, LinkTheLefty (ended April 11, 2024)
Remove non-Super Mario content from Super Smash Bros. series challenges articles, BMfan08 (ended May 3, 2024)
Merge Stompybot 3000 with Colonel Pluck, DrippingYellow (ended May 4, 2024)
Split "Team Dinosaur" from The Dinosaurs, Blinker (ended May 15, 2024)

List of talk page proposals

Writing guidelines

None at the moment.

New features

Empty sections templates

We have the MarioWiki:Trivia page, and the Template:Trivia page to warn contributors about overly long trivia sections. Since we have the MarioWiki:Empty Section Policy page, I think we should create a Template:Empty page. It would look like something like this:

We would also:

  • add this template in every empty section;
  • create a category to find every empty section in an easy way;
  • add this category in the MarioWiki:Maintenance page.

Proposer: Banon (talk)
Deadline: June 4, 2013, 23:59 GMT

Support

  1. Banon (talk) This is my proposal.
  2. Megadardery (talk) From what I understand, I think it is a good idea.
  3. Yoshi876 (talk) Per proposal.
  4. Baby Luigi (talk) Per proposal, except make the template a different color than the trivia one.
  5. Mr. Game & Watch (talk) Per Baby Luigi.
  6. MegaDigga3 (talk) Per Baby Luigi. I also think that it should be just a tad more descriptive.
  7. ThePremiumYoshi (talk) — Per Baby Luigi and MegaDigga3.
  8. King Pikante (talk) Per all.
  9. GBAToad (talk) Per Banon and Baby Luigi.
  10. ParaLemmy1234 (talk) Per all. A different colour would be better though, like maybe a dark blue or purple.
  11. Mariotime11 (talk) Per proposal.

Oppose

Comments

I agree for your criticisms about the template. Feel free to make your own version of the template! — Banon (talk)

What about this:
Also, I'm not very good at coding so someone should probably look at it... Banon (talk) 09:54, 30 May 2013 (EDT)
It looks too much like the image template. I suggest
Baby Luigi (talk) 18:18, 30 May 2013 (EDT)
That one looks similar to Template:MoreImages. Also, I'm pretty sure you can't use your custom sigs here. Time Turner (talk)
Yeah yeah, I'll change my sig. It's a nasty habit I have. But thanks for notifying me of that. I'll think of another color:
Baby Luigi (talk)
Black... I believe no other template uses that color. That could work, but how about we just give it the same/similar colors to Template:Trivia?
Time Turner (talk)
I agree that it would be best to make it look like {{Trivia}}. This is dealing with the same sorta issue as Trivia (a section of the page needs work because it's not up to current standards), so consistency makes sense. Plus it's not a huge, pressing issue, so brightly coloured templates would be unnecessarily eye-catching; they're also a bit of an eye-sore, and if anything, might make the page look worse than it would with latent empty sections. - Walkazo (talk)
I dunno why, but I like black for referencing something empty. But whatever floats your boat. Baby Luigi (talk)

Hey, why do you absolutely want that this template be different than any other? I think consistency is best. Actually I think every notice or navigation template should be of the same color (maybe it's worth a proposal, I don't know). Banon (talk)

That would cause more confusion than it's worth. Time Turner (talk)
Consistency shouldn't apply to notice templates. It would be pretty confusing to see all templates as a different color. A standard may be all right, but not making them all the same color. Baby Luigi (talk)
I don't get it: you say it's confusing if they're all in a different color, but then you say you don't want them to be all the same color. Banon (talk)
Sorry for the contradictory statement. I meant it would be confusing if it was all in the same color. I don't know how that ended up on the screen. Baby Luigi (talk)

Mostly, all those sections with each other in one page are empty.. I mean probably no one fix a single section without fixing the other. The trouble is: We will need to put the template everywhere on the page.. and one page would have up to 5 of the same templates. I really know this template is Important but before we do anything we have to discuss this problem first. Probably changing the wording (for ex: The following sections are linking to other article are empty. Please add a short description of the main article ) or something like that, and then add the template to the top of all the sections. Here is an example image see here.Megadardery (talk)04:26, 1 June 2013 (EDT)

You're right, but I think we should do it anyway. We can't just add one template if there are five empty sections. IMO we should add the template everywhere, and then a category in the Maintenance page. If we do this, there would probably be a fewer number of templates soon (contributors would most likely write short descriptions and remove the templates). Banon (talk)
We can also change it to "The page contains Empty Sections. Please add a short description of the main article" so only one can be incorporated. Baby Luigi (talk)

Y'know, instead of many templates, or one template, one could always simply add stuff to the empty sections... You're already seeking them out, so why not just fix them as you go instead of adding ugly templates and coming back "later"; at least when the sections are simply empty, random readers won't know that's a bad thing, whereas they'll certainly notice the template(s). I've been mulling it over since the proposal was first made, and I am still failing to see how this is the best way to go about the issue... - Walkazo (talk)

The only problem I have with this is that not everyone knows about the Empty Sections Policy, and putting a hideous template there notifies them about the problem Baby Luigi (talk)
What about this:
Banon (talk)
I agree with you, except that your point is valid for every notice template, as Trivia, Construction, Image, or Image-quality. The only difference would be that it's shorter, but it's still long in the long run. The point of these templates is to seek them out for us and other contributors. — Banon (talk)
I have the same issue with the Trivia template, tbh: just take an extra couple minutes to remove or incorporate some stuff, rather than slapping on a template and hoping someone else does the dirty work. Construction (and Rewrite) is for pages that require a lot of work and will obviously look incomplete in the meantime, so that template makes sense; Image is also a bit more involved, especially if the images need uploading, which not everyone can do anyway, hence the validity of using Image-quality to try to get the attention of someone who can improve the image. However, removing Trivia, adding a sample image gallery, or making a quick blurb about beta elements or glitches or whatever is something that anyone should be able to do in a reasonably short amount of time. As for the draft, the second sentence might be better if it read: "Please add short previews of the separate pages that are linked to by these sections." ("previews" seems more accurate to what we want than "descriptions", afaik). - Walkazo (talk)

Removals

Delete quote sections/articles that don't have any meaningful quotes

Delete quotes articles and sections in the sporting games and Mario Party series, if they are composed of meaningless ones i.e. "Hooray"

These sections/pages are not needed. People do not need to read "Let's-a-go" or "Congratulations" as these are just simple words. The quotes sections should be for character development not "Here I go!". And most of these have been under construction for many years, List of quotes in the Mario Kart series has been under construction since 2008, so people aren't contributing to it. I think these pages are unneeded should therefore be deleted.

Proposer: Yoshi876 (talk)
Deadline: June 3, 2013, 23:59 GMT

Delete pages

  1. Yoshi876 (talk) Per proposal.
  2. MegaDigga3 (talk) Per proposal.
  3. YoshiKong (talk) Per proposal. This has been on the back of my mind for a while.
  4. Tails777 (talk) I look at the list of Mario Kart Quotes and under Mario's section for Mario Kart 64, it lists what he says on the main menu. Him saying "Data" or "Options" don't really count as quotes. In short per all, we don't need quotes of characters saying what mode your in.
  5. King Pikante (talk) Per proposal.
  6. Tucayo (talk) - Per all.
  7. A Paragoomba and the Koopa Bros. (talk) -- Per all, people don't need to reading short and dumb things like "Peach!".

Keep the pages

  1. Baby Luigi (talk) This isn't the right decision. While most of these quotes are inane and pointless, we should delete the inane and pointless quotes instead of deleting the entire page. Believe it or not, some sporting and Mario Party games DO contain meaningful quotes (see: List of quotes in Mario Super Sluggers) and therefore, if this proposal passes, we delete not only the short, pointless ones, but also the ones where the proposal EXPLICITLY STATES that it should support. So it's very contradictory.

Comments

@BabyLuigi I see your point, and that was one thing that worried me, so I'll change it to the ones that are entirely composed of stupid "Yahoos" and so on. Yoshi876 (talk)

Shouldn't we reset votes? Because this proposal got altered, making my oppose vote pointless Baby Luigi (talk)

I did, but Walkazo said that even though it's been changed, I can't remove the votes. You might be able to remove your oppose, or you'll just have to put the line through it. Yoshi876 (talk)
Yeah, you can't remove comments and votes like that - although if the users don't check back in on their own, you can contact them and let them know the proposal changed and their votes are no longer applicable. Also, since Baby Luigi's original vote was addressed in the comments, it would be best if she'd slash it out, rather than remove it - and then re-cast or rewrite her vote, if she so chooses, of course. - Walkazo (talk)
My only concern with getting rid of those two, is that they'd probably still agree. I mean the proposal only changed to keep the meaningful quotes and so I highly doubt they'd say 'No, let's get rid of those ones as well'. Yoshi876 (talk)
Well, you don't have to let the users know there was a slight change: it's ultimately up to a voter to check back in even after they vote. If a proposer wants to let them know, they can, but if they don't, they don't; like you said, they'll probably keep supporting, so if you want to just leave it, that's perfectly fine. If there was a major change, it'd be best to archive and restart the proposal, that way the voting is reset, but that'd be unnecessary here. Don't be concerned about something you don't have to do anyway. - Walkazo (talk)

Remove all unsourced information from glitches and beta elements pages

This was first discussed here.

It is extremely easy to put a glitch or a beta element on it's corresponding page without providing any proof. Therefore, I am suggesting that we remove all unsorced information from these pages, though they can be brought back if someone gives actual proof about these (an image, a source from a reliable external site, or a YouTube video is enough), because these "glitches" or "beta elements" can just be a random user typing random things.

Proposer: Mr. Game & Watch (talk)
Deadline: June 8, 2013, 23:59 GMT

Remove unsourced information

  1. Mr. Game & Watch (talk) Per proposal.
  2. Baby Luigi (talk) Per proposal, but I also want to add that sourcing the glitch from an external, but reliable site will suffice as well.
  3. TheRedOne (talk) Per proposal.
  4. Mariotime11 (talk) I've seen extremely absurd glitches (such as Template:Plainlink), which could provide false information. Having to provide a reliable reference will ensure that the glitch is real. Per proposal.
  5. ThePremiumYoshi (talk) — Per all. I especially agree with removing unsourced beta element information.
  6. Yoshi876 (talk) Per proposal.
  7. King Pikante (talk) Per all.

Keep unsourced information

  1. Banon (talk) I agree that some glitches are ridiculous, however sometimes contributors add a real glitch but can't provide a source. If we got rid of all the unsourced glitches, we would lose these glitches.

Comments

@Baby Luigi; I added your suggestion to the proposal. Mr. Game & Watch (talk)

Actually, how about requiring a reference for every glitch? Mariotime11 (talk)

Isn't removing unsourced material basically already covering that? Baby Luigi (talk)
I can't imagine all those unconfirmed sources to be thrown away at all. Some of the glitches may have legitimate results if inputted correctly. I suggest creating a group that dedicated to: confirming the glitches by providing references found on the internet, or reproducing them on their on and making references of their own. Of course, it'll be tedious for everyone involved because it requires someone to play the game in it's original fashion, and that the former is probably more easier to do than the latter in terms of time commitment. RAP (talk) 22:28, 1 June 2013 (EDT)
@RAP, some people may need help from a youtube video or image and couldn't understand the inputted text without it, or the image/video could be used as proof to the glitch. I don't think we need a group based on glitches. TheRedOne (talk)
This is just like confirming elements for an upcoming game: you can't prove it exists without a reliable source, and too many of these entries are questionable. It's like saying I work for Nintendo. Baby Luigi (talk)

I'm really torn about this. I do feel we have to remove unsourced content, but I feel it would be far better to add a template similar to the one the Fallout Wikia uses on unverified glitches/bugs. It's simple; when a bug hasn't got a source, they add the template, indicating a four week period in which a source for the bug should be mentioned. If the four weeks pass and no source was indicated, the template will indicate the verification is overdue. I feel that's a good compromise, as we wouldn't be outright deleting stuff that could be valid, but we wouldn't be keeping unsourced glitches. -- Tucayo (talk)

Changes

No you's, no I's

Ok, here goes. Yesterday I came upon a little something not-so-pleasent. So, I deleted it and said it happened on that article's talk page. It was Super Mario 64 DS glitches Chill Bully Suicide. That certain glitch has a template that warns people about corrupting or permanantly damaging their system. Now for the bad part. I found the words "I MEAN IT" exactly like that at the end of the section. My point is, we should change the "no you's" rule and add "no I's". This makes sense as to that people who do that break a writing rule and are (maybe, depending how much they do it) blocked.

Proposer: MegaDigga3 (talk)
Deadline: June 12, 2013, 23:59 GMT

Support

  1. MegaDigga3 (talk) It's my proposal, and I agree with it.
  2. Banon (talk) We should add this new rule here.

Oppose

  1. Yoshi876 (talk) Whilst I agree, most people do this anyway and it'd only be new users or IPs who wouldn't know what they were doing and would only need a friendly nudge in the right direction.
  2. YoshiKong (talk) The policy applies to second person, which includes the use of "I".
  3. Baby Luigi (talk) Per YoshiKong. This proposal is completely redundant.
  4. King Pikante (talk) Per all.

Comments

This proposal is unnecessary because it's already our policy; that proposal wouldn't change anything :/ — Banon (talk)

Using any second person word not only violates the "No You" rule because it applies to first person as well, but also are completely nonstandard and unprofessional, thus violating another universal rule about standard writing, which this wiki definitely uses. This proposal is not necessary in any way since there will not be any change regardless of which side gets more votes. Baby Luigi (talk)

I did not know that Baby Luigi... MegaDigga3 (talk)

Well, this is an FYI thing, so yeah. Baby Luigi (talk)

Intro standards for subpages

This has been discussed here and here.

First of all, when I say "subpages", I mean pages that were previously subpages, and current subpages. This includes the glitches, media, quotes, staff, beta elements pages, as well as galleries.

So basically this proposal is "let's have a standard for subpages intros!". Why?

There are so many variations in how the intro is worded: a standard write-up would be great.
YoshiKong

I would also like to add a clarification:

It's still a good idea to have a slug line up there, rather than leaving the top of the page blank.

Consistency is good, but the intro could be changed up a little for different types of galleries - to provide a little variety.

Like "This is a gallery of images pertaining to the game Template:Fakelink." (which could, when applicable, be followed by "For a gallery of images pertaining to the remake, Template:Fakelink, see Template:Fakelink.") for games, and then substitude "show"/"movie"/whatever if it's part of another media. Then "This is a gallery of images featuring (the) X(s)." for specific subjects (characters/species/items/forms/gaming systems). Specialized subjects may also need specialized intros to work (i.e. "This is a gallery of the images from Rosalina's Storybook, featured in Super Mario Galaxy.").

Walkazo

Proposer: Banon (talk)
Deadline: June 8, 2013, 23:59 GMT

Support

  1. Banon (talk) This is my proposal.
  2. YoshiKong (talk) – Per Banon.
  3. ThePremiumYoshi (talk) — Per proposal.
  4. GBAToad (talk) Per Banon.
  5. Baby Luigi (talk) Per proposal
  6. Mr. Game & Watch (talk) Per Banon.
  7. King Pikante (talk) Per all.

Oppose

Comments

Miscellaneous

Merge the DK: Jungle Climber navigational templates

Merge all of the DK: Jungle Climber navigational templates into one template (with a separate template for the levels)

The way that the templates for DK: Jungle Climber are set up is just... odd. The characters, the minigames, the worlds, and the levels in each world all have templates made specifically for them, and I am just confused as to why. There are only nine characters in the game (including major and minor) seven minigames, six worlds, and thirty levels in this game, and that's not including the enemies that we never decided to list and the items that were haphazardly listed. At most, we have (or at least should have) an individual template for anything that has a lot of entries for it (levels, minigames, items, etc.), and then one for everything else. However, the individual templates usually have around 50 or more entries in them, whereas here, we have at most, nine, and that's for the characters. So, I propose to merge all of these templates (Jungle Climber for the characters, DKJC-Minigames, Worlds in DKJC, Sun Sun Island, Lost Island, and Chill 'n' Char Island) into two templates; one for the six worlds and thirty levels, and one for all the other templates, as well as including any other elements that are not included in any of these templates, such as enemies and items. Since I'm only able to work with what the wiki currently has (and I'll presumably be the one creating this all-inclusive template), the template might not be entirely complete, but in my opinion, it'll look a lot better than what we currently have.

Proposer: Time Turner (talk)
Deadline: June 2, 2013, 23:59 GMT

Merge templates

  1. Time Turner (talk) Per proposal.
  2. Yoshi876 (talk) Per proposal, and if I'm correct all the games do this anyway so it keeps it consistent.
  3. MegaDigga3 (talk) Per Yoshi876.
  4. Mario4Ever (talk) Per proposal.
  5. ThePremiumYoshi (talk) — Per all.
  6. King Pikante (talk) Per all.
  7. YoshiKong (talk) Per policy.

Keep split

Comments

I think put in "DK: Jungle Climber Places" for the first of two templates mentioned. MegaDigga3 (talk)

You don't need a proposal for this: policy already states that games should only get single all-inclusive templates (although they can leave levels separate, as well as other sprawling groups of pages that will make the template unwieldy if they're included). - Walkazo (talk)