MarioWiki:Proposals

List of talk page proposals

 * Split Densetsu no Stafy 3 from Video game references (Discuss) Passed
 * Split ghosts from game page (Discuss) Deadline: June 17, 2013, 23:59 GMT
 * Make a separate subpage for places (Discuss) Deadline: June 18, 2013, 23:59 GMT

Writing guidelines
None at the moment.

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

 This section is empty. Please add a short description of the main article.

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 Maintenance page.

Proposer: Deadline: June 4, 2013, 23:59 GMT

Support

 * 1) This is my proposal.
 * 2) From what I understand, I think it is a good idea.
 * 3) Per proposal.
 * 4) Per proposal, except make the template a different color than the trivia one.
 * 5) Per Baby Luigi.
 * 6) Per Baby Luigi. I also think that it should be just a tad more descriptive.
 * 7) &mdash; Per Baby Luigi and MegaDigga3.
 * 8) Per all.
 * 9) Per Banon and Baby Luigi.
 * 10) Per all.  A different colour would be better though, like maybe a dark blue or purple.
 * 11) Per proposal.
 * 12) Per all.

Comments
I agree for your criticisms about the template. Feel free to make your own version of the template! —


 * What about this:

 This section linking to another article is empty. Please add a short description of the main article.


 * Also, I'm not very good at coding so someone should probably look at it... 09:54, 30 May 2013 (EDT)
 * It looks too much like the image template. I suggest

 This section linking to another article is empty. Please add a short description of the main article.
 * 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.
 * 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:

 This section linking to another article is empty. Please add a short description of the main article.
 * 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?
 * 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?

 This section linking to another article is empty. Please add a short description of the main article.


 * I agree that it would be best to make it look like . 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. -
 * I dunno why, but I like black for referencing something empty. But whatever floats your boat.

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).
 * That would cause more confusion than it's worth.
 * 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.
 * 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.
 * 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.

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.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).
 * 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.

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... -
 * 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
 * What about this:

 This article contains one or several empty sections. Please add a short description of the respective main articles.
 * 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. —
 * 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. —


 * 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). -
 * Agreed. So maybe I should withdraw my proposal and replace it by a collab thread on the forum? 16:51, 3 June 2013 (EDT)
 * There actually is a collab thread for this issue, it's just dead - but you can bump it if you want, I suppose. Whatever you feel is best: it's your proposal, after all. -

Uh... Is it too late to withdraw my proposal? I should have done it yesterday but I couldn't. —
 * It has already passed.

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: Deadline: June 8, 2013, 23:59 GMT

Remove unsourced information

 * 1) Per proposal.
 * 2) Per proposal, but I also want to add that sourcing the glitch from an external, but reliable site will suffice as well.
 * 3) Per proposal.
 * 4) I've seen extremely absurd glitches (such as ), which could provide false information. Having to provide a reliable reference will ensure that the glitch is real. Per proposal.
 * 5) Per all.
 * 6) Per all.
 * 7) Per all, we don't need stuff like "There was gonna be a portrait ghost who was removed in the final product because he would have had frightening dialogue" that isn't sourced
 * 8) Per all.

Keep unsourced information

 * 1) 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.
 * 2) Yes, well some glitches are completly bogus, there is a very small amount of bogus glitches in pages. Also, I have tested unsourced glitches that work, making no sense to remove all unsourced glitches. If I can, I would help to get a reference for them.
 * 3) – I believe that removing unsourced glitches would mean that their would be less than half left over. Not all unsourced glitches are bogus: instead of removing potentially legitimate information, we should add a request for reference tag. I strongly disagree with this proposal.
 * 4) - Much better than outright than removing them.
 * 5) Per Tucayo's comments below
 * 6) Per All
 * 7) This seems like a very extreme way to go about this. Per all.
 * 8) - Per all.
 * 9) - Per all: removing them is shooting first and asking questions later. It's always best to avoid scrapping potentially good info, and until we find the desired proof, we can just use  to let readers know that stuff's unverified.
 * 10) &mdash; Actually, Tucayo does have a good point, so per him.
 * 11) Per all
 * 12) Per all.
 * 13) Per Walkazo.

Comments
@Baby Luigi; I added your suggestion to the proposal.

Actually, how about requiring a reference for every glitch?
 * Isn't removing unsourced material basically already covering that?
 * 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. 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.
 * 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.
 * I forgot to insert that I would prefer implementing a group dedicating to this task if this proposal passes. So far the majority of the tally votes oppose this proposal.

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


 * If this passes, I'm going to try my very best to overturn it. The proposed action really isn't the right way to go. -- 09:49, 3 June 2013 (EDT)


 * Or a template like the Wikipedia one? 16:48, 3 June 2013 (EDT)

I agree with YoshiKong, this proposal is outrageous, it makes no sense, no one here seems to me that adds fake glitch has never happened and never will happen to me, even if there was a low probability to happen it would not be a drama I think it's that easy to recognize a true glitch a glitch invented on the spot, and then there are numerous glitch without sources, but that can be easily found on youtube. --Sonic98 16:54, 3 June 2013 (EDT)


 * @Banon: We already have such a template: . -

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: Deadline: June 5, 2013, 23:59 GMT

Support

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

Oppose

 * 1) 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) The policy applies to second person, which includes the use of "I".
 * 3) Per YoshiKong. This proposal is completely redundant.
 * 4) Per all.
 * 5) Per all.
 * 6) - Per all, including Baby Luigi's comments below.

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

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.

I did not know that Baby Luigi...
 * Well, this is an FYI thing, so yeah.

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 ." (which could, when applicable, be followed by "For a gallery of images pertaining to the remake,, see .") 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: Deadline: June 8, 2013, 23:59 GMT

Support

 * 1) This is my proposal.
 * 2) – Per Banon.
 * 3) &mdash; Per proposal.
 * 4) Per Banon.
 * 5) Per proposal
 * 6) Per Banon.
 * 7) Per all.
 * 8) Per all.
 * 9) Per all.
 * 10) Per all.
 * 11) Per all.

Comments
Just to be clear, are you proposing we have something along the lines of Walkazo's example or something else entirely?
 * I think the Walkazo's example is great. —

Miscellaneous
None at the moment.