SmashWiki talk:How to Test Propositions

I'm not sure this is a good idea.

Maybe we should test it first? DoctorPain99 15:33, 30 March 2014 (EDT)

In all seriousness, though, I don't see why we need this, and it could cause a whole fuckton of problems, so oppose. DoctorPain99 15:34, 30 March 2014 (EDT)

Nope Bad suggestions don't magically become good suggestions just because we "tested" them, and that's the only case where this would have any sort of beneficial impact. Toomai Glittershine The Producer 15:51, 30 March 2014 (EDT)

Oppose Don't be doing this just to try and get your other failed proposals to suddenly pass. Scr7(talk · contribs) 15:53, 30 March 2014 (EDT)

Oppose I have no idea what your talking about. "Testing" propositions? Something just might cause disaster... Dots (talk) The Goldeneye 16:12, 30 March 2014 (EDT)

Edit conflict: Alrighty then, I guess I'll have to reply to all of you individually...

@Doc: Yes, it MAY cause "a fuckton of problems" depending on what proposal is being tested, but that's why the testing period is only temporary, so if it doesn't work, we can cut it off early and deem it a bad idea.

@Toomai: I don't believe I said anything about bad suggestions turning into good ones just because they were tested. All I'm saying is that even a small amount of potential can be found in even the shittiest of proposals that have ever happened. And to possibly increase that amount of potential, we should test things that require consensus in order to find it. Also, I may not have mentioned it in the proposal, but proposals can still fail even after they get tested, so your complaint is quite frankly a non-issue.

@Scr7: No I am not trying to get my past proposals in by coming up with this one. I am just pointing out that one of the best ways to see if something's as bad or good as people say it is, is to test it out. And if a proposed policy is bad, then it doesn't get accepted. End of story! Also, this isn't just to test out MY past proposals, but ALL proposals that happen here. And once again, just as I said in Toomai's reply, a proposal can still fail even after it is tested, so this will not be a sure-fire way to get my other policies in anyway.

@Dots: If that's the case, then I think I might have to revise this to make it clearer. :|

To be honest, you guys here seem to be getting the wrong idea here, and as I just mentioned, I'll try and make this seem more understandable. MeatBall104: Get In Mah Belleh!!! 16:17, 30 March 2014 (EDT)

It may be "temporary" but damage will be done and we'll have to fix it. New users will get confused about what's going on, pages might have to be moved then moved back, if the username policy had been tested then failed, we'd even have to change usernames and then changed back. What you're proposing is too much of a logistical nightmare to be useful. DoctorPain99 16:26, 30 March 2014 (EDT)

So should we test this proposition about testing propositions by testing testing propositions? But on a serious note, this just seems like you're saying that all/most propositions should be implemented despite the opinion of them, and then after we realize we were right that they are bad, we clean up the mess that could have been avoided by just trusting our knowledge that they were bad. Even the wording makes it sound like you're just saying "opinions on proposals don't matter and we should just do them anyway." Some proposals are bad and should not be put in place. Others are good and should be put in place. We don't need to make a huge mess every time someone has an idea to know that the idea is bad. Ryxis (talk) 17:18, 30 March 2014 (EDT)