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 with the signature code (~).

How To
 * 1) Actions that sysops feel are appropriate to have community approval first can be added by anyone, but they must have a strong argument.
 * 2) Users then vote and discuss on the issue during that week. The "deadline" for the proposal is one week from posting at:
 * 3) Monday to Thursday: 5pm
 * 4) Friday and Saturday: 8pm
 * 5) Sunday: 3pm
 * 6) At any time a vote may be rejected if at least three active users believe the vote truly has strong reasons supporting it. Every vote should have a reason accompanying it.
 * 7) " # " should be added under the last vote of each support/oppose section to show another blank line.
 * 8) At the deadline, the validity of each vote and the discussion is reviewed by the community.
 * 9) The original proposer calls the result of the proposal and takes action(s) as decided if necessary.

The times are in EDT, and are set so that the user is more likely to be online at those times (after school, weekend nights).

So for example, if a proposal is added on Saturday night at 11:59 PM EDT, the deadline is the next Saturday night at 8:00 PM. If it is indeed a minute later, the deadline is a day plus 15 hours (Sunday), as opposed to a day minus 4 hours.

CURRENTLY: , 27 2024 (EDT)

Force Edit Summaries
Short & simple: Edit summaries are nice little notices when looking at a revision of what to expect in a diff, or, what the contributor edited. When editing a section, the edit summary links to that section as a default, but very often contributors are leaving edit summaries blank. In 1.10, if an edit summary is left blank when creating a new page, the beginning of the page's content is shown by default, which can clog recent changes.

I found a Javascript code released in the public domain on Wikipedia that will force the use of edit summaries if it is left blank by either displaying a message or flashing the edit summary input line when submitting. Should I implement this and thus force a better user habit?

Proposer: Deadline: 15:00, 24 June

Make it Mandatory

 * 1) – it's a good habit to keep, previews a diff with the general idea, clears recent changes somewhat

Keep it Optional

 * 1) Hk -- Are you an idiot? There's no way to enforce this. You can always highly recommend it, but enforcement is impossible. Your little javascript is flawed. I could add the word "doodoo" as the edit summary. This is the dumbest idea I've ever heard come through this channel.... What's next? A proposal to ban proposals? This is one of those things that coding can't fix. This on of those things that can't be enforced. There are too many ways around this count. The validity of even wasting time installing the javascript was just crumbled, by the way. In case you weren't paying attention. This would HELP spammers more than hurt them.
 * 2) - I don't think this works out. When making a very minor edit, many users will just fill in random characters in the edit summary. A different point would be false edit summaries, I've seen one on Wikipedia today. The summary suggested on-topic work, while it was just vandalism. You cannot trust all edit summaries.
 * 3) Gofer -- As everyone said, there's no efficient way of enforcing it, using the javascript code would more encourage spam than anything and using block would be ridiculous. As Cobold said, paying attention to false edit summaries would be a better thing to do.
 * 4) Ya whateveryone said :)
 * 5) It's stupid to force a summary. Use the "diff to peniultimate" buttons to figure out what they did. It's easy.
 * 1) It's stupid to force a summary. Use the "diff to peniultimate" buttons to figure out what they did. It's easy.

Welcoming Committee
I propose a Welcoming Committee  that will be run by yours truly. The welcoming comtiee will make sure Every User gets a welcome, welcoming will not be restricted to just Committee members everyone can help. The Committee will also help users with user stuff and mariowiki stuff, a Committee member will have had to be aroud for a while, be able to handle stress, and great knowledge of WikiSyntax. I see how this Committee will do no harm, besides all it will do is help. Proposer: Deadline: 15:00, 24 June

Support

 * 1) Seems like a good idea.
 * 2) Hk -- Erm... Yeah. Newbies are important. We all go through that stage.
 * 1) Hk -- Erm... Yeah. Newbies are important. We all go through that stage.

Comments
Bean, you need a better reason than that, and I already said we could help newbies without a committee, Hk.
 * I end up helping everyone, it'd be nice to have some guys that can help too, and if we have an "unofficail Comitee" why not make it offical, this will end up helping the wiki and making it better.
 * Well, I don't think it should be run by anyone. A committee is usually run by everyone. And if everyone can participate, it isn't really a commitee.
 * But they don't, and now they'll ask the people in the Committee.

Removals
None active currently

Miscellaneous
None active currently