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
(→‎Using bold or italics for music names (December 18th, 2023 - January 1st, 2024): as mentioned on the discord, I was completely wrong about what I thought the standard was. Doing the <!-- --><br><s></s> thing to not break the numbering)
 
(93 intermediate revisions by 17 users not shown)
Line 2: Line 2:


='''Current Proposals'''=
='''Current Proposals'''=
==Standardize wiki text to favor some words without hyphens (December 17th, 2023 - December 31st, 2023)==
==Create categories for names in specific languages (June 21, 2024 - July 5, 2024)==
I honestly don't know what else to name this, nor exactly how to word it as a guideline eventually. But these five words in particular have been brought up by many different editors over the years, and it has caused some confusion of new editors and sometimes even readers.
This topic was discussed on Discord, but after it felt like it was settled, arguments against were brought up, which is why this proposal exists. The gist of it is to split [[:Category:Articles which list non-English names]] by language (Japanese, Korean, Italian, et cetera).


You are reading an article, and it writes "moveset" for one section. You keep reading and another section calls it "move-set". Does that sound familiar?
The reasoning here is that, as of now, the category has little to no practical use. I believe it was originally created to track progress of pages which lacked the template, and the description was modified to <u>encourage speakers of the languages to help explain the names</u>. Nowadays, almost every article fits in there, with the exception of those which have conjectural or meta names and therefore don't need the template at all. Reasonably, I don't see anyone using the category for serious purposes.


Move-set, cut-scene, mid-air, 3-D and 2-D are the five most common words I've seen on WiKirby article text that are sometimes spelled with hyphens, sometimes not. In particular, most of these five words are mostly commonly spelled without hyphens (which I will prove soon), and in official Kirby text, we've only had usages of them without hyphens as far as I know (although for "moveset", I haven't really seen any official use of the word in any form). You are free to correct me if I'm wrong on official usage, but in particular for 3D and 2D, I've fairly sure of that, at least in recent sources. And, I mean, it's the Nintendo 3DS and 2DS, not 3-DS and 2-DS...
On the other hand, having categories for specific languages has several benefits: 1. Speakers of the languages will actually be able to find the pages which concern them, rather than the current thousands of pages 2. In a case where the page doesn't mention a name but the speaker knows it, using the split category will help pin it down with alphabetical deduction 3. For languages which have few localizations, it helps give a general overview, which is just interesting from a reader's point of view.


Point is, there is no standardization, so some articles use them with hyphens, some without, some mix and match, and it's not uncommon for editors to go and "fix" to one way or the other. But without a rule, anyone could revert these changes and go "actually, I prefer with/without hyphen". Also, as I mentioned, it's clear that the most common forms of these five words are without hyphens, being used in official Kirby media as well.
Some downsides which were pointed out are 1. You can't exclude a specific category, so you would still have to analyze several categories if you want to find pages with only a specific (group of) language(s) 2. It's a lot of additional categories for a niche function. In my opinion, most downsides will still mostly remain even with our current system; if anything, more specific search has at least 1-2 additional uses. It's not that much extra work (I already made the template edit draft under a sandbox), so the real issue is clutter.


With all these in mind, my proposal is to standardize the spelling of these words, much how we favor spelling of words in American English, to the following:
Finally, even if it is implemented, we're not sure whether or not to separate regional variants (e.g. Canadian or European French). If we judge from a translator's point of view, then there isn't much of a reason to split them; but for research purposes (about localization in different countries), splitting would give extra insight.


*'''Cutscene''' over '''cut-scene'''. "Cutscene" has 33 million results in Google, while "cut-scene" has 3 million. One example of "cutscene" being used in official Kirby media, Miiverse posts: [[List of HAL Laboratory Miiverse posts - Kirby: Triple Deluxe]];
Anyway, this is something that is best voted on. If none of the aforementioned options are to your liking, there's always the wildcard option of getting rid of the category altogether. {{User:ShadowKirby/sig}} 13:12, 21 June 2024 (UTC)
*'''Moveset''' over '''move-set'''. "Moveset" has 15 million results on Google, while "move-set" has 1.5 million (with many actually resulting in finding "move set", and not "move-set"). I don't actually know any examples of official Kirby media using the word in either form;
*'''Midair''' over '''mid-air'''. This one is the only one basically tied on Google: "midair" has 18 million results on Google, while "mid-air" has 22 million. However, officially Kirby has only ever used "midair", in moveset descriptions;
*'''3D''' over '''3-D'''. "3D" has 3.6 billion results on Google, while "3-D" has 276 million. Many names use "3D" and none use "3-D", such as [[3D Classics: Kirby's Adventure]], [[3D Helmet Cannon]], [[3D Warp Star]] etc. Descriptions of ''Forgotten Land'' in particular use 3D, such as [https://www.nintendo.com/us/store/products/kirby-and-the-forgotten-land-switch/ the one on Nintendo's website];
*'''2D''' over '''2-D'''. "2D" has 1.2 billion results on Google, while "2-D" has 214 million (should mention though that a good number of the results actually are for the Gorillaz member). For consistency with "3D". I don't know of many sources that use "2D", but at least [https://gigi9714.wordpress.com/2023/04/07/translation-of-the-kirbys-return-to-dream-land-deluxe-interview-from-the-may-2023-edition-of-nintendo-dream/ this interview I translated] used it (yes, even in the original Japanese text).


So, what do you all think? I think something like this is long overdue. I accept suggestions on where/how to word it, but I feel this is something we need to officially address in some form. {{User:Gigi/sig}} 19:14, 17 December 2023 (UTC)
{{Option|1|Split, keep regional variants together}}
 
#First choice. I'm in the translator camp, and I don't think separating variants makes too much sense. {{User:ShadowKirby/sig}} 13:12, 21 June 2024 (UTC)
{{Support}}
#First choice, I'm not in the translator camp but I don't see much purpose in separating language variants. {{User:Pinkyoshifan/sig}} 13:22, 21 June 2024 (UTC)
#I definitely agree that it should be standardized. For every example other than move-set, it automatically makes the most sense to spell it without a hyphen, since that's what official Kirby media does. For every example other than mid-air, it's more commonly spelled without a hyphen online. And for all examples, I personally think it just looks better without a hyphen. {{User:RHVGamer/sig}} 19:34, 17 December 2023 (UTC)
#Second choice, I don't really mind either way about the regions, but the new categories can be useful. [[User:SilvTheGrape|SilvTheGrape]] ([[User talk:SilvTheGrape|talk]]) 13:52, 21 June 2024 (UTC)
#Standardization is good, especially when it matches Kirby media. {{User:Pinkyoshifan/sig}} 21:33, 17 December 2023 (UTC)
#First choice. I do think splitting regional variants is going overboard, but this could be useful for listing pages with, say, Spanish names. It wouldn’t be too many extra categories, either, and it’d be much more useful than the status quo. {{User:YoshiFlutterJump/sig}} 15:25, 21 June 2024 (UTC)
#I'm in favor of consistency, especially considering how most of these terms have spelling variant that is clearly more common than the other. [[User:Typman|Typman]] ([[User talk:Typman|talk]]) 22:40, 17 December 2023 (UTC)
{{Option|2|Split, keep regional variants separate}}
#I agree. Consistency is cool. --[[User:Paistrie|Paistrie]] ([[User talk:Paistrie|talk]]) 00:06, 18 December 2023 (UTC)
#Second choice. Generally not opposed to the idea of doing this though. {{User:ShadowKirby/sig}} 13:12, 21 June 2024 (UTC)
#Support. (And even if moveset isn't confirmed anywhere I prefer that, which isn't what we're going for but still consistent) {{User:ShadowKirby/sig}} 07:14, 18 December 2023 (UTC)
#Second choice, either this or above is fine with me but slightly prefer together for less clutter. {{User:Pinkyoshifan/sig}} 13:22, 21 June 2024 (UTC)
#Consistency is important, so support. --{{User:EleCyon/sig}} 13:54, 18 December 2023 (UTC)
#First choice, it would be easier to find out if a translation is missing in one of the regions by keeping them separate. [[User:SilvTheGrape|SilvTheGrape]] ([[User talk:SilvTheGrape|talk]]) 13:52, 21 June 2024 (UTC)
#Consistency is always appreciated, support. [[User:Infinite Possibilities|Infinite Possibilities]] ([[User talk:Infinite Possibilities|talk]]) 19:52, 19 December 2023 (UTC)
#Second choice. It sounds unwieldy to me compared to Option 1, but this can definitely work, and is still an improvement from the status quo. {{User:YoshiFlutterJump/sig}} 15:25, 21 June 2024 (UTC)
#Though I still prefer “move set”, a more formal spelling used by ''Smash Bros.'', all four others are entered in the Merriam-Webster and New Oxford American dictionaries unhyphenated. And in any case, consistency is always a good idea. {{User:YoshiFlutterJump/sig}} 22:57, 19 December 2023 (UTC)
{{Option|3|Do not split, keep category as is}}
#I agree. There's not really anything I can say to support it since everyone else had the same idea, but it holds the same weight. {{User:Starvoid/sig}} 23:15, 19 December 2023 (UTC)
{{Option|4|Delete category}}
#This is on the same level as (for example) having articles written in third person and in present tense by default, and likewise should be part of the [[WiKirby:Writing style|style guide]]. {{User:WillIdleAway/sig}} 00:35, 20 December 2023 (UTC)
#Third choice. I see no use in the category as it is today, something needs to change imo. {{User:ShadowKirby/sig}} 13:12, 21 June 2024 (UTC)
{{Oppose}}
#Third choice. As it is right now, it's basically just [[Special:Whatlinkshere/Template:Names|whatlinkshere]] sorted alphabetically. {{User:Pinkyoshifan/sig}} 13:22, 21 June 2024 (UTC)
{{Neutral}}
#Third choice. The category as it stands is not very useful at all, so with no other changes to it, might as well delete it. {{User:YoshiFlutterJump/sig}} 15:25, 21 June 2024 (UTC)
 
===Discussion===
 
{{clear}}
 
==Using quotation marks for music names (December 18th, 2023 - January 1st, 2024)==
This will be the first of hopefully a full series of proposals concerning music and their dedicated pages. To start it simple, I would like to suggest making quotation marks for their titles consistent. The difference is essentially [[Green Greens (theme)|Green Greens]] vs Green Greens vs "Green Greens" (to name an example). As we have it now, the more common formatting (or what it should be) is:
*Quotation marks:
**Opening abstract
**Infobox caption
**Outside of links in composition and game appearances [edit that hopefully doesn't cause conflict: actually no, this is inconsistent, but it's due to bold text and italics, which will be a proposal for another time I suppose {{User:ShadowKirby/sig}} 14:59, 18 December 2023 (UTC)]
 
*No quotation marks:
**Music navboxes
**Page title
**Infobox title
**Within names in other languages tables
**Jukebox tables
 
*Inconsistent usage:
**Conjectural titles in various areas, in particular with "the" preceding the name
**Headings for English names in other languages
**Track names for stage/level infoboxes
**Titles within links outside of templates
 
The inconsistencies are the more concerning part. I don't think any changes should be made to the currently consistent format, but that is open to discussion in the corresponding section. The four points of inconsistency will have separate votes, to make it easier. '''Votes in favor''' (where applicable) are for '''adding quotation marks''', while voting '''against''' is for '''removing''' them. {{User:ShadowKirby/sig}} 08:52, 18 December 2023 (UTC)
 
Update: I clarified what is what under each section with examples since there was confusion. {{User:ShadowKirby/sig}} 13:23, 18 December 2023 (UTC)
 
===Conjectural titles===
Examples:
*The "[[Town (theme)|Town]]" theme and "[[Ordeal (theme)|Ordeal]]"
*The [[Town (theme)|Town]] theme and "[[Ordeal (theme)|Ordeal]]"
*The [[Town (theme)|Town]] theme and [[Ordeal (theme)|Ordeal]]
{{Option|1|Always use quotation marks}}
#Second choice. I'd rather have all of them be distinguished like that than not at all. [[User:Infinite Possibilities|Infinite Possibilities]] ([[User talk:Infinite Possibilities|talk]]) 19:52, 19 December 2023 (UTC)
#First choice. It looks more consistent this way, and it looks better to distinguish music names like this. -{{User:YoshiFlutterJump/sig}} 23:03, 19 December 2023 (UTC)
#First choice. While it may look a bit strange, it makes sense so that editors and viewers can tell if something is a song name or part of a song name. {{User:Starvoid/sig}} 23:20, 19 December 2023 (UTC)
{{Option|2|Do not use quotation marks if "the" is present}}
#First choice. I can see the quotation marks being helpful for distinguishing conjectural titles, but it looks a bit off with <code>The "name" theme</code>. {{User:Pinkyoshifan/sig}} 13:55, 18 December 2023 (UTC)
#First choice. When a "the" precedes the conjectural name adding quotation marks as well seems unnecessary to me. [[User:Infinite Possibilities|Infinite Possibilities]] ([[User talk:Infinite Possibilities|talk]]) 19:52, 19 December 2023 (UTC)
#Second choice, per above, but I feel like it’s better to avoid this use to whatever extent possible; just “Town” and “Ordeal” are sufficient. {{User:YoshiFlutterJump/sig}} 23:03, 19 December 2023 (UTC)
#Second choice. Very similar to my first choice, but removing "the". {{User:Starvoid/sig}} 23:20, 19 December 2023 (UTC)
#First choice. If a name isn't official, I don't see much use to put quotations in a theme name when it has "the" before and "theme" after. Meanwhile, without the "the" and "theme" it can get confusing what is being talked about, and quotation marks can help clarify it's about a song, even if the name isn't official. {{User:Gigi/sig}} 01:30, 20 December 2023 (UTC)
{{Option|3|Do not use quotation marks}}
#Second choice. Having quotation marks to distinguish conjectural titles could be good but I'm fine with this one too. {{User:Pinkyoshifan/sig}} 13:55, 18 December 2023 (UTC)
#Second choice. In a way, not using quotations for conjectural names makes it clearer in general that they aren't official names. {{User:Gigi/sig}} 01:30, 20 December 2023 (UTC)
{{Neutral}}
 
===Names in other languages headings===
Compare [[Time for the Results#Names in other languages]] and [[Memories (I'll Never Forget You)#Names in other languages]]
{{Support}}
#Per my vote for the infoboxes. I don’t see any issue with using quote marks here, consistency is better, and we italicize game names in headings the same way. {{User:YoshiFlutterJump/sig}} 23:10, 19 December 2023 (UTC)
{{Oppose}}
#When the track name is the only thing in the heading, the quotation marks just make it look more cluttered. {{User:Pinkyoshifan/sig}} 13:44, 18 December 2023 (UTC)
#Similar to my vote above, I don't think adding quotation marks is necessary when it is already distinguished, in this case by being alone in the heading. [[User:Infinite Possibilities|Infinite Possibilities]] ([[User talk:Infinite Possibilities|talk]]) 19:52, 19 December 2023 (UTC)
{{Neutral}}
 
===Music in stage/level infoboxes===
Compare [[Butter Building - Stage 1]] and [[Popstar]]
{{Support}}
#We italicize game names even if they’re the only thing in the infobox section, so I don’t see the issue with using quote marks here. Again, consistency is always better. {{User:YoshiFlutterJump/sig}} 23:08, 19 December 2023 (UTC)
#It can get really confusing when songs named after stages/levels get linked in infoboxes. Without the quotation marks, a reader can be confused and wonder, for example, why there is "The Fountain of Dreams" in [[Nebula Belt]]: they could think of the location before the song. While, sure, you could argue they should know better because there is a description and music files above, it's important to consider. And since we often add game names to clarify where a song is from (like in [[Bubbly Clouds (Battle Stage)]]) I feel it makes sense to be consistent and, much how games are always italicized, we should have song names with quotation marks. {{User:Gigi/sig}} 01:38, 20 December 2023 (UTC)
{{Oppose}}
#Same as with names in other languages above, when the track name is the only thing there, the quotation marks just make it look more cluttered. {{User:Pinkyoshifan/sig}} 13:44, 18 December 2023 (UTC)
#Also similar to my votes above, when the track name it is already distinguished in some way, in this case by being alone in the infobox, adding quotation marks doesn't really add anything. [[User:Infinite Possibilities|Infinite Possibilities]] ([[User talk:Infinite Possibilities|talk]]) 19:52, 19 December 2023 (UTC)
{{Neutral}}
 
===Outside of square (link) brackets===
Compare [[Inside the Castle#Composition]] and [[Coin Clash (theme)#Composition]]
{{Support}}
#Here having quotation marks appears as the logical throughline to me. Makes it easier to tell at a glance whether it refers to a track or something else. [[User:Infinite Possibilities|Infinite Possibilities]] ([[User talk:Infinite Possibilities|talk]]) 19:52, 19 December 2023 (UTC)
#Can’t really add too much to my vote comments above, but in addition to that, it makes it immediately obvious whether the link goes to [[Green Greens]] or "[[Green Greens (theme)|Green Greens]]". {{User:YoshiFlutterJump/sig}} 23:14, 19 December 2023 (UTC)
{{Oppose}}
#I think it's better to just do what we do for other articles (e.g. [[Kirby]]) and just bold the first instance of the article title in the infobox as well as the main text. {{User:Pinkyoshifan/sig}} 13:44, 18 December 2023 (UTC)
{{Neutral}}
{{Neutral}}
 
#I was the one who was opposed or at least concerned about the specifics of this, but I'm leaning neutral now as I see there's some support for this idea and so it's not as niche as I initially anticipated. I think there is some value to splitting regional variants if this is done, but I can see why you wouldn't want to. My main concern right now is clutter, as we'll have a lot of similar-looking categories even if they're hidden, but if they're serving a purpose then no harm no foul. It's all automated so I suppose it'd be easy to tweak or remove anyway. [[User:StarPunch|StarPunch]] ([[User talk:StarPunch|talk]]) 17:54, 21 June 2024 (UTC)
===Discussion===
===Discussion===
:Regarding the comment for the vote for the fourth aspect (quotation marks paired with links), I would like to be clear that it does not affect bold text. It affects listing other themes as a part of the composition or a medley. For example, it's differentiating between <"Green Greens" can include [[Kirby's Triumphant Return]]> and <"Green Greens" can include "[[Kirby's Triumphant Return]]">. {{User:ShadowKirby/sig}} 15:55, 18 December 2023 (UTC)
{{clear}}
==Using bold or italics for music names (December 18th, 2023 - January 1st, 2024)==
The sister proposal for the above, for an individual aspect that is significantly more complex than the above.
'''Bold''' text can be seen used:
*In the infobox caption and opening abstract
*For alternate names listed in the article
*When listing medleys that a theme is a part of
''Italics'' are typically used for translations of foreign titles.
They serve as a visual cue, preventing important information from going unnoticed, but between their interactions with links and/or quotation marks, they are used inconsistently, in particular as far as the latter two points are concerned. So, here come more subpoints to discuss. {{User:ShadowKirby/sig}} 15:52, 18 December 2023 (UTC)
===Formatting alternate names (English)===
For example, "[[A Trip to Alivel Mall (theme)|A Trip to Alivel Mall]]" is named "Love, Love, Alivel" in ''Kirby's Dream Buffet''. [[Welcome to the New World!]] is "Kirby and the Forgotten Land: Bonus Song 3". So, how do we treat these? (Ranked voting highly recommended due to a large number of options)
{{Option|1|Only bold}}
{{Option|2|Only italics}}
#When writing/typing the name of a song, I'm pretty sure you're supposed to either italicize it or underline. This format would technically be the most correct one. --[[User:Paistrie|Paistrie]] ([[User talk:Paistrie|talk]]) 17:12, 18 December 2023 (UTC)<!--
--><br><s>#First choice. Italicizing music titles is the standard for main titles, I don't see a reason why that shouldn't apply to other titles. {{User:Pinkyoshifan/sig}} 01:26, 20 December 2023 (UTC)</s>
{{Option|3|Only quotation marks}}
#Second choice. Would want to avoid italics personally. {{User:ShadowKirby/sig}} 06:38, 20 December 2023 (UTC)
#Second choice. Same reasoning as before with consistency, although it seems like the standard both here and in other places is actually quotes for single track titles (italics for albums).
{{Option|4|Bold and italics}}
{{Option|5|Bold and quotation}}
#First choice. To highlight the important text and still be consistent with using quotation (per discussions way above) {{User:ShadowKirby/sig}} 06:38, 20 December 2023 (UTC)
#First choice. I can see this being helpful since that might be what brought people to an article. {{User:Pinkyoshifan/sig}} 13:35, 20 December 2023 (UTC)
{{Option|6|Italics and quotation}}
{{Option|7|All formatting}}
{{Neutral}}
===Formatting (alternate) names (foreign)===
This primarily applies to names from something like ''Kirby Star Allies'', where we have an official Japanese title. This is more complex. Do we want to name only the English text and have Japanese in Names in other languages? Or name Japanese and English together in text? If the latter, then how? For the first case, formatting is established in the above proposals will be used. '''Foreign titles will not be within quotation marks or italics''' (unless someone in discussions shows up and disagrees) because they're clunky, and so is this proposal.
{{Option|1|Only English name in text}}
{{Option|2|Don't bold foreign, italics English}}
<s>#Second choice. Italicizing the English name seems good to be consistent with native English names being italicized, but bolding the foreign name seems standard on other wikis and also to some extent here. {{User:Pinkyoshifan/sig}} 01:26, 20 December 2023 (UTC)</s>
#Second choice. Makes sense if there is no reason to bold the foreign text ig. {{User:ShadowKirby/sig}} 06:38, 20 December 2023 (UTC)
{{Option|3|Bold foreign, italics English}}
#In many other wiki websites, many foreign names are bolded, while translations are italicized. This one should be used in order to be consistent with other wikis. --[[User:Paistrie|Paistrie]] ([[User talk:Paistrie|talk]]) 17:43, 19 December 2023 (UTC)
#First choice. This seems to be the current de facto standard, and avoiding names in other languages sections having several tables with one line seems good. {{User:Pinkyoshifan/sig}} 01:26, 20 December 2023 (UTC)
#First choice. It's how we do it now in most cases. If the foreign name doesn't have quotations and translation is in paranthesis, quotation marks would only add to clutter, right? {{User:ShadowKirby/sig}} 06:38, 20 December 2023 (UTC)
{{Option|4|Don't bold foreign, quotation marks English}}
#Second choice. Again, same reasoning as before with consistency with native English names but now looking at the actual standard for those.
{{Option|5|Bold foreign, quotation marks English}}
{{Option|6|Don't bold foreign, double format English}}
{{Option|7|Bold foreign, double format English}}
{{Neutral}}
===Formatting medleys===
This technically overlaps with the foreign names point half of the time, but it stands separate for something like... "[[Kirby's Triumphant Return]]". This overrides the bold rule for foreign titles above for medleys specifically. Aspects not mentioned here are covered above (this includes the use of quotation marks).
{{Option|1|Bold medleys}}
#First choice. In favour of bolding medleys as important info. {{User:ShadowKirby/sig}} 06:38, 20 December 2023 (UTC)
{{Option|2|Don't bold medleys (includes foreign)}}
#Second choice, to not differentiate foreign from English going with this. In case it's suddenly considered not too important. {{User:ShadowKirby/sig}} 06:38, 20 December 2023 (UTC)
#First choice. While it's most likely an edge case with this, [[Kirby's Triumphant Return]] does show one issue with bolding medleys in the KatFL section: bold stops looking important because there's so many things bolded. {{User:Pinkyoshifan/sig}} 13:35, 20 December 2023 (UTC)
{{Option|3|Don't bold medleys (doesn't include foreign)}}
{{Option|4|Italics for medleys (doesn't include foreign)}}
#Since these are still individual themes, italicizing these would also be grammatically correct. --[[User:Paistrie|Paistrie]] ([[User talk:Paistrie|talk]]) 17:50, 19 December 2023 (UTC)<!--
--><br><s>#First choice. Same reason for other votes, normal music tracks are italicized and I don't see why that shouldn't apply here. {{User:Pinkyoshifan/sig}} 01:26, 20 December 2023 (UTC)</s>
{{Neutral}}


{{clear}}
{{clear}}

Latest revision as of 17:54, 21 June 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.
Voting regulations
  1. Proposal adding and voting is open only to registered users who have attained Autopatrol status and above. Users who do not have Autopatrol+ may still participate in discussions.
  2. Users who are currently blocked will not be allowed to vote, and any outstanding votes they have on proposals will be removed. Any proposal made by a user who is blocked during the consideration period will also be removed.
  3. All votes must be signed with signatures (type four tildes (~~~~.)) Unsigned votes are automatically negated, regardless of any points made.
  4. After two (2) weeks of voting, a proposal will be immediately enacted if the number of supportive votes is greater than the number of opposing votes, or, in the case of multi-option votes, any option receives a plurality consisting of three or more votes. In the event of a tie, the proposal may be re-voted upon with a one week duration, or annulled by the administrators.
  5. In the event a proposal has seven (7) unanimous support votes OR ten (10) support votes and no more than two neutral votes, as well as the support of a bureaucrat, a proposal may pass in only one (1) week instead of two.
  6. If a supported proposal is vetoed by the administrators, it is considered failed and should not be started again for at least 8 weeks (56 days).
  7. If a proposal fails to garner three (3) supporting votes (or 3 votes on any one option in multi-option proposals), it will not be considered.
  8. The original proposal maker may not vote on their own proposal if it only contains two options (i.e., "yes" or "no" proposals). However, proposers may vote on their own proposals if they have three or more options.
  9. All votes must be supported by a substantial reason from the voter. Simple and/or unproductive comments like "I agree" or "No that's stupid" will result in the vote being removed.
  10. The original proposer may cancel the proposal for any reason during the first three (3) days of its run, and it will not be considered failed. Admins may veto subsequent proposals if this is abused.
  11. Voting users may change their vote at any time before a proposal's deadline passes, but should update their timestamp if doing so.
  12. Discussion must remain civil at all times! Any uncivil discussion will result in the offending users' votes being negated, and possibly lead to strikes or a block.
  13. Excessive campaigning for any proposals will result in the campaigner's vote(s) being negated, or proposal being removed if applicable.
  14. Proposals about minor article manipulation (such as splits, merges, renames, or deletions) should not be created, unless the scope of the discussion is particularly large; otherwise, these should be handled on a case-by-case basis, through discussions or polls on the talk page of the article in question.
  15. It is recommended that a single user make only one (1) proposal at a time. Though simultaneous proposals from the same user are allowed, they are discouraged; this should ideally only be done if multiple issues are in question, and not many proposals are already active.
  16. For multi-option votes, voters are encouraged (but not required) to indicate a first, second, third, etc. vote. The exception to this is neutral votes, which must be the only vote if chosen.

Current Proposals

Create categories for names in specific languages (June 21, 2024 - July 5, 2024)

This topic was discussed on Discord, but after it felt like it was settled, arguments against were brought up, which is why this proposal exists. The gist of it is to split Category:Articles which list non-English names by language (Japanese, Korean, Italian, et cetera).

The reasoning here is that, as of now, the category has little to no practical use. I believe it was originally created to track progress of pages which lacked the template, and the description was modified to encourage speakers of the languages to help explain the names. Nowadays, almost every article fits in there, with the exception of those which have conjectural or meta names and therefore don't need the template at all. Reasonably, I don't see anyone using the category for serious purposes.

On the other hand, having categories for specific languages has several benefits: 1. Speakers of the languages will actually be able to find the pages which concern them, rather than the current thousands of pages 2. In a case where the page doesn't mention a name but the speaker knows it, using the split category will help pin it down with alphabetical deduction 3. For languages which have few localizations, it helps give a general overview, which is just interesting from a reader's point of view.

Some downsides which were pointed out are 1. You can't exclude a specific category, so you would still have to analyze several categories if you want to find pages with only a specific (group of) language(s) 2. It's a lot of additional categories for a niche function. In my opinion, most downsides will still mostly remain even with our current system; if anything, more specific search has at least 1-2 additional uses. It's not that much extra work (I already made the template edit draft under a sandbox), so the real issue is clutter.

Finally, even if it is implemented, we're not sure whether or not to separate regional variants (e.g. Canadian or European French). If we judge from a translator's point of view, then there isn't much of a reason to split them; but for research purposes (about localization in different countries), splitting would give extra insight.

Anyway, this is something that is best voted on. If none of the aforementioned options are to your liking, there's always the wildcard option of getting rid of the category altogether. ShadowKirby (t/c) a.k.a. your new overlord ShadowMagolor 13:12, 21 June 2024 (UTC)

Option 1: Split, keep regional variants together
  1. First choice. I'm in the translator camp, and I don't think separating variants makes too much sense. ShadowKirby (t/c) a.k.a. your new overlord ShadowMagolor 13:12, 21 June 2024 (UTC)
  2. First choice, I'm not in the translator camp but I don't see much purpose in separating language variants. ---PinkYoshiFan 13:22, 21 June 2024 (UTC)
  3. Second choice, I don't really mind either way about the regions, but the new categories can be useful. SilvTheGrape (talk) 13:52, 21 June 2024 (UTC)
  4. First choice. I do think splitting regional variants is going overboard, but this could be useful for listing pages with, say, Spanish names. It wouldn’t be too many extra categories, either, and it’d be much more useful than the status quo. -YFJ (talk · edits) 15:25, 21 June 2024 (UTC)
Option 2: Split, keep regional variants separate
  1. Second choice. Generally not opposed to the idea of doing this though. ShadowKirby (t/c) a.k.a. your new overlord ShadowMagolor 13:12, 21 June 2024 (UTC)
  2. Second choice, either this or above is fine with me but slightly prefer together for less clutter. ---PinkYoshiFan 13:22, 21 June 2024 (UTC)
  3. First choice, it would be easier to find out if a translation is missing in one of the regions by keeping them separate. SilvTheGrape (talk) 13:52, 21 June 2024 (UTC)
  4. Second choice. It sounds unwieldy to me compared to Option 1, but this can definitely work, and is still an improvement from the status quo. -YFJ (talk · edits) 15:25, 21 June 2024 (UTC)
Option 3: Do not split, keep category as is
Option 4: Delete category
  1. Third choice. I see no use in the category as it is today, something needs to change imo. ShadowKirby (t/c) a.k.a. your new overlord ShadowMagolor 13:12, 21 June 2024 (UTC)
  2. Third choice. As it is right now, it's basically just whatlinkshere sorted alphabetically. ---PinkYoshiFan 13:22, 21 June 2024 (UTC)
  3. Third choice. The category as it stands is not very useful at all, so with no other changes to it, might as well delete it. -YFJ (talk · edits) 15:25, 21 June 2024 (UTC)
Neutral
  1. I was the one who was opposed or at least concerned about the specifics of this, but I'm leaning neutral now as I see there's some support for this idea and so it's not as niche as I initially anticipated. I think there is some value to splitting regional variants if this is done, but I can see why you wouldn't want to. My main concern right now is clutter, as we'll have a lot of similar-looking categories even if they're hidden, but if they're serving a purpose then no harm no foul. It's all automated so I suppose it'd be easy to tweak or remove anyway. StarPunch (talk) 17:54, 21 June 2024 (UTC)

Discussion

Proposal Archive

Successful proposals
Failed proposals
Withdrawn proposals

Basic help
Getting started • Categories • Colors • Disambiguation • File uploading • Formatting • Formatting file pages • Moving pages • Protected Page • Redirects • References • Tables • Talk pages • Templates • User Navigation Bar • Userboxes
Advanced help
Advanced tables • Creating navmaps • Creating templates • Custom Signatures • HTML • Page history • Special pages • Tabs • Template documentation • Using infoboxes
Policies
Abbreviations • Article creation • Article manipulation • Audio standards • Blocking of users • Categories • Citing • Community polls • Conjecture • Cookies • Copyrights • Deletion of content • Disputes • Featured content • File use • Formatting specifics • General content • General disclaimer • Glitch disclaimer notes • Glitches • Image standards • Infoboxes and Navboxes • Interwiki • Language • Layout • Localization • Long pages • Naming • Non-Kirby content • Personal content • Privacy • Sourcing standards • Stubs • Talk pages • Trivia sections • User accounts • Videos • Writing style • Writing specifics
Useful links
About WiKirby • Affiliates • April Fools • Archive • Current events • Dedication • Discord • Featured Article Nomination • Featured Picture Nomination • Good recommendations • IPA • Maintenance (Project Clean-Up) • Proposals • Ranks (Bots • Check user • Editor-in-Chief • System Admin) • Sandbox • Social media • Special pages
KSA Parasol Waddle Dee Pause Screen Artwork.png
Retrieved from "https://wikirby.com/w/index.php?title=WiKirby:Proposals&oldid=479036"