Dates

This hackathon spans Saturday, February 7th to Sunday, February 8th. Submissions should be made by 10:00 AM ET on Sunday, February 8th.

Eligibility

Any college student registered for DevFest may participate.

Each team MUST have 1 – 4 members.

Project and Submission Requirements

For all projects, the following is required: 

For design projects: Must include product graphics (i.e. screenshots of a prototype)

For software projects: Must include product code.

DevFest will not be accepting any hardware hacks.

Judging Criteria and Winner Selection

  • Completeness
    The extent to which the hack has been tangibly created. Hacks with working webpages, GitHub repositories, and (if needed) prototypes are strongly favored.
  • Capability of solving a real-world problem
    How feasible is the hack in solving the problem it is targeting, and how well does it do so?
  • Creativity
    How original is the solution compared to other hacks and products available on the market?

Please see below for our official Code of Conduct.

Media Disclosure Agreement: This agreement allows DevFest hackers to opt out of media disclosure to DevFest for any purpose. Both parties agree that hackers can withdraw media content usage consent at any time.

Rules

Spirit of the Competition

Remember that hackathons are like marathons. Some people go to compete, but most people take part to better themselves and have fun. Whatever the reason is you're at a hackathon, make sure you're upholding the hacker spirt and Community Values by collaborating with other teams, helping beginners, and having fun.

Hackathon Rules

All participants agree to uphold the MLH Code of Conduct to keep hackathons safe, welcoming spaces for everyone.

All team members should be actively participating in the event.

Any projects submitted must be started and completed during the duration of DevFest, and only submitted to DevFest (no other hackathons).

Teams can use an idea they had before the event, existing ideas, etc BUT all code and other project materials must be original. If open-source code is used, it must make up no more than 30% of the codebase of your project. 

Teams can use libraries, frameworks, or open-source code in their projects. Working on a project before the event and open-sourcing it for the sole purpose of using the code during the event is against the spirit of the rules and is not allowed.

Teams must stop hacking once the time is up, and all project assets, including video and full code (GitHub repository), must be uploaded at this time. 

Teams can be disqualified from the competition at the organizers' discretion. Reasons might include but are not limited to breaking the Competition Rules, breaking the Code of Conduct, or other unsporting behaviour.