MarioWiki:Proposals

Implement the ability to remove support votes in nominations for featured articles
After seeing that people can't remove support votes in featured article nominations...why is this necessary? If we can remove both support and oppose votes in unfeatured article nominations, then why can't we do the same for featured article nominations? After all, no matter what, all you're really voting for is whether the article should be granted featured status or if it should be unfeatured, so being only able to remove oppose votes in featured article nominations sounds inconsistent.

In the policy page, the rule will look like somewhat approaching this:

''Users may vote for the removal of a support/oppose vote if they feel it is invalid or not specific enough, but have to give reasons for their choice. Three users, including an administrator, are required for the removal of a support/oppose vote. This is how it should look like:''

==== Removal of support/oppose votes ==== Name of a specified user
 * 1) Reasons the support/oppose vote should be removed

''After the required amount of votes is met, users must wait 24 hours before removing the vote. Any vote that has per'd without providing any additional reason will also be removed.'' Proposer: Deadline: January 28, 2018, 23:59 GMT

Support

 * 1) It doesn't hurt to be consistent on the wiki.
 * 2) After seeing your recent edit be reverted on the Super Mario Run Nomination page, I was just about to propose this myself. Implementing this would only enforce consistency and weed out any illegitimate votes. I'm not looking to single anyone out, but the two support votes on the current Super Mario Run nomination are not legitimate and should not be allowed to stay. This new system would be implemented to strictly remove any support votes that shouldn't be there. Why let them stay if we all agree that there has been cases as mentioned. Per Lcrossmk8 and my comments below.
 * 3) Because of what just happened, once this passes, any support votes that don't follow rules would get vaporized with the removal feature. Per all.
 * 4) Per all.
 * 5) If the nomination only has one support vote, then that vote carries weight. If that vote is being held up with faulty reasoning, then I see no reason to keep it there. Per all.
 * 6) There's really no reason not to do this. If the only support vote is clearly invalid then it should be able to be removed. We shouldn't have to wait out the process if the whole nomination is invalid.
 * 7) Per all.

Oppose

 * 1) &mdash; The reason that the wiki does not allow for the removal of support votes from Featured Article nominations is that such a process would not have a real impact on the progress of the nomination. The job of the support is not to outnumber the opposition by a particular margin; rather, it is to completely satisfy any legitimate concerns that the opposition might have. Even if one hundred people flooded in with illegitimate support reasons, one oppose vote would disallow the nomination from being passed. Because oppose votes hold much more weight than support votes and are difficult to remove if they are justified, it is pointless to design a process to remove illegitimate support votes. Additionally, the comparison of FA support votes to Unfeature support votes falls flat when one considers that they are inherently different; whereas the burden falls on the support to pass a Featured Article nomination, the burden falls on the opposition to fail an Unfeature nomination. This means that in the Unfeature process, support and oppose votes are more equal in importance and must both be backed by strong reasoning for the process to actually work.
 * 2) - Per SMB. Support votes are moot if there are any opposes anyway.
 * 3) Per SMB and Alex.
 * 4) Do we actually have to do this?  It seems useless.  Standard proposals do not work the same way as FA nominations.  Per SMB.
 * 5) Was originally going to support, but didn't know that a Feature nomination failed with any number of opposes, so per all.
 * 6) Per SMB.

Comments
This doesn't hurt anyone either. If we can remove opposition we should have the same guidelines to remove supports. Good idea.

You need to create a draft for writing guidelines. 17:22, 14 January 2018 (EST)
 * ^Before anyone else votes, the proposal should be drafted so we know what this new guideline would look like. 17:30, 14 January 2018 (EST)
 * To clarify, you need to include a draft of what the rule will look like in the policy page. 17:51, 14 January 2018 (EST)
 * May I suggest instead of saying "not specific enough" in your draft change in to something like "insufficient." I feel that word is used better to describe it.

@SMB: We do have a process to remove any kind of fan vote, support or oppose, so it's not an entirely novel concept. Also, I'd say that support votes can carry weight if they convince other users to support it regardless of any erroneous reasons, and the users then proceed to spend their time arguing with the opposers rather than anything productive. 19:04, 14 January 2018 (EST)
 * @Time Turner: I overlooked that and modified my vote to reflect the policy change. Even still, the reasoning applies to any other sorts of illegitimate or poorly-supported support votes. Of course, support votes can carry a symbolic weight if they are well-constructed, but that does not change the fact that when it comes down to pure policy, an oppose vote has much more weight than a support vote. 19:14, 14 January 2018 (EST)
 * I don't disagree that a single oppose vote does more than any number of support votes, but personally, it feels weird to allow poorly constructed votes to stay just because they're not strictly impacting the nomination. They could contain false or just plain bad information and reasoning, and you yourself brought up the potential symbolic weight of them. Even if they're worth a single drop of a near-full bucket, I don't want to disregard it, because that still means that it constitutes something. 19:20, 14 January 2018 (EST)
 * Eh, it sounds like the burden falls on the opposition to fail both featured and unfeatured article nominations. And also, @SMB, the removal of support votes does have as much impact on the progress of the nomination as much as the removal of oppose votes, especially in most of the cases when you see only one reason being given by the first voter and everyone else giving it a "per all" secondary vote. It happens in both support and oppose votes. The burden falls on the supporters to support the nomination and the opposition to fail the nomination in any nomination. After all, what's the point of voting in the first place if there is no burden on your side? 19:22, 14 January 2018 (EST)
 * Regardless of how many support votes there are, if there's even one oppose vote, then the feature nomination won't matter anyway. There's no need to have a "Removal of supports" because voting against the nomination does more than enough already. 19:47, 14 January 2018 (EST)
 * @Time Turner: I also don't disagree that faulty support votes constitute something; rather, I believe the process already handles these situations adequately by virtue of giving a single opposition vote more weight than any amount of support votes. If the support offers weak arguments, then the opposition will simply have a strong counterargument. It is then up to the support to revise its standpoint or edit the article to eliminate these concerns. The process is designed to handle the very concern that the proposal attempts to combat.
 * @Lcrossmk8: The burden absolutely falls on the support in the case of Featured Articles. A single support vote will not make a technical difference as long as the FA nomination meets the five vote threshold; however, a single oppose vote will completely stall the nomination from being accepted. The opposition does not have to make any real attempt to improve the article for their viewpoint to be officially accepted, whereas the support must address the concerns of the opposition if they want the nomination to succeed. Of course, there is some sort of "burden" on both sides; however, the process heavily favors the opposition, which means the support must work harder to succeed in their goal. 19:57, 14 January 2018 (EST)
 * And for some reason, oppose votes don't face the same burdens? If the opposition doesn't want the nomination to succeed, then it's up to them to give all legitimate reasons as to why the support is wrong and the nomination should not succeed. It's not that complicated for any nomination, both the support and the opposition must give legitimate reasons as to why their side is right. You can say that more support votes don't make a difference in the progress of the nomination, but I can turn that around and say the exact same thing for the oppose votes: more of them don't make a difference in the progress of the nomination. The opposition must have legitimate reasons to not support the nomination for featured articles, because there is absolutely no point to them voting at all if they don't give good enough reasons. After all, my point is this: why are you voting at all if you don't have any burden to support or fail the nomination? 20:17, 14 January 2018 (EST)
 * Oppose cancels support. End of story. - 20:26, 14 January 2018 (EST)
 * It's unnecessary to have the oppose votes cancel the illegitimate support votes. This is about consistency and balance. Support can cancel out oppose. 20:29, 14 January 2018 (EST)

Support does NOT cancel oppose. That's why we have "removal of support". - 20:32, 14 January 2018 (EST)
 * Exactly my point. You just proved my point right there. That's what we should have. 20:36, 14 January 2018 (EST)
 * Uh, no. I meant to say "removal of oppose".  You might call it a typo.  But a "removal of support" is pointless. - 20:56, 14 January 2018 (EST)

@all opposers: I think you're all looking too deeply into this. Yes we understand that oppose votes carries a lot of weight against support votes, understandably. But you're all acknowledging that in some cases, there are support votes that really shouldn't be there. I think this new system will force any vote, regardless of support or oppose, to have legitimate reason. You're all acknowledging that there is a problem sometimes with faulty support votes, so why let that continue? Force the voters to put thought and dedication into their votes, instead of illegitimate ones that, frankly (and bluntly) stick out like a sore-thumb.
 * Well, fan votes can be deleted on sight anyway. - 20:33, 14 January 2018 (EST)
 * @Lcrossmk8: The burden of proof is on the support side to demonstrate why an article should be featured. The reason for this is quality control: by design, it is harder to feature an article and easier to prevent its being featured. That is why opposition is tasked with providing legitimate reasons for opposing. You cannot say that more oppose votes don't make a difference, because that's simply wrong: more opposition votes do make a difference in the progress of the nomination, provided there are a variety of concerns with the article. No matter how many reasons there are to support an article being featured, just one point against it can derail the nomination; two or more reasons to oppose absolutely creates more roadblocks to the nomination passing. Also, it is not unnecessary to have an oppose vote "cancel" illegitimate support votes (which is not the term I would use... "counteract" would be better in this case), it is literally what the system is designed to do. Support absolutely cannot cancel out opposition, because the system is skewed toward the opposition for quality-control reasons.
 * @DKPetey99: There is no "problem" with faulty votes. As I said above, the system is already designed to deal with the circumstance. The voters will be forced to put thought and dedication into their votes when they get met by a well-supported opposition vote. 20:38, 14 January 2018 (EST)
 * Well I feel this proposed system furthers that principle for the better.
 * @SMB, and the burden of proof is on the oppose side to demonstrate why an article should not be featured. In theory, you might be right about more oppose votes making a difference, but in reality, all I see is the first oppose voter giving the reasons for why the article should not be featured and everyone after him or her just saying "per all", and once the issues get fixed, why should the oppose votes be there anymore? All it really shows is how inherently weak the oppose side can really be at times. And plus, why just keep the support votes there if they are not legitimate? It's the same with oppose votes--if they are not legitimate, then get rid of them. If you look at it, there's a clear reason why I designed the system to be exactly like the system used to get rid of bad oppose votes. 20:46, 14 January 2018 (EST)
 * Nobody is arguing with removing opposition votes if the initial concerns have been remedied. Just because a concern has been fixed does not mean it was "inherently weak," it means that the support actually rose to the occasion and improved the article. The main responsibility of the opposition is to critique and suggest improvement, whereas the main responsibility of the support is to act on these suggestions to ensure article quality. In the end, it does not matter why the supporters want the article to be featured; the implied idea behind supporting is that they believe it meets the requirements set out for featuring and that they will take action to ensure it gets featured. It absolutely does matter, however, why the opposition votes the way they do; their job is to critique the article and control the quality of the FA process. That is why their vote is given much more weight and power, and why they are more accountable for their votes; on the other hand, that is why the support is not held as accountable for their vote, but must produce results if there are legitimate concerns with the nomination. 21:18, 14 January 2018 (EST)
 * And with the implementation of this feature, does this mean that the power of the oppose votes will be diminished? Not really, all it does is ensure that the support votes are making sure that they are sure in what they want and that they are being entirely legitimate in their reasons for wanting the article to be featured--it does matter why they want the article to be featured, because what they say will reflect off of the quality of writing on the wiki as much as the oppose voters' criticism will. In other words, we are holding these support voters more accountable for their actions. That is exactly what we need to see here on this wiki, and plus, we cannot give the constructive criticism of the oppose voters more power and weight than the positivity and idealism of the support voters. Both positive feedback and negative feedback are of equal importance, and with the ability to remove support votes, we are basically saying that we will hold the support voters to the same standard we hold the oppose voters to. Also, this is going to hold the entire wiki to a higher standard, because if people want more articles to gain featured status, then they are going to have to work harder to make the articles and the content more high-quality and well-written. If we want to be the world's best database and research center on the Mario franchise ever found, then we're going to need to keep pushing ourselves to make better articles and more high-quality content. 21:49, 14 January 2018 (EST)

I urge all users to look into the history of the Featured Articles system, specifically historic proposals and decisions that are similar in nature to the current one:
 * Reformat Featured Articles...again! – Introduced the Featured Articles system to the Super Mario Wiki after several failed attempts. Notably did not specify that supporters provide a reason for supporting, just that objectors provide their reasons.
 * FA Support – Failed due to not meeting quorum. Interestingly, the designer of the FA system,, directly stated that "it doesn't make sense to have to provide a reason to support, cause all your reasons are already listed on the FA page."
 * Fanvotes – Failed due to tie. Again, Son of Suns argues that "a support vote does not mean the article will become an FA - it is simply a pledge" to work on the article.
 * Featured Article Voting Modification – Passed; allowed for users to remove both support and oppose votes through the removal process.
 * Repeal "Featured Article Voting Modification" – Passed; partially repealed the previous proposal, specifically the provision to allow for the removal of support votes. It is noteworthy that, the sponsor of the previous proposal, supported this repeal and stated that he regretted including the provision in question.
 * Change FA removal of votes rules – Passed; allowed for administrators to remove fan votes (although it is worth mentioning that support reasons themselves were not required).
 * Change FA rules part 1 – Rejected; would have re-enabled the process for users to remove fan votes.
 * Allow Support Votes to be Removed on Nomination Pages? – Rejected; essentially the same idea as the above proposal. It was deemed unnecessary due to the previous proposal by allowing for Sysops to remove fan votes.
 * Support Votes – Official community compromise reached to replace Tucayo's rule. Only the nominator was allowed to post an official support reason; otherwise, all other votes could remain but be stripped of any comments following the vote. This did not apply to oppose votes or any functions of the Unfeatured process.
 * Require FA Support Reason – Rejected; attempted to overturn prior decision and force users to post support reasons.
 * Require Support Reasoning for FA Nomination – Rejected; essentially the same proposal as the one listed directly above.
 * Automatically Removing Fan Votes from FA Nominations – Passed; reintroduced the removal of all fan votes and expedited the process, requiring automatic removal. However, when it was implemented, support votes for FA nominations were specifically excluded.
 * Officially repeal the "no support reason" Featured Article nomination rule – Passed; overturned the "Support Votes" community decision to end the practice of arbitrarily removing support reasons.

This proposal isn't anything new; on the contrary, I think it fails to account for over a decade of intense debate on the very topic and numerous community discussions and decisions to try and resolve the issue. Not only has this idea been implemented before, but those that were once the strongest proponents gradually became the strongest opponents of the measure. If you check through the proposals I have linked to, you might notice that I actually supported this idea many years ago; however, I have since come to realize that I was wrong. Son of Suns (creator of the FA process), and all other objectors to this idea were absolutely correct: it is not a good idea to demand a "legitimate" reason of the supporters of FA nominations as their vote is an implicit acknowledgement that they believe the article meets the requirements to be featured. 00:55, 15 January 2018 (EST)

New features
None at the moment.

Removals
None at the moment.

How to order navigation templates
According to MarioWiki:Navigation templates, navigation templates are to be ordered as such: "species templates should come first, followed by game-specific and series-wide templates, which are arranged in pure chronological order." I'm fine with species coming before game and series, but I have a problem with the bolded section (emphasis my own). The purely chronological order helps nobody: readers definitely don't know when every game came out, and editors are especially inconvenienced by having to look up every single game until they find exactly where each template fits... or they might just guess where it fits, and if you don't believe that's not being done, look at any large page and count how many templates are out-of-place. This may not be that much of an issue on smaller pages or with new games, but good luck trying to slot in a new template for an older game on Mario's page. The fact of the matter is, the date that a game came out is not obvious to anyone. Why not change it, then?

Option 1: Purely alphabetically

This matches how our categories are currently ordered (including how species go at the top). The templates would be ordered by the first letters in their name and nothing more.

Option 2: By series, then chronologically

This matches how the history sections of the pages themselves are currently ordered. The templates would be grouped together by their subjects' series, then subsequently ordered by their date of release.

Option 3: By series, then alphabetically

An amalgamation of options 1 and 2. The templates are grouped by series, then ordered alphabetically.

Option 4: Purely chronologically (i.e. do nothing)

Everything stays the same, and no changes are made.

Examples of all of the options can be seen here. I'm personally partial to the purely alphabetical option, because it mirrors the categories and it doesn't involve any digging around with dates, but the choice is yours.

Proposer: Deadline: January 20, 2018, 23:59 GMT

Option 1

 * 1) Per proposal.
 * 2) Out of the two non-series based options, this is preferred due to it being done without going to other articles, due to it being easily organize-able, and per proposal.

Option 2

 * 1) - I'm fine with either option, but I often order things chronologically when able over alphabetically. Preferred option
 * 2) Per proposal.
 * 3) Per proposal.
 * 4) I like this option best because it only makes sense if most articles are formatted this way. Per proposal.
 * 5) I think this is the best way to go abut it as it is in line with most other things that require similar ordering, per all.
 * 6) Per all.
 * 7) Per all.
 * 8) Per all.  But how will we arrange the series?  I think Super Mario games should be on top.
 * 9) Per all.
 * 10) Per all. The only problem I have is the templates colors would be grouped. However, this is preferred out of all due this exactly coming before categories.
 * 11) Pretty sure this is how the articles are structured anyway, so yeah.
 * 12) Ordering them the same way as the history sections seems like a good idea.

Option 4

 * 1) - I'm fine with either option, but I often order things chronologically when able over alphabetically.
 * 2) This fixes potential arbitrarity regarding what series should go first, particularly with the game Donkey Kong being both in the Mario and Donkey Kong franchise.
 * 3) Chronological ordering is fine as well, as it provides users with an alternative to the alphabetical ordering of the categories.

Comments
Dear everyone who picked 2: What about the game Donkey Kong? Should the first several templates on Mario's page relate to his involvement in the Donkey Kong franchise? Doc von Schmeltwick (talk) 15:59, 13 January 2018 (EST)
 * The series would be ordered as they're ordered in the history pages. Not particularly arbitrary. At the very least, you should be having a problem with a lot more of the wiki, then. 16:00, 13 January 2018 (EST)
 * Do you mean the history sections? The only reason I don't complain about those is that we have tables of contents for that. The current template ordering, makes sense, unlike the other options. Doc von Schmeltwick (talk) 16:03, 13 January 2018 (EST)
 * How does a table of contents make a difference? They're being ordered the same way. Also, what's so nonsensical about alphabetical ordering? 16:08, 13 January 2018 (EST)
 * Sigh I can see where things are ahead of time and jump to them in a table of contents. Alphabetical ordering is inadequate due to some games having different names depending on region, including English regions. Doc von Schmeltwick (talk) 16:13, 13 January 2018 (EST)
 * Games having different names is a moot point when every other aspect of the wiki is using those names. Someone looking for information about whatever game would see that name, and they'd then know what name to search for afterwards. Nobody is going to the navigation templates first. 16:17, 13 January 2018 (EST)
 * It's still far less helpful than the current ordering, IMO. Doc von Schmeltwick (talk) 16:18, 13 January 2018 (EST)
 * My main point is that the current ordering helps nobody in the slightest. Who is so familiar with every game's release date that they can navigate the templates with ease? 16:20, 13 January 2018 (EST)
 * The person you're speaking with? It just makes more sense to me to see Donkey Kong or Super Mario Bros in the front than, say, Captain Toad: Treasure Tracker, or to have Hotel Mario be the first for Wiggler. Doc von Schmeltwick (talk) 16:36, 13 January 2018 (EST)
 * I'm sure your knowledge applies to every single one of the wiki's readers. 16:55, 13 January 2018 (EST)
 * AGAIN, Hotel Mario and Captain Toad would become the foremost templates on several articles. This is a bad idea. Doc von Schmeltwick (talk) 16:56, 13 January 2018 (EST)
 * You realize it's "By series, then chronologically", right? The only way Hotel Mario or Captain Toad: Treasure Tracker would be the first template on an article is if that was their first appearance in the series overall. -- 22:11, 13 January 2018 (EST)
 * Yes, but I still see the pressing Mario series vs. Donkey Kong series. I'm talking about alphabetical here. I'm saying the way we currently have it has no judgement calls, which the "by series" one would require in some cases. Doc von Schmeltwick (talk) 02:23, 14 January 2018 (EST)
 * I disagree. If something appeared in the Donkey Kong series first, then it's logical that their templates would come first. No judgment calls necessary. -- 16:56, 14 January 2018 (EST)
 * But the game Donkey Kong is in both the Mario and Donkey Kong franchise. Doc von Schmeltwick (talk) 00:49, 15 January 2018 (EST)
 * The first game-related templates on Mario's page are Donkey Kong-related already, but in any case, if you refer to this chart, you'll see that a judgment call has already been made based on their coloration. The arcade games and the Mario vs. Donkey Kong games are Donkey Kong games first and foremost. The implementation of option 2 wouldn't change that.

Miscellaneous
None at the moment.