MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
m (Not a leap year...)
 
Line 1: Line 1:
<center>http://i143.photobucket.com/albums/r149/Deadringerforlove/dessert1.jpg</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), removal of a previously added feature that has tired out, or new policies that must be approved via [[Wikipedia:Wikipedia:Consensus|consensus]] before any action(s) are done.
*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.''
 
==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.


<h2 style="color:black">How To</h2>
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:
#Actions that users feel are appropriate to have community approval first can be added by anyone, but they must have a strong argument.
#Users then start to discuss on the issue. 24 hours after posting the proposal (rounding up or down to the next or previous full hour, respectively, is allowed), the voting period begins. (The proposer is allowed to support their proposal right after posting.) The "deadline" for the proposal is one week from voting start at: ('''All times GMT''')
#*Monday to Thursday: 23:00 (11pm)
#*Friday and Saturday: 2:00 (2 am) of the next day. A proposal posted on a Thursday ends the following Saturday morning; a proposal posted on a Friday ends the following Sunday morning.
#*Sunday: 21:00 (9pm)
#Every vote should have a reason accompanying it.
#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. The voter 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]].
#"<nowiki>#&nbsp;</nowiki>" should be added under the last vote of each support/oppose section to show another blank line.
#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.
#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.
#No proposal can overturn the decision of a previous proposal that is less than '''4 weeks''' ('''28 days''') old.
#Proposals can only be rewritten or deleted by their proposer within the first three days of their creation. However, the proposer can request that their proposal be deleted by a [[MarioWiki:Administrators|Sysop]] at any time, provided they have a valid reason for it.
#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 a Sysop, the proposer can ask for that help.
#There shouldn't be proposals about creating articles on a 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 [[MarioWiki:Administrators|System Operator]] promotions and demotions. Sysops can only be promoted and demoted by the will of [[MarioWiki:Bureaucrats|Bureaucrats]].
#If the Sysops 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.
#No joke proposals. Proposals are serious wiki matters, and should be handled professionally. Joke proposals will be deleted on sight.


The times are in [[wikipedia:GMT|GMT]], and are set so that the user is more likely to be online at those times (after work/school, weekend nights). If a proposal is added on Monday night at 11:59 PM GMT, the deadline is the next Monday night at 11:00 PM. If it is posted a minute later, the deadline is a week Tuesday, since midnight is considered to be part of the next day, as 00:00 AM.
:''For profiles and statistics of Luigi in Mario Sports Superstars, see [[List of Luigi profiles and statistics#Mario Sports Superstars|here]].''


===Basic Proposal and Support/Oppose Format===
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.
This is an example how 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 you want this Proposal to be like, what changes you would suggest and what this is about]</nowiki>


<nowiki>'''Proposer''': {{User|[enter your username here]}}<br></nowiki><br>
'''Proposer''': {{User|Super Mario RPG}}<br>
<nowiki>'''Voting start''': [insert a voting start time here, f.e. "2 January, 2010, 14:00". Voting start times are 24 hours after the time at which the proposal was posted, as described in Rule 2 above.]<br></nowiki><br>
'''Deadline''': January 1, 2025, 23:59 GMT
<nowiki>'''Deadline''': [insert a deadline here, f.e. "8 January, 2010, 23:00". Rule 2 above explains how to determine a deadline.]</nowiki>
 
====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.
 
====Oppose====


<nowiki>====Support====</nowiki>
====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)


<nowiki>====Oppose====</nowiki>
===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.


<nowiki>====Comments====</nowiki>
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)]].
-----
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 anoother user's Proposal. If you are voting on your own Proposal, you can just say "Per my Proposal".
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.


__TOC__
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.


<!--<center><span style="font-size:200%">CURRENTLY: '''{{#time: H:i, d M Y}} (GMT)'''</span></center>-->
'''Proposer''': {{User|Scrooge200}}<br>
'''Deadline''': January 5, 2025, 23:59 GMT


====Support====
#{{User|Scrooge200}} Per proposal.
#{{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|Salmancer}} I've tried to see if an image I wanted to use was already uploaded via the category, which would encourage me to make the text and get the article up. Due to the sheer number of images, this is a bad idea. This proposal will make that less of a bad idea for cases where an asset or artwork is being searched for.
#{{User|EvieMaybe}} hell yea


====Oppose====


<br>
====Comments====
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)


==Talk Page Proposals==
==Removals==
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.
''None at the moment.''


===How To===
==Changes==
#All active talk page proposals must be listed below in chronological order (new proposals go at the bottom). All pages effected 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.
===Broaden the scope of the <nowiki>{{rewrite}}</nowiki> template and its variations===
#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, 4 and 5, as follows:
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.
#Voting in talk page proposals will be open for two weeks, not one. There is no 24 hour delay between the posting of a talk page proposal and the commencement of voting.
#Talk page proposals may closed by the proposer if both the support ''and'' the oppose sides each have fewer than five votes.
#After two weeks, a clear majority of three votes is required. Without the majority, the talk page proposal will be listed as "NO QUORUM".
#The talk page proposal '''must''' pertain to the article it is posted on.


===List of Talk Page Proposals===
First of all, the <nowiki>{{rewrite}}</nowiki> template currently reads as follows:
*Merge information pertaining to generic Blue and Yellow Toads into [[Toad (species)]] and [[Toad Brigade]], leaving the separate [[Blue Toad]] and [[Yellow Toad]] pages for the specific Toad characters that appeared in ''New Super Mario Bros. Wii''. Whether or not these pages will be named "{{fakelink|Blue Toad (New Super Mario Bros. Wii)}}" and "{{fakelink|Yellow Toad (New Super Mario Bros. Wii)}}" or "{{fakelink|Bucken-Berry}}" and "{{fakelink|Ala-Gold}}" is also being voted on. ([[Talk:Yellow Toad|Discuss]]) '''Passed''' 
----
*Merge [[Nintendo GameCube Microphone]] into [[Nintendo GameCube]]. ([[Talk:Nintendo GameCube Microphone|Discuss]]) '''Passed'''  
<pre>
*Merge [[Banana Bunch]] into [[Banana]]. ([[Talk:Banana Bunch|Discuss]]) '''Passed''' 
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
*Merge [[Special Kit 1]] and [[Special Kit 2]] into [[Mario vs. Donkey Kong 2: March of the Minis]]. ([[Talk:Special Kit 1|Discuss]]) '''Passed''' 
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}}}}}})}}
*Split [[SSX on Tour]] from [[Video game references]]. ([[Talk:SSX on Tour|Discuss]]) '''Passed'''   
</div>
*Merge [[Triple Bananas]] and [[Giant Banana]] into [[Banana]]. ([[Talk:Banana|Discuss]]) '''Passed''' 
</pre>
*Split [[Mushroom]] (Super Mario RPG info) into [[Mushroom]] and {{Fakelink|Mushroom (Status effect)}} ([[Talk:Mushroom|Discuss]]) '''Passed'''
*Merge [[M]] into [[Graffiti]]. ([[Talk:M|Discuss]]) '''Passed'''
*Merge [[Mushroom]] (SMRPG info), [[Bad Mushroom]], [[Mid Mushroom]], [[Max Mushroom]] onto one page. ([[Talk:Mushroom|Discuss]]) '''Deadline:''' 25 February 2010, 20:00
*Merge [[Standard Bike M]], [[Standard Bike L]], and [[Standard Bike S]] into [[Bike]]. ([[Talk:Standard Bike M|Discuss]]) '''Deadline:''' 25 February 2010, 20:00
*Merge [[Standard Kart S]], [[Standard Kart M]], and [[Standard Kart L]] into [[Kart]]. ([[Talk:Standard Kart M|Discuss]]) '''Deadline:''' 25 February 2010, 20:00
*Merge [[Entei]] and similar pages, where characters appear as stage trophies into {{fakelink|List of Stage Trophies}}. ([[Talk: Entei|Discuss]]) '''Deadline:''' 4 March 2010, 23:00
*Merge [[Turtle (Super Smash Bros.)]] into [[Trophy Descriptions (Super Smash Bros. Melee) ]] ([[Talk:Turtle (Super Smash Bros.)|Discuss]]) '''Deadline:''' 6 March 2010, 2:00
*Merge [[King Bulblin and Lord Bullbo]] into [[Bridge of Eldin]] ([[Talk:King Bulblin and Lord Bullbo|Discuss]]) '''Deadline:''' 6 March 2010, 2:00
*Merge [[Special Kit 3]] into [[Mario vs. Donkey Kong 2: March of the Minis]]. ([[Talk:Special Kit 3|Discuss]]) '''Deadline:''' 7 March 2010, 2:00
*Split [[Dark Koopa]] into [[Dark Koopa]] and {{fakelink|Dark Koopa (Super Paper Mario)}}. ([[Talk:Dark Koopa|Discuss]]) '''Deadline:''' 2 March 2010, 22:00
*Split [[Pauline's items]] into {{Fakelink|Parasol}}, {{Fakelink|Bag}}, and {{Fakelink|Hat}}. ([[Talk:Pauline's items|Discuss]]) '''Deadline:''' 9 March 2010, 23:00
*Delete [[Spipoopy]]. ([[Talk:Spipoopy|Discuss]]) '''Deadline:''' 10 March 2010, 23:00
*Merge [[Dragonfly (Mario Paint)]] into [[Mario Paint]]. ([[Talk:Dragonfly (Mario Paint)|Discuss]]) '''Deadline: 11 March 2010, 23:00
*Merge [[Rainbow Boost]] into [[Boost Pad]]. ([[Talk:Rainbow Boost|Discuss]]) '''Deadline:''' 11 March 2010, 23:00


==New Features==
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
===Table Button On Editing Screen===
It has been requested that this article be '''rewritten'''.
You know that making tables is a hard thing to do? Well, I was thinking on that bar on the top of the edit screen? I think that we should add a table button to this, so when clicked, a box will pop up like the one in Microsoft Word, and you can choose how many rows and columns. Then the table appears in the edit box, and all you have to do is change the colour and content. Easy as pie (although not the Pie Button!) I beleive this will save ages trying to remember how to make a table, and new users will find this helpful for their first contributions.
</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>


'''Proposer:''' {{User|LucariosAura}}<br>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
'''Deadline:''' March 1, 2010, 23:00
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>
 
<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 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>
</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 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>
 
<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): <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>
----
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|GuntherBayBeee}}<br>
'''Deadline''': <s>December 23, 2024, 23:59 GMT</s> Extended to December 30, 2024, 23:59 GMT


====Support====
====Support====
#[[User:LucariosAura|LucariosAura (used to be specialk)]] 13:30, 22 February 2010 (EST)
#{{User|GuntherBayBeee}} Per proposal
#{{User|KS3}} Who knows how to memorize that 36 line thingie. I sure don't.
#{{User|MATEOELBACAN}} Per Proposal, of course!
#{{User|Mr bones}} Per proposal.It will be very helpful.


====Oppose====
====Oppose====
#{{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|Mario}} Best to keep things simple with these improvement templates.
#{{User|Technetium}} Per Mario.


====Comments====
====Comments====
This would surely be helpful, but I doubt it's realizable technically. {{User|Time Q}}


:Yeah, it would be a good idea, but how would we implement this into the edit page? {{User|BabyLuigiOnFire}}
Here's how I would fix some things:


WikEd has a button to create tables, it inserts the coding and you change it to your liking :) {{user|Tucayo}}
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>


The "Not Pie Button" section reminds me of the Virtual Pie for Everyone proposal. {{User|KS3}}
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
:Couldn't you just insert the coding on your own? It's what I do and I like it much better as it's much easier to use a preformatted template than doing it on your own. This is sounding a little bit too much like wikia's wikicoding beta for my liking - that's one of the reasons I left wikia. Another option is to copy/paste - that's what I do for the longer templates. {{User|Marioguy1}}
It has been requested that this article be '''rewritten'''.
::I don't like having to resort to look somewhere else to copy and paste the table. And I'm still confused at this process, even I've been here for a while. {{User|BabyLuigiOnFire}}
</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>


How the heck will the sysops implement this? You can't just say "Abra, Kadabra, Alakazam" and expect everything to work for you. {{User|Reversinator}}
<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>


KS3 that is exactly what i was thinking when I put that! Baby Luigi on fire I agree, my current method is copy/pasteing, and it is very hard. and reversinator I was hoping a Sysop would edit the edit bar to make a table button. What else would I mean? [[User:LucariosAura|LucariosAura (used to be specialk)]] 10:43, 23 February 2010 (EST)
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
:I'm fairly certain that {{User|Porplemontage}} would have to edit some files in the database to make this work. That's the only way this would work. -- {{User|Stooben Rooben}}
It has been requested that this article be '''rewritten''' and '''expanded''' to include more information.
::Some questions that should be answered if we do this. 1 - For the button, wouldn't you have diffulty with more typing when it gives you the basics for it, and you need like 60 sections or something? 2 - Most users cut and paste for templates too, and they are like tables. 3 - Also, there are different versions of tables (like [[Mario & Luigi: Bowser's Inside Story|this one used here]] and [[List of Tayce T. Recipes/By Ingredient|this other one]].), we can't have many buttons for the varied tables. That is about what I have to say. {{User|Baby Mario Bloops}}
</div>
:::Remember this wont be obligatory to use, people would be able to make the tables they want by inserting the coding themselves, this is for people who just want a basic table. {{user|Tucayo}}
----
::: @BMB After you click the table button then a window pops up saying what kind of table you want. Then the number of columns and rows you want window appears and you choose how many columns and rows. Then the exact table you imputed into the windows will appear. {{User|KS3}}
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>


===Add Quote of the Week (or Featured Quote) to the Main Page===
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
There are a lot of quotes out there that are great. If we have the featured Articles and the Featured Images, there are a lot of quotes that are wise and this might make our wiki seem that there is more than "this weird person who rides on ugly froglike creatures killing people just to save his girlfriend" (I was just giving an example Sorry if I insulted Yoshi but that's what some people actually think). We can put it under the Featured Images and move the Did You Know section down. There will be a separate page for voting to see which ones are the best (like the FA and FI)
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>


'''Proposer:''' {{User|KS3}} <br>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
'''Deadline:''' March 2 2010, 23:00
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>


====Add new feature====
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
#{{User|KS3}} Per proposal.
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>
#{{User|MATEOELBACAN}} Per Proposal (But don't say that of Yoshi...people he's a dinosaur!)
</div>
#{{User|Mr bones}} Per proposal.
#[[User:LucariosAura|LucariosAura (used to be specialk)]] I agree with MATEOELBACAN, yoshi is cool. And per proposal.
#{{user|Tucayo}} - Per. We have a template for this {{tem|RandomQuote}}. Perhaps the look will be something like [http://www.mariowiki.com/index.php?title=Main_Page&oldid=597208 this].
#{{user|Reversinator}} It's interesting, and I'm not getting any slow down.


====Don't add====
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)
#{{User|T.c.w7468}} Didn't we knock the quote of the day thing down a few months ago because it slowed everything up? Besides, many of the quotes that end up on this are pretty bad, and it doesn't add much to the page anyway.
: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)
#{{user|Bloc Partier}} -- Per all. Plus, no one ever puts the quotes in right so we always have to edit the pages themselves to keep the Main Page template working.
#{{User|Baby Mario Bloops}} - I knew people would come over to the don't add side. Anyways, we got rid of the quotes for many reasons (like I said in the comments): 1 - Takes forever to get to the Main Page, plus all the broken links it can cause. 2 - It can glitch a lot when doing some quotes that is more than one sentence, making it not that useful. 3 - We have plentiful things about our wiki that tells info on the Mario things.
#{{User|Time Q}}: Per all.
#{{User|Marioguy1}} - We had this quote before, it slowed loading time and showed a different quote every time someone looked at it - that isn't even a "Featured" quote! I definitely don't think we should create Mariowiki:Featured Quote as we  have enough featured content already, besides - a quote is too minor to be nominated and then we go through a whole process over about 10 words.
#{{User|Fawfulfury65}} It will make the main page take longer to load. And do we really need it? I mean, are we gonna like choose a featured quote or something? I don't think this will really help anything.


====Comments====
===Decide what to do with Template:Move infobox===
Can I see what the new main page would look like? The main page is half informational, half aesthetic (probably the only page that is). {{User|Marioguy1}}
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.  


:LOL, LeftyGreenMario said that. Anyway, did you know that there was a proposal to remove that Quote of the Day thingy because of loading time? Just for your information. {{User|BabyLuigiOnFire}}
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.
::Just like BLOF said above, the loading time took forever to get onto MarioWiki, and for many users like me it caused the broken link to appear more often. Also, wasn't there a glitch with the template for the quotes when it used more than one quote? {{User|Baby Mario Bloops}}


@LucariosAura Can you please use the form <nowiki> {{User|LucariosAura}} </nowiki> We don't need to know that You used to be specialK. -{{User|KS3}}
Should we keep '''Template:Move infobox''' around? If we do keep it, is it good as is, or does it need changes?


:@Baby Mario Bloops: Yes. That was the glitch that I was talking about in my vote. {{user|Bloc Partier}}
'''Proposer''': {{User|EvieMaybe}}<br>
::@KS3: Actually, he doesn't have too - according to the [[Mariowiki:No-Signature Policy|no-sig policy]], he's allowed to do <nowiki>[[User:LucariosAura|XYZ]]</nowiki>. {{User|Marioguy1}}
'''Deadline''': January 1st, 2025, 23:59 GMT


@Baby Mario Bloops: We aren't going to use the template. We are going to vote on the quotes like the images for the FI, so 1. we won't get any bad quotes, and 2. this won't cause the glitch.
====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.
#{{User|Salmancer}} It would bring more attention to our move pages. I'm down for that.


===Bring back Weekly Polls===
====Keep Move infobox, but with changes====
We used to have weekly polls, and they are very good. We still have [[MarioWiki:Weekly Polls|this page]]. But instead of doing only one poll, we will be doing 3 polls. The reason why is because let's say the poll is "What is the easiest stage in Platformer games", and you only own Spinoffs and RPGs, then you can't answer the poll, while if you have 3, then you can at least answer one.


'''Proposer:''' {{User|KS3}}<br>
====Delete Move infobox====
'''Voting start:''' 25 February 2010, 22:00<br>
'''Deadline:''' 4 March 2010, 23:00


====Bring them back====
====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)


====Don't bring them back====


====Comments====
It got removed because it was too bustling with activity ONLY with that Poll page. I may be fond of the Poll of the Day, but we don't get it our way all the time. {{User|BabyLuigiOnFire}}


==Removals==
===Another Proposal on removing the FI===
We voted to keep the FI via this old proposal - [http://www.mariowiki.com/MarioWiki:Proposals/Archive#Remove_Featured_Images_From_Main_Page]. The FI is like idle and most of the pictures that are there are kind of bad (pixelly, logo everywhere, too small, etc.).  and Per the reasons of the old proposal.


An alternative is to reuse old pictures like the Featured Articles, as said in the old proposal.
===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?


'''Proposer:''' {{User|Red Shell 68066vr}}<br>
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.
'''Deadline:''' February 25, 2010, 23:00


====Remove the FI====
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.
#{{User|Red Shell 68066vr}} Per proposal.
#{{User|Time Q}}: Per my reasoning on the old proposal. I don't think the main problem is running out of images. I think the main problem is that the concept of FIs is rubbish. Unlike articles, images are not our work. Also see my comment below.
#{{user|Bloc Partier}} -- Per all.
#{{User|Walkazo}} - Per Time Q.
#{{User|LeftyGreenMario}} I'm done with this. We can't do featured images properly unless we have an unbiased point of view. Too bad that's impossible because we use opinions to feature images. Nothing else on our wiki uses opinions to feature things. I think featured images should go down the sewers. And the empty white space? Whatever. I don't care.
#{{User|Stooben Rooben}} - Per Time Q.


====Reuse old pictures====
'''Proposer''': {{User|Mario}}<br>
'''Deadline''': January 1, 2025, 23:59 GMT


====Keep as it is====
====Blank support====
#{{User|King Bean}} - There are still a lot of images that deserves to be featured. We haven't ran out of them yet.
#{{User|Mario}} Per all.
#{{User|Fawfulfury65}} If you keep a sharp eye out for images, you eventually find a nice one. And of course SMG2 doesn't have any artwork yet, it doesn't even have a release date yet! I think we'll have enough images for quite a while, though.
#{{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|Reversinator}} There's no release date of SMG2, and you're expecting artwork from that game to just fall from the sky? Per all.
#{{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|4DJONG}} As I said before, the wiki still has plenty of images worthy of being featured. Images might not be our work but they give a break from all the writing on the main page, If we get rid of them there wont be any thing but writing on the main page.
#{{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|Tucayo}} - Per all.
#{{User|FanOfYoshi}}
#{{User|BabyLuigiOnFire}} They're still Mario stuff, even if it wasn't our own work. Besides, Featured Images give color and touch to the main page. Come on, think of main page with just two images and the rest are text. Plus, not everyone would look at the 'Shroom anyway.
#{{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|Gamefreak75}} How many times is this proposal gonna come up? Per all. And what do you mean it's been a week and no pics of SMG2? >_>' And like everyone said, who's gonna want to read a main page full of text. The pitures give it personality and color instead of reading text after text.
#{{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|Baby Mario Bloops}} - As I said in the last proposal of this, and the fact that your impatient and too literal to realize that SMG2 won't be out in a week, so give it time and enjoy the great images we have around the wiki.
#{{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|Zero777}} I am Zero! Per all. Zero signing out.
#{{user|Ninja Squid}} Per proposal.
#{{User|MATEOELBACAN}} Per King Bean.
#{{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.
#{{User|Marioguy1}} - The FI adds an artistic touch to the wiki. We can't have everyone thinking that we are a boring place that nobody wants to be at. We need to do two things to keep the wiki a ''happy'' place for some users. 1. Have images as well as articles. 2. Keep [[Mariowiki:The 'Shroom|The 'Shroom]] running. This may as well be a proposal to remove the 'shroom as the 'shroom does not include any factual information or help the wiki knowledge in any way. The 'Shroom is simply a community project that many users like and have fun with, as are FIs - while they are very disorganized and very illogical in some places, users still like them and they should stay to make users ''like'' the wiki.
#{{User|Pie Shroom}} Per all.
 
====Comments====
First of all: ''Super Mario Galaxy 2'' has not been released yet. I don't know what you're talking about. Second: You can't just propose to "reuse old pictures", you should at least propose rules of when to do so. For example, if an image has less than 10 positive votes at the end of a week, reuse an old picture. Third: one of the reasons for opposing my old proposal was that the Main Page wouldn't be balanced anymore without the FIs. Look at our current Main Page. Since talk page proposals were added to it, it's not balanced anymore at all. Now if we remove the FIs and move the talk page proposals to the right, we could balance it out again. {{User|Time Q}}


About the "not our work" thing for the images. I would think of something like this to be going on the shroom', but what if we had some thing like FIs where we could have fan made Mario images made by us users? And the one with the most votes gets on the main page? Maybe? I'm not sure if this is a stupid idea or not so... {{User|Fawfulfury65}}
====Blank Oppose====
:I wouldn't recommend that. We only have official content on the wiki, no fanon articles etc., so we shouldn't encourage users to make images themselves. But of course we could have all that in the 'Shroom. Just like the FIs ;) {{User|Time Q}}
#{{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.


Everyone, I checked on a bunch of websites and it says that it comes out on February 11th, 2010. {{User|Red Shell 68066vr}}
====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)


You seriously think that it came out last week? Wow. {{User|Reversinator}}
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)
:Where did you hear that nonsense? It's supposed to come out around summer time...{{User|Gamefreak75}}
: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)
::''I'' checked a bunch a websites, and they all said "TBA 2010". And I look at the official ones. Gamefaqs, IGN, Gamespot, you know, what you should rely on. {{User|Reversinator}}
: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)
:::Same at the Nintendo website. Nintendo is the most official and exact one (obviously). {{User|Gamefreak75}}


Okay...<br>
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)
But we still have to get rid of the FI. {{User|Red Shell 68066vr}}


:No, we don't all text on the main page and what someone (I forgot who...) brought up on the first removal of FI was a very good point. What will we replace it with because we can't have a huge are of whitespace on the front page. {{User|Gamefreak75}}
===Set Vector-2010 to the default wiki skin===
::There's a picture of Mario in the upper left corner and all the ads have pictures. {{User|Red Shell 68066vr}}
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.
::: That Mario picture is not enough. And ads... I hate those things. They do not count as images in the main page since they are annoying and distracting. Besides, I use Firefox with Noscript and AdBlocker, which means I won't see those ads. {{User|LeftyGreenMario}}
::::I forgot. There is also the picture from the Featured Articles every article. {{User|Red Shell 68066vr}}
:::::Still, the purpose of FI is to give a colorful touch to our wiki. That image with Featured Articles is just there because people are visual learners. Besides, I don't find the image with the Featured Article very appealing, and the news section either. Where should we fill that empty space, then, if we remove the FI? More text?
{{User|BabyLuigiOnFire}}


:::::: The Featured Images crap is all opinion based. We can't have that. I don't know what to replace the main page, though. Let's leave it like that. :P {{User|LeftyGreenMario}}
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.
::::::: Nah, most of the time, we get good featured images, like the Super Mario Galaxy one and the Height Chart. Well, not everyone has the same opinions as us. Maybe that's why this "well-written" requirement for an FA has pretty much no meaning since we have different opinions of "well-written". Still, everyone can see low quality or blurriness, or white background, but everyone has their own opinion in other qualities of the picture. {{User|BabyLuigiOnFire}}


First of all, Super Mario Galaxy 2 is coming out in March 23, 2010. Second of all, this proposal is probably going to fail considering it is 6-12 and that it wouldn't make the main page any better. Third, there are a lot of good (Mario Party) pictures waiting to be featured. Fourth, @LGM So will the Featured Quote when it passes (look at the above section). Fifth, The ones that are bad usually get deleted in a week. -{{User|KS3}}
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.
:Dude, what the heck are you even talking about? YOU started the proposal! Are you trying to take us for fools? {{User|Time Q}}
::@LGM: While I agree with you that the FIs are very disorganized and have horrible reasons so far. That is ''not'' a point against the FIs. The '''''FIs''''' are a good idea. The '''''people putting those votes up''''' are the ones you should blame for the disorganization of the page - not the page itself as I really doubt the page itself can do that much harm as it is only a webpage...{{User|Marioguy1}}


{{User|KS3}} I'm going to take a break from here.
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.


:>_> Nothing to be discouraged about...and it's actually May, not March, it's a 2-month difference. {{User|Gamefreak75}}
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]].


==Changes==
'''Proposer''': {{User|Super Mario RPG}}<br>
===Proposals Should End At The end of the day one week after voting starts (In GMT)===
'''Deadline''': January 1, 2025, 23:59 GMT
It's a really long title, but here's what it's trying to say. Currently, after proposals are posted, there's a 24-hour delay, and then voting starts. Depending on when the voting period starts, the voting could end anywhere from 7 to 8 days from when voting starts. I don't like this, because I realise that the times (5 p.m. and 7 p.m. I think they were) were adjusted for the GMT proposal, but now the times are 11 p.m. and 2 a.m. of ''the next day''. I believe the proposals, from the beginning of voting should end at 23:59:59 of the same weekday 7 days later. (i.e. From the proposal itself, +8 days and however many hours until 11:59 p.m. GMT). So, for instance, (for our purposes, let's just pretend that today is a Friday.) the voting for this proposal (it is currently 23:16, 23 February 2010), would end at the end of the day (23:59 or 0:00 depending on how you see it) of 2 March 2010, rather than 2:00 of 3 March 2010. I believe this would simply the process a lot more, not to mention that the whole ending time difference was so it's more convenient for people living on the East Coast to vote for. I apologize if the whole "end-of-the-day" thing is confusing; I tried my best to explain it. Feel free to ask questions in the comments before and after voting starts.


'''Proposer:''' {{User|Garlic Man}}<br>
'''Voting start:''' 24 February 23:16<br>
'''Deadline:''' 3 March, 2010, 23:00
====Support====
====Support====
#{{User|Super Mario RPG}} Per.


====Oppose====
====Oppose====
#{{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|DryBonesBandit}} Per Camwoodstock.
#{{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, there is no difference with the GMT time, proposals end at exactly the same hour. Sorry if I didn't understand the proposal. {{user|Tucayo}}
{{@|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)
:He's proposing we scrap those ending hours and simply use midnight as the deadlines. I never liked how different days of the week had different ending times - it always seemed superfluous, and now that the conversion to GMT has pushed the weekend times into the following day, it's even more confusing. The proposal's example is a little hard to follow too, but if I understand correctly, simply put, Garlic Man is saying that the new system will be: "Proposal written on Day 1 at X:AB o'clock, voting starts on Day 2 at X:00 o'clock, deadline at Day 8 at 24:00 o'clock (which is also Day 9, 00:00); the day of the week doesn't matter." ...right? - {{User|Walkazo}}
: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)
::Thanks Walka :) I udnerstand now. Seems a good idea {{user|Tucayo}}
 
Yes, that is correct. --{{User|Garlic Man}}
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)
:OK, this is kinda related - what will we do when voting opens? Remove the Voting Opens thing? Cross it out? Leave it as is? {{User|Marioguy1}}
: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)
::Uh, leave it as is. There would be no reason to change it. This proposal says nothing about changing it, so we would be unable to touch it. {{user|Bloc Partier}}
::{{@|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.''
<!-- Please do not remove, archive or place comments below this message. -->
&nbsp;

Latest revision as of 23:51, December 25, 2024

Image used as a banner for the Proposals page
Current time:
Saturday, December 28th, 12:00 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)
Stop integrating templates under the names of planets and areas in the Super Mario Galaxy games, Nintendo101 (ended December 25, 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)

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.
  3. Salmancer (talk) I've tried to see if an image I wanted to use was already uploaded via the category, which would encourage me to make the text and get the article up. Due to the sheer number of images, this is a bad idea. This proposal will make that less of a bad idea for cases where an asset or artwork is being searched for.
  4. EvieMaybe (talk) hell yea

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.
  6. Salmancer (talk) It would bring more attention to our move pages. I'm down for that.

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 (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)

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 (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=4472551"