Team Formation

  • Your team may consist of up to four participants. You may also work individually, but you will be judged at the same standards as any other team.
  • All team members must be registered participants of HackKU and must check in and be present at the event.
  • Don’t worry if you don’t have a team yet! There will be a team formation event after the opening ceremonies to find others to hack with. Additionally, there will be a teambuilding channel on Discord to find teammates.

Project Specifics

  • All code for your project MUST be written during HackKU, between the hours of 8PM on April 14th and 8AM on April 16th.
  • Your entire project must be written and created by only the participants on your team
  • Your code must be made public on GitHub for judging purposes. We will use your GitHub to verify that all of the rules and deadlines of the competition were followed. All teams may be subject to a code review.
  • All submissions will remain as the intellectual property of the individuals that created them.

Submission

All projects will be submitted via Devpost. Project submissions must include a Github link to your source code. The link to HackKU 2023’s Devpost page will be available closer to the event.

Demos
  • Teams competing for prizes must give a short (5-minute) live demo of their project to judges.
  • All teams are encouraged to demo, even if your project is not complete. There is no downside to demoing your project! This is a chance to show off what you accomplished and learned during HackKU.

Judging Criteria

  • Theme: If you are competing on the themed track, your project should follow this theme. This does not apply if you are competing on the general track.
  • Technology: Considering your prior knowledge, the judges should be impressed by what you accomplished. Your project should have challenged you to explore new technologies and you should have learned something new during HackKU
  • Completeness: Keeping in mind that your project was built in 36 hours, your project should be reasonably usable and somewhat complete.
  • Innovation: Your project should not be an exact re-creation of an existing product, it should introduce new concepts and expand upon prior ideas.
  • Presentation: Your demo should be clear and concise, and explain your project and how you created it.

Tracks & Challenges

There will be two tracks at HackKU 2023: the General Track, and a to-be-announced Themed Track. Participants must choose ONE track to submit their project on and will compete for the prizes associated with that chosen track.

Code of Conduct

As an MLH-affiliated event, all participants will be expected to follow the MLH Code of Conduct. Also, don’t spam Discord!