MarioWiki:Proposals

List of Talk Page Proposals

 * Split the sections Attackathlon, Toad Quiz and Lakitu Info Centre into and  (Discuss) Passed
 * Split Spiny Fish from Spiny Cheep Cheep (Discuss) Deadline: May 2, 2016, 23:59 GMT

Writing Guidelines
None at the moment.

New features
None at the moment.

Removals
None at the moment.

Merge all YWW [X] Patch Articles with Their Non-Patch Articles
In Yoshi's Woolly World, some enemies, such as the Ruffin Tumble, have a patch form, that is simply a pixelated version of the original enemy; they're the exact same as the originals, except that they look different and that the patch forms are seen in blocks, and are released after the block is eaten. I don't think that one minor difference is enough to warrant separate articles for the original and the patch form. The only thing that might be a problem is their positions in the Scrapbook Theater, but I'm not sure that warrants separate articles either.

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

Support

 * 1) My proposal.

Oppose

 * 1) Looking at the Dream Team enemies, the R enemies all have separate changes, despite being only recolors with different stats. For consistency, the patch enemies should keep their own pages.
 * 2) per Superchao
 * 3) - Per Superchao.
 * 4) I don't necessarily agree with comparison Superchao is trying to make. We separate R enemies because they're treated as separate enemies, supported by stats and a recolor. We do sometimes merge mere aesthetic variants such as the Scarescraper ghosts. I do oppose because there are only four patch enemies in the game, so all we're getting are four harmless small articles on a minor aesthetic variant. You can also argue that the methods for encountering them is different compared to the standard enemy as another case to leave them split, but just the amount of articles alone tells me it's okay to leave them as standalone.
 * 5) Per Superchao and Bazooka Mario.
 * 6) Completely different enemies. Per all.
 * 7) Per Bazooka Mario.
 * 8) Per Bazooka Mario!

Comments
It may be an issue if all enemies have a patch form, but it seems to me that we have only Bullet Bill Patch, Monty Mole Patch, Nipper Spore Patch, and Ruffin' Tumble Patch that exist. Maybe it's not so bad that we leave it as it is? 19:14, 11 April 2016 (EDT)

Create a template for proposal outcomes
The current coding for the proposal outcome is repetitive and cumbersome to remember every single time we need to archive a proposal, which has resulted in inconsistent headers (we first used Times New Roman, then switched to Comic Sans, and we're allowed to do that because one, there's virtually no guideline on this, and two, the coding is a crap to remember). So, exactly why isn't the outcomes in a template again? Repetitive coding is essentially template fodder, and there's no reason why we need to remember and duplicate difficult to remember coding when we can simply remember a template and use switchers to depend on the outcomes of a proposal. has created various templates in his sandbox pages to demonstrate how we can use the template to make archiving proposals easier.

There are two options:


 * A test on how the new template will look like. The first one is more complex, but it has more options to fit, while the second option is simpler to code, but requires some extra parameters for some outcomes, namely the veto outcome.
 * Option 1 draft coding
 * Option 2 draft coding

In the long term, I believe this will greatly benefit users who want to archive older proposals and will make remembering the exact coding less of a hassle.

Also, this will eliminate the egregious misplacement of the notorious and extremely unprofessional Comic Sans font, which will be replaced by Verdana. Comic Sans is not a web-safe font, and any browser who doesn't have it installed will fallback to Arial and therefore look incredibly inconsistent with different browsers, whereas, Verdana is a web-safe standard font that should be used for more professional headers, especially those that notify readers the outcomes of important wiki matters. If past "minor" problems such as the misuse of subspecies and beta elements can be addressed, I don't see why it's particularly difficult to address what is essentially a design problem, which is more important to others than others, like terminology. The little things matter too.

Proposer:, with great help from Deadline: April 25, 2016, 23:59 GMT

Implement Option 1

 * 1) I feel like this version of the proposal outcome is better, as even though it's more complex and has more switchers, it's far more flexible and easier to use than option 2.
 * 2) I don't mind which version gets used, both are easy to use in my mind. I'm slightly leaning towards this design though, but fundamentally, I agree with using a template.
 * 3) . Absolutely do this, and don't bother with "Option 2" coding even as a fallback. More parameters might be slightly more complex to use, but make it much less likely that things will end as a mess of inconsistency all over again. (I wouldn't bother specifying a font at all, actually - the text being big, bold and coloured is enough to make it stand out, after all. Verdana's definitely better than CS though).
 * 4) I like the one in which the possible outcomes are already coded, so it's easier to use without creating many orthogarphic dramas and especially allows to see what are the possible outcomes. By the way, tie and no-quorum have the same text, so maybe you should change the text of the tie case.
 * 5) It's worth standardizing the formatting for the proposal outcomes, especially since such text should go in a template since they're repetitive and are found in several pages, exactly what templates are for. While comic sans dominates proposal outcomes, we also have a few off Times New Roman-styled outcome text lying around, so we should fix that too. That means getting rid of the comic sans: the typeface clashes with everything else (especially since we're supposed to be a serious wiki) and, as a result, the casual, unsophisticated typeface appears ugly and sloppy, which goes against our idea that proposals should be serious matters. Years of careless handling with typefaces do not justify continued mishandling nor do years of editor oversight on what should've been a template in the first place. The only reason it is tedious to change them is the result of that error. Once the changes are done, everything will be much easier to manage, from the template itself to how proposals should be archived. I also think we don't really need to change to Verdana since the font (the colors, size, and bold, that is) does a good job at helping it stand out. Sure, it might seem all minor in the end, but the little stuff shouldn't be disregarded. We should regard every aspect of the wiki as if we care; the egregious use of comic sans gives off the vibe of carelessness. This is an easy, harmless fix. The biggest issue I find is that many of these outcomes are tucked under protected archives, but that in of itself shouldn't be a reason against this change.

Comments
Maybe we can take a step further and color-code proposal outcomes similar to color legend in the proposals archive? 18:47, 18 April 2016 (EDT)
 * i don't know, i think it's a bit complex to remember what passed and what didn't, and over time, we might have to remember to change it. I think sticking to a three color scheme would keep those simpler. You also have to keep in mind that this also applies to TPP, not simply mainspace proposals, so more stuff gets affected. 19:02, 18 April 2016 (EDT)
 * It is the simplest thing currently: green passed, red failed, gray has no impact.-- 19:05, 18 April 2016 (EDT)
 * ---A spontaneous idea is that we could technically allow both ways of using the template.-- 19:09, 18 April 2016 (EDT)
 * I wouldn't be 100% opposed to this, but wouldn't it overcomplicate things? 19:10, 18 April 2016 (EDT)
 * I did it with a slight modification. If you feel that this creates an inconsistency you can revert it, it's your idea after all.-- 19:13, 18 April 2016 (EDT)
 * I'm a stupid layperson, so it's pretty unclear to me what you changed. 19:15, 18 April 2016 (EDT)

"Comic Sans is not a web-safe font, and any browser who doesn't have it installed will fallback to Times New Roman"

It'll actually fallback to the default Arial typeface, so that's not a valid point. 20:41, 18 April 2016 (EDT)
 * whatever 21:33, 18 April 2016 (EDT)