From WiKirby, your independent source of Kirby knowledge.
Jump to navigationJump to search

Your opinions matter!

Due to WiKirby's recent surge in community interaction, we have seen fit to implement a formal proposals page. Up to this point, proposal-handling has been informal, with larger ones handled via referendum, but this page serves to clear away any ambiguity and provide a set of procedures for suggesting changes to the wiki, whether that be the handling of certain content, or changes and additions to policy.

How to make a proposal

All proposals must be made using the template provided below, posted under the "Current Proposals" heading:

==(insert proposal here) (insert date here)==
(insert details of proposal here and sign with ~~~~)



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 11:59:59 P.M. UTC on the 14th 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.


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.

Current Proposals

Overhaul Template:Aboutfile 101621-103021

I've come to make an announcement in regards to the project that I am leading regarding adding Template:Aboutfile to every image that lacks it currently. In short, I want to make changes to the currently existing template to be more like the Template:File on Wars Wiki and StrategyWiki (see here).

Simply put, I think that this template is not only objectively better but also extremely easy to implement. Here is a list of reasons in a relative order of importance:

  • This would be a non-destructive change. This is only changing the components of Aboutfile, which means that that the old styling and the suggested new changes can be together without conflict. This is simply just trying to add to the existing template, not make a new one.
  • It's drastically easier for new users to use. People that don't have much experience uploading files will find exactly everything they need to enter directly where it needs to be, most likely without having to open up other pages or categories to see exactly what needs written for that file, and don't need to memorize certain aspects of uploading.
  • It's drastically easier for you, yes YOU to use. The primary benefit to Wars' Template:File is that a lot of components don't need to be manually written. If a game is entered into the |game= slot, the game not only has a link to it, but is automatically categorized for that game. Wars' |type= section not only categorizes the file to the "type" conditional's category (like Category:Screenshots) but also automatically generates the file license which means...
  • No more licensing templates needed. Everything will automatically be fed through the template and generate exactly what is needed! No need to write out categories or licenses. This is a fantastic way to reduce potential errors, as typos can always exist on the categorization meaning people looking for images cannot find them as easily.
  • Sourcing becomes a lot better managed. Currently for Wars, if a section is left blank, the file will automatically be added to a category for unsourced files. What could occur is the current file needs sourcing template is integrated into the new Aboutfile template so that there is a bright, contrasting warning inside the box indicating the file has no source and one needs located. This can be taken a step further by having a second warning specifically for any files sourced through Kirby FANDOM or FANDOM overall.
  • Finding errors and improvements when changing the template. I have seen a significant as in over 200 files that need image-quality templates, header fixes, or other types of fixes while compiling the list. This is a fantastic way to address these types of problems when making changes to files anyway.
  • Saves space on new uploads. This is pretty minor. But it's cool and notable.

The only current either downside or hinderances in my way for fully integrating this today right now are the following: Your collective support for the idea, making the template still look as pretty as it does now, and how exactly we would approach other media like the anime or books or something. I would personally suggest just dropping it in |game= but there might be a few lingustic rivals amongst us that disagree with using game for not-games.


  • Aboutfile is converted to include the automatics involved in Wars Wiki's Template:File through additional parameters.
  • Template:File source is converted to File source link (or something similar) to specifically notate files that have a written source, but no link to it (such as many of RMV's uploads). File source needed and Not-using-FANDOM conditionals are built into Aboutfile.
  • Trig posts his big freaky list and people start chipping away at it.
--Trig Jegman - 03:05, 16 October 2021 (UTC)

For an example of a file change, please click "Expand" on the right.

Consult File:KMA Tortletummy Thorn sprite.png

== Summary ==
|description=In-game sprite of [[Tortletummy Thorn]] from ''[[Kirby Mass Attack]]''
|game=''[[Kirby Mass Attack]]''
|source=[ Spriters Resource]

== License ==
{{Game sprite}}
[[Category:Kirby Mass Attack images]]

would move to

|description=In-game sprite of [[Tortletummy Thorn]] from ''[[Kirby Mass Attack]]''
|game=Kirby Mass Attack
|source=[ Spriters Resource]

in order to provide the same exact results.

  1. Sounds good to me. Any changes that make the process of proper file uploading easier for new users in particular gets a thumbs up from me. --Samwell (talk) 03:07, 16 October 2021 (UTC)
  2. Complete support. This is very beneficial, and what catches my eye more is both the auto placement of unsourced files and, on top of everything, the auto Categorization in general. -Kirbeat (talk) 04:35, 16 October 2021 (UTC)
  3. Simpler is better, especially for new users. ---PinkYoshiFan 10:59, 16 October 2021 (UTC)
Neutral Comments



A couple of issues I'm foreseeing:

  • Automization with "|game=Kirby's Game" doing ''[[Kirby's Game]]'' [[Category:Kirby's Game images]] will work only for games, so aside from linguistics, this is why I think "|media=" should be a separate field. Not all media will have pages and categories (that work the same way).
  • Pipe links are impossible.
  • When an image comes from multiple games (e.g. KNiDL, KaTAM and KSqS) - although additional categories can be added manually.
  • License parameters (e.g. {{Game screenshot|official}}) and multiple licenses (e.g. {{WikimediaImage}} + {{PD}}).

There might be more, so clean automization is hard, unless we introduce more parameters. ⁠–⁠Vipz (talk · edits) 11:58, 16 October 2021 (UTC)

Back from my trip. I agree that perhaps having a secondary |media= that does not cause an automatic link may be useful, but would suggest we emphasize using |game= when most possible. Secondarily, I cannot necessarily think of an appropriate reason to have a piped link for a game title. Anything that is a deviation from a full game name seems like it would qualify as an inaccuracy. At the absolute worst, |media= would solve that. If an image comes from multiple games, I would suggest simply using |description= to list other included games and writing in more categories. I think that multi-game files would be exceedingly rare. Licensing parameters would be able to be changed to be their own separate variable switch. The way the template works is by using a different, all-encompassing switch template to change the file license instead of having several dozen templates so one parameter could just become |type=Screenshotofficial or something similar. As for multiple licenses, I do not forsee {{WikimediaImage}} being necessary if we are specifically listing the source out, though once again another parameter could be added for a Wikimedia+PD parameter if absolutely needed. Trig - 00:29, 18 October 2021 (UTC)

Template WIP

While not fully complete, User talk:Trig Jegman/Sandbox here is a rough draft of how the template will function including the requests made above/on Shiver Star. Trig - 21:07, 19 October 2021 (UTC)

Proposal Archive

Successful proposals
Failed proposals