MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
 
Line 1: Line 1:
<table style="background:#fefffe;color:black;-moz-border-radius:8px;border:2px solid black;padding:4px" width=100%><tr><td>
{{/Header}}
<div class="proposal">
<center>http://img33.picoodle.com/img/img33/9/9/17/f_propcopym_9045f2d.png</center>
<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>. '''Signing with the signature code <nowiki>~~~(~)</nowiki> is not allowed''' due to technical issues.


<h2 style="color:black">How To</h2>
==Writing guidelines==
#Actions that users feel are appropriate to have community approval first can be added by anyone, but they must have a strong argument.
''None at the moment.''
#Users then vote and discuss on the issue during that week. The "deadline" for the proposal is one week from posting at:
##Monday to Thursday: 17:00 (5pm)
##Friday and Saturday: 20:00 (8pm)
##Sunday: 15:00 (3pm)
#Every vote should have a reason accompanying it.
#At any time a vote may be rejected if at least '''three''' active users believe the vote truly has no merit or was cast in bad faith. However, there must be strong reasons supporting the invalidation.
#"<nowiki>#&nbsp;</nowiki>" should be added under the last vote of each support/oppose section to show another blank line.
#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 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.


The times are in EDT, and are set so that the user is more likely to be online at those times (after school, weekend nights).
==New features==
 
''None at the moment.''
So for example, if a proposal is added on Saturday night at 11:59 PM EDT, the deadline is the next Saturday night at 8:00 PM. If it is indeed a minute later, the deadline is a day plus 15 hours (Sunday), as opposed to a day minus 4 hours.
 
Also,
<br><span style="font-family:sans-serif;font-size:30px;line-height:30px;font-weight:900;">NO PROPOSALS ABOUT HAVING BANJO AND CONKER ARTICLES</span> -The Management.
 
__TOC__
 
<center><span style="font-size:200%">CURRENTLY: '''{{LOCALTIME}}, {{LOCALDAY}} {{LOCALMONTHNAME}} {{LOCALYEAR}} (EDT)'''</span></center>
 
==New Features==
''None at the moment.


==Removals==
==Removals==
''None at the moment.
''None at the moment.''


==Splits & Merges==
==Changes==
===Repeated Info, Pointless Pages?===
===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]].


If you look at the [[Final Smash]] page, you'll see that each one is listed in a table, along with a fairly large amount of info about it. Each one has a link to the page that is specifically about that particular Final Smash (e.g. the Aura Storm has its own page, etc). I've read these individual separate pages, and their info is practically the same as what it says on the main Final Smash page. So, are these small pages kind of pointless? In fact, some of the descriptions on the FS page are more detailed than on the page they link to, as they contain info about damage percentages and stuff.
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}}


I think either one of these options should be considered: We either remove all the individual FS pages (as in [[End of Day]], [[Mario Finale]], etc) and make the info in the table of Final Smash page more detailed...
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.


OR we only include very small amounts of info on the main Final Smash page, so that it's actually worth having the linked pages.
'''Proposer''': {{User|GuntherBayBeee}}<br>
 
'''Deadline''': September 19, 2024, 23:59 GMT
'''Proposer''': [[User:Dom|Dom]]
 
'''Deadline''': July 13, 2008, 15:00


====Support====
====Support====
#{{User|Dom}} - I'm thinking my second option is the better one, after reading Pokemon DP's comment. In other words, I'm kind of supporting myself.
#{{User|GuntherBayBeee}} Per proposal.
#{{User|Freekhenstra}} - See my comment
#[[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) - Kept forgetting to do this during my ongoing sports project.
#{{User|MegaMario9910}} - Per Dom and Freekhenstra
#{{User|Pikax}} - Per Freekhenstra
#{{User|Tucayo}} - I support the idea of erasing the individula pages, it's better to have them in a unique, more complete page
#{{User|Glitchman}} - See my comment below.
#{{User|ItameMarioFan}} - Yes. The pages have the same description as on the [[Final Smash]] page. Only thing new is the throphies. Per Dom and Glitchman (comment below).
#{{user|Luigi001}} Per Dom and Pokemon DP. Expanding the individual pages would make much more sense than getting rid of them all.
#{{User|Walkazo}} - I guess something's better than nothing.
#{{user|Toadette 4evur}} Per DP.
#{{user|Yowuza}} Yeah, this isn't the SmashWiki, this is the Super Mario Wiki.
#{{user|Sonic64}} Per DP
#{{User:Luigi3000/sig}}Per 4Evar


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


====Comments====
====Comments====
If the moves have articles, Final Smashes should have them too. The Final Smash article has too many details, Aura Storm for example. It can be shortened to just: "Lucario jumps high above the stage, then fires a beam of Aura, that the player can guide across the stage to devastate his opponents". The Final Smash article should have descriptions like that, while the article of the Final Smash itself could have the details. {{User|Freekhenstra}}
:That sounds good in theory, but I'm going to respectfully disagree. While the idea of getting rid of information on the main page to make all of the pages incomplete would definitely lead to more proposals down the road, I do agree that we should get rid of all the off-shoot pages and have all of the final smashes on one big, complete page. Each of the final smashes would just have to redirect to that page. {{User|Glitchman}}
Uhh, I don't get what the proposal is saying, what are we supporting? I'm confused. {{User|Toadette 4evur}}
:Same, it's not really clear whether we're deleting the list or the articles, as it is now, "Support" is just saying we do ''something''. Anyway, I support Glitchman's idea, for all the reasons listed above as well as the fact that the Final Smash articles could be turned into redirects, wheras the list would be harder to deal with. However, if memory serves, a similar proposal was shot down a couple months/weeks ago, on the basis of Freekhanstr'a point that moves have articles too, and they're more minor than FSs. I say the moves ''and'' the Final Smashes should be nixed, though sadly I don't think that will fly. - {{User|Walkazo}}
I actually have to say, asking for all the respective pages to be deleted was the dumbest thing I ever heard. If we do that, we might as well delete all the special move articles, which would be of less importance than the Final Smashes. Regardless, I agree that the information on the Final Smash article is overboard. But do not touch the individual articles; ONLY the Final Smash article. {{User|Pokemon DP}}
'''Note to Toadette 4evur:''' I guess the support means that you agree that some information should be moved/merged to or from the main FS page and the individual pages. That sounds a bit vague, I know. {{User|Dom}}
'''Note to Pokemon DP:''' I hope you weren't calling ''me'' dumb...  I'll admit it would be a bit harsh to delete all those articles, but that's why I mentioned 2 options. And I'm leaning towards the second one, the one you agreed was more appropriate.  {{User|Dom}}
But even considering to delete those articles as an option wasn't very wise... Well, whatever. I'm still all for shortening the (supposedly) brief descriptions on the Final Smash article. {{User|Pokemon DP}}
:What option do you vote for when supporting? I am for individual articles and less information on the Final Smash page. - {{User|Cobold}} 10:41, 7 July 2008 (EDT)
'''Note to Cobold:''' - Since my comments to 2 other users, I guess I've kind of confirmed that the Support means what you agreed to - less info on Final Smash page. {{User|Dom}}
===Paper Luigi===
It is pretty hard to find all of the data from luigi's quest from The thousand year door, on this wiki. So I propose that we merge all the articles that have to do with luigi's quest in the waffle kingdom, into one single article. that way, if someone needs to look it up, they can easily find it.
(I know that this is a pretty short proposal)
'''Proposer''': [[User:Dryest bowser|Dryest bowser]]
'''Deadline''': July 17, 2008, 17:00
====Support====
#[[User:Dryest bowser|Dryest bowser]]- per myself
====Oppose====
#{{User|Walkazo}} - See below.
====Comments====
I don't get this Proposal at all. {{User|Pokemon DP}}
Neither do I. I dont think weshould do it cus it is fine as is.{{User|Luigi3000}}
{{User|Dryest bowser}} I just want to make a single article for luigi's story in paper mario the thousand year door. it will make the wiki more organized. and we can stop having extremly short articless for all of the ccharacters and places
:As in [[Super Luigi Series|this]]? If not, kindly provide a link to the pages you '''are''' talking about. - {{User|Walkazo}}
{{User|Dryest bowser}} I mean articles like [[jerry]],[[Hizza]] and [[torque]]. these articles are kind of minor,and It would be easier to merge them
:They're characters, and all characters get their own articles unless they're carbon copies of each other like the [[Board (Super Mario Galaxy)|Board]]s, or if they're always found together and do nothing significant individually, like [[Ashley and Red]] and [[Kat and Ana]]. The only one you can argue over is Hizza, since his article's a stub; and because he wasn't encountered by the player, meaning he could be considered an implied character and can therefore be relegated to the [[List of Implied Characters]], or converted into a redirect to [[Plumpbelly Village]]. However, neither of those options is what you want for this proposal; what you're asking just isn't feasible, sorry. - {{User|Walkazo}}
==Changes==
===Fire and Ice Templates===
As I said on the [[Template_talk:Fire|Fire talk page]], too many things use fire (or ice) for these templates to be practical. Instead, I propose we alter these templates so that they only include things made of, or irrefutably linked to fire/ice. This is a better design because readers could then research creatures of fire or ice with as much ease as if they were using the [[Template:Birds|Bird]] or [[Template:Fish|Fish]] Templates to research those kinds of beings, instead of getting bogged down with species that only use fire or ice. For example, if someone wants to research Birds, anything else in the Bird Template that flies but isn't a bird would slow them down; however a misfile like this would be obvious as a bird is a clearly defined animal, while what can be considered appropriately placed under "Fire" and "Ice" is much more subjective. As such, I'm open to suggestions on what should or shouldn't be removed, my first attempt (complete with justifications for my choices) can be seen alongside the original templates [[User:Walkazo/Templates|here]]; as are newer split-template versions of Fire and Ice suggested by [[User:Soler|Soler]] below, which are now the designs I plan to put into effect if this proposal passes.
'''Proposer''':[[User:Walkazo|Walkazo]]
'''Deadline''': July 9, 2008, 17:00
====Support====
#{{User|Walkazo}} - My reasons above.
#{{User|Pikax}} - I have seen what Walkazo plans to separate from the templates and why she wants to separate those things, and I have no objections to her plan.
#{{User|Dryest bowser}}-per all
#{{User|The Writing Guy}} - Per Walkazo.
#{{user|ParaBob-omb}}- Per all.
#{{User|Dom}} - Per the above users who are crushing my writing here with their heavy words. I say Soler's comment below which includes his 2 split templates is a perfect solution, that should be used instead of what currently exists.
#{{User|MegaMario9910}} - Per Walkazo and Soler's comment.
#{{User|Mrsdaisyluigi}} - Per all
# {{User|Tucayo}} - Per Walkazo. They should be separated, its OK for characters like [[bowser]] to be removed, because the fact they spit fire doesnt make him a fire creature.
# {{User|Stooben Rooben}} - Per Walkazo, the Proposal-Genius. 23:18, 4 July 2008 (EDT)
#{{User|Soler}}: per all.
#{{User|Pokemon DP}} Per Walkazo.
====Oppose====
====Comments====
How about something like this for the Fire template, and something similar for the Ice? I tried to simulate Walkazo's formatting as best as I could: feel free to fix the formatting. I feel that this would serve both people with Walkazo's view of the term and those with a broader view of it. If the show/hide feature is unnecessary, please remove it. Another option would be to split the templates in two. —{{User|Soler}}. (I am going on holidays on Sunday, so please excuse me if I do not reply to your unrelenting criticism...)   
{| align="center" width=100% class="toccolours" cellspacing="0" cellpadding="2"
|-
| align=center bgcolor=orange style="border: 1px solid white"|<div style="background:#orange; text-align=center;">'''Fire Creatures'''<showhide><small>__HIDER__</small><hide><div>
{| width=100%
| align="center" style="font-size: smaller; background:ghostwhite" | [[Angry Sun]] | [[Blargg]] | [[Bomb (species)|Bomb]] | [[Burn Bit]] | [[Czar Dragon]] | [[Ember]] | [[Fiery Bubble]] | [[Fire Chomp]] | [[Fire Elemental Ghost]] | [[Fire Snake]] | [[Fireball (enemy)|Fireball]] | [[Fryguy]] | [[Fryguy (species)|Fryguys]] | [[Helio]] | [[Hot Foot]] | [[Hot Lips]] | [[Hothead]] | [[Kleever]] | [[Lava Bubble]] | [[Lava Bud]] | [[Lava Drop]] | [[Lava Ghost]] | [[Lava Piranha]] | [[Li'l Sparky]] | [[Mini Fryguy]] | [[Petit Piranha]] | [[Phantom Ember]] | [[Podoboo]] | [[Pyro Guy]] | [[Pyrosphere]] | [[Sparky]] | [[Sun (character)|Sun]] | [[Torcher]] | [[Trouble Bug]]
|}</div></hide></showhide></div>
|-
| align=center bgcolor=orange style="border: 1px solid white"|<div style="background:orange; text-align=center; color:black">'''Fire-Related Creatures'''<showhide><small>__HIDER__</small><hide><div>
{|
| align="center" style="font-size: smaller; background:ghostwhite" | [[Baby Bowser]] | [[Birdo]] | [[Bowser]] | [[Bowser Jr.]] | [[Calm Volcano Plant]] | [[Dhalsim]] | [[Dino-Torch]] | [[Fire Bro.]] | [[Flare]] | [[Gao]] | [[Iggy Koopa]] | [[Jumping Piranha Plant]] | [[King Totomesu]] | [[Lava Lotus]] | [[Ludwig von Koopa]] | [[Sumo Bro.]] |  [[Tryclyde]] | [[Venus Fire Trap]] | [[Vivian]] | [[Volcano Lotus]] | [[Zeus Guy (Bandit)]] | [[Zeus Guy (Snifit)]]
|}</div></hide></showhide></div>
|}
{{User|Dom}} - Hey, the User called ''Soler'' made these templates about fire! Get it? Solar...fire? Ha ha...........???
On a serious note: Soler's split templates are a brilliant idea, better than the all-in-one oversized template.
:Yeah, I definately like that idea, too!  Awesome work, Soler! {{User|Stumpers}}
::Oh, thanks! Does anyone think that two Ice and two Fire templates would be better than the above idea of a "double template"? (I myself think that the double one would be easier for navigation.) —{{User|Soler}}.
:::I prefer the double one, and I've taken your example and refined new split-templates for both Fire and Ice which I've put up [[User:Walkazo/Templates|here]] with the earlier versions. As I said in the added last line of the Proposal, I'd rather go with them than my earler attempts. Nice going! - {{User|Walkazo}}


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

Latest revision as of 18:34, September 12, 2024

Image used as a banner for the Proposals page

Current time:
Friday, September 13th, 05:54 GMT

Proposals can be new features (such as an extension), 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 13, 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

Unimplemented proposals

Proposals

Split Mario Kart Tour character variants into list articles, Tails777 (ended May 4, 2022)
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)
Remove excessive Pokémon lists and images, Super Mario RPG (ended August 28, 2024)
^ NOTE: Proposal is requesting image deletions, which require admins
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)
Characters with multiple galleries should have them divided by decade, not medium, Nintendo101 (ended September 8, 2024)
^ NOTE: still needs to be applied to Luigi, Bowser, Waluigi, and Donkey Kong
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

None at the moment.

New features

None at the moment.

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.

Oppose

Comments

Miscellaneous

None at the moment.