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) There are two topics that cannot be decided on through a proposal: the first is sysop promotions and demotions, which are decided by Bureaucrats. Secondly, no proposals calling for the creation of Banjo, Conker or Sonic series articles are allowed (several proposals supporting them have failed in recent history).

The times are in EDT, 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: , 28 2024 (EDT)

New Features
''None at the moment.

Removals
''None at the moment.

L Block
I was stopping by to check on blocks recently, and I saw that L Block had almost no info. I have a feeling L Block should be merged with M Block.

Proposer: Deadline: October 23, 2008, 17:00

Don't Merge

 * 1) - I have 3 reasons why it shouldn't be merged. 1) It is officially named, 2) It affects gameplay differently, no matter how slight a difference it has from the M Block, 3) It is almost the same length as the M Block. With an expansion, the articles will be fine separate.
 * 2) - I agree with Stooben's third point.  Plenty of articles on this Wiki are short and would, in their current states, be better merged, but there's so much potential for those articles that it would be a waste.  I'm thinking of minor characters from Mario Tennis: Power Tour for example.  Yeah, I know that after I voted for the merging levels into world articles it probably seems weird that I'm opposing this, but that was a presentation thing, whereas this is not.
 * 3) - Per all.
 * 4) - No way there two differnt boxes.
 * 5) - Ay. Per all. L Block can be expanded into a good-sized article. And iggykoopa, I do believe you are voting in the wrong section.
 * 6) *sigh* There are different blocks that are officaly named. They can't be merge those blocks aren't the same.

Mame Block and Bagubagutchi
I recently passed by Mametchi's page and found a user had merged Bagubagutchi and Mame Block in to the one article. We need the pages as someone might need the info.

Proposer: Deadline: October 15, 2008, 20:00

Spilt

 * 1) Per my proposal

Comments
Umm I think they have a proposal to merge all those items together since they're stubish.
 * Yes. And it passed. Besides, you can find all the info... In the one article. This proposal is not necessary.

Userbox Page
Recently, I stopped by the userbox page and found it to be absolutly unacceptable. Users add new userboxes at will, and often don't care for things such as, I dunno, GRAMMAR? So, I'm prposing that we lock up the Userbox page or at least trim it down. If you want to make a new userbox so badly, don't place it on the main page.

Proposer: Deadline: October 15, 2008, 17:00

Don't lock
REMOVED VOTE: - Right now I'm busy enough operating the rest of the Wiki, but maybe the other sysops aren't.  Regardless, I have to say, userboxes themselves are useless, so I don't see why a useless userbox would be a problem. Plus, what are your criteria for determining whether a userbox is useless or useful? Since other sysops are cool with trimming the page down, I no longer object. However, I'm keeping this vote here for everyone who "per'd" me.
 * 1) Per myself. Anyways why lock just because if some userboxes seem useless. There just for user whom want them. You don't have to use the new ones that just pop up. The userboxes page is for every user to post a userbox (as long as there aproperate.)
 * 2) - Per Stumpers' original vote. Userboxes are epic, and someone may want to create their own.
 * 3) - As long as the userbox is appropriate, I don't see the problem.  Besides, even if that article is locked, we'll still be able to make our own personal userboxes for our user page.
 * 4) - I really see userboxes as an eyesore, nor would I ever use them. However, I do see where they may be appealing to others. Quite simply, the fact that they're constantly being used entirely makes up for the fact that they're cheesy and an eyesore.
 * 5) - More will get done if dedicated Users of all ranks can hack away at the garbage (as opposed to just the Sysops, who have more important things to do than this inconsequential community fluff).
 * 6) - As long as the grammor improves,anyways i make tons of userboxes.
 * 7) - First, Timn, if you want better grammer in the userbox page, you should spell it right.  Next, the userbox page is alright, but we should delete duplicates.  The ones we delete do matter though.  If one is a more complicated and desired one, the one that is less complicated and desired.  Get the picture?
 * 8) - A dreadful idea. I can hardly figure how to do a userbox and I'm trying to put some in my page. If the page is locked, I would be unable to access it and, therefore, I would have to keep my personal page as simple as it is right now. I suggest that it is improved.

Trim down

 * 1) Per what I said.
 * 2) -Both sides have a good point we should have criteria for userboxes {ie:This user likes luigi. OK. This user is friends with [insert username here]. NO} It shouldn't be that hard delete some keep others and we really need to trim down the userbox section other [I had to remove my own cose the page had trouble loading].
 * 3) - That page has been chaotic for quite a few months now. Many of the userboxes on there aren't needed, as they are simply edited from other similar userboxes. Also, the "This user is friends with __" have absolutely no reason to be on there; these userboxes, if created, should be created only for users to give to their friends. (Just like I used to do.) The page takes ridiculously long to load due to the mass amounts of images and coding on it as well. It's a MarioWiki page, not a User page. It's a fine page for referring to how to make basic userboxes, (ex: This user is an advanced gamer), etcetera. These userboxes that say, "this user's favorite character is Mametchi/Luigi/Francis/whatever" are entirely unnecessary – there only needs to be one userbox for that "genre" of userboxes – This user's favorite character is ___. The userbox can be edited from there to the user's liking. Take my userbox tower for example: Most of the userboxes on there were created/edited by me, but I don't recall ever putting them in the userbox page.
 * 4) - This is definitely something that needs to be done. As Stooben said, one genre of userboxes that can be customized to the user's liking. Specific, one person/object/etc. userboxes should not be put of there.
 * 5) - Per Stooben. Took the words right out of my mouth.
 * 6) - I'm switching sides to back Rooben... that's the second time this week.  Per Stoob.
 * 7) - Per St00by.
 * 8) - Per all.  Strange as it may be that I don't even have a page FOR userboxes yet I have an opinion, really, failure at grammar and over-complication bother me.  That, and I have actually been turned off of making mine based on how many userboxes there are.
 * 9) - Per Stooben. I think users can create their own userboxes, but it isn't necessary to put them in the userbox page.
 * 10) - Per all. Besides, altering existing Userboxes on one's specific User Page is fairly easy, so if someone really wants to say something unique, they still can; while those of us with cruddy computers can still see the general boxes without fear of freezing.
 * 11) - Per all

Comments
Okay, I take that back. But if you had stopped by before I cleaned it up, you'd see how atrocious it's become.
 * Rather than locking the page, what about just eliminating all of the excess userboxes? Take this, this, and this for examples: they could easily be trimmed down to basic userboxes that could be edited to a user's liking. Also, if there was a "Trim Down" option on this proposal, I'd vote for it.
 * Same here. The Sysops have enough things to do without having to worry about something as frivolous as Userboxes. Simply let the Users who care about Userboxes keep them tidy, and be done with it. -
 * But that's the whole point. The page isn't kept tidy. It overloads the bandwidth with all the pictures and code, and most are used by maybe one or two people: the people that made them and decided to stick them on there. I have plenty of userboxes that I created myself without needing to put it on the Userbox page.
 * Walkazo: You've conivinced my to change my mind. Now that I think about it, sysops DO have better things to do :l Phoenix Rider: Ditto. Palkia47:True, but they still don't need to clog up the page.
 * Since Stumpers switched his vote, I have a question about those who said "Per Stumpers". Since Grapes and Palkia have additional reasoning to their votes aside from "Per Stumpers", would their votes still be valid? With that being said, would Super-Yoshi's vote be the only invalid one?
 * Good question. I assume that we can now take "Per Stumpers" to be "Per what Stumpers' original vote said."
 * Sounds good.
 * Done.
 * Glad I looked at the comments before editing. I was going to point out that anyone who was 'per'ing a now nonexistent vote wouldn't be counted if said vote still read as such when the proposal closed. --

When I feel like making a new Userbox, I just 'steal' one from another User page, or make a new one. I never use that Userbox page, it seems kinda pointless. Like a blunt arrow.
 * Ditto.

Okay, first there's voting on whether or not is should be locked, and then there's voting to trim it down (but no header to vote for leaving it the way it is?). No one's voted on both issues yet, but can we? This is more like two proposals in one, which is a bit... screwy. -
 * I think since we were talking about the sysops being busy, we're not going to want to lock it to all but the sysops... but maybe a new user block would work.
 * Good idea. And I could change the voting choices to "Don't change it" and "Trim it down".
 * Triming down sound better. (Because some computer/Laptops can freeze if there too much kilo bytes.) Plus there is some stupid userboxes like, This User thinks that Luigi shouldn't be called Mama Luigi.
 * Protecting it from the new Users and their userbox-fever is definitely a good plan, as are cutting out some of the more superfluous ones and adding that extra header for the people who disagree. -

Phailure: Just swapping "Don't Lock" for "Don't Change Anything" isn't right: those votes are now misplaced and should have been removed like mine. -

''SuperMarioFan14 You'll be still able to ascess the Userbox page. Lock the page only due one thing and thats make the page unable to be edited.


 * Speaking of your vote, Walkazo, you currently have two votes. Be sure to delete the old one. (or move it as I did my old vote if someone per'd you)
 * Right now I'm voting once on the locking issue, and once on the trimming issue; as I said before, this proposal is messed-up. If it isn't going to be about locking or not locking anymore, but about trimming and leaving it as it is, the sections pertaining to locking and all the corresponding votes should all be deleted. But then the people would need to vote again, and time is running out before the deadline (which brings to mind an older discussion about changing proposals). -
 * Yeah, that was my mistake, I wasn't really thinking about the votes needing to be recounted.

Siblings Template
I've noticed that the Siblings template, though useful, is in need of a change, notably, the fact that, on looking, one cannot actually tell which characters are, in fact, siblings. For example, Mario has two characters between him and Luigi, or on a much more dramatic scale, Dixie Kong and Tiny Kong are on complete opposite ends of the template. Some characters, like Kat and Ana, have this remedied with the word "and" in some form. My proposal, in order to clean this template up, is to do that with all characters with an unlinked 'and' between them, for example, Mario and Luigi. Naturally, this wouldn't apply to, say, the Jellyfish Sisters, as they don't have an and in their name, or to, say, Kat and Ana, who already have an and which is a part of the page name. They would be arranged alphabetically by first character's name, so it would be, say, Mario and Luigi after Baby Mario and Baby Luigi, but before Punio and Petuni.

Proposer: Deadline: October 18, 2008, 20:00

Combine

 * 1) Per above.
 * 2) I had actually thought about doing this, but I was too lazy. :P Per Shrikeswind.
 * 3) Whoa, great idea. That'd definitely organize it a little more.
 * 4) - Per all. I don't think a proposal was necessary, however...
 * 5) - I thought about colour-coding this template a few months back, and even came up with the organizing principle; but I never proposed it because it looked bad. This idea blows mine out of the water!
 * 6) ~Per all.
 * 7) - Per All. This is gonna help s stay organized, too :P.
 * 8) - This is actually a very well done proposal, especially for a first.  Anyway, this would increase the usefulness of the template, and as Walkazo showed us, is plausible and aesthetically pleasing.
 * 9) - Per all.
 * 10) - Always those little bitty things... anywho, per all.
 * 11) - Moo. That's Cow for 'per all'.
 * 12) - per all.
 * 13) - Per all, its easier to look that way

Comments
Jeez, I hope I did this right. My first proposal and I feel like an idiot doing it. Any help would be much appreciated. -
 * You did a good job. ;) Kudos.

Er... Could you link to the template, please? :') I'll go find it myself, but it would be nice for people who newly see the proposal.
 * Here ya go.

As I said in my vote, I already did the research and came up with divisions for the siblings a while ago. I saved my work, and just went through and converted it to this idea, and this is the result. If you like it, Shrikeswind, perhaps we can use it as the new Sibling's Template if (or rather, when) this proposal passes? If there's anything amiss, please tell me. -
 * Nice template! :) It's very well organized. I might have an idea for an even more well organized version of it though.
 * I was thinking the template could look like a cross between this, and what you have as a prototype, but the outcome wasn't real good. So, your way is definitely the better way.
 * Thanks! I was thinking of dividing it up a bit like that too; but yeah, there were too many single siblings, one-link pairs, and small families to make it worthwhile... -
 * That's almost exactly what I was thinking, and no less that's a better way to do it, especially considering, for example, the Koopalings. Thank you Walkazo.
 * My pleasure :) I love template work. -

Miscellaneous
''None at the moment.