1. The primary objective of the event is to meet people while having fun building something new.  Don't do anything that would detract from the fairness or fun of the event.
  2. The bulk of the construction should happen during the weekend. It's not going to be a fun event if some teams show up on Sunday evening with super-elaborate projects that they've been working on for months. All teams will be required to disclose whatever pre-built hardware or software components were used. You may be asked to do a code review before judging. For example: "We used the Ruby-on-Rails framework with jQuery library to make this website"; "We 3d designed this piece before the Hackathon, and then printed it out at DHF", and so forth. The judges can factor this into their decision and will give preference to projects that use limited pre-built components.
  3. Brainstorming, planning, and mock ups are fine to prepare in advance of the hackathon, these do not count as pre-built components. You are also allowed to consider what APIs and third party services you plan to use.
  4. You can use whatever tools and spaces are at your disposal. You must either present physically at the event, or you may use a google hangout to present your project IN ORDER TO BE ELIGIBLE. Please email adam@digitalharbor.org if you are presenting remotely! 
  5. Projects must be submitted to the DevPost by the deadline provided. Projects that aren’t submitted to DevPost by 1PM are not qualified to win. 
  6. Each participant may compete individually or as part of one team, but not both, and not on multiple teams/projects.
  7. Please list all team members that contributed to your project on your presentation in the “Team Members” slide, even if they did not officially sign up for the hackathon. It is not fair to receive extra outside help without disclosing that information so the judges can take that into consideration (don’t try to make it look like 2 people did the work of 4).
  8. Volunteers are eligible for prizes as long as they are not working with the judges. This includes defining judging rules, criteria, selection, and concierge services.
  9. Anyone in violation of the Code of Conduct (at the organizer's discretion) will be asked to leave and their project will be deemed ineligible to win a prize.

http://hackcodeofconduct.org/