Theme

The theme of our event is CIVICS.

The dictionary definition of civics is “the study of the rights and duties of citizenship”, but what we are looking for is a solution to a civics-related problem in the community. This means that your project should be something that benefits the community, such as improving civic engagement. The topic is broad on purpose to give you all more room to innovate and demonstrate your creativity.

 

In addition to our regular, in-person hackathon rules, the rules below apply to our online hackathon.

  1. <hack> Cupertino judges and City of Cupertino staff have the final decisions on all matters.
  2. Ideas do not have to be original, but the implementation must be original. Open-source libraries, frameworks, and starting points are allowed, but teams must disclose what they created at the event, and what was already made. Judges will only consider new additions made during the hackathon. We have a strict no-plagiarism policy. We will require a copy of the code to review.
  3. All work submitted will be open source.
  4. Late submissions will not be accepted.
  5. 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 tools. While you may not begin coding in advance, you can plan and discuss it 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.
  1. 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. While you may not begin coding in advance, you can plan and discuss it 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.
  1. Teams may consist of 1-4 people. We will be using Devpost submissions to determine final teams/projects.