MarioWiki:Proposals
|
|
Friday, September 27th, 03:54 GMT |
|
|
Proposals can be new features, the removal of previously-added features that have tired out, or new policies that must be approved via consensus before any action is taken.
|
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, but they may not vote for every option available.
- 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(s) 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.
- If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
- If a proposal reaches its deadline and the first place option is ahead of the second place option by three or more votes, then the first place option must have over 50% support to win. If the margin is only one or two votes, then the first place option must have at least 60% support to win. If the required support threshold is not met, then the proposal is extended for another week.
- Use the {{proposal check}} tool to automate this calculation; see the template page for usage instructions and examples.
- Proposals can only be extended up to three times. If a consensus has not been reached by the fourth deadline, then 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 canceled by their proposer within the first three days of their creation (six days for writing guidelines and talk page proposals). However, proposers can request that their proposal be canceled 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: "September 27, 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
Proposals concerning a single page or a limited group of pages are held on the most relevant talk page regarding the matter. Proposals dealing with a large amount 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
- All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{TPP discuss}}. 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 {{settled TPP}}.
- 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 subject page of the talk page 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.
List of ongoing talk page proposals
- Allow usage of {{Release}} as a generic "flag list" template (discuss) Deadline: September 27, 2024, 23:59 GMT
- Prune "sports" games from Black Shy Guy in line with White Shy Guy and Red Boo (discuss) Deadline: September 28, 2024, 23:59 GMT
- Merge Preying Mantas with Jellyfish (discuss) Deadline: September 28, 2024, 23:59 GMT
- Create article(s) for the SM64DS character rooms (discuss) Deadline: September 30, 2024, 23:59 GMT
- Create an article for the Peach doll from Super Mario RPG: Legend of the Seven Stars (discuss) Deadline: September 30, 2024, 23:59 GMT
- Remove the remaining non-Super Mario "stage gimmicks and hazards" from Super Smash Bros. (discuss) Deadline: October 1, 2024, 23:59 GMT
- Remove non-Super Mario "stage cameos" from Super Smash Bros. (discuss) Deadline: October 1, 2024, 23:59 GMT
- Rename {{Manga infobox}} to {{Publication infobox}} (discuss) Deadline: October 4, 2024, 23:59 GMT
- Merge Play Nintendo secret message puzzles (discuss) Deadline: October 4, 2024, 23:59 GMT
- Merge categories for Donkey Kong Country remakes with their base game's categories (discuss) Deadline: October 5, 2024, 23:59 GMT
- Refer to "King Bill" as "Bull's-Eye Banzai" for coverage in New Super Mario Bros. Wii (discuss) Deadline: October 6, 2024, 23:59 GMT
- Rename Perfect Edition of the Great Mario Character Encyclopedia to Perfect Ban Mario Character Daijiten (discuss) Deadline: October 7, 2024, 23:59 GMT
- Create article for Ally mechanic from Mario Party (discuss) Deadline: October 10, 2024, 23:59 GMT
Unimplemented proposals
Proposals
| Establish a standard for long course listings in articles for characters/enemies/items/etc., Koopa con Carne (ended June 8, 2023) |
| Break alphabetical order in enemy lists to list enemy variants below their base form, EvieMaybe (ended May 21, 2024) |
| Standardize sectioning for Super Mario series game articles, Nintendo101 (ended July 3, 2024) |
- ^ NOTE: Not yet integrated for the New Super Mario Bros. games, the Super Mario Maker games, Super Mario Run, or Super Mario Bros. Wonder
| Expand use of "rawsize" gallery class, Doc von Schmeltwick (ended July 19, 2024) |
| Create new sections for gallery pages to cover "unused/pre-release/prototype/etc." graphics separate from the ones that appear in the finalized games, Doc von Schmeltwick (ended September 2, 2024) |
| Tag sections regarding the unofficially named planets/area in Super Mario Galaxy games with "Conjecture" and "Dev data" templates, GuntherBayBeee (ended September 10, 2024) |
| Create MarioWiki:WikiLove and WikiLove templates, Super Mario RPG (ended September 20, 2024) |
Talk page proposals
| Split all the clothing, Doc von Schmeltwick (ended September 12, 2021) |
| Split machine parts, Robo-Rabbit, and flag from Super Duel Mode, Doc von Schmeltwick (ended September 30, 2022) |
| Make bestiary list pages for the Minion Quest and Bowser Jr.'s Journey modes, Doc von Schmeltwick (ended January 11, 2024) |
| Allow separate articles for Diddy Kong Pilot (2003)'s subjects, Doc von Schmeltwick (ended August 3, 2024) |
| Split Bowser's Flame from Fire Breath, Doc von Schmeltwick (ended September 18, 2024) |
| Split Banana Peel from Banana, Doc von Schmeltwick (ended September 18, 2024) |
| Split truck article into cargo truck and pickup truck articles, Doc von Schmeltwick (ended September 21, 2024) |
| Merge Crocodile Isle (Donkey Kong 64) with Crocodile Isle, Doc von Schmeltwick (ended September 21, 2024) |
List of talk page proposals
Template:TPPDiscuss Template:TPPDiscuss
Unimplemented proposals
Writing guidelines
None at the moment.
New features
None at the moment.
Removals
None at the moment.
Changes
Update the Manual of Style to discourage contractions on the wiki
First of all, I'm aware this proposal might sound pedantic. It's perfectly fine to use contractions in every day speech and writing because it's easier than to use the whole structure when it doesn't matter that much; see, I just did that four times now. However, they do sound unprofessional on a site that is treated as an encyclopedia. Using structures such as "it's" and "don'ts" in main space sentences create the impression of a personal addressing to the reader, much like the use of "you's" would. Therefore, I propose that the manual of style be updated to simply state that contractions are not really welcome on the wiki, and that current instances should be expanded to their full forms when spotted. I'm not saying the manual should downright enforce writing without contractions because that would be a colossal maintanance undertaking. But really, what you do when you contract a structure is basically replace one letter with an apostrophe. I don't think omitting one letter reduces the effort, and frankly, sometimes it's annoying to see that so aggressively put in practice.
Proposer: Super Radio (talk)
Deadline: October 27, 2018, 16:45 GMT
Do it
- Super Radio (talk) This can't, I mean cannot be accepted much longer.
- Syncro263892XL (talk) I agree. It should not be 'Mario can't do it'. It must be 'Mario cannot do it.'
- Toadette the Achiever (talk) As long as it's enforced on the same line as how we already enforce proper usage of italics (see comment below), I'm for this. Per Super Radio.
- Alex95 (talk) - I've been writing like this anyway when it comes to content pages, so I guess I've already agreed.
- TheFlameChomp (talk) I’ve recently been removing some contractions when preforming maintenance edits to articles, so I do not have a problem with doing this.
- Yoshi the SSM (talk) I know we aren't (are not) Wikipedia. However, it does do this. And if it works there, it should work here too. As long as it doesn't effect official contractions (quotes and article titles), I am ok with this. Even though, I am part of the problem thus far. So, I per the proposal.
- Bazooka Mario (talk) *looks forlornly at the glitch pages*
- Doomhiker (talk) This change would definitely improve the overall quality of the writing on the wiki, and saying Donkey kong did not do it sounds a lot better than Donkey kong didn't do it, in my opinion.
- Baby Luigi (talk) Contractions are a type of slang, which already contradict most style guides anyway. Support.
- Niiue (talk) Per all.
- PianoKing03 (talk) I will admit, I fall a bit short of being able to say I support this fully, however I believe I will cast a vote of approval. While it could propose minor problems for those with less integrity in their sentence form, I do believe it can still be put into effect, especially if every change, major and minor, is examined for contractions. It would take quite an effort, but in the end, I do see this significantly improving the appearance of the Wiki’s pages. You have my approval.
Don't
- MarioManiac1981 (talk) While I'm not entirely against this proposal, I feel that, as Super Radio mentioned before, it is huge maintenance to remove contractions, and monitor their use on this wiki. It is somewhat contradictory to enforce a rule against the usage of contractions, because the manual of style uses contractions quite a lot for its explanations. We just need to discuss when contractions will not be tolerated, and when they're just fine to use.
- Scrooge200 (talk) I think contractions are fine. I do agree that they can get out of hand sometimes, but it's better to just fix a few small instances of contraction overdose than discourage contractions entirely.
- WeirdDave13 (talk) Changing vote, as this seems unnecessary.
- MeritC (talk) I seriously do not see why our not being able to use contractions whenever necessary would be unprofessional. The only thing that's a definite standard is not using the word "you" in mainspace articles since this is to be treated like an "encyclopedia site". So I'm voting no here.
Comments
While I certainly agree, I don't think we should draw a hard line on using contractions, just notify users when they use them, like what we already do for users who forget to use proper italics. 
(T|C) 13:01, 13 October 2018 (EDT)
- True, maybe I should have worded my proposal this way... -- -- KOOPA CON CARNE 13:04, 13 October 2018 (EDT)
@MarioManiac1981: The proposal only addresses content in main space articles (Super Mario Bros., Princess Peach, Super Mushroom etc.), not talk pages and project pages, like this one or the guidelines. -- -- KOOPA CON CARNE 15:18, 13 October 2018 (EDT)
@Yoshi the SSM: Don't be so harsh on yourself :) -- -- KOOPA CON CARNE 16:46, 13 October 2018 (EDT)
Miscellaneous
None at the moment.
