MarioWiki:Proposals/Archive/46

Split all remaining courts/boards based on recurring places from their parent articles
There's big inconsistently going on around the wiki partially revolving around stages in the sports games as well as Fortune Street that articles based on new places would be allowed their own article but those based on recurring locations will be forced to share an article (Bowser's Castle and Luigi's Mansion (place) amount the biggest offenders). What I don't get is that if they happen to stages from more popular games such as Mario Kart and Super Smash Bros., they get their own articles which isn't really fair. So I propose that all these sports courts and party boards are split from their parent article as I think the wiki is better off that way.

I was oringnally going to have this as a TPP on Bowser's Castle but I realised this issue was much present outside the article.

Proposer: Deadline: September 24, 2016, 23:59 GMT

Support

 * 1) Per what I said above.
 * 2) That's a great idea! Per NSY!
 * 3) Per all
 * 4) per all. By the way, this proposal can be used for finding out which people are willingly wanting to be involved. If there is someone who is determined not to do it, that person would most likely oppose; but not all opposes (in theory) will be from people who are that way; there could be some who just don't want those to split but would do it if this passes.

Comments
I like the proposed idea, but only if someone were willing to take the responsibility of making sure that the splitted sections do not become stub articles. For example, the Mario Hoops section in Luigi's Mansion (place) is severely lacking in information, and if that area in the game isn't very unique as it sounds (I know nothing about Mario Hoops 3 on 3), then it would turn out to be an awful article.
 * I can ensure that those sections that are currently in states that would result in them benign stuby would be expanded to contain enough information. All the other courts from Mario Hoops 3 on 3 have enough info on them so it shows that it can be expanded to a decent length.

NSY, there is nothing that has "forced" the merge with the main place articles. Nor does it depend on how "popular" games are. New articles already states that all individual stages (including SSB stages, party boards, racing and other kinds of sports stages) be given a stand-alone article. Most splits should be done immediately due to the acceptable size of the article sections. Some still require a "layout" section (such as the Fortune Street series boards which are still merged), which would guarantee an acceptable size according to the policy. The article identifiers would need to be determined, I suggest these for all the boards/sports courts.


 * Bowser's Castle (Fortune Street series)
 * Bowser's Castle (Mario Sports Mix)
 * Bowser's Castle (tennis court)
 * Bowser's Castle (basketball court)
 * Luigi's Mansion (Mario Sports Mix)
 * Luigi's Mansion (basketball court)
 * Luigi's Mansion (baseball field)
 * Peach's Castle (Fortune Street series)

I think these titles would be acceptable. The bottom line is, you don't actually need to pass a proposal to split these articles; we just need users who are willing to do so. This proposal should best be withdrawn. – 04:05, 18 September 2016 (EDT)

Pixl Queen, Waffle Kingdom, and Croacuses (rulers)
It may seem like common sense to do right now the first two, but the third one wasn't mentioned in the passed proposal. The Pixl Queen story had a major part of the story before Super Paper Mario happened. The Waffle Kingdom has many characters from it. As for the Croacuses, they are former rulers of Floro Sapiens. I would like all three (more like 6 because the croacuses rulers are four, but I could do just the actual three rulers not the prince. Either way, the Croacuses are together.) be split from the respective articles, yet still have some kind of a mention in them. Because how this proposal is set up, only one choice can be chosen by a voter.

Proposer: Deadline: October 8, 2016, 23:59 GMT

Do all three

 * 1) I want to do all three.

Do only two
If you vote here, please say which two. The 2 highest will be chosen.

Do only one
If you vote here, please say which one. The highest will be chosen.
 * 1) Of all the three listed, the Croacus family are the only ones who are physically seen in some way. While they are just photos, having info on their pasts as well as an idea of what they look like puts them at more of an advantage against the Pixel Queen and the Waffle Kingdom. So if I'm gonna pick and choose, I'd say that the Croacus family should get separate articles, mainly since they have a bit more to work off of.

Do none of them

 * 1) I want to say I will oppose!

Comments
Alright, the options in this proposal are a mess. You can't have specific conditions on each option, options need to be absolute and clear. And you can't make the proposal ignore a rule (saying users can only vote for one option). To be honest, this feels like three proposals crammed into one. Either split this into three TPP's in List of implied characters our outright remove this proposal. -- 22:45, 1 October 2016 (EDT)
 * Ok, I will let the proposal run during the weekend and sometime on Monday or early Tuesday, I will move it over to a more clear proposal(s) or cancel it all together. It all depends on the votes cast during this time. All those who do cast votes during this time will be talked to get them to vote in the proposal(s) if I do move it.

Create or delete categories about an area's citizens
As far as I know, there are only two categories that catalogue every inhabitant of an area: Category:Rogueport Denizens (for Rogueport) and Category:Glitzville Denizens (for Glitzville). It seems rather inconsistent for these two areas, densely populated as they are, to be the only ones to group an area's characters together. Such a category wouldn't be necessary for a lot of locations, but there are at least a few others, such as Toad Town, Flipside, Flopside, Shroom City (although that's a near-perfect overlap of Category:Mario Party Advance Characters), and possibly others. Since MarioWiki:Categories has a minimum amount of only five entries for a category to be created, this could theoretically get out of hand quickly, but there's nothing that's stopping us from moving the goalposts ourselves. At the same time, though, it's not as if the subcategories are all that necessary, since both the Rogueport and Glitzville citizens have a home in Category:Paper Mario: The Thousand-Year Door Characters, and they don't offera. So, let's put it to a vote: either we create new categories for other cities (within reason, unless it's discussed otherwise), delete the two categories that currently exist, or leave everything as it is and say that these are the only two areas that deserve categories.

Proposer: Deadline: October 2, 2016, 23:59 GMT Extended October 9 2016 23:59 GMT

Create categories

 * 1) This is my primary choice. If I had the Paper Mario: The Thousand Year Door, I would be an actual helper rather than just a supporter.
 * 2) My primary choice. It makes a lot more sense to create than delete, even if it does take more work.

Delete categories

 * 1) The characters that live in a given area can be listed on said area's article, and they can be included in a table that gives information about them; one example of this in action is this table on Goomba Village created by A gossip-loving Toad. Having these categories just doesn't seem beneficial to me.
 * 2) I agree with him! So, let's get rid of it and per him!
 * 3) I think we should do something for consistency, but I do not care what course of action we take.
 * 4) - A table would work much better. Per TT.
 * 5) The table look way better for this than category. So, per Time Turner.
 * 6) Per all

Do nothing

 * 1) This is my second choice. This wiki shouldn't just delete categories just because there is not enough of that category to make 5. If there is less then five areas in a game, would it make sense to delete those categories? The answer, unless they have no problem being with the game's characters.
 * 2) This is my second choice.
 * 3) My second choice, I just don't think deleting is a good idea.

Comments
Just to clarify what the proposal is this effecting, which category? Paper Mario: The Thousand Year Door characters, area characters, Paper Mario: The Thousand Year Door area charcters or another?


 * It's referring to Category:Rogueport Denizens and Category:Glitzville Denizens, concerning whether they should be merged with the overall Category:PMTTYD Characters, and the "inhabitants" be listen on the area articles instead of having a category.


 * I'm quite neutral about it. 31 and 34 pages in the "denizens" categories would make a very large list, unlike the example that MW:CAT gives on Aquatic Attackers, which is a very small list and already makes navigation with a category unnecessary. This is why we have "[game] Levels" categories, and "[game] Bosses". Sure, they could already be listed on the game article (with the table that you suggested). But since there's already a lot of other kind information on the game page, relying on a long and detailed page list could become quite exhaustive to navigate with. That's why we have "levels" and "bosses" categories for games. – 03:11, 25 September 2016 (EDT)
 * I didn't mean that the game's article would have a giant table; that would easily become way too big. I was suggesting that every location would have a table that lists the NPCs in that location. 18:26, 25 September 2016 (EDT)

@Yoshi the SSM: By voting for the "Do nothing" option, you're saying that the Rogueport and Glitzville categories are the only two that should exist, and that no other will be created. Since you seemed confused about the proposal's intentions, I wanted to make that clear. 18:26, 25 September 2016 (EDT)
 * Let me remind you that it is the second choice I am taking, not the first. It means that I would rather have nothing done than a deletion. I also rather create categories rather than doing nothing. Also, it is fact that people don't become leaders in most situations. 23:23, 25 September 2016 (EDT)

I don't see what's wrong with with having a category for the citizens as well as a table on the locations' articles. The Donkey Kong Country article has a list of all the levels and the game also has a category for its levels. One is a list of links and the other is a list of information. The categories for the Mario Party Advance characters wouldn't be too small, either. There are several locations in every city with many characters. Same for Paper Mario places.
 * I just find it to be a needless division that makes it harder to find certain information without offering much in return (as per Categories, only the lowest subcategory is placed on an article; anything higher isn't used). I don't think it's particularly beneficial to have a category for a given location's characters when those characters are already listed on the location's article. Anyone looking for its inhabitants would already go to the location's article, so the category doesn't offer any added convenience. 23:22, 28 September 2016 (EDT)
 * I'm not sure if I really like the "anyone looking for its inhabits would already go to the location's article". Wouldn't this be akin to saying that we have a list of all Goombas in the infobox of the Goomba article; therefore, we don't need a Goomba category? Or we have a giant list of enemies, we don't need Category:Enemies? And so forth. I myself don't exactly see the harm in including a category like this, which does add one layer of organization without being frivolous. The rules say, if the area is too small to have enough characters for a category, let common sense dictate that case and don't create the category. That doesn't seem that hard to me. 14:29, 29 September 2016 (EDT)
 * The Goomba article, at best, only has an undetailed list of species and characters in the infobox and a brief description of each of them smushed between the actual Goombas. A simple list alone is not what I want, but the table that I had suggested would be more helpful than the category. It's hardly unreasonable to say that someone who doesn't know the name of a character would go to the article of the location in which they appear, which is something that a category cannot do. The harm that I see in these categories is that the sky can actually be the limit: as I said, a category technically only needs a minimum of five entries to be accepted, and there are plenty of locations with more than five characters; common sense as to what the limit should be or which locations should or shouldn't get articles can vary wildly between people. Even if there's a rigid system that works perfectly and logically, the end result will be that there's a main category which contains the bulk of the characters and then a bunch of smaller categories that needlessly disperses a handful of other characters, making it harder for navigation. I do not see the benefit in having that. 14:44, 29 September 2016 (EDT)

Move Yoshi, Donkey Kong and Wario (series) pages to * (franchise) and retool
This has been bugging me for a bit, and looking at the series pages (which are, in general, a fully acknowledged mess) while tidying up the tables over the past day or two hammered that these three are simply not series - for DK and Yoshi in particular, the only commonality between them is that they feature the named character to some degree, usually in the title, being motley mixes of platformers, puzzles and "other". In addition, there are a bunch of series-within-these-series (including Wario) that get their own pages with nigh-identical content based on a subset of the page, in clear violation of Once and only once (compare Donkey Kong (series) to Donkey Kong Country (series), for instance).

What I'm proposing is that we retool along these lines. Not deleting or merging anything for now, just splitting a couple of things and reducing duplication on the basis that this'll be enough to be getting on with, since the series pages have long been a triumph of ambition over accomplishment...:

Nearly everything is already on a (sub-)series page anyway. Complete the job, remove the MW:O&OO-violating material and look to make a proper overview
 * Donkey Kong
 * - overview page. Initially this will probably be fairly short, but the ultimate goal is to have something along the lines of 's reworking of Mario (franchise)
 * Donkey Kong (series) - basically, this becomes everything based on the original arcade game and the sequels thereof (so the arcade games and their ports, Game & Watches, Donkey Kong GB)
 * Donkey Kong Country (series) - in the short-term, not terribly different from now. (Currently includes DK64, and I would keep that. Indeed, I would merge...)
 * Donkey Kong Land (series) - frankly, I think this should be merged with the DKC series page, which it has to be viewed in the context of, but unless there's heavy support for that, keep it as it is for now
 * Diddy Kong Racing (series)
 * Donkey Konga (series)
 * Mario vs. Donkey Kong (series)
 * DK (series)
 * The remainder remain on Donkey Kong (franchise) for now


 * Yoshi:
 * - overview page. As above
 * - all the Yoshi+Baby Mario(/etc) games
 * - could use a better name, but Yoshi, Yoshi's Cookie, Tetris Attack
 * The remainder remain on Yoshi (franchise) for now


 * Wario:
 * - overview page. As with DK, almost all of the games are on the (sub-)series pages anyway, it's just enforcing MW:O&OO
 * Wario Land (series)
 * WarioWare
 * The remainder remain on Wario (franchise) for now

Proposer: Deadline: 17 October 2016, 23:59 GMT

Support

 * 1) Per above
 * 2) Have those three as franchises? Yes. Have Donkey Kong Land part of the Donkey Kong Country? Best to keep them separate. How to do the franchises? Just like Mario (franchise). Why do I support the idea of making like the Mario (franchise)? Franchises must be similar in appearance. Series can be better, but I don't care much what happens to them. Also, they are more than just series. If you were to look at Super Smash Bros. (series), you will find out that their symbol is the franchise they are from. How long this will take to get completely done? Quite a while. 5th year of the Nintendo Direct will come before this is completed and probably the NX will come before this is 100% completed, but this last one is a bit of a stretch since the official date isn't known and this should take more than a month to do. Short answer is, I support the decision to do the proposal.
 * 3) This sounds like a good idea to me. About merging the DKC series and the DKL series, it sounds like a good idea because they are so similar, but I'm not sure because of the name difference.
 * 4) Per all.
 * 5) Mario series = Mario franchise! So, let's try it!
 * 6) Per above. Also, I want to comment that I understand the reasoning behind wanting to merge the DKC and DKL series, even though I don't like the idea. While it's true that the DKL games are in no way remakes of the DKC games, they do have the same protagonists and antagonists, which make up the main bulk of the Donkey Kong Country (series) article. If we put that info in the DKL article, which is awfully short without it, the information would be repeated.

Comments
3D Player 2010: I genuinely don't think you understand what I'm suggesting. RIGHT NOW, "the Arcade based Donkey Kong games including the Mario vs. Donkey Kong series" are "lumped" "in with the more standard Donkey Kong series". I am not suggesting getting rid of, e.g., Mario vs. Donkey Kong (series) - note the words "not deleting or merging anything" as part of the proposal. Indeed, I'm suggesting creating a page JUST for "the Arcade based Donkey Kong games" at Donkey Kong (series), which is currently the "lump everything in" page. If this passes, there will be more pages, not fewer, but with less duplication [compare Donkey Kong (series) and Donkey Kong Country (series) as they presently stand). The retooling of what was "Mario (series)" and is now Mario (franchise) did not obliterate, for instance, the list of games on Super Mario (series). - Reboot (talk) 01:22, 12 October 2016 (EDT)

@Reboot: If it is okay with you, I will get to work on changing the Yoshi series to the Yoshi franchise as soon as this proposal passes. This would include creating two pages, so I have to ask. 10:18, 17 October 2016 (EDT)
 * Okay. I want to do DK first anyway. - Reboot (talk) 17:17, 18 October 2016 (EDT)
 * Okay. I will get the first part done as soon as possible. 17:24, 18 October 2016 (EDT)

Change the rules of BJAODN
I think that we should change 5 rules of BJAODN to allow things even funnier to happen.

Proposed Rule Changes:


 * 1) 00ff00


 * 1) ff0000

The bad jokes and other deleted nonsense archive is the fun and controversy archive on the super #ff0000#00ff00 wiki. Its purpose? To have the most bad works documented. for fun!

On a more serious note, this archive was created to store vandalism and poor writing that users consider to be humorous. The archive is for anyone to edit, as long as the added content satisfies one condition: it must be funny.

Before editing, please read the following rules:


 * This is not a general vandalism archive.
 * While it is true that what may be considered "humorous" is fairly subjective, common sense should play a part here. The Mario article being replaced with something along the lines of "MARIO IS A [insert swear word here]" is not funny; it is childish and obnoxious.
 * Do not add impertinent content to the archive.
 * As stated above, information containing vandalism and poor writing is the only type of content that is acceptable to add here. Such content may include entire articles, sections of articles, or "joke" proposals, but may only be taken from valid wiki articles or Proposals. Content derived from user talk pages or any other namespace is not allowed under any circumstances and will be removed on sight.
 * Users reserve the right to remove content which they wrote.
 * The focus of this archive is to store vandalism and poorly written material deemed to be humorous. However, there is an exception: if something you wrote happens to be archived here, you have the right to remove it if you wish for it not to be there (this obviously does not apply in the case of blatant vandalism). For this reason, there should not be any edit warring between users over any specific section being removed.
 * Newbie bashing is not tolerated.
 * There is a difference between poorly written articles that new users may be susceptible to creating and something so confusing and devoid of information that you become suspicious of the writer's sanity. We accept only the latter variety in this archive. #00ff00
 * Don't write badly on purpose.
 * ff0000#00ff00 create all-new material just to add to the archives, #00ff00 don't alter existing material to "make it funnier" #00ff00, and definitely don't vandalize actual articles in order to get them into BJAODN, because you will be punished.

Here are a few tips for organizing BJAODN pages:
 * Entries should be placed in alphabetical order.
 * Entries that have obviously bogus Red Links should be replaced with the template,.
 * Commentary is permitted, but users should show restraint in this matter. Commentary should make the entries funnier, and commenting just for the sake of commenting will be removed#ff0000.
 * You don't need to ask permission to add something.

Summary of ideas:


 * The first rule change is basically fixing a typo in the page.
 * The second rule change creates an exception to a rule. I understand why that rule exists, as we are trying to not offend people, but if someone thinks that something they wrote in the past when they themselves were a newbie, deserves to be added, why not? If having it added would truly offend them, then they would not add it.  It's that simple.
 * Some people might have a desire to be creative with BJAODN entries. Currently, the rules do not allow that.  The third rule change allows users to be creative, and expands what can be added to BJAODN, which would make BJAODN even funnier.
 * Sometimes BJAODN content is written with minor errors added onto the existing nonsense. I think we should cut out the minor errors, and simply leave only the nonsense remaining.  The fourth rule change does just that, allowing users to fix spelling and wiki formatting errors in BJAODN entries, so that the entries become entirely nonsense.
 * The fifth rule change allows users to start conversations about how they feel about BJAODN entries. Having such conversations would make things funnier, by allowing users to talk about the nonsense, in addition to the nonsense already being there.

If necessary, we can implement a rule similar to the Userspace policy where excessive BJAODN editing is a warnable offense, so that people do not overdo it, or create an account just to participate.

Proposer: Deadline: October 27, 2016, 23:59 GMT

Support

 * 1) per proposal

Oppose

 * 1) My reasoning below.
 * 2) Per Glowsquid.
 * 3) Per Glow!
 * 4) Per Glowsquid.
 * 5) Having a huge all-or-nothing proposal to "fix" some of BJAODN's "flaws" is not the right way to go: for example, the first change you proposed was fixing the intentionally misspelled "mairo", so that's something I'm already against as it goes against the point of that sentence. Another thing is, we strictly forbid the creation of new content to go into this page for a reason: people will end up vandalizing pages and writing poorly on purpose just to get an entry on this page because they think they're "funny XD", as opposed to unintentionally funny content due to the result of genuine intentions but terribad bad execution. A lot of these fixes are just not suitable for proposal format, and they're better off with a regular discussion on the BJAODN's talk page. In my opinion, none of these changes would be beneficial to the BJAODN and they add several layers of unnecessary complexity to what should be an easy-to-understand thing: just take badly written stuff that made you laugh and at it on there.
 * 6) Ninja: Very bad idea. I see the BJAODN rules as is as fine. One, the misspelling of "Mario" is intentional, as inferred from the bad grammar. We also have had a proposal that wanted to allow users to write badly on purpose, which massively failed. The reasons I'm opposing are the same as that one: allowing users to intentionally create content for BJAODN defeats the entire purpose of its humor. It exists to surprise and amuse users that someone had written a part and had the poor judgement to believe that it is acceptable. This proposal promotes bad edits, which is goes against the core of what this wiki is supposed to be about. Sure, maybe some of the stuff in BJAODN are Poe's Law in action, but this proposal would just open the floodgates and, in my opinion, ruin BJAODN since the surprise is gone. There is nothing to gain from this proposal except allowing users to have a reason to write badly. Anyhow, there isn't a rule against people adding their own poor writing from years ago, as it still retains BJAODN's purpose. The conversations about BJAODN should also be short and sweet or else they'll just be a stick in the mud and weaken the effect of the entry itself. There isn't a subjective rule, but conversations go on other venues. Same thing for writing bad on purpose.
 * 7) Per all oppose.
 * 8) – Per everyone.

Comments
Arght, so:

-The typo is intentional. -If someone wants to add their own contributions to the archive, of course they can do that. It's an obvious exception that does not need to be said. -BJAODN's whole point is showcasing well-meaning errors along with the rare bit of clever vandalism. When I proposed the page in like... 2009, I think?... one of my argument is that it could even be faintly educational by showing people what not to do. Just allowing anyone to shit up the page not only defeats any pratical purpose it might have, but also open the floodgates for unfunny monkeycheese; to recycle what I said in an earlier proposal, past attempts to add original material on BJAODN were less funny than a documentary on Darfur war refugee camps. -BJAODN is meant to be an archive of crap. Allowing people to fix errors runs counter to its whole point. -Excessive conversations were agreed to be removed in forum discussions because they were unfunny and made navigation more tedious.

I do not agree with any of the changes proposed. --Glowsquid (talk) 19:36, 19 October 2016 (EDT)


 * I probably did not think through the full effect of the changes I am suggesting would entail. Under normal circumstances, I would withdraw this proposal.  However, this is not a normal circumstance.  Since so many oppose votes have already been cast, I cannot withdraw this proposal, due to rule 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."  20:17, 19 October 2016 (EDT)
 * Your quote literally has the term "talk page proposals" in it. This is not a talk page proposal. 20:18, 19 October 2016 (EDT)

Prohibit the use of, , and  other than for legibility reasons
I just got done de-ing the various Mario Party series templates (e.g. ), because the character names were picked out in "relevant" colours (e.g., Mario in red). Not only was this inconsistent with basically every other series template, but a lot of the uses were at best borderline illegible, with colours like yellow, gold and limegreen against light yellow. This isn't the only example of colours like those being used across MarioWiki, and it's always random and frequently hard-to-read. Not to mention that picking out a in red breaks one of the most basic wiki precepts, since "redlinks" are empty/uncreated pages.

So I'm suggesting that it's just stopped. The only valid use of these templates should be where the default text colour would be hard (or impossible) to read against a background - e.g., the SMM3DS link in the footer of against the dark red, the external links in the right column of List of official Super Mario Maker courses against the SMB sky blue (since it was decided that would be the best colour to put the costume sprites against on Costume Mario) or a couple of the rows in the table on Crystal Stars. No "...while limegreen jumps higher..." stuff any more.

EDIT: This will not apply to or  pages (including non-mainspace talk).

EDIT2: Okay, I think some further clarification is needed - I'm not suggesting removing all coloured text or backgrounds from the wiki as certain users seem to think. What I *am* saying is that links or text should not be coloured using these templates in Skittles-like fashion. It looks unprofessional, removes a degree of Wiki functionality, is frequently near-illegible and could cause further legibility problems if a "dark mode" is ever created (as is occasionally requested), whereupon the legibility problem would flip for those users such that dark colours specified in ordinary text with these templates would be illegible to them. They're a blunt instrument that isn't particularly well-suited to anything except colouring text in tables, navboxes and infoboxes - and in the latter cases, the colours should probably be specified with CSS site-wide rather than template-by-template (in the same way they already are to some extent for navigation templates), and in the former case they should be primarily specified alongside the table background (and if there's no background specified, that's bad for the same reason it's bad in text).

Proposer: Deadline: November 1, 2016 23:59 GMT

Support

 * 1) Per me.

Oppose

 * 1) This proposal, as it is worded, will apply to more than just template and mainspace articles, but also to userpages, signatures, and not just arbitrary uses, but also to lists where coloring is used to signify categories of some kind, for example.  This proposal is simply way too broad in application by word of suggestion, that I cannot support it.
 * 2) {A Toad says, “Hey! Mario ! Hurry! Hurry!” Mario jumps into the castle then says Luigi out loud. Luigi walks into the castle finishing getting ready. A Toad says, “It’s a meeting! Big meeting! You’ve gotta hurry, please! Everyone’s wating, Mario! In the conference hall ! …Oh. Luigi came too. Super...."} Bowser's Inside Story with commentary from me. If games do this, why does this wiki don't do this? Makes no sense to me. Oppose.
 * 3) Per Yoshi the SSM.
 * 4) Coloring should not be used in navigation templates or sentences like the proposal's example about Luigi jumping. However, it should be used in situations like the two examples Megadardery put below. This proposal is too general for me to support for the reasons in  the first two sentences.
 * 5) Per all.
 * 6) I like some of the ideas here, such as banning color-link text in character sections in the Mario Party templates (which you already took care of before you started this proposal), but I don't think proposals are the best idea to handle misuse of colored text. It's better if we go along by case-by-case basis. I'd like to point out that yes, we always strive to be legible in the first place, so saying we can't use colored text except for legibility reasons is a bit redundant with already what we want to do and thus that part doesn't really need to be proposed. I'd also like to per Bazooka Mario's comment as well.
 * 7) Per Luigi 64DD and Baby Luigi. 3D Player 2010 misses the point and I've argued against Yoshi the Space Station Manager's position on color text, that the colors serve purely a gameplay purpose (which is highlighting / emphasis for the player) that doesn't translate well to the wiki (make it look garish and distracting). If emphasis for the readers' curiosities is so important, then just make them regular links, which can also be piped for clarification (e.g. It ate that fat man!). I also believe legibility is already something we do. The policy on navigation templates already assumes the navigation templates use plain blue links so there's that. I do support removing the color links on Mario Party navigational templates, Mario Kart character galleries, adjusting color links in 3D World's character gallery to make them black, and removing color links on Mario Party character galleries (while restructuring their table to be color-coded so we keep how the games color-code their characters, but not on minigame list articles or on quotes where colors serve a meaningful purpose like Fawful's battle quotes rather than simply highlighting important information.
 * 8) I'll give a per all.

Comments
Regardless of the side implications that this proposal may include, it seems that it is just a shot in the foot. Although I might agree on that some applications of the colors are terrible, others are pleasant, because the characters were depicted with these colors in-game. There is absolutely no need to outright ban them.-- 18:21, 25 October 2016 (EDT)
 * And yet, in your "pleasant" example, "Princess Daisy" is only barely legible. I very much doubt a light-orange/yellow on white is in the game. - Reboot (talk) 18:35, 25 October 2016 (EDT)


 * To be honest, I think the colors on Mario Kart 64 are fine, because they are used to present information categories that, in my opinion, could not be presented any better than the way it is now. 18:31, 25 October 2016 (EDT)
 * Like the vast majority of examples. With a background colour, or with text. Which wouldn't invoke red/green colourblindness problems. (I have, however, clarified above regarding User & Talk pages, since it wasn't my intent to change anything regarding those). - Reboot (talk) 18:35, 25 October 2016 (EDT)

@Yoshi the Space Station Manager: So, what about the redlink problem? And are you planning to go through the whole wiki and colour every "Mario" red? - Reboot (talk) 18:40, 25 October 2016 (EDT)
 * No, I am not going to change every instance of Mario to red. The redlink problem you're talking about; Maintenance has a place to find redlinks. There is also a problem with your plan. I was looking at a userbox colored black. If it didn't have white words, one would have to highlight it to read it. Probably very limited that there is black places (more than just userboxes), but I want you to be aware of this. 18:49, 25 October 2016 (EDT)
 * And the vast majority of users will never look at Special:Wantedpages. But they will read articles, and if they see a red link, if they're at all familiar with Wikipedia, MarioWiki, etc they'll realise it's a "dead" link and possibly be tempted to fill it out if they're familiar with the topic. The more links that don't follow the standard colour coding, the less chance that has of happening. It actively harms the wiki. - Reboot (talk) 19:27, 25 October 2016 (EDT)
 * I find it interesting that you don't like red links, yet you have red links all over the place. A simple fix would be to create a userpage for your red links that you have. Any reason why you haven't created a userpage? 20:28, 25 October 2016 (EDT)
 * I don't see the need for one. My userspace isn't in the encyclopaedic portion of MW, and I'd rather not waste the site's bandwidth & CPU with a bunch of userboxes that serve no purpose. - Reboot (talk) 20:31, 25 October 2016 (EDT)
 * I doesn't have to be very long. Look at Steve's. 20:34, 25 October 2016 (EDT)


 * @YTSSM: Reboot clarified above that he didn't intend this proposal to cascade onto userspace pages, so userboxes aren't an issue to be concerned about here. – YoshiKong (talk) 18:54, 25 October 2016 (EDT)
 * @YoshiKong: I said after that more than just userboxes. 19:04, 25 October 2016 (EDT)
 * ...do you know what "for legibility reasons" means? If you don't, you should withdraw your vote. - Reboot (talk) 19:27, 25 October 2016 (EDT)


 * @Reboot: There is another problem which new users will have. New users don't know how to color code yet, so they will be putting down blue links instead of black links. As a matter of fact, I learned how to color code when I wrote my oppose vote. 19:20, 25 October 2016 (EDT)
 * And they SHOULD be putting down blue links! That is, as they say, not a bug but a feature. - Reboot (talk) 19:27, 25 October 2016 (EDT)
 * Let me quote you: "the external links in the right column of List of official Super Mario Maker courses against the SMB sky blue (since it was decided that would be the best colour to put the costume sprites against on Costume Mario)". You intend to make them a different color. That would mean that you want all links to be the same. At least, that is what is implied. The most obvious choice of color would be black since it is the default color of regular text. 19:33, 25 October 2016 (EDT)
 * Actually, that relates (1) to external links, since the external link colour is very nearly the same colour as the background there, so the redlink thing doesn't apply and (2) easily falls under "for legibility reasons" in the same way that text on a black background should not be black. - Reboot (talk) 19:59, 25 October 2016 (EDT)

The Mario Party 3 example looks mostly fine to me, and frankly, Princess Daisy was only made a little harder to read. But if there is a color coding that makes it incredibly hard to read, it should be removed. I disapprove of YSSM's idea because, while it may be good for in game text, it's not good for Mario Wiki's encyclopedic appearance. Lastly, I think color coding should be removed from navigation templates and generally from paragraphs in articles, but situations like the MP3 example are fine. -- 18:58, 25 October 2016 (EDT)
 * @Luigi 64DD: I did not suggest that we should change the coding one bit. Here for clarification for others too. 19:04, 25 October 2016 (EDT)
 * @YSSM I think you misunderstood me. I'm not talking about coding. I'm talking about this: "In Luigi's Mansion, Mario 's Cap is one of the five items that Mario lost, and Luigi must bring it to Madame Clairvoya to receive information regarding Mario 's whereabouts." That example is from Mario's Cap article. I added colors to it to demonstrate. If that is what you are saying, then I disagree with it. -- 19:10, 25 October 2016 (EDT)
 * @Luigi 64DD: Like I said, I don't plan on changing every instance of Mario to red. For starters, that will be ridicules. Secondly, that is not what I suggested (as you can see Mario and Luigi not having color all the time in the passage). 19:15, 25 October 2016 (EDT)
 * Then what are you suggesting? Having coloring for quotes that had coloring in the games? -- 19:18, 25 October 2016 (EDT)
 * To keep color coding how it is. Not to go around every article and change every color code to black. Direct quotes don't have to be color coded as the text in game. 19:21, 25 October 2016 (EDT)
 * There are very few at the moment. Partly because most of them have been killed over time. Hence why stamping it out entirely is an option. - Reboot (talk) 19:27, 25 October 2016 (EDT)
 * @YSSM Oh...The quote you put is misleading, because coloring is not used in sentences on this wiki. The quote made me think you were suggesting doing that. That's also why Reboot thought you wanted to change every instance of Mario to red before you clarified. -- 19:31, 25 October 2016 (EDT)

Bottom line is: I can't support this since the implied statements. And now that I started using color coding, I don't think that a hard time reading may be a bad idea. Except in cases where it is impossible. Do that (and not near impossible), and I might accept. Also, don't have any implied statements. 19:39, 25 October 2016 (EDT) Actually, I don't think it should happen because I like it how some things are colored. I not going to support something that will get rid of it even at a small level. It will lead to many things. 19:47, 25 October 2016 (EDT)

Concerning EDIT2: Seeing as the examples that I do not think the color should be removed in use the templates, I am not changing my vote.-- 20:08, 25 October 2016 (EDT)

While I do agree that anyone who ever coded in css yellow text against the white wiki background should be shot, I also believe that parts of this proposal isn't needed and writing a proposal to end the trend of specific cases here and there isn't wieldly, especially when all the formatting you suggested should already be inline with the common rules of color theory and design and it's simply because people who edit this wiki either didn't caught up with color design, were ignorant of it, or just didn't care about it. Your "legibility" reasons, it's incredibly broad and vague. Define what it means. Does it mean a certain degree of readability, or does it mean passing the contrast test? To me, deep gold on yellow isn't that illegible, and it's easily fixable to by using an even deeper orange or a darker yellow, something that is compromisable. I don't think the colors should be used in navtemplates (like entries such as "Mario" and whatever), but I do believe they should be kept on the Mario Party character gallery pages, as well as the color formatting used in the Mario Kart 8 article. I'd also argue for some cases of using red-text: in Mario's case, where red text is most commonly used, of course people would know Mario's page is already created, and while people on mobile suffer from this as they can't hover over the link, if you hover over a dead link, it links to something different than a real link, which is how I even learned red links are dead in the first place.

ie I think this is a complex problem that a proposal itself isn't the best tool for deciding on an entirely black or white basis. I feel like more discussion should have been made before you jumped to making a proposal abolishing this and that color links which have their uses, especially when used to highlight differences between such and such so people can more easily identify what is what. 21:35, 25 October 2016 (EDT)

I don't support the blanket thrust this proposal has (mainly because it may have unforeseen effects), but I'm for limiting color use a bit. I don't think there's really a need to give those links a different color, but this proposal's provisions can cover aspects not intended (would List of Mario Party 5 minigames be affected?). Anyhow, copying game text detail-by-detail which includes the colors such as in Yoshi the Space Station Manager's example or in areas like Speak Up bonus panels text doesn't translate well at all since they're two very different media. The game needs to highlight such text for purely gameplay reasons, to highlight important information for the player. For an example, check this revision in WiKirby. This text is colored exactly how it appears in game, but this is garish in the wiki and greatly hinders legibility. On the other hand, it might be helpful to color some quotes by, say, Fawful to fully understand the context. Some words he says are either red or green. For example, "You have readiness for red" If these words don't have a random color (such as THIS always being red), then it would make sense to give those words a color. Finally, I don't find color text too harmful on the eyes, though gold-yellow and light gray contrast very poorly with white. While Mario Party and Super Mario 3D World somewhat has some reason for its colors, since those colors are assigned and used, there is little reason we should give color links to characters in Mario Kart games. However, those color links aren't even necessary or even good in the 3D World example I gave because the contrast is very poor and we already have color codes in the form of background color. I think in the end, we'll have to decide a case-by-case rather than impose a blanket removal. In the end, I do support removing some color links and probably just replacing them with something more appropriate like a table with color-coded pastel backgrounds when possible. That means rearranging the character lists in the Mario Party articles (the one provided can be easily changed into a colorful table while we nix the color links or at least adjust them to make them legible in the color table), removing the character-specific color links in the navigation template, removing most color links in flavor text, and keeping the color links that do serve a purpose (such as in List of Mario Party 5 minigames and potentially in Fawful quotes and other quotes that use colors for context reasons) intact. 21:44, 25 October 2016 (EDT)
 * I'd also say that sometimes you need to use color links in the case of tables but again, it's supposed to be part of the "legibility" part of the proposal which is so broadly and vaguely defined that I feel like it was slapped in as a side-note merely to address comments that may bring it up as a legit criticism of this proposal rather than specify what will be done about them. Which all turns around to my case-by-case argument again. 22:03, 25 October 2016 (EDT)

Allow .APNGs and create a notice template related to them
'''This proposal will not replace the .gif format as the preferred animated format. Instead, it will allow .apngs only in cases where there is a clear benefit to using them.'''

This proposal will overturn this one and will likely reinstate this proposal that attempted to create a notice for APNG images.

We briefly had some .apngs running around in this wiki, though we have disallowed them mainly because of lack of universal browser support (notably, in Chrome).

The current animated format we use and prefer, .gif, however, is highly flawed. Not to mention, it's very outdated. This is because it supports only 256 different colors, making the images indexed, which isn't really much of an issue because most sprites are below this format. It also does not allow semi-transparent values, thus making it "all-or-nothing". It also usually isn't a problem, but recently, we have several images that use semi-transparent values, but are forced into a .gif format, thus greatly reducing the quality of these images. It also forces the transparency to look horrible and resemble a poorly-cropped image that goes against our own policy on transparent images. Arguably, this forced change also goes against our aim to give game-accurate impressions.

APNGs are intended to be a replacement for the outdated .gif images, but again, its biggest issue is that it lacks universal browser support, as in the comments before. Otherwise, for any other browser that doesn't support APNG I don't think we should have to bend backwards to stick to a superseded format. Still, there is a sizeable amount of browsers that don't support .apngs, and it has been shown to me that a majority of users here are Chrome, so we should not go full-on transition to .apng. Additionally, thumbnails cannot be rendered as animated when they're .apng images due to technical limitations, so they may not be immediately apparent since many images are used as thumbnails.

If this proposal passes, we'll have to create a notice template as in this proposal (see comments section). I also don't think we should get out of our way to convert every single .gif to .apng either, but we have to, at the minimum, allow .apngs. We might have gotten away with .gifs due to the simplicity of most sprites, but we have some recent games that use sprites that don't transition well into .gif at all, which includes Wario Land: Shake It! and Paper Mario: Color Splash and we have some miscellaneous animated images as shown here that would benefit from staying as an .apng rather than a .gif.

In brief:


 * This proposal allows .apngs because of transparency and indexing issues with .gif. .gif is an outdated format, and it shows.
 * A template on apngs will be created to warn users that use browsers without .apng support.
 * This proposal does not intend that .gifs must be replaced with .apngs. In fact, most .gifs should remain the as is. We use .apngs only when they have a clear advantage, which is accurately preserving colors and transparency values.

Proposer: Deadline: November 25, 2016, 23:59 GMT

Support

 * 1) Per proposal
 * 2) – If Porple is willing, this has my support.
 * 3) The palette of the GIF format was a bit worrying, as I had noticed that some colors were indeed being replaced by different ones. Since I like to have images as faithful to the original ones as possible within the upload limits, definitely supporting this proposal!
 * 4) I support. Per all
 * 5) Per all, especially Shokora.
 * 6) I don't even know what APNG is, or whether my browser can run it, but why not? It sounds useful. Get with the times, Mario Wiki!
 * 7) I support allowing APNG, but gifs should remain the preferred format because of it's universal support across all devices and browsers and image editing programs.
 * 1) I support allowing APNG, but gifs should remain the preferred format because of it's universal support across all devices and browsers and image editing programs.

Comments
Actually, if APNG images saved as .png files are used instead, the browsers that don't support APNG images can still show the first frame. Should we recommend APNG images in .png files instead?--Mister Wu (talk) 20:53, 18 November 2016 (EST)
 * I don't think that would be necessary. We should be using .apng only when it is absolutely needed, like those Color Splash sprite animations. 22:36, 18 November 2016 (EST)

By the way, would it be affordable to use javascripts that display APNGs on browsers with HTML5 canvas support? Just an afterthought, though... -- 23:24, 18 November 2016 (EST)
 * That'll be something to ask Steve, and that's assuming he's on board with this (I hope he is). 23:35, 18 November 2016 (EST)

Though I support uploading APNGs, each should have a gif version uploaded as well. Even though it's supported by Firefox, Safari, and soon Chrome, there are far more browsers that don't support it. Gif, while not as great, is supported across all devices and browsers, as well as being easy to make. In most cases the low quality doesn't matter. I've been uploading a fair amount of the color splash gifs lately, along with Mister Wu. For their purposes to show the enemy idle animations, the gifs do just fine. But, I agree that it would be great to save the animation from the wiki to the desktop and keep its full quality from the sprite sheet. In such case, we could add a link on the gif file pages that can take you to the APNG version. I use Microsoft Edge on my laptop, and Dolphin on my phone, and neither of those support APNG to my knowledge.-- 00:00, 19 November 2016 (EST)
 * The Paper Mario Color Splash idle animations are the primary reasons for this proposal. The .gifs aren't fine to me because they index the transparency so the image looks very bad when placed against a background. Yeah, I don't think either Edge or Dolphin support apngs but most major browsers do, so I think we should settle on a compromise. .gifs should still be the most common format but where .apng is clearly better, it should be used. 00:07, 19 November 2016 (EST)

53% of our visitors use Chrome. Just because there is a bug report for APNG support in Chrome (as there has always been) doesn't mean they have any intention of actually including it. So you can think of this proposal as asking, "Should we break animated images for the majority of our visitors?" Even if Google comes out and says they will support it, I wouldn't do anything until we can actually see it in action on both desktop and mobile. -- 01:02, 19 November 2016 (EST)
 * Okey, good point. I've reworded the proposal to not replace .gif as the preferred format, but merely to allow animated .pngs in cases where preserving transparency and colors is a big benefit. 01:09, 19 November 2016 (EST)
 * After adding-in IE, Edge, and some miscellaneous browsers that don't support APNG, the image animations wouldn't work for about 60% of visitors. I understand your concerns about image quality, but is it really worth breaking the animation for 60% of people so that 40% can see it in higher-quality? Mainspace articles should work the same for nearly everyone. It's a whole different story if Chrome starts supporting it, but we would have to wait for that to happen first. -- 01:34, 19 November 2016 (EST)
 * Hm, probably not. I would almost recommend making .apngs separate, which would work fairly well for the animated sticker images, but I realized that'll mean reuploading all those Color Splash enemies as .apngs as well AND providing .gifs and static .pngs to boot. Not a pretty picture. Anyhow, probably withdraw the proposal. Thanks, Google. 01:51, 19 November 2016 (EST)
 * My Browser doesn't support OGGs on this wiki. If I can handle that (even though I will never use it), then I can handle not being able to see APNGs. But I do agree that GIFs and APNGs have links to each other. 01:53, 19 November 2016 (EST)
 * .oggs aren't as widespread as images though, so I think that's something we can conveniently ignore. 01:56, 19 November 2016 (EST)
 * That's why I said it depends on Chrome. Edge is such a small percentage that we wouldn't wait for their support. -- 02:00, 19 November 2016 (EST)

I would like to say that I use Microsoft Edge. Also, Paint Guy Idle Animation has a very small but noticeable bad look. It only comes when I look at it very carefully. But after seeing the flaw, I think that this flaw should not exist even if it isn't noticeable. One thing I don't really understand is why browsers don't support APNGs, but support PNGs. 01:15, 19 November 2016 (EST)
 * The Paint Guy idle is only meant to be temporary. I knew it was bad when I made it, but I had no other options. 01:25, 19 November 2016 (EST)

Clarify the Wiki's policy on APNG images in .png files
At the time of the initial deadline, the proposal should have in fact passed when following a pending change to rule 9. The admins are currently working on updating the rule, and are withdrawing this proposal with a "no change" enforcement in order to avoid confusion once the rule is updated later this week. Asides from this, the wiki's proprietor doesn't wish to change any policies or regulations about animated PNG images, until it gains more support across different browsers and devices. The replacement of .gif files with .apng files is not yet viable due to the lack of support on the browsers that have the majority of market share. There is however, a second case which is similar but also importantly different: that of APNG images in .png files. The first frame of this kind of images is shown by all browsers that support PNG images but not APNG images. In fact,, the Wiki infrastructure already supports them as well, to the point that the details about the animation are shown next to the image name, and there is even a warning message about the automatically generated thumbnails not being animated. The current image use policies don't forbid them either, the only way to know that they are not recommended is seeing an old proposal.

At this point, I think a final clarification on this special kind of images should be done, and since it is impossible for them to be used for all kinds of animation, I see two possible policies, beside that of not changing anything:

TOLERANCE

The APNG images in .png files should be tolerated in special cases where the first frame is already informative enough, while not being mentioned in the policies in order to avoid suggesting their use; for example, a rescaled (250px of width) version of my example image might seem viable for infoboxes (please note that it won't be actually used as such, it's just an example image!), as the first frame is already informative enough, while the animation is a welcome plus. Note that this scenario does not enforce modifying the current infrastructure to generate animated thumbnails; while this would be a welcome feature, ultimately an user using this kind of images should also take on themselves the burden of uploading and using versions of said images with appropriate width and height on the Wiki, with due notices when this needs to happen and it's not happening.

COMPLETE AVOIDANCE

The current image use policies should be updated to explicitly forbid the use of APNG images in .png files, automated measures to issue warnings on APNG images on .png files might be done as well, but they are not part of this choice, since the Wiki staff should be able to handle the few cases in which these images are uploaded already well.

Proposer: Deadline: November 26, 2016 December 3, 2016, 23:59 GMT

Tolerance

 * 1) I still think that, while they cannot fully replace GIF images and they cannot even be suggested as viable format for animated images, the APNG images on .png files can be useful in cases like the one I mentioned.
 * 2) For me, a static picture on my end would be better than a bad looking picture. And when the day comes that Google does support APNGs, APNGs will become more popular. Especially since GIFs are outdated a bit. I support APNGs in PNGs.
 * 3) I've been supportive in the past of APNG's that enhance the visual experience without being required, per that. Also see my comment below.

Complete avoidance

 * 1) See my comments below.

Not changing anything

 * 1) See my comments below.
 * 2) - Per Wildgoosespeeder and because I don't want any last-minute votes in favor deciding something as important.
 * 3) Per all. I didn't realize I hadn't voted yet.
 * 4) Per all.
 * 5) I think it's better to abstain until Chrome officially has APNG, which we hope won't be far away. Until then, we should just continue as we should.

Comments
Quoting myself from here: "There is no such thing as a .apng file, in the same fashion as there isn't a .agif file. The extension is always .png, animated or not." Be mindful of this. Bulbapedia is a good example of good use. A lot, if not most sprites are APNG's over there. They don't appear to have any form of policy that I could find on it though, everyone just seems to go with it and tag them with a template. 15:03, 19 November 2016 (EST)
 * Should we then create a template that highlights the nature of the APNG? The bold warning below the text may not be immediately apparent. 19:26, 19 November 2016 (EST)
 * A template more or less is a must-have to avoid people replacing them with static images. Here's an example of usage. To illustrate the effect, two animated sprites are used in the template, with the warning not to replace the image if neither sprite moves. Images are also categorised. We should have a similar template to warn users to not upload static images (minus the first frame thing, as that isn't always the case). 04:04, 20 November 2016 (EST)
 * On a side note, the bold message is from MediaWiki:File-no-thumb-animation or MediaWiki:File-no-thumb-animation-png. These can be customized to be more prominent or suppressed in favor of a template notice. -- 08:53, 20 November 2016 (EST)
 * Thanks, though those pages are for the Wiki's main language (US English) only and won't affect users with a different display language. 16:43, 20 November 2016 (EST)

Although the quality is nice and can completely replace GIF, APNG is not a mainstream format nor is it an official format like GIF is. Internet Explorer doesn't support it and Google Chrome requires a plug-in. Also PNG Monstrous doesn't play nice with it because it removes metadata, and I think APNG's frames are metadata to the PNG format. Also what are some programs that could be used to create these APNGs? It would be much better to distinguish APNG with PNG by extension instead of a template. I think that MediaWiki can support the extension, judging by Special:MediaStatistics. MNG is being developed by the same group as PNG so there will be a distinction unlike PNG and APNG, but no MediaWiki support yet. -- 04:49, 20 November 2016 (EST)
 * MNG has already been released, but no browser development team wants to support it (Mozilla dropped support in its browsers in 2003); currently it's impossible to upload .apng images on this wiki (I tested this personally); the program you can use to create those APNG images are GIMP (I personally used it to create my example image) and VirtualDub (which I used to create this image); finally you're right, the other frames are in the ancillary chunks, meaning you should not use optimizers that get rid of ancillary chunks in these kinds of images (you should never get rid of ancillary chunks, by the way, as there are also those about gamma (gAMA chunk) and color space (cHRM, iCCP and sRGB), so you should seriously reconsider the use of these kinds of optimizations).--Mister Wu (talk) 06:26, 20 November 2016 (EST)


 * There is no reason to go about MNG as absolutely no support exists for it whatsoever, which isn't the case with APNG. Secondly, PNG is build around chunks, of which Mister Wu named a few. Some are indeed metadata, no problem (some of which you shouldn't delete, like author and copyright comments), others are used for the right display, gamma and animation chunks being examples. Optimisers just need to support these chucks in order to be viable, either be optimising them or ignoring them. The way PNG is build up makes the metadata-ness of a chunk up to what it does, not it's build. Another editor to add to Mr. Wu's list is RealWorld Paint, and there are some programs you can feed separate PNG's and frame durations. 06:42, 20 November 2016 (EST)
 * This brings up an interesting question about how to optimize APNGs. Just like Photoshop, GIMP doesn't optimize its output if saved in the PNG format. PNG was never designed to be animated because the group thought that it would be dumb to add confusion to the format. Are there any programs that just "stitch together" PNGs to be outputted as APNG (no loading of the image to just be resaved and undo optimizations)? That's the only way I see optimization happen with APNGs. --!
 * I think this is outside the scope of the proposal, but I believe that most outputters will only save the changed region of the image as a frame, i.e. if only a small region changes, only that region is saved. This is according to standard and is good practice anyway. A frame is saved in the exact same format as a normal PNG image (though all frames must use the same format), just named differently. You can choose to replace the entire aforementioned region, or paint over it, the latter being a good thing if the region doesn't change much, but does contain a lot of detail. Enough optimisation opportunities. 16:43, 20 November 2016 (EST)
 * THe APNG specification allows to code differences from previous frames using the Alpha channel, indeed, when adding the Alpha Channel in VirtualDub I obtained smaller file sizes in two cases I tested, in the case of my aforementioned example, without Alpha Channel the size is 224 MB, with Alpha Channel the size is 135 MB, so there are indeed many possible ways to optimize the output files; some of which are apparently already in use by current software.--Mister Wu (talk) 17:14, 20 November 2016 (EST)

Here's a different question; do APNGs work in iOS or Android? Also since the whole file is downloaded and nothing gets animated if it isn't supported, this could be really be detrimental to people with slow or metered connections. I'm pretty sure that GIF is massively supported and preferred in these cases. -- 18:24, 20 November 2016 (EST)
 * They work in iOS, and are even used and recommended for iMessage. They will likely be supported in Android as soon as Google Chrome supports them (this might happen earlier than expected, as development should start in Q4 of this year according to the Google Chrome staff). Regarding the concern of data use, my example, despite being formed by 7 frames at 786 × 890 resolution at 32 bits per pixel (8 bits per color channel + 8 bits Alpha channel), is still a 686 KB file, while the GIF is a 345 KB file despite being palettized; since there is a 10MB upload limit on the Wiki and due to the nature of the proposal, the APNG images would be used mostly for in-game data, which is easily compressible with the PNG format.--Mister Wu (talk) 19:03, 20 November 2016 (EST)
 * For the sake of correctness, neither of the images were optimized; using GIMP's "Optimize (for GIF)" command I could reduce the file size of the GIF file to 201 kB, while the APNG image, optimized with APNG Optimizer 1.4 and 15 iterations of Zopfli, has now a size of 276 kB; I could verify that in the latter case the optimizations didn't change the images using APNG Disassembler 2.8 on both the original and optimized version and comparing the individual frames with WinMerge 2.14, showing that indeed there were no changes in each of the frames. I'm sorry for having reported data about unoptimized images, hopefully this wasn't relevant for the votes.--Mister Wu (talk) 21:59, 27 November 2016 (EST)

The deadline in this proposal was not supposed to be extended; the not changing anything option won. 19:18, 26 November 2016 (EST)
 * Current rule 9 still is 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 all votes cast must be for a single option, rather than one option simply having more votes than the other options., though. At this point, we need a clarification from the staff.--Mister Wu (talk) 19:27, 26 November 2016 (EST)
 * There are eight total votes, four cast for "not changing anything". That's not more than half, five votes would have been needed. -- 20:50, 26 November 2016 (EST)
 * Thanks for the clarification!--Mister Wu (talk) 21:15, 26 November 2016 (EST)
 * No problem :) -- 11:28, 27 November 2016 (EST)
 * But you misunderstood the proposal I linked to. There are 7 voters; as 1 voter picked multiple options. Because of that proposal; that is what counts, not the fact that there are 8 votes. There are 4 votes for the not changing anything option. That is a majority of voters (4 to 3); just as was decided to be necessary by the linked proposal.  11:37, 27 November 2016 (EST)
 * The archives say that even though that proposal passed, the change hasn't been made yet. For some reason. SmokedChili (Talk) (Thoughts) 11:56, 27 November 2016 (EST)
 * We are currently reviewing this case and I'll get back to you. -- 11:57, 27 November 2016 (EST)

Redesign the Bestiaries
Following a proposal from January to redesign the RPG infoboxes and bestiaries, I propose a new way to handle bestiaries and RPG infoboxes from now on.
 * 1) All bestiaries will use templates rather than tables. ( look here ) - This gives a more appealing look, like an ID card, and makes it easier to fill out future bestiaries.
 * 2) Each template will be based on the respective RPG infobox - Doing this keeps the enemy stats consistent between the bestiary and infobox.
 * 3) All RPG infoboxes will use transclusion to display stats directly from the bestiary. ( look here ) - This makes distributing the infoboxes to each page easier, and ensures the infoboxes will ALWAYS have the exact same stats as the bestiary.

Now here is the code to display the Super Mario RPG bestiary template:

Proposer: Deadline: November 29, 2016, 23:59 GMT

Support

 * 1) per my proposal
 * 2) Looks good to me! It looks like a lot of effort was put into it.
 * 3) Per Eldritchdraaks. It would be a lot of work to implement this idea, but a lot easier in the long run.
 * 4) Per Eldritchdraaks.
 * 5) – Per proposal, this is very logical.
 * 6) Per all.
 * 7) This really seems to simplify the editing work and to avoid inconsistencies between bestiaries and infoboxes, so I support the idea!
 * 8) Per all.
 * 9)  Per all.
 * 10) It is about time I supported. I am not going to wait any longer. I didn't want to discourage other people from going first. Anyways, one of the reason why the Once and only once policy was enforced was because of the need to keep everything updated and editors may not get to all versions. This new proposal will transfer all information and even if it does break the Once and only once policy (which will most likely not happen due to the information needing to be both on the bestiary and the enemy which is part of the bestiary), it will not break the reason why it was enforced because if the bestiary is updated, the other places will automatically update and the editor won't have to worry about the other versions. And sorry if this is quite long, but I needed to say something about it kind of helping out the Once and only once policy.
 * 11) Per all.
 * 12) Have my support.
 * 13) Per all.
 * 14) Per all.
 * 15) Per all, this is a great idea! Each game should have it's own template to transclude from as needed. I have a few further maintenance ideas that I will work on though.
 * 16) Per all.
 * 17) Per proposal

Comments
Do the color-scheme you use for the templates here will be implement if your proposal passed? Walkazo's RPG infoboxes use the same colour-scheme as navigation templates for consistency, neatness and easy readability and in my opinion those color-scheme are better.-- 12:30, 22 November 2016 (EST)
 * The colors I used are not set in stone. I used the header color from the tables in each bestiary. The color-scheme will not be the same as the navigation templates, rather they will be different for each game.-- 12:45, 22 November 2016 (EST)

It looks like you thought everything through, but do we have to use your name to use the template? That seems a little inconvenient. And I agree with Ultimate Mr. L up there; it would take a while to implement them. 12:49, 22 November 2016 (EST)
 * No, you won't, don't worry. That is just temporary. That links to the bestiary page for that game, which right now is my userspace.-- 13:00, 22 November 2016 (EST)

This idea is fantastic, the template will indeed ensure that any stat corrections on the bestiary will automatically be corrected on the transcluded articles as well. I do have a question first: do you intend to only apply this to specific character bestiary pages, such as "List of Goomba profiles and statistics"? Or is there the potential to extend this to game bestiaries as well, such as "Mario & Luigi: Paper Jam bestiary"? 18:02, 22 November 2016 (EST)
 * Everything you just said is exactly what I am proposing. This applies to all.-- 18:26, 22 November 2016 (EST)


 * Great, definitely supporting. I asked because I wasn't positive that it was taken into account with the single example that you gave. 19:25, 22 November 2016 (EST)
 * I didn't give just a single example. I provided two links above to show the templates in use, and to show the stats transcluded to the infobox.-- 19:31, 22 November 2016 (EST)

Having all the data in one place is definitely good yet there remain small tables like Mario & Luigi: Partners in Time § Enemies. Any idea to make them in sync too? -- 04:46, 25 November 2016 (EST)
 * Those would likely be replaced with enemy boxes. -- 12:05, 25 November 2016 (EST)
 * And become a duplication of the bestiary? I'd like there to be another template (in addition to and ) that extracts the HP, EXP, coin and location and put them into the original tables, because they looks so nice, and the misc stats will be too cumbersome when folded into cards. This also makes a sortable version of the bestiary available. -- 03:09, 26 November 2016 (EST)
 * It just seems unnecessary. Actually, it should probably be removed due to the "Once and Only Once policy". Your idea for a second template like the bestiary template doesn't make sense. That template creates a nice display on the bestiary page, it doesn't affect the enemy box at all. I get what you're going for though, but I can't setup another template like you want without breaking the first the system. Still the table there should probably go, even if my proposal doesn't pass.-- 03:30, 26 November 2016 (EST)
 * If we're to remove the tables under Mario & Luigi: Partners in Time, what should go there then? -- 03:40, 26 November 2016 (EST)
 * See Paper Mario: Color Splash-- 04:22, 26 November 2016 (EST)
 * Worse comes to worse, if some people can't be bothered to look at previous edits of a bestiary's history when as a sortable table -- and believe me, there are folks out there that would still prefer to sort through enemies' stats, and that was my intention when making most of the bestiaries anyway -- then I suppose having an external link to such a version would be alright? --
 * Actually, using the history isn't that bad of an idea. PM, PMTTYD, and PMCS could be replaced with a sortable table, then we could revert that edit and place a link to it on the current page. But I still think having a second table like that on the main article would be against the "Once and Only Once" policy. It has to be directly transcluded from the bestiary, and we can't do that from template to table, or vice versa.-- 12:48, 26 November 2016 (EST)
 * It's possible with  and then  . Another approach is to implement an ad-hoc  ment that output code for a table row, besides ,   and   that output infoboxes. Haven't tried either approach, though. -- 00:06, 27 November 2016 (EST)
 * Actually, I think it would be best to do it just like Paper Mario: The Thousand-Year Door. Here, only the bosses of the game are listed, and the bestiary is linked just above it. The formatting is decent, and the same thing is done for Super Paper Mario and Paper Mario: Sticker Star. After looking over the articles for the Mario & Luigi games, there really is a lot of content that doesn't need to be on the main article, especially the enemy tables.-- 06:14, 27 November 2016 (EST)

GIF vs. PNG Sprites: What to Keep/Delete
A redesign of bestiaries passed and an unforeseen consequence of that is some GIFs that were in use got placed in Special:UnusedFiles (might see them elsewhere because this page is using them). Further concerns were added once approved the deletions. There are some of those kinds of files pending deletion right now (some images that are currently there don't count for this proposal because they are either replacements or duplicate images). I was just cleaning up files leftover from the change and had some concerns with my  tagging. I find it redundant to have both a static PNG and animated GIF of the same enemy uploaded for the bestiary enemies. You can see my arguments here. Let's settle this by choosing what should be done about these for future uploads. My votes below explain how each option works.

Proposer: Deadline: December 18, 2016, 23:59 GMT

Prefer PNG and Delete GIF Versions

 * 1) My preferred choice. Not every static sprite had an animation counterpart (as far as I could tell).
 * 2) Per Wildgoosespeeder, though I wouldn't mind the animated GIFs being placed elsewhere, like in galleries of the respective game or character.

Prefer GIF and Delete PNG Versions

 * 1) If we must use GIF, get rid of the PNGs because it's just redundant to have it when the GIF animation contains the static PNG frame. If no GIF animation exists, keep using PNG until a GIF version is uploaded. Currently deleted GIFs will be restored and have their PNG versions deleted.

Keep Both

 * 1) - I want to use the static PNGs on the bestiary, and the dynamic gifs in the enemyboxes, via transclusion. Other than that I don't think we should favor one over the other here.
 * 2) Since at least Paper Mario: Sticker Star sprites that involve more than 256 unique colors have started to appear, and Paper Mario: Color Splash even has sprites with 8-bit Alpha Channel, causing artifacts if palettization is forced on them, thus PNG is needed for the appropriate display of the newer sprites; since APNG support is being completed in Chromium in these days, it is not yet possible to use PNG both for static and animated images, thus requiring also the use of GIF for the second purpose as a necessary compromise. In my opinion, by default, both should be kept, and is up to the uploader to use them properly; if they can't, one of them will become unused and then deleted anyway.
 * 3) There might still be use for both types of images.
 * 4) I say keep both. PNGs can be used if it needs to be exact color, and GIFs can be used if it needs to have life. This will work until Google supports APNGs. I suggest that if there is any unused images, put them on that subjects gallery.
 * 5) Per Eldritchdraaks.
 * 6) Per Eldritchdraaks.
 * 7) Per all.

No Preference

 * 1) This option is to keep it for a case by case basis, which is what we currently have.

Comments
Do any confusions exist? -- 02:11, 11 December 2016 (EST)

@Eldritchdraaks That might make editing the enemy pages more confusing keeping both where the PNG is for bestiary only and GIF for enemy pages only. -- 02:27, 11 December 2016 (EST)
 * That can be easily remedied by using  on the bestiary pages. You can place the bestiary image in there and choose a different image while editing the page with the enemy box.-- 02:40, 11 December 2016 (EST)
 * Outsiders might not know to edit a bestiary page instead of the enemy page to change the sprite(s) for said enemy page. -- 02:44, 11 December 2016 (EST)
 * They wouldn't have to. By default, the enemy box would display the image on the bestiary, but you could chose to instead edit the enemy page to use a different image.-- 03:06, 11 December 2016 (EST)
 * Are there any reasons to provide an override when the default image is satisfactory? -- 04:08, 11 December 2016 (EST)
 * See Megasparkle Goomba. The page currently uses promotional artwork for the Megasparkle Goomba, rather than the in-game sprite used in the bestiary. For this character and the use of the enemy box, this works.-- 14:49, 11 December 2016 (EST)
 * Because GIF is better. Just too much of it is distracting. -- 18:33, 11 December 2016 (EST)

IMO, this proposal isn't worded very well. At a glance, it seems to be a general preference, but this proposal actually deals with a preference for .GIFs and .PNGs in the bestiaries. For future reference, I think we should change the title a bit. 19:43, 11 December 2016 (EST)
 * I chose the wording I did because I have seen this trend in non-RPGs, such as Category:Super Mario World Images. -- 20:22, 11 December 2016 (EST)

@Mister Wu

Is it worth animating in the first place? Aside from animations that demonstrate something, are animations for looks all that useful to the wiki or is it extra work with little payoff and has some drawbacks? Also keep in mind that it is possible to break the 256 color limit. I think the SM64DS animation I linked to is demonstrative of this. Still not a 24-bit color animation like APNG, but it is a noticeable improvement over the previous version of the image and the GIF artifacts are barely noticeable. -- 01:47, 12 December 2016 (EST)
 * It provides visitors with an extra flair, showing how an enemy moves in the case of the bestiary/enemybox. It's not up to anyone but ourselves to decide if making these gifs are worth it. I've been slowly making the enemy gifs for Color Splash, and while I have neglected to upload pngs at the moment, the gifs bring these enemies to life.-- 02:46, 12 December 2016 (EST)

Expand the "Outcome template" rule to appeal outcomes
Eight months ago, expressed concern about the misuse of proposal outcome headers. Her rationale was that introducing a template to use in all future proposal outcomes would make implementing the archive much easier, and that the usage of Verdana as a font rather than Comic Sans was important because it was web-friendly, and looked more professional. While the proposal brought up a good, well-thought-out idea, and I would have supported it myself, the thing that still bothers me is, why does it only affect proposals and TPPs? I don’t see why it can’t affect the appeals system at all. I do understand that most appeal headers are seldom improperly formatted, but introducing a template could simplify the archiving of the appeals system, let alone the proposal system. For this reason, I have created a draft template, which you can view here for reference on how the archiving system can work via a template. It's still a start, but let's start keeping the archival systems consistent.

Proposer:  Deadline: January 7, 2017, 23:59 GMT

Support

 * 1) Per proposal.
 * 2) The only reason the appeal outcomes haven't been included is that I completely forgot about them, really. Per proposal, and per consistency.
 * 3) per all.
 * 4) Per all.
 * 5) This doesn't need a proposal.
 * 6) Per all.
 * 7) Sounds like this is a good idea that was forgotten about in the past proposal. Per all
 * 8) Per all.
 * 9) – Looks good to me, per proposal.
 * 10) Per all.

Comments
I just fixed a formatting error in your original proposal text where you linked to your main userpage, instead of the subpage you seem to have intended to link to. 18:17, 31 December 2016 (EST)
 * Thanks for doing that! 18:26, 31 December 2016 (EST)

How funny :) I created a draft for that like 7 months ago for LGM, I didn't notice it wasn't implemented yet.-- 11:13, 1 January 2017 (EST)

Template
Details here. It explains everything while containing the code used to achieve it. Two articles I can think of that uses the  prefix are Nintendo Switch and Electrodrome.


 * - This page () should show up in the file usage section of the file supplied for the template to the left while still providing a link to the file page

Proposer: Deadline: January 8, 2017 23:59 GMT

Support

 * 1) Per proposal.
 * 2) – I like this idea; it brings together the benefits of both "File:" and "Media:" links. And I can't think of any potential drawbacks, so per proposal.
 * 3) I definitely can see the benefits of this, as the image's page might have interesting information that is going to be missed when just using the "Media:" links.
 * 4) Per all. I see no problems with implementing this.
 * 5) Per all.
 * 6) Per all.
 * 7) Per Shokoroach. Also my first impression when I read your page.
 * 8) Per all.
 * 9) Per all.
 * 10) Per all.

Comments
I'm confused... What exactly are you proposing? 19:28, 1 January 2017 (EST)
 * Pretty much a way to add a link to the image's page while having the image indicated as used in the page containing the link. At the moment, the image is indicated as used only if you use the Media link, which directly leads to the image, making it cumbersome to read the additional information contained in the image's page, which might sometime be useful. Hopefully soemone else will be able to explain it in more simple terms than me... I would like to support the idea, but I want to know if this workaround does not go against a deliberate choice made by the Wiki's staff to force the use of the Media link.--Mister Wu (talk) 20:46, 1 January 2017 (EST)
 * I don't think this goes against sysop wishes. At most, we continue using  as we always had (citations with  ) but this time we use  instead. That way the link generated is something more desired if we click it while making sure that the linked file stays out of Special:UnusedFiles. -- 16:46, 2 January 2017 (EST)

Splitting Large Galleries
As I mentioned here, Mario's gallery page is incredibly large; over 87,000 bytes, which makes loading take a significant amount of time. The following proposal wouldn't just effect Mario's gallery, but all gallery pages in general.

Once a gallery page reaches a certain number of bytes, around 50-60K, it starts to lag on loading time. So I'm proposing we split those pages up once they reach that amount into separate pages to help cut down on loading times and lessen the strain on our computers, as well as making navigation easier. The page would be split into the following pages like this:

This gallery page would contain all the artwork from various games as well as scans of the subject from books, magazines, manga, etc. I'm grouping them together as these two things seem to coincide with each other, and it doesn't seem right to split them.
 * Gallery:(name) artwork and scans

This gallery page would contain the many sprites of the subject.
 * Gallery:(name) sprites

This gallery page would contain all the screenshots from games and animation we've captured of the subject.
 * Gallery: (name) screenshots

In the case of the original gallery page, it would become a disambiguation to guide users and readers to the proper location. Additionally, sample images relating to the linked page can be included to give readers an example of what to expect. In Mario's case, the page would look like this:

"Due to the size of this gallery, it has been split to reduce loading times.
 * For artworks and scans of Mario, see here.


 * For the gallery of images relating to Mario's younger form, Baby Mario, see here.
 * For images relating to Mario's powered-up forms, see here ."

I don't know if the opening statement really needs to be there, but it'll help users who weren't aware of this proposal to split (should it pass) explain why this gallery page is different from the rest.

Should this proposal pass, the Galleries page should be updated to reflect this change. The navbox would also have to be updated to reflect the change, for example: "Mario (Artworks and Scans · Sprites · Screenshots)"

Proposer: Deadline: Friday, January 27th, 2017, 23:59 GMT

Support

 * 1) Per my proposal above.
 * 2) – Per proposal.
 * 3) Sounds like a good idea to me. Especially since Mario gets like 4 or 5 pieces of individual artwork per game.
 * 4) – Per all.
 * 5) - This is definitely needed, per proposal.
 * 6) - Per all.
 * 7) Splitting pages to curb length and loading time strain is relieving and sometimes even necessary considering that browsing through high-traffic pages can be overwhelming both for the browser and the reader. In addition to this, splitting upon length alone is a much easier task with galleries than it is with articles, because they're, well, image repositories. The only things I feel need to be covered are how the  will be edited accordingly to this change and where or whether we should draw the line for gallery sizes, but other than that, everything looks fine, so per Alex95.
 * 8) Per all. (Note: I am wondering which galleries are above 50GB? It will help the proposal.)
 * 9) Per all
 * 10) Anything to keep loading times more bearable. Sure thing except finding appropriate Mario images to shitpost in the forums will be more of a challenge tho . Now, what do we do with those Bowser and Mario pages in this wiki...
 * 11) Per all. Hopefully this can happen on most of the larger galleries.
 * 12) Per all.
 * 13) Per All
 * 14) Per all.

Comments
Let me get one thing straight, while the Wiki-code for Gallery:Mario is 87KB, the generated HTML (i.e. the code that actually gets loaded) is 997KB (which is compressed to 95KB when sent to your browser). Including the images, the size (compressed) will be 21MB, which is the actual culprit of the loading time (1+ minute). (On mobile devices this is even 58MB / 2 minutes) 18:31, 20 January 2017 (UTC)
 * Ah, okay. I, uh... didn't know the technical stuff. I just knew the page was taking too long to load and I wanted to do something to fix it. 13:38, 20 January 2017 (EST)
 * The problem is valid though, even if the effective numbers come from a somewhat different source. (Also, just an info, you can vote and support in your own proposals.) 23:17, 20 January 2017 (UTC)
 * Yep, completely forgot to do that. I'm out of it today... 18:22, 20 January 2017 (EST)

Could it be worth to have a small sample of each gallery on the main Gallery page instead of it just being a disambiguation page? Or maybe link to all pages from the main article? I'm just trying to save some users a click. -- 18:56, 20 January 2017 (EST)
 * Some example images are perfectly fine, yeah, I added that in. And doesn't the disambig example list all the pages already? I just showed the coding so users would know what to include. 19:03, 20 January 2017 (EST)

@, you bring up a point I completely forgot about: the. I've seen other templates use the following format whenever there is a grouped subject, e.g.: Mario (Artworks and Scans · Sprites · Screenshots). Would that work? 19:39, 20 January 2017 (EST)
 * Yes, that probably would. I'm not sure what else to say here other than, yes, it's important to be consistent, especially with navbox templates. 21:09, 20 January 2017 (EST)
 * Consistency is important! 21:18, 20 January 2017 (EST)

@YtSSM, the only gallery I've found so far above 50KB is Mario's, but Luigi's is getting close and probably the Mushroom's? Regardless, this will effect a gallery should it end up beyond 50KB. 22:42, 20 January 2017 (EST)

@Alex95 – I think that gallery template format would work fine for the most part. The only problem I can think of is the entry being separated to another line, The alternative would be to link to the "hub" gallery only, which leaves the subject with a single link on Template:Galleries. Because thinking ahead, it would be confusing to see split parenthesis lines throughout the template. 05:37, 21 January 2017 (EST)
 * Only linking to the "hub" gallery would make it easier, sure, but makes an extra step in navigating. Should there be an "Additional Galleries" section on the template? I can see the original idea working fine, but... sheesh, I don't know anymore :P I'm open to ideas, but I'm having trouble finding ways to make them all work correctly... 12:35, 21 January 2017 (EST)

Prohibit Converting Between GIF, JPEG, and PNG Formats
Converting between image formats is pointless and unconstructive maintenance. Why? Quality doesn't improve at all. There's also some misunderstandings how each image format works. JPEG to PNG preserves the JPEG artifacting (known as lossy compression). GIF to PNG keeps all the same pixels just to have a smaller file format because PNG compression is better than GIF compression (yes, there is a compression algorithm to GIF), which means improper colors are preserved because GIF is limited to 256 colors.
 * Introduction

PNG is the best format out there for web images but requires care to be wielded properly. It makes things harder to identify what needs replacing if improperly used. JPEG to PNG directly is improper use in general. This is especially true if it just to apply transparency that JPEG isn't capable of doing, which could fall under violation of a proposal prohibiting bad/fan transparency. The image that is in need of transparency should have a version that is officially applied by Nintendo, such as a press kit release. If it doesn't exist, don't convert to PNG (or edit the clean image if it is found to exist but not transparent). The file size will just be bloated at that point without affecting the quality at all.
 * What this proposal applies to

This doesn't apply to sprite rips or custom 3D model renders because the aliasing makes it super easy to apply so there is no potential for bad transparency. If there is a mistake, it can be corrected without affecting the overall image.
 * What this proposal doesn't apply to

This doesn't apply to replacing images if a clean version of that image exists or can exist. I replace screenshots and sprites often, especially if they are in the wrong format or improperly taken. You can see my images to see just how they compare to the image I was targeting to replace at the time.

If the image is found to be released in PSD or a similar format and it doesn't have transparency with all exposed layers, it might be possible to apply the transparency without it violating the bad transparency proposal.

Sometimes images are in the BMP format or some other raw format. That is OK to convert to PNG. No quality loss there.

However, if the PNG is seen to be too large for upload, even after compression optimization (10MB max at this time for each file), exceptions can be made to allow PNG to JPEG conversion. At that point, the JPEG will be of lower space requirements but the lower space requirements means lossy compression took place.
 * Exceptions

In short, keep the original format and don't convert directly. Do things properly. If this proposal passes, Image use policy needs to be amended to reflect the change. This applies to future uploading only. If it can be spotted that an image already uploaded is in violation of this policy change, deal with it on a case by case basis as things are discovered. No need to massively go through each an every image uploaded all at once.
 * Conclusion

Proposer: Deadline: January 30, 2017, 23:59 GMT

Support

 * 1) Per proposal
 * 2) - Per Wildgoosespeeder
 * 3) It took me two whole days to read and fully digest what this proposal means to the quality of images, considering how complicated it is, but after some thought, I've decided to support. It helps to have near pixel-perfect image conversions that don't affect the format (because affecting the format of an image is actually harder than it sounds). I also appreciate the fact that you're planning to update the written policy on images since, again, considering how complicated it is, this proposal, should it pass, is better written than unwritten. So long as you know exactly what you're proposing, well, per proposal!
 * 4) Per proposal.

Comments
Anything unclear? -- 22:45, 22 January 2017 (EST)

I think suffices to tell other editors that the image in question has JPEG artifacts or GIF 256-color limits. There are benefits of keeping things in a single format when the image size is small. When I created the list of Star Pieces in Paper Mario, I first used the screenshots from a 100% Paper Mario run on the Internet, which were similar to JPG, then replaced them with GIFs from the Star Piece guide on RPGClassics and finally retook them myself for successively higher quality. Since things were done in PNG at first, this saved the work of replacing all the images two times, with the additional benefit of preserving all the older versions for historical reference. -- 00:42, 23 January 2017 (EST)
 * There has been much debate over the use of that tag. I think it's best to just prohibit future uploads from converting the images so that way new debates if the tag should be placed on those images don't get started and existing debates can get resolved ASAP (any affected images that currently occupy Category:Quality requested). -- 01:10, 23 January 2017 (EST)
 * What if someone takes a screenshot from a YouTube video, like a Nintendo ad? I would save it as PNG to avoid another layer of compression, but the result would still be PNG with lossy compression. (Correct me if I'm wrong.) -- 09:54, 23 January 2017 (EST)
 * Even though the content is definitely heavily lossy compressed, compressing it as JPEG would cause further losses in quality, furthermore it can be subsequently replaced with a proper PNG screenshot without renaming. If no uncompressed or at least high bitrate lossy compressed source video can be found I would therefore say that in this case it is fine saving as PNG, stating that the source is a video and possibly including a link to the actual video.--Mister Wu (talk) 10:41, 23 January 2017 (EST)
 * I don't think those kinds of images apply to the proposal. This is more for artwork, screenshots, or other images obtained by means through someone else rather than through the submitter's own doing, like if the image they find through a Google Image Search is in the JPEG or GIF format and they submit it as a PNG instead. In general, I find that kind of practice plagiarism, unless the source is specified and there is no way for the submitter to replicate the result. -- 15:41, 23 January 2017 (EST)

If I wanted to make a jpg transparent (make it a png), would this be allowed based on your proposal? --Andymii (talk) 23:46, 27 January 2017 (EST)
 * That's already covered by the proposal. -- 15:47, 28 January 2017 (EST)
 * What if the image is a scan (like most of the pre-internet artworks)? What's wrong with making them transparent so they don't have fuzzy backgrounds? I feel it would be better if each case was taken upon individually, instead of having a sweeping rule that may in fact get in the way for certain cases. --Andymii (talk) 12:59, 29 January 2017 (EST)
 * This is a matter of image format and understanding what format is best for what situation and understanding that converting between formats doesn't increase quality. PNG doesn't mean higher quality. PNG means that it will preserve an image in whatever state it is in 100% accurately. BMPs are ideal for PNG because no degradation occurred. JPEG uses encodings that estimate what a color is at certain pixels, divided into blocks, which is why it is regarded as a lower quality lossy format that degrades an image. There is nothing wrong with JPEGs if that is all that is available at this time. It's also better for photographs or other images that are complex with colors and patterns, which can often compress better than PNG. JPEG is a tradeoff of lower space requirements for images that can get away with quality loss, which visually, could be undetectable.
 * This is also a matter of patience and making things easier to track what needs a high quality replacement at some point, if at all. High quality versions of images will eventually come. Just a month or two ago, (formerly ) found BMPs of Super Mario World artwork that MarioWiki hosted JPEG versions of instead. The JPEGs were replaced with the BMPs (converted to PNG). That's something we don't have to worry about anymore. -- 18:35, 29 January 2017 (EST)
 * How come that if something doesn't increase quality it must be forbidden? It is true that PNG encodes a photo worse than JPG, but it encodes better than GIF a pixel artwork < 256 color, such as early images on Nintendo's website before PNG came. -- 21:30, 29 January 2017 (EST)
 * We should focus on constructive edits. Converting wastes time and makes things more confusing in the long run and problems can go unnoticed for years. At least if we forbid conversion, we can track JPEG and GIF by extension instead of by visually scanning the image for imperfections if it was converted to PNG and tagging them with, thus keeping Category:Quality requested more manageable. The extension is like a MediaWiki maintenance category in disguise. Just have to use Special:Export (formerly could use Special:MIMESearch) and remove the PNGs from the list of possible JPEGs and GIFs that should see a replacement.
 * PNG isn't encoding. It's the result of reducing data redundancy without affecting the image's pixel data. JPEG goes about compression much differently, which leads to detail loss.
 * I am kind of iffy converting those GIFs to PNG because GIF has an inferior algorithm compared to PNG but there could be a better version floating around where the colors aren't limited to 256 colors.
 * I hope this clears things up. -- 22:14, 29 January 2017 (EST)

I mostly agree with your proposal, however, I disagree with this:

Exceptions

However, if the PNG is seen to be too large for upload, even after compression optimization (10MB max at this time for each file), exceptions can be made to allow PNG to JPEG conversion. At that point, the JPEG will be of lower space requirements but the lower space requirements means lossy compression took place.

I would truthfully rather have no image at all for a given subject in cases like this if the alternative is an image with lossy compression. 16:41, 30 January 2017 (EST)
 * Two problems with that. Resolution reduction isn't desirable. Also you would have to ask to increase the upload file size limits. This is also a very rare case. I have only come across a situation like this twice out of the 70,000+ files we have uploaded. -- 17:54, 30 January 2017 (EST)