Please remember that WiKirby contains spoilers, which you read at your own risk! See our general disclaimer for details.

WiKirby:Proposals: Difference between revisions

From WiKirby, your independent source of Kirby knowledge.
Jump to navigationJump to search
 
(681 intermediate revisions by 47 users not shown)
Line 1: Line 1:
<!-- This prevents the Table of Contents from showing up. -->
{{#css: .firstHeading{display:none} }} __NOTOC__{{ProposalRules}}
__NOTOC__
{{ProposalRules}}


='''Current Proposals'''=
='''Current Proposals'''=
=="NIWA wikis" template to replace its notice template equivalents (March 31st, 2021 - April 14th, 2021)==
==Standardized Boss Moves Locations (April 6, 2024 - April 20, 2024)==
{{User:Viperision/Transclusion
Hi! We currently have boss moves put somewhat unevenly around the wiki, with some bosses having their moves recorded on their personal pages ([[King Dedede]], [[Dark Matter Clone]], etc.) and at least one boss I can't track down has them on their stage page. I think these should be standardized, and specifically I think they should go to the boss stage pages. This is because:
|title=This template
# Wiki-assisted players will have the convenience of the information being on the boss page, instead of having to go somewhere else to find the knowledge they need.
|Nookipedia=Template:Other Wikis
# This will put relevant information on boss stage pages, most of which aren't stubs, but still fairly short due to their nature of being mostly just an arena (except such as in ''[[Kirby Star Allies]]'' but it still won't hurt).
|NWiki=Template:Otherwikis
# This will mildly slim down several character pages, only having a major impact for the already lengthy pages of King Dedede and [[Meta Knight]], and it doesn't much impact any other boss.
|SuperMarioWiki=Template:NIWA
Thoughts? ~ [[User:Waddlez3121|by Waddlez!]] 23:02, 6 April 2024 (UTC)
|XenoSeries=1
===Option 1: move to stage page===
}}
# My only preferred choice. ~ [[User:Waddlez3121|by Waddlez!]] 23:02, 6 April 2024 (UTC)
<pre>
#Second choice. I can see the merit in having the info on the stage page, although ultimately we're not a strategy guide. Also any standardization is better than none. {{User:Pinkyoshifan/sig}} 23:44, 6 April 2024 (UTC)
{{User:Viperision/Transclusion
|title=This template
|Nookipedia=Template:Other Wikis
|NWiki=Template:Otherwikis
|SuperMarioWiki=Template:NIWA
|XenoSeries=1
}}</pre>
There was this template in my backlog of ideas, and it came up to viably replace [[Template:SmashWiki]], [[Template:MarioWiki]], [[Template:MetroidWiki]] and [[Template:NWiki]] in order to condense the space multiple such interwiki links take, as well as to distinguish them from maintenance-related [[:Category:Notice templates|notice templates]].


Current templates look okay (or even better) on smaller (mobile) resolutions, but I think they are sometimes obnoxious with their yellow tone and take too much space when used, especially in sections. This alternative would work well in "External links" sections, although [[Meta Knight#Super Smash Bros. series|there are examples]] where it could be less wieldy to use.
===Option 2: move to boss's character/other page===
#First choice. It's the moveset for the character, so it should go on their page. {{User:Pinkyoshifan/sig}} 23:44, 6 April 2024 (UTC)
#Primary (and only) choice. Not just because the attack tables would be better off for the character but also because of a potential problem regarding bosses exclusive to circumstances like The Ultimate Choice. More details in the Discussion section. &ndash; [[User:Owencrazyboy17|Owencrazyboy17]] ([[User talk:Owencrazyboy17|talk]]) 23:55, 6 April 2024 (UTC)
#Single choice here. As stated, this ''is'' the boss character we're talking about, so it wouldn't make as much sense to put the move-set where the boss appears when the boss has its own page.--[[User:Paistrie|Paistrie]] ([[User talk:Paistrie|talk]]) 16:00, 10 April 2024 (UTC)
#It makes far more sense to me to list all the moves on one page given that boss moves tend to evolve over time. We could easily use an <nowiki>{{main}}</nowiki> on stage pages to link to the move listing page wherever that is. {{User:Basic Person/sig}} 19:36, 11 April 2024 (UTC)
#I think having boss moves on their own makes the most sense for bosses and I think it'd be best to have these instead of putting them on location pages, mostly because it would be awkward for bosses that only appear in [[Arena]] modes. [[User:NVS Pixel|NVS Pixel]] ([[User talk:NVS Pixel|talk]]) 13:14, 12 April 2024 (UTC)
#First option, and this is already what we do. Stage pages don't make sense when Kirby has many bosses exclusive to game modes like arenas, and putting boss details there would make giant pages. A boss page should cover info about a boss, and a stage page info about the stage. {{User:Gigi/sig}} 13:36, 12 April 2024 (UTC)


Note that =1 will link to <code><nowiki>{{FULLPAGENAME}}</nowiki></code>, otherwise to another specified article. —[[User:Viperision|Viperision]] ([[User talk:Viperision|talk]]) 13:48, 31 March 2021 (UTC)
===Option 3: make no changes===
#Second option, although this is essentially the same as option 2, as we already only put boss moves in boss/character pages. For reasoning, same as option 2. {{User:Gigi/sig}} 13:36, 12 April 2024 (UTC)


{{Support}}
===Discussion===
#The pink not looking like the improvement templates (and more Kirby-like) and the whole thing being more compact (''especially'' if there are multiple interwiki links) are both great. This also would fix the fact that not every wiki has a template, which while not necessarily a problem, doesn't hurt for consistency's sake. {{User:Pinkyoshifan/sig}} 23:01, 1 April 2021 (UTC)
I thought of a bit of a major issue when it comes to option 1. Say, for example, a boss was fought exclusively in The True Arena or another location or mode with no defined stage count. If option 1 passed with the majority of votes...then how on earth would an attack table for a boss like Chaos Elfilis even work?! Wonder if there's some sort of solution that I'm not seeing... &ndash; [[User:Owencrazyboy17|Owencrazyboy17]] ([[User talk:Owencrazyboy17|talk]]) 23:55, 6 April 2024 (UTC)
<s>#This looks like it'll be a nice improvement. Having the notice templates look like maintenance ones is inconsistent and takes up space, so this will be a better way to handle these interwiki links. {{User:Obsessive Mario Fan/sig}} 20:58, 10 April 2021 (UTC)</s>
:I'd just put it on the Colosseum page under an exclusive boss heading, myself. <s>They wouldn't be the only exclusive boss there...</s> I get why that might not be appealing to some if the page is just intended to describe the mode but I think that's a good solution should option 1 be passed. Alternatively, special cases could be made for them, but that'd ruin the whole standardization idea.
{{Oppose}}
 
{{Neutral}}
:I'm not fond of putting it under character pages because seeing what a boss uses in each fight over a vast number of games really isn't as useful as having info about the boss in the page about where you fight it, in my opinion. ~ [[User:Waddlez3121|by Waddlez!]] 00:04, 7 April 2024 (UTC)
*This seems like a good initiative to cut down on notice space. That said, I do wonder how truly necessary this is, since not a lot of our articles will have/need links to multiple different wikis. Also, I'm wondering if it would be better to format this so it appears on the left side of the page, rather than the right. --[[User:Samwell|Samwell]] ([[User talk:Samwell|talk]]) 15:10, 31 March 2021 (UTC)
 
Like I mentioned on Discord, I am a bit confused on this proposal's existence. As far as I know, where to put boss attacks is already standardized, and that is to say to put it in the character/boss page, which would make option 2 and 3 the same. {{User:Gigi/sig}} 12:44, 10 April 2024 (UTC)
:I can see the merit of moving it to the stage pages, as this would help somewhat with clogged character pages or pages for characters with multiple boss appearances where the moveset just gets listed over and over again (for example, [[King Dedede]], [[Meta Knight]], [[Kracko]]). I find those inconvenient. But I'm not sure if that's the proper solution to the problem, when it's probably a deeper underlying problem we can find a better way to handle. [[User:StarPunch|StarPunch]] ([[User talk:StarPunch|talk]]) 16:23, 10 April 2024 (UTC)
::On Discord I proposed for recurring characters that are also bosses (mostly Dedede and Meta Knight) we should have separate boss pages for them, so that's another idea. That in general appears to be a problem for characters that appear in more than one game and aren't always bosses. {{User:Gigi/sig}} 13:39, 12 April 2024 (UTC)
 
==Add a guideline to discourage edits that don't correct or add any new information (April 10, 2024 - April 24, 2024)==
Mentioned this a couple times in the past week or so about this, and finally it's time to make it a proper proposal.


===Discussion===
For context, while not that common, sometimes there are edits on WiKirby that simply change a part of the text to one thing or another and both the version before and after the edit are correct and not incomplete. Two major examples are adding or removing the [[wikipedia:Serial comma|Oxford comma]], and adding or removing contractions to words (don't to do not, for example, and vice-versa): both are correct in English, so there is little to no point in changing from one way or another. In particular, due to both ways being correct, this can easily create a dispute between editors, and in the end there is no real resolution as there is no one way that is more correct or incorrect. So, in a similar vein to other past proposals (see [[WiKirby:Proposals/Archive-2023#Standardize_wiki_text_to_favor_some_words_without_hyphens_(December_17th,_2023_-_December_24th,_2023)|here]] and [[WiKirby:Proposals/Archive-2023#Deciding_upon_pronouns_for_characters_with_none_(March_24th,_2023_-_April_7th,_2023)|here]]), my proposal is to add a new mantra to the [[WiKirby:Writing specifics|writing specifics]], that is something like:
Re: [[User:Samwell|@Samwell]], yeah I thought about it, only a handful of wikis will ever be inter-linked in mainspace this way (the fact there are only these four templates for this purpose shows itself), relatively low number of times. As for the alignment, a parameter can be easily made to appear anywhere you want. Nonetheless, this proposed template is meant to just be an alternative for wherever the mentioned four templates are used. —[[User:Viperision|Viperision]] ([[User talk:Viperision|talk]]) 22:59, 1 April 2021 (UTC)


I wondering - where this template will be put? Not every page has external links section, and making such section solely for this template doesn't look nice (especially when it's on the right). {{User:Superbound/sig}} 15:46, 10 April 2021 (UTC)
'''Don't correct what is correct''' - Unless something is incorrect, don't correct it.
:I imagine it could just go wherever the [[Template:MarioWiki|current]] [[Template:NWiki|templates]] [[Template:SmashWiki|for this stuff]] go now, at the start of pages or sections (should work fairly well as long as a parameter to make it on the left is implemented). {{User:Pinkyoshifan/sig}} 17:14, 10 April 2021 (UTC)
::I think it would work a lot better being in the bottom section, off to the right, [https://www.mariowiki.com/Mario#References like MarioWiki handles it]. If we just had one of these replace all of those notice templates, it would be much more obnoxious. {{User:Obsessive Mario Fan/sig}} 20:58, 10 April 2021 (UTC)
:::'''@PinkYoshiFan''' [https://cdn.discordapp.com/attachments/323530530681520129/830682546034704404/viper_proposal_1.PNG here] it would look horrible in my opinion.
:::'''@Obsessive Maroi Fan''' there's problem, as this wiki almost universally uses {{t|ref}}, making it impossible to put it there, and it would be awkward having this template in urelated section like "Names in other languages" or "Gallery". [https://cdn.discordapp.com/attachments/323530530681520129/830682624217448468/viper_proposal_2.PNG This] is how it would look like if put on one of the smaller articles in the bottom section, where it's rather unnoticeable in my opinion. {{User:Superbound/sig}} 05:59, 11 April 2021 (UTC)
::::I thought we would just handle it like I mentioned, but I forgot about the ref thing, and the ways you've shown don't look good at all. I'll withdraw my vote on this for now. {{User:Obsessive Mario Fan/sig}} 06:45, 11 April 2021 (UTC)
:{{t|ref}} can be modified to include an optional parameter for code injection between <nowiki>==References== and <references/></nowiki> to make this template usable in that section like on SMW. For the [https://cdn.discordapp.com/attachments/323530530681520129/830682624217448468/viper_proposal_2.PNG Metroid article example] - I haven't figured out how to give margins to infobox templates (ideally these boxes wouldn't touch). Here [https://i.imgur.com/VVNcUIh.png are] [https://i.imgur.com/Hwy8hIL.png two] alternative ways with '''left float''' (separated from text by placing the template in a new paragraph). Regardless of this template, [https://i.imgur.com/eGnjBbf.png this is how] the current MetroidWiki template would look with "lightpink" border and "pink" background.


:Some articles don't have a "References" or "External links" section, but placing it in the very bottom right above navboxes seems how other wikis handle this. —[[User:Viperision|Viperision]] ([[User talk:Viperision|talk]]) 12:42, 11 April 2021 (UTC)
(The above can be reworded of course, this is just my first idea, feel free to suggest changes)
::Y'know, it was suggested on the Discord by erika that instead of having a separate template for linking to other NIWA wikis, we could instead add those links to the infobox for the subject in question. I think making the infobox slightly taller in order to cut down on other more intrusive templates may be the best solution here, and probably something we could enact without needing to make it a proposal. --[[User:Samwell|Samwell]] ([[User talk:Samwell|talk]]) 13:46, 11 April 2021 (UTC)
:::That seems like a good idea, but what about articles line [[Nintendo]] that don't have infoboxes? {{User:Pinkyoshifan/sig}} 14:01, 11 April 2021 (UTC)
::::I think we could keep the old notice templates for articles like that as a temporary measure. Ideally, the Nintendo article should have an infobox of some kind or other in future. --[[User:Samwell|Samwell]] ([[User talk:Samwell|talk]]) 14:06, 11 April 2021 (UTC)


I like the infobox idea, albeit that idea derails from this proposal entirely, which means that most likely it will need to separated from this. I don't mind creating {{t|Infobox-Company}} or {{Infobox-Staff}}. Also if it comes to existence I want to create a special template for inserting interwiki links here to preserve icons as they look cool.
Also, for clarification, this is not to say that we shouldn't change European English spelling to American English, that is a guideline we have on WiKirby to prefer American English stuff so that is unrelated to this proposal, and any other specific rules we may have about how to write things is also unrelated to this proposal. To put it another way, if there is no specific guideline on WiKirby to say we should say one thing one way or another, an editor shouldn't come to a page to just change it because they prefer it another way. While this mostly applies to spelling, this could be expanded to for example to changing mentions of NTSC and PAL to North American and European: as there's no rule (at least right now) on WiKirby to prefer one way or the other, there shouldn't be edits to "correct" these one way or the other.


If that doesn't come into play however, I'm not against modifying ref template like you suggested '''@Viperision'''.
What do you all think? {{User:Gigi/sig}} 16:13, 10 April 2024 (UTC)


Putting NIWA template on left just looks... ugly, I prefer the above mentioned infobox solution.
{{Support}}
#Agreed, there's no real reason to change things that are correct. {{User:Pinkyoshifan/sig}} 16:18, 10 April 2024 (UTC)
#Right, there's definitely a distinction to be had between fixing up writing to match the writing guidelines and just doing pointless style edits that don't add anything. A lot of wikis have a similar mantra, sometimes phrased as "first come, first served". If it's not ''incorrect'', there's no need to do an edit solely to change it to your preferred style. Whatever is there first should stay there, as long as it's correct and consistent. [[User:StarPunch|StarPunch]] ([[User talk:StarPunch|talk]]) 16:23, 10 April 2024 (UTC)
#I also agree. As was previously stated, if the initial wording was perfectly fine...why bother changing it? The only exception for me is applying that train of thought to using outdated video signal terminology for regional video game releases (especially since modern sources like NSO go with the standard "NA and EU version" route), but I don't think it's that pressing a concern right now. &ndash; [[User:Owencrazyboy17|Owencrazyboy17]] ([[User talk:Owencrazyboy17|talk]]) 16:48, 10 April 2024 (UTC)
#Supporting. Spelling is definitely something some people have strong opinions and preferences, even when both options are correct, so having a policy like that to prevent arguments is good. {{User:Superbound/sig}} 19:18, 11 April 2024 (UTC)
#I think this is a good thing to clarify. That said, I should warn you now that this likely will not stop certain users from insisting that certain things (like the Oxford comma situation) are ''correct'', so it probably won't stop most edit wars on these grounds. At the very least, it gives the admins firmer ground, so supporting regardless. --[[User:Samwell|Samwell]] ([[User talk:Samwell|talk]]) 19:26, 11 April 2024 (UTC)
#I concur with those above about this subject. However, I feel as though the current proposed message could be a bit more descriptive and outright include some along the lines of: "No minor wording changes" just to be more specific and clear. {{User:Basic Person/sig}} 19:36, 11 April 2024 (UTC)
{{Oppose}}
{{Neutral}}


Pink notice templates could work as a (hopefully temporary) notice template on pages without infoboxes, through as a replacement for current ones don't make sense - one of the points of the original idea was to reduce space taken by them, and it won't work like that.
===Discussion===


And my final, a little bit small, worry, is that ''"slightly taller ''[infoboxes]''"'' might not be just "slight" in case of [[Super Smash Bros. Ultimate#External Links|some pages]]. {{User:Superbound/sig}} 18:34, 12 April 2021 (UTC)
:I think we might end up doing the infobox solution over the one in my proposal. In that case, I'm not sure whether the original proposal is to be vetoed (regardless of the vote outcome). I'll try to make these into the infobox in near time. {{User:Viperision/sig}} 19:18, 12 April 2021 (UTC)
::We could just make the link section collapsed by default, but yeah, this isn't the same proposal anymore. Since it's at less than three support and zero oppose, it's just going to go on infinitely unless something happens... Should I change my vote to oppose then to stop this proposal? {{User:Pinkyoshifan/sig}} 20:36, 12 April 2021 (UTC)
{{clear}}
{{clear}}


='''Proposal Archive'''=
='''Proposal Archive'''=
{{Large|[[WiKirby:Proposals/Archive|Successful proposals]]}}</br>
{{Large|[[WiKirby:Proposals/Archive|Successful proposals]]</br>
{{Large|[[WiKirby:Proposals/Failed Archive|Failed proposals]]}}</br>
[[WiKirby:Proposals/Failed Archive|Failed proposals]]</br>
[[WiKirby:Proposals/Withdrawn Archive|Withdrawn proposals]]}}


{{clear}}
{{clear}}
{{Navbox-Help}}
{{Navbox-Help}}
[[Category:WiKirby]]
[[Category:WiKirby]]

Latest revision as of 13:39, 12 April 2024

Your opinions matter!

Welcome to the Proposals page. Here, WiKirby's editors may propose changes to the way the wiki operates, including how to handle certain categories of content, quality standards, or even just making aesthetic suggestions. Any user who has Autopatrol status or above may make a proposal or vote on one, and after two weeks of voting, if it passes, it will be incorporated into policy. Please see below for the specifics on how to make and/or vote on a proposal.

How to make a proposal

Please use one of the following templates to make a new proposal:

Single vote: This is for proposals which only propose a single change to the wiki.

==(insert proposal here) (insert date here)==
(insert details of proposal here and sign with ~~~~)
{{Support}}
{{Oppose}}
{{Neutral}}

===Discussion===

{{clear}}

Multi-option vote: This is for proposals which include many possible changes to a particular element of policy. One option should always be to keep things as they were. It is recommended that no more than 8 options are given in a single proposal, including the "no change" option.

==(insert proposal here) (insert date here)==
(insert details of proposal here and sign with ~~~~)
{{Option|1|(option title 1)}}
{{Option|2|(option title 2)}}
{{Option|3|(option title 3)}}
{{Option|etc.|(option title etc.)}}
{{Neutral}}

===Discussion===

{{clear}}

Multi-facet vote: This is for proposals which want to make several smaller changes to a single element of policy (for instance, making several changes to how the main page looks). Each change needs to be voted up or down individually. There should not be more than 5 parts to a proposal like this. This type of proposal should not be made without approval from wiki administration.

==(insert proposal here) (insert date here)==
(insert summary of proposal here and sign with ~~~~)
===Change 1===
(insert details here)
{{Support}}
{{Oppose}}
{{Neutral}}
====Change 1 discussion====

===Change 2===
(insert details here)
{{Support}}
{{Oppose}}
{{Neutral}}
====Change 2 discussion====

===Change 3===
(insert details here)
{{Support}}
{{Oppose}}
{{Neutral}}
====Change 3 discussion====

etc.

{{clear}}

Once a proposal is made, the voting period begins (see voting regulations below). Voting period for a proposal ends two weeks after it starts, at 23:59:59 UTC on the 14th full day of voting. An administrator can veto a proposal at any time, although such action should always be justifiable and agreed upon by multiple admins. Administrators should not use this right to add more weight to their own opinions.

Restrictions

Users may propose many different changes or additions to the wiki. The following things, however, may not be voted on:

  1. Proposals which target specific users (such as bestowing or removing ranks or rights).
  2. Proposals which violate the law, as specified in the general content policy.
  3. Proposals which seek to overturn a recently (within the last 8 weeks (or 56 days)) approved proposal.
  4. Re-submitted proposals which were recently (within the last 8 weeks (or 56 days)) rejected, and which have not been significantly altered.

Current Proposals

Standardized Boss Moves Locations (April 6, 2024 - April 20, 2024)

Hi! We currently have boss moves put somewhat unevenly around the wiki, with some bosses having their moves recorded on their personal pages (King Dedede, Dark Matter Clone, etc.) and at least one boss I can't track down has them on their stage page. I think these should be standardized, and specifically I think they should go to the boss stage pages. This is because:

  1. Wiki-assisted players will have the convenience of the information being on the boss page, instead of having to go somewhere else to find the knowledge they need.
  2. This will put relevant information on boss stage pages, most of which aren't stubs, but still fairly short due to their nature of being mostly just an arena (except such as in Kirby Star Allies but it still won't hurt).
  3. This will mildly slim down several character pages, only having a major impact for the already lengthy pages of King Dedede and Meta Knight, and it doesn't much impact any other boss.

Thoughts? ~ by Waddlez! 23:02, 6 April 2024 (UTC)

Option 1: move to stage page

  1. My only preferred choice. ~ by Waddlez! 23:02, 6 April 2024 (UTC)
  2. Second choice. I can see the merit in having the info on the stage page, although ultimately we're not a strategy guide. Also any standardization is better than none. ---PinkYoshiFan 23:44, 6 April 2024 (UTC)

Option 2: move to boss's character/other page

  1. First choice. It's the moveset for the character, so it should go on their page. ---PinkYoshiFan 23:44, 6 April 2024 (UTC)
  2. Primary (and only) choice. Not just because the attack tables would be better off for the character but also because of a potential problem regarding bosses exclusive to circumstances like The Ultimate Choice. More details in the Discussion section. – Owencrazyboy17 (talk) 23:55, 6 April 2024 (UTC)
  3. Single choice here. As stated, this is the boss character we're talking about, so it wouldn't make as much sense to put the move-set where the boss appears when the boss has its own page.--Paistrie (talk) 16:00, 10 April 2024 (UTC)
  4. It makes far more sense to me to list all the moves on one page given that boss moves tend to evolve over time. We could easily use an {{main}} on stage pages to link to the move listing page wherever that is. --Basic Person (talk/contribs) 19:36, 11 April 2024 (UTC)
  5. I think having boss moves on their own makes the most sense for bosses and I think it'd be best to have these instead of putting them on location pages, mostly because it would be awkward for bosses that only appear in Arena modes. NVS Pixel (talk) 13:14, 12 April 2024 (UTC)
  6. First option, and this is already what we do. Stage pages don't make sense when Kirby has many bosses exclusive to game modes like arenas, and putting boss details there would make giant pages. A boss page should cover info about a boss, and a stage page info about the stage. - Gigi (talkedits) 13:36, 12 April 2024 (UTC)

Option 3: make no changes

  1. Second option, although this is essentially the same as option 2, as we already only put boss moves in boss/character pages. For reasoning, same as option 2. - Gigi (talkedits) 13:36, 12 April 2024 (UTC)

Discussion

I thought of a bit of a major issue when it comes to option 1. Say, for example, a boss was fought exclusively in The True Arena or another location or mode with no defined stage count. If option 1 passed with the majority of votes...then how on earth would an attack table for a boss like Chaos Elfilis even work?! Wonder if there's some sort of solution that I'm not seeing... – Owencrazyboy17 (talk) 23:55, 6 April 2024 (UTC)

I'd just put it on the Colosseum page under an exclusive boss heading, myself. They wouldn't be the only exclusive boss there... I get why that might not be appealing to some if the page is just intended to describe the mode but I think that's a good solution should option 1 be passed. Alternatively, special cases could be made for them, but that'd ruin the whole standardization idea.
I'm not fond of putting it under character pages because seeing what a boss uses in each fight over a vast number of games really isn't as useful as having info about the boss in the page about where you fight it, in my opinion. ~ by Waddlez! 00:04, 7 April 2024 (UTC)

Like I mentioned on Discord, I am a bit confused on this proposal's existence. As far as I know, where to put boss attacks is already standardized, and that is to say to put it in the character/boss page, which would make option 2 and 3 the same. - Gigi (talkedits) 12:44, 10 April 2024 (UTC)

I can see the merit of moving it to the stage pages, as this would help somewhat with clogged character pages or pages for characters with multiple boss appearances where the moveset just gets listed over and over again (for example, King Dedede, Meta Knight, Kracko). I find those inconvenient. But I'm not sure if that's the proper solution to the problem, when it's probably a deeper underlying problem we can find a better way to handle. StarPunch (talk) 16:23, 10 April 2024 (UTC)
On Discord I proposed for recurring characters that are also bosses (mostly Dedede and Meta Knight) we should have separate boss pages for them, so that's another idea. That in general appears to be a problem for characters that appear in more than one game and aren't always bosses. - Gigi (talkedits) 13:39, 12 April 2024 (UTC)

Add a guideline to discourage edits that don't correct or add any new information (April 10, 2024 - April 24, 2024)

Mentioned this a couple times in the past week or so about this, and finally it's time to make it a proper proposal.

For context, while not that common, sometimes there are edits on WiKirby that simply change a part of the text to one thing or another and both the version before and after the edit are correct and not incomplete. Two major examples are adding or removing the Oxford comma, and adding or removing contractions to words (don't to do not, for example, and vice-versa): both are correct in English, so there is little to no point in changing from one way or another. In particular, due to both ways being correct, this can easily create a dispute between editors, and in the end there is no real resolution as there is no one way that is more correct or incorrect. So, in a similar vein to other past proposals (see here and here), my proposal is to add a new mantra to the writing specifics, that is something like:

Don't correct what is correct - Unless something is incorrect, don't correct it.

(The above can be reworded of course, this is just my first idea, feel free to suggest changes)

Also, for clarification, this is not to say that we shouldn't change European English spelling to American English, that is a guideline we have on WiKirby to prefer American English stuff so that is unrelated to this proposal, and any other specific rules we may have about how to write things is also unrelated to this proposal. To put it another way, if there is no specific guideline on WiKirby to say we should say one thing one way or another, an editor shouldn't come to a page to just change it because they prefer it another way. While this mostly applies to spelling, this could be expanded to for example to changing mentions of NTSC and PAL to North American and European: as there's no rule (at least right now) on WiKirby to prefer one way or the other, there shouldn't be edits to "correct" these one way or the other.

What do you all think? - Gigi (talkedits) 16:13, 10 April 2024 (UTC)

Support
  1. Agreed, there's no real reason to change things that are correct. ---PinkYoshiFan 16:18, 10 April 2024 (UTC)
  2. Right, there's definitely a distinction to be had between fixing up writing to match the writing guidelines and just doing pointless style edits that don't add anything. A lot of wikis have a similar mantra, sometimes phrased as "first come, first served". If it's not incorrect, there's no need to do an edit solely to change it to your preferred style. Whatever is there first should stay there, as long as it's correct and consistent. StarPunch (talk) 16:23, 10 April 2024 (UTC)
  3. I also agree. As was previously stated, if the initial wording was perfectly fine...why bother changing it? The only exception for me is applying that train of thought to using outdated video signal terminology for regional video game releases (especially since modern sources like NSO go with the standard "NA and EU version" route), but I don't think it's that pressing a concern right now. – Owencrazyboy17 (talk) 16:48, 10 April 2024 (UTC)
  4. Supporting. Spelling is definitely something some people have strong opinions and preferences, even when both options are correct, so having a policy like that to prevent arguments is good. Superbound (talk) 19:18, 11 April 2024 (UTC)
  5. I think this is a good thing to clarify. That said, I should warn you now that this likely will not stop certain users from insisting that certain things (like the Oxford comma situation) are correct, so it probably won't stop most edit wars on these grounds. At the very least, it gives the admins firmer ground, so supporting regardless. --Samwell (talk) 19:26, 11 April 2024 (UTC)
  6. I concur with those above about this subject. However, I feel as though the current proposed message could be a bit more descriptive and outright include some along the lines of: "No minor wording changes" just to be more specific and clear. --Basic Person (talk/contribs) 19:36, 11 April 2024 (UTC)
Oppose
Neutral

Discussion

Proposal Archive

Successful proposals
Failed proposals
Withdrawn proposals

KSA Parasol Waddle Dee Pause Screen Artwork.png