MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
(→‎List of Talk Page Proposals: completed it. if you want to replace any other sprite image sizes with 30px in tables, contact me)
(Undo revision 1894130 by Baby Luigi (talk) - not done properly, and let the proposer do it themself)
Line 2: Line 2:


===List of Talk Page Proposals===
===List of Talk Page Proposals===
*Resize the [[Costume Mario]] costumes. ([[Talk:Costume Mario#Proposal: Resize the Costume Mario Sprites revamp|Discuss]]) '''Passed'''
*Revamp the images on the [[Trick]] page. ([[Talk:Trick#Revamp the pix on this page|Discuss]]) '''Deadline:''' October 2, 2015, 23:59 GMT
*Revamp the images on the [[Trick]] page. ([[Talk:Trick#Revamp the pix on this page|Discuss]]) '''Deadline:''' October 2, 2015, 23:59 GMT
*Overhaul the "Aliases" and the "Occupations" sections in the [[Mario]] article. ([[Talk:Mario#Overhaul the "Aliases" and the "Occupations" sections|Discuss]]) '''Deadline:''' October 5, 2015, 23:59 GMT
*Overhaul the "Aliases" and the "Occupations" sections in the [[Mario]] article. ([[Talk:Mario#Overhaul the "Aliases" and the "Occupations" sections|Discuss]]) '''Deadline:''' October 5, 2015, 23:59 GMT

Revision as of 18:24, October 2, 2015

Image used as a banner for the Proposals page

Current time:
Thursday, March 28th, 22:31 GMT

Proposals can be new features (such as an extension), the removal of previously-added features that have tired out, or new policies that must be approved via consensus before any action is taken.
  • "Vote" periods last for one week.
  • Any user can support or oppose, but must have a strong reason for doing so (not, e.g., "I like this idea!").
  • All proposals must be approved by a majority of voters, including proposals with more than two options.
  • For past proposals, see the proposal archive and the talk page proposal archive.

A proposal section works like a discussion page: comments are brought up and replied to using indents (colons, such as : or ::::) and all edits are signed using the code {{User|User name}}.

How to

Rules

  1. If users have an idea about improving the wiki or managing its community, but feel that they need community approval before acting upon that idea, they may make a proposal about it. They must have a strong argument supporting their idea and be willing to discuss it in detail with the other users, who will then vote about whether or not they think the idea should be used. Proposals should include links to all relevant pages and writing guidelines. Proposals must include a link to the draft page. Any pages that would be largely affected by the proposal should be marked with {{proposal notice}}.
  2. Only registered, autoconfirmed users can create, comment in, or vote on proposals and talk page proposals. Users may vote for more than one option on proposals with more than two choices.
  3. Proposals end at the end of the day (23:59) one week after voting starts, except for writing guidelines and talk page proposals, which run for two weeks (all times GMT).
    • For example, if a proposal is added at any time on Monday, August 1, 2011, the voting starts immediately and the deadline is one week later on Monday, August 8, at 23:59 GMT.
  4. Every vote should have a strong, sensible reason accompanying it. Agreeing with a previously mentioned reason given by another user is accepted (including "per" votes), but tangential comments, heavy sarcasm, and other misleading or irrelevant quips are just as invalid as providing no reason at all.
  5. Users who feel that certain votes were cast in bad faith or which truly have no merit can address the votes in the comments section. Users can ask a voter to clarify their position, point out mistakes or flaws in their arguments, or call for the outright removal of the vote if it lacks sufficient reasoning. Users may not remove or alter the content of anyone else's votes. Voters can remove or rewrite their own vote at any time, but the final decision to remove another user's vote lies solely with the administrators.
    • Users can also use the comments section to bring up any concerns or mistakes in regards to the proposal itself. In such cases, it's important the proposer addresses any concerns raised as soon as possible. Even if the supporting side might be winning by a wide margin, that should be no reason for such questions to be left unanswered. They may point out any missing details that might have been overlooked by the proposer, so it's a good idea as the proposer to check them frequently to achieve the most accurate outcome possible.
  6. If a user makes a vote and is subsequently blocked for any amount of time, their vote is removed. However, if the block ends before the proposal ends, then the user in question holds the right to re-cast their vote. If a proposer is blocked, their vote is removed and "(banned)" is added next to their name in the "Proposer:" line of the proposal, which runs until its deadline as normal. If the proposal passes, it falls to the supporters of the idea to enact any changes in a timely manner.
  7. No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
  8. Any proposal where none of the options have at least four votes will be extended for another week. If after three extensions, no options have at least four votes, the proposal will be listed as "NO QUORUM." The original proposer then has the option to relist said proposal to generate more discussion.
  9. All proposals that end up in a tie will be extended for another week. Proposals with more than two options must also be extended another week if any single option does not have a majority support: i.e. more than half of the total number of voters must appear in a single voting option, rather than one option simply having more votes than the other options.
  10. If a proposal with only two voting options has more than ten votes, it can only pass or fail by a margin of three votes, otherwise the deadline will be extended for another week as if no majority was reached at all.
  11. Proposals can only be extended up to three times. If a consensus has not been reached by the fourth deadline, the proposal fails and can only be re-proposed after four weeks, at the earliest.
  12. All proposals are archived. The original proposer must take action accordingly if the outcome of the proposal dictates it. If it requires the help of an administrator, the proposer can ask for that help.
  13. If the administrators deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to remove it at any time.
  14. Proposals can only be rewritten or deleted by their proposer within the first three days of their creation (six days for talk page proposals). However, proposers can request that their proposal be deleted by an administrator at any time, provided they have a valid reason for it. Please note that canceled proposals must also be archived.
  15. Unless there is major disagreement about whether certain content should be included, there should not be proposals about creating, expanding, rewriting or otherwise fixing up pages. To organize efforts about improving articles on neglected or completely missing subjects, try setting up a collaboration thread on the forums.
  16. Proposals cannot be made about promotions and demotions. Users can only be promoted and demoted by the will of the administration.
  17. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
  18. Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.

Basic proposal and support/oppose format

This is an example of what your proposal must look like, if you want it to be acknowledged. If you are inexperienced or unsure how to set up this format, simply copy the following and paste it into the fitting section. Then replace the [subject] - variables with information to customize your proposal, so it says what you wish. If you insert the information, be sure to replace the whole variable including the squared brackets, so "[insert info here]" becomes "This is the inserted information", not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but what each voting section is supporting must be clearly defined. Such options should also be kept to a minimum, and if something comes up in the comments, the proposal can be amended as necessary.


===[insert a title for your proposal here]===
[describe what issue this proposal is about and what changes you think should be made to improve how the wiki handles that issue]

'''Proposer''': {{User|[enter your username here]}}<br>
'''Deadline''': [insert a deadline here, 7 days after the proposal was created (14 for writing guidelines and talk page proposals), at 23:59 GMT, in the format: "March 28, 2024, 23:59 GMT"]

====Support====
#{{User|[enter your username here]}} [make a statement indicating that you support your proposal]

====Oppose====

====Comments====


Users will now be able to vote on your proposal, until the set deadline is reached. Remember, you are a user as well, so you can vote on your own proposal just like the others.

To support, or oppose, just insert "#{{User|[add your username here]}}" at the bottom of the section of your choice. Just don't forget to add a valid reason for your vote behind that tag if you are voting on another user's proposal. If you are voting on your own proposal, you can just say "Per my proposal".

Talk page proposals

All proposals dealing with a single article or a specific group of articles are held on the talk page of one of the articles in question. Proposals dealing with massive amounts of splits, merges or deletions across the wiki should still be held on this page.

For a list of all settled talk page proposals, see MarioWiki:Proposals/TPP archive and Category:Settled talk page proposals.

Rules

  1. All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{TPPDiscuss}}. Include a brief description of the proposal while also mentioning any pages affected by it, a link to the talk page housing the discussion, and the deadline. If the proposal involves a page that is not yet made, use {{fake link}} to communicate its title in the description. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links. Place {{TPP}} under the section's header, and once the proposal is over, replace the template with {{SettledTPP}}.
  2. All rules for talk page proposals are the same as mainspace proposals (see the "How to" section above), with the exceptions made by Rules 3 and 4 as follows:
  3. Voting in talk page proposals will be open for two weeks, not one (all times GMT).
    • For example, if a proposal is added at any time on Monday, August 1, 2011, it ends two weeks later on Monday, August 15, 2011, at 23:59 GMT.
  4. The talk page proposal must pertain to the article it is posted on.
  5. When a talk page proposal passes, it should be removed from this list and included in the list under the "Unimplemented proposals" section until the proposed changes have been enacted.

List of ongoing talk page proposals

Unimplemented proposals

Proposals

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

Talk page proposals

Split all the clothing, Doc von Schmeltwick (ended September 12, 2021)
Split the various reissues of Mario Bros., Doc von Schmeltwick (ended April 22, 2022)
Split machine parts, Robo-Rabbit, and flag from Super Duel Mode, Doc von Schmeltwick (ended September 30, 2022)
Expand source priority exception to include regional English differences, LinkTheLefty (ended January 14, 2023)
Add product IDs in game infoboxes, Windy (ended March 18, 2023)
Remove the list of Super Smash Bros. series objects, Axis (ended May 10, 2023)
Merge Start Dash with Rocket Start, Koopa con Carne (ended August 17, 2023)
Use italics for the full title of the Mario Kart 8 Deluxe – Booster Course Pass, Hewer (ended September 15, 2023)
Split Special Shot into separate articles by game, Technetium (ended September 30, 2023)
Convert the lists of episode appearances for television series characters into categories, Camwoodstock (ended November 22, 2023)
Decide which series certain Yoshi games are related to, GuntherBB (ended December 14, 2023)
Change the Super Mario 64 DS level section to include more specific character requirements, Altendo (ended December 20, 2023)
Replace "List of Game Over screens" and "'Game Over' as death" sections with a "History" section, DrippingYellow (ended December 20, 2023)
Split the Jungle Buddies from Animal Friends, DrippingYellow (ended December 22, 2023)
Make major changes to the MarioWiki:Links page, PnnyCrygr (ended January 10, 2024)
Make bestiary list pages for the Minion Quest and Bowser Jr.'s Journey modes, Doc von Schmeltwick (ended January 11, 2024)
Merge the "Johnson" running gag into one page, Doc von Schmeltwick (ended January 11, 2024)
Merge the ghost Bats and Mice from Luigi's Mansion to their respective organic counterparts from the later games, Doc von Schmeltwick (ended January 20, 2024)
Split Strobomb from Robomb, Doc von Schmeltwick (ended January 20, 2024)
Stop listing reruns of tours separately in the lists of tours in Mario Kart Tour, Hewer (ended February 23, 2024)

List of Talk Page Proposals

  • Resize the Costume Mario costumes. (Discuss) Passed
  • Revamp the images on the Trick page. (Discuss) Deadline: October 2, 2015, 23:59 GMT
  • Overhaul the "Aliases" and the "Occupations" sections in the Mario article. (Discuss) Deadline: October 5, 2015, 23:59 GMT
  • Split Giant Kamek and Kamek. (Discuss) Deadline: October 15, 2015, 23:59 GMT

Writing Guidelines

None at the moment.

New features

Add a 3D render licensing template

We have this proposal for earlier reference. It failed mainly because of legal redundancy. I understand that {{game-sprite}} already covers this issue. Currently, however, 3D renders such as this, this, this, this, this and this are lumped with sprites in this category. This is not good when one of our wiki policies already took pains to distinguish between what's a sprite (including pre-rendered sprites) and a live rendered model. So, the legal argument is not a valid point against creating a template and a category, and it fails to address a more immediate problem, which is an organizational one, in this wiki. This proposal aims to remove this disparity by including a licensing template called {{game-3Drender}} and its content will look like this (embedded categories excluded):

Copyrighted game screenshot This is a 3D render originally from a copyrighted computer or video game, and the copyright for it is most likely held by the company that developed the game. It is believed that the use of a limited number of web-resolution sprites for identification and critical commentary on the computer or video game in question or the copyrighted character(s) depicted on the 3D render in question qualifies as fair use under United States copyright law, as such display does not significantly impede the right of the copyright holder to sell the copyrighted material, is not being used to turn a profit in this context, and presents ideas that cannot be exhibited otherwise. See Copyrights and fair use rationale.

Again, the legal issue is not the main point I'm going for; we need this so we can organize such images into a convenient category rather than awkwardly lumping them with our sprites. Our current way of doing this violates the policy I've mentioned earlier, so taking a step to include a separate category (which will have more than enough entries) would benefit our wiki.

One possible alternate option would be to rename the category, but it would be an unnecessary hassle to rename all of those categories, and it wouldn't help with our organization at all. Again, we're supposed to treat sprites and renders as two separate and distinct entities as outlined by MarioWiki:Good Writing. Otherwise, you might as well just lump everything under {{game-screenshot}} like it used to be before {{game-sprite}} was created in 2011. I think just creating a new one to cover the renders is a far better and consistent option.

There is also another option to simply add a new category but that doesn't solve the licensing by itself, so you have to edit the licensing template to accommodate 3D renders, making it more convoluted than what's being proposed.

We can also go with "3D model" rather than "3D render", but "3D render" is much more precise and not too jargon-y. If there is a sudden call to change from "render" to "model", please let me know.

If this proposal passes, it will overturn the previous proposal and will give us one more drop-down option under licensing when you upload an image.

Proposer: Bazooka Mario (talk)
Deadline: October 3, 2015 23:59 GMT

Support

  1. Bazooka Mario (talk)
  2. Roy Koopa (talk) Per proposal
  3. Niiue (talk) Per all.
  4. Baby Luigi (talk) please for the love of god yes, i keep asking for a licensing template that would differentiate between two clearly-wouldn't-be-more-different things
  5. Tails777 (talk) They are two different things. I agreed to making a separate licensing template back in that previous proposal. So heck yeah this is a per proposal.
  6. Megadardery (talk) Per all. Even though the trouble that will arise from this is not little, it is clear that sprites are not models. "3D render" also sounds a lot better than plain "model".
  7. The Pyro Guy (talk) Per all.
  8. Andymii (talk) Per all.
  9. RandomYoshi (talk) – Per all.

Oppose

Comments

Megadardery: "Even though the trouble that will arise from this is not little[...]". Elaborate? I don't think this will cause any problems other than a little reorganization, but it's not like we haven't done this before. Icon showing how many lives Mario has left. From Super Mario 64 DS. It's me, Mario! (Talk / Stalk) 15:24, 27 September 2015 (EDT)

Pretty much the "surfing the wiki and finding all 3D models" is what comes to my mind. Plus the fact that few users would not notice this proposal, and continue marking models as sprites. Plus the fact that some users would still confuse some 3D renders as sprites (NSMBDS comes to mind). It's an inconvenient to say the least.--
User:MegadarderyUser talk:MegadarderyDashbot signature
12:00, 28 September 2015 (EDT)
Well, that's not stopping us from at least making an effort to reorganize the renders. We've made drastic wiki organizational changes before, such as removing "beta" and "sub-species" terminology. Sure, users will probably categorize renders from sprites, but it's not different from any other type of bad categorization, poor formatting, or even bad grammar. Hell, it's why we have this section in policy. We can't just leave them like that. Icon showing how many lives Mario has left. From Super Mario 64 DS. It's me, Mario! (Talk / Stalk) 20:40, 28 September 2015 (EDT)
Which is basically why I'm supporting.--
User:MegadarderyUser talk:MegadarderyDashbot signature
12:16, 29 September 2015 (EDT)
I don't even know if nsmbds uses sprites or prerendered models. Some enemies are clearly sprites. Even the player models have frames ripped in the spriters resource. BabyLuigiFire.png Ray Trace(T|C) 19:22, 29 September 2015 (EDT)
Well, they're still technically renders, but I'll give the benefit of doubt and say that Mayro, Loogie, Pitch, Bowz, and Junior are 3D renders. Icon showing how many lives Mario has left. From Super Mario 64 DS. It's me, Mario! (Talk / Stalk) 19:35, 29 September 2015 (EDT)

Removals

None at the moment.

Changes

Make location infoboxes more appropriate for buildings as well

I propose us to make location infoboxes more fitting to articles on buildings. That is because the current one uses the terms greater location, ruler and inhabitants, which seem more suitable/common for regions. We could create a switch to a "building" option, that would switch:

  • Greater location to Location;
  • Ruler to Owner;
  • Inhabitants to Residers.

Proposer: Mr. Ice Bro. (talk)
Deadline: October 4, 2015, at 23:59 GMT.

Support

  1. Mr. Ice Bro. (talk) Per my proposal.
  2. Niiue (talk) Per Mr. Ice Bro. (Though I'd advice changing "Residers" to "Residents").
  3. The Pyro Guy (talk) It makes a lot of sense to do so.

Oppose

  1. Roy Koopa (talk) Very vague. Good idea, but too vague.
  2. Walkazo (talk) - Simplifying "location" is a good idea, but it would be a mistake to make the other two changes: I'd rather "owner" be added instead of replacing "ruler", and "inhabitants" works perfectly well for both types of places.
  3. Pseudo-dino (talk) Per Walkazo.
  4. Warioad (talk) Per Walkazo.
  5. SuperYoshiBros (talk) Per Walkazo.

Comments

Changing "greater location" to "location" would make sense either way, but "inhabitants" already works for buildings, so I think that one should be left alone. Also, while "ruler" indeed doesn't work for buildings, "owner" would sound awkward for countries and whatnot, so why not just make both variables usable? "Ruler" is already optional, so just add "owner" as a different optional variable, and then both types of situations are covered. - Walkazo (talk)

Roy Koopa: If it's too vague, then what parts of the proposal do you think needs elaboration? Also, I agree with Walkazo, just add more if parameters into the infoboxes. This probably doesn't even need a proposal for such an inconsequential change. We don't need a new infobox, just add it to "location". Icon showing how many lives Mario has left. From Super Mario 64 DS. It's me, Mario! (Talk / Stalk) 15:27, 27 September 2015 (EDT)

It's vague because the only reasoning is "this is bad we should change it to this." File:RoyNSMBU.png Roy Koopa 18:37, 28 September 2015 (EDT)
The propositions seem to be fairly specific though, but I do think elaboration is needed for why these propositions are needed, but inferring from the propositions and proposal titles, it seems to be apparent. That "location" as it's currently used also covers "buildings", which is pretty awkward. Icon showing how many lives Mario has left. From Super Mario 64 DS. It's me, Mario! (Talk / Stalk) 20:22, 28 September 2015 (EDT)

I don't know. Some things work in this proposal, others don't. I personally think Walkazo's idea is the best. I'm not voting yet either way as of now. Magikrazy (talk)

Miscellaneous

None at the moment.