MarioWiki:Proposals

Writing guidelines
None at the moment.

Create an archive system for talk page proposals
Once more, with feeling. I'm aware of the previous failed proposal, but frankly, I don't agree with the opposition. Yes, talk page proposals don't affect as many pages as regular proposals (usually), but at the same time, they're still affecting pages, and that can easily have repercussions as well as set a precedent for the future. If a user is unsure if there's anything to support something that they want to do, they can look through the archive of proposals and see if any similar proposals have happened as well as their outcomes. That's certainly something I've done with the regular proposals, so I don't think it's unreasonable to do the same for talk page proposals. To use a concrete example, for my proposal on implied subjects, I had to dig through history pages and rely on my terrible memory to find talk page proposals that were relevant to my own; why not make the process simpler? Also, pointing people to the category as a suitable substitute when it gives no details about the content of the proposals, when they happened, what their outcome was, or even if multiple proposals happened on the same page is not satisfactory for me. Banana's talk page has six separate proposals (and it's hardly the only one of its kind), but that fact becomes completely obfuscated if we only use the category. Also, if we relied on categories for everything, we wouldn't have navigation templates. Besides, this only requires a single page.

Like the original proposal, I'm not planning on literally making an archive that houses every talk page proposal: I want to create a page that emulates Proposals/Archive, but instead of linking to subpages with every proposal, I would be simply linking to the original talk pages. This gives added clarification and convenience, and I really don't see why we shouldn't have it.

Proposer: Deadline: August 11, 2017, 23:59 GMT

Support

 * 1) Per proposal.
 * 2) - I was thinking about making a proposal like this myself, but I wasn't sure how to go about it. I get lost looking for TPPs, especially if it's one I wasn't aware existed in the first place (and there have been a few occasions where finding a past TPP would've help me, but I just couldn't find it). A condensed page similar to the main proposal archive can work, so I support.
 * 3) I really see the benefit of this. Per all.
 * 4) Per all.
 * 5) Per all.
 * 6) Per all.
 * 7) I don't like the argument that "it's not hard to find TPPs" which was the primary reason to oppose in the previous proposal. History has shown and some users stated, yes, it IS harder to find the proposals by browsing through an endless assortment of pages listed by categories. And I don't understand why we can't take the time and effort to improve navigation and organization of these things: depending on your perspective, TPPs can be more major than main space proposals, and it has spawned paragraphs and paragraphs of discussion. Plus, I don't see how lesser importance means that we should completely ignore still facets that have an influence in changing around policy, regardless of scale. I say, the correct move is to take effort and organize them better and it'd would benefit pretty much everyone in the long-term.
 * 8)  with its category Category:Settled talk page proposals is insufficient compared to Proposals/Archive.
 * 9) I agree from a navigational perspective this would be much better.
 * 10) Per all.
 * 11) - Per TT.
 * 12) Per all, especially Baby Luigi.

Comments
I think you should have drafted a sandbox page for this before you made a proposal out of it, see what it looks like before we cast a vote on this. 22:50, 4 August 2017 (EDT)
 * It's ostensibly going to be the same as Proposals/Archive, just with different links. Still, I can try to quickly whip something up. 22:52, 4 August 2017 (EDT)
 * I have a very rough draft here: it'll obviously be increased and adjusted as time goes on. 23:56, 4 August 2017 (EDT)

Now that I'm going through the talk page proposals, I'm noticing that there are a few proposals that are canceled and then immediately put into effect, usually because the proposed change is valid but the whole proposal process is unnecessary. Would anyone object if I added a color for these situations? I'm thinking mauve would look alright (and it's on the mock-up; search for Axem or Gargantua). 11:02, 5 August 2017 (EDT)
 * I think white would be better, as mauve might be confusing for color-blind people (like me) with purple. I think blue is what's normally used in this case, though. 11:42, 5 August 2017 (EDT)
 * Blue is meant for proposals that fail, but whose proposed changes are later implemented anyways. A canceled proposal is different from a failed proposal - that's why we have both red and pink. I can definitely change the color, but since white is also what generically appears if a color hasn't been inputted correctly, I think that might be confusing. EDIT: Actually, if we're concerning ourselves with colorblindness, then the current color system has its own issues. 11:46, 5 August 2017 (EDT)
 * Here is a suggestion. If a proposal was cancelled but changes took place after the proposal, than it would be light blue. It's not much of a difference, but a difference nevertheless. 17:39, 5 August 2017 (EDT)
 * It'd be hard to distinguish between light blue and regular blue at a glance, especially since our current blue is already fairly light. 17:41, 5 August 2017 (EDT)
 * We could use black, but then the text would have to change accordingly. As for blue, apparently the color we're using is lighter than the #0000FF code for standard blue. So with that in mind, maybe dark blue? 17:50, 5 August 2017 (EDT)
 * If the blue's too dark, then we come to the same issue as using black (and in fact, the standard "DarkBlue" or "Navy" is definitely too dark). The template also isn't currently set up for changing the text color, and in any case, I think that it'd be best to keep the text uniform. For now, I've thrown more colors onto the table at the top for demonstrative purposes. If you have a particular color in mind, this website works well for testing how it would like against black text. 18:11, 5 August 2017 (EDT)
 * The problem I think we're having is we've used all the basic colors; any others we chose aside from a very light or a very dark color will end up looking close to ones we're already using. Dark blue doesn't look too bad, imo, though ivory, light yellow, slate, and chartreuse (as ugly as that is) are some other possible options. 18:23, 5 August 2017 (EDT)
 * It'd be more convenient if you could provide hex color codes that show exactly what you're talking about, if you don't mind. 18:32, 5 August 2017 (EDT)
 * Ivory: #FFFFF0, Light yellow: #FFFFE0, Slate: #708090, and Chartreuse: #7FFF00. The dark blue I was thinking of was actually Dark cyan, my mistake there: #008B8B. 18:41, 5 August 2017 (EDT)
 * Threw all of those colors up there for good measure. Now that they're all up there, I'm partial to dark cyan. Everything else is either illegible or too similar to another (established) color. 18:47, 5 August 2017 (EDT)
 * darkcyan looks the best out of them all, imo. Is there a chance this new parameter could be added to main proposals as well, just in case something like that happens here in the future? 18:51, 5 August 2017 (EDT)
 * I'll start using that for now, then (although I'll call the parameter "teal" for convenience). I'll leave the discussion of implementing it with the main proposals to you administrators. 19:00, 5 August 2017 (EDT)

Delete the RPG Item categories
(borrowing my argument from here)

Both Category: RPG Items - General and Category:RPG Items - Special are inconsistent with the rest of the wiki. We don't have categories for platformer items or sports items, nor do we have broad RPG categories for characters or enemies or any other subject. At best, we only have categories that encompass a series (for example, Category:Mario & Luigi Series Enemies branches off into the game-specific enemy categories), but nothing that's solely based on genre. Every item in these categories already has a home in another, more specific and more helpful item category. Nothing is gained from having them, and nothing would be lost if they were deleted.

Proposer: Deadline: August 16, 2017, 23:59 GMT

Delete

 * 1) Per my proposal.
 * 2) Per proposal.
 * 3) Per proposal.
 * 4) Why do we have this? I know RPGs are special because they give meaning to items, but a wiki shouldn't just put them all together in one category and call it a day. Even look at this if you want to know why. Per proposal
 * 5) Per all.
 * 6) Per proposal.
 * 7) Also take a look at this page.

Merge Super Mario Sunshine sub-level articles into their missions' articles
We currently have articles for various sub-levels from Super Mario Sunshine (e.g. Sand Portal, Bottle). These are obviously just artifacts from before the game's missions were split off. Now that we have the mission articles, the sub-level articles themselves are completely obsolete; we now have several pairs of articles covering the exact same thing. Some of them even have conjectural names derived right from the mission names (Hotel Lobby's Secret, Shell's Secret), which not only emphasizes the redundancy but adds confusion. So any relevant content on these articles not already on the mission articles should just be moved to those. It's not like we generally have separate articles for sub-levels anyway; we don't have articles for Shifting Sand Land's pyramid or Lethal Lava Land's volcano.

Here are what the results of this proposal will be if it passes:
 * Hillside Cave --> The Hillside Cave Secret
 * Cliff Spring Cave --> The Secret of the Dirty Lake
 * Ricco Tower --> The Secret of Ricco Tower
 * Sand Portal --> Dune Bud Sand Castle Secret
 * The Yoshi-Go-Round --> The Yoshi-Go-Round's Secret
 * Hotel Lobby's Secret --> The Hotel Lobby's Secret
 * Bottle --> Red Coins in a Bottle
 * Shell's Secret --> The Shell's Secret

The secret levels in Delfino Plaza (Super Slide, Pachinko Game, Lily Pad Ride, Turbo Track, Red Coin Field) are not affected by this proposal. They fall under the same category as levels like The Princess's Secret Slide and The Secret Under the Moat, and should stay.

Proposer: Deadline: August 12, 2017, 23:59 GMT

Support

 * 1) Per proposal.
 * 2) Per proposal.
 * 3) Per Proposal
 * 4) Some of these names aren't even "names" per se, they're just descriptive locations, like hillside cave. Anyway, most of these are pretty much the equivalent of our planet sections in the Super Mario Galaxy articles, so I think a merge is sufficient.
 * 5) - The mission articles go into detail about the secret areas anyway. Support.
 * 6) Per all.
 * 7) If we can indeed cover the sub-levels in the mission pages without losing any amount of relevant detail and without creating pages that are too long and difficult to browse, I definitely support the idea of writing everything in one page.
 * 8) So long as mission/episode articles are not affected (which looks like they'll stay), per proposal!

Oppose

 * 1) I think the Episode description should describe the entire mission, including getting to the secret, but not getted bogged down with every geographical detail of said secret level's layout, which the article for the secret area should have instead.

Miscellaneous
None at the moment.