MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
mNo edit summary
 
Line 1: Line 1:
<center>[[File:Proposals.png]]</center>
{{/Header}}
<br clear=all>
{| align="center" style="width: 85%; background-color: #f1f1de; border: 2px solid #996; padding: 5px; color:black"
|'''Proposals''' can be new features (such as an extension), removals of previously added features that have tired out, or new policies that must be approved via [[Wikipedia:Wikipedia:Consensus|consensus]] before any action is taken.
*Any user can support or oppose but must have a strong reason for doing so, not, e.g., "I like this idea!"
*"Vote" periods last for one week.
*All past proposals are [[/Archive|archived]].
*All proposals must pass by a majority, including proposals with more than two options.
|}
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==
===Change how "infinitely respawning" enemies are counted in level enemy tables===
Currently, the wiki lists enemy counts for each level in tables located in that level's article. This is all well and good, but the problem arises when infinitely respawning ones (like piped ones) are included. As seen [[World 6-B (New Super Mario Bros.)|here]], this is awkwardly written as
*"[number] (not including the infinite [enemy] spawning from [number] [method]),"
and why shouldn't it include them? That method of writing is ungainly, misleading, and bloats the table's width unnecessarily. Therefore, I propose the alternate writing of
*"[number] + (∞ x [number]),"
with the "x [number]" and parentheses being removed if there is only one case. So in the linked example, it would be "6 + ∞," which says the same thing without contradicting itself with a lengthy diatribe.
<br>(Also I had to restrain myself from using * rather than x because that's how I'm used to writing multiplication in equations. Thanks, higher-level math classes defaulting to "X" as a variable! But the asterisk could be used too, anyway.)


<h2 style="color:black">How To</h2>
'''Proposer''': {{User|Doc von Schmeltwick}}<br>
<h3 style="color:black">Rules</h3>
'''Deadline''': September 30, 2024, 23:59 GMT
#If users have an idea about improving the wiki or managing its community, but feel that they need community approval before acting upon that idea, they may make a proposal about it. They must have a strong argument supporting their idea and be willing to discuss it in detail with the other users, who will then vote about whether or not they think the idea should be used. Proposals should include links to all relevant pages and [[MarioWiki:Writing Guideline|Writing Guideline]] proposals ''must'' include a link to the draft page.
#Anyone can comment on proposals whether logged-in or not, but only registered users can create or vote on proposals.
#Proposals end at the end of the day (23:59) one week after voting starts, except for Writing Guidelines and Talk Page Proposals, which run for two weeks. ('''All times GMT.''')
#*For example, if a proposal is added at any time on Monday, August 1, 2011, the voting starts immediately and the deadline is one week later on Monday, August 8, at 23:59 GMT.
#Every vote should have a reason accompanying it. Agreeing with or seconding a previously mentioned reason given by another user is accepted.
#Users who feel that certain votes were cast in bad faith or which truly have no merit can address the votes in the Comments section. Users can ask a voter to clarify their position, point out mistakes or flaws in their arguments, or call for the outright removal of the vote if it lacks sufficient reasoning. Users may '''not''' remove or alter the content of anyone else's votes. Voters can remove or rewrite their own vote at any time, but the final decision to remove another user's vote lies solely with the [[MarioWiki:Administrators|administrators]].
#If a user makes a vote and is subsequently blocked for any amount of time, their vote is removed. However, if the block ends before the proposal ends, then the user in question holds the right to re-cast their vote. If a proposer is blocked, their vote is removed and "(banned)" is added next to their name in the "Proposer:" line of the proposal, which runs until its deadline as normal. If the proposal passes, it falls to the supporters of the idea to enact any changes in a timely manner.
#No proposal can overturn the decision of a previous proposal that is less than '''4 weeks''' ('''28 days''') old.
#Any proposal that has three votes or less at deadline will automatically be listed as "[[Wikipedia:Quorum|NO QUORUM]]." The original proposer then has the option to relist said proposal to generate more discussion.
#All proposals that end up in a tie will be extended for another week. Proposals with more than two options must also be extended another week if any single option does not have a majority support: i.e. more than half of all votes cast must be for a single option, rather than one option simply having more votes than the other options.
#If a proposal has more than ten votes, it can only pass or fail by a margin of '''three''' votes. In other words, one option must have 50% + 3 of all votes cast. This means that if a basic two-option proposal reaches the deadline and the total number of votes for each option differ by two or less votes, the deadline will be extended for another week. Proposals with more than two options require more precise counting of votes to determine if an extension is necessary.
#Proposals can only be extended up to three times. If a consensus has not been reached by the fourth deadline, the proposal fails and can only be re-proposed after four weeks, at the earliest.
#All proposals are archived. The original proposer must '''''take action''''' accordingly if the outcome of the proposal dictates it. If it requires the help of an administrator, the proposer can ask for that help.
#If the administrators deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to remove it at any time.
#Proposals can only be rewritten or deleted by their proposer within the first three days of their creation. However, proposers can request that their proposal be deleted by an [[MarioWiki:Administrators|administrator]] at any time, provided they have a valid reason for it. Please note that cancelled proposals must also be archived.
#There should not be proposals about creating articles on an underrepresented or completely absent subject, unless there is major disagreement about whether the content should be included. To organize efforts about completing articles on missing subjects, try setting up a [[ForumBoard:57|collaboration thread on the forums]].
#Proposals cannot be made about promotions and demotions. Users can only be promoted and demoted by the will of the [[MarioWiki:Administrators|administration]].
#No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.


<h3 style="color:black">Basic Proposal and Support/Oppose Format</h3>
====Support====
This is an example of what your proposal must 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]". Proposals presenting multiple alternative courses of action can have more than two voting options, but what each voting section is supporting must be clearly defined.
#{{User|Doc von Schmeltwick}} - Per
-----
#{{User|Altendo}} - This doesn't sound like a bad idea, although I do think there should be an asterisk like "*" instead which leads to a note saying "not including the infinite [enemy] spawning from [number] [method]", as enemies can spawn in different ways, and showing how they spawn could still be useful. If we just show "∞ x [number]", it wouldn't show how Goombas are spawned in (the linked page doesn't specify how they are spawned in otherwise). But I do like the idea of shortening the "count" section of tables.
<nowiki>===[insert a title for your proposal here]===</nowiki><br>
#{{User|ThePowerPlayer}} Per Altendo. This formatting is much better, but I also think some note of where the infinite enemy spawner(s) originate from should be preserved.
<nowiki>[describe what issue this proposal is about and what changes you think should be made to improve how the wiki handles that issue]</nowiki>
#{{User|Super Mario RPG}} Per all.


<nowiki>'''Proposer''': {{User|[enter your username here]}}<br></nowiki><br>
====Oppose====
<nowiki>'''Deadline''': [insert a deadline here, 7 days after the proposal was created, at 23:59 GMT. (14 days for </nowiki>[[MarioWiki:Writing Guideline|Writing Guidelines]] and [[#Talk Page Proposals|Talk Page Proposals]])
#{{User|Hewer}} I don't see the benefit of changing this. The current wording is straightforward and succinct, I'd expect the reader to understand "6 (not including the infinite Goombas spawning from one Warp Pipe)" easily. Changing it to "6 + ∞" just makes it less clear for no reason, I'd definitely be confused if I saw that and didn't know this specific context. The fact that the other support votes have also brought up how doing this risks losing the specific information completely (and suggested a more long-winded solution that seems to contradict the proposal) compels me to oppose this more.
#{{User|Waluigi Time}} Per Hewer.
#{{User|FanOfYoshi}} Per all.
#{{User|Axii}} Per Hewer
#{{User|SolemnStormcloud}} Per all.
#{{User|EvieMaybe}} we don't need to throw a mathematical equation at people


<nowiki>====Support====</nowiki><br>
====Comments====
<nowiki>#{{User|[enter your username here]}} [make a statement indicating that you support your proposal]</nowiki>
{{@|Hewer}} - "succinct" would generally imply "short, sweet, and to-the-point," of which the current method is the exact opposite. I'm fine with including an asterisk-note next to the infinity, but the current one is much too bloated, outright admits to stating false information, and since the tables are center-aligned with that horizontal-bloat, it makes it look incredibly awkward. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 12:41, September 17, 2024 (EDT)
 
:I guess we just have totally opposing opinions on this one, because I don't personally find ten words of explanation to be "much too bloated", would rather "state false information" (not really what's happening because it's immediately clarified and the only way not to state any "false" info would be to just put "∞" which helps no one) than obscure the meaning of what we're trying to say, and I don't at all think the somewhat wider tables look "incredibly awkward". This is a case where I feel giving more explanation than "6 + ∞" is necessary for the sake of conveying clear information, so I'd rather prioritise that over having a thin table (which I still don't really see why that's so desirable). {{User:Hewer/sig}} 03:19, September 18, 2024 (EDT)
<nowiki>====Oppose====</nowiki>
 
<nowiki>====Comments====</nowiki>
-----
Users will now be able to vote on your proposal, until the set deadline is reached. Remember, you are a user as well, so you can vote on your own proposal just like the others.
 
To support, or oppose, just insert "<nowiki>#{{User|[add your username here]}}</nowiki> at the bottom of the section of your choice. Just don't forget to add a valid reason for your vote behind that tag if you are voting on another user's proposal. If you are voting on your own proposal, you can just say "Per my proposal".


__TOC__<!--
If this proposal passes, I think that a dedicated template should be made; something like <code><nowiki>{{infinite respawn|5|3}}</nowiki></code> that would produce "{{hover|5 + (∞ × 3)|5 (not including the 3 infinite spawning points)}}". Or at the very least, use an actual "×" symbol rather than "x". {{User:Jdtendo/sig}} 12:08, September 19, 2024 (EDT)


<center><span style="font-size:200%">CURRENTLY: '''{{#time: H:i, d M Y}} (GMT)'''</span></center>
I'll refrain from voting because I have a visceral reaction to anything that resembles a math formula, and I want as little as possible for personal preference to seep into my vote. That's not to say I don't understand what's being proposed, in fact it makes perfect sense if you're aiming strictly for concision, but you'd need to take into account how accessibly that information is communicated--you'd need to establish that "infinity symbol" stands for infinite enemy spawning point, which is not immediately clear. At that point, you'd go for a relatively lengthy explanation nonetheless. Though, I agree that the phrasing in that page you linked doesn't sound inclusive. I think something like "5 individual, 3 infinite spawning points" works better if we're going down this path.<br>If the proposal passes, I'd like to see it implemented in the manner Jdtendo suggests above.<br>EDIT: I'm aware there's [[Mario Kart Tour race points system#Bonus-points boost|already plenty of math on this wiki that has potential to confound people]], but in that case, not only is its succinctness a better way to explain how the game's scoring system works (as opposed to paragraphs-long descriptions), but it's taken straight out of the game as well. I'd say, use math formulas only when you're sure prose would be of less service to its intended audience: people looking up how many enemies are in a level aren't necessarily interested in complex gameplay dynamics. {{User:Koopa con Carne/Sig}} 13:12, September 19, 2024 (EDT), edited 14:55, September 19, 2024 (EDT)


==New features==
===Add {{iw|mw|Extension:WikiLove|WikiLove}} extension (includes templates)===
Inspired by my recently passed Thanks proposal and engagement with editors over time, I think a precedent has been set to add more [[Wikipedia:WikiLove|WikiLove]] features on to the wiki so that (willing) members may enjoy engaging with one another and feel motivated when others compliment their work, or just personal appreciations.


The main thing this proposal is focused on is the {{iw|mw|Extension:WikiLove|MediaWiki extension}}, which is called WikiLove. On the rationale of the {{iw|mw|WikiLove}} page, it says that lesser experienced users may feel discouraged when looked down upon by more experienced editors as they try to figure out how to do wikis, and this could help motivate not only newer editors, but also more experienced editors.


<br>
It says one can make custom WikiLove messages. Being a wiki on ''Super Mario'', I think this wiki could aim to do WikiLove messages themed around the ''Super Mario'' franchise. The community can decide on WikiLove messages if this proposal passes (e.g., one message could say like "You're a super star like Mario"), as well as personalized ones toward editors. But if others do not want involvement, the courtesy policy can be updated to reflect this.
-->


<h2 style="color:black">Talk Page Proposals</h2>
I wish there were more images to show, but here's a [[mw:File:WikiLove-screenshot-2014.png|representative image]] to show how WikiLove would look. Would it be worth giving this a try?
All proposals dealing with a single article or a specific group of articles are held on the talk page of one of the articles in question. Proposals dealing with massive amounts of splits, merges or deletions across the Wiki should still be held on this page.


:''For a list of all settled Talk Page Proposals, see [[:Category:Settled Talk Page Proposals|here]].''
'''Edit:''' For clarity, if this proposal passes, this also means WikiLove templates will be created, like how Wikipedia has them. It can be what the community decides, and categorical examples could include {{iw|wikipedia|Template:Happy New Year|seasonal}}, {{iw|wikipedia|Template:Doggy|animals}}, {{iw|wikipedia|Template:Glass of milk|drinks}}, or {{iw|wikipedia|Template:Friend|expressing friendships}}, and obviously ''Super Mario''.


<h3 style="color:black">Rules</h3>
'''Proposer''': {{User|Super Mario RPG}}<br>
#All active talk page proposals must be listed below in chronological order (new proposals go at the bottom). All pages affected must be mentioned in the ''brief'' description, with the talk page housing the discussion linked to directly via "({{fakelink|Discuss}})". If the proposal involved a page that is not yet made, use {{tem|fakelink}} to communicate its title. The '''Deadline''' must also be included in the entry. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links. Place {{tem|TPP}} under the section's header, and once the proposal is over, replace the template with {{tem|SettledTPP}}.
'''Deadline''': September 20, 2024, 23:59 GMT
#All rules for talk page proposals are the same as mainspace proposals (see the "How To" section above), with the exceptions made by Rules 3 and 4 as follows:
#Voting in talk page proposals will be open for two weeks, not one. ('''All times GMT.''')
#*For example, if a proposal is added at any time on Monday, August 1, 2011, it ends two weeks later on Monday, August 15, 2011, at 23:59 GMT.
#Talk page proposals may be closed by the proposer at any time if both the support ''and'' the oppose sides each have fewer than five votes.
#The talk page proposal '''must''' pertain to the article it is posted on.
#When a talk page proposal passes, replace its deadline with "Passed" but do not remove it from the list below until the proposed changes have been enacted.
 
===List of Talk Page Proposals===
*Make separate articles for [[Greenie]]s wearing suits of armor or mummy wrappings ([[Talk:Greenie#Mummies and Knights|Discuss]]) '''Deadline:''' May 18, 2013, 23:59 GMT
*Delete {{Tem|SMB3 Levels}} ([[Template talk:SMB3 Levels#Delete this template|Discuss]]) '''Deadline:''' May 27, 2013, 23:59 GMT
*Create a BJAODN subpage for levels ([[MarioWiki talk:BJAODN#Create a subpage for levels|Discuss]]) '''Deadline:''' May 29, 2013, 23:59 GMT
 
==Writing Guidelines==
''None at the moment.''
 
==New Features==
===Give users the option to not leave redirects when moving pages===
Currently, it seems that only admins have this option. Though sometimes the admins themselves ask people to not leave redirects, but it is not possible as they don't have that option. For example; (taken from Baby Luigi and Tucayo's talk pages)
 
<blockquote>
Hello. Please try not to leave file redirects the next time you move an image; they serve no use. --{{User:Tucayo/sig}} 12:02, 11 May 2013 (EDT)<br>
I'm sure I am unable to move files without leaving a redirect. I don't think regular users have the option to do that, since I don't see the option anywhere, and I would have preferred it. {{User:Baby Luigi/sig}} 13:53, 11 May 2013 (EDT)
</blockquote>
 
The reason I am proposing this is simple; like Tucayo said, sometimes redirects serve no purpose, like when moving files. This would also save the admins some time, as they don't have to keep checking the to be deleted category for stuff that could be avoided if this was in place before.
 
'''Proposer:''' {{User|Goomba}}<br>
'''Deadline:''' May 22, 2013, 23:59 GMT
 
====Give users the option====
#{{User|Goomba}} Per proposal.
 
====Don't give users the option====
#{{User|Baby Luigi}} As much as I like to have this feature, it is simply unfeasible. Moving the page without leaving a redirect is just like moving the page, but automatically deleting the redirect. Since users do not have the privilege to delete pages, this option cannot be done unless users have the right to delete pages.
#{{User|Walkazo}} - I don't think it's possible and even if it was, I think it's best to ''not'' muck around with deletion rights. It's really not a big deal to have to delete the automatically-created redirects; in fact, you could even think of it as just another way the admins can patrol and approve these changes.
#{{User|King Pikante}} Per all.
#{{user|NewSMBU}} Good idea, but not everyone can have the rights to delete a page or a file.
#{{User|Phoenix}} Per Walkazo.
#{{User|ThePremiumYoshi}} - Per all.
 
====Comments====
That was a mistake on my part, I wasn't aware users didn't see the "Don't leave a redirect" option. -- {{user|Tucayo}}
 
===Warning for editing large pages for mobile users (re-proposed feature)===
SPLIT FROM {{Plainlink|1=[http://www.mariowiki.com/index.php?title=MarioWiki:Proposals&diff=prev&oldid=1466741 MY COMMENT HERE]}}, RE-PROPOSED FROM {{User|Goomba}}'s [[MarioWiki:Proposals/Archive_33#Warning_for_editing_large_pages_for_mobile_users|ORIGINAL PROPOSAL]]
 
I made a comment [http://www.mariowiki.com/index.php?title=MarioWiki:Proposals&diff=prev&oldid=1466741 here] on [[MarioWiki:Proposals/Archive_33#Warning_for_editing_large_pages_for_mobile_users|the original proposal]] made by {{User|Goomba}} that instead of a template for large  pages that serves as a warning for mobile users, we could have something like this:
 
<pre><!-- WARNING: This page contains a large amount of content and may not be suitable for mobile browsers. Please take note of this before editing.--></pre>
 
That would put the warning only in the page's source, so that user's don't have to see templates littered around everywhere.
 
'''Proposer:''' {{User|Mariotime11}}<br>
'''Deadline:''' May 23, 2013, 23:59 GMT


====Support====
====Support====
#{{User|Mariotime11}} Per proposal.
#{{User|Super Mario RPG}} Per.
#{{User|ThePowerPlayer}} This would be a great form of positive feedback to counter the struggles faced by new and existing editors alike, since learning how to use a wiki is more difficult than you might expect. Ultimately, this should increase the feeling of community around the wiki to keep editing from feeling like a chore.
# {{User|Derekblue1}} I know people are happy with what I do ever since I update the Discord server on my progress on ''Mario is Missing!''. The WikiLove extension will make people feel more connected. I see this as a boost of encouragement just like the Thanks extension.
#{{User|Technetium}} Seems really fun, especially if we go full on Mario theming with it!
#{{User|Sparks}} Hooray for more positivity!
#{{User|DryBonesBandit}} <s>give me my glass o' milk now</s> This seems like it would be a nice addition to the wiki. Per all!
#{{User|FanOfRosalina2007}} I know I had a rough time when I first joined some of the websites I'm currently on today, so I'm all for this! I just love having the option to thank people and encourage them! Per all!
#{{User|BMfan08}} Sure! I'm all for kittens (I could even make do with [[Kitten|Mario kittens]]). Per all!


====Oppose====
====Oppose====
#{{User|Walkazo}} - It's best to not clutter up the page sources with unnecessary and easily missed or ignored advisories. As was argued in the last proposal, reverting the odd accident here and there is not a problem, and not worth all this fuss.
#{{User|Turboo}} - Per Walkazo.
#{{User|LeftyGreenMario}} This template is pretty much like closing the canary cage after the canary escapes. The warning says, "Please take note of this before editing.", but since it appears only in the code, then the user has to click edit button to view this warning in the first place. Not to mention, such warnings like that are very easy to overlook, as what Walkazo had said. If we '''must''' warn mobile users, we should create a separate page showing a list of articles that mobile phones may have a problem on so that way, users know what articles to have caution on and we won't have a useless warning in the article, but even then, there's a reason I bolded "must".
#{{User|King Pikante}} Per all.
#{{User|ThePremiumYoshi}} - Per Walkazo.
#{{User|Jazama}} Per all
#{{User|Mario4Ever}} Per Walkazo.
#{{User|Phoenix}} Per Walkazo.
#{{user|NewSMBU}} Warnings written as hidden comments in articles can be easily overlooked. Not even a category would work easily.


====Comments====
====Comments====
@LeftyGreenMario I don't think users would see a category like that either. {{User|Mariotime11}}
{{@|ThePowerPlayer}} I realized WikiLove templates could fit into the scope of this proposal, so it's been updated, if your "Support" will count towards voting for those as well. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 22:24, September 13, 2024 (EDT)
:Maybe not, but I can't find any other ideas to implement this without making the page look distracting or the warning overlooked. {{User|LeftyGreenMario}}
 
===Add a Level-up system to the wiki===
A level-up system to the wiki would be a fun way to encouarage people to edit articles and make the wiki better, for example, a new article could give someone 100xp, an edit would give someone 25, and a minor edit would give someone 10. Userspace edits maybe wouldnt count, and undone edits or deleted pages could take away XP, so admins wouldnt have to manually take away the troll's XP, although this would take a long time to make, you could establish a team to make this if the proposal passes. One could start out as a Goomba, and maybe work up by editing to be a Mario. Also, depending on people's rank, it would make it easier to decide the patrollers,etc.
 
'''Proposer''': {{User|Robecuba}}<br>
'''Deadline''': May, 25, 2013 23:59 GMT
 
====Support====
#{{User|Robecuba}} Per proposal, the wiki would be more accurate with more edits and more people would sign up
 
====Oppose====
#{{User|Yoshi876}} In theory it sounds great, but in practise I feel it'd get too complicated quickly and people might abuse this by purposefully doing a spelling mistake then changing it back, or accidnetly forget something and then get more XP for doing something they intended to do in the first place. Also I'm not sure whether it'd be possible to do something like this as it'd require quite a bit of coding.
#{{User|GBAToad}} Per Yoshi876. Wikia implements this system and people abuse it easily by making ridiculous contributions just to get more privileges.
#{{User|Prince Bowser Junior}} Per all.
#{{User|Baby Luigi}} Users gaining privileges depend more on the quality of the edits, not the quantity. Simple. Quality always beats out quantity.
#{{User|Turboo}} - Per all.
#{{User|King Pikante}} Per all.
#{{User|Mariotime11}} Per all, especially Baby Luigi.
#{{user|NewSMBU}} No. Just no. This could be abused and if you were to make sure so that if you get a certain amount of points you get new user rights or, should I say, level-up, everyone would abuse it to "monopolize" the site or whatever.
#{{User|Walkazo}} - Needlessly complicated, easily abused and completely unnecessary. Edit counting is already the wrong mindset to have about contributing to the wiki, and a point and rank system would be even worse.


====Comments====
I really like this, but does Porplemontage know about this proposal? I know he approved and implemented the "Thanks" extension, but I just wanna be sure! {{User:Sparks/sig}} 22:37, September 13, 2024 (EDT)
:{{@|Sparks}} The proposal is easily viewable on this page. And the proposal basically concerns a WikiLove system in general (since I updated it to also mention templates), so something like {{fake link|MarioWiki:WikiLove}} page can be set up with the corresponding templates. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 08:17, September 14, 2024 (EDT)
::Alrighty! Good to know. {{User:Sparks/sig}} 08:52, September 14, 2024 (EDT)


==Removals==
==Removals==
Line 168: Line 73:


==Changes==
==Changes==
===Allow Cursing===
===Rename the remaining baseball teams to their current titles===
One of the first proposals ever made here was to ban cursing, yes while there are children on this site, there are most likely are to not know the swear words or use them themselves anyway. Back when I first joined in 2011, I didn't like swearing very much and actually I was against swearing as a whole, however today I have no problem with it and it actually prevents us saying are true feelings. Yes I do think overswearing should be banned and swearing at the mods. I do think users can disallow swearing on their talk page if they don't to see the words.
One thing is certain: ''Mario Super Sluggers'' was first released in Japan almost three years after ''Mario Superstar Baseball'' was first released in said country. In this case, I humbly suggest that there's a possibility to move the remaining baseball team pages with their ''Mario Superstar Baseball'' name to their current name from ''Mario Super Sluggers''. So far, the current names already in use are the [[Peach Monarchs]] and [[Bowser Monsters]].


Also there's a moderate about of swearing down at the forum and userpeadia and yet children go to these places as well. people don't care much about this anyway and they don't really offend anyone unless used to offend, I don't mind them when your not using them to offend others. I think we should officially remove this rule as a whole
The following of the remaining pages will be affected by the move:
*[[Mario Sunshines]] → {{fake link|Mario Fireballs}}
*[[Yoshi Islanders]] → {{fake link|Yoshi Eggs (team)}}
*[[Wario Greats]] → {{fake link|Wario Muscles}}
*[[DK Kongs]] → {{fake link|DK Wilds}}


'''Proposer''': {{User|NSY}}<br>
Once this proposal passes, we'll be able to move the remaining baseball teams with their ''Mario Superstar Baseball'' names to their current ''Mario Super Sluggers'' titles.
'''Deadline''': May 20, 2013, 23:59 GMT
 
'''Proposer''': {{User|GuntherBayBeee}}<br>
'''Deadline''': September 19, 2024, 23:59 GMT


====Support====
====Support====
#{{User|NSY}} Per proposal  
#{{User|GuntherBayBeee}} Per proposal.
#[[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) - Kept forgetting to do this during my ongoing sports project.
#{{User|Jdtendo}} The most recent names should be prioritized.
#{{User|Super Mario RPG}} Definitely.
#{{User|ThePowerPlayer}} Per (baseb)all.
#{{User|Hewer}} Don't see why not.
#{{User|Killer Moth}} Per proposal. Sounds like a good idea.
#{{User|Technetium}} Per proposal.
#{{User|Windy}} Per all.
#{{User|BMfan08}} Per all. <s>I wish we had more than just one team in ''Sluggers''</s>
#{{User|FanOfRosalina2007}} Consistency. Per all.


====Oppose====
====Oppose====
#{{User|A Paragoomba and the Koopa Bros.}} No, kids under the age of 7 surf this website and might use swears in life, and thus swearing should not be allowed
#{{User|Iggy Koopa Jr}} I am against swearing. So vulgar. You can't just make swearing legal.
#{{User|LeftyGreenMario}} The problem with this proposal is that nowhere is stated explicitly swearing is banned, so what this proposal is asking for (allowing swearing) is moot. The main reason we discourage swearing is the same reason society discourages swearing in public, formal locations; it's crude and unprofessional in these settings. Userpedia is way more informal than MarioWiki, so it's a fairly bad analogy. That being said, there is almost never an appropriate time where you have to swear anyway, since venting is a terrible way to deal with your anger, and if you're really angry about something, it's always best to sound calm and controlled. Overall, though, this proposal is not needed.
#{{User|Rpg gamer}} Per all, especially LeftyGreenMario. No Mario games have swearing in and this a Mario wiki. Do other wikis swear? No.
#{{user|NewSMBU}} - What the person above the person above me said. This is a pointless and unnecessary proposal.
#{{User|MeritC}} Per all; you're forgetting that this Wiki represents the Mario series itself, which is supposed to be family friendly content wise for the most part. So, no.
#{{User|BowserJunior}} Per LGM, this is unnecessary.
#{{User|King Pikante}} Per all.
#{{User|Walkazo}} - Per LGM and Turboo in the comments. There's no rule to overturn here: the  "ban swears" proposal is six years old and no longer enforced to the letter; [[MarioWiki:Courtesy#Swear|the Courtesy Policy merely says]] that users should use profanity in moderation and respect others' wishes if they don't want cursing on their talk page. The only thing you absolutely can't do is swear ''at'' people.
#{{User|Mario4Ever}} Per Walkazo.
#{{User|ThePremiumYoshi}} - Very unnecessary; per all.
#{{User|Prince Bowser Junior}} Per all.


====Comments====
====Comments====
@A Paragoomba and the Koopa Bros, will seeing these words really turn them away from this site? {{user|NSY}}
===Decide how to handle the "latest portrayal" section in infoboxes===
:RE: I changed that, but still, I've seen kids swear. {{User|A Paragoomba and the Koopa Bros.}}
Currently, in infoboxes, the "latest portrayal" section of it is inconsistent across characters. When ''[[Paper Mario: The Thousand-Year Door (Nintendo Switch)|Paper Mario: The Thousand-Year Door]]'' came out, for example, it listed both [[Kevin Afghani]] (Mario's current voice actor) and [[Charles Martinet]] (who voices Mario in ''The Thousand-Year Door'' from original archival voicing) as Mario's latest portrayals, yet [[Jen Taylor]] (whose voice clips were also reused) wasn't added to Peach's latest portrayal. Therefore, to make these infoboxes consistent for characters with multiple voice actors, I am proposing several options:
*Option 1: Only add in the current voice actor for the character (reissues with archival voices from retired voice actors will not be added).
*Option 2: Only add in the voice actor for the character in the most recent game (reissues with archival voices will overtake the "current" voice actor if the latest one did not record voice lines for the character, the current voice actor will be re-added to the infobox following the release of a game with voices from the current voice actor).
*Option 3: Add both the current voice actor and the voice actor for the latest release (this puts two voice actors in the "latest portrayal" section if the character is voiced via archival footage from a retired voice actor, but the current voice actor also gets to remain. When a new game comes out with new voice lines from the current voice actor, the voice actor from the previous release will be removed).
*Option 4: Do nothing (infoboxes with both actors will not change, and same with infoboxes with the current actor even if a game featuring archival voicing from a retired voice actor is the latest one).


I don't see the point of this proposal; swearing is allowed in mainspace for direct quotes, and there's nothing that prevents people from swearing on their or others' userspace (assuming the user is OK with it, in the latter case). - {{User|Turboo}}
With regards to mixed use of voices, if multiple voice actors voice a single character in a single game, the latest person who voiced the character as of the game's release takes priority, meaning that archival voices from retired actors will not appear in the infobox if the character in that game is also (and especially mostly) voiced by the current actor for that character. As for other media (like ''[[The Super Mario Bros. Movie]]''), whether or not the game/other media actor takes priority or if both should be listed is also of question, but I will likely wait until the [[Untitled The Super Mario Bros. Movie follow-up|follow-up]] to create that proposal.


Creating this type of proposal might cause… well… stuff. You should check what happened [[Talk:Bob Hoskins#Proposal|here]]. {{user|newSMBU}}
'''EDIT:''' With regards to [[User:Tails777|Tails777]]'s vote, I don't know exactly how it will play out if Option 3 passes, although I will say if a game (like a compilation) does have a single character voiced by more than one voice actor who isn't the current one, the latest voice actor whose voice clips are used in the game as of the game's release will be the second option added to the infobox (like Peach in ''3D All-Stars'', who would've listes Samantha Kelly as her current and ''Galaxy'' voice actress, as well as Jen Taylor as her ''Sunshine'' voice actress, although I don't think it would be that consistent because it would exclude Leslie Swan, her ''64'' voice actress, but since Jen Taylor was the more recent of the two, she is the one who is listed).


@Turboo Wasn't [[Bob Hoskins|this]] the only article where there's swearing? I don't see why there would be any other direct quotes related to the <i>Mario</i> series that would need to have profanity. {{User|Mariotime11}}
'''Proposer''': {{User|Altendo}}<br>
'''Deadline''': September 21, 2024, 23:59 GMT


:Yes, but my point is that it's allowed in general (so if we had to quote something else like that, it would be fine). - {{User|Turboo}}}
====Only add in the current voice actor====
#{{User|Altendo}} Primary choice. "Latest portrayal", to me, means the person who last voiced the character, and I don't think archival voices should count as this, especially since those voices were recorded before the current voice actor. This also avoids the issues of multiple voice actors voicing a single character in compilations and switching/adding or removing voice actors when reissues and original games come out (as described below).
#{{User|Shadow2}} Re-using old sound clips has no bearing on a character's "Latest portrayal". Charles does not voice Mario anymore, and to list him as such just because of older re-used sound clips is misrepresentative.
#{{User|Hewer}} Per both, this is the less misleading option (the infobox doesn't specify whether the "latest" voice actor was just re-usage of old voice clips, so listing both Charles and Kevin gives the impression that they're both actively voicing Mario, which is wrong).
#{{User|Super Mario RPG}} Per all.


What Turb says is correct, this proposal is pointless. -- {{user|Tucayo}}
====Only add in the the voice actor for the "latest" game====
#{{User|Altendo}} Tertiary choice. If "Latest portrayal" really means the person who voiced the character in the latest game, regardless of said actor's as-of-game-release status, then maybe archival voices can count because it is the voice of the character in the "latest" game. I do not recommend this option as this will cause a lot of infobox editing and switching voice actors when reissues (particularly ports and remasters) do inevitably come out, and if a compilation game (like ''[[Super Mario 3D All-Stars]]'') comes out, multiple voice actors who voice the same character in a single compilation (like [[Princess Peach]], who had [[Leslie Swan|three]] [[Jen Taylor|voice]] [[Samantha Kelly|actresses]] in a single compilation) will stack up in the infoboxes. And when a new game comes out, all of that is thrown out the window, reverting to their current voice actor. [[MarioWiki:Proposals/Archive/63#Rename "Latest portrayal" section in character infobox to "Notable portrayals"|This is why some were against enforcing the absolute "latest" portrayals in a previous proposal]]. The only reason why I am for this is consistency.
====Add both current and latest voice actor====
#{{User|Altendo}} Secondary choice. It feels nice to respect both the voice actor who is currently voicing the character and the person whose voices, even in archival, are the sole ones used in the latest game. However, my point about voice actor switching, while not as big as an issue because archival voice actors will only be added rather than replace the current one, still kind of stands because reissues will add the archival voice actor for one game, only to remove it when a new game comes out. Additionally, if compilations ''only'' contain voices from retired voice actors, this will stack it up even more (although for ''3D All-Stars'', it still wouldn't change much due to Peach's ''[[Super Mario Galaxy]]'' voice actress still being her current one). Still, this does make the infoboxes consistent.
#{{User|Tails777}} I agree with this one more; it's best to keep it up to date when it comes to VAs, but it isn't uncommon for various games to recycle voice clips (TTYD once again being a good example). I feel it is best to at least acknowledge if voice clips get recycled in this respect, though I also feel this should be limited to one at a time, in case there are examples where someone had more than even two voice actors.
#{{User|FanOfYoshi}} Per all.


What's WRONG with swearing? They're just words, nothing "evil" about them. When you think about it, words themselves are just grunts made by the animal known as homo sapiens. Also, the Bob Hoskins article shoots f-bombs everywhere. {{User|Binarystep}}
====Do nothing====
:The words themselves have no meaning. It's the context the establishes them, and swearing in MarioWiki is totally out of context and should not be used. Exceptions apply, and that exception happens to be a direct quote. That's fine, since we are presenting that quote objectively as possible. In general, swearing does not fit in this wiki. The proposal, however, is asking for allowing swearing, and the main problem is that swearing was never really banned in the first place, just discouraged. MarioWiki should be as formal and family-friendly (the wiki covers as family-friendly subject), though, which is why we strongly discourage it. {{User|LeftyGreenMario}}
::Take into consideration that most TV programs usually censor swearing and that professionals usually NEVER use it and you understand why swearing is HIGHLY discouraged. It doesn't make you smart, it's unprofessional, and it's highly discouraged in formal areas like these. {{User|Baby Luigi}}
 
===Do not allow un-autoconfirmed users to create their own user talk pages===
Lately, I've seen some users create their own user talk pages just to put things on them that would normally go on their user page. This is both violating the Userspace Policy and is a big loophole in the "create your userpage" privilege when becoming autoconfirmed. What I propose is simple; the account onwers ''themselves only'' cannot create their own user talk pages, but others can. For example; {{fakelink|MarioLover12345}} made an account, and I gave him/her the welcome template. He/she is now free to edit their user talk page. But, if no one gives him/her a Welcome template, he/she cannot start it him/herself until he/she is autoconfirmed. It's as simple as that.
 
'''Proposer:''' {{User|Goomba}}<br>
'''Deadline:''' May 22, 2013, 23:59 GMT
 
====Support====
#{{User|Goomba}} Per proposal.
 
====Oppose====
#{{User|YoshiKong}} &ndash; Per the comments made by Turboo and myself.
#{{User|King Pikante}}. Per YoshiKong.
#{{User|Turboo}} - Per my and YoshiKong's comments.
#{{User|Yoshi876}} Per comments below me
#{{User|ThePremiumYoshi}} - Per all.
#{{user|NewSMBU}} What person number (6 − 3) × 4 ÷ 6 − 1, a.k.a. YoshiKong said.
#{{User|Mario4Ever}} Per YoshiKong and Turboo.
#{{User|Walkazo}} - Per YoshiKong and Turboo.
#{{User|LeftyGreenMario}} Per all; this feature creates only problems. New users need some ease to begin to be familiar with MarioWiki, and giving them more restrictions like that doesn't help.
#{{User|Luigi700MarioWiki}} I would advise against it, perhaps it's too restricted.


====Comments====
====Comments====
But, what if they wanted to post a question they had on their own talk page? I often see that happening, and I don't think that should be prevented. And are we sure that restricting the creation of their own user talk only until becoming autoconfirmed is feasible? --{{User|YoshiKong}} 03:04, 15 May 2013 (EDT)
I'm conflicted between simply listing only whoever is currently voicing the character vs. potentially opening a can of worms by listing multiple actors from archival clips, even though that would respect the portrayals from the most recent game whether it used newly recorded or archived voices. No matter how this proposal ends up, I think that a future proposal should consider standardizing the "Portrayals" header in the character articles themselves. For Mario, the list of portrayals does a great job at comprehensively documenting everyone who has officially voiced Mario, but falters in conveying the inconceivable magnitude of media in which Martinet has voiced Mario, and how much he has contributed to the character's brand recognition to the point where many people will continue to see him as ''the'' voice of Mario, even moving forward as Kevin Afghani takes on that role. {{User:ThePowerPlayer/sig}} 23:57, September 16, 2024 (EDT)
:They can ask an admin about said question, it doesn't specifically need to be on their talk page. And if restricting the creation of user pages is feasible, so is this. {{User|Goomba}}
 
If a user is that set on using their talk page as their temporary userpage, they could still do that after getting a Welcome template (I think distribution of these is mostly "oh, I feel like giving X a template" now that the bot is gone). If it's really that random and we have no idea who'll be trying to set up their user talk as a camp of sorts, what do you hope to achieve by implementing something like this? YoshiKong also has a valid point, since some users want to be heavily involved in their userspace from the beginning and others just want to ask a simple question or two on their talk page. - {{User|Turboo}}


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

Latest revision as of 15:13, September 19, 2024

Image used as a banner for the Proposals page

Current time:
Thursday, September 19th, 22:16 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.
  • "Vote" periods last for one week.
  • Any user can support or oppose, but must have a strong reason for doing so (not, e.g., "I like this idea!").
  • 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.

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 {{User|User name}}.

How to

Rules

  1. If users have an idea about improving the wiki or managing its community, but feel that they need community approval before acting upon that idea, they may make a proposal about it. They must have a strong argument supporting their idea and be willing to discuss it in detail with the other users, who will then vote about whether or not they think the idea should be used. Proposals should include links to all relevant pages and 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}}.
  2. Only registered, autoconfirmed users can create, comment in, or vote on proposals and talk page proposals. Users may vote for more than one option, but they may not vote for every option available.
  3. Proposals end at the end of the day (23:59) one week after voting starts, except for writing guidelines and talk page proposals, which run for two weeks (all times GMT).
    • For example, if a proposal is added at any time on Monday, August 1, 2011, the voting starts immediately and the deadline is one week later on Monday, August 8, at 23:59 GMT.
  4. Every vote should have a strong, sensible reason accompanying it. Agreeing with a previously mentioned reason given by another user is accepted (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 administrators.
    • 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 "(banned)" is added next to their name in the "Proposer:" line of the proposal, which runs until its deadline as normal. If the proposal passes, it falls to the supporters of the idea to enact any changes in a timely manner.
  7. No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
  8. 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.
  9. If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
  10. 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% support to win. If the margin is only one or two votes, then the first place option must have at least 60% support to win. If the required support threshold is not met, then the proposal is extended for another week.
    • Use the {{proposal check}} tool to automate this calculation; see the template page for usage instructions and examples.
  11. Proposals can only be extended up to three times. If a consensus has not been reached by the fourth deadline, then the proposal fails and can only be re-proposed after four weeks (at the earliest).
  12. 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.
  13. If the administrators deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to remove it at any time.
  14. Proposals can only be rewritten or canceled by their proposer within the first three days of their creation (six days for talk page proposals). However, proposers can request that their proposal be canceled by an administrator at any time, provided they have a valid reason for it. Please note that canceled proposals must also be archived.
  15. 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.
  16. Proposals cannot be made about promotions and demotions. Users can only be promoted and demoted by the will of the administration.
  17. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
  18. Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.

Basic proposal and support/oppose format

This is an example of what your proposal must 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 replace the whole variable including the squared brackets, so "[insert info here]" becomes "This is the inserted information", not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but what each voting section is supporting 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|[enter your username here]}}<br>
'''Deadline''': [insert a deadline here, 7 days after the proposal was created (14 for writing guidelines and talk page proposals), at 23:59 GMT, in the format: "September 19, 2024, 23:59 GMT"]

====Support====
#{{User|[enter your username here]}} [make a statement indicating that you support your proposal]

====Oppose====

====Comments====


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 "#{{User|[add 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 just say "Per my 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. Proposals dealing with a large amount of splits, merges, or deletions across the wiki should still be held on this page.

For a list of all settled talk page proposals, see MarioWiki:Proposals/TPP archive and Category:Settled talk page proposals.

Rules

  1. 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. Place {{TPP}} under the section's header, and once the proposal is over, replace the template with {{settled TPP}}.
  2. All rules for talk page proposals are the same as mainspace proposals (see the "How to" section above), with the exceptions made by Rules 3 and 4 as follows:
  3. Voting in talk page proposals will be open for two weeks, not one (all times GMT).
    • For example, if a proposal is added at any time on Monday, August 1, 2011, it ends two weeks later on Monday, August 15, 2011, at 23:59 GMT.
  4. The talk page proposal must pertain to the subject page of the talk page it is posted on.
  5. When a talk page proposal passes, it should be removed from this list and included in the list under the "Unimplemented proposals" section until the proposed changes have been enacted.

List of ongoing talk page proposals

  • Split Bowser's Flame from Fire Breath (discuss) Deadline: September 18, 2024, 23:59 GMT
  • Split Banana Peel from Banana (discuss) Deadline: September 18, 2024, 23:59 GMT
  • Consider the "Blurp" and "Deep Cheep" in the Super Mario Maker games an alternate design of Cheep Cheep with the former twos' designs as a cameo rather than a full appearance of the former two, in line with the game's own classification (discuss) Deadline: September 18, 2024, 23:59 GMT
  • Split truck into cargo truck and pickup truck (discuss) Deadline: September 21, 2024, 23:59 GMT
  • Split the navigation template for Donkey Kong between arcade and Game Boy versions (discuss) Deadline: September 21, 2024, 23:59 GMT
  • Merge Crocodile Isle (Donkey Kong 64) to Crocodile Isle (discuss) Deadline: September 21, 2024, 23:59 GMT
  • Prune "sports" games from Black Shy Guy in line with White Shy Guy and Red Boo (discuss) Deadline: September 21, 2024, 23:59 GMT
  • Determine what to do with the feather item from Super Mario 64 DS (currently on Wing Cap) (discuss) Deadline: September 21, 2024, 23:59 GMT
  • Add English to {{foreign names}} and retitle to {{international names}} (discuss) Deadline: September 26, 2024, 23:59 GMT
  • Allow usage of {{Release}} as a generic "flag list" template (discuss) Deadline: September 27, 2024, 23:59 GMT
  • Merge Preying Mantas with Jellyfish (discuss) Deadline: September 28, 2024, 23:59 GMT
  • Create article(s) for the SM64DS character rooms (discuss) Deadline: September 30, 2024, 23:59 GMT
  • Create an article for the Peach doll from Super Mario RPG: Legend of the Seven Stars (discuss) Deadline: September 30, 2024, 23:59 GMT
  • Remove the remaining non-Super Mario "stage gimmicks and hazards" from Super Smash Bros. (discuss) Deadline: October 1, 2024, 23:59 GMT
  • Remove non-Super Mario "stage cameos" from Super Smash Bros. (discuss) Deadline: October 1, 2024, 23:59 GMT

Unimplemented proposals

Proposals

Establish a standard for long course listings in articles for characters/enemies/items/etc., Koopa con Carne (ended June 8, 2023)
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 New Super Mario Bros. games, the Super Mario Maker games, Super Mario Run, or Super Mario Bros. Wonder
Expand use of "rawsize" gallery class, Doc von Schmeltwick (ended July 19, 2024)
Do not use t-posing models as infobox images, Nightwicked Bowser (ended September 1, 2024)
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)
Tag sections regarding the unofficially named planets/area in Super Mario Galaxy games with "Conjecture" and "Dev data" templates, GuntherBayBeee (ended September 10, 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)

Writing guidelines

Change how "infinitely respawning" enemies are counted in level enemy tables

Currently, the wiki lists enemy counts for each level in tables located in that level's article. This is all well and good, but the problem arises when infinitely respawning ones (like piped ones) are included. As seen here, this is awkwardly written as

  • "[number] (not including the infinite [enemy] spawning from [number] [method]),"

and why shouldn't it include them? That method of writing is ungainly, misleading, and bloats the table's width unnecessarily. Therefore, I propose the alternate writing of

  • "[number] + (∞ x [number]),"

with the "x [number]" and parentheses being removed if there is only one case. So in the linked example, it would be "6 + ∞," which says the same thing without contradicting itself with a lengthy diatribe.
(Also I had to restrain myself from using * rather than x because that's how I'm used to writing multiplication in equations. Thanks, higher-level math classes defaulting to "X" as a variable! But the asterisk could be used too, anyway.)

Proposer: Doc von Schmeltwick (talk)
Deadline: September 30, 2024, 23:59 GMT

Support

  1. Doc von Schmeltwick (talk) - Per
  2. Altendo (talk) - This doesn't sound like a bad idea, although I do think there should be an asterisk like "*" instead which leads to a note saying "not including the infinite [enemy] spawning from [number] [method]", as enemies can spawn in different ways, and showing how they spawn could still be useful. If we just show "∞ x [number]", it wouldn't show how Goombas are spawned in (the linked page doesn't specify how they are spawned in otherwise). But I do like the idea of shortening the "count" section of tables.
  3. ThePowerPlayer (talk) Per Altendo. This formatting is much better, but I also think some note of where the infinite enemy spawner(s) originate from should be preserved.
  4. Super Mario RPG (talk) Per all.

Oppose

  1. Hewer (talk) I don't see the benefit of changing this. The current wording is straightforward and succinct, I'd expect the reader to understand "6 (not including the infinite Goombas spawning from one Warp Pipe)" easily. Changing it to "6 + ∞" just makes it less clear for no reason, I'd definitely be confused if I saw that and didn't know this specific context. The fact that the other support votes have also brought up how doing this risks losing the specific information completely (and suggested a more long-winded solution that seems to contradict the proposal) compels me to oppose this more.
  2. Waluigi Time (talk) Per Hewer.
  3. FanOfYoshi (talk) Per all.
  4. Axii (talk) Per Hewer
  5. SolemnStormcloud (talk) Per all.
  6. EvieMaybe (talk) we don't need to throw a mathematical equation at people

Comments

@Hewer - "succinct" would generally imply "short, sweet, and to-the-point," of which the current method is the exact opposite. I'm fine with including an asterisk-note next to the infinity, but the current one is much too bloated, outright admits to stating false information, and since the tables are center-aligned with that horizontal-bloat, it makes it look incredibly awkward. Doc von Schmeltwick (talk) 12:41, September 17, 2024 (EDT)

I guess we just have totally opposing opinions on this one, because I don't personally find ten words of explanation to be "much too bloated", would rather "state false information" (not really what's happening because it's immediately clarified and the only way not to state any "false" info would be to just put "∞" which helps no one) than obscure the meaning of what we're trying to say, and I don't at all think the somewhat wider tables look "incredibly awkward". This is a case where I feel giving more explanation than "6 + ∞" is necessary for the sake of conveying clear information, so I'd rather prioritise that over having a thin table (which I still don't really see why that's so desirable). Hewer A Hamburger in Super Smash Bros. Brawl. (talk · contributions · edit count) 03:19, September 18, 2024 (EDT)

If this proposal passes, I think that a dedicated template should be made; something like {{infinite respawn|5|3}} that would produce "5 + (∞ × 3)". Or at the very least, use an actual "×" symbol rather than "x". Jdtendo(T|C) 12:08, September 19, 2024 (EDT)

I'll refrain from voting because I have a visceral reaction to anything that resembles a math formula, and I want as little as possible for personal preference to seep into my vote. That's not to say I don't understand what's being proposed, in fact it makes perfect sense if you're aiming strictly for concision, but you'd need to take into account how accessibly that information is communicated--you'd need to establish that "infinity symbol" stands for infinite enemy spawning point, which is not immediately clear. At that point, you'd go for a relatively lengthy explanation nonetheless. Though, I agree that the phrasing in that page you linked doesn't sound inclusive. I think something like "5 individual, 3 infinite spawning points" works better if we're going down this path.
If the proposal passes, I'd like to see it implemented in the manner Jdtendo suggests above.
EDIT: I'm aware there's already plenty of math on this wiki that has potential to confound people, but in that case, not only is its succinctness a better way to explain how the game's scoring system works (as opposed to paragraphs-long descriptions), but it's taken straight out of the game as well. I'd say, use math formulas only when you're sure prose would be of less service to its intended audience: people looking up how many enemies are in a level aren't necessarily interested in complex gameplay dynamics. -- KOOPA CON CARNE 13:12, September 19, 2024 (EDT), edited 14:55, September 19, 2024 (EDT)

New features

Add WikiLove extension (includes templates)

Inspired by my recently passed Thanks proposal and engagement with editors over time, I think a precedent has been set to add more WikiLove features on to the wiki so that (willing) members may enjoy engaging with one another and feel motivated when others compliment their work, or just personal appreciations.

The main thing this proposal is focused on is the MediaWiki extension, which is called WikiLove. On the rationale of the WikiLove page, it says that lesser experienced users may feel discouraged when looked down upon by more experienced editors as they try to figure out how to do wikis, and this could help motivate not only newer editors, but also more experienced editors.

It says one can make custom WikiLove messages. Being a wiki on Super Mario, I think this wiki could aim to do WikiLove messages themed around the Super Mario franchise. The community can decide on WikiLove messages if this proposal passes (e.g., one message could say like "You're a super star like Mario"), as well as personalized ones toward editors. But if others do not want involvement, the courtesy policy can be updated to reflect this.

I wish there were more images to show, but here's a representative image to show how WikiLove would look. Would it be worth giving this a try?

Edit: For clarity, if this proposal passes, this also means WikiLove templates will be created, like how Wikipedia has them. It can be what the community decides, and categorical examples could include seasonal, animals, drinks, or expressing friendships, and obviously Super Mario.

Proposer: Super Mario RPG (talk)
Deadline: September 20, 2024, 23:59 GMT

Support

  1. Super Mario RPG (talk) Per.
  2. ThePowerPlayer (talk) This would be a great form of positive feedback to counter the struggles faced by new and existing editors alike, since learning how to use a wiki is more difficult than you might expect. Ultimately, this should increase the feeling of community around the wiki to keep editing from feeling like a chore.
  3. Derekblue1 (talk) I know people are happy with what I do ever since I update the Discord server on my progress on Mario is Missing!. The WikiLove extension will make people feel more connected. I see this as a boost of encouragement just like the Thanks extension.
  4. Technetium (talk) Seems really fun, especially if we go full on Mario theming with it!
  5. Sparks (talk) Hooray for more positivity!
  6. DryBonesBandit (talk) give me my glass o' milk now This seems like it would be a nice addition to the wiki. Per all!
  7. FanOfRosalina2007 (talk) I know I had a rough time when I first joined some of the websites I'm currently on today, so I'm all for this! I just love having the option to thank people and encourage them! Per all!
  8. BMfan08 (talk) Sure! I'm all for kittens (I could even make do with Mario kittens). Per all!

Oppose

Comments

@ThePowerPlayer I realized WikiLove templates could fit into the scope of this proposal, so it's been updated, if your "Support" will count towards voting for those as well. Super Mario RPG (talk) 22:24, September 13, 2024 (EDT)

I really like this, but does Porplemontage know about this proposal? I know he approved and implemented the "Thanks" extension, but I just wanna be sure! link:User:Sparks Sparks (talk) link:User:Sparks 22:37, September 13, 2024 (EDT)

@Sparks The proposal is easily viewable on this page. And the proposal basically concerns a WikiLove system in general (since I updated it to also mention templates), so something like MarioWiki:WikiLove page can be set up with the corresponding templates. Super Mario RPG (talk) 08:17, September 14, 2024 (EDT)
Alrighty! Good to know. link:User:Sparks Sparks (talk) link:User:Sparks 08:52, September 14, 2024 (EDT)

Removals

None at the moment.

Changes

Rename the remaining baseball teams to their current titles

One thing is certain: Mario Super Sluggers was first released in Japan almost three years after Mario Superstar Baseball was first released in said country. In this case, I humbly suggest that there's a possibility to move the remaining baseball team pages with their Mario Superstar Baseball name to their current name from Mario Super Sluggers. So far, the current names already in use are the Peach Monarchs and Bowser Monsters.

The following of the remaining pages will be affected by the move:

Once this proposal passes, we'll be able to move the remaining baseball teams with their Mario Superstar Baseball names to their current Mario Super Sluggers titles.

Proposer: GuntherBayBeee (talk)
Deadline: September 19, 2024, 23:59 GMT

Support

  1. GuntherBayBeee (talk) Per proposal.
  2. Doc von Schmeltwick (talk) - Kept forgetting to do this during my ongoing sports project.
  3. Jdtendo (talk) The most recent names should be prioritized.
  4. Super Mario RPG (talk) Definitely.
  5. ThePowerPlayer (talk) Per (baseb)all.
  6. Hewer (talk) Don't see why not.
  7. Killer Moth (talk) Per proposal. Sounds like a good idea.
  8. Technetium (talk) Per proposal.
  9. Windy (talk) Per all.
  10. BMfan08 (talk) Per all. I wish we had more than just one team in Sluggers
  11. FanOfRosalina2007 (talk) Consistency. Per all.

Oppose

Comments

Decide how to handle the "latest portrayal" section in infoboxes

Currently, in infoboxes, the "latest portrayal" section of it is inconsistent across characters. When Paper Mario: The Thousand-Year Door came out, for example, it listed both Kevin Afghani (Mario's current voice actor) and Charles Martinet (who voices Mario in The Thousand-Year Door from original archival voicing) as Mario's latest portrayals, yet Jen Taylor (whose voice clips were also reused) wasn't added to Peach's latest portrayal. Therefore, to make these infoboxes consistent for characters with multiple voice actors, I am proposing several options:

  • Option 1: Only add in the current voice actor for the character (reissues with archival voices from retired voice actors will not be added).
  • Option 2: Only add in the voice actor for the character in the most recent game (reissues with archival voices will overtake the "current" voice actor if the latest one did not record voice lines for the character, the current voice actor will be re-added to the infobox following the release of a game with voices from the current voice actor).
  • Option 3: Add both the current voice actor and the voice actor for the latest release (this puts two voice actors in the "latest portrayal" section if the character is voiced via archival footage from a retired voice actor, but the current voice actor also gets to remain. When a new game comes out with new voice lines from the current voice actor, the voice actor from the previous release will be removed).
  • Option 4: Do nothing (infoboxes with both actors will not change, and same with infoboxes with the current actor even if a game featuring archival voicing from a retired voice actor is the latest one).

With regards to mixed use of voices, if multiple voice actors voice a single character in a single game, the latest person who voiced the character as of the game's release takes priority, meaning that archival voices from retired actors will not appear in the infobox if the character in that game is also (and especially mostly) voiced by the current actor for that character. As for other media (like The Super Mario Bros. Movie), whether or not the game/other media actor takes priority or if both should be listed is also of question, but I will likely wait until the follow-up to create that proposal.

EDIT: With regards to Tails777's vote, I don't know exactly how it will play out if Option 3 passes, although I will say if a game (like a compilation) does have a single character voiced by more than one voice actor who isn't the current one, the latest voice actor whose voice clips are used in the game as of the game's release will be the second option added to the infobox (like Peach in 3D All-Stars, who would've listes Samantha Kelly as her current and Galaxy voice actress, as well as Jen Taylor as her Sunshine voice actress, although I don't think it would be that consistent because it would exclude Leslie Swan, her 64 voice actress, but since Jen Taylor was the more recent of the two, she is the one who is listed).

Proposer: Altendo (talk)
Deadline: September 21, 2024, 23:59 GMT

Only add in the current voice actor

  1. Altendo (talk) Primary choice. "Latest portrayal", to me, means the person who last voiced the character, and I don't think archival voices should count as this, especially since those voices were recorded before the current voice actor. This also avoids the issues of multiple voice actors voicing a single character in compilations and switching/adding or removing voice actors when reissues and original games come out (as described below).
  2. Shadow2 (talk) Re-using old sound clips has no bearing on a character's "Latest portrayal". Charles does not voice Mario anymore, and to list him as such just because of older re-used sound clips is misrepresentative.
  3. Hewer (talk) Per both, this is the less misleading option (the infobox doesn't specify whether the "latest" voice actor was just re-usage of old voice clips, so listing both Charles and Kevin gives the impression that they're both actively voicing Mario, which is wrong).
  4. Super Mario RPG (talk) Per all.

Only add in the the voice actor for the "latest" game

  1. Altendo (talk) Tertiary choice. If "Latest portrayal" really means the person who voiced the character in the latest game, regardless of said actor's as-of-game-release status, then maybe archival voices can count because it is the voice of the character in the "latest" game. I do not recommend this option as this will cause a lot of infobox editing and switching voice actors when reissues (particularly ports and remasters) do inevitably come out, and if a compilation game (like Super Mario 3D All-Stars) comes out, multiple voice actors who voice the same character in a single compilation (like Princess Peach, who had three voice actresses in a single compilation) will stack up in the infoboxes. And when a new game comes out, all of that is thrown out the window, reverting to their current voice actor. This is why some were against enforcing the absolute "latest" portrayals in a previous proposal. The only reason why I am for this is consistency.

Add both current and latest voice actor

  1. Altendo (talk) Secondary choice. It feels nice to respect both the voice actor who is currently voicing the character and the person whose voices, even in archival, are the sole ones used in the latest game. However, my point about voice actor switching, while not as big as an issue because archival voice actors will only be added rather than replace the current one, still kind of stands because reissues will add the archival voice actor for one game, only to remove it when a new game comes out. Additionally, if compilations only contain voices from retired voice actors, this will stack it up even more (although for 3D All-Stars, it still wouldn't change much due to Peach's Super Mario Galaxy voice actress still being her current one). Still, this does make the infoboxes consistent.
  2. Tails777 (talk) I agree with this one more; it's best to keep it up to date when it comes to VAs, but it isn't uncommon for various games to recycle voice clips (TTYD once again being a good example). I feel it is best to at least acknowledge if voice clips get recycled in this respect, though I also feel this should be limited to one at a time, in case there are examples where someone had more than even two voice actors.
  3. FanOfYoshi (talk) Per all.

Do nothing

Comments

I'm conflicted between simply listing only whoever is currently voicing the character vs. potentially opening a can of worms by listing multiple actors from archival clips, even though that would respect the portrayals from the most recent game whether it used newly recorded or archived voices. No matter how this proposal ends up, I think that a future proposal should consider standardizing the "Portrayals" header in the character articles themselves. For Mario, the list of portrayals does a great job at comprehensively documenting everyone who has officially voiced Mario, but falters in conveying the inconceivable magnitude of media in which Martinet has voiced Mario, and how much he has contributed to the character's brand recognition to the point where many people will continue to see him as the voice of Mario, even moving forward as Kevin Afghani takes on that role. ThePowerPlayer Slug.png ThePowerPlayer 23:57, September 16, 2024 (EDT)

Miscellaneous

None at the moment.