|
|
| Line 2: |
Line 2: |
|
| |
|
| ===List of Talk Page Proposals=== | | ===List of Talk Page Proposals=== |
| *Merge [[5 Gold Coin]] and [[50 Gold Coin]] with [[Coin]] ([[Talk:Coin#Merge 5 Gold Coin and 50 Gold Coin with Coin|Discuss]]) '''Deadline''': January 13, 2016, 23:59 GMT
| |
| *Use {{tem|construction}} only when pages clearly have an informal appearance ([[Template_talk:Construction#Use_the_template_only_when_pages_clearly_have_an_informal_appearance|Discuss]]) '''Deadline''': January 15, 2016, 23:59 GMT | | *Use {{tem|construction}} only when pages clearly have an informal appearance ([[Template_talk:Construction#Use_the_template_only_when_pages_clearly_have_an_informal_appearance|Discuss]]) '''Deadline''': January 15, 2016, 23:59 GMT |
| *Create the page: Drilldigger ([[Talk:Robo-Drilldigger#Create the page: Drilldigger|Discuss]]) '''Deadline''': January 17, 2016, 23:59 GMT | | *Create the page: Drilldigger ([[Talk:Robo-Drilldigger#Create the page: Drilldigger|Discuss]]) '''Deadline''': January 17, 2016, 23:59 GMT |
|
Current time:
Monday, May 27th, 05:09 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
- 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 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 with a margin of at least 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 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
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
- 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.
List of ongoing talk page proposals
- 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 Extended to May 19, 2024, 23:59 GMT Extended to May 26, 2024, 23:59 GMT
- Add a Composers Subsection to Template:Themes (discuss) Deadline: May 28, 2024, 23:59 GMT
- Include Rainbow Coaster & Rainbow Downhill back in the Rainbow Road article (discuss) Deadline: May 28, 2024, 23:59 GMT
- Split the contents of the blimp page (discuss) Deadline: May 28, 2024, 23:59 GMT
- Create a Rewrite-remove template (discuss) Deadline: May 30, 2024, 23:59 GMT
- Decide whether to redesign the Main Page (discuss) Deadline: June 1, 2024, 23:59 GMT
- Consider Spike Top derived from both Buzzy Beetles and Spinies (discuss) Deadline: June 4, 2024, 23:59 GMT
- Merge Iron Cleft with The Iron Adonis Twins (discuss) Deadline: June 6, 2024, 23:59 GMT
- Merge Meat (object) with Meat (discuss) Deadline: June 6, 2024, 23:59 GMT
- Re-merge Frog (Yoshi's Story) with Frog (discuss) Deadline: June 7, 2024, 23:59 GMT
- Move the chef-based recipe lists (such as List of Tayce T. recipes) to game-based ones (discuss) Deadline: June 9, 2024, 23:59 GMT
- Merge the corresponding chef-named recipes (discuss) Deadline: June 9, 2024, 23:59 GMT
- Merge Silver Credit and Gold Credit to Silver Card and Golden Card, respectively (discuss) Deadline: June 9, 2024, 23:59 GMT
- Move Moo Moo back to cow (discuss) Deadline: June 10, 2024, 23:59 GMT
Unimplemented proposals
Proposals
- ^Note: This has yet to be done with with several non–Super Mario fighters who still have their own page; namely, Banjo, Fox, Inkling, Isabelle, Kirby, Link, Mega Man, Pac-Man, R.O.B., Sonic, and Villager.
Talk page proposals
List of Talk Page Proposals
- Use {{construction}} only when pages clearly have an informal appearance (Discuss) Deadline: January 15, 2016, 23:59 GMT
- Create the page: Drilldigger (Discuss) Deadline: January 17, 2016, 23:59 GMT
- Split the sections Attackathlon, Toad Quiz and Lakitu Info Centre into Template:Fakelink and Template:Fakelink (Discuss) Deadline: January 18, 2016, 23:59 GMT
- Split Gold Bar and Template:Fakelink (Discuss) Deadline: January 18, 2016, 23:59 GMT
- Split Banana and Template:Fakelink (Discuss) Deadline: January 19, 2016, 23:59 GMT
- Split Template:Fakelink from Rope (Discuss) Deadline:
December 29, 2015, 23:59 GMT Extended: January 5, 2016, 23:59 GMT, January 12, 2016, 23:59 GMT, January 19, 2016, 23:59 GMT
Writing Guidelines
None at the moment.
New features
None at the moment.
Removals
None at the moment.
Changes
The reason for this is similar to the {{conjecturaltext}} proposal above - when adding a vote or comment on a page that has a prior (usually settled) proposal, you get sent to the equivalent section for the first proposal. Similarly, the section link from RecentChanges will also send you to the wrong section in the same way (in either case, you're sent to, e.g., #Support when the section you're looking for has an anchor along the lines of #Support_2, even though the header is just ====Support====).
It wouldn't have to be long or complicated (e.g., this proposal could have headers of something like "Support/Oppose requiring short detail"/"Comment on requiring short detail"), the point is just for it to be unique on the page (although simplicity of rule-writing means that it would be better to include the first proposal on a page in it). Headers in past proposals wouldn't need to be changed; this would only apply to proposals, including Talk Page Proposals, started after the new policy would come into effect.
Proposer: Reboot (talk)
Deadline: January 17, 2016, 23:59 GMT
Support
- Reboot (talk). Per own proposal.
Oppose
- Walkazo (talk) - Too much screwing around for something as superfluous as where you appear in the page after saving. The Table of Contents brings you to the right header, and when you try to edit, you're in the right section, so there's really no problem. Maybe someday the MediaWiki bug will be fixed, but in the meantime, it's not worth complicating basic header stuff.
- Ghost Jam (talk) Aside from per Walkazo, since the page load bug is a bug, it's not something we can really fix.
- Roy Koopa (talk) Per Walkazo and the comments below. It's a MediaWiki glitch that most likely won't be fixed in the near future. All this does is add unneeded tedium to the process of proposal creation; even though Andymii (talk) does this, it doesn't mean we should all be required to do this. I get that we're trying to work around something the can possibly get very irritating (I actually talked to Porple about it because at that point, I didn't know it was a well known MediaWiki glitch), but like I said, all this rule (for lack of a better word) would do is add unnecessary and unwanted tedium to creating proposals; and besides, the only thing it would really be absolutely necessary for is TPPs because on this page, it doesn't take much effort to go from one proposal to the next, because scrolling from Proposal A over Proposal B to Proposal C does not take much effort at all. To sum up, it really should just be an option, not a requirement.
Ghost Jam: Isn't this what this proposal is all about, though? Circumventing a bug? 
It's me, Mario! (Talk / Stalk) 19:05, 11 January 2016 (EST)
- Exactly. We can't fix it (it's more or less baked in - the only ways to technologically fix it would be [a] prohibit more than one section with the same name on a page by throwing an error when someone tries to save it as such or [b] make section anchors something like a random alphanumeric code with no connection to the actual header text. The former is a more extreme version of what I'm suggesting, and no-one anywhere wants the latter), but we can work around it. - Reboot (talk) 00:42, 12 January 2016 (EST)
- Or just ignore it. It's a minor bug: not worth bending over backwards over and adding another, confusingly fiddly step to proposal-making - one that promotes inconsistency and needless wordiness, at that, which will then look terrible in the archives forever. Both the long-term and short-terms costs far outweigh any benefit from avoiding a glitch that causes a second's worth of inconvenience at a time: we've shrugged and carried on for over 8 years, and we should continue with that path of least resistance. - Walkazo (talk) 01:12, 12 January 2016 (EST)
Miscellaneous
Split the Mario & Luigi and Super Mario RPG consumables into separate articles
Remember back in the day when the word "stub" was thrown around like it was going out of fashion and everything smaller than Bowser's article was a stub? This resulted in a lot of articles being clumped together into one superarticle, which is kind of like Superman if he had to wear Kryptonite. What I want to bring up today involves several articles merged during that period, including Super Syrup, Ultra Syrup, Max Syrup, Super Mushroom, Ultra Mushroom, Max Mushroom, and plenty more (including subjects that were affected long after the merges). Every article that I want to split will be listed in the comments. So, the reason I want to split these articles is because there's no reason for them to be merged in the first place. They're individual items with individual names, individual effects, individual buying/selling prices, and individual locations that the games treat like individuals. In some cases, they even have individual appearances, and no, some items having the same appearance is not enough to keep them merged when everything else about them is different. The clumped articles themselves aren't all that pleasant, trying to hop from several topics in rapid succession when that information would be more easily presented in separate articles. Also, having a bunch of Foreignname templates stacked on top of each other is not good in the slightest. I was one of the people who supported those proposals, but looking back, I simply cannot see how the articles are "clearly not working seperate". In light of the recent splits, I thought this would be appropriate.
Proposer: Time Turner (talk)
Deadline: January 17, 2016, 23:59 GMT
Split
- Time Turner (talk) Per proposal.
- NSY (talk) Per proposal.
- RandomYoshi (talk) – Consistency is key. Per proposal.
- Walkazo (talk) - Per Time Turner.
- LudwigVon (talk) Per proposal.
- Niiue (talk) Per all.
- Bazooka Mario (talk) Should've happened earlier.
- Tucayo (talk) - Per TT.
- Reboot (talk) - Cautious support. I agree with the general thrust of the proposal, but there does have to be a threshold below which two things are similar/minor enough to go on the same page. One-sentence pages, even if notionally complete, don't help anything. (I presume that last sentence doesn't apply to any of these specific splits)
- Baby Luigi (talk) Per all
- Tails777 (talk) Per proposal
Don't Split
Full list:
- Mushroom - Super Mushroom, Ultra Mushroom, Max Mushroom, Mid Mushroom, Bad Mushroom
- Syrup - Super Syrup, Ultra Syrup, Max Syrup
Nuts - Super Nuts, Ultra Nuts, Max Nuts (on a side note, shouldn't it be "Nut"?)- Nut - Super Nut, Ultra Nut, Max Nut
- 1-Up Mushroom - 1-Up Deluxe, Double 1-Up Mushroom
- Drumstick - Hot Drumstick, Fiery Drumstick, TNT Drumstick
- Candy - Super Candy, Ultra Candy, Max Candy
- Any others that I've missed
I'm tempted to thrown in the Peppers alongside this proposal, but they're not quite in the same boat as the other ones. There's also the Mushroom that the Triplets give, which has a completely different effect to a regular Mushroom, but I don't know how the article would be properly identified if split. Hello, I'm Time Turner.
- It most definitely should be Nut instead of Nuts. It shouldn't be renamed right away, but it should be renamed after you've made the different Nut articles. You're allowed to link to just Template:Fakelink even if that would generate a red link.
RandomYoshi(Talk • PMs • C) 20:17, 9 January 2016 (EST)
@Reboot: We're not giving articles to every subject under the angry sun (see: Fan (souvenirs), Lightwand), but the articles that I've listed all have more than enough information to support themselves individually. Hello, I'm Time Turner.
- I'm not sure if I understand the plan for the mushrooms. Is the intention to give the Super Mushroom from the various RPGs its own article(s), or merely move the information around to the existing one? Either way, it should be noted that the Mid/Super Mushroom and Max/Ultra Mushroom had identical Japanese names. It would appear to be another example of a translator – Ted Woolsey in this case – providing one-off separate names which would later be changed or reverted. The mushrooms in Super Mario RPG do heal different amounts of health, but those values are also inconsistent within the Mario & Luigi series itself. Mid/Super Mushroom definitely seems straightforward enough, but there is confusion with the Max Mushroom since it was actually introduced separately from Ultra Mushroom in the Mario & Luigi series, and it performs just like the original Super Mario RPG version in Superstar Saga and Partners in Time. That's not even considering Super Shroom and Ultra Shroom from Paper Mario (albeit colored differently). How does that all work out under this proposal? LinkTheLefty (talk) 03:00, 10 January 2016 (EST)
It's me, Mario! (Talk / Stalk) 19:05, 11 January 2016 (EST)
