MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
 
Line 1: Line 1:
<center>[[File:Proposals.png]]</center>
{{/Header}}
<br clear=all>
{| align="center" style="width: 85%; background-color: #f1f1de; border: 2px solid #996; padding: 5px; color:black"
|'''Proposals''' can be new features (such as an extension), removals of previously added features that have tired out, or new policies that must be approved via [[Wikipedia:Wikipedia:Consensus|consensus]] before any action is taken.
*Any user can support or oppose but must have a strong reason for doing so, not, e.g., "I like this idea!"
*"Vote" periods last for one week.
*All past proposals are [[/Archive|archived]].
|}
A proposal section works like a discussion page: comments are brought up and replied to using indents (colons, such as : or ::::) and all edits are signed using the code <nowiki>{{User|</nowiki>''User name''<nowiki>}}</nowiki>.


This page observes the [[MarioWiki:No-Signature Policy|No-Signature Policy]].
==Writing guidelines==
''None at the moment.''


<h2 style="color:black">How To</h2>
==New features==
<h3 style="color:black">Rules</h3>
===Create a template to direct the user to a game section on the corresponding List of profiles and statistics page===
#If users have an idea about improving the wiki or managing its community, but feel that they need community approval before acting upon that idea, they may make a proposal about it. They must have a strong argument supporting their idea and be willing to discuss it in detail with the other users, who will then vote about whether or not they think the idea should be used. Proposals should include links to all relevant pages and [[MarioWiki:Writing Guideline|Writing Guideline]] proposals ''must'' include a link to the draft page.
This proposal aims to create a template that directs people to a game section on a Profiles and statistics list page, saving the user the step of having to scroll for it themselves. The reason why I'm proposing this is because as more ''Super Mario'' games are released, it becomes harder to comfortably find what you're searching for in the corresponding List of profiles and statistics page, especially for [[Mario]], [[Bowser]], and many other recurring subjects.
#Proposals end at the end of the day (23:59) one week after voting starts, except for Writing Guidelines and Talk Page Proposals, which run for two weeks. ('''All times GMT.''')
#*For example, if a proposal is added at any time on Monday, August 1, 2011, the voting starts immediately and the deadline is one week later on Monday, August 8, at 23:59 GMT.
#Every vote should have a reason accompanying it. Agreeing with or seconding a previously mentioned reason given by another user is accepted.
#Users who feel that certain votes were cast in bad faith or which truly have no merit can address the votes in the Comments section. Users can ask a voter to clarify their position, point out mistakes or flaws in their arguments, or call for the outright removal of the vote if it lacks sufficient reasoning. Users may '''not''' remove or alter the content of anyone else's votes. Voters can remove or rewrite their own vote at any time, but the final decision to remove another user's vote lies solely with the [[MarioWiki:Administrators|administrators]].
#If a user makes a vote and is subsequently blocked for any amount of time, their vote is removed. However, if the block ends before the proposal ends, then the user in question holds the right to re-cast their vote. If a proposer is blocked, their vote is removed and "(banned)" is added next to their name in the "Proposer:" line of the proposal, which runs until its deadline as normal. If the proposal passes, it falls to the supporters of the idea to enact any changes in a timely manner.
#No proposal can overturn the decision of a previous proposal that is less than '''4 weeks''' ('''28 days''') old.
#Any proposal that has three votes or less at deadline will automatically be listed as "[[Wikipedia:Quorum|NO QUORUM]]." The original proposer then has the option to relist said proposal to generate more discussion.
#All proposals that end up in a tie will be extended for another week.
#If a proposal has more than ten votes, it can only pass or fail by a margin of '''three''' votes. If a proposal reaches the deadline and the total number of votes for each option differ by two or less votes, the deadline will be extended for another week.
#Proposals can only be extended up to three times. If a consensus has not been reached by the fourth deadline, the proposal fails and can only be re-proposed after four weeks, at the earliest.
#All proposals are archived. The original proposer must '''''take action''''' accordingly if the outcome of the proposal dictates it. If it requires the help of an administrator, the proposer can ask for that help.
#Proposals can only be rewritten or deleted by their proposer within the first three days of their creation. However, proposers can request that their proposal be deleted by an [[MarioWiki:Administrators|administrator]] at any time, provided they have a valid reason for it. Please note that cancelled proposals must also be archived.
#If the administrators deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to remove it at any time.
#There should not be proposals about creating articles on an underrepresented or completely absent subject, unless there is major disagreement about whether the content should be included. To organize efforts about completing articles on missing subjects, try creating a [[MarioWiki:PipeProject|PipeProject]].
#Proposals cannot be made about promotions and demotions. Users can only be promoted and demoted by the will of the [[MarioWiki:Administrators|administration]].
#No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.


<h3 style="color:black">Basic Proposal and Support/Oppose Format</h3>
Another reason I think this would be valid is because of the fact that listing statistics in prose (e.g. 2/10 or 2 out of 10) looks off, especially if that can already be seen in the corresponding statistics box; in that case, the prose could change from "2/10" to something more vague like "very low stat", which isn't typically worded as such in the statistics box.
This is an example of what your proposal should look like, if you want it to be acknowledged. If you are inexperienced or unsure how to set up this format, simply copy the following and paste it into the fitting section. Then replace the [subject] - variables with information to customize your proposal, so it says what you wish. If you insert the information, be sure to <u>replace the whole variable including the squared brackets</u>, so "[insert info here]" becomes "This is the inserted information", not "[This is the inserted information]".
-----
<nowiki>===[insert a title for your Proposal here]===</nowiki><br>
<nowiki>[describe what issue this Proposal is about and what changes you think should be made to improve how the Wiki handles that issue]</nowiki>


<nowiki>'''Proposer''': {{User|[enter your username here]}}<br></nowiki><br>
For example, let's say for [[Luigi]] in his appearance in ''[[Mario Sports Superstars]]'', there could be a disclaimer either below the section heading or in a box to the side (we can decide the specifics when the proposal passes) that informs the reader that there's corresponding section that shows his profiles/statistics corresponding. Like such:
<nowiki>'''Deadline''': [insert a deadline here, 7 days after the proposal was created, at 23:59 GMT.]</nowiki>


<nowiki>====Support====</nowiki><br>
:''For profiles and statistics of Luigi in Mario Sports Superstars, see [[List of Luigi profiles and statistics#Mario Sports Superstars|here]].''
<nowiki>#{{User|[enter your username here]}} [make a statement indicating that you support your proposal]</nowiki>


<nowiki>====Oppose====</nowiki>
The above message is not necessarily the final result (just a given example), but the disclaimer would definitely point the user to the appropriate game section on the profiles and statistics list page, should this pass.


<nowiki>====Comments====</nowiki>
'''Proposer''': {{User|Super Mario RPG}}<br>
-----
'''Deadline''': January 1, 2025, 23:59 GMT
Users will now be able to vote on your Proposal, until the set deadline is reached. Remember, you are a user as well, so you can vote on your own Proposal just like the others.


To support, or oppose, just insert "<nowiki>#{{User|[add your username here]}}</nowiki> at the bottom of the section of your choice. Just don't forget to add a valid reason for your vote behind that tag if you are voting on another user's Proposal. If you are voting on your own Proposal, you can just say "Per my Proposal".
====Support====
#{{User|Super Mario RPG}} Per.
#{{User|Hewer}} I don't really see a need to deliberately make prose less specific, but otherwise I like this idea, per proposal.


__TOC__<!--
====Oppose====


<center><span style="font-size:200%">CURRENTLY: '''{{#time: H:i, d M Y}} (GMT)'''</span></center>
====Comments====
{{@|Hewer}} I don't think this would necessarily eliminate cases in which statistics are in prose, but it may be redundant if there's the link to conveniently access the statistics or profiles. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 15:15, December 18, 2024 (EST)


===Add an abbreviation template to type out full game titles===
{{early notice|December 25}}
This proposal is about creating a template that it makes it easier to type out full game titles. Although ''The Legend of Zelda'' games generally have longer titles (and Zelda Wiki even has templates for some of their shorter titled games, like ''{{iw|zeldawiki|Hyrule Warriors}}'', {{iw|zeldawiki|Template:HW|here}}), there have still been cases in which some game titles are uncomfortably long, such as ''[[Donkey Kong Country 3: Dixie Kong's Double Trouble!]]'' or ''[[Super Mario RPG: Legend of the Seven Stars]]'', and while it may seem like not a big deal to some, it would be a small quality-of-life improvement if we could have a template where we input the abbreviation, and the output becomes the game title.


For example, <nowiki>{{a|M&LSS}}</nowiki> would result in ''Mario & Luigi: Superstar Saga'' (complete with italics formatting). Meanwhile, <nowiki>{{a|M&LSS|l}}</nowiki> to link to the game, outputting ''[[Mario & Luigi: Superstar Saga]]'', although depending on who creates the template, it could be vice versa, like it links by default and <nowiki>{{a|M&LSS|n}}</nowiki> would prevent a link.


<br>
Since ''Super Mario'' has several releases, it may get difficult maintaining with all the abbreviations, and there have been cases where two games have shared the same abbreviation. (e.g. [[SMS]] for both ''Mario Sunshine'' and ''Mario Strikers''). In that case, either <nowiki>{{a|SMS|2002}}</nowiki> (with the year of release) or a custom abbreviation (e.g. <nowiki>{{a|SMShine}}</nowiki>) would be needed (personally I'd prefer the latter).
-->


<h2 style="color:black">Talk Page Proposals</h2>
Consider we already have similar templates for Princess Peach and Princess Daisy (i.e. {{tem|Peach}} and {{tem|Daisy}}), and both of their full titles (with "Princess" included) is a lot shorter than the two game titles in the first paragraph.
All proposals dealing with a single article or a specific group of articles are held on the talk page of one of the articles in question. Proposals dealing with massive amounts of splits, merges or deletions across the Wiki should still be held on this page.


:''For a list of all settled Talk Page Proposals, see [[:Category:Settled Talk Page Proposals|here]].''
'''Proposer''': {{User|Super Mario RPG}}<br>
'''Deadline''': January 1, 2025, 23:59 GMT


<h3 style="color:black">Rules</h3>
====Support====
#All active talk page proposals must be listed below in chronological order (new proposals go at the bottom). All pages affected must be mentioned in the ''brief'' description, with the talk page housing the discussion linked to directly via "({{fakelink|Discuss}})". If the proposal involved a page that is not yet made, use {{tem|fakelink}} to communicate its title. The '''Deadline''' must also be included in the entry. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links. Place {{tem|TPP}} under the heading.
#{{User|Super Mario RPG}} Per.
#All rules for talk page proposals are the same as mainspace proposals (see the "How To" section above), with the exceptions made by Rules 3 and 4 as follows:
#{{User|Camwoodstock}} We don't see the harm in this, even if it would admittedly be fairly niche. The only real complaint we have is the lack of an additional parameter for changing the displayed text, so if we need to say something like "in the [[Paper Mario: The Thousand-Year Door (Nintendo Switch)|remake]]", we have to write that out the old-fashioned way.
#Voting in talk page proposals will be open for two weeks, not one. ('''All times GMT.''')  
#{{User|EvieMaybe}} might make some link-heavy pages lighter!
#*For example, if a proposal is added at any time on Monday, August 1, 2011, it ends two weeks later on Monday, August 15, 2011, at 23:59 GMT.
#{{User|Salmancer}} Words cannot express the relief that my fingers would feel if they never have to type out "Mario & Luigi: Bowser's Inside Story + Bowser Jr.'s Journey" again.
#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.
#{{User|Tails777}} Mario already took my example, but it still stands; the amount of times I've had to type out that title (or even the abbreviation for it) was incredibly annoying. Per all.
#The talk page proposal '''must''' pertain to the article it is posted on.
#{{User|Scrooge200}} Yes, these titles can be a pain to write out in full. Per all.
#{{User|Technetium}} Per all.
#{{User|Sparks}} Per all.


===List of Talk Page Proposals===
====Oppose====
*Move the [[Vaporware]] page. ([[Talk:Vaporware|Discuss]]) '''Deadline''': December 9, 2011, 23:59 GMT
*Fix [[Template:Warning]]. ([[Template talk:Warning|Discuss]]) <s>December 3, 2011, 23:59 GMT</s> '''Extended''': December 10, 2011, 23:59 GMT
*Delete [[Lakitu (character)]]. ([[Talk:Lakitu (character)|Discuss]]) '''Deadline''': December 11, 2011 23:59 GMT
*Merge [[Chuckorok]] with [[Chuckola Rock]]. ([[Talk:Chuckola Rock|Discuss]]) '''Deadline''': December 12, 2011 23:59 GMT
*Delete [[Wuhu Island]] ([[Talk:Wuhu Island|Discuss]]) '''Deadline''': December 13, 2011 23:59 GMT
*Change Character Infobox image for [[Princess Peach]]. ([[Talk:Princess_Peach#Character_Infobox_Image_Change|Discuss]]) '''Deadline''': December 17, 2011 23:59 GMT
*Decide on name for [[Queen Bee]] ([[Talk:Queen Bee|Discuss]]) '''Deadline''': December 18, 2011 23:59 GMT
*Merge [[Flight]] with the [[List of Implied Characters]] ([[Talk:Flight|Discuss]]) '''Deadline''': December 18, 2011 23:59 GMT


==Writing Guidelines==
====Comments====
===MarioWiki:Upcoming content===
:{{@|Camwoodstock}} Such a parameter can always be added to the template. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 18:18, December 18, 2024 (EST)
This writing guideline is meant to establish a consistent guideline for how we handle content from unreleased games. The only aspect of upcoming content that is not covered in this guideline are the project articles themselves. This is because I believe they need a separate guideline page due to their complex nature. Most of what's covered in the guideline is already more or less adhered to, except for one thing. If this proposal passes, '''all information about upcoming projects will need to have a suitable reference'''. The main reason for this is because information from upcoming projects are at high risk of being false and references improve our credibility. It really shouldn't be too difficult to enforce on a mass scale, today's games have ton of secondary source coverage and it is easy to find something that backs up the information. The process is detailed a little more in the draft page. Comments and suggestions for improvement are always welcome.


'''Proposer''': {{User|Knife}}<br>
Salmancer: ''[[Mario & Sonic at the Sochi 2014 Olympic Winter Games]]'' might be the other worst game title I've had to type out. {{User:Mario/sig}} 00:59, December 20, 2024 (EST)
'''Deadline''': December 8, 2011, 23:59 GMT<br>
:Damn it, that was gonna be my example! {{User:Tails777/sig}}15:34, December 20, 2024 (EST)
'''Draft''': [[User:Knife/Policy]]
 
===Split image categories into separate ones for assets, screenshots, and artwork===
This proposal will address the bloat some image categories have and make them easier to navigate.
 
Why is this useful? It makes adding to galleries or finding images to replace much easier. If you want to retake screenshots from a game, you can go to the screenshots category to find them. If you have sprite rips to replace, there's a category for that. The same goes for finding images from a game that aren't on the gallery already and being able to sort them more efficiently. This is also how we divide up character galleries already, such as [[Gallery:Mario (2010-2019)]].
 
Now, I can see a few edge cases, like when games have screenshots of themselves for credits images (i.e. ''[[Paper Mario: The Thousand-Year Door (Nintendo Switch)]]''). I would still classify these as assets, since they are ripped from the game. Artwork that is used in smaller forms in-game, such as in ''[[Super Mario Maker 2]]'', would be classified as artwork if externally released or an asset if it was ripped from the game files. Edge cases shouldn't be too common and they're easy to work out: it's not too different from how we license images or put them in character or subject galleries.
 
I think the name "assets" would be more useful in shorthand than "sprites and models," in addition to covering textures, so I propose for the category to be called that, but I can change it if there's opposition. The global images category can still exist in the case there's scans, merchandise, video screenshots, or such images that cannot be further categorized.
 
'''Proposer''': {{User|Scrooge200}}<br>
'''Deadline''': January 5, 2025, 23:59 GMT


====Support====
====Support====
#{{User|Knife}} &ndash; Per proposal.
#{{User|Scrooge200}} Per proposal.
#{{user|coincollector}} - Per all. And what per all I mean is Knife.
#{{User|Waluigi Time}} I support this in principle, as long as there's room for discretion on what gets split and what gets left alone. A game with only ten or so pieces of artwork doesn't need a separate category for them, they can just stay in the main images category for that game. Otherwise, this seems useful, I just don't want users to go overboard by purely following the letter of this proposal.
#{{User|Mario4Ever}} Per proposal.
#{{User|New Super Yoshi}} I could actually keep track of new info which I always would want to Per all.
#{{User|Jazama}} Per all
#{{User|Bop1996}} Per proposal.
#{{User|RandomYoshi}} — Per Knife. We really need this thing.
#{{User|Walkazo}} - Per Knife.
#{{User|B.wilson}} - Per proposal.
#{{User|Lindsay151}} Per all.
#{{User|Tails777}} Per all.
#{{User|Toad85}} I don't know what to say other than Per All, and that's a bad thing. However, this proposal is a good thing.
#{{User|Superfiremario}} Per Knife! Great idea!
#{{User|Fawfulfury65}} Per proposal.
#{{User|Awesome12456}} ok
#{{User|Bowser's luma}} I thought this was already in effect - a definite Yes.
#{{User|Raven Effect}} Per proposal


====Oppose====
====Oppose====


====Comments====
====Comments====
It's just my opinion, but I think it's not by their complex nature but rather by their unique nature. Regarding to the new subjects (articles that talk about new element of the game like enemies, courses, etc. ''especially'' those  that are introduced in a game) Is it possible to use the infoboxes and make mention of their appearance? I see a problem with this. Usually we don't include the appearance of something of a an upcoming game in the infobox until it is officially released. However, some articles (for example, the racecourses of Mario Kart 7) include their appearance despite the fact that the game has not been released yet which may be incosistent to the guidelines. {{user|coincollector}}
This is already being done (e.g. [[:Category:Mario Kart Tour item icons]]). [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 11:02, December 23, 2024 (EST)
:That's why those articles have the <nowiki>{{newsubject}}</nowiki> template on them. The information within the articles, as I understand it, is coming from one or more of the official websites, but that doesn't mean the articles aren't subject to revision once the game comes out. {{User|Mario4Ever}}


Yes, but that doesn't explain the necessity to include an infobox with such information in a upcoming subject, that's what bothers me. Include information to the infoboxes respecting the sources or get the rules of not include information to them until the game is released? {{user|Coincollector}}
==Removals==
:Correct me if I'm wrong, but I think the issue only arises when people try to add appearances in an unreleased game on preexisting subjects (like if someone tried to say that the latest appearance of Maple Treeway is in MK7). There's nothing that says we can't include appearances in infoboxes for subjects (e.g. Melody Motorway) that have yet to appear in the series provided it comes from a reputable source. {{User|Mario4Ever}}
''None at the moment.''
 
==Changes==
===Broaden the scope of the <nowiki>{{rewrite}}</nowiki> template and its variations===
With the [[Template talk:Unreferenced#Delete or be more specific|previous proposal]] having passed with being more specific as the most voted, I've come up with a proposal about the possibility to make the {{tem|rewrite}}, {{tem|rewrite-expand}}, and {{tem|rewrite-remove}} templates more specific. As you can see, these templates are missing some smaller text. As such, I am just wondering if there is a possibility to have the smaller text added to the <nowiki>{{rewrite}}</nowiki>, <nowiki>{{rewrite-expand}}</nowiki>, and <nowiki>{{rewrite-remove}}</nowiki> templates.


If that were the case, I think it should be needed to make notice of that, because some people may get that the appearance of a new subject should be applied likewise for another previously released and will make an upcoming appearance as well. {{User|Coincollector}}
First of all, the <nowiki>{{rewrite}}</nowiki> template currently reads as follows:
:Maybe the new subject's infoboxes could have "(upcoming)" next to the game's name to set them apart from normal released appearances. I also think it'd be a good idea to have a small section on Infoboxes in the policy page to make the varying use of the "latest appearance" clear. Additionally, I think more emphasis on using references could be made in the "New articles pertaining to upcoming project" and "Previously existing articles in upcoming projects" - nothing major, however, just a short note in each section (leaving the discussion to the section). Like, in the former section one sentence could be expanded to "''If an article does have sufficient information backed up by reliable references,''", and the latter section could have "''as long as the information is not speculation and is accompanied by solid references''". Also, "''Once information has been rewritten''" seems redundant: if the info was well-written from the start, maybe it doesn't need rewriting, just supplementation, and something like "''Once the project has been released for a reasonable amount of time and more content has been added''" seems like it's giving more bang for the buck (since it's also pointing out that the template can't be removed immediately). - {{user|Walkazo}}
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten'''. {{#if:{{{reason|{{{1|}}}}}}|'''Reason:''' {{{reason|{{{1}}}}}}|<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}
</div>
</pre>


'''@ Walkazo:''' That sounds fine to me. {{user|Coincollector}}
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this article be '''rewritten'''.
</div>
----
However, once the proposal passes, the <nowiki>{{rewrite}}</nowiki> template will read as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten'''{{#if:{{{reason|{{{1|}}}}}}|<nowiki/> for the following reason(s): {{{reason|{{{1}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}}.</small>
</div>
</pre>


@Stuff regarding infobox usage: I'm not going to include that into this Writing Guideline since that is a rule that deals with the template specifically. Such rules of usage should be mentioned on the template page itself. The only reason why I mention how to use the Newsubject templates is because those template are specifically for this purpose.<br>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
@Walkazo's suggestion to the wording: I'll amend all the changes you suggested except for the  "''Once the project has been released for a reasonable amount of time and more content has been added''" suggestion. I don't think either case is necessary to do a rewrite. Sometime the amount of content is fine as it is and asking for more can sometimes prove to be difficult. Using the words "reasonable time" is unnecessarily restrictive. If the article has all the information it needs, then why wait longer to remove the template? Plus what defines a "reasonable" amount of time? I should clarify though; rewrite in cases like this only refers to changing future tense in present tense (will appear>appears in) and removing unneeded references. I will expand on this more when I make the amendments.--{{User|Knife}} 11:16, 29 November 2011 (EST)
It has been requested that this article be '''rewritten''' for the following reason(s): <reason(s)>.<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this article}}.</small>
</div>
----
And another thing—the <nowiki>{{rewrite-expand}}</nowiki> template currently reads as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' and '''expanded''' to include more information. {{#if:{{{reason|{{{1|}}}}}}|'''Reason:''' {{{reason|{{{1}}}}}}|<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}
</div>
</pre>


Okay, made some changes. Supporters, please review them. I basically just differentiated vaporware and cancelled games (based on Glowsquid's proposal) and added a section for revision help.--{{User|Knife}} 23:56, 29 November 2011 (EST)
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this article be '''rewritten''' and '''expanded''' to include more information.
</div>
----
However, once this proposal passes, the <nowiki>{{rewrite-expand}}</nowiki> will read as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' and '''expanded''' to include more information.{{#if:{{{reason|{{{1|}}}}}}|<nowiki/> for the following reason(s): {{{reason|{{{1}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}} by filling in the missing details.</small>
</div>
</pre>


:The changes are good, but I disagree with your decision to not include anything about the infoboxes. While the infoboxes ''do'' have their own sets of rules on the pages, this particular aspect of their use is ''directly related to'' upcoming/new releases. Dealing with infoboxes (or leaving them alone) is part of writing about upcoming games, and since different things are being done regarding the infoboxes, an outline for those specific procedures would be handy on a Writing Guideline. Why hope that users will happen to visit infobox pages and find out what to do when you could easily present them the info in a couple lines of text, laid out nice and simple? There's no rule against only describing writing policies in one page and no where else - on the contrary, many policy pages ''have'' overlapping content, and that's a good thing. It's not like it'll be a huge essay about general infobox usage, so what's the harm? - {{User|Walkazo}}
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
::A specific suggestion regarding infoboxes: we would probably benefit from a note somewhere about changing the images on infoboxes after the games release, as I don't believe that's official policy, and it could use some clarification. {{User|Bop1996}}
It has been requested that this article be '''rewritten''' and '''expanded''' to include more information for the following reason(s): <reason(s)>.<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this article}} by filling in the missing details.</small>
:::Again I agree with Walkazo. Abstain from this suggestion means you're leaving this in half-way, Knife. This is ''also'' part of the upcoming project, And I'm not talking the infobox itself, it's the information of the infobox that likewise is part of the context. At Bop1996, what do you mean exactly? In my experience, I see that some pictures are changed often when a new game is released. But not always... For example, Princess Daisy's picture has been never changed to this point, similar to Waluigi's. Additionally, I dunno really, but it seems there is a rule about not adding pictures of characters alongside other objects that may distract the prime subject... for example: the picture of Metal Mario of Mario Kart 7 which is new but it cannot be used by these circumstances. {{user|Coincollector}}
</div>
::::Recently, when we've had new high-quality artworks of characters like, Peach, Mario, Toad, etc, people seem to just replace the artwork when they feel like it. MeritC, I believe, has been reverting these changes until the games release, and I started doing the same for the same reasons. However, this isn't in any policy currently, but since we're discussing infoboxes and upcoming content, I figured it would be a good idea to mention that we aren't supposed to change the infobox images until the game they come from has released. We don't have to change it when the game releases if the artwork isn't better, but if we agree to change it, it should wait until after the game releases, basically. {{User|Bop1996}}
----
:::Hmmm... MeritC told me the same thing and apparently that discussion came from the forums (Again I'm not sure). Going to your point, I guess it needs to be applied but looking how we are currently with the images, I think we should clarify that a bit more. But, again it can be done - At least if Knife approves this or else we have to do this by ourselves. {{User|Coincollector}}
Lastly, the <nowiki>{{rewrite-remove}}</nowiki> currently reads as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' to have <u>{{{content|{{{1|content<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}}}}}</u> '''removed''' for the following reason(s): {{{reason|{{{2|???<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}}}}}{{#if:{{{date|{{{3|}}}}}}|<nowiki/> (tagged on {{{date|{{{3}}}}}})}}
</div>
</pre>


Sorry for the late response. If you all really feel it's necessary to mention it here, that's fine. However, I'm not 100% sure what you want me to put in. It would probably be best for someone who is more familiar with the userbox usage to write that section of the guideline. You can either add a section for it on draft or post raw coding into this comments section (for non-sysops). If no one comes up with a draft by then, we can put in later assuming no one opposes adding this information.--{{User|Knife}} 20:24, 4 December 2011 (EST)
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this article be '''rewritten''' to have <u>content</u> '''removed''' for the following reason(s): ???
</div>
----
However, once this proposal passes, the <nowiki>{{rewrite-remove}}</nowiki> will read as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' to have {{#if:{{{content|{{{1|}}}}}}|<u>{{{content|{{{1}}}}}}</u>|content}} '''removed'''{{#if:{{{reason|{{{2|}}}}}}|<nowiki/> for the following reason(s):{{{reason|{{{2}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{3|}}}}}}|<nowiki/> (tagged on {{{date|{{{3}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}} by removing the unnecessary details.</small>
</div>
</pre>


==New Features==
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
===Music Files===
It has been requested that this article be '''rewritten''' to have content '''removed''' for the following reason(s): <reason(s)>.<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this article}} by removing the unnecessary details.</small>
I read one of Bop1996's comments in the previous proposal of mine and he had a better idea, to make a sub page for music files. (So credit to him for the idea). So I decided to delete the other proposal and restart it and going with his idea instead.
</div>
----
That will be a perfect idea to make the <nowiki>{{rewrite}}</nowiki> template and its variations as more specific as the {{tem|media missing}} and {{tem|unreferenced}} templates. That way, we'll be able to add smaller text to the remaining [[:Category:Notice templates|notice templates]] in the future.


'''Proposer:'''{{User|Tails777}}<br>
'''Proposer''': {{User|GuntherBayBeee}}<br>
'''Deadline:'''December 10, 2011 23:59 GST<br>
'''Deadline''': <s>December 23, 2024, 23:59 GMT</s> Extended to December 30, 2024, 23:59 GMT


====Support====
====Support====
#{{User|Tails777}} Per proposal.
#{{User|GuntherBayBeee}} Per proposal
#{{User|B.wilson}} If you say the music would be located at a subpage named ''Music'', like for the article [[Mario]], ''Mario/Music'', I'd say it's an adequate idea.
#{{User|Bop1996}} It would cut down on clutter in the music sections, just like having huge Galleries on separate pages does.
#{{User|Bowser's luma}} Pages would load faster. A yes from this impatient user.
#{{User|Jazama}} Per all
#{{User|Lakituthequick}} Good idea, we can ask [[User:Porplemontage|Porplemontage]] to create a namespace for music (like we have a gallery namespace)
#{{User|RandomYoshi}} — Per all.


====Oppose====
====Oppose====
#{{User|New Super Yoshi}} I think just having a list of music is a bad idea. People can look it up on YouTube and people need a player to listen to these and it would be easier to find the song they are looking for on YouTube anyway and it would take a lot of work to upload every Mario song in the series.
#{{User|Altendo}} As far as I can tell, the proposal that was linked added parameters that allowed what was supposed to be referenced to be referenced. This one simply adds a subtitle to the bottom of each template. "Be more specific" does not mean saying general information and helpful links, but rather exactly what needs to be done; in terms of that, the existing templates not only all already have parameters, but [[MarioWiki:Proposals/Archive/61#Discourage drive-by templating|filling them out is enforced]]. As [[User:Nightwicked Bowser|Nightwicked Bowser]] said, "Be more specific - Similar to [[MarioWiki:Proposals/Archive/61#Discourage drive-by templating|this proposal]], what exactly needs references must be specified in the template when putting it in the article. A parameter for this will still need to be added." This only adds a subtitle and does not make this "more specific". As for the changes, this is actually harmful in some way, as the <nowiki>(tagged on {{{date|{{{3}}}}}})</nowiki> tag will be added to the subtitle, rather than the main body, which could make it more confusing in my opinion. Feel free to update this and add in what "more specific" actually means, or just change this to "add subtitles" and change the location of <nowiki>(tagged on {{{date|{{{3}}}}}})</nowiki> to the main body, but until then, my vote is staying here.
#{{User|Toad85}} Per NSY.
#{{User|Mario}} Best to keep things simple with these improvement templates.
#{{User|Technetium}} Per Mario.


====Comments====
====Comments====
For the record, the previous proposal about Music Files can be found [[MarioWiki:Proposals/Archive#Music_files|here]]. - {{User|Walkazo}}


'''@ Tails777:''' Can you specify the title of your proposal? It's about the Sound files, but what's exactly the matter about them? {{user|Coincollector}}
Here's how I would fix some things:
 
First of all, the <nowiki>{{rewrite}}</nowiki> template currently reads as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten'''. {{#if:{{{reason|{{{1|}}}}}}|'''Reason:''' {{{reason|{{{1}}}}}}|<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}
</div>
</pre>
 
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this article be '''rewritten'''.
</div>
----
However, once the proposal passes, the <nowiki>{{rewrite}}</nowiki> template will read as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten'''{{#if:{{{reason|{{{1|}}}}}}|<nowiki/> for the following reason(s): {{{reason|{{{1}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}}.</small>
</div>
</pre>
 
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this article be '''rewritten''' for the following reasons:<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this article}}.</small>
</div>
----
And another thing—the <nowiki>{{rewrite-expand}}</nowiki> template currently reads as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' and '''expanded''' to include more information. {{#if:{{{reason|{{{1|}}}}}}|'''Reason:''' {{{reason|{{{1}}}}}}|<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}
</div>
</pre>
 
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this article be '''rewritten''' and '''expanded''' to include more information.
</div>
----
However, once this proposal passes, the <nowiki>{{rewrite-expand}}</nowiki> will read as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' and '''expanded''' to include more information{{#if:{{{reason|{{{1|}}}}}}|<nowiki/> for the following reason(s): {{{reason|{{{1}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}} by filling in the missing details.</small>
</div>
</pre>
 
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this article be '''rewritten''' and '''expanded''' to include more information for the following reasons:<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this article}} by filling in the missing details.</small>
</div>
----
Lastly, the <nowiki>{{rewrite-remove}}</nowiki> currently reads as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' to have <u>{{{content|{{{1|content<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}}}}}</u> '''removed''' for the following reason(s): {{{reason|{{{2|???<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}}}}}{{#if:{{{date|{{{3|}}}}}}|<nowiki/> (tagged on {{{date|{{{3}}}}}})}}
</div>
</pre>
 
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this article be '''rewritten''' to have <u>content</u> '''removed''' for the following reason(s): ???
</div>
----
However, once this proposal passes, the <nowiki>{{rewrite-remove}}</nowiki> will read as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' to have {{#if:{{{content|{{{1|}}}}}}|<u>{{{content|{{{1}}}}}}</u>|content}} '''removed''' {{#if:{{{reason|{{{2|}}}}}}|<nowiki/> for the following reasons:{{{reason|{{{2}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{3|}}}}}}|<nowiki/> (tagged on {{{date|{{{3}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}} by removing the unnecessary details.</small>
</div>
</pre>
 
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this article be '''rewritten''' to have content '''removed''' for the following reason(s):<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this article}} by removing the unnecessary details.</small>
</div>
 
This should fix some things, and I also recommend you change the title or at least context of this proposal. If so, then I might change my vote. [[User:Altendo|Al]][[User talk:Altendo|ten]][[Special:Contributions/Altendo|do]] 19:58, December 9, 2024 (EST)
:I {{plain link|https://www.mariowiki.com/index.php?title=MarioWiki:Proposals&diff=prev&oldid=4457576|fixed this problem}} for you. How does it look? {{User:GuntherBayBeee/sig}} 09:40, December 10, 2024 (EST)
 
===Decide what to do with Template:Move infobox===
A while ago (November 4th, specifically), I created [[Template:Move infobox]]. After all, we had templates for essentially all the Browse tabs on the wiki sidebar, except for moves. There WERE templates about specific types of moves, such as [[Template:M&L attack infobox]], but no general template in the same vein as items, characters, species, games, locations, etc.
 
I discussed it on the Discord briefly, nobody said no, and a bit of feedback later about how it should look and what it should have, I created it. It has since been applied to exactly four pages at the time of writing, half of which I was the one to apply it to. In hindsight, this could've used with a proposal instead of me just making it, so here's a belated one.
 
Should we keep '''Template:Move infobox''' around? If we do keep it, is it good as is, or does it need changes?
 
'''Proposer''': {{User|EvieMaybe}}<br>
'''Deadline''': January 1st, 2025, 23:59 GMT


'''@Coincollector''' Nothing is wrong about them, I just find it would be better to put the music on a sub page rather than the game's page. Like what others have said, like gallery pages. {{User|Tails777}}
====Keep Move infobox, as is====
#{{User|Sparks}} I can see this template working really well for moves that aren't in every ''Mario'' game, like [[Spin]]. This has lots of potential!
#{{User|Nintendo101}} Per proposal.
#{{User|Camwoodstock}} We don't see why not--having a dedicated Moves infobox could come in handy, especially if we get any more Mario RPGs in the wake of the weird little renaissance period we've been getting with the back-to-back-to-back SMRPG remake, TTYD remake, and release of Brothership. Per proposal.
#{{User|Pseudo}} Per proposal.
#{{User|Technetium}} Per proposal.


I would only support this if we use YouTube Videos not Music Files because more people like me can listen to the music.--{{User|New Super Yoshi}} 11:37, 7 December 2011 (EST)
====Keep Move infobox, but with changes====


:'''@ New Super Yoshi:''' The wiki doesn't use Youtube videos for the articles. See [[Mariowiki:Help]] for the reason. {{user|Coincollector}}
====Delete Move infobox====


I don't see a good reason. Anyway music and video flies are taken from YouTube so what is the point. -{{User|New Super Yoshi}}
====Move infobox Comments====
Considering the nature of the attack infoboxes, wouldn't it be weird to have moves all in purple but a Mario & Luigi attack use yellow and green and a Paper Mario attack use white and green? Should there be variants of the Move infobox to match the color schemes of existing templates? If an article is covering multiple related moves, how will the infobox work? (ex. [[Handstand]], [[Cap Throw]], [[Roll]], [[Slide Kick]]... there's more of these than I thought). What happens when a move is referenced in somewhat less "move-y" ways? Okay, that last one is kinda strange, but basically I mean "dashing" in Super Mario Run is just a fancy animation, Mario & Luigi Dream Team has an animation where Giant Luigi crouches (with posing and skidding clearly meant to be a platformer callback), to slide under an attack. Do these instances get incorporated into the infobox? Continuing the train of thought, what about sports games? Yoshi can Flutter Jump as his special action on Mario & Sonic games. Does that count as a method of input for a Flutter Jump? [[User:Salmancer|Salmancer]] ([[User talk:Salmancer|talk]]) 21:35, December 19, 2024 (EST)
:that's a lot of very interesting questions!
:*i went with purple to set it apart from the already taken light red (game), green and white (character), blue (level), pink (location), grey (item) and navy/grey (species) infoboxes. changing the color could be a good idea.
:*as for sorting which moves "count" or not, we have to decide these things for other types of subject too, after all, and they get infoboxes. it's a valid concern, though! {{User:EvieMaybe/sig}} 15:09, December 20, 2024 (EST)


:We had various proposals talking about inserting Youtube videos to articles, which all of them failed, mostly because Youtube videos are very informal and because of that contrast greatly with the articles' essential function. {{user|Coincollector}}
===Allow blank votes and reclassify them as "per all"===
There are times when users have nothing else to add and agree with the rest of the points. Sure, they can type "per all", but wouldn't it be easier to not to have to do this?


==Removals==
Yeah sure, if the first oppose vote is just blank for no reason, that'll be strange, but again, it wouldn't be any more strange with the same vote's having "per all" as a reasoning. I've never seen users cast these kinds of votes in bad faith, as we already have rules in place to zap obviously bad faith votes.
''None at the moment.''
 
This proposal wouldn't really change how people vote, only that they shouldn't have to be compelled to type the worthless "per all" on their votes.
 
'''Proposer''': {{User|Mario}}<br>
'''Deadline''': January 1, 2025, 23:59 GMT
 
====Blank support====
#{{User|Mario}} Per all.
#{{User|Ray Trace}} Casting a vote in a side is literally an action of endorsement of a side. We don't need to add verbal confirmation to this either.
#{{User|PopitTart}} <small>(This vote is left blank to note that I support this option but any commentary I could add would be redundant.)</small>
#{{User|Altendo}} <small>(Look at the code for my reasoning)</small><!---It might not seem annoying, but over time, or answering multiple proposals at once, it can start putting stress. Copy-pasting can be done, but it is just much easier to not type anything at all.---->
#{{User|FanOfYoshi}}
#{{User|OmegaRuby}} While on the outset it may seem strange to see a large number of votes where people say "per all" and leave, it's important to understand that the decision was made because the user either outright agrees with the entire premise of the proposal, or has read discussion and points on both sides and agrees more with the points made by the side they choose. And if they really ''are'' just mindlessly voting "per all" on proposals with no second thought, we can't police that at ''all.'' <small>(Doing so would border on FBI-agent-tech-magic silliness and would also be extremely invading...)</small> <!---Silent per all.---->
#{{User|Shy Guy on Wheels}} I've always thought of not allowing blank votes to be a bit of a silly rule, when it can so easily be circumvented by typing two words. I think it's better to assume good faith with voting and just let people not write if they don't have anything to add, it's not as if random IPs are able to vote on this page.
#{{user|TheDarkStar}} - Dunno why I have to say something if I agree with an idea but someone's already said what I'm thinking. A vote is a vote, imo.
#{{user|Ninja Squid}} Per proposal.
#{{User|Tails777}} It's not like we're outright telling people not to say "Per all", it's just a means of saying you don't have to. If the proposal in question is so straight forward that nothing else can be said other than "Per proposal/Per all", it's basically the same as saying nothing at all. It's just a silent agreement. Even so, if people DO support a specific person's vote, they can still just "Per [Insert user's name here]". I see no problem with letting people have blank votes, especially if it's optional to do so in the first place.
 
====Blank Oppose====
#{{user|Doc von Schmeltwick}} - Honestly? I'd prefer to get rid of "per all" votes since they're primarily used for the "I don't/like this idea" type of thing that has historically been discouraged. If you don't care enough to explain, you don't care enough to cast IMO.
#{{User|Technetium}} I don't think typing "per all" is that much of an annoyance (it's only two words), and I like clearly seeing why people are voting (for instance, I do see a difference between "per proposal" and "per all" - "per all" implies agreeing with the comments, too). I just don't think this is something that needs changing, not to mention the potential confusion blank votes could cause.
#{{User|Camwoodstock}} Maybe we're a little petty, but we prefer a "per all" vote to a blank one, even if "per all" is effectively used as a non-answer, because it still requires that someone ''does'' provide an answer, even if it's just to effectively say "ditto". You know what to expect with a "per all" vote--you don't really get that information with a fully blank vote.
#{{User|Ahemtoday}} {{color|white|Forgive me for the gimmicky formatting, but I want to make a point here — when you see a blank oppositional vote, it's disheartening, isn't it? Of course, it's always going to be that way when someone's voting against you, but when it doesn't come with any other thoughts, then you can't at all address it, debate it, take it into account — nothing. This also applies to supporting votes, if it's for a proposal you oppose. Of course, this is an issue with "per all" votes as well. I don't know if I'd go as far as Doc would on that, but if there's going to be these kinds of non-discussion-generating votes, they can at least be bothered to type ''two words''.}}
#{{User|Jdtendo}} Per all <small>(is it too much to ask to type just two words to explicitely express that you agree with the above votes?)</small>
#{{User|Axii}} Requiring people to state their reason for agreeing or disagreeing with a proposal leads to unnecessary repetition (in response to Doc). Letting people type nothing doesn't help us understand which arguments they agreed with when deciding what to vote for. The proposer? Other people who voted? Someone in particular, maybe? Maybe everyone except the proposer? It's crucial to know which arguments were the most convincing to people.
#{{User|Pseudo}} Per Technetium, Camwoodstock, and Axii.
#{{User|Hooded Pitohui}} I admit this vote is based on personal preference as any defensible reasoning. To build on Camwoodstock and Ahemtoday's points, though, the way I see it, "per all" at least provides ''some'' insight into what has persuaded a voter, if only the bare minimum. "Per all" is distinct at least from "per proposal", suggesting another voter has persuaded them where the original proposal did not by itself. A blank vote would not provide even that distinction.
#{{User|Mister Wu}} Asking for even a minimal input from the user as to why they are voting is fundamental, it tells us what were the compelling points that led to a choice or the other. It can also aid the voters in clarifying to themselves what they're agreeing with. Also worth noting that the new editors simply can't know that blank means "per all", even if we put it at the beginning of this page, because new editors simply don't know the internal organization of the wiki. Blank votes would inevitably be used inappropriately, and not in bad faith.
#{{user|DesaMatt}} Per all and per everyone and per everything. Per.
 
====Blank Comments====
I don't think banning "per all" or "per proposal" is feasible nor recommended. People literally sometimes have nothing else to add; they agree with the points being made, so they cast a vote. They don't need to waste keystrokes reiterating points. My proposal is aiming to just streamline that thought process and also save them some keystrokes. {{User:Mario/sig}} 20:34, December 17, 2024 (EST)
:I think every sort of vote (on every level, on every medium) should be written-in regardless of whether something has been said already or not; it demonstrates the level of understanding and investment for the issue at hand, which in my opinion should be prerequisite to voting on any issue. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 20:53, December 17, 2024 (EST)
::There is no way to actually determine this: we are not going to test voters or commenters their understanding of the subject. Someone can read all of the arguments and still just vote for a side because there's no need to reiterate a position that they already agree with. {{User:Ray Trace/sig}} 20:55, December 17, 2024 (EST)
:::My personal belief is that "test[ing] voters or commenters their understanding of the subject" is exactly what should be done to avoid votes cast in misunderstanding or outright bandwagoning. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 23:06, December 17, 2024 (EST)
::::My personal view is that a change like the one you are suggesting potentially increases the  odds of inexperienced or new users feeling too intimidated to participate because they feel like they do not have well articulated stances, which would be terrible. I think concerns about "bandwagoning" are overstated. However, more pressingly, this proposal is not even about this concept and it is not even one of the voting options, so I recommend saving this idea for another day. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 23:32, December 17, 2024 (EST)
:{{@|Mario}} I agree. Banning people from saying that in proposals is restricting others from exercising their right to cast a vote in a system that was designed for user input of any time. I'd strongly oppose any measure to ban "per" statements in proposals. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 00:11, December 18, 2024 (EST)
 
Technetium: I understand, but blank votes are a fairly common practice in other wikis, and it's clearly understood that the user is supporting the proposal in general. {{User:Mario/sig}} 20:36, December 17, 2024 (EST)
:Fair point, I didn't know that. Not changing my vote just yet, but I'll keep this in mind as the proposal continues. [[User:Technetium|Technetium]] ([[User talk:Technetium|talk]]) 20:48, December 17, 2024 (EST)
:There's a lot of variation in how other wikis do it. WiKirby, for example, doesn't even allow "per" votes last I checked. {{User:Hewer/sig}} 04:13, December 18, 2024 (EST)
 
I'm not really much of a voter, but I'm of the opinion "it's the principle of the matter". Requiring ''a'' written opinion, of any kind, at least encourages a consideration of the topic. [[User:Salmancer|Salmancer]] ([[User talk:Salmancer|talk]]) 21:35, December 19, 2024 (EST)
 
===Stop integrating templates under the names of planets and areas in the ''Super Mario Galaxy'' games===
{{early notice|December 25}}
The aims of this proposal is to repeal [[MarioWiki:Proposals/Archive/69#Decide how to handle conjectural sections about Super Mario Galaxy planets/areas|this one]] that passed earlier this year. I will reiterate my position here:
<blockquote>The planetary bodies in galaxies do not just "lack" publicly accessible names - they are straight up not supposed to have names. The Shogakukan guidebook for ''Mario Galaxy'' does not give planets name. The game does not give planets name. The instruction booklet does not give planets name. The only "source" that applies discrete names for planets are from the developers and we have no reason to think these were intended to be the planets. These galaxy articles are generally a bit outdated, and I think the mistake in the first place was suggesting that some of the planets have real names "except where otherwise noted." They largely do not. I think it would would healthier to recognize that they are just different sections of a greater whole, much like areas in courses for the earlier 3D games, and apply titles accordingly.</blockquote>
To elaborate on my perspective, I think using dev data to provide names for these planets is completely fine, and I understand the desire to do so. Citing the Prima Games guidebooks for potential names for these areas is fine. That is not what this proposal is about. Rather, integrating the ''templates'' themselves - be it for conjectural or dev data-derived names - underneath the individual headers for each planet, in my view, looks very poor, as you can see here for [[Yoshi Star Galaxy#Planets|Yoshi Star Galaxy]] and [[Honeyhive Galaxy#Planets/Areas|Honeyhive Galaxy]]. They are detractingly eye-catching and break these articles without substantive benefit. I think having a nonintrusive note at the top or bottom of these articles - as was the case before the proposal I link to above passed - is perfectly sufficient and healthier for these articles.
 
I provide two options:
#'''Support: Do not put conjectural and dev-data name templates beneath the names of individual planets and areas in  the ''Super Mario Galaxy'' games''': This is a full repeal of the proposal I link to above.
#'''Oppose: Change nothing'''
 
'''Proposer''': {{User|Nintendo101}}<br>
'''Deadline''': January 1, 2025, 23:59 GMT
 
====Support: Do not put templates underneath the name's of planets and areas====
#{{User|Nintendo101}} Per proposal.
#{{User|1468z}} Per proposal.
#{{User|Waluigi Time}} The previous solution looked a lot nicer. I also agree with Nintendo101 that we should rethink how we approach planet names in general. They don't necessarily "need" names any more than specific portions of levels in other games do.
#{{User|Jdtendo}} I still don't agree with the "planets are not supposed to have names" argument, but I do agree that having templates beneath every section heading is excessive.
#{{User|Camwoodstock}} Per all, especially Waluigi time. The overall assumption that the planets have names unless otherwise stated feels like the consequence of a decision made very, very early on into the wiki, that's just kind of gone unquestioned or unnoticed until very recently. This won't stop that particular case of WikiJank™ completely, but it's a step in the right direction.
#{{User|Sparks}} Per all.
#{{User|EvieMaybe}} if all the names are unofficial, then we only need to say it once. if there's an official name, we can just say "all names are unofficial unless specified" and specify in the one planet that has a name (is there any planets with names even???). having the template on each individual section is both ugly and inefficient
#{{User|Mario}} Yeah, the setup before this was satisfactory. Per Evie, but I also agree with Waluigi Time that we probably don't need to require naming these parts of the level either.
#{{User|Ray Trace}} I always thought assigning these objects meant to be part of the environment conjectural templates has always struck me as odd and I don't know why only Super Mario Galaxy gets singled out out of all games. We don't name the rooms the Mario Party minigames take place in.
#{{User|Tails777}} I was sincerely confused when I saw the templates put back on the various galaxy articles and questioned "Why? It was better beforehand." Per all.
#{{User|Hooded Pitohui}} In the longer-term, WT and Nintendo101 bring up points which ought to be considered. In the shorter term, this would be a beneficial first step to de-cluttering these sections for better readability.
#{{User|Ninja Squid}} Per all.
#{{User|Technetium}} Per Nintendo101, Waluigi Time, and Porple's comment below.
#{{User|MCD}} Per N101, WT and Porple below. I also agree our attitude on what counts as "conjectural" when it comes to naming planets needs a rethink, i.e. it's not conjecture to call the planet the player starts on the "starting planet" because that's just a factual description. (Also, why does [[Starting Planet]] just redirect to a random galaxy? lol)
 
====Oppose: Keep the templates====
#{{User|Ahemtoday}} I'm opposing this proposal ''as currently slated to be implemented'' — as in, just removing [[Template:Conjecture]] and [[Template:Dev data]] from these sections and leaving it at that. These need to be marked, and I don't feel that an "unless otherwise noted" disclaimer is an elegant way to do that. However. There is a way of accomplishing this that I ''would'' be amenable to: replacing those templates with [[Template:Conjectural]] or a new dev data equivalent to it. This is the same way our glitch pages do it, for exactly the same reason you want to get rid of these templates on the galaxy pages. I think it makes perfect sense to use this convention here as well to solve this problem.
 
====Comments on the planet template proposal====
I agree that we don't need the repeated templates, and the whole naming situation of the planets is a bit odd. Rather than giving the planets capitalized "names" (e.g. "Starting Planet") and noting them as conjectural, they should just be described in sentence case, at which point it should be somewhat obvious that it's a description and not a "name". For example, section heading "Starting planet" and text "The starting planet has..." You could do a single {{tem|conjecture|2=subsections=yes}} under the "Planets" heading if you really wanted to, but I think if we removed all the inappropriate capitalization then even that wouldn't be necessary. --{{User:Porplemontage/sig}} 20:11, December 19, 2024 (EST)
 
===Set Vector-2010 to the default wiki skin===
This proposal is about setting the 2010 [[mw:Skin:Vector|Vector]] as the default wiki skin ([https://web.archive.org/web/20160207064154/https://upload.wikimedia.org/wikipedia/foundation/4/44/Logo_new-vector_screenshot.png screenshot here]) for desktop users, with the focus being on people who are new to wikis in particular, while obviously keeping the existing MonoBook skin as an option. What made me think to create this proposal is when I made a [[Talk:Main Page]] proposal about the to-do list tasks and how they are more accessible than clicking the "Wiki maintenance" on the sidebar, I had to uncomfortably squint to find "Wiki maintenance" on the wiki sidebar. But Vector-2010 has the sidebar links slightly larger and a bit more spaced out. With the existing interface, there could be some who may struggle to find options listed on the sidebar.
 
While we're clearly different from Wikipedia (that's why I'm not Vector-2022, since it'd be too much of a departure and likely uncomfortable for several), I do want to refer to [http://web.archive.org/web/20180213165624/https://blog.wikimedia.org/2010/05/13/a-new-look-for-wikipedia/ this page], which summarizes why Wikipedia transitioned to it. Though it is vague, they cite accessibility as the reason, which I think this wiki has been taking steps toward doing.
 
I'll cite my reasons for preferring Vector and applying this to possible people who are visiting a wiki for the first time. The text is larger, which is especially important for larger screen monitors, some of the lesser used tabs are collapsible on the sidebar, summarizing the most commonly used options, and the user links at the top right are also more noticeable and less close to the body of the article where the content is read.
 
Though it could take time getting used to the Edit button being on the right (not to mention the search button), the button is at least larger, making it more usable on even lower quality screen monitors, and I like how it's separate from the Page and discussion options, meaning that options that involve viewing articles are on the left while options that involve editing or changing the page in some form are on the right.


==Changes==
If this proposal passes and others don't like the change, they can always return to the MonoBook option in their [[Special:Preferences#mw-prefsection-rendering|preferences]].
===Change Navigation Templates Colors===
The navigation templates have a strange choice of colors. Some are hideous. The Mario Wiki could be more beautiful and organizated by changing game Navigation Templates by series (''Super Mario'' series in red and ''DK'' in brown, for example). It will make the Navigation Templates less confusing and easier to understand. See [[Mario]] page Navigation Templates: so messy.


'''Proposer''': {{User|Ultra Koopa}}<br>
'''Proposer''': {{User|Super Mario RPG}}<br>
'''Deadline''': December 11, 2011, 23:59 GMT
'''Deadline''': January 1, 2025, 23:59 GMT


====Support====
====Support====
#{{user|Ultra Koopa}} Per my proposal.
#{{User|Super Mario RPG}} Per.
#{{User|ThePremiumYoshi}} - Yeah, it's better to change the color of some Templates. While others are fine, there are some Templates with horrid color, like the Super Mario Kart Template which is... PINK! This color totally doesn't fit SMK. Per proposal.
#{{User|Magikrazy51}} Per proposal. Pink would better suit the Super Princess Peach template, not the Nintendo DS Games template. That would be better as red or blue.
#{{User|New Super Yoshi}} Some of the Colors just don't work right. Per All.
#{{User|Bowser's luma}} Good idea - trading psychadellia for functionality.
#{{User|Jazama}} Per all
#{{User|RandomYoshi}} — Per Magikrazy51.
#{{User|Lakituthequick}} We need some cleanup, yes.


====Oppose====
====Oppose====
#{{User|Knife}} &ndash; I don't really disagree with the premise, but I feel your proposal isn't specific enough to actually do something. What I think you should do is make a draft page detailing navigation color scheme and put up a Writing Guideline proposal.
#{{User|Camwoodstock}} Admittedly, this vote is largely a matter of preference--we just don't like Vector that much--but we can't think of any real reason to switch to Vector 2010 as the default over the current Monobook beyond the mentioned text spacing; while that is a nice boon, we personally find the weird gradient buttons for the various tabs up top a little grating looking, and we're a fan of the more compact design that Monobook provides--though, this is likely a byproduct of our personal preference for more neatly packed web design. And uh, the less said about the other two options (Vector 2022, and. Timeless. <s>Which is the most dated theme possible, namely to mid-2010s mobile web design.</s>), the better. If you like Vector 2010, that's great, and we're fine with that! Heck, if anyone likes Vector 2022 or Timeless, that's cool too, and more power to them! Variety is the spice of life, after all. But switching it to the default is something that should not be taken lightly, and the reasons for a switch in this proposal feel a little too loosey-goosey for us, we're sorry.
#{{user|Coincollector}} - Partly oppose, backing up Knife's comment. Also see my comment.
#{{User|DryBonesBandit}} Per Camwoodstock.
#{{User|Bop1996}} Per Knife.
#{{User|Nintendo101}} I like how MonoBook looks a little more than Vector. It is what I am comfortable with. If it ain't broke, don't fix it.
#{{User|Drago}} Per Nintendo101. I actually prefer the smaller text of Monobook since you can see more of the page at once. I also want to point out that although logged-in users like us can change the skin in preferences, we'd still be forcing the change on logged-out users.
#{{User|Ahemtoday}} Per Drago.
#{{User|Technetium}} Per Nintendo101 and Drago. I just don't see any reason to make this change.
#{{User|Altendo}} I'm saying this as a Vector-2010 skin user, and I'll say that people have their preferences. I live Vector-2010 because that is how Wikipedia at least used to look before they switched to Vector (2022); On Wikipedia, Vector was renamed to Vector legacy (2010), while Vector 2022 is named Vector (2022). Although I do prefer Vector-2010, I know a lot of people that prefer Monobook, and even if not, this can be changed in the preferences. No need to change the default skin. I get that IPs can't change their appearance, but aside from that, users can, and what they see doesn't have to be default on the wiki. Everyone can change what they specifically see.


====Comments====
====Comments====
Actually I think that ''some'' of the templates need a better color scheme. Change color scheme because they are colored in a "weird" manner and some whose colors don't allow to read clearly. Fine examples are the {{tem|bee}}, {{tem|MK7}}, {{tem|Fuzzy}}, {{tem|MP3}}, among a vast quantity of others that would make the list considerably long. On the other hand I agree with Knife that the templates require a better maintenace, following a firm writing guideline for the creation of templates. However this is a discussion that has long been even in our discussions in the boards. I suggest some of you to see my [[MarioWiki:Proposals/Archive#Remove customizable infoboxes|past proposal]] that overlaps with this topic. However, not all templates look so bad as to need a more proper color, like those used for the consoles - which they follow certain guideline to color the template according to the topic, although doesn't work for everything, and some of these really need a better color coding, for example, the ''Mario'' series-related templates and the Donkey Kong-related templates.  
{{@|Camwoodstock}} That is true that it's a major change. It's based mainly upon impression from newcomers from them seeing a more prominent edit tab, slightly larger text size, and other minor details like tab names that are easier to read (including a collapsible feature for the lesser used tab). The skin change was based on old Wikipedia research at the time (like how WikiLove was a result of their research). I have no strong feelings whether this passes or not. Although it's vague, since there's no way to tell the statistics (and the wiki's already successful at the moment), I still have a feeling it could help some, but to each their own. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 18:32, December 18, 2024 (EST)
{{user|Coincollector}}
:We feel like if anybody would be capable of providing any statistics on skin usage, it'd be Porple, but even then, we don't actually know if that's one of the things he tracks, and it feels a little silly to pester him over this of all things... ;p {{User:Camwoodstock/sig}} 18:55, December 18, 2024 (EST)
:@ '''Magikrazy51:''' The color of the DS' template was based in that japanese added some color-coding to their consoles: pink for the DS, light Bbue for the Wii, and red for the 3DS. {{user|Coincollector}}


:@ '''Knife''' I already have a draft presentation showing some colors for the Templates.{{Unsigned|Ultra Koopa}}
I'm okay with opposition, but in case of misunderstanding, this proposal isn't about personal preferences so much as what I believe to be a more ergonomic interface to a wider audience. I know we're not Wikipedia, but there's also the consideration that they've used the Vector skin longer than they had for MonoBook. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 13:45, December 19, 2024 (EST)
 
:If it's what "you believe", then it ultimately (and probably unavoidably) is about personal preferences. Anyway, another consideration is the fact that people often prefer what they're used to. I feel like how long this wiki has used its skin is more relevant than how long Wikipedia has. {{User:Hewer/sig}} 16:39, December 19, 2024 (EST)
You didn't link to it in your proposal, as far as I'm concerned it doesn't exist. Your first three days are up anyway so it's too late to implement a major change like that. As I said before, you should make a Writing Guideline (with a written policy to complement the template color examples). Even if this proposal passes, you won't really have the ability to do anything since it is so vague.--{{User|Knife}} 11:12, 8 December 2011 (EST)
::{{@|Hewer}} I suppose I'm overthinking the ergonomic interface. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 15:19, December 20, 2024 (EST)


==Miscellaneous==
==Miscellaneous==
''None at the moment''.
''None at the moment.''

Latest revision as of 14:14, December 25, 2024

Image used as a banner for the Proposals page
Current time:
Wednesday, December 25th, 21:31 GMT
Proposals can be new features, the removal of previously-added features that have tired out, or new policies that must be approved via consensus before any action is taken.
  • Voting periods last for two weeks, but can close early or be extended (see below).
  • Any autoconfirmed user can support or oppose, but must have a strong reason for doing so.
  • All proposals must be approved by a majority of voters, including proposals with more than two options.
  • For past proposals, see the proposal archive and the talk page proposal archive.

If you would like to get feedback on an idea before formally proposing it here, you may do so on the proposals talk. For talk page proposals, you can discuss the changes on the talk page itself before creating the TPP there.

How to

If someone has an idea about improving the wiki or managing its community, but feel that they need community approval before acting upon that idea, they may make a proposal about it. They must have a strong argument supporting their idea and be willing to discuss it in detail with other users, who will then vote on whether or not they think the idea should be implemented. Proposals should include links to all relevant pages and writing guidelines. Proposals must include a link to the draft page. Any pages that would be largely affected by the proposal should be marked with {{proposal notice}}.

Rules

  1. Only autoconfirmed users may create or vote on proposals. Anyone is free to comment on proposals (provided that the page's protection level allows them to edit).
  2. Proposals conclude at the end of the day (23:59) two weeks after voting starts (all times GMT).
    • For example, if a proposal is added at any time on Monday, August 1, 2011, the voting starts immediately and the deadline is two weeks later on Monday, August 15, at 23:59 GMT.
  3. Users may vote for more than one option, but they may not vote for every option available.
  4. Every vote should have a strong, sensible reason accompanying it. Agreeing with a previously mentioned reason given by another user is acceptable (including "per" votes), but tangential comments, heavy sarcasm, and other misleading or irrelevant quips are just as invalid as providing no reason at all.
  5. Users who feel that certain votes were cast in bad faith or which truly have no merit can address the votes in the comments section. Users can ask a voter to clarify their position, point out mistakes or flaws in their arguments, or call for the outright removal of the vote if it lacks sufficient reasoning. Users may not remove or alter the content of anyone else's votes. Voters can remove or rewrite their own vote(s) at any time, but the final decision to remove another user's vote lies solely with the wiki staff.
    • Users can also use the comments section to bring up any concerns or mistakes in regards to the proposal itself. In such cases, it's important the proposer addresses any concerns raised as soon as possible. Even if the supporting side might be winning by a wide margin, that should be no reason for such questions to be left unanswered. They may point out any missing details that might have been overlooked by the proposer, so it's a good idea as the proposer to check them frequently to achieve the most accurate outcome possible.
  6. If a user makes a vote and is subsequently blocked for any amount of time, their vote is removed. However, if the block ends before the proposal ends, then the user in question holds the right to re-cast their vote. If a proposer is blocked, their vote is removed and "(blocked)" is added next to their name in the "Proposer:" line of the proposal, which runs until its deadline as normal. If the proposal passes, it falls to the supporters of the idea to enact any changes in a timely manner.
  7. Proposals cannot contradict an already ongoing proposal or overturn the decision of a previous proposal that concluded less than four weeks (28 days) ago.
  8. If one week before a proposal's initial deadline, the first place option is ahead of the second place option by eight or more votes and the first place option has at least 80% approval, then the proposal concludes early. Wiki staff may tag a proposal with "Do not close early" at any time to prevent an early close, if needed.
    • Tag the proposal with {{early notice}} if it is on track for an early close. Use {{proposal check|early=yes}} to perform the check.
  9. Any proposal where none of the options have at least four votes will be extended for another week. If after three extensions, no options have at least four votes, the proposal will be listed as "NO QUORUM." The original proposer then has the option to relist said proposal to generate more discussion.
  10. If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
  11. If a proposal reaches its deadline and the first place option is ahead of the second place option by three or more votes, then the first place option must have over 50% approval to win. If the margin is only one or two votes, then the first place option must have at least 60% approval to win. If the required approval threshold is not met, then the proposal is extended for another week.
    • Use {{proposal check}} to automate this calculation; see the template page for usage instructions and examples.
  12. Proposals can be extended a maximum of three times. If a consensus has not been reached by the fourth deadline, then the proposal fails and cannot be re-proposed until at least four weeks after the last deadline.
  13. All proposals are archived. The original proposer must take action accordingly if the outcome of the proposal dictates it. If it requires the help of an administrator, the proposer can ask for that help.
  14. After a proposal passes, it is added to the appropriate list of "unimplemented proposals" below and is removed once it has been sufficiently implemented.
  15. If the wiki staff deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to cancel it at any time.
  16. Proposals can only be rewritten or canceled by their proposer within the first four days of their creation. However, proposers can request that their proposal be canceled by a staff member at any time, provided they have a valid reason for it. Please note that canceled proposals must also be archived.
  17. Unless there is major disagreement about whether certain content should be included, there should not be proposals about creating, expanding, rewriting, or otherwise fixing up pages. To organize efforts about improving articles on neglected or completely missing subjects, try setting up a collaboration thread on the forums.
  18. Proposals cannot be made about promotions and demotions. Staff changes are discussed internally and handled by the bureaucrats.
  19. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
  20. Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.

Basic proposal formatting

Below is an example of what your proposal must look like. If you are unsure how to set up this format, simply copy the following and paste it into the fitting section. When updating the bracketed variables with actual information, be sure to replace the whole variable including the square brackets, so "[insert info here]" becomes "This is the inserted information" and not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but the objective(s) of each voting option must be clearly defined. Such options should also be kept to a minimum, and if something comes up in the comments, the proposal can be amended as necessary. 

===[insert a title for your proposal here]===
[describe what issue this proposal is about and what changes you think should be made to improve how the wiki handles that issue]

'''Proposer''': {{User|{{subst:REVISIONUSER}}}}<br>
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

====[option title (e.g. Support, Option 1)]: [brief summary of option]====
#{{User|{{subst:REVISIONUSER}}}} [make a statement indicating that you support your proposal]

====[option title (e.g. Oppose, Option 2)]: [brief summary of option]====

====Comments ([brief proposal title])====

Autoconfirmed users will now be able to vote on your proposal. Remember that you can vote on your own proposal just like the others.

To vote for an option, just insert #{{User|[your username here]}} at the bottom of the section of your choice. Just don't forget to add a valid reason for your vote behind that tag if you are voting on another user's proposal. If you are voting on your own proposal, you can simply say "Per proposal".

Talk page proposals

Proposals concerning a single page or a limited group of pages are held on the most relevant talk page regarding the matter. All of the above proposal rules also apply to talk page proposals. Place {{TPP}} under the section's header, and once the proposal is over, replace the template with {{settled TPP}}. Proposals dealing with a large amount of splits, merges, or deletions across the wiki should still be held on this page.

All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{TPP discuss}}. Include a brief description of the proposal while also mentioning any pages affected by it, a link to the talk page housing the discussion, and the deadline. If the proposal involves a page that is not yet made, use {{fake link}} to communicate its title in the description. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links.

List of ongoing talk page proposals

Unimplemented proposals

Proposals

Break alphabetical order in enemy lists to list enemy variants below their base form, EvieMaybe (ended May 21, 2024)
Standardize sectioning for Super Mario series game articles, Nintendo101 (ended July 3, 2024)
^ NOTE: Not yet integrated for the Super Mario Maker titles, Super Mario Run, and Super Mario Bros. Wonder.
Create new sections for gallery pages to cover "unused/pre-release/prototype/etc." graphics separate from the ones that appear in the finalized games, Doc von Schmeltwick (ended September 2, 2024)
Add film and television ratings to Template:Ratings, TheUndescribableGhost (ended October 1, 2024)
Use the classic and classic-link templates when discussing classic courses in Mario Kart Tour, YoYo (ended October 2, 2024)
Clarify coverage of the Super Smash Bros. series, Doc von Schmeltwick (ended October 17, 2024)
Remove all subpage and redirect links from all navigational templates, JanMisali (ended October 31, 2024)
Prioritize MESEN/NEStopia palette for NES sprites and screenshots, Doc von Schmeltwick (ended November 3, 2024)
Stop considering reused voice clips as references (usually), Waluigi Time (ended November 8, 2024)
Allow English names from closed captions, Koopa con Carne (ended November 12, 2024)
^ NOTE: A number of names coming from closed captions are listed here.
Split off the Mario Kart Tour template(s), MightyMario (ended November 24, 2024)
Split major RPG appearances of recurring locations, EvieMaybe (ended December 16, 2024)
Use official alt text as a source, Koopa con Carne (ended December 24, 2024)

Talk page proposals

Split all the clothing, Doc von Schmeltwick (ended September 12, 2021)
Split machine parts, Robo-Rabbit, and flag from Super Duel Mode, Doc von Schmeltwick (ended September 30, 2022)
Make bestiary list pages for the Minion Quest and Bowser Jr.'s Journey modes, Doc von Schmeltwick (ended January 11, 2024)
Allow separate articles for Diddy Kong Pilot (2003)'s subjects, Doc von Schmeltwick (ended August 3, 2024)
Create articles for specified special buildings in Super Mario Run, Salmancer (ended November 15, 2024)
Expand and rename List of characters by game to List of characters by first appearance, Hewer (ended November 20, 2024)
Determine how to handle the Tattle Log images from Paper Mario: The Thousand-Year Door (Nintendo Switch), Technetium (ended November 30, 2024)
Merge False Character and Fighting Polygon/Wireframe/Alloy/Mii Teams into List of Super Smash Bros. series bosses, Doc von Schmeltwick (ended December 2, 2024)

Writing guidelines

None at the moment.

New features

Create a template to direct the user to a game section on the corresponding List of profiles and statistics page

This proposal aims to create a template that directs people to a game section on a Profiles and statistics list page, saving the user the step of having to scroll for it themselves. The reason why I'm proposing this is because as more Super Mario games are released, it becomes harder to comfortably find what you're searching for in the corresponding List of profiles and statistics page, especially for Mario, Bowser, and many other recurring subjects.

Another reason I think this would be valid is because of the fact that listing statistics in prose (e.g. 2/10 or 2 out of 10) looks off, especially if that can already be seen in the corresponding statistics box; in that case, the prose could change from "2/10" to something more vague like "very low stat", which isn't typically worded as such in the statistics box.

For example, let's say for Luigi in his appearance in Mario Sports Superstars, there could be a disclaimer either below the section heading or in a box to the side (we can decide the specifics when the proposal passes) that informs the reader that there's corresponding section that shows his profiles/statistics corresponding. Like such:

For profiles and statistics of Luigi in Mario Sports Superstars, see here.

The above message is not necessarily the final result (just a given example), but the disclaimer would definitely point the user to the appropriate game section on the profiles and statistics list page, should this pass.

Proposer: Super Mario RPG (talk)
Deadline: January 1, 2025, 23:59 GMT

Support

  1. Super Mario RPG (talk) Per.
  2. Hewer (talk) I don't really see a need to deliberately make prose less specific, but otherwise I like this idea, per proposal.

Oppose

Comments

@Hewer I don't think this would necessarily eliminate cases in which statistics are in prose, but it may be redundant if there's the link to conveniently access the statistics or profiles. Super Mario RPG (talk) 15:15, December 18, 2024 (EST)

Add an abbreviation template to type out full game titles

Based on the vote so far, this proposal may be eligible to close one week early. Please use {{proposal check|early=yes}} on December 25 at 23:59 GMT and close the proposal if applicable.

This proposal is about creating a template that it makes it easier to type out full game titles. Although The Legend of Zelda games generally have longer titles (and Zelda Wiki even has templates for some of their shorter titled games, like Hyrule Warriors, here), there have still been cases in which some game titles are uncomfortably long, such as Donkey Kong Country 3: Dixie Kong's Double Trouble! or Super Mario RPG: Legend of the Seven Stars, and while it may seem like not a big deal to some, it would be a small quality-of-life improvement if we could have a template where we input the abbreviation, and the output becomes the game title.

For example, {{a|M&LSS}} would result in Mario & Luigi: Superstar Saga (complete with italics formatting). Meanwhile, {{a|M&LSS|l}} to link to the game, outputting Mario & Luigi: Superstar Saga, although depending on who creates the template, it could be vice versa, like it links by default and {{a|M&LSS|n}} would prevent a link.

Since Super Mario has several releases, it may get difficult maintaining with all the abbreviations, and there have been cases where two games have shared the same abbreviation. (e.g. SMS for both Mario Sunshine and Mario Strikers). In that case, either {{a|SMS|2002}} (with the year of release) or a custom abbreviation (e.g. {{a|SMShine}}) would be needed (personally I'd prefer the latter).

Consider we already have similar templates for Princess Peach and Princess Daisy (i.e. {{Peach}} and {{Daisy}}), and both of their full titles (with "Princess" included) is a lot shorter than the two game titles in the first paragraph.

Proposer: Super Mario RPG (talk)
Deadline: January 1, 2025, 23:59 GMT

Support

  1. Super Mario RPG (talk) Per.
  2. Camwoodstock (talk) We don't see the harm in this, even if it would admittedly be fairly niche. The only real complaint we have is the lack of an additional parameter for changing the displayed text, so if we need to say something like "in the remake", we have to write that out the old-fashioned way.
  3. EvieMaybe (talk) might make some link-heavy pages lighter!
  4. Salmancer (talk) Words cannot express the relief that my fingers would feel if they never have to type out "Mario & Luigi: Bowser's Inside Story + Bowser Jr.'s Journey" again.
  5. Tails777 (talk) Mario already took my example, but it still stands; the amount of times I've had to type out that title (or even the abbreviation for it) was incredibly annoying. Per all.
  6. Scrooge200 (talk) Yes, these titles can be a pain to write out in full. Per all.
  7. Technetium (talk) Per all.
  8. Sparks (talk) Per all.

Oppose

Comments

@Camwoodstock Such a parameter can always be added to the template. Super Mario RPG (talk) 18:18, December 18, 2024 (EST)

Salmancer: Mario & Sonic at the Sochi 2014 Olympic Winter Games might be the other worst game title I've had to type out. Mario (Santa)'s map icon from Mario Kart Tour Mario-HOHO! (Talk / Stalk) 00:59, December 20, 2024 (EST)

Damn it, that was gonna be my example! Sprite of Yoshi's stock icon from Super Smash Bros. Ultimate Tails777 Talk to me!Sprite of Daisy's stock icon from Super Smash Bros. Ultimate15:34, December 20, 2024 (EST)

Split image categories into separate ones for assets, screenshots, and artwork

This proposal will address the bloat some image categories have and make them easier to navigate.

Why is this useful? It makes adding to galleries or finding images to replace much easier. If you want to retake screenshots from a game, you can go to the screenshots category to find them. If you have sprite rips to replace, there's a category for that. The same goes for finding images from a game that aren't on the gallery already and being able to sort them more efficiently. This is also how we divide up character galleries already, such as Gallery:Mario (2010-2019).

Now, I can see a few edge cases, like when games have screenshots of themselves for credits images (i.e. Paper Mario: The Thousand-Year Door (Nintendo Switch)). I would still classify these as assets, since they are ripped from the game. Artwork that is used in smaller forms in-game, such as in Super Mario Maker 2, would be classified as artwork if externally released or an asset if it was ripped from the game files. Edge cases shouldn't be too common and they're easy to work out: it's not too different from how we license images or put them in character or subject galleries.

I think the name "assets" would be more useful in shorthand than "sprites and models," in addition to covering textures, so I propose for the category to be called that, but I can change it if there's opposition. The global images category can still exist in the case there's scans, merchandise, video screenshots, or such images that cannot be further categorized.

Proposer: Scrooge200 (talk)
Deadline: January 5, 2025, 23:59 GMT

Support

  1. Scrooge200 (talk) Per proposal.
  2. Waluigi Time (talk) I support this in principle, as long as there's room for discretion on what gets split and what gets left alone. A game with only ten or so pieces of artwork doesn't need a separate category for them, they can just stay in the main images category for that game. Otherwise, this seems useful, I just don't want users to go overboard by purely following the letter of this proposal.

Oppose

Comments

This is already being done (e.g. Category:Mario Kart Tour item icons). Super Mario RPG (talk) 11:02, December 23, 2024 (EST)

Removals

None at the moment.

Changes

Broaden the scope of the {{rewrite}} template and its variations

With the previous proposal having passed with being more specific as the most voted, I've come up with a proposal about the possibility to make the {{rewrite}}, {{rewrite-expand}}, and {{rewrite-remove}} templates more specific. As you can see, these templates are missing some smaller text. As such, I am just wondering if there is a possibility to have the smaller text added to the {{rewrite}}, {{rewrite-expand}}, and {{rewrite-remove}} templates.

First of all, the {{rewrite}} template currently reads as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten'''. {{#if:{{{reason|{{{1|}}}}}}|'''Reason:''' {{{reason|{{{1}}}}}}|<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}
</div>

It has been requested that this article be rewritten.

However, once the proposal passes, the {{rewrite}} template will read as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten'''{{#if:{{{reason|{{{1|}}}}}}|<nowiki/> for the following reason(s): {{{reason|{{{1}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}}.</small>
</div>

It has been requested that this article be rewritten for the following reason(s): <reason(s)>.
Please review the Manual of Style and good writing standards and help improve this article.

And another thing—the {{rewrite-expand}} template currently reads as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' and '''expanded''' to include more information. {{#if:{{{reason|{{{1|}}}}}}|'''Reason:''' {{{reason|{{{1}}}}}}|<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}
</div>

It has been requested that this article be rewritten and expanded to include more information.

However, once this proposal passes, the {{rewrite-expand}} will read as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' and '''expanded''' to include more information.{{#if:{{{reason|{{{1|}}}}}}|<nowiki/> for the following reason(s): {{{reason|{{{1}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}} by filling in the missing details.</small>
</div>

It has been requested that this article be rewritten and expanded to include more information for the following reason(s): <reason(s)>.
Please review the Manual of Style and good writing standards and help improve this article by filling in the missing details.

Lastly, the {{rewrite-remove}} currently reads as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' to have <u>{{{content|{{{1|content<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}}}}}</u> '''removed''' for the following reason(s): {{{reason|{{{2|???<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}}}}}{{#if:{{{date|{{{3|}}}}}}|<nowiki/> (tagged on {{{date|{{{3}}}}}})}}
</div>

It has been requested that this article be rewritten to have content removed for the following reason(s): ???

However, once this proposal passes, the {{rewrite-remove}} will read as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' to have {{#if:{{{content|{{{1|}}}}}}|<u>{{{content|{{{1}}}}}}</u>|content}} '''removed'''{{#if:{{{reason|{{{2|}}}}}}|<nowiki/> for the following reason(s):{{{reason|{{{2}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{3|}}}}}}|<nowiki/> (tagged on {{{date|{{{3}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}} by removing the unnecessary details.</small>
</div>

It has been requested that this article be rewritten to have content removed for the following reason(s): <reason(s)>.
Please review the Manual of Style and good writing standards and help improve this article by removing the unnecessary details.

That will be a perfect idea to make the {{rewrite}} template and its variations as more specific as the {{media missing}} and {{unreferenced}} templates. That way, we'll be able to add smaller text to the remaining notice templates in the future.

Proposer: GuntherBayBeee (talk)
Deadline: December 23, 2024, 23:59 GMT Extended to December 30, 2024, 23:59 GMT

Support

  1. GuntherBayBeee (talk) Per proposal

Oppose

  1. Altendo (talk) As far as I can tell, the proposal that was linked added parameters that allowed what was supposed to be referenced to be referenced. This one simply adds a subtitle to the bottom of each template. "Be more specific" does not mean saying general information and helpful links, but rather exactly what needs to be done; in terms of that, the existing templates not only all already have parameters, but filling them out is enforced. As Nightwicked Bowser said, "Be more specific - Similar to this proposal, what exactly needs references must be specified in the template when putting it in the article. A parameter for this will still need to be added." This only adds a subtitle and does not make this "more specific". As for the changes, this is actually harmful in some way, as the (tagged on {{{date|{{{3}}}}}}) tag will be added to the subtitle, rather than the main body, which could make it more confusing in my opinion. Feel free to update this and add in what "more specific" actually means, or just change this to "add subtitles" and change the location of (tagged on {{{date|{{{3}}}}}}) to the main body, but until then, my vote is staying here.
  2. Mario (talk) Best to keep things simple with these improvement templates.
  3. Technetium (talk) Per Mario.

Comments

Here's how I would fix some things:

First of all, the {{rewrite}} template currently reads as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten'''. {{#if:{{{reason|{{{1|}}}}}}|'''Reason:''' {{{reason|{{{1}}}}}}|<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}
</div>

It has been requested that this article be rewritten.

However, once the proposal passes, the {{rewrite}} template will read as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten'''{{#if:{{{reason|{{{1|}}}}}}|<nowiki/> for the following reason(s): {{{reason|{{{1}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}}.</small>
</div>

It has been requested that this article be rewritten for the following reasons:
Please review the Manual of Style and good writing standards and help improve this article.

And another thing—the {{rewrite-expand}} template currently reads as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' and '''expanded''' to include more information. {{#if:{{{reason|{{{1|}}}}}}|'''Reason:''' {{{reason|{{{1}}}}}}|<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}
</div>

It has been requested that this article be rewritten and expanded to include more information.

However, once this proposal passes, the {{rewrite-expand}} will read as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' and '''expanded''' to include more information{{#if:{{{reason|{{{1|}}}}}}|<nowiki/> for the following reason(s): {{{reason|{{{1}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}} by filling in the missing details.</small>
</div>

It has been requested that this article be rewritten and expanded to include more information for the following reasons:
Please review the Manual of Style and good writing standards and help improve this article by filling in the missing details.

Lastly, the {{rewrite-remove}} currently reads as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' to have <u>{{{content|{{{1|content<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}}}}}</u> '''removed''' for the following reason(s): {{{reason|{{{2|???<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}}}}}{{#if:{{{date|{{{3|}}}}}}|<nowiki/> (tagged on {{{date|{{{3}}}}}})}}
</div>

It has been requested that this article be rewritten to have content removed for the following reason(s): ???

However, once this proposal passes, the {{rewrite-remove}} will read as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' to have {{#if:{{{content|{{{1|}}}}}}|<u>{{{content|{{{1}}}}}}</u>|content}} '''removed''' {{#if:{{{reason|{{{2|}}}}}}|<nowiki/> for the following reasons:{{{reason|{{{2}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{3|}}}}}}|<nowiki/> (tagged on {{{date|{{{3}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}} by removing the unnecessary details.</small>
</div>

It has been requested that this article be rewritten to have content removed for the following reason(s):
Please review the Manual of Style and good writing standards and help improve this article by removing the unnecessary details.

This should fix some things, and I also recommend you change the title or at least context of this proposal. If so, then I might change my vote. Altendo 19:58, December 9, 2024 (EST)

I fixed this problem for you. How does it look? GuntherBayBeee.jpgGuntherBayBeeeGravity Rush Kat.png 09:40, December 10, 2024 (EST)

Decide what to do with Template:Move infobox

A while ago (November 4th, specifically), I created Template:Move infobox. After all, we had templates for essentially all the Browse tabs on the wiki sidebar, except for moves. There WERE templates about specific types of moves, such as Template:M&L attack infobox, but no general template in the same vein as items, characters, species, games, locations, etc.

I discussed it on the Discord briefly, nobody said no, and a bit of feedback later about how it should look and what it should have, I created it. It has since been applied to exactly four pages at the time of writing, half of which I was the one to apply it to. In hindsight, this could've used with a proposal instead of me just making it, so here's a belated one.

Should we keep Template:Move infobox around? If we do keep it, is it good as is, or does it need changes?

Proposer: EvieMaybe (talk)
Deadline: January 1st, 2025, 23:59 GMT

Keep Move infobox, as is

  1. Sparks (talk) I can see this template working really well for moves that aren't in every Mario game, like Spin. This has lots of potential!
  2. Nintendo101 (talk) Per proposal.
  3. Camwoodstock (talk) We don't see why not--having a dedicated Moves infobox could come in handy, especially if we get any more Mario RPGs in the wake of the weird little renaissance period we've been getting with the back-to-back-to-back SMRPG remake, TTYD remake, and release of Brothership. Per proposal.
  4. Pseudo (talk) Per proposal.
  5. Technetium (talk) Per proposal.

Keep Move infobox, but with changes

Delete Move infobox

Move infobox Comments

Considering the nature of the attack infoboxes, wouldn't it be weird to have moves all in purple but a Mario & Luigi attack use yellow and green and a Paper Mario attack use white and green? Should there be variants of the Move infobox to match the color schemes of existing templates? If an article is covering multiple related moves, how will the infobox work? (ex. Handstand, Cap Throw, Roll, Slide Kick... there's more of these than I thought). What happens when a move is referenced in somewhat less "move-y" ways? Okay, that last one is kinda strange, but basically I mean "dashing" in Super Mario Run is just a fancy animation, Mario & Luigi Dream Team has an animation where Giant Luigi crouches (with posing and skidding clearly meant to be a platformer callback), to slide under an attack. Do these instances get incorporated into the infobox? Continuing the train of thought, what about sports games? Yoshi can Flutter Jump as his special action on Mario & Sonic games. Does that count as a method of input for a Flutter Jump? Salmancer (talk) 21:35, December 19, 2024 (EST)

that's a lot of very interesting questions!
  • i went with purple to set it apart from the already taken light red (game), green and white (character), blue (level), pink (location), grey (item) and navy/grey (species) infoboxes. changing the color could be a good idea.
  • as for sorting which moves "count" or not, we have to decide these things for other types of subject too, after all, and they get infoboxes. it's a valid concern, though! eviemaybe (talk / contributions) 15:09, December 20, 2024 (EST)

Allow blank votes and reclassify them as "per all"

There are times when users have nothing else to add and agree with the rest of the points. Sure, they can type "per all", but wouldn't it be easier to not to have to do this?

Yeah sure, if the first oppose vote is just blank for no reason, that'll be strange, but again, it wouldn't be any more strange with the same vote's having "per all" as a reasoning. I've never seen users cast these kinds of votes in bad faith, as we already have rules in place to zap obviously bad faith votes.

This proposal wouldn't really change how people vote, only that they shouldn't have to be compelled to type the worthless "per all" on their votes.

Proposer: Mario (talk)
Deadline: January 1, 2025, 23:59 GMT

Blank support

  1. Mario (talk) Per all.
  2. Ray Trace (talk) Casting a vote in a side is literally an action of endorsement of a side. We don't need to add verbal confirmation to this either.
  3. PopitTart (talk) (This vote is left blank to note that I support this option but any commentary I could add would be redundant.)
  4. Altendo (talk) (Look at the code for my reasoning)
  5. FanOfYoshi (talk)
  6. OmegaRuby (talk) While on the outset it may seem strange to see a large number of votes where people say "per all" and leave, it's important to understand that the decision was made because the user either outright agrees with the entire premise of the proposal, or has read discussion and points on both sides and agrees more with the points made by the side they choose. And if they really are just mindlessly voting "per all" on proposals with no second thought, we can't police that at all. (Doing so would border on FBI-agent-tech-magic silliness and would also be extremely invading...)
  7. Shy Guy on Wheels (talk) I've always thought of not allowing blank votes to be a bit of a silly rule, when it can so easily be circumvented by typing two words. I think it's better to assume good faith with voting and just let people not write if they don't have anything to add, it's not as if random IPs are able to vote on this page.
  8. TheDarkStar (talk) - Dunno why I have to say something if I agree with an idea but someone's already said what I'm thinking. A vote is a vote, imo.
  9. Ninja Squid (talk) Per proposal.
  10. Tails777 (talk) It's not like we're outright telling people not to say "Per all", it's just a means of saying you don't have to. If the proposal in question is so straight forward that nothing else can be said other than "Per proposal/Per all", it's basically the same as saying nothing at all. It's just a silent agreement. Even so, if people DO support a specific person's vote, they can still just "Per [Insert user's name here]". I see no problem with letting people have blank votes, especially if it's optional to do so in the first place.

Blank Oppose

  1. Doc von Schmeltwick (talk) - Honestly? I'd prefer to get rid of "per all" votes since they're primarily used for the "I don't/like this idea" type of thing that has historically been discouraged. If you don't care enough to explain, you don't care enough to cast IMO.
  2. Technetium (talk) I don't think typing "per all" is that much of an annoyance (it's only two words), and I like clearly seeing why people are voting (for instance, I do see a difference between "per proposal" and "per all" - "per all" implies agreeing with the comments, too). I just don't think this is something that needs changing, not to mention the potential confusion blank votes could cause.
  3. Camwoodstock (talk) Maybe we're a little petty, but we prefer a "per all" vote to a blank one, even if "per all" is effectively used as a non-answer, because it still requires that someone does provide an answer, even if it's just to effectively say "ditto". You know what to expect with a "per all" vote--you don't really get that information with a fully blank vote.
  4. Ahemtoday (talk) Forgive me for the gimmicky formatting, but I want to make a point here — when you see a blank oppositional vote, it's disheartening, isn't it? Of course, it's always going to be that way when someone's voting against you, but when it doesn't come with any other thoughts, then you can't at all address it, debate it, take it into account — nothing. This also applies to supporting votes, if it's for a proposal you oppose. Of course, this is an issue with "per all" votes as well. I don't know if I'd go as far as Doc would on that, but if there's going to be these kinds of non-discussion-generating votes, they can at least be bothered to type two words.
  5. Jdtendo (talk) Per all (is it too much to ask to type just two words to explicitely express that you agree with the above votes?)
  6. Axii (talk) Requiring people to state their reason for agreeing or disagreeing with a proposal leads to unnecessary repetition (in response to Doc). Letting people type nothing doesn't help us understand which arguments they agreed with when deciding what to vote for. The proposer? Other people who voted? Someone in particular, maybe? Maybe everyone except the proposer? It's crucial to know which arguments were the most convincing to people.
  7. Pseudo (talk) Per Technetium, Camwoodstock, and Axii.
  8. Hooded Pitohui (talk) I admit this vote is based on personal preference as any defensible reasoning. To build on Camwoodstock and Ahemtoday's points, though, the way I see it, "per all" at least provides some insight into what has persuaded a voter, if only the bare minimum. "Per all" is distinct at least from "per proposal", suggesting another voter has persuaded them where the original proposal did not by itself. A blank vote would not provide even that distinction.
  9. Mister Wu (talk) Asking for even a minimal input from the user as to why they are voting is fundamental, it tells us what were the compelling points that led to a choice or the other. It can also aid the voters in clarifying to themselves what they're agreeing with. Also worth noting that the new editors simply can't know that blank means "per all", even if we put it at the beginning of this page, because new editors simply don't know the internal organization of the wiki. Blank votes would inevitably be used inappropriately, and not in bad faith.
  10. DesaMatt (talk) Per all and per everyone and per everything. Per.

Blank Comments

I don't think banning "per all" or "per proposal" is feasible nor recommended. People literally sometimes have nothing else to add; they agree with the points being made, so they cast a vote. They don't need to waste keystrokes reiterating points. My proposal is aiming to just streamline that thought process and also save them some keystrokes. Mario (Santa)'s map icon from Mario Kart Tour Mario-HOHO! (Talk / Stalk) 20:34, December 17, 2024 (EST)

I think every sort of vote (on every level, on every medium) should be written-in regardless of whether something has been said already or not; it demonstrates the level of understanding and investment for the issue at hand, which in my opinion should be prerequisite to voting on any issue. Doc von Schmeltwick (talk) 20:53, December 17, 2024 (EST)
There is no way to actually determine this: we are not going to test voters or commenters their understanding of the subject. Someone can read all of the arguments and still just vote for a side because there's no need to reiterate a position that they already agree with. BabyLuigiFire.pngRay Trace(T|C) 20:55, December 17, 2024 (EST)
My personal belief is that "test[ing] voters or commenters their understanding of the subject" is exactly what should be done to avoid votes cast in misunderstanding or outright bandwagoning. Doc von Schmeltwick (talk) 23:06, December 17, 2024 (EST)
My personal view is that a change like the one you are suggesting potentially increases the odds of inexperienced or new users feeling too intimidated to participate because they feel like they do not have well articulated stances, which would be terrible. I think concerns about "bandwagoning" are overstated. However, more pressingly, this proposal is not even about this concept and it is not even one of the voting options, so I recommend saving this idea for another day. - Nintendo101 (talk) 23:32, December 17, 2024 (EST)
@Mario I agree. Banning people from saying that in proposals is restricting others from exercising their right to cast a vote in a system that was designed for user input of any time. I'd strongly oppose any measure to ban "per" statements in proposals. Super Mario RPG (talk) 00:11, December 18, 2024 (EST)

Technetium: I understand, but blank votes are a fairly common practice in other wikis, and it's clearly understood that the user is supporting the proposal in general. Mario (Santa)'s map icon from Mario Kart Tour Mario-HOHO! (Talk / Stalk) 20:36, December 17, 2024 (EST)

Fair point, I didn't know that. Not changing my vote just yet, but I'll keep this in mind as the proposal continues. Technetium (talk) 20:48, December 17, 2024 (EST)
There's a lot of variation in how other wikis do it. WiKirby, for example, doesn't even allow "per" votes last I checked. Hewer A Hamburger in Super Smash Bros. Brawl. (talk · contributions · edit count) 04:13, December 18, 2024 (EST)

I'm not really much of a voter, but I'm of the opinion "it's the principle of the matter". Requiring a written opinion, of any kind, at least encourages a consideration of the topic. Salmancer (talk) 21:35, December 19, 2024 (EST)

Stop integrating templates under the names of planets and areas in the Super Mario Galaxy games

Based on the vote so far, this proposal may be eligible to close one week early. Please use {{proposal check|early=yes}} on December 25 at 23:59 GMT and close the proposal if applicable.

The aims of this proposal is to repeal this one that passed earlier this year. I will reiterate my position here:

The planetary bodies in galaxies do not just "lack" publicly accessible names - they are straight up not supposed to have names. The Shogakukan guidebook for Mario Galaxy does not give planets name. The game does not give planets name. The instruction booklet does not give planets name. The only "source" that applies discrete names for planets are from the developers and we have no reason to think these were intended to be the planets. These galaxy articles are generally a bit outdated, and I think the mistake in the first place was suggesting that some of the planets have real names "except where otherwise noted." They largely do not. I think it would would healthier to recognize that they are just different sections of a greater whole, much like areas in courses for the earlier 3D games, and apply titles accordingly.

To elaborate on my perspective, I think using dev data to provide names for these planets is completely fine, and I understand the desire to do so. Citing the Prima Games guidebooks for potential names for these areas is fine. That is not what this proposal is about. Rather, integrating the templates themselves - be it for conjectural or dev data-derived names - underneath the individual headers for each planet, in my view, looks very poor, as you can see here for Yoshi Star Galaxy and Honeyhive Galaxy. They are detractingly eye-catching and break these articles without substantive benefit. I think having a nonintrusive note at the top or bottom of these articles - as was the case before the proposal I link to above passed - is perfectly sufficient and healthier for these articles.

I provide two options:

  1. Support: Do not put conjectural and dev-data name templates beneath the names of individual planets and areas in the Super Mario Galaxy games: This is a full repeal of the proposal I link to above.
  2. Oppose: Change nothing

Proposer: Nintendo101 (talk)
Deadline: January 1, 2025, 23:59 GMT

Support: Do not put templates underneath the name's of planets and areas

  1. Nintendo101 (talk) Per proposal.
  2. 1468z (talk) Per proposal.
  3. Waluigi Time (talk) The previous solution looked a lot nicer. I also agree with Nintendo101 that we should rethink how we approach planet names in general. They don't necessarily "need" names any more than specific portions of levels in other games do.
  4. Jdtendo (talk) I still don't agree with the "planets are not supposed to have names" argument, but I do agree that having templates beneath every section heading is excessive.
  5. Camwoodstock (talk) Per all, especially Waluigi time. The overall assumption that the planets have names unless otherwise stated feels like the consequence of a decision made very, very early on into the wiki, that's just kind of gone unquestioned or unnoticed until very recently. This won't stop that particular case of WikiJank™ completely, but it's a step in the right direction.
  6. Sparks (talk) Per all.
  7. EvieMaybe (talk) if all the names are unofficial, then we only need to say it once. if there's an official name, we can just say "all names are unofficial unless specified" and specify in the one planet that has a name (is there any planets with names even???). having the template on each individual section is both ugly and inefficient
  8. Mario (talk) Yeah, the setup before this was satisfactory. Per Evie, but I also agree with Waluigi Time that we probably don't need to require naming these parts of the level either.
  9. Ray Trace (talk) I always thought assigning these objects meant to be part of the environment conjectural templates has always struck me as odd and I don't know why only Super Mario Galaxy gets singled out out of all games. We don't name the rooms the Mario Party minigames take place in.
  10. Tails777 (talk) I was sincerely confused when I saw the templates put back on the various galaxy articles and questioned "Why? It was better beforehand." Per all.
  11. Hooded Pitohui (talk) In the longer-term, WT and Nintendo101 bring up points which ought to be considered. In the shorter term, this would be a beneficial first step to de-cluttering these sections for better readability.
  12. Ninja Squid (talk) Per all.
  13. Technetium (talk) Per Nintendo101, Waluigi Time, and Porple's comment below.
  14. MCD (talk) Per N101, WT and Porple below. I also agree our attitude on what counts as "conjectural" when it comes to naming planets needs a rethink, i.e. it's not conjecture to call the planet the player starts on the "starting planet" because that's just a factual description. (Also, why does Starting Planet just redirect to a random galaxy? lol)

Oppose: Keep the templates

  1. Ahemtoday (talk) I'm opposing this proposal as currently slated to be implemented — as in, just removing Template:Conjecture and Template:Dev data from these sections and leaving it at that. These need to be marked, and I don't feel that an "unless otherwise noted" disclaimer is an elegant way to do that. However. There is a way of accomplishing this that I would be amenable to: replacing those templates with Template:Conjectural or a new dev data equivalent to it. This is the same way our glitch pages do it, for exactly the same reason you want to get rid of these templates on the galaxy pages. I think it makes perfect sense to use this convention here as well to solve this problem.

Comments on the planet template proposal

I agree that we don't need the repeated templates, and the whole naming situation of the planets is a bit odd. Rather than giving the planets capitalized "names" (e.g. "Starting Planet") and noting them as conjectural, they should just be described in sentence case, at which point it should be somewhat obvious that it's a description and not a "name". For example, section heading "Starting planet" and text "The starting planet has..." You could do a single {{conjecture|subsections=yes}} under the "Planets" heading if you really wanted to, but I think if we removed all the inappropriate capitalization then even that wouldn't be necessary. --Steve (talk) Get Firefox 20:11, December 19, 2024 (EST)

Set Vector-2010 to the default wiki skin

This proposal is about setting the 2010 Vector as the default wiki skin (screenshot here) for desktop users, with the focus being on people who are new to wikis in particular, while obviously keeping the existing MonoBook skin as an option. What made me think to create this proposal is when I made a Talk:Main Page proposal about the to-do list tasks and how they are more accessible than clicking the "Wiki maintenance" on the sidebar, I had to uncomfortably squint to find "Wiki maintenance" on the wiki sidebar. But Vector-2010 has the sidebar links slightly larger and a bit more spaced out. With the existing interface, there could be some who may struggle to find options listed on the sidebar.

While we're clearly different from Wikipedia (that's why I'm not Vector-2022, since it'd be too much of a departure and likely uncomfortable for several), I do want to refer to this page, which summarizes why Wikipedia transitioned to it. Though it is vague, they cite accessibility as the reason, which I think this wiki has been taking steps toward doing.

I'll cite my reasons for preferring Vector and applying this to possible people who are visiting a wiki for the first time. The text is larger, which is especially important for larger screen monitors, some of the lesser used tabs are collapsible on the sidebar, summarizing the most commonly used options, and the user links at the top right are also more noticeable and less close to the body of the article where the content is read.

Though it could take time getting used to the Edit button being on the right (not to mention the search button), the button is at least larger, making it more usable on even lower quality screen monitors, and I like how it's separate from the Page and discussion options, meaning that options that involve viewing articles are on the left while options that involve editing or changing the page in some form are on the right.

If this proposal passes and others don't like the change, they can always return to the MonoBook option in their preferences.

Proposer: Super Mario RPG (talk)
Deadline: January 1, 2025, 23:59 GMT

Support

  1. Super Mario RPG (talk) Per.

Oppose

  1. Camwoodstock (talk) Admittedly, this vote is largely a matter of preference--we just don't like Vector that much--but we can't think of any real reason to switch to Vector 2010 as the default over the current Monobook beyond the mentioned text spacing; while that is a nice boon, we personally find the weird gradient buttons for the various tabs up top a little grating looking, and we're a fan of the more compact design that Monobook provides--though, this is likely a byproduct of our personal preference for more neatly packed web design. And uh, the less said about the other two options (Vector 2022, and. Timeless. Which is the most dated theme possible, namely to mid-2010s mobile web design.), the better. If you like Vector 2010, that's great, and we're fine with that! Heck, if anyone likes Vector 2022 or Timeless, that's cool too, and more power to them! Variety is the spice of life, after all. But switching it to the default is something that should not be taken lightly, and the reasons for a switch in this proposal feel a little too loosey-goosey for us, we're sorry.
  2. DryBonesBandit (talk) Per Camwoodstock.
  3. Nintendo101 (talk) I like how MonoBook looks a little more than Vector. It is what I am comfortable with. If it ain't broke, don't fix it.
  4. Drago (talk) Per Nintendo101. I actually prefer the smaller text of Monobook since you can see more of the page at once. I also want to point out that although logged-in users like us can change the skin in preferences, we'd still be forcing the change on logged-out users.
  5. Ahemtoday (talk) Per Drago.
  6. Technetium (talk) Per Nintendo101 and Drago. I just don't see any reason to make this change.
  7. Altendo (talk) I'm saying this as a Vector-2010 skin user, and I'll say that people have their preferences. I live Vector-2010 because that is how Wikipedia at least used to look before they switched to Vector (2022); On Wikipedia, Vector was renamed to Vector legacy (2010), while Vector 2022 is named Vector (2022). Although I do prefer Vector-2010, I know a lot of people that prefer Monobook, and even if not, this can be changed in the preferences. No need to change the default skin. I get that IPs can't change their appearance, but aside from that, users can, and what they see doesn't have to be default on the wiki. Everyone can change what they specifically see.

Comments

@Camwoodstock That is true that it's a major change. It's based mainly upon impression from newcomers from them seeing a more prominent edit tab, slightly larger text size, and other minor details like tab names that are easier to read (including a collapsible feature for the lesser used tab). The skin change was based on old Wikipedia research at the time (like how WikiLove was a result of their research). I have no strong feelings whether this passes or not. Although it's vague, since there's no way to tell the statistics (and the wiki's already successful at the moment), I still have a feeling it could help some, but to each their own. Super Mario RPG (talk) 18:32, December 18, 2024 (EST)

We feel like if anybody would be capable of providing any statistics on skin usage, it'd be Porple, but even then, we don't actually know if that's one of the things he tracks, and it feels a little silly to pester him over this of all things... ;p ~Camwoodstock (talk) 18:55, December 18, 2024 (EST)

I'm okay with opposition, but in case of misunderstanding, this proposal isn't about personal preferences so much as what I believe to be a more ergonomic interface to a wider audience. I know we're not Wikipedia, but there's also the consideration that they've used the Vector skin longer than they had for MonoBook. Super Mario RPG (talk) 13:45, December 19, 2024 (EST)

If it's what "you believe", then it ultimately (and probably unavoidably) is about personal preferences. Anyway, another consideration is the fact that people often prefer what they're used to. I feel like how long this wiki has used its skin is more relevant than how long Wikipedia has. Hewer A Hamburger in Super Smash Bros. Brawl. (talk · contributions · edit count) 16:39, December 19, 2024 (EST)
@Hewer I suppose I'm overthinking the ergonomic interface. Super Mario RPG (talk) 15:19, December 20, 2024 (EST)

Miscellaneous

None at the moment.

Retrieved from "https://www.mariowiki.com/index.php?title=MarioWiki:Proposals&oldid=4471872"