All materials submitted in connection with the Hackathon must be in English or, if not in English, the Maker must provide an English translation of the demonstration video, text description, and testing instructions as well as all other materials submitted.
An Eligible Individual may join only one Team. If a Team is entering the Hackathon, they must appoint and authorize one individual (the “Team Leader”) to represent, act, and enter a Submission, on their behalf. By entering a Submission on the Site on behalf of a Team you represent and warrant that you are the Representative authorized to act on behalf of your Team.
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 it with your team in advance. 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 can use an idea they had before the event.
Teams must submit the hack within the provided time limit. However, teams are allowed to debug and make small fixes to their programs after time is up. e.g. If during demoing your hack you find a bug that breaks your application and the fix is only a few lines of code, it’s okay to fix that. Making large changes or adding new features is not allowed.
You must treat all team members, competitors, judges, coaches, volunteers, etc, with respect and courtesy, abiding by the code of conduct.
Your Submission and all components thereof must:
Be your (or your Team) original work product.
Be solely owned by you or your Team with no other person or entity having any right or interest in it.
not violate the intellectual property rights or other rights, including but not limited to the copyright, trademark, patent, contract, and/or privacy rights, of any other person or entity.
Teams will have all rights and own the IP of the product. However, all code needs to be in the public domain (open source) so that it can be evaluated by the judges.