vBulletin 3 Hacks & Quality Assurance at vB.org

[Velocd]

The ratings aren't going to be made public, so that should ease some of the verbal abuse in competitions.

[Xenon]

Originally Posted by []\[]emesis

I fully support it. I think a 1 to 10 scale is just fine. I think it would be best if it was right down to the wire in the rating system. Like 7.6 Rating not just 8. Im sure you know what i mean, im a bit tired myself. lol

There should also be an area where not so great coders can post hacks too as well. Of course with this in mind, making sure all users know that this isnt the best coded hack.

noone will stop users from releasing hacks, even if they are bad coded.
it should just be visible to users that a hack is problematical/easy/good coded/well optimized or something like.

[N9ne]

Originally Posted by Velocd

The ratings aren't going to be made public, so that should ease some of the verbal abuse in competitions.

That's ok then.

As for the rating system, I think a % would be suitable, if not, scale it down to x / 10.

[KuraFire]

Originally Posted by N9ne

That's ok then.

As for the rating system, I think a % would be suitable, if not, scale it down to x / 10.

Again, ratings themselves will not be made public, not to the hackmaker nor to the general public of vB.org.

A Hack will either be approved or not approved. The Hackmaker will hear which aspects of Hacking/coding could be improved (whether the hack is approved or not), but (s)he will never hear the exact rating / score.

Why not? People will always get into arguments when they see a score. There will always be people who disagree with a certain rating, then there will always be others going around saying "my hack is better than yours because I got an 8.1 and you got a 7.5!", then you will have people trying to appeal to a decision and get a second opinion and what not. When you only release YES/NO approved to the public, there is very little to make a fuss about. And that's what we want - we don't want to cause a ruckus for each hack, we want things organized, clear, and useful. A big heated discussion isn't useful, nor well-organized. A set of guidelines on where you can improve on, is.

That said, we will also provide an extensive 'document' with help, tips and guidelines on how to make hacks, along with Kier who is writing such a thing already (last I heard).

As stated in the announcement, we want to improve the overall quality of all hacks released on vB.org, and we would most like to be doing that without causing a lot of fights/arguments among the crowds.

[sigh]

I'm a pretty basic php & MySQL coder - not up to hacking standards, but ok for installing them.

I'd REALLY appreciate this system, since I like adding hacks to my board, but need to keep it stable & secure.

Great idea!

[TECK]

Originally Posted by Xenon

noone will stop users from releasing hacks, even if they are bad coded.
it should just be visible to users that a hack is problematical/easy/good coded/well optimized or something like.

Thanks Stefan, exacly my point.
People can release hacks galore if they want to compete in "some" competition... but if we have an input from people with experience, we can decide if we should wait or go for the mod.

I will even go one step further. Should we make the author being not able to see the comments? Not sure if it's a good idea...
This is with 2 sides... If you don't see the comments of people, you cannot get upset...
However, how do you learn then from the coding mistakes? I'm sure you guys will find the right balance for it.... Let me know please.

[assassingod]

Originally Posted by TECK

Thanks Stefan, exacly my point.
People can release hacks galore if they want to compete in "some" competition... but if we have an input from people with experience, we can decide if we should wait or go for the mod.

I will even go one step further. Should we make the author being not able to see the comments? Not sure if it's a good idea...
This is with 2 sides... If you don't see the comments of people, you cannot get upset...
However, how do you learn then from the coding mistakes? I'm sure you guys will find the right balance for it.... Let me know please.

Yeah, stopping the author view the comments makes no sense because it then defeats the purpose of the system

[NTLDR]

Originally Posted by assassingod

Yeah, stopping the author view the comments makes no sense because it then defeats the purpose of the system

Its my understanding that hackers will be shown where they have gone wrong and pointed in the right direction so they learn from their mistakes and can improve

[Erwin]

TECK, please PM me. Did you get my email? You have PM disabled so I cannot PM you.

[futureal]

A rating system would need to be adjustable as future incarnations of a hack arrive. If a bug-ridden 1.0 is replaced by a stable 1.1 (or whatever) then it may not deserve the potentially shoddy rating it received at the onset.

Feedback should be appreciated by any hack author (I know I appreciate any that I receive) but I am not sure that public critique is such a good idea (beyond the rating). If it were up to me, I would leave that private for the hack author. Having somebody put a lot of work into something only to see negative comments from experienced coders in public is not going to encourage them to keep working on it. Especially because something that takes me 20 minutes might take someone else 4 hours, or might take Chen 53 seconds, and so on. The chance of people thinking that other, more experienced hackers are "talking down" to them is high.

I think a publicly viewable stability rating (or whatever you want to call it) would suffice, along with private comments to the author about why such a rating is deserved and what he/she can do to improve upon it.