These rules are subject to change. The final rules will be given out on the day of the event.

• All design elements, code, hardware builds, etc. for your project must be created during the event. Third party tools and frameworks are allowed as well as your normal tooling (Gulp, Yeoman, Composer, NPM, Bower, etc.). While you may not begin coding in advance, you can plan and discuss with your team in advance. Written documents and design sketches are allowed.  You may also incorporate pre-existing material that is freely available to the public into your project, such as public domain images, Creative Commons music, open-source libraries, existing APIs and platforms, and the like.
• Teams must be comprised of 2-3 people.
• Only five of the competing teams will present their projects in the final round of judging at the end of the event. The presenting teams will be determined by an initial round of judging that will take place during the final 1.5 hours of the event.
• Teams that make it to the final round will be given up to five minutes to present their finished project to a panel of judges.
• At least one team member must be physically present during sign-in, and one must be conscious and present to present the project to the judges during their assigned presentation time. A team of three may have one remote member who never works from the hackathon location. The other members must spend the majority of their design/coding time at the hackathon location.
• Any intellectual property developed during the hackathon will belong to the team that developed it. We expect that each team will have an agreement between themselves regarding the IP, but this is not required.