Build. Learn. Grow.

RevolutionUC is a student hackathon in which we invite students from across the midwest to partake in a weekend of code, community, and self-improvement. You don't have to attend the University of Cincinnati and you don't have to be a computer science major or engineering student. We're looking for people who share our passion to do awesome things with technology.

You can find more information about RevolutionUC at https://revolutionuc.com/

For information about the schedule for the event visit the schedule page at https://revolutionuc.com/schedule

View full rules

Eligibility

RevolutionUC is open to all college and high school students 16 or older. Before any hacking begins we require you to sign a waiver, which will be emailed to all registered participants prior to the hackathon. If you are under 18 you will need a parent or legal guardian to sign the waiver.

View the FAQ page on the event's website (https://revolutionuc.com/faq) or contact us for more details.

Requirements

  • Be prepared to present your hack to multiple judges in four minutes
  • Demo the project you've been working on for the past 24 hours
  • Be proud of what you've worked on!
  • Tell us what all you've learned while hacking (in only three minutes!)
  • Check out the judging criteria (Projects are judged based on creativity, learning, and functionality)
  • Tell us if you've used an opt-in or sponsor prize category
  • Be sure to tell us if you've used any of the MLH sponsored hardware for you hack

Please have your Devpost submission in by 12:00 PM on SUNDAY, February 23rd to facilitate judging.

Initially, we only need your table number, group name, and the prize categories you're submitting to.

Your project will remain editable until 1:30 PM on SUNDAY, February 23rd.

Use the table number at your current table when asked - the table number you write down is where you will be judged - don't move!

Judges

John Doe

John Doe

Judging Criteria

  • Learning
    Did you learn something new? Have you attempted something you haven't before? Did you challenge yourself?
  • Execution
    How well did you achieve what you set out to do? How polished is your project? Are the features you included functional and thorough?
  • Originality
    Did you think outside of the box? If it's been done before, what did you change? How did you improve it?