MarioWiki:Proposals

Proposals can be new features (such as an extension), removals of previously added features that have tired out, or new policies that must be approved via consensus before any action is taken. Any user can support or oppose but must have a strong reason for doing so, not, e.g., "I like this idea!" "Vote" periods last for one week. All past proposals are archived.

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}}.

This page observes the No-Signature Policy.

How To

Rules

1. If users have an idea about improving the wiki or managing its community, but feel that they need community approval before acting upon that idea, they may make a proposal about it. They must have a strong argument supporting their idea and be willing to discuss it in detail with the other users, who will then vote about whether or not they think the idea should be used. Proposals should include links to all relevant pages and Writing Guideline proposals must include a link to the draft page.
2. 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.
3. Every vote should have a reason accompanying it. Agreeing with or seconding a previously mentioned reason given by another user is accepted.
4. 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.
5. 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.
6. No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
7. 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.
8. All proposals that end up in a tie will be extended for another week.
9. 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.
10. 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.
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 an administrator, the proposer can ask for that help.
12. Proposals can only be rewritten or deleted by their proposer within the first three days of their creation. However, proposers can request that their proposal be deleted by an administrator at any time, provided they have a valid reason for it. Please note that cancelled proposals must also be archived.
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. There should not be proposals about creating articles on an underrepresented or completely absent subject, unless there is major disagreement about whether the content should be included. To organize efforts about completing articles on missing subjects, try creating a PipeProject.
15. Proposals cannot be made about promotions and demotions. Users can only be promoted and demoted by the will of the administration.
16. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.

Basic Proposal and Support/Oppose Format

This is an example of what your proposal must look like, if you want it to be acknowledged. If you are inexperienced or unsure how to set up this format, simply copy the following and paste it into the fitting section. Then replace the [subject] - variables with information to customize your proposal, so it says what you wish. If you insert the information, be sure to replace the whole variable including the squared brackets, so "[insert info here]" becomes "This is the inserted information", not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but what each voting section is supporting must be clearly defined.

---

===[insert a title for your Proposal here]===
[describe what issue this Proposal is about and what changes you think should be made to improve how the Wiki handles that issue]

'''Proposer''': {{User|[enter your username here]}}<br>
'''Deadline''': [insert a deadline here, 7 days after the proposal was created, at 23:59 GMT. (14 days for Talk Page Proposals.)]

====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 here.

Rules

1. All active talk page proposals must be listed below in chronological order (new proposals go at the bottom). All pages affected must be mentioned in the brief description, with the talk page housing the discussion linked to directly via "(Template:Fakelink)". If the proposal involved a page that is not yet made, use {{fakelink}} 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 {{TPP}} 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. (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. Talk page proposals may be closed by the proposer at any time if both the support and the oppose sides each have fewer than five votes.
5. The talk page proposal must pertain to the article it is posted on.

List of Talk Page Proposals

• Delete The Weekly Wario or merge it to WarioWare: Smooth Moves (Discuss) Deadline: March 31, 2012, 23:59 GMT
• Split Red and Green into separate articles. (Discuss) Deadline: April 1, 2012, 23:59 GMT
• Provide a raw premade aboutfile template for the Upload file page. (Discuss) Deadline: April 1, 2012, 23:59 GMT
• Change Character Infobox image for Bowser. (Discuss) Deadline: April 10, 2012, 23:59 GMT

Writing Guidelines

Creating Separate Level Pages in Super Mario Platformers, and Reworking Use of World Pages

Draft: User:Bwf8398/Draft

Since the creation of this site, users have been told that if a level has a name, such as Awesome, it gets its own article, but if the level is a number, such as World 2-4, then it does not. Currently, World articles are being used to house information about 6 or 7 different levels, in places such as World 3 (New Super Mario Bros. Wii). If the levels had names, they would most certainly be given separate articles, and the idea that the entire position and most of the writing quality of a level article is based on its name is absurd. People say that it is because it can be hard to find a specific level, such as world 2-4, when there are multiple levels under that name, but the current system is no better! Users have to find World Articles instead, and there are even more articles about World 2 than there would be about something like World 2-4. It is much better to have many short to medium length articles that use infoboxes to be easier to understand than to create long, useless world articles, where information about the levels are basically non-existent.

People say that inconsistency is a bad thing, and this is another case of it. The fact that some games have their own level articles, while others are instead lumped together in world articles is very confusing to someone not familiar with the site. I remember spending a long time trying to find an article for World 9-6 in NSMBW before I was on the site, because I thought that the description on the world page was just an overview, and that the actual article was elsewhere.

Though in theory, it is true that articles will be the same length regardless of if they're in a World Article or a Level Article, this is not true in practice. The truth is that there are several paragraphs in a well-written level article at least, and writing quality suffers severely in the level articles. The reason is that the page is already so long, and seems to have so much information that users do not feel it necessary to add more. However, it becomes a problem when articles turn out to be this short:

This is the only level that features Huckit Crabs. There are also a lot of Urchins and Mega Urchins. From World 4-3 (NSMBW)

This gives no information about the level, just that three enemies appear in it. Compare that to articles such as this, from Super Mario World, or Bramble Scramble, which attained FA status, and you realize how much having its own article affects if people actually work on it.

Naming

Articles should be named as "Level name (game it's from)". For example, names should be like World 2-4 (New Super Mario Bros. Wii) or World 1-3 (Super Mario Bros. 2), and redirect for all abbreviations (e.g. World 2-4 (NSMBW)). For levels where the second number is a picture, name them as World 3-Fort or World 6-Airship. Disambiguation pages will also have to be created, but there are so many of these already for world articles that it won't increase the total that much.

Components of an Article

Many users oppose this, claiming that this would just create stubs. However, these articles will certainly be longer than things like the minigame articles, such as this, if written correctly. In each platformer article, there should be:

• An infobox, containing a picture sized at 260 px. There is already an infobox available for New Super Mario Bros. Wii, which could probably be recycled for other games, such as Super Mario 3-D Land.
• A short introduction, describing the setting of the level, any unique characteristics the level has, etc.
• One section for each room in the level. A room is defined as a continuous sections of a level, such as the beginning of a level to the first Warp Pipe. If the screen has to redraw, then the player has entered a different room. Rooms which must be gone through in order to complete the level should be called "Main Room (Number)", and optional rooms, such as those that only contain 1-Up Mushrooms or Star Coins, should be labeled as "Secret Room (Number)", where the numbering is based on how early on they appear in the level.
• One section containing a list of all enemies in the level, such as in the Super Mario Galaxy 2 levels.
• One section briefly describing position in world; what levels it unlocks, and what levels are prerequisites to play this.
• One section describing any Hint Movies for the level, if applicable
• One section for trivia
• If available, a level map, such as what is currently featured here.
• Description of Boss Battle (Fort and Castle levels only)

Components of a Room Section

• Brief description of setting, if changed (e.g. grassland to underground)
• Any Star Coins or 1-Up Mushrooms in it
• Hazards: Enemies, Pits, Scrolling Camera
• For main rooms, any rooms it leads to.
• For secret rooms, what room leads to them.

Using Template:Main

The other main complaint users have as that this would require a lot of extra clicking, and navigation. To counter-act this, I propose that we write brief descriptions of each level in the world article, and then link these to the main article. That way, the world articles could focus more on the world itself, rather than merely being a collection of disjointed information about different levels. This could be used to give a short summary of the level, so that readers can distinguish and select the level they want, without going to over-the-top detail.

Though this will require a lot of work, it will make the information many times easier to understand, and improve the quality of writing on all Super Mario Platformer levels greatly. Please consider carefully, and post any questions in the comments. Example articles are included in the draft.

Proposer: Bwf8398 (talk)
Deadline: April 12, 2012, 23:59 GMT

Support

1. Bwf8398 (talk) - Per the proposal.

Oppose

1. Raven Effect (talk) Per the arguments in ever other proposal that deals with this matter [1] [2] [3] [4] [5]
2. Mario4Ever (talk) From a navigational standpoint, it makes more sense to have all of the levels in one article (e.g. by world) rather than separate articles on the levels.
3. Super Famicom 64 (talk) Proposal passes = load of new stubs. No.
4. RandomYoshi (talk) – Per Raven Effect.

Comments

Please be more specific Raven Effect. You are not giving a reason as much as a redirection to proposals on different issues, and this explains nothing to people who haven't extensively read other proposals that may be similar. Bwf8398 (talk)

Thank you for the links, but please point out one thing in there that isn't covered here. I have studied them carefully and taken measures to counteract such problems. This won't create inconsistency, which was the main point in number 5, because it will be for all platforming game. Proposal 4 merged them because they were stubs that were badly written, which I have explained how to avoid in the proposal. Proposal 3 is similar to what Mario4ever said- it would be combatted by leaving enough info on the page so that users can distinguish between levels, and if a user wanted to read a level more extensively, it's just one click. Proposal 2 was similar to point 3- users said the info wold be harder to reach, which is combatted by main article template. And Proposal 1 was incoherent, since the user seemed to want to merge every World 1-1 into one article, which is irrelevant to my proposal. None of the points in those aren't covered in the proposalBwf8398 (talk)

@Mario4ever: That's what the use of Template:Main is all about- there will still be info, but much more will be presented in the actual article. They will all still be in one place, and it will be easy to access.

We do have articles for galaxies for SMG 'n' SMG2, but they don't count as levels, and if users search for example World 3 (Super Mario Bros. 3) in search for level information, they won't find it. Super Famicom 64 (talk)

@Super Famicom 64 This would not mean that we would have stub articles if they are written correctly Raven Effect (talk)

Sorry if I'm going to go mad but MOST OF THE SMW LEVEL ARTICLES ARE NOT STUBS AND THEY ARE THE SAME LEGTH AS NSMBW. Everything needs an article. New Super Yoshi (talk)

Navigation Templates

Draft: User:Walkazo/Essays#Navigation_Templates

This proposal is aiming to do for navigation templates, what this proposal did for categories. As seen in the draft, this will expand and update MarioWiki:Navigation Templates, and while this will not overhaul the system like the categories proposal, there are a few changes, which I'll briefly go over here.

First of all, the policy includes a big chart of colours that should be used for all game- and series-based templates; I also have examples of recoloured templates further down my page. (There was already a proposal about this, but that user didn't create an actual code, so no actual changes could/should have come as a result of its passing.) Non-series-based templates (i.e. stuff like {{Koopa Troopas}} or {{Cheeps}}) can be given unique colours that pertain to their subject matter, rather than using the same colours as their parent series.

Secondly, the order in which templates should be placed on articles is outlined in the policy: namely, any random templates (i.e. species-based templates) should come first, followed by all the game/series-based templates, which should go in pure chronological order. So, unlike History sections, which clump series together, different games would simply be arranged according to the year they came out, with no regard for when the rest of the series' installations were released. Instead, the templates' colour-coding can be used to pick out all the members of a given series.

Finally, the policy outlines what types of templates can be made. Basically, there are three types of templates, each with slightly different content structure and criteria:

• Game-specific templates will ideally contain everything about a game, like {{DKC2}} or {{SML}}, whereas separate templates about certain specific aspects of a game should hereon in be avoided. However, if a subject is very numerous, such as minigames, levels or RPG items, it can keep its own separate template, since merging it might make the main template too bulky. For example, {{YIBC}} (bonus challenges) should be folded into {{Yoshi's Island}}, but {{YoshiLevels}} can stay separate. Both the main template and the separate level/whatever template should go on the level articles, but obviously, the level template wouldn't need to go on non-level pages (except the game's page itself, which should have all the relevant game-specific templates).
• Series-wide templates should almost always be templates that list the games in a series, rather than templates for subjects that are found all throughout a series. These should only be made for things like {{Racecourses}} that have lots of overlap or parallels between games best served by back-to-back comparisons, or things like {{RPG Attacks}}, where a centralized list of far-reaching subjects is likely to be organizationally useful in a manner similar to species templates (see next entry), but limited to a single series and organized by game. In most cases, however, game-specific templates are a better way to organize things than templates like {{Yoshi}} or {{Wario}}, both of which will be scrapped should this policy pass.
• Everything else are species templates, which groups things based on what they are, rather than where they come from. Most of these templates will be species-based, like {{Goomba}} or {{Human}}, but important items like {{Blocks}}, and even a few miscellaneous subjects like {{Earth}} or {{MarioFamily}} are given this sort of template too. The only stipulation is that they all have to be decently important, numerous and/or complicated: really minor and small, or overly large, vaguely defined groups of species (i.e. anything smaller than {{Blarggs}}, or things like Category:Fish) don't need templates, and items and miscellanea are under even stricter scrutiny, so users will have to think long and hard before making templates like these.

The policy also has a big section on how to set up templates (i.e. what headers to use, how to arrange the lists of links, etc.), but that's a lot of nitty-gritty details, and it's mostly explaining what we already do, so I won't go over that here. If you have any questions about details on the draft or aspects that I could only briefly touch upon in the proposal, definitely post them in the comments, but overall, I hope this and the draft are enough to convince you that this will be a vast improvement to the small, outdated policy we have today.

Proposer: Walkazo (talk)
Deadline: March 30, 2012, 23:59 GMT

Support

1. Walkazo (talk) - Per my proposal.
2. Bop1996 (talk) Per proposal.
3. Mario4Ever (talk) Per proposal.
4. Baby Mario Bloops (talk) - Per proposal.
5. Commander Code-8 (talk) This is a great idea. Per Proposal.
6. Phoenix (talk) Per proposal.
7. RandomYoshi (talk) - Per all.
8. Super Famicom 64 (talk) - Per proposal.
9. Lakituthequick (talk) Per proposal. Little bit complicated, but good idea.
10. Tails777 (talk) Per all.
11. Jazama (talk) Per all
12. Fawfulfury65 (talk) Per proposal.
13. Coincollector (talk) Per proposal. We badly need this.

Comments

I know you're trying to be clear, but can you please clarify further/sum it up what the changes are? I can't really comprehend what's going to happen, it seems too complex. BabyLuigiOnFire (talk)

I don't understand this proposal either. All I know is that it is supposed to improve organization or something in templates. The rest, I had trouble comprehending. LeftyGreenMario (talk)

The first section (of this proposal) covers the various template colors that are to be used (the color depends on the template). The second section determines template priority (so at the bottom of an article, you'd have species templates, followed by game/series templates (in order of release date by game)). The third section details what information goes into each template. The rest is about making templates in general. Mario4Ever (talk)

Ah, thanks for clearing that up BabyLuigiOnFire (talk)

No problem. Mario4Ever (talk)

Mario4Ever's summary was bang on. And to clarify, this proposal isn't so much about making a few specific changes, but rather, getting a bigger, better policy approved. A lot of the drafted update to MarioWiki:Navigation Templates is just explaining unwritten conventions that are already more-or-less followed, but from this point onwards, there will be something concrete to refer back to. It's also regulating a few things that are inconsistent now, or at the very least, making recommendations based on the various ways users are already setting up their templates. There are too many details to list, but there are a few notable features that I can further boil down if you guys do want the specific changes:

• New colour-coding system (different series get different colours; random stuff gets personalized colours).
• New order on templates (random stuff first, followed by games in chronological order).
• Templates about subjects across a series (i.e. {{Yoshi}}) are now discouraged.
• Everything about a game should be in one template, rather than multiple smaller ones, which used to be done periodically. The exception to this is when there's a really big subject like SMG galaxies, which can be left separate just to keep the templates from getting unmanageably large.
• In the cases where there is a separate template for an aspect of a game, both that template and the main template would go on the page (i.e. a SMG galaxy would have both {{SMG}} and {{Galaxy}}, but an SMG enemy would only get {{SMG}}), whereas currently, the main template is often omitted.

The template classification and the terminology is also new (under the old system, there's four template types, whereas there's three types in the draft), but that's more of an internal change: it's important from a policy standpoint, but only the above list will really be affecting the wiki at large. A couple of the finer details (which I didn't talk about in the proposal to save space) that will also affect folks are:

• Templates must be 100% wide (most of them already are, but there are a couple that run afoul of this, however a lot of them are already in trouble with the fourth bullet point).
• If a page has 10 or more templates, they should be collapsed using {{navtemplate}}; the original threshold is 7. As always, the templates themselves should all be collapsible.
• Templates should not have categories in them (this is already on the categories policy, but this emphasizes it).
• Nav templates are for mainspace only (same as the current policy), with galleries and game subpages (/beta, /staff, etc.) getting their own special templates.
• Really minor or vaguely defined subjects shouldn't get templates (i.e. yes to {{Boos}} and {{Mushrooms}}, no to {{Fish}} or {{Trains}}, same as always.

And that's all I can recall for now; I can't simplify the proposal any more than that without getting rid of the details, but like I said at the beginning of this post, when it comes to an in-the-nutshell description, M4E's post already has it covered. - Walkazo (talk)

Would Template:GPteams be merged to Template:PM2 as a result of this proposal? Reversinator (talk)

I have a question about the templates: would it be a good idea if we add pictures to some templates? Or do all of them have to be a solid color? LeftyGreenMario (talk)

Reversinator: No, GPteams is large and complex enough to remain separate: it's a good idea to sort the teams, but it would take up too much room and draw too much focus to a relatively minor aspect of the game to do so in the main PM2 template. LeftyGreenMario: Solid colour; templates don't need flashy pictures, and most won't get them anyway, which will just make things inconsistent and draw extra attention to a few select templates, wrecking the uniformity of the colour-coded blocks. However, I do think the image-background currently used on {{Super Mario Bros.}} would be a neat addition to {{Galleries}}, seeing as that template is unique, and appears on a special group of articles (which are all about images). {{Media}} and other templates like {{BetaElements}} or {{Quotes}} might also work with that image setup, but with different background colours (i.e. dark blue from the water levels, and black for castles/underground; after that we'd have to get creative), or possibly different games' sprites, although that would be a lot more complex to make and set up. I didn't include that idea in the policy draft right off the bat, since I'm still mulling over the details, and seeing as it's a very specialized idea, I'd rather get specific approval for it with a subsequent Proposal. - Walkazo (talk)

Also, it would be nice to see what the templates will look like when it's finished. Considering the support in this proposal, maybe you can work on the future templates as soon as possible. That way, I can have a better understanding what the result will be. Also, it is possible to make templates always expanded when only a few of them are present, like in the minigame articles? LeftyGreenMario (talk)

The future templates are currently here BabyLuigiOnFire (talk)

Hm, my CSS makes all those templates the same color. :P LeftyGreenMario (talk)

You can see how it looks like when you log out. BabyLuigiOnFire (talk)

Odd - I copied all the actual template codes directly and then swapped the colours, nothing more: no idea why there'd be a problem seeing them. (Also, this is actually a more direct link to the test templates.) Anyway, I don't know if there's any way to make templates automatically expanded on short pages, but I wouldn't recommend it anyway: it'd be inconsistent with long pages, pushing the [show] button isn't exactly arduous, and personally, I think it looks better when they're automatically collapsed anyway - it makes the pages less bottom-heavy. - Walkazo (talk)

New Features

None at the moment.

Removals

None at the moment.

Changes

None at the moment.

Miscellaneous

Radio Conversation Characters

Peppy Hare, Slippy Toad, Krystal, Panther Caroso, Leon Powalski, Colonel Roy Campbell, Otacon, Mei Ling. All of these characters appear in codec conversations, either with Fox, Falco, Wolf, or Solid Snake. Panther, Krystal, and Leon have articles that redirect to the list of trophies, while the rest of them don't. I really can't see why they don't have articles. I mean, they all have the same role, and it's a minor one. Do the Metal Gear characters have articles because they have more dialogue? More dialogue doesn't change their minor role. Do Slippy and Peppy have articles because they appear in Arwings on Corneria to shoot people? We don't have articles on Tingle or Ultimate Chimera, even though they are also stage characters. There are quite a few options we could take: merging all of them to the stages they appear in (Lylat Cruise and Shadow Moses Island), merging all of them into one article specifically for them, making articles for Krystal, Leon, and Panther, or doing nothing.

Proposer: GreenDisaster (talk)
Deadline: March 31, 2012, 23:59 GMT

Merge to an article specifically for them

1. GreenDisaster (talk) Seems like the best way.
2. Tails777 (talk) Per GreenDisaster
3. Arceus79 (talk) Per other two
4. Commander Code-8 (talk) I don't think they all warrant a seperate but they should get an article that lists all of them.
5. Bowser's luma (talk) Sure. Per all

Comments

Peppy and Slippy were both in Meelee and brawl so that's why they have an article much like how Whispy Woods has an article but aside from that I pretty much agree with this proposal Raven Effect (talk)

Whispy Woods has an article because of its appearance in a Club Nintendo comic, I believe. We have a precedent of merging SSB-only stage hazards to stage articles, but not when they have other Mario-related appearances. Bop1996 (talk)

Would Peppy count? I mean, he did appear in a comic, but it was a really minor role. GreenDisaster (talk)