MarioWiki:Proposals

 http://img33.picoodle.com/img/img33/9/9/17/f_propcopym_9045f2d.png 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. Signing with the signature code (~) is not allowed due to technical issues.

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 vote and discuss on the issue during that week. The "deadline" for the proposal is one week from posting at:
 * 3) Monday to Thursday: 17:00 (5pm)
 * 4) Friday and Saturday: 20:00 (8pm)
 * 5) Sunday: 15:00 (3pm)
 * 6) Every vote should have a reason accompanying it.
 * 7) At any time a vote may be rejected if at least three active users believe the vote truly has no merit or was cast in bad faith. However, there must be strong reasons supporting the invalidation.
 * 8) " # " should be added under the last vote of each support/oppose section to show another blank line.
 * 9) 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.
 * 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) Proposals can not be made about System Operator promotions and demotions. Sysops can only be promoted and demoted by the will of Bureaucrats.
 * 12) 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.

The times are in EDT (UTC -4:00), 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 Saturday night at 11:59 PM EDT, the deadline is the next Saturday night at 8:00 PM. If it is a minute later, the deadline is a day plus 15 hours (Sunday), as opposed to a day minus 4 hours.

CURRENTLY: , 27 2024 (EST)

Create a Dispute Resolution Committee
So, I've been browsing Wookieepedia and have noticed they have a sysop's noticeboard. I think we should have something like this to alert sysops of important things and solve disputes between users. We would call this the "Dispute Resolution Committee".

Proposer: Deadline: March 16, 2009 17:00

Oppose

 * 1) - A public record of issues may do more harm than good. Sysops can already discuss things on their forum board.
 * 2) Per YY.
 * 3) - Per YY.
 * 4) - YellowYoshi398 does have a point. So per YY.

Comments
I think we need this so regular users may alert sysops, since regular users do not have access to the sysop boards.
 * I used to and still do use the main talk page when the matter is public, and before I was buro or sysop and I wanted to keep something quiet (like an interuser dispute) I just dropped a note on a sysop's page. If this feature was updated and I had something I didn't want to get full blown I'd probably just use the sysop's talk page anyway... What I want to know is, how would it be different from the main page?  We still have a smallish Wiki so I think we might be able to make do with that. :)

Removals
''None at the moment.

Splits & Merges
''None at the moment.

Change Log-In
1 hour ago I just had a horrible experience.My computer had somehow forgot my password for this Wiki,thus I took 1 hour trying to remember it,as I had lost the piece of paper the password was written on.So to stop this experience happening to anyone else,we could maybe have two options,like a question? Instead of a password? Are we allowed this? Do you want it? I'll be waiting!

Proposer: Deadline: March 16, 2009, 17:00

Something Different!

 * 1) Huzzah! per above.
 * 2) - SOunds good, maybe adding a security question

Leave as is!

 * 1)  - Um... You guys do realise this will lead to sockpupeting and people being able to log in as other users. So this is one heck of a bad idea.
 * 2) - Umm, no. You can store your passwords in like a secret text document, but losing your password would be kinda silly amirite? If you choose a password that you cant remember well, then choose a password thats both secure and you can remember it from the top of your head. Mistakes happen, I know. I don't think there's a MediaWiki extension for a second log-in thingy.
 * 3) - If someone forgets their password, it's their fault and their problem. If you know you have memory issues (AMNESIA for example...), then save the password in a text document somewhere on your computer. Users must take responsibility for their own account issues.
 * 4) - Per all.
 * 5) - It's better to keep the passwords rather than just add questions, because, as Nerdy Guy said above, this would lead other users into logging onto accounts that don't belong to them, and therefore hacking in to them. Per all.
 * 6) - Per all,We rather have an user who have to make ten accounts because the user forgot the password for the other nine,other then to block an user for what someone else did.

Comments
Is the password thing something all Wikis HAVE to do? if it is,ignore this.

Hmmm... I'm not entirely sure I understand the proposal. Do you mean two accounts? That's what I think you are saying.


 * No, it means two ways to log in
 * You're going to have to specify that second way. You mentioned security questions as an idea in the proposal, but right now we're just voting for "something" to happen.  You'll need to reword it, otherwise we're voting on whether or not to give you a blank slate to work with as far as log ins are concerned.  22:44, 9 March 2009 (EDT)

Ok,I added an example.This IS my first proposal.
 * Much better - and I'm sorry if I came off strict. :)

Miscellaneous
None at the moment.