MarioWiki:Proposals

Proposals can be new features (such as an extension), removal of a previously added feature that has tired out, or new policies that must be approved via consensus before any action(s) are done. Any user can support or oppose, but must have a strong reason for doing so, not, e.g., "I like this idea!" "Vote" periods last for one week. All past proposals are archived. A proposal section works like a discussion page: comments are brought up and replied to using indents (colons, such as : or ::::) and all edits are signed using the code {{user|User name}}. Signing with the signature code ~~~(~) is not allowed due to technical issues. How To Actions that users feel are appropriate to have community approval first can be added by anyone, but they must have a strong argument. Users then vote and discuss on the issue during that week. The "deadline" for the proposal is one week from posting at: Monday to Thursday: 17:00 (5pm) Friday and Saturday: 20:00 (8pm) Sunday: 15:00 (3pm) Every vote should have a reason accompanying it. At any time a vote may be rejected if at least three active users believe the vote truly has no merit or was cast in bad faith. However, there must be strong reasons supporting the invalidation. "# " should be added under the last vote of each support/oppose section to show another blank line. Any proposal that has three votes or less at deadline will automatically be listed as "NO QUORUM." The original proposer then has the option to relist said proposal to generate more discussion. All proposals are archived. The original proposer must take action accordingly if the outcome of the proposal dictates it. If it requires the help of a sysop, the proposer can ask for that help. Proposals can not be made about System Operator promotions and demotions. Sysops can only be promoted and demoted by the will of Bureaucrats. There shouldn't be proposals about creating articles on a underrepresented or completely absent subject, unless there is major disagreement about whether the content should be included. To organize efforts about completing articles on missing subjects, try creating a PipeProject. The times are in EDT, and are set so that the user is more likely to be online at those times (after work/school, weekend nights). If a proposal is added on Saturday night at 11:59 PM EDT, the deadline is the next Saturday night at 8:00 PM. If it is a minute later, the deadline is a day plus 15 hours (Sunday), as opposed to a day minus 4 hours. CURRENTLY: 04:57, 24 December 2024 (EST) New Features Template Reorganization Guide I think we need a guide called "MarioWiki:Navigation Templates" in order to fully understand the actual purpose of navigation templates. Many of our nav templates are useless, huge, or otherwise poorly designed, (be it clunky, having colors that are rather blinding, etcetera). (I've made quite a few of those, back in my n00by days. :P) So, please bare with me as I try to tackle all I think should be changed with nav templates. (I'm pulling some of this from Talk:Dragon Wario for further reference.) I feel navigation templates are a vital part of this wiki. Not only are they important aesthetically, but they also help people navigate from one page to another easily. The problem is, not all of them are really organized well, and make navigation hard, rather than easy. I feel the following rules should be set in stone: 1) All navigation templates should be collapsible completely. This means all the way down to one row. Then, said templates should be reorganized in an easy to navigate manner, be it by alphabetizing it's contents, or by grouping them together and alphabetizing them. (That's my favorite way to do it, as you can see with many of my later templates.) By doing so, navigation templates take up exactly the same amount of space, but can be enlarged with the click of a button to find exactly what you're looking for. Though this can slow down some computers considerably, a way around that is to conceal navigation templates on articles with many of them. (Ex: Mario, Bowser, Princess Peach) I have tested that with putting the showhide feature on a page in order conceal many navigation templates, they bog down browsers hardly at all. 2) All navigation templates should refer only to any one of the following: Game-specific templates — when making a template based on one game, you should break it down into four main sections: Locations, Items, Enemies, and Bosses. Other sections can be added if necessary. (Examples are {{SM64}}, {{SMB2}}, and {{Super Mario Bros.}}.) Series-specific templates — this should mainly be used to target an entire series of games with one common feature. This one feature would be broken down into its appearance within each game in the series. (Examples are {{Racecourses}}, {{MP}}, and {{Boss}}.) Species-specific templates — this should only be used with enemies with a large amount of species, as well as a reasonable amount of characters based on said species. (Examples are {{Goomba}}, {{Hammer Bros.}}, and {{Spinies}}, and even {{Dragons}}.) Item/Object-specific templates — this should only be used in order to group items or objects of similarity into one template. This would also refer to terms and such found throughout games. (Examples are {{Mushrooms}} and {{Crystalstar}}, as well as {{Golfing Terms}} and {{References}}.) Character-specific templates — this would refer to a series of characters that have a solid link proven between them. (An example is {{Star Spirits}}.) Having said all that, I feel that this policy would enforce a regulation between all navigation templates, making thinks perfectly synonymous. I will require the help of others to help put this policy fully in place, as it is a huge load. (And I may become inactive soon, but I'm not 100% sure. So please don't think that I've purposely left the place because I didn't want to tackle the burden!) Proposer: Stooben Rooben (talk) Deadline: February 9, 2009, 17:00 Support Stooben Rooben (talk) - Per my reasons above. Mario3v (talk) - Ok I see, Per Stooben. Walkazo (talk) - Per Stooben. This is long overdue. Stumpers (talk) - Perfect - can't wait to see how it turns out! Coincollector (talk) - See my comment... Dom (talk) - Per Stooben's long, informative and very accurate explanation (as usual). Tucayo (talk) *yawns* Per Stooby Bloc Partier (talk) - Aye. Per Stoobs. Canama (talk) - Per all! Super-Yoshi (talk) Yes, per St00by. Some templates are just messed up. RAP (talk) - Per the wiki world of the people who voted teh "support" option. ;o Yoshi Boo 118 (talk) Per All. JerseyMarioFreak (talk) I'll have to agree per myself, it sounds helpful Oppose Comments How is "{{Fire}}" a species? It seems if we allow something like that, we open up the doors to templates like Undead and Fish and anything else related to a type of creature, as opposed to an officially named species. -- Son of Suns (talk) My bad. I forgot to add the last section of the proposal when editing that comment I made on Talk:Dragon Wario. It's fixed now. Stooben Rooben (talk) What does that mean though? Element-specific templates? "Elements" (be it Earth, Wind, or Oxygen) have never played a strong role in the Mario series. What does Element mean anyways? Would a "Metal" template be appropriate for all Creatures and Characters made of the Element Metal? That part of the proposal seems the most flawed and will just replicate the poor templates we already have. Element templates appear to be "useless" (not related to any official concept unlike the other templates), "huge" (can be filled basically indefinitely - is Mario a fire character cause he can shoot fireballs? - there is no way to establish a clear boundary between what is and what is not "related to fire) and "otherwise hideous." -- Son of Suns (talk) Okay, the "hideous" part was kinda harsh, so I reworded that. About the element-specific templates: from what I read in my dictionary, "elements" refers to earth (being of rock and/or metal), water and fire. "Air", or any of its variants, were never mentioned as being an element; neither was anything else. Ice is the same as water, only frozen. However, I looked up the aforementioned terms on Wikipedia and some of its cited sources, and it didn't mention any of them as being an "element". Merriam-Webster has failed me again. Only because the term "element" can refer to "any object that is used in the creation of something", as I read on one of Wikipedia's citations, I am removing that part of the proposal. The definition I have of "element" is poor, and I apologize for trying to implement it into the wiki. I do, however, feel that the other template categories I mentioned are specific and have a strong enough definition to stay in place. =) Stooben Rooben (talk) I believe the concept of "Elements" came from the Greeks and the Chinese (independently). The Greeks said everything was made of four elements (Water, Fire, Earth, Air/Wind). Indeed, I believe it took time for all four categories to actually be developed. The Chinese had a similar system, except Metal was its own independent category. Currently, we have over a hundred elements such as Oxygen, Iron, Gold, Uranium, etc. They are the elements that make up eveything. But anyways...I think the rest of the templates are pretty specific and strong...expect maybe Dragons (although maybe that just needs to be trimmed down to characters and creatures that have actually been called dragons, as opposed to creatures that kinda look like a dragon...a lot of those creatures actually look like seahorses). But yeah, the other templates seem a lot stronger. -- Son of Suns (talk) I remember the concept of "elements" being brought up in my Greek History class, but it was extremely vague. In all honesty, I wouldn't be surprised if the Greeks and the Chinese introduced the concept to at least part of the world; then, the Romans probably stole the concept, as they seemed to be so notable for doing so. (:P) Right, back on-topic. I feel that some entries in the Dragon template should be dropped, ironically. While I feel the template is useful, it has some questionable entries, (like Blargg and Pinwheel). Other than that, I'm glad you agree that the other templates seem strong! Stooben Rooben (talk) I still say {{Dragons}} (and {{Birds}} and {{Fish}}, for that matter) have worth as navigational tools. They prevent articles from being template-less (and neglected as a result), and they are actually less speculative than one would think (i.e. Bowser's pretty draconian, but he's been left off, whereas the Super Mario Land seahorse-like enemies are there because of their leader, Dragonzamasu). Moving on to my next (unrelated) point, what about templates dealing with specific levels in a game, like {{Galaxy}} and {{YoshiLevels}}? They're too large to incorporate into the game templates, but too usefull as navigation tools to scrap. The Galaxy template also has to do with another possible category: Location-specific templates, like {{Isle Delfino}}. Some of these areas might be able to be incorporated into the games from wence they came, but they are also quite usefull on their own (smaller templates can be easier on the eyes). I love template work, so I'd be more than happy to help out with this whole thing. - Walkazo (talk) I kinda have to agree with what you said about the Dragon/Bird/Fish templates. They are quite useful, and they at least fall under the "Species-specific" category. (Though, I still fell {{Dragon}} needs a little bit of trimming, and maybe {{Birds}} and {{Fish}} could be organized a tad better.) On to point two: Level-specific templates fall right under game-related templates. Usually, levels, (or locations with some game templates), are implemented into the game templates to begin with; but if it makes the overall game template too large, then they should be made into their own template. However, the same wouldn't really apply to Characters, Enemies, or Items from a specific game, as they should always be compiled into the game's main template. Ehh...I'm not real fond of having location templates. It's too hard to say "have location-specific, but still game-specific templates". We've had templates for "Beaches", "Subterranean Locations", and other things, and they really prove pointless. If a template as small as {{Isle Delfino}} is standing on its own, it should be implemented into the main SMS template and done away with. Like {{PiT}}; the locations are small enough to fit into that template without being too large. Stooben Rooben (talk) What about implementing something like Wikipedia's Tnavbar in templates? Also, the Chinese elements are Wood, Fire, Earth, Metal, and Water. However, the names are mostly superficial. They aren't really related to those things. Twentytwofiftyseven (talk) That's completely right. I see many templates rediculously long, just because they contain the same elements as category pages have (an example: Subterranean locations {{sub}}) this really horrible template should be removed because it contains all the links as a category page must need. If that's the case, we are making "shortcuts" from going to category pages and ignore the order for all pages. In accordance to Stoob; for overlong templates, I recently installed the Collapsible function for navigation boxes using javascript. Thus, there is now a simpler way to hide the content of those navigation boxes, as well as preventing some glitches that appeared when used the show/hide function. I'm on a personal project under the name of "Template pipeproject" where I usually check all templates present, making some edits and fixings on them. Coincollector (talk) This is slightly less important, but: Should there be strict regulations on the colours of templates, such as them having to relate to the subject of the template? (Obviously, some subjects would not relate to any particular colour) A while ago I changed the Subterranean Locations template colour from an unfitting blue to a logical brown. Oh, and also: With that template, I Moved it from "Template:Sub" to "Template:Subterranean Locations" because calling it "Sub" looked lazy to me. So should there also be rules that Templates have full titles rather than abbreviations... or is that insignificant? It probably is, knowing my theories... Dom (talk) To respond to Walkazo, Dragon, Fish, and Bird articles would never be template-less, as they will always be in game-specific templates. But perhaps like Dragon, Fish and Bird need some trimming. For example, Craw is in the Bird template, although I don't know if they are explicitly called birds. They are bird-like, but they may not be recognized as birds in-game. -- Son of Suns (talk) CC: I appreciate your support. And I forgot to mention that you found a new way to collapse templates with ease; it makes the task a lot less difficult for us all! 2257: Implementing that onto the wiki may not be a bad idea at all. We'll have to see if it's completely necessary first, but nonetheless it may help. Interesting! I learn something knew every day! Dom: Good points! Generally, template colors should complement each other, as well as the subject they deal with. However, because it'd be too difficult for one to actually decide which colors would be entirely deemed as "subject-specific", I'm afraid that we would just have to edit the templates as we see fit. We can, however, make sure that all templates have good colors that complement each other, rather than a blinding fusion of colors. As for making a rule for specific templates...that would also be pretty hard to determine what's an appropriate abbreviation and what's not. Personally, I feel that the only templates that should have abbreviations are game- and series-specific templates, and those would only use the game's most common abbreviation. (Like Super Mario Bros. 3's is "SMB3", but Yoshi's Safari and Yoshi's Story both share "YS" for their common abbreviation.) -- Stooben Rooben (talk) Wait (double take)...can you simplify this? -Ralphfan (talk) Gladly. Which part would you like simplified? Stooben Rooben (talk) Oh, shoot, what about location templates, such as Template:Kitchenisland? And also, level template. The ones that show all the levels in a certain world, like Template:YoshiLevels. Those are quite helpful. Bloc Partier (talk) I already asked both those questions (and interestingly, we both chose {{YoshiLevels}} as an example). Levels and Locations are going to be incorporated into their parent game unless that'll make the template too large. Therefore, {{Kitchenisland}} would be merged with a Super Mario Land 3: Wario Land template, but {{YoshiLevels}} would stay separate. - Walkazo (talk) Heh, I suppose I could have read the comments before posting. :P My bad. And thanks for the answer. ;) Bloc Partier (talk) Create Good Articles 2.0 Hmmm... how to start? Oh, yes. I'm sure many of you have seen articles that are very good, but not good enough to become a FA (like Luigi's Mansion or Koopa Troopa), so I propose we create a new category called "Good Articles", this will give an acknowledgement (long word) to this articles. In order to become a FA, an article needs to fulfill all of this, so a Good Article will only need to fulfill most of them, excluding points number 7 and 9, and changing the 4000 characters to 2500. Who's with me? Proposer: Tucayo (talk) Deadline: February 10th 2009, 17:00 Create Tucayo (talk) - Per... ME! Mario3v (talk) - Well I guess it would work ok, I see. Per Tucayo. DON'T create Son of Suns (talk) - Instead of arguing about what is a "Good Article," we should focus on getting articles to FA status (which itself is a long process - now imagine if we were having debates about if certain articles are Good, not bad but also not FA level). Also, there are no details for how this system would actually work. Bloc Partier (talk) - Per Son of Suns. If users actually worked on improving articles and making them FA's, it would probably be way better. Super-Yoshi (talk) - Per SoS. There would be no point, an article should just be plain well done to be nominated as an FA. BUt how could you nominate a..GA? JerseyMarioFreak (talk) - Per me. Who to decide that non-lengthy articles, not long because it doesn't have to be, is not a "good article"? The little ones with good, rock solid information should still be considered "good". Debates about what articles good and what's not good is rather dubious. We don't need this. Commentaries In all honesty, this sounds like a pretty good idea. However, before I vote, I'd like to ask a question. Exactly which standards would an article need to meet in order to become a "Good Article"? Stooben Rooben (talk) 1,2,4,6,7 and 11 Tucayo (talk) They have this on wookieepedia. YourBuddyBill (talk) Okay, thanks Tucayo! Stooben Rooben (talk) On Wookiepedia, they have a Good Articles system - but that is only for articles that basically meet all FA requirements except for achieving a certain level of content. Here, that would be the 4,000 characters rule. By Wookiepedia standards, an article that filled all FA criteria except rule 11 would be a Good Article. The criteria Tucayo provided left out rules like must be sourced with all appearances and cannot have an improvement template on the page. So these "good articles" may end up being not very "good" at all. -- Son of Suns (talk) Well, it sounds better like that Tucayo (talk) Might I suggest making "Good Articles" fit the same profile as a FA, with the exception of rules 6, 7, and 9? And change the 4,000 character rule to 2,500 characters? Stooben Rooben (talk) Come again? Ralphfan (talk) Stooby: Sounds good, should i specify that in the proposal? Tucayo (talk) I'd recommend Since it's your proposal, it's up to you. Stooben Rooben (talk) K, done, but it seems that pont 6 is important, so I didnt include it Tucayo (talk) Removals None at the moment. Splits & Merges None at the moment. Changes Nothing at the moment. Miscellaneous None at the moment.