[Zach]

I have not read through all of this yet - but its a great idea, and maybe this was already mentioned, or planned, but it seemed the first half of the posts seemed to get to caught up in becoming an English teacher with a red pen.

I think the idea is awesome - but I think that when being reviewed that it should be more looked at not as a review or grading process, but as a finalization process. Most hacks are really not that big. Some are, but most are not. If there is something wrong with it - lets just fix it, give feedback of what was done, why it was done, and then release it as a completely solid piece of work - with no mention of any changes made or not made between submission and release.

The last part would be crucial as otherwise people would be scared of having to much red ink in the public eye - which I think you guys are trying to cover already anyway.

But again - if this process was used to just take out that extra two db calls and tighten stuff up, use more standard variable names, etc, this would be something spectacular for the community. If it became a king on high, you pass, you fail, thing - even if that was kept private to everyone but the person that "failed", it would kill things - it would create a three class system - the judges, the ones that are always accepted, and the ones that always fail. While the guys that didnt get accepted would be only known to that one person - that person is going to notice that some Pot Smoking goody goody (sorry overgrow - I have been around to long and still get a kick out of your forums topic and your importance in this community) - but anyway notice this pot smoking goody goody is always approved, while they are not - - which would start to build up resentment in some, and discourage them from submitting more.

done rambling - just full of my two cents remarks today -