Feedback System & Beta System

[hambil]

Rather than make this two topics, I'm just going to combine it into one.

Feedback System
We really need this. There is already an unspoken contract between hack authors and hack users.

• Authors will test their code (more on that in the beta part of this thread)
• Authors will follow the code guidelines layed out in the vBulleting Manual
• Authors will support their hacks

• Users will click install
• Users will not remove copyrights or modify hacks without permission

I'm sure there are other things I'm not thinking of. An eBay like feedback system where authors can reward users for good behavor, and warn other authors about bad behavor, and users can do the same for authors, seems like a very good idea to me.

Beta System
The "beta" checkbox is not enough. No matter how well I test bugs will be found by users because there are many ways to use vb, and many other hacks to interact with. Having to release a hack as 'beta' and let anyone download it makes no sense.

I recommend a beta system where a hack can be released as a true beta, and users can ask to participate in much the way group join requests work. Combined with the feedback system Authors can then let other authors know if a user is a good beta tester or not.