Hacking Rules

  • Forming Teams
    • Rules
      • No more than 4 Fellows per team
      • No less than 3 Fellows per team
    • Encouraged
      • Racial Diversity
      • School Diversity
      • Gender Diversity
      • Work with people you haven’t interacted with much

All work must be completed between July 23 and July 24.

Presentations and hosted link (if applicable) must be submitted by 10:00 am on Sunday. No modifications are allowed. Any submissions after that time will be docked 10 points per minute. The hackathon officially begins at 10am on Saturday July 23rd. You may not begin coding, setting up your project, working on your presentation, or use code you’ve written before the hackathon officially begins.

You must present a working demo! You may present mocks in addition to the demo but you must show an application running during your presentation.

Participants must contact the organizers if they wish to reuse code they’ve created outside the hackathon.

All work must be done in the designated hacking zone unless permission has been granted from the Hack4Diversity organizers.

Third party libraries are permitted if they are available freely and publicly accessible to all teams.

3rd Party materials, like graphics and images may be used in products and presentation if they fall under public domain, creative commons, or fair use policies.

External 3rd Party Guidance and Assistance in the form of a non-team member assisting in the hackathon projects is strictly forbidden, EXCEPT in the case of registered Hack4Diversity mentor.

Please contact a Hack4Diversity organizer during the event for questions regarding 3rd party help or libraries.

Demos

Length of demos will be no more than 2 minutes with 3 minutes of Q&A from the Judges. This will be strictly enforced. No videos permitted. One team member presents while at least one other team member controls the laptop.

Code of Conduct

All participants are expected to follow the Hack Code of Conduct.