[MetaBUIDL] Hackathon Judging Rubrics

[ilblackdragon]

Create set of rubrics and a way for judges to fill in their opinion and create final scores. Account for general prize, work & play and also any local nodes.

[think-in-universe]

Here is a draft version of Hackathon Judging Rubrics for review: https://docs.google.com/spreadsheets/d/1jFRx0jYqkmdVry2MKz5EMsbYcMyszb9gUDM9vHS9VhQ/edit?usp=sharing

[think-in-universe]

For judging submission, one way is create an airtable table for the judges to submit their scores. (rows are the projects, and columns are the judging categories). need to confirm whether the design work well with airtable.

[starpause]

@think-in-universe great work on this! I've taken a stab with these changes:

• "feasibility" rolled into Value & Impact (those two sections were saying the same thing)
• "Quality of Implementation" broken into "Functionality" and "Fidelity". They both still have a score of 0-20. Fidelity is something we want to highly reward since that's what will convince web2 users to stick with a product. It also captures Sasha's comment requesting a "wow factor" rubric.
• Technical complexity score reduced to at max of 10 points. We're more interested in impact than if something has a million gears under the hood, but do want to avoid teams submitting freshly forked and unmodified repos.
• Presentation section has key deliverables and if all of them are present it's possible for a team to hit 10 points.

[think-in-universe]

thanks @starpause

I agree with most of the enhancements, except I think we can still keep a separate Wow Factor category since it's not just about UI. So I suggest we take 10 points out of Fidelity and create another Wow Factor category.