#{{User|Alex95}} - Originally voted to do nothing as I thought this was also talking about coins in a broader term, i.e. also including [[Red Coin]]s and [[Blue Coin]]s. But for referring to just the standard Yellow Coins, yes, "Coin" should be capitalized (at least in instances outside of quotes).
#{{User|Alex95}} - Originally voted to do nothing as I thought this was also talking about coins in a broader term, i.e. also including [[Red Coin]]s and [[Blue Coin]]s. But for referring to just the standard Yellow Coins, yes, "Coin" should be capitalized (at least in instances outside of quotes).
#{{user|Mario jc}} Per Alex, and supporting for consistency (unless "coin" is used in generic terms; see [https://youtu.be/_GQGUGe7kDU?t=15m18s this]).
#{{user|Mario jc}} Per Alex, and supporting for consistency (unless "coin" is used in generic terms; see [https://youtu.be/_GQGUGe7kDU?t=15m18s this]).
#{{user|3D Player 2010}} per all
====Use "coin"====
====Use "coin"====
Revision as of 15:28, September 2, 2017
Current time:
Monday, February 10th, 18:23 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.
Voting periods last for two weeks, but can close early or be extended (see below).
Any autoconfirmed user can support or oppose, but must have a strong reason for doing so.
All proposals must be approved by a majority of voters, including proposals with more than two options.
If you would like to get feedback on an idea before formally proposing it here, you may do so on the proposals talk. For talk page proposals, you can discuss the changes on the talk page itself before creating the TPP there.
If someone has 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 other users, who will then vote on whether or not they think the idea should be implemented. 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}}.
Rules
Only autoconfirmed users may create or vote on proposals. Proposals can be created by one user or co-authored by two users.
Anyone is free to comment on proposals (provided that the page's protection level allows them to edit).
Proposals conclude at the end of the day (23:59) two weeks after voting starts (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 two weeks later on Monday, August 15, at 23:59 GMT.
Users may vote for more than one option, but they may not vote for every option available.
Every vote should have a strong, sensible reason accompanying it. Agreeing with a previously mentioned reason given by another user is acceptable (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 wiki staff.
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 "(blocked)" 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.
Proposals cannot contradict an already ongoing proposal or overturn the decision of a previous proposal that concluded less than four weeks (28 days) ago.
If one week before a proposal's initial deadline, the first place option is ahead of the second place option by eight or more votes and the first place option has at least 80% approval, then the proposal concludes early. Wiki staff may tag a proposal with "Do not close early" at any time to prevent an early close, if needed.
Tag the proposal with {{early notice}} if it is on track for an early close. Use {{proposal check|early=yes}} to perform the check.
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% approval to win. If the margin is only one or two votes, then the first place option must have at least 60% approval to win. If the required approval threshold is not met, then the proposal is extended for another week.
Use {{proposal check}} to automate this calculation; see the template page for usage instructions and examples.
Proposals can be extended a maximum of three times. If a consensus has not been reached by the fourth deadline, then the proposal fails and cannot be re-proposed until at least four weeks after the last deadline.
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.
After a proposal passes, it is added to the appropriate list of "unimplemented proposals" below and is removed once it has been sufficiently implemented.
If the wiki staff deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to cancel it at any time.
Proposals can only be rewritten or canceled by their proposer within the first four days of their creation. However, proposers can request that their proposal be canceled by a staff member 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. Staff changes are discussed internally and handled by the bureaucrats.
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 formatting
Copy and paste the formatting below to get started; your username and the proposal deadline will automatically be substituted when you save the page. Update the bracketed variables with actual information, and be sure to replace the whole variable including the square brackets, so "[insert info here]" becomes "This is the inserted information" and not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but the objective(s) of each voting option 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|{{subst:REVISIONUSER}}}}<br>
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT
====[option title (e.g. Support, Option 1)]: [brief summary of option]====
#{{User|{{subst:REVISIONUSER}}}} Per proposal.
====[option title (e.g. Oppose, Option 2)]: [brief summary of option]====
====Comments ([brief proposal title])====
Autoconfirmed users will now be able to vote on your proposal. Remember that you can vote on your own proposal just like the others.
To vote for an option, just insert #{{User|[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 simply say "Per 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. All of the above proposal rules also apply to talk page proposals. Place {{TPP}} under the section's heading, and once the proposal is over, replace the template with {{settled TPP}}. Proposals dealing with a large amount 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 {{ongoing TPP}}. 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.
List of ongoing talk page proposals
Move Kutlass to Kutlass (enemy) (discuss) Deadline: February 10, 2025, 23:59 GMT
What to do about the unresolved identity of Worlds A-C human (discuss) Deadline: February 10, 2025, 23:59 GMT
Currently, the wiki has no set standard for the capitalization of the golden that Mario and co. collect in abundance across the franchise: is it "Coin", with a capital C, or "coin", with a lowercase c? This isn't entirely clear-cut: from the games that I've looked at, there are many that do not capitalize it, including most recently Mario Party 8, Sm4sh, and New Super Mario Bros. 2, but there are also other games that capitalize it, including New Super Mario Bros. Wii and Mario Party, and there's something odd and inconsistent about listing the Red Coin, the Purple Coin, the Blue Coin, the 20 Coin, the Key Coin, and many others as being derivatives of the coin. That lowercase "coin" seems out of place, doesn't it? Lowercasing it just because it's a generic noun doesn't hold either; the Mushroom is plainly and consistently capitalized in just about every circumstances. If you're going to say it's because the Mario Mushrooms obviously aren't like the real-life mushrooms, then I'd argue the same goes for the floating, golden, abundant Coins. There is a precedent for not capitalizing the names of subjects with, for example, treasure chest (despite there being at least one in-game source that capitalizes them, but that's an issue for another time), but it's a moot point if the subject isn't generic in the first place.
This may seem like a trivially minor issue, but at the same time, this is an issue that has yet to reach a decisive conclusion. I fail to see a reason why we shouldn't strive for consistency, especially since we've already had a proposal to decide on a set spelling for minigame (spoilers: we decided on minigame).
Proposer: Time Turner (talk) Deadline: September 2, 2017, 23:59 GMT
Use "Coin"
Time Turner (talk) It's hardly as if no official sources have ever not capitalized it. Per proposal.
Alex95 (talk) - Originally voted to do nothing as I thought this was also talking about coins in a broader term, i.e. also including Red Coins and Blue Coins. But for referring to just the standard Yellow Coins, yes, "Coin" should be capitalized (at least in instances outside of quotes).
Mario jc (talk) Per Alex, and supporting for consistency (unless "coin" is used in generic terms; see this).
Doc von Schmeltwick (talk) Alternate vote here, because the games themselves almost always refer to them in lowercase. Still, silly proposal.
LinkTheLefty (talk) Unless it's referring to a specific type in most cases, coins (and for that matter, blocks and, in at least one instance, coin blocks) have consistently been generically lowercase in RPGs.
Do nothing
Toadette the Achiever (talk) I highly doubt that there is enough definitive official sources that specifically stick to one capitalization. I'd rather stick with this option until an official capitalization is given, and right now, there doesn't seem to be. (One example of this is that I found an all-lowercase "coin" in the Super Mario Galaxy 2 instruction booklet.)
If anyone has any more in-game citations for "Coin" or "coin" from any games that haven't been mentioned, then I'm all-ears. Hello, I'm Time Turner. 00:16, 26 August 2017 (EDT)
@Toadette: I don't see why we should be inconsistent solely because the games also happen to be inconsistent. Hello, I'm Time Turner. 00:47, 26 August 2017 (EDT)
@Time Turner: Changed the content of my vote. (T|C) 00:50, 26 August 2017 (EDT)
What kind of official capitalization do you want? Is it necessary for Nintendo to make a press release declaring whether it's lowercase or up case? Through the simple fact that the names are seen in plain text, we already have an abundance of official names. It's up to us to decide how we should use the information. Hello, I'm Time Turner. 00:52, 26 August 2017 (EDT)
Because it's an inanimate object that is super inconsistent as to how it's capitalized. Honestly, if you wanna go by policy, see how the latest game spells it. Doc von Schmeltwick (talk) 01:58, 26 August 2017 (CT)
If we strictly followed every new game, the spelling might constantly change, and there are likely cases in which there's no adequate source for capitalization. Best to nip it in the bud, no? I also don't get your point with it being an inanimate object. Hello, I'm Time Turner. 03:06, 26 August 2017 (EDT)
I don't get what's acceptable about setting a standard for "microgame" but not for "coin"? Hello, I'm Time Turner. 17:14, 26 August 2017 (EDT)
It's capitalized in the tutorial of Mario Party 2, but not capitalized in the tutorial of Mario Party 3. It's inconsistent between such close games. A better choice would be to capitalize it depending on the game, and have the higher case be more dominant otherwise (because it is a main item), but I feel this is such a minor unnoticeable issue, yet the "do nothing" option does not convince me. --
06:30, 27 August 2017 (EDT)
Removals
None at the moment.
Changes
Include the date a proposal was withdrawn within the proposal (when applicable)
When it comes to the proposal archives, in which we write down the date each proposal ended, it's standard to use the date a proposal was canceled by its proposer or withdrawn for whatever other reason, rather than the proposed deadline (as documented here). This makes sense: it wouldn't be accurate to say that a proposal had concluded a week later than it actually did, and the point of the archives is that we're documenting each proposal exactly as they played out (which is why we make note of proposals that themselves failed but whose proposed changes later passed, and vice-versa). With that in mind, why do we only make note of this in the broadarchives and not within the proposals itself? Sure, it's possible to find the date it was canceled by going through the page's history, in the same way it's also possible to find the original proposer through the history page, but we still make note of it within the proposal itself. Leaving only the proposed deadline by itself is also rather misleading and non-informative, considering that any users reading through the proposal wouldn't be able to obviously tell when it actually closed. Even with the proposal outcome saying it was canceled, that doesn't help people find out when it was canceled. We should strive for accuracy, especially when all we'd need to do is make note of one more date.
The changes I have in mind would only be applicable to proposals that were canceled before their deadline, obviously. First of all, the Deadline section would be renamed to Proposed Deadline, with no changes to the date. Secondly, a section called Date Withdrawn would be placed underneath the Deadline, documenting exactly when the proposal was canceled. Ideally, this would include the time in GMT to match the Deadline, but for simplicity's sake, this proposal will only ask that the day needs to be documented and not the time. The details may be subject to change through future discussions, but the main change is clear: within the proposals, document when they were canceled.
Proposer: Time Turner (talk) Deadline: September 9, 2017, 23:59 GMT
(T|C) 00:50, 26 August 2017 (EDT)
Yoshi the SSM (talk) 01:37, 26 August 2017 (EDT)
