MarioWiki:Proposals: Difference between revisions
BBQ Turtle (talk | contribs) m (→Unimplemented proposals: I've implemented that one now.) |
No edit summary |
||
| Line 94: | Line 94: | ||
==Writing guidelines== | ==Writing guidelines== | ||
===Expand Featured Articles writing guidelines=== | |||
Currently our writing standards regarding what constitutes as a Featured Article at [[MarioWiki:Featured_articles#Featured_article_standards|MarioWiki: Featured Articles]] is a vague list of short phrases and one-liners, which makes it far too loose to interpretation to my liking, especially for a process where quality control is key and enforcing these guidelines is a pivotal step to picking out only the best articles in MarioWiki. I propose that we expand these guidelines into small little paragraphs, detailing what exactly we want out of a Featured Article. This will follow the model similar to how we write out [[MarioWiki:Good writing|our good writing policy]], where key points are organized under a header as a list first, and a paragraph detailing what we want under the header will be elaborated on. | |||
If you want the specifics on how exactly I want the writing guidelines to look like, I have worked on it in the following sandbox page, where most of my proposed points is detailed out and worked on | |||
*[[User:Baby Luigi/Featured Articles guidelines]] | |||
If you suggest any improvements to the writing or any further clarity, please comment on the proposal! | |||
'''Proposer''': {{User|Baby Luigi}}<br> | |||
'''Deadline''': February 8, 2018, 23:59 GMT | |||
===Support=== | |||
#{{User|Baby Luigi}} | |||
===Oppose=== | |||
===Comments=== | |||
==New features== | ==New features== | ||
| Line 103: | Line 119: | ||
==Changes== | ==Changes== | ||
'' | ===Manually manage Featured Article nominations=== | ||
For some years, I personally had a problem with how Featured Articles nominations, both active and archived nominations are handled, especially at [[MarioWiki:Featured Articles]]. We currently just link to an archive via categories when I think it's a very messy, cumbersome, and frankly lazy way to do this. No other processes in the wiki let categories organize and link to their pages; the equivalent is letting categories organize implemented proposals and nothing else. What's especially bad for the category system is that unregistered users mostly cannot even see the active nominations in the category page, as it often requires a manual refreshment of the browser cache to see the active links. I propose to organize the following processes: | |||
;Active Featured Article nominations | |||
I would like to implement a sortable wikitable in the '''Nominated articles/lists''' and '''FAs proposed for unfeaturing''' header. This table is something we would manually have to update ourselves, which shouldn't be a problem with our active editor community and some effort for some oversight. The table would list a link to the active Featured Article/Unfeature nomination, piped with the article name, the time it was nominated, the deadline, and the time it was passed in. If there exist no parameters, the table would be left blank, filled with a ---. We add cells as nominations go up, and delete cells when nominations pass/fail, and the minimum amount of cells is one row with dashes if there are no active nominations at the time. | |||
;Featured Articles archives | |||
The headers regarding the archives at [[MarioWiki:Featured Articles]] would be reorganized under a big header, '''Archives''', with two smaller headers: '''Feature nominations''' and '''Unfeature nominations'''. Both failed and successful archives would therefore be merged together. These archives would also be handled through a sortable table format that we have to manually update, but again, this isn't any skin off our nose, as we can easily archive and document past proposals. The table format cells would use a color system similar to how we archive MarioWiki:Proposals, with a color denoting how the process goes: passed, failed, passed at the time but unfeatured today, and failed at the time but passed today. The cells would link to the archive of the Featured Article with a piped name for the name of the article, which user nominated the article, the time it was nominated, what number of nominations it has (N1, N2, etc.), and the time the nomination passed/failed. | |||
;References | |||
If you want a more visual picture of how I want things to be organized at [[MarioWiki:Featured Articles]], you can check out my sandbox below. Any refinements, suggestions for improvements, or any correction of possible errors are encouraged and should be noted in the comments section. | |||
*[[User:Baby Luigi/Featured Articles]] | |||
I hope this proposal would smoothen and refine the process of Featured Article nominations and make it easier for the end user to access past featured article nominations as well as guide them around links easier as they explore our Featured Article pages. | |||
'''Proposer''': {{User|Baby Luigi}}, giving huge special thanks to {{User|Toadette the Achiever}} for a lot of effort helping me develop my sandbox page.<br> | |||
'''Deadline''': February 8, 2018, 23:59 GMT | |||
===Support=== | |||
#{{User|Baby Luigi}} | |||
===Oppose=== | |||
===Comments=== | |||
==Miscellaneous== | ==Miscellaneous== | ||
''None at the moment.'' | ''None at the moment.'' | ||
Revision as of 13:54, February 1, 2018
|
|
Tuesday, February 25th, 14:05 GMT |
|
|
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.
How to
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."
Poll proposal formatting
As an alternative to the basic proposal format, users may choose to create a poll proposal when one larger issue can be broken down into multiple sub-issues that can be resolved independently of each other. In a poll proposal, each option is its own mini-proposal with a deadline and Support/Oppose subheadings. The rules above apply to each option as if it were a its own two-option proposal: users may vote Support or Oppose on any number of options they wish, and individual options may close early or be extended separately from the rest. If an option fails to achieve quorum or reach a consensus after three extensions, then "Oppose" wins for that option by default. A poll proposal closes after all of its options have been settled, and no action is taken until then. If all options fail, then nothing will be done.
To create a poll proposal, copy and paste the formatting below to get started; your username and the option deadlines 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]".
===[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}}}}
====[option title (e.g. Option 1)]: [brief summary of option]====
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT
;Support
#{{User|{{subst:REVISIONUSER}}}} Per proposal.
;Oppose
====[option title (e.g. Option 2)]: [brief summary of option]====
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT
;Support
#{{User|{{subst:REVISIONUSER}}}} Per proposal.
;Oppose
====[option title (e.g. Option 3)]: [brief summary of option]====
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT
;Support
#{{User|{{subst:REVISIONUSER}}}} Per proposal.
;Oppose
====Comments ([brief proposal title])====
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 24, 2025, 23:59 GMT
- Merge Poochy Dash into Poochy & Yoshi's Woolly World and Poochy Hut (discuss) Deadline: February 26, 2025, 23:59 GMT
- Split the Monstro Town Mushroom from the normal Mushroom (discuss) Deadline: February 26, 2025, 23:59 GMT
- Merge Free-for-All Space with 4-Player Space (discuss) Deadline: February 26, 2025, 23:59 GMT
- Tighten Category:Power-ups and its subcategories (discuss) Deadline: February 27, 2025, 23:59 GMT
- Split Toad wearing headphones off from Jammin' Toad (discuss) Deadline: February 28, 2025, 23:59 GMT
- Count ongoing serialized comics for latest appearances (discuss) Deadline: March 2, 2025, 23:59 GMT
- Merge Mega Kantera with Big Lantern Ghost (discuss) Deadline: March 3, 2025, 23:59 GMT
- Rename Dark Horse Comics to "Dark Horse Books" (discuss) Deadline: March 5, 2025, 23:59 GMT
- Properly define Brown Yoshi (discuss) Deadline: March 6, 2025, 23:59 GMT
- Remove
font-familyproperty from Template:Proposal outcome (discuss) Deadline: March 6, 2025, 23:59 GMT - Don't consider the snakes from Mario Kart snake jars to be Cobrats (discuss) Deadline: March 6, 2025, 23:59 GMT
- Merge Kong army to Kong (discuss) Deadline: March 8, 2025, 23:59 GMT
Unimplemented proposals
Proposals
| 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 Super Mario Maker titles and Super Mario Run.
| 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) |
| Add film and television ratings to Template:Ratings, TheUndescribableGhost (ended October 1, 2024) |
| Use the classic and classic link templates when discussing classic courses in Mario Kart Tour, YoYo (ended October 2, 2024) |
| Clarify coverage of the Super Smash Bros. series, Doc von Schmeltwick (ended October 17, 2024) |
| Remove all subpage and redirect links from all navigational templates, JanMisali (ended October 31, 2024) |
| Prioritize MESEN/NEStopia palette for NES sprites and screenshots, Doc von Schmeltwick (ended November 3, 2024) |
| Allow English names from closed captions, Koopa con Carne (ended November 12, 2024) |
- ^ NOTE: A number of names coming from closed captions are listed here.
| Split off the Mario Kart Tour template(s), MightyMario (ended November 24, 2024) |
| Split major RPG appearances of recurring locations, EvieMaybe (ended December 16, 2024) |
| Organize "List of implied" articles, EvieMaybe (ended January 12, 2025) |
| Split Mario & Luigi badges and remaining accessories, Camwoodstock (ended February 1, 2025) |
| Merge Chef Torte and Apprentice (Torte), Camwoodstock (ended February 3, 2025) |
| Merge the Ancient Beanbean Civilizations to List of implied species, Camwoodstock (ended February 13, 2025) |
| Make Dark Mode available to everyone, Pizza Master (ended February 20, 2025) |
| Standardize the use of "English", "English (United States)" and/or "English (United Kingdom)" as languages in game infoboxes, PaperSplash (ended February 23, 2025) |
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) |
| Create articles for specified special buildings in Super Mario Run, Salmancer (ended November 15, 2024) |
| Expand and rename List of characters by game to List of characters by first appearance, Hewer (ended November 20, 2024) |
| Merge False Character and Fighting Polygon/Wireframe/Alloy/Mii Teams into List of Super Smash Bros. series bosses, Doc von Schmeltwick (ended December 2, 2024) |
| Merge Wiggler Family to Dimble Wood, Camwoodstock (ended January 11, 2025) |
| Split the Ink Bomb, Camwoodstock (ended January 12, 2025) |
| Create a catch-all Poltergust article, Blinker (ended January 21, 2025) |
| Merge the two Clawing for More articles, Salmancer (ended January 27, 2025) |
| Merge Dangan Mario to Invincible Mario, PrincessPeachFan (ended January 30, 2025) |
| Give the Cluck-A-Pop Prizes articles, Camwoodstock (ended January 31, 2025) |
| Reverse the proposal to trim White Shy Guy, Waluigi Time (ended February 8, 2025) |
| Split Animal Crossing (game), Kaptain Skurvy (ended February 12, 2025) |
| Split the modes in the Battles page, Mario (ended February 15, 2025) |
| Split the SMRPG Chain Chomp from Chain Chomp, Kirby the Formling (ended February 22, 2025) |
List of talk page proposals
Template:TPPDiscuss Template:TPPDiscuss Template:TPPDiscuss Template:TPPDiscuss Template:TPPDiscuss Template:TPPDiscuss
Unimplemented proposals
Writing guidelines
Expand Featured Articles writing guidelines
Currently our writing standards regarding what constitutes as a Featured Article at MarioWiki: Featured Articles is a vague list of short phrases and one-liners, which makes it far too loose to interpretation to my liking, especially for a process where quality control is key and enforcing these guidelines is a pivotal step to picking out only the best articles in MarioWiki. I propose that we expand these guidelines into small little paragraphs, detailing what exactly we want out of a Featured Article. This will follow the model similar to how we write out our good writing policy, where key points are organized under a header as a list first, and a paragraph detailing what we want under the header will be elaborated on.
If you want the specifics on how exactly I want the writing guidelines to look like, I have worked on it in the following sandbox page, where most of my proposed points is detailed out and worked on
If you suggest any improvements to the writing or any further clarity, please comment on the proposal!
Proposer: Baby Luigi (talk)
Deadline: February 8, 2018, 23:59 GMT
Support
Oppose
Comments
New features
None at the moment.
Removals
None at the moment.
Changes
Manually manage Featured Article nominations
For some years, I personally had a problem with how Featured Articles nominations, both active and archived nominations are handled, especially at MarioWiki:Featured Articles. We currently just link to an archive via categories when I think it's a very messy, cumbersome, and frankly lazy way to do this. No other processes in the wiki let categories organize and link to their pages; the equivalent is letting categories organize implemented proposals and nothing else. What's especially bad for the category system is that unregistered users mostly cannot even see the active nominations in the category page, as it often requires a manual refreshment of the browser cache to see the active links. I propose to organize the following processes:
- Active Featured Article nominations
I would like to implement a sortable wikitable in the Nominated articles/lists and FAs proposed for unfeaturing header. This table is something we would manually have to update ourselves, which shouldn't be a problem with our active editor community and some effort for some oversight. The table would list a link to the active Featured Article/Unfeature nomination, piped with the article name, the time it was nominated, the deadline, and the time it was passed in. If there exist no parameters, the table would be left blank, filled with a ---. We add cells as nominations go up, and delete cells when nominations pass/fail, and the minimum amount of cells is one row with dashes if there are no active nominations at the time.
- Featured Articles archives
The headers regarding the archives at MarioWiki:Featured Articles would be reorganized under a big header, Archives, with two smaller headers: Feature nominations and Unfeature nominations. Both failed and successful archives would therefore be merged together. These archives would also be handled through a sortable table format that we have to manually update, but again, this isn't any skin off our nose, as we can easily archive and document past proposals. The table format cells would use a color system similar to how we archive MarioWiki:Proposals, with a color denoting how the process goes: passed, failed, passed at the time but unfeatured today, and failed at the time but passed today. The cells would link to the archive of the Featured Article with a piped name for the name of the article, which user nominated the article, the time it was nominated, what number of nominations it has (N1, N2, etc.), and the time the nomination passed/failed.
- References
If you want a more visual picture of how I want things to be organized at MarioWiki:Featured Articles, you can check out my sandbox below. Any refinements, suggestions for improvements, or any correction of possible errors are encouraged and should be noted in the comments section.
I hope this proposal would smoothen and refine the process of Featured Article nominations and make it easier for the end user to access past featured article nominations as well as guide them around links easier as they explore our Featured Article pages.
Proposer: Baby Luigi (talk), giving huge special thanks to Toadette the Achiever (talk) for a lot of effort helping me develop my sandbox page.
Deadline: February 8, 2018, 23:59 GMT
Support
Oppose
Comments
Miscellaneous
None at the moment.
