MarioWiki:Proposals

http://i143.photobucket.com/albums/r149/Deadringerforlove/dessert1.jpg 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

 * Make Articles for the Instruments in the Conservatory (Discuss) Deadline: October 30, 23:59 GMT

New Features
None at the moment.

Removals
None at the moment

Make a Gallery Template
I just thought how easy it would be to have a Gallery template so new users could easily find more galleries when they access one and even editors could easily access their favorite galleries without having to go through the trouble. We could make a template for Character galleries and a template for Game galleries. Anyone think this is a good idea? I am thinking about making sections for Characters, Species, Bosses, and Games.

Proposer: Voting start: Monday 7:54, 11 October 2010(UTC) Deadline: Monday 23:59 18 October 2010 (UTC) Extended: Monday 23:59 25 October 2010 (UTC)

Make a Gallery Template

 * 1) Per myself. If this proposal passes, then I will truly make a gallery template.
 * 2) Hey! Here's a good idea! Per Mileycyrussoulja.
 * 3) - A navbox sounds like a good idea! It can help navigation around the galleries and it can't hurt, for examples see the staff articles (i.e. Super Mario Galaxy/Staff)
 * 4) Nice idea.  It got me thinking of when I was a noob to the wiki.  Anything to make things easier, I say.

Comments
Although we already have links to Galleries within most articles, I notice a few have galleries but don't link to them such as Waluigi and a few other characters that appear to have no link to their galleries. Although while back on subject, a gallery template on gallery pages would be nice. A segment of the template, for humans, species, bosses.
 * Do you have any example of this? Examples are commonly needed on this proposals.
 * This could be difficult...I'll work on something :)

Is this proposing to make something like a navigation template for galleries?
 * From what I understand, yes. Like a big list of galleries.
 * OK. I'd really like to see an example of this, though it sounds pretty good.

Remember, supporters, saying any variation of "I like this idea!" is not a valid reason to support.
 * I really want to see an example of this, I don't feel comfortable allowing something this difficult to pass. This is something that could actually be pretty hard...
 * OK, is this what you're thinking of? I think it looks good...granted it's not in a template but if you want it in a template, I could try that.
 * I think what he means is one of those little boxes at the bottom of the page. It could group galleries of characters like Bowser, Bowser Jr., etc. or Mario, Luigi, etc.
 * yes, i do, Bowser's luma.

They're called navboxes.

Grammar Team
Many people have different ways of typing things, most of the time mixing up grammar. I propose that we have a team who will check and edit any grammar mistakes. This may be changing words, adding letters, etc.

Example:

THIS is A ExAMpLE LINE oF TexT Four thiS.

Edit -: This is a example line of text for this.

Propser: Voting Start 12:00, October 18th Deadline 12:00, October 25th

Make a Grammar Group

 * Per my idea.

Don't make it.

 * 1) Per comments below. I think that such a group is unnecessary for grammar errors.
 * 2) - Per comments below.
 * 3) Per comments below.
 * 4) Not a good idea to make a group about something users correct anyways.
 * 5) Per all. We don't need a group for something as simple as that.
 * 6) If I see a grammar error, I'd correct it immediately. If I were forced to search for grammar errors, I would get mighty bored very quickly. I don't think we need a group JUST to correct grammar errors.
 * 7) The problem isn't official enough to make a change.  It's kind of an amateur thing to fix errors you see while browsing the wiki.  If there were a lot of errors on the pages I would say of course.  Go for it.  But like I said, not a major problem.
 * 8) I don't think that's really needed, editing the wiki is team work, everyone and anyone participate to correct those mistakes. And per LGM.

Comments
While this seems to be a great policy to have, I have a slight feeling that there may be arguements caused by this over Americanized spellings and non-Americanised spellings. For example, one of my earliest edits was edited, without my knowledge, shortly afterwards to change my English spellings to Americanized spellings: "colour" to "color". And that, frankly, is pointless. 13:04, 17 October 2010 (UTC)
 * There are a lot of many ways, such as form and forme, colour and color, and so on and so forth. But the proposal is stating that we have just one group of users do all the grammar issues. I don't approve of this idea as there are over 3,000 users that have the job of editing and improving the page, and just limiting the grammar stuff is like taking away nearly all the work needed on this wiki. We can't just have a group of people be in charge of it, as it is too much for just that. If you really want this, I say you should make this a Pipeproject (if there isn't one about this kind of issue).
 * I see your point BMB, and I agree with it; however my point was about the possibility of disagreements and edit wars(maybe) over what spelling scheme ought to be used. Because if this proposal did pass, then wouldn't every article have to adhere to one uniform spelling and grammar scheme?
 * I agree with BMB, we don't need to limit this to certain users, all users should be allowed, and encouraged, to fix grammar mistakes. If you wish to change a policy, do that, but making a specific team won't stop bickering throughout the team. If this proposal does pass, it won't make anything in addition to what we currently have.
 * Per. This is pointless. Anyone is welcome to fix the grammar mistakes they find. We don't need a team for it.

People who care about grammar will fix it on their own accord. Creating a silly group monicker that has no pratical tool for the job won't do snuff. --Glowsquid 11:59, 19 October 2010 (UTC)

For the record, anyone changing a British spelling to American or vice-versa is in the wrong, as both are allowed on the wiki to reflect the international nature of the wiki. (In fact, if I catch someone changing a word, I revert it, even if they were changing it to my country's spelling; if the change was part of an overall rewrite, it's fine, imho.) -

This could make a good BJAODN bad proposal section, aside from that this is probably one of the worst and poorly done proposals so far. Also per all above and what they have said.


 * You don't really have to belittle people, you know. Ideas are ideas, and we appreciate ideas. Anyway, although we can have both British and American spelling in articles, I think we should to one type of spelling in one article (if an article has mainly British spelling, then it should be British spelling, e.g.). Not that I'm right, but I do love consistency.
 * We should the British spelling only for articles where the stuff gets released in Europe first, and American if it gets released in North American first.
 * I am Zero! Then that will confuse the visitor when jumping from article to article and great grammar LGM. Zero signing out.
 * I concur, BLOF sounds like he has a nice idea going on. D:
 * But that's a pain to keep track of. I also like the mix inside the articles; just think of them as synonyms giving the pages variety, rather than inconsistencies in spelling. -