[Princeton]

Here's what I think should be done:

• NEW RELEASES should be APPROVED HACKS.
• All hacks are sumbitted into BETA HACKS forum for review/approval.
• Judges and members review hacks to make end-product optimized and approved. Upon approval hacks are "moved" to APPROVED HACKS.
• Judge's comments are highlighted (using vbcode so that coders/members) can distinguish who is a judge.

Not a very viable option because that would mean that we are to either review every single hack that is released, and thus it's sort of an enforcement (ie. hack authors have no choice anymore about whether they want their hack reviewed or not). That, or we are to not review any hacks at all, which defeats the whole purpose of this plan.

1. The "rating" system does not necessarily have to be open to all members. I never said it should. On the other hand, the BETA HACKS forum SHOULD be open to ALL members (which it is).
2. By entering BETA HACKS forum, a member already assumes that hack may not be up to par. If a hack is submitted in BETA HACKS forum any member can use such hack at their own discretion. At the same time, "judges" will not have a backlog of reviews to implement at any one time. Isn't the BETA HACKS forum available to coders for such a review? Will judges install and test all hacks?
3. This system will make any hacks immediately available to everyone. BECAUSE, at any one time you cannot gaurantee that all "judges" will be available. As the saying goes, anthing can happen.
4. Furthermore, any hacks not approved may discourage authors to submit additional hacks or requests a review. At the very least, submitting such a hack into the BETA HACKS forum will allow authors to improve such hack using recommendations from everyone especially the "judges".
5. Upon approval, not the coder; but, "judges" may move such hacks to APPROVED HACKS.

As ADMINs:

• You should think about the workload.
• You should think about usability.
• You should think about how people behave/react.
• All criticism is good for coders. A critique made for one coder can and will help other coders. However, a guideline should be created on "how" to critique. We do not want people to degrade others or feel degraded.
• There should be a defualt beta hacks questionaire for judges; and, answers should be visible on hack page (showthread) with comments on how to improve.
• I believe, also, there should be a usability factor. Not to determine "approval"; but, to make aware to all users who are not familiar with what is usable. How usable is this hack?
• There should be a "probationary period" for members who are found to go against these rules. To let a member know that they are in probation, admins should change style to reflect a "probationary period". For example, a red highlighted border on page; and, for usabiltiy purposes the written words "You are in probation ... read more here" with a heading style. It will be used as a reminder to what could come after --> BAN.

Here's a scenario:
Upon the release of VB3 RC1 an influx of new hacks will be submitted for approval. Why? Because, all coders want to release a clean and optimized hack. Will your reviews be available instantly? Or, will coders have to wait-in-line to get such approval? And, will such hack be available online without a seal-of-approval?