Rules
- Each team must have 4 hackers. All team members must have been accepted to Hack the Student Life by IEEE U of T. Registering through Devpost alone does not qualify a team member as a registered hacker.
- All team members should be present at the hackathon venue for the duration of the event.
- All work on a project must be completed at the hackathon within the time indicated for hacking.
- Teams can use ideas generated before the hackathon, but must not re-use any tangible material or code from previous projects.
- 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 hackathon and will result in disqualification.
- Adding new features to existing projects is allowed. Judges will only consider new functionality introduced or new features added during the hackathon.
- Teams must stop hacking once the hackathon has ended.
- Projects that violate the Code of Conduct will be disqualified.
- Teams can be disqualified from the hackathon at the organizers' discretion. Reasons for disqualification might include but are not limited to breaking the hackathon rules, breaking the Code of Conduct, or other unsporting behaviour.
Submission Requirements
- What to enter. Hackers must submit a link to their project (i.e., GitHub repository) along with a comprehensive description detailing the problem addressed, a <1 min working demo, the solution proposed, and how AWS services are utilized. The Project Story section of your Devpost submission will prompt you with headings that make for a strong description.
- File Upload. While hackers can upload one file, such as a ZIP file containing project materials, it is not mandatory unless specific assets need to be shared for evaluation.