All attendees, sponsors, partners, volunteers and staff at our hackathon are required to agree with the following code of conduct. Organizers will enforce this code throughout the event. We are expecting cooperation from all participants to help ensure a safe environment for everybody.

Our hackathon is dedicated to providing a harassment-free experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, nationality, religion, previous hackathon attendance or computing experience (or lack of any of the aforementioned). We do not tolerate harassment of hackathon participants in any form. Sexual language and imagery is not appropriate at any hackathon venue, including hacks, talks, workshops, parties, social media and other online media. Hackathon participants violating these rules will be expelled from the hackathon at the discretion of the hackathon organizers.


  • All teams must have a Team Lead
  • Team Lead is the sole point of contact with organizers
  • Any prizes won will be given to the team lead, to be distributed to the team
  • No remote team members


  • Teams will use BitBucket, GitHub, or similar version control tool for code collaboration
  • Teams will register themselves on Devpost

Presentations / Judging criteria

  • Presentations will be limited to 3 minutes. Projects should be hosted on
  • Only teams comprised wholly of eligible participants that submit their hacks to this devpost, and then go on to demo their hack can win prizes. 
  • What are we looking for?
    • Completeness/polish
    • Does it solve one of the problem statements?
    • Does it solve the needs of Utilities like California American Water?
    • Is it a good solution?
    • Would it make a good product?
  • Everyone likes something pretty. Give us something that we like to look at.
  • Start with telling us what you did, and showing us a demo, then explain the problem afterwords
  • If you don’t finish your project, we understand. 36 hours is not a lot of time. However, don’t make excuses, and go on and on about why you didn’t finish. Instead, talk about what you were able to get done, and where you planned on going. Finishing isn’t the only metric for judging, but if all you focus on is how you didn’t finish, then it will cast a shadow on your entire presentation

Participants will be scored by a point system

  • Judges will use Devpost for voting
  • Teams will be tracked on Devpost

Coding Requirements

  • Teams have until 3:00 PM Sunday to finish coding. There are no restrictions on what form it should take, programming languages or devices. You must build your project during the allocated time.
  • Source code must be disclosed and code repository must be publicly accessible. You are free to use whatever code repository service you want (e.g. GitHub or BitBucket).
  • Preference is for code to be as open source as possible.
  • No prior work. Everyone arrives with open minds, blank sketchbooks, empty text editors, and full hearts (hooking into any DB or existing API is fine).
  • Teams must not do any development work before the competition. You are free to conduct research and generate ideas before the competition.
  • You may use legally licensed material and tools that are freely available to the public. Some examples include: public domain images, Creative Commons music, open source libraries, and existing APIs and platforms.
  • You cannot steal another team's source code

General Requirements

  • It's the weekend and you’re here to hack, not work. Block out your schedule and tell your employer.
  • No non-registered guests allowed.
  • Failure to comply with the Basic Rules can see you removed from the competition and/or expelled from the venue.
  • Please keep your event ticket and badge on your person at all times.
  • The decision of judges is final for determining prizes and awards
  • Please comply with all instructions from Water/Energy Nexus Hackathon organizers
  • Don't be a jerk

All submissions to the 2015 Water/Energy Nexus Hackathon remain the intellectual property of the individuals or teams that developed them. By registering, consenting to the terms of the Hackathon, and entering a Submission, however, the Participant agrees that the organizers and technology partners reserve an irrevocable, nonexlusive, royalty-free license to use, distribute to the public, and publicly display and perform a Submission for a period of one year starting on the date of the announcement of contest winners (August 16, 2015) as an example of work. We encourage participants to open source their projects to both share their hacks with the greater community and promote innovation in this space.


By submitting a 2015 Water/Energy Nexus Hackathon Entry or accepting any prize, you represent and warrant the following: (a) you will not submit content that is copyrighted, protected by trade secret or otherwise subject to third party intellectual property rights or other proprietary rights, including privacy and publicity rights, unless you are the owner of such rights or have permission from their rightful owner to post the content and to grant 2015 Water/Energy Nexus Hackathon all of the rights granted herein; (b) you will not publish falsehoods or misrepresentations that could damage 2015 Water/Energy Nexus Hackathon, Sponsors, or any third party; (c) you will not submit content that is unlawful, obscene, defamatory, libelous, threatening, pornographic, harassing, hateful, racially or ethnically offensive, or encourages conduct that would be considered a criminal offense, give rise to civil liability, violate any law, or is otherwise inappropriate or destructive to 2015 Water/Energy Nexus Hackathon's or Sponsors' brand image or goodwill; (d) you will not post advertisements or solicitations of business; (e) 2015 Water/Energy Nexus Hackathon will not be obligated to pay any compensation to, or permit any participation by, any third party in connection with the use, reproduction, modification, publication, display or other exploitation of any of the content that you submit; and (f) the content submitted by you does not contain any viruses, Trojan horses, worms or other disabling devices or harmful code.

By posting or submitting a 2015 Water/Energy Nexus Hackathon Entry to the Contest (regardless of the form or medium of such content), you hereby grant 2015 Water/Energy Nexus Hackathon, Sponsors, their respective affiliates, and their affiliates' agents and third party contractors, without additional consideration, a worldwide, perpetual, irrevocable, non- exclusive right and license, with the right to sublicense, to discuss, publicize, market and otherwise display content derived from or relating to the 2015 Water/Energy Nexus Hackathon Entry ("Marketing Content"), and to distribute and use such Marketing Content for promotional and marketing purposes (either in the form submitted or in the form of a derivative or adapted work). You understand that you will not receive any compensation or credit for use of your 2015 Water/Energy Nexus Hackathon Entry, other than what is described in these Official Contest Rules.