|
|
Line 54: |
Line 54: |
|
| |
|
| Hey, so: if this passes, the only track left in the ''8 Deluxe'' section of the race courses template will be [[Sky-High Sundae]]. Do we keep it there since there's always the chance of more tracks like it, or should we scrap that section entirely and move Sky-High Sundae to the ''Tour'' section? It is, after all, apparently being treated as a new track for both games. [[User:Ahemtoday|Ahemtoday]] ([[User talk:Ahemtoday|talk]]) 01:31, August 9, 2022 (EDT) | | Hey, so: if this passes, the only track left in the ''8 Deluxe'' section of the race courses template will be [[Sky-High Sundae]]. Do we keep it there since there's always the chance of more tracks like it, or should we scrap that section entirely and move Sky-High Sundae to the ''Tour'' section? It is, after all, apparently being treated as a new track for both games. [[User:Ahemtoday|Ahemtoday]] ([[User talk:Ahemtoday|talk]]) 01:31, August 9, 2022 (EDT) |
| | :After the next tour starts we'll have a look at the internal name of the course to see its original target platform, if it's ''mob'' (mobile devices, i.e. ''Mario Kart Tour''), then it would make sense to just remove that section, if it is ''u'' or ''nsw'' then we could keep it for the future courses added in the Booster Course Pass that will be treated as new courses in both ''Mario Kart Tour'' and the Booster Course Pass while being primarily designed for the latter.--[[User:Mister Wu|Mister Wu]] ([[User talk:Mister Wu|talk]]) 03:20, August 9, 2022 (EDT) |
|
| |
|
| ==Miscellaneous== | | ==Miscellaneous== |
| ''None at the moment.'' | | ''None at the moment.'' |
|
Current time:
Thursday, May 30th, 09:23 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 30, 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
- 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
- Include Rainbow Coaster & Rainbow Downhill back in the Rainbow Road article (discuss) Deadline:
May 28, 2024, 23:59 GMT Extended to June 4, 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
- Split Samus from List of fighters debuting in Super Smash Bros. (discuss) Deadline: June 11, 2024, 23:59 GMT
Unimplemented proposals
Proposals
Talk page proposals
Writing guidelines
None at the moment.
New features
None at the moment.
Removals
None at the moment.
Changes
Merge city course and Kalimari Desert layouts
Mario Kart 8 Deluxe's version of N64 Kalimari Desert combines the Mario Kart Tour layouts in the same way as it does with Tour's city courses, which I think warrants a reexamination of our policy surrounding these types of tracks. Under that policy, we should have a separate article for the MK8DX version of this course, distinct from both N64 Kalimari Desert and N64 Kalimari Desert 2. We currently don't - however, I take this as less of a call to make one, and more of a sign that our current policy isn't built for this situation.
I make the argument that we should be considering courses with multiple layouts as one course instead of multiple, for the following reasons (many of which I've also stated above):
- Under our current policy, if N64 Kalimari Desert 2 never existed, MK8DX N64 Kalimari Desert would be the same track and share its article with the original. Conversely, if there was a GCN Sherbet Land 2 where players drove under the ice, MK8 GCN Sherbet Land would be considered a different track. My point is that these splits aren't contingent on the tracks themselves and how similar they are to the tracks they share a name with, it's contingent on whether or not a third track exists.
- The marketing makes no mention of the Booster Course Pass's layouts being new courses - it refers to them as classic courses just like the rest, suggesting they're viewed internally as the same course rather than multiple courses with the same theme. The very name and classification of N64 Kalimari Desert 2 supports this as well - if it was considered a different course, I don't think they'd call it a classic course. They already have a way to format the names of new courses based on old ones with the RMX courses, so if they considered it one, I'd think they'd use that.
- The line between a city-style layout variant and a T or R variation is blurry, with both moving objects around the same model. Tracks like Wii Coconut Mall T and GCN Baby Park T even take racers outside the normal bounds of the track. Most importantly, racers', drivers', and gliders' favorite and favored courses have T and R variations listed just as separately as numbered variations are.
As such, I propose a full merge of main-series multi-layout tracks, which will entail the following:
(If you want to read further discussion on this topic, it has also been discussed here and here.)
Proposer: Ahemtoday (talk)
Deadline: August 13, 2022, 23:59 GMT
Do as proposed
- Ahemtoday (talk) Per proposal.
- Tails777 (talk) Per proposal and the discussion on Kalimari Desert’s talk page.
- Arend (talk) Per proposal and what we have discussed here.
- Hewer (talk) Per all.
- Mister Wu (talk) We need to keep the course icons of the numbered variants in Mario Kart Tour in the wiki and also highlight their gameplay implications in terms of being a favorite and favored of different drivers, karts and gliders, just like the respective R, T and R/T variants, but I don't think we need to treat them as courses fully separate from the original - not even the game does that.
- RSM (talk) per discussion in Talk:N64 Kalimari Desert and per proposal
- Archivist Toadette (talk) Yeah, in the end, if the Booster Course Pass uses all of the different layouts at once, then that pretty much makes everything redundant. Per all.
Split the MK8DX section into its own article instead
Leave as-is
In case one is confused at what Ahemtoday is talking about with "As discussed above", this proposal was originally posted on Talk:N64 Kalimari Desert. I suggest looking there for previous discussion points.
Furthermore, I would like to ask if this also affects this section on the Mario Kart Tour article. Arend (talk) 03:34, August 6, 2022 (EDT)
- the only thing i think this'll change would be the links, other then that, it would probably remain the same - RSM 08:22, August 6, 2022 (EDT)
Hey, so: if this passes, the only track left in the 8 Deluxe section of the race courses template will be Sky-High Sundae. Do we keep it there since there's always the chance of more tracks like it, or should we scrap that section entirely and move Sky-High Sundae to the Tour section? It is, after all, apparently being treated as a new track for both games. Ahemtoday (talk) 01:31, August 9, 2022 (EDT)
- After the next tour starts we'll have a look at the internal name of the course to see its original target platform, if it's mob (mobile devices, i.e. Mario Kart Tour), then it would make sense to just remove that section, if it is u or nsw then we could keep it for the future courses added in the Booster Course Pass that will be treated as new courses in both Mario Kart Tour and the Booster Course Pass while being primarily designed for the latter.--Mister Wu (talk) 03:20, August 9, 2022 (EDT)
Miscellaneous
None at the moment.