• All hackathon submissions must have a Devpost with a project video included.
    • You must have the Devpost created prior to the “stop hacking” deadline, but you can continue working on it until the Devpost update deadline.
      • This also applies for the project video.
    • Your project video should be at least 30 seconds, and you should treat it like an elevator pitch for your idea.
    • Not having a project video (or having one that provides so little value it may as well not exist) will result in a penalty for your project. Coding isn’t the only part of a hackathon!
  • Premade assets acquired from the internet should be attributed properly according to their licensing.
    • It is recommended to use assets with permissible copyright licenses such as Creative Commons, MIT, Apache, GPL etc.
    • Copyright/licensing information should be included in your Devpost or Github repository.
  • Any use of Generative AI for asset creation should be noted in your Devpost.
    • Acceptable: “Generative AI was used in this project for certain assets.”
    • Good: “Some assets were created with Midjourney.” (Specify AI tool used)
    • Excellent: “The app icon, and all images used in the app were generated using Stable Diffusion.” (Specify specific assets)
  • No work must be done prior to the commencement announcement at the opening ceremony.
    • This includes code, GitHub repositories, assets, and other materials. Premade assets or code (e.g. StackOverflow, stock photos, code written for past projects) are permitted for use.
    • [EXCEPTION] Assets created prior to the hackathon for the purposes of 3D printing will be permitted as long as they were created after May 27 12:00AM (Monday). The 3D printing of any materials is permitted after this time as well.
  • No coding work can be done after the “stop hacking” announcement on the second day of the hackathon.
    • After the “stop hacking” deadline, you are permitted to do the following:
      • Updating your Devpost & working on your project video
      • Updating/fixing documentation in your GitHub repo
      • Making last-minute repairs, additions, or modifications to hardware.
      • You may be allowed to make minor changes to your demo for judging, such as UI adjustments or bug fixes, but please ask an organizer first.
      • Absolutely no work on your project can be done after the “Devpost/Project video” deadline.
      • After this deadline, whatever you have completed is considered final and ready for judging, and you may no longer make changes.
      • Exceptions may be offered on a case-by-case basis.