MarioWiki:Proposals

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.

This page observes the No-Signature Policy.

How To
 * 1) Actions that users feel are appropriate to have community approval first can be added by anyone, but they must have a strong argument.
 * 2) Users then start to discuss on the issue. 24 hours after posting the proposal (rounding up or down to the next or previous full hour, respectively, is allowed), the voting period begins. (The proposer is allowed to support their proposal right after posting.) Each proposal ends at the end of the day one week after voting start. (All times GMT).
 * 3) Every vote should have a reason accompanying it. Agreeing or seconding a previously mentioned reason given by another user is accepted.
 * 4) 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. The voter can remove or rewrite his/her own vote at any time, but the final decision to remove another User's vote lies solely with the Administrators.
 * 5) All proposals that end up in a tie will be extended for another week.
 * 6) If a proposal has more than ten votes, it can only pass or fail by a margin of three votes. If a proposal reaches the deadline and the total number of votes for each option differ by two or less votes, the deadline will be extended for another week.
 * 7) Any proposal that has three votes or less at deadline will automatically be listed as "NO QUORUM." The original proposer then has the option to relist said proposal to generate more discussion.
 * 8) No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old.
 * 9) Proposals can only be rewritten or deleted by their proposer within the first three days of their creation. However, the proposer can request that their proposal be deleted by a Sysop at any time, provided they have a valid reason for it.
 * 10) 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 a Sysop, the proposer can ask for that help.
 * 11) There shouldn't be proposals about creating articles on a underrepresented or completely absent subject, unless there is major disagreement about whether the content should be included. To organize efforts about completing articles on missing subjects, try creating a PipeProject.
 * 12) Proposals cannot be made about System Operator promotions and demotions. Sysops can only be promoted and demoted by the will of Bureaucrats.
 * 13) If the Sysops 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.
 * 14) No joke proposals. Proposals are serious wiki matters, and should be handled professionally. Joke proposals will be deleted on sight.

The times are in GMT, and are set so that the user is more likely to be online at those times (after work/school, weekend nights). If a proposal is added on Monday night at 23:59 GMT, the deadline is the night of the Tuesday of the next week at 23:59 PM. If it is posted a minute later, the deadline is 23:59 PM of the Wednesday of the next week, since midnight is considered to be part of the next day, as 00:00 AM.

Basic Proposal and Support/Oppose Format
This is an example how your proposal should 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]". - ===[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: Voting start: [insert a voting start time here, f.e. "2 January, 2010, 14:00". Voting start times are 24 hours after the time at which the proposal was posted, as described in Rule 2 above.] Deadline: [insert a deadline here, 7 days after the voting start, at 23:59 GMT.]

====Support====
 * 1) [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 " # 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.

How To

 * 1) All active talk page proposals must be listed below in chronological order (new proposals go at the bottom). All pages effected must be mentioned in the brief description, with the talk page housing the discussion linked to directly via "". If the proposal involved a page that is not yet made, use to communicate its title. The Deadline must also be included in the entry. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links. Place  under the heading.
 * 2) 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:
 * 3) Voting in talk page proposals will be open for two weeks, not one. There is no 24 hour delay between the posting of a talk page proposal and the commencement of voting.
 * 4) Talk page proposals may be closed by the proposer if both the support and the oppose sides each have fewer than five votes.
 * 5) The talk page proposal must pertain to the article it is posted on.

List of Talk Page Proposals

 * Split from Grand Goomba (Discuss) Deadline: 31 December, 2010 23:29 GMT
 * Merge Wooden Trapdoor and Steel Trapdoor into (Discuss) Deadline: 8 January, 2011 23:59 GMT

New Features
None at the moment.

Removals
None at the moment

Mario Kart Wii Kart Statistics
This is my first proposal. I just think it would be easier to understand the stats, if they were in percentages. I don't understand all the '+1's and '+3's (etc.). It would be easier to know what to choose for which Grand Prix-s and courses. And if this does take action, I ask for help.

Proposer: Voting start: December 29, 2010 00:00 Deadline: January 5, 2011 00:00

Oppose

 * 1) – Per comments below.
 * 2) Per my comments.
 * 3) I am Zero! We shouldn't change official statistics just because someone somehow find it hard to understand how to add some statistics. How hard is it add just a few numbers on some stats? Zero signing out.
 * 4) Per all. It's going to be confusing for some people either way anyway.
 * 5) Per all.
 * 6) I'm pretty sure that's the way the stats are in the game. I don't find any need to put something in the article in a different way than in the game.
 * 7) - Per all.

Comments
I really don't understand what you are talking about! I went through the whole Mario Kart Wii page and saw only one thing mentioned about '+1' or '-3'. it wasn't even about the statistics!

Yoshigalaxy2: The proposer suggested that we should change the character specific bonus numbers. Anyway, I'm not sure if the quantity values are official (but they are accurate).

I agree with BLOF, but again, no one would know the exact percentage of the statistics.


 * Approximate can be good. Or X/10 format.
 * No, the proposer didn't mean the vehicle values, the proposer meant character values.
 * No, they mean vehicle values. Check the proposal's title.
 * Bowser's luma is right, but Britannic, you can win with any vehicle on the Grand Prix if you do good stuff with it. Basically, I don't think we should even have a statistics thing on the article because if they want to know that stuff, they can just go on the game and look at the stuff..
 * We can't get rid of info just because you can see it in the game. Then there would be hardly anything here.

BabyLuigiOnFire: Oh! Well, Ok that kinda helped. That made it clearer to me. Thanks!

The TPP Effect
Third times the charm I hope, but let's not focus on what proposal number this is that I've made. Lately there has been many talk page proposals by the same user that conflict with each or they conflict with past tpps that have already passed. It is quite confusing on how unorderly and how inconsistent it is starting to become.

What I propose is that we have some changes to the Talk Page Proposal rules shown far above this. I say that if a tpp is being runned that conflicts and disagrees with another tpp that one of them has to change in order for consistency to be played out. Now of course some circumstances should be made about that, depending on what it is and the reasons, but if it is for the same reasoning as another, then that rule should change. But it is hard if it conflicts with other proposals from the past. What I say we should do about it is to have that ttp turn into a proposal that will go into misc and deal with all that it effects. Then, depending on whether the proposal passes or fails, shall the pages be changed depending on the outcome.

I believe that all I have said above is very logical, and will solve many issues that we have had here on the MarioWiki with the tpp's going on lately. If you don't quite fully understand my proposal, comment in the comments section.

Proposer: Voting start: December 29, 2010 5:16 Deadline: January 4, 2011 23:59

Support

 * 1) - Probably should have done this when I made the proposal, but wanted to see some opinions first. Since this seems to be looking like a good proposal, I support it 100%! Per me!
 * 2) Per guy above
 * 3) I am Zero! Per BMB. Zero signing out.
 * 4) Per all.
 * 5) Per Proposal.
 * 6) Per all.

Oppose

 * 1) - I'm sorry, but this is way too vague to be incorporated in our policies. Maybe if you flesh it out and formulate it into clear, precise paragraphs, we can think about adding something like that. But in this form: Just no.
 * 2) Per Edofenrir. I think it would turn out as a confusing policy.
 * 3) - I like the idea, but I have to agree with Edo, this is vague.
 * 4) Well, I agree with all that oppose this, it's main idea is good, but BMB, you need to make your description less vague. I can personally not see the specifics to this idea, thus, I simply have to oppose this for the time being.
 * 5) - Per Edofenrir: I don't see how we could possibly turn this proposal into some clear, concise rules. Besides, we already aim for consistency and if things really do get out of whack, Rule 13 gives the admins the means to set things straight. The problem is that a lot of the time, comparing TPPs is like comparing apples and oranges, and the whole thing is rather subjective: what's inconsistent for one person might be perfectly fine for another. No rule or policy will ever change that, and trying to shoehorn the TPPs into a strict guideline could actually backfire and make it much more difficult to run and regulate them; having wiggle-room is very useful sometimes.

Comments
I like your idea, we do need that. Consistency above all.

Can you clarify what you're saying please?


 * @Bowser's luma: Pretty much I am just solidifing the rules since a lot of agruements and conflicts have been going off in some TPP's. I am just saying to add/change a rule or two in the TPPs so that we can have consistency and to have a more understanding structure. That is about it.
 * Ok. Consistency is good.
 * This seems a little vague, could you be a little more in-depth?
 * Let's see if I can make it fit your idea of "clear". Hmmm...Pretty much if this proposal passes, we will be adding some more rules to TPP's. If a TPP conflicts with another (let's say one is to merge Goomba and Paragoomba, but another at the same time that has Goomba be split to Goomba (species) and Goomba (character)) then one of them has to be deleted or changed so that it doesn't happen like that. But if they interfere with each other, and one is running and another is passing (Example, split M&L series mushrooms apart, and a proposal that passed a few months ago merged them to the Mushroom article), then the current one either has to change the proposal, delete it, or bring it on this page as a main proposal and if passes, then the TPP would say something like "this TPP has changed via ". Its to help put consistency into the TPP's as we have struggled ever since they have been made with what is right and wrong and if this or that conflicts with that or this.

Agree! But that is not consistency, that is preventing conflict.

WAIT! This proposal has already been passed! See the "How to" section above, it has this rule: 8. No proposal can overturn the decision of a previous proposal that is less than 4 weeks (28 days) old. So that means that the proposal made second would have to be deleted to follow this rule so this proposal is unnecessary.
 * Not exactly, it is actually to expand that rule. Because the rule refers to proposals dealing with the same subject, while this proposal talks about proposals that deal with similar circumstances.
 * Well if the circumstances are conflicting, such as in the case of his Goomba/Paragoomba example, one of them would be deleted so either his proposal is unnecessary or his example is faulty.

Super Mario Galaxy 1/2 Planet Names
Hey, I am back with another proposal. I have noticed that many(most) galaxies articles have names for the planets. Pond Planet, Circular planet, Peewee Planet, etc. This names are fine, even if they are not official, because they make things easier. They are fine as long as they are understandable, objective, and make clear what planet they are talking about.

So, what I propose is to create an official policy for the Galaxy articles, which is something like: ''While it is correct to name planets to help identification, these names must be clear as to which planet they are referring to, and must be professional-sounding names (i.e. NO Happy Slide Fun Time Planet). The first planet must always be named "Starting Planet", except in galaxies where the player starts in different planets on different missions. To identify the planet names are conjectural, will be used. Note: Although the names may sound official, we acknowledge that they are not official, but conjectural names given by our users''. How does that sound? It makes things easier, more professional, and without complications.

Proposer: Voting Starts: 23:00 GMT, December 31st, 2010 Deadline: 23:00 GMT, January 7th, 2011

Support

 * 1) - Per me

Comments
I don't really know if this adds anything, I'm not voting because of this.
 * It does, it makes it so every starting planet has to be named that way, it tells our readers the names are conjectural, and it bans stupid names.

Change to
First proposal, I'm sorry if it's n00by. So recently, I found out that the template that has all the courses in the Mario Kart Series is. I think it is a little childish to put in the Race in Racecourses. I can understand if you disagree, but sounds better. Once again, sorry if it's n00by.

Proposer: Voting Start: December 30 2010 22:56 Deadline: January 5, 2010 17:56

Comments
I disagree with you. I think the prefix adjective, "race" specifies "course". There are many types of courses out there, such as an obstacle course or battle course (it could even mean a school course), so changing it to "course" would be simply too vague. I don't understand what makes putting in the word "race" makes things childish. It describes the places perfectly, since you definitely (most of the time) are racing in there.
 * I agree. Also, would have to be switched to the new template name on over 60 pages, which seems like a lot of work for mere semantics. -