MarioWiki:Proposals

Writing guidelines
None at the moment.

New features
None at the moment.

Removals
None at the moment.

Discourage drive-by templating part 2
Building off of this proposal, I propose taking this one step further with some more templates that are often used. Suggestions to merge, split, and rename articles are frequently made using the relevant templates, but many times that's the end of it and no talk page discussion is ever started. The reasons for the suggested change are left behind in a quickly buried edit summary, or not elaborated on at all. That makes it a lot harder for users to know why the change was suggested in the first place, and to discuss whether to do it.

If this passes, then these templates must be accompanied by either an active discussion or proposal. The discussion/proposal doesn't need to be on the talk page of the article where the template is used, but it does need to exist somewhere, and the template needs to link to the appropriate page. I'm hesitant to define what counts as an active discussion here, because I think it's fair to have some level of discretion there - personally, I would say that if there hasn't been any engagement whatsoever in the past 365 days, the discussion isn't active anymore (please be aware that this is not set in stone). This is to prevent having these templates left behind while attached to discussions that are years old - like proposals, if you suggest a change it's up to you (or the other supporters) to see that through and keep it active until a consensus is reached.

Articles where the proposed changes are enforced by a proposal but not enacted yet are exempt, as a decision has already been made. However, the proposal field of these templates should be used to link to the relevant proposal.

The following templates will be affected:
 * Template:Merge to
 * Template:Merge from
 * Template:Split
 * Template:Move

Proposer: Deadline: May 4, 2023, 23:59 GMT

Support

 * 1) yeah
 * 2) Per proposal.
 * 3) Per proposal.
 * 4) "Yeah" indeed. (To be honest, I thought this was something the previous proposal did...)
 * 5) Explaining why you suggest a split/merge/move in the edit summary is horrible for wiki maintenance. The reasoning is often very hard to find (if it even exists), and the templates end up linking to a red link talk page. If you can't be bothered to actually start a discussion on the changes you want to see made, then you shouldn't be allowed to use these templates in the first place.
 * 6) Per proposal.
 * 7) Yeah, fully on board with this. I've seen this template many times and it often doesn't have any sort of discussion tying to it.
 * 8) Per all, I've seen so many instances of this with no discussion to be found anywhere.
 * 9) This is exactly what I had brought up on the previous proposal.
 * 10) - Please? (because a "per proposal" doesn't drive home the urgency.)
 * 11) Pretty please. Way too many instances of articles having these specific tags but never linking to talk pages, or any other way to give out what the reason for it's inclusion is. I especially hate it when the reason is hidden away in edit summaries, like, edit summaries are only ment for telling what you did on a page, it is NOT for explaining complex topics that better warrant an entire discussion on a talk page.
 * 1) Pretty please. Way too many instances of articles having these specific tags but never linking to talk pages, or any other way to give out what the reason for it's inclusion is. I especially hate it when the reason is hidden away in edit summaries, like, edit summaries are only ment for telling what you did on a page, it is NOT for explaining complex topics that better warrant an entire discussion on a talk page.

Miscellaneous
None at the moment.