MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
Line 131: Line 131:
#{{User|Sdman213}} Per all.
#{{User|Sdman213}} Per all.
#{{User|KoolKoopa}} By that logic non-Mario Mario Kart courses would also be merged which doesn't make a lot of sense.
#{{User|KoolKoopa}} By that logic non-Mario Mario Kart courses would also be merged which doesn't make a lot of sense.
#{{User|Mustard Machine}} Per all.


====Comments====
====Comments====

Revision as of 01:51, October 22, 2022

Image used as a banner for the Proposals page
Current time:
Wednesday, May 8th, 12:55 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 on proposals with more than two choices.
  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 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. 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 the total number of voters must appear in a single voting option, rather than one option simply having more votes than the other options.
  10. If a proposal with only two voting options has more than ten votes, it can only pass or fail by a margin of three votes, otherwise the deadline will be extended for another week as if no majority was reached at all.
  11. 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.
  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 deleted 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 deleted 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: "May 8, 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

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 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 {{TPPDiscuss}}. 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 {{SettledTPP}}.
  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 article 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

Merge the Wrecking Crew and VS. Wrecking Crew phases into list articles, Axis (ended February 24, 2022)
Do not consider usage of classic recurring themes as references to the game of origin, Swallow (ended March 9, 2022)
Split Mario Kart Tour character variants into list articles, Tails777 (ended May 4, 2022)
Enforce WCAG Level AA standards to mainspace and template content, PanchamBro (ended May 29, 2022)
Change how RPG enemy infoboxes classify role, Doc von Schmeltwick (ended September 18, 2022)
Trim away detailed special move information for all non-Mario fighters, Koopa con Carne (ended January 30, 2023)
Classify the Just Dance series as a guest appearance, Spectrogram (ended April 27, 2023)
Establish a standard for long course listings in articles for characters/enemies/items/etc., Koopa con Carne (ended June 8, 2023)
Consider filenames as sources and create redirects, Axis (ended August 24, 2023)
Add tabbers to race/battle course articles, GuntherBB (ended November 18, 2023)
Remove elemental creatures categories from various Super Mario RPG enemies, Swallow (ended January 11, 2024)
Standardize the formatting of foreign and explanatory words and phrases in "Names in other languages" tables, Annalisa10 (ended February 7, 2024)
Merge Super Mario Bros. (film) subjects with their game counterparts, JanMisali (ended April 18, 2024)
Remove profiles and certain other content related to the Super Mario Bros. Encyclopedia from the wiki, Koopa con Carne (ended April 30, 2024)
Create The Cutting Room Floor link template, Bro Hammer (ended May 7, 2024)

Talk page proposals

Split all the clothing, Doc von Schmeltwick (ended September 12, 2021)
Split the various reissues of Mario Bros., Doc von Schmeltwick (ended April 22, 2022)
Split machine parts, Robo-Rabbit, and flag from Super Duel Mode, Doc von Schmeltwick (ended September 30, 2022)
Expand source priority exception to include regional English differences, LinkTheLefty (ended January 14, 2023)
Add product IDs in game infoboxes, Windy (ended March 18, 2023)
Remove the list of Super Smash Bros. series objects, Axis (ended May 10, 2023)
Merge Start Dash with Rocket Start, Koopa con Carne (ended August 17, 2023)
Use italics for the full title of the Mario Kart 8 Deluxe – Booster Course Pass, Hewer (ended September 15, 2023)
Split Special Shot into separate articles by game, Technetium (ended September 30, 2023)
Convert the lists of episode appearances for television series characters into categories, Camwoodstock (ended November 22, 2023)
Decide which series certain Yoshi games are related to, GuntherBB (ended December 14, 2023)
Change the Super Mario 64 DS level section to include more specific character requirements, Altendo (ended December 20, 2023)
Replace "List of Game Over screens" and "'Game Over' as death" sections with a "History" section, DrippingYellow (ended December 20, 2023)
Split the Jungle Buddies from Animal Friends, DrippingYellow (ended December 22, 2023)
Make major changes to the MarioWiki:Links page, PnnyCrygr (ended January 10, 2024)
Make bestiary list pages for the Minion Quest and Bowser Jr.'s Journey modes, Doc von Schmeltwick (ended January 11, 2024)
Merge the "Johnson" running gag into one page, Doc von Schmeltwick (ended January 11, 2024)
Merge the ghost Bats and Mice from Luigi's Mansion to their respective organic counterparts from the later games, Doc von Schmeltwick (ended January 20, 2024)
Split Strobomb from Robomb, Doc von Schmeltwick (ended January 20, 2024)
Split the NES and SNES releases of Wario's Woods, SONIC123CDMANIA+&K(B&ATSA) (ended March 27, 2024)
Merge Mii Brawler, Mii Swordfighter, and Mii Gunner to Mii, TheUndescribableGhost (ended March 28, 2024)
Merge Masterpieces to the Super Smash Bros. Brawl and Super Smash Bros. for Wii U articles, Camwoodstock (ended March 31, 2024)
Split Mario's Time Machine (Nintendo Entertainment System), or the Super Nintendo Entertainment version along with both console versions of Mario is Missing!, LinkTheLefty (ended April 11, 2024)
Rename Beanstalk to Vine, DrippingYellow (ended April 11, 2024)
Remove non-Super Mario content from Super Smash Bros. series challenges articles, BMfan08 (ended May 3, 2024)
Merge Stompybot 3000 with Colonel Pluck, DrippingYellow (ended May 4, 2024)
Merge Party Ball (item) with Party Ball, GuntherBayBee (ended May 5, 2024)

Writing guidelines

Standardize citations for archived pages

Many web pages that are used as citations on the Mario Wiki are no longer available at their original links. Consequently, the citations use links from web page archival sites such as archive.today or the Wayback Machine. This can be seen on articles that reference the English translation of the Mario Portal, such as Banzai Bill, as well as other articles, such as Nintendo GameCube. Including archived citations is especially important for web pages that are volatile by design, such as online store listings for merchandise. However, nowhere does MarioWiki:Citations feature a template for how to properly cite archived web pages; therefore, an example of a citation for an archived page should be created under the heading What to put as references.

EDIT: Per Koopa con Carne's comments, I've revised my recommendations for a standardized template below.

The current basic template for citations of non-archived pages looks like this:

Author Name (January 1, 2000). Link to Page on Live Web. Publisher. Retrieved January 1, 2022.

In order to make citations of archived pages as simple as possible, they should only link to the archived page, followed by the date and timestamp (if available) of the archived page, along with the name of the archival website:

Author Name (January 1, 2000). Link to Archived Page. Publisher. Archived January 1, 2000, 09:00:00 UTC via Archival Website. Retrieved January 1, 2022.

This is what an actual citation would look like under this standard, using one of the references on the Nintendo GameCube article as an example:

Satterfield, Shane (August 25, 2000). Nintendo's GameCube Unveiled. GameSpot. Archived September 5, 2015 via Wayback Machine. Retrieved July 15, 2022.

Here's another example, using the citation of the Mario Portal on the Banzai Bill article (because this specific page does not have an author nor a release date attributed to it, these details are omitted from the citation):

Super Mario World | Game Archives | Mario Portal | Nintendo. Nintendo. Archived August 13, 2022 14:17:58 UTC via archive.today. Retrieved August 13, 2022.

As a clarification, this proposal does not mean to mandate that every citation of a web page should include an archived link; that should be left to editor consideration. However, in cases where archived links are necessary, such as volatile links or links that are already dead, a standard method of citation would be useful to implement.

Proposer: ThePowerPlayer (talk)
Deadline: October 24, 2022, 23:59 GMT

Support

  1. ThePowerPlayer (talk) Per proposal.
  2. Hewer (talk) I think I'd rather have it link to both the archive and the original, but I can see why that might not be ideal and this is still better than nothing so per proposal.
  3. Killer Moth (talk) Per proposal.
  4. RHG1951 (talk) Per proposal.

Oppose

  1. Koopa con Carne (talk) I agreed with making it a formal encouragement to treat archive links as supplementary to authentic links, thereby easing the process of swapping them when the latter are discontinued. However, I don't see a use for replacing perfectly fine, working links with archived counterparts, much less so extending that to policy. Generally speaking, archived snapshots load slowly and can be a fuss to instate in the first place; making their use obligatory and exclusive, on top of what I just said, might discourage editors from actually sourcing their information. Besides, ignoring this aspect, all in all this reads to me like trying to make an amendment for an issue that doesn't exist.

Comments

Can you articulate some specifics for this standard? Namely, would it suffice to include the link to a snapshot, or would editors be requested to also add the time, date, and name of the archivation website of that particular snapshot? You are putting forward the Banzai Bill citation as a template and, though I agree on encouraging comprehensive fact-checking and easy readability/access (as the user who basically pushed for this whole format across the wiki over the past years), I reckon some editors may not like being forced by policy to tick so many boxes when structuring their links. -- KOOPA CON CARNE 00:50, October 10, 2022 (EDT)

I've edited the description of my proposal to reflect your criticisms. If there's anything else I was unclear about, please let me know. ThePowerPlayer Slug.png ThePowerPlayer 11:57, October 10, 2022 (EDT)
I wouldn't disallow snapshot timestamps. I recognise that the presence of such info creates an inconsistency with the way the original link's access date is formatted, but one could argue the timestamp is a defining, unique attribute of the snapshot. I.E., a snapshot taken at 09:00:00 UTC on January 1, 2000 is stored separately from another snapshot taken 17:00:00 UTC on the same day, and (on Wayback Machine at least) there's a set waiting period before a new snapshot can be created, so there exist no two simultaneous snapshots of a given web page. Another proviso in your proposal I would like to address regards the way broken links are handled: it's fairly counterintuitive to put forth a link that doesn't work and treat the working archive link as secondary; the way I've gone with this has been to treat the archive links as any other regular link, complete with its original website's name and access date, and sandwich the archival details in-between the former two, like so:

Snapshot. website. Archived January 1, 2000, 09:00:00 UTC via Mayback Wachine. Retrieved January 1, 2022.

An additional practice I've seen on Wikipedia is to also append the original link as an accessory, as "Archived January 1, 2000, 09:00:00 UTC from the original via Wayback Machine", which I suppose makes documentation more thorough--if a bit overly so, which is why I suspect some editors may find fault in this addition. -- KOOPA CON CARNE 20:30, October 10, 2022 (EDT)
I've made more revisions to the template I recommended for citing archived links. I elected to simply include only the archived link within the citation, both because the original link is always available on any credible archived page, and for simplicity's sake so editors don't find it too tedious to implement said template. ThePowerPlayer Slug.png ThePowerPlayer 23:35, October 10, 2022 (EDT)

So, is the proposal now championing the prohibition of first-hand links in favour of archived links, or just a guideline recommendation for using the latter? The last statement of the proposal is in direct contradiction with the rest: "As a clarification, this proposal does not mean to mandate that every citation of a web page should include an archived link; that should be left to editor consideration." -- KOOPA CON CARNE 18:04, October 11, 2022 (EDT)

For additional clarification to that final sentence in particular, users should decide on their own whether to use an archived link in their citation (especially for pages that are volatile or already dead on the live web), or if using a regular link would be sufficient (this applies to most pages). However, if the user decides that an archived link would be appropriate, the standardized template described above should be used. There should be a template for citing archived links in addition to the existing template for citing regular links; that was the goal of this proposal in the first place. There will always be outliers and exceptions (for example, the reference on Il Piantissimo's article would be difficult to fit into a standard template), but having these guidelines is good practice because it sets the standard for credible and accessible citations. ThePowerPlayer Slug.png ThePowerPlayer 21:33, October 11, 2022 (EDT)

New features

None at the moment.

Removals

Remove external links to Zelda Dungeon Wiki and/or Triforce Wiki

Early this year, a proposal was passed to add external links to Zelda Dungeon Wiki and Triforce Wiki by 10-0; the intent was to add two links to two independently hosted wikis as Zelda Wiki at the time was hosted on Fandom.

Fortunately for us, this is no longer the case. Zeldapedia is now independently hosted and doing well. I think while Zelda Dungeon Wiki and Triforce Wiki have served their purpose and are great resources for Zelda content, it would be embarassing (as a NIWA wiki) to continue using these wikis when it was originally intended to supplement a Fandom wiki that has since forked its content to become independently hosted once again.

Edit: After giving some thoughts, I've decided to allow users to either remove ZD Wiki or Triforce Wiki or remove them both.

Proposer: PanchamBro (talk)
Deadline: October 27, 2022, 23:59 GMT

Remove both

  1. PanchamBro (talk) Per my reasons.

Remove only Triforce Wiki

Remove only Zelda Dungeon Wiki

Do nothing

  1. Doc von Schmeltwick (talk) - Disregarding my personal ties to Triforce Wiki, I'd actually support (and even prefer) allowing more specifically approved outside-NIWA indy wikis of Nintendo subjects to be included, if only for variety's sake. (Also, I am very happy for ZeldaWiki!)
  2. LinkTheLefty (talk) Agreed. Disregarding the biases involved with Triforce Wiki's approach being modeled after this wiki's, I think it's more in our interest to keep the line drawn at non-NIWA wikis that cross into Mario franchise coverage. I might be misremembering, but wasn't there a time when the Sonic News Network links were in question due to the Sonic Retro wiki, but it was decided to keep both because while the former isn't independent, it's more mature as a wiki? For our purposes, the relevant content is mature enough. Cutting off options does a disservice to readers.

#Wikiboy10 (talk) - per Doc

Comments

Here's the thing, I'm more in favor of just removing Triforce Wiki. Zelda Dungeon Wiki, I feel, should still be kept for the reasons Doc has said. However, I'm more in favor of removing Triforce Wiki because the owner has had disturbing history on many NIWA wikis. Wikiboy10 (talk) 09:53, October 20, 2022 (EDT)

I tried my best to not mention it, but yeah the history of Triforce Wiki had been concerning for many. If people want to keep ZD Wiki and remove Triforce Wiki, I'd be happy to add it as an option. -- PanchamBro (talk • contributions) 10:03, October 20, 2022 (EDT)
I'm going to let Doc touch on this since I don't know as much - being that I had never been in Discord - but know the bottom line is that the founder is no longer actively involved and I disbelieve that one's personal actions taints a whole. LinkTheLefty (talk) 10:25, October 20, 2022 (EDT)
Um... TriForce Wiki was always my little pet project. RMV even said as much himself. Technically the domain is now hosted by grifkuba, I've banned RMV for his - quite frankly dangerous - behavior, and I am the de facto proprietor now - I've just been inactive due to being busy on this site. Doc von Schmeltwick (talk) 12:34, October 20, 2022 (EDT)

Disregarding the problematic history with Triforce Wiki (and thank god he's no longer involved), I have some issues with your argument @LinkTheLefty.

"I think it's more in our interest to keep the line drawn at non-NIWA wikis that cross into Mario franchise coverage. [...] Cutting off options does a disservice to readers."

I'm not sure if this is a great argument. We already have issues with Smash coverage here, and at the moment they aren't linking to any other Smash wiki than SmashWiki. I might be getting into slippery slope territory by saying this, but I don't want an instance where we decide that if we provide enough coverage to a franchise, we should link to every wiki that covers that franchise. Relatively speaking, I don't want this wiki to start linking to https://animalcrossing.fandom.com (which is unlikely, but still). I don't think Zeldapedia minds about linking to other Zelda wikis, but I don't want this to set a precedent that quite frankly should be avoided. -- PanchamBro (talk • contributions) 11:08, October 20, 2022 (EDT)

I was going to mention Smash before, but I thought that example was already implicitly inapplicable given the franchise's special scope in wiki coverage (for the time being or not), so I didn't bother. Your Fandom example isn't applicable either, per this proposal. Furthermore - and I'm aware this wasn't your intention when you made this but I want this to be clear - associating Triforce Wiki with one person/incident it has largely moved away from is REALLY unfair to Doc, who has been open about it being a pet project of hers and earned the title of current proprietor of the wiki, which is now hosted by Grifkuba among other NIWA wikis. That's all I really want to say about this matter. LinkTheLefty (talk) 11:54, October 20, 2022 (EDT)

Changes

Merge all non-Mario universe Super Smash Bros. Stages into a collective article

Throughout the past few months the wiki has been trimming down on Super Smash Bros. content. Mutliple propsoals have now been passed supporting the trimming of Smash content including propsoals merging items, deleting general technqiues and most recently the merging of bosses. Up until I recently beleived that Smash should receive full coverage on this wiki becuause of the high level of represention Mario and its sub-franchies recive in these games. However the recent trimming of content combined with the existence of Smash Wiki I have changed my mind on this. The next step that should be taken in trimming smash content is would be to merge the stages into one collective artcile.

This is probably the most radical proposal in the trimming of Smash content so far giving the stages are a big part of the Super Smash Bros. franchise. However if we are no longer going to have seperate artciles for Items and Bosses then I think it now has to be questioned to wherever or not non-Mario stages should be also still have seperate pages given this the Mario Wiki that they based on locations that have nothing or very little to do with the Mario franchise and that seperste artciles of these stages exist on Smash Wiki.

Given that this the Mario Wiki that all stages based locations from the Mario and the sub-franchises should keep their artciles. By keeping them split it will emphasis that this the Mario Wiki by given increased focus on elements from Smash that are based on Mario. Therefore should this propsoal pass stages from these franchises which are covered by this wiki remain split:

  • Mario
  • Donkey Kong
  • Yoshi
  • Wario

One series where I think there is question mark to wherever they should be split or merged are Smash oringal stages, ie Battlefield and Final Destination. I would be also keep these with their own articles as these stages have the most hertiage of all Smash stages in the series and that they are not specfially based on a non-Mario franchise. I will therefore provide two options for merging one that sees the Smash oringnal stages remain split and the one that sees them merged.

As for all the other franchises inclduing not listed above they would all be merged into an idvidual artcile with the page names being replaced by redirects and include external links to Smash Wiki. Futhermore the infoboxes for the non-mario stages are removed and the text body should be limited to one paragrah per stage.

I'm very much aware that if this proposal passes it would be a very signifcant change for the wiki. But I beleive now given the trimming of smash content that has been taking place it is one that I beleive should hapoen. (Amendments made to proposal in comments below)

Proposer: NSY (talk)
Deadline: October 8, 2022, 23:59 GMT Extended to October 15, 2022, 23:59 GMT Extended until October 22, 2022, 23:59 GMT

Merge all non-Mario universe stages excluding stages orignal to Smash

  1. NSY (talk) Per proposals, first prefrence

Merge all non-Mario universe stages including stages orignal to Smash

  1. NSY (talk) Second prefrence.
  2. Koopa con Carne (talk) I'm in agreement with the proposal, and generally also with the original proposition to have some of the information trimmed, such as the soundtrack listings (although I wouldn't exactly restrict stage entries to only one paragraph, but I digress). The way Super Mario Wiki covers Smash content is an infamously messy attempt at a compromise between the practices of a bygone era of the wiki and its current efforts to curate information. Most of these stages, while not entirely out of the wiki's scope given their presence in a crossover game, have too tenuous a connection to Mario to have dedicated articles; related information is much better conveyed on Smash Wiki, i.e. someone can go there to see Dream Land's track selection if that's a concern. For the record, I would support a similar treatment for fighters that haven't appeared in Mario media.
  3. Spectrogram (talk) After some thought, I think this is also a fine option.
  4. ThePowerPlayer (talk) Per Koopa con Carne. I see little to no reason to keep entire Smash articles with little to no relation to the Mario franchise if said information is documented far more comprehensively on SmashWiki; it just sets a standard of redundant documentation. People aren't visiting the Mario Wiki to learn about Brinstar.
  5. Shiny K-Troopa (talk) Since simply deleting Smash content that is irrelevant to Mario doesn't seem to be an option for this wiki for some reason, this is the best compromise I guess. Per proposal.
  6. Somethingone (talk) I was opposed to merging the bosses before, but now that they are merged, why are we prolonging the inevitable? It makes little sense that things that amount to a backdrop & a floor have more priority than the actual items and bosses and every other mechanic (minus the players) in the series. Per proposal.

Merge only non-Mario adventure mode and subspace emissary stages

  1. 7feetunder (talk) Merging all stages seems like biting off more than we can chew right now, but these in particular aren't really significant enough to warrant separate articles for them.
  2. Spectrogram (talk) Per my reasoning in the comments
  3. TheFlameChomp (talk) I think that the main stages are prominent enough to remain separate, per Waluigi Time’s vote below, but I feel like these stages are less significant and can be merged.
  4. Killer Moth (talk) Per TheFlameChomp. the adventure mode and subspace emissary stages don't need separate pages.
  5. Hewer (talk) Per all, the arguments for stages being too prominent to merge don't really apply to the adventure mode stages.
  6. Tails777 (talk) Per all. I agree to this most.
  7. ThePowerPlayer (talk) Second choice; per all. Even if most non-Mario-related stages won't be merged, I strongly feel that these stages have too little relation to Mario to be split.
  8. Power Flotzo (talk) The main stages are just as essential to Smash as the fighters, so I see no reason to merge them. Per all.
  9. Waluigi Time (talk) Second choice since a full merge seems to be gaining traction suddenly.
  10. PanchamBro (talk) Per all.

Keep all Smash stages split

  1. Waluigi Time (talk) Creating a single page to contain every non-Mario stage in the series history, as this proposal seems to aim to do, is going to be way too messy. I'm also strongly against this specific sentence: "Futhermore the infoboxes for the non-mario stages are removed and the text body should be limited to one paragrah per stage." By doing that, we either lose information while trying to keep it trimmed to an arbitrary maximum (why?) or we have all the information we can talk about regarding each stage clumped into a single paragraph, which isn't nice to read. Take a look at Dream Land (Super Smash Bros.) for example, and try to think of how this would look merged. It's not pretty. Stages are a big enough part of the series gameplay that I think they're fine keeping separate, and frankly, I wasn't really too happy about items being merged either, but at least that was easier to pull off.
  2. Doc von Schmeltwick (talk) - Too much, too far. Engaging pushback mode.
  3. Bazooka Mario (talk) I feel stages are the second to only playable roster in terms of prominence in a Smash Bros. game (I mean we didn't get an "Everything is Here!" for stages 😒) so I feel a lot of other content should be merged first before we consider stages.
  4. LinkTheLefty (talk) I may consider The Subspace Emissary, which is mostly Smash-original content (and the parts that aren't, aren't Mario-related), but Adventure mode mostly consists of normal stages, and one of the nonstandard stages gets utility outside of the mode via Event Match.
  5. RHG1951 (talk) Per all.
  6. Archivist Toadette (talk) Per all. At least, until we can adequately address the issues brought up by other users.
  7. Sdman213 (talk) Per all.
  8. KoolKoopa (talk) By that logic non-Mario Mario Kart courses would also be merged which doesn't make a lot of sense.
  9. Mustard Machine (talk) Per all.

Comments

I'm very conflicted about this. I think non-Mario Subspace Emissary stages such as Battleship Halberd Bridge or The Path to the Ruins need to be merged, but regular stages that shape Smash Bros. into what it is are fine. Not to mention, Battlefield according to the last Smash proposal will be merged with Fighting Polygons and other teams, so that would mean merging a stage that was already just merged. Keeping it unsplit alone would also be seen as weird. Your proposal also does not make an exception for Wrecking Crew (stage). Please add an option to only merge non-Mario Subspace Emissary levels Spectrogram (talk) 13:07, October 1, 2022 (EDT)

I agree with merging Subspace Emissary stages, along with Melee Adventure Mode stages barring Mushroom Kingdom. Dark BonesSig.png 17:23, October 1, 2022 (EDT)

Thanks for all the feedback given on this proposal, I created this proposal because I feel like it should either be all or nothing when consdiering Smash content, either it should be all merged or all split and I felt based off the pervious proposals held that the consenus of smash content leaned towards it being merged. By having items and bosses merged but stages split i feel it is middle of the road but i do understand the points made of stages being more important. It seems very likely that this proposal is not going to pass but i'll going make amendments based of the things said to see if changes any minds. Firstly as per comments from Spectrogram and 7feetunder I've added the extra option to merge non-Mario adventure mode subpace emissary stages. Secondly in regards to infobox removals and trimming of content, i've decided to strike that off from the proposal given ideas clearly sound unpopular. Thirdly in regards to Wrecking Crewe I completly forgot that stage existed and if this proposal were to pass then that would also stay split. Lastly if this proposal passes then maybe rather than one aritcle it be mutliple articles perhaps one per game to avoid it being messey. That being said even despite these ameadments the consenus clearly belevies the stages should remain split and fully see where all of you are coming from the points made but I curious to see what you all think of these amendments. NSY (talk)

@KoolKoopa, no, it doesn't. Smash series is an exception in the coverage policy, which allows such proposals to be made. It wouldn't imply removing content from other crossovers. Spectrogram (talk) 13:58, October 18, 2022 (EDT)

@KoolKoopa "By that logic..." Erm, no? Mario Kart is a pure, distinctly Mario game spin-off with non-Mario stuff in it, and said non-Mario stuff gets covered as a result. Smash is not a pure, distinctly Mario game. It's a 50-ish way crossover with its own unique stuff in it on top of that. Those two situations are Apples to Fruit Punch levels of different.

Decide what Paper Airplane Chase is

Paper Airplane Chase is a DSiWare game that was made based on the minigame Paper Plane (minigame came first). If this game wasn't made based on the WarioWare minigame, the answer to how MarioWiki should cover it would be obvious: a cameo appearance. The characters just appear on the background and serve no gameplay functionality. So the question is, how should Paper Airplane Chase be covered on this wiki?

  • Part of the Mario franchise: Paper Airplane Chase gets considered a full part of the Wario series, since it originated from the WarioWare minigame. This option results in the game receiving full coverage
  • Guest appearance: Not sure how to justify this option. The page remains, no full coverage
  • Cameo appearance: Paper Airplane Chase gets considered nothing more than a cameo appearance, resulting in the article getting removed

Proposer: Spectrogram (talk)
Deadline: October 22, 2022, 23:59 GMT

Mario game

  1. Hewer (talk) It's a direct spin-off of Wario, and I'm pretty sure that makes it count as a game in the franchise by our policy.
  2. Waluigi Time (talk) It's taken directly from WarioWare and still keeps the elements of that series, I don't see why we should do anything else.
  3. TheFlameChomp (talk) I think it makes sense to give the game full coverage if it is based directly off of a WarioWare subject and continues to contain some elements from the series.
  4. Spectrogram (talk) Per all
  5. ThePowerPlayer (talk) Per all.
  6. Killer Moth (talk) Per all.

Guest appearance

Cameo appearance

Comments

Miscellaneous

None at the moment.

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