#{{User|Stonehill}} Per proposal as this would prevent from cluttered image change logs.
#{{User|Stonehill}} Per proposal as this would prevent from cluttered image change logs.
#{{User|BabyLuigi64}} Per proposal.
#{{User|BabyLuigi64}} Per proposal.
#{{User|Toads Forever!}} It would mean that Users wouldn't just change (for example) a .gif (animated file) to a .png (solid picture)
====Oppose====
====Oppose====
Revision as of 14:39, March 5, 2015
Current time:
Wednesday, May 8th, 06:29 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.
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
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}}.
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.
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.
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.
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.
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.
No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
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.
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.
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.
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.
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.
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.
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.
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.
Proposals cannot be made about promotions and demotions. Users can only be promoted and demoted by the will of the administration.
No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
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: "May 8, 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".
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.
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}}.
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:
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.
The talk page proposal must pertain to the article it is posted on.
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.
Consider Beanies and Octoombas to be related to Goombas rather than direct variants of them (for consistency with Galoomba et al.) (discuss) Deadline: May 10, 2024, 23:59 GMT
Split "Baby Fat" from Baby Yoshi (discuss) Deadline: May 10, 2024, 23:59 GMT
In Template:Species infobox, expand "Relatives" guidelines to include variant-type relationships with significant differences between species (discuss) Deadline: May 12, 2024, 23:59 GMT
Seeing how Bulbapedia does things, I came up with a cool idea. Maybe we should create a template that should state whether this image is animated. It's purpose? To explain that some browsers are limited to viewing only the first frame of animated images and kindly remind users (especially new users that use old and worn-out browsers) not to change the image, even if it's not moving at all (unless there's really a problem, in which someone good at animated images can help).
Toads Forever! (talk) It would mean that Users wouldn't just change (for example) a .gif (animated file) to a .png (solid picture)
Oppose
Comments
The idea makes sense, but the template must be consistent in design with other image notices, such as {{MapImage}}, {{Award-image}}, {{BJAODN image}}, etc. Having the whole "if the Goombas aren't moving" explanation also seems unnecessary: just say something like "This image is animated; please do not reupload it as a static image." and maybe an additional note that some brows might erroneously display it as already being a static image, but either way, be succinct. - Walkazo (talk)
As long as the image doesn't look like crap, it can be whatever (of the two, I'd say the SMB Goomba looks better). But there should only be one image. And again, I still think the "if the Goombas aren't moving" caveat is unnecessary (and it's unnecessary on Bulbapedia too), since even folks who see movement shouldn't reupload static versions of the image, and either way, simpler is better. The excessive !s are also less than ideal and Help:Image has nothing to do with the issue so there's no point in linking to it. Right now, I would suggest this as the design:
This is an animated image. However, it may not display properly on certain browsers and devices. Please be careful to not re-upload it as a static image by mistake.
"To explain that some browsers are limited to viewing only the first frame of animated images and kindly remind users (especially new users that use old and worn-out browsers) not to change the image"
Which browsers don't support animated images? I think most popular browsers (FireFox and Internet Explorer and maybe Safari) supports the basic animated .gif image. Finally, for the notice template, it would be better if the image included has transparency instead of a white background, but it's just my opinion. It's me, Mario! (Talk / Stalk) 18:30, 4 March 2015 (EST)
The Evotag example Stonehill provided actually doesn't work on Chrome without an extension (but it works in Firefox; dunno about IE), and afaik mobile devices often can't load GIFs. Anyway, I agree about the image: I couldn't do anything before since I was at school, but now that I'm home, I reuploaded it as a transparent GIF. - Walkazo (talk)
Walkazo, the gif has an incorrect frame of animation. Just pointing that out for you. Ray Trace(T|C) 23:23, 4 March 2015 (EST)
Yeah, sorry, it saved with the wrong layer mode by accident. It should be better now, but the revisions haven't refreshed for me here or on the file page so I can't tell for sure yet. - Walkazo (talk)
Miscellaneous
Remove extraneous Super Smash Bros. conversations from articles' main body
The title's unwieldy, but this proposal is specifically covering the Snake's codec conversations and Palutena's Guidance conversations. These conversations are charming bits of dialog between Snake/Pit and their advisers, providing tidbits and small background information on whichever character they're talking about. However, these conversations really don't provide anything groundbreaking, usually saying things that aren't relevant or would have already been mentioned, and yet, all articles have the Snake conversations and the Palutena ones are steadily being added as well. There's really nothing substantial that they're adding; right now, all they're doing is contributing to the mass of headers within the Smash sections. At best, they should be relegated to the articles' "Profile and statistics" headers or they should be removed entirely and kept to the lists I linked to above.
Proposer: Time Turner (talk) Deadline: March 9, 2015, 23:59 GMT
Move convos. to profiles and statistics
Time Turner (talk) I'd say that the conversations are roughly comparable to the trophies; neat information, but it's probably best to leave it outside of the main body.
Baby Luigi (talk) Yeah I was exactly thinking that they should belong under "profiles and statistics" before you mentioned it. I disagree that they "don't provide anything groundbreaking", they're interesting tidbits from an easter egg from the game, they don't necessarily have to be groundbreaking or be relevant or whatever to warrant a space here in MarioWiki. Move them to profiles and statistics, that's what they really are.
Mario (talk) I was about to suggest replacing it with a link, but that would be unnecessary. Per all.
Walkazo (talk) - Per all. The info's definitely comparable to official bios, and the less SSB subheaders cluttering up the History sections, the better.
Toadbrigade5 (talk) - Eh. I don't care as long as the wiki keeps the information somewhere, but I'd rather this than the one below, so I'll support here to just break a tie if there ever is one.
Tails777 (talk) I kinda liked them the way they were, but the proposal is a pretty good point and makes sense so per all.
Megadardery (talk) Per all, but not removing them from the article entirely, but move them to the 'Profile and statistics' section.
Stonehill (talk) Per all. Yes, all. Every single one of them. Not a single one left. However, I'm also suggesting we could move the conversations to their own article and edit other pages accordingly. Per all anyway.
Remove convos.
Keep convos.
Comments
@Baby Luigi: I'm not saying that they don't have a place on the wiki, I'm just saying that their place isn't necessarily in the articles' main body. Hello, I'm Time Turner.