UC Davis's premier hackathon for social good is back with 3 main tracks: education, environment, and health.
Check out hackdavis.io/live during the event.
HackDavis is back and better than ever! We are UC Davis's major collegiate hackathon dedicated to social good. This winter, over 700 students, hackers, and creatives will come together for 24 hours of hacking. We're providing a platform to bring together the most talented students in California to address the world's most pressing social issues.
There are three main tracks to the hackathon: Environment, Health & Wellness, and Education. With these 3 tracks, we hope to inspire change and cultivate a growing hacker community dedicated to social change at UC Davis.
Eligibility
All previously registered and RSVPd students can take part.
Requirements
- YOU MUST BE REGISTERED FOR HACKDAVIS TO WORK ON A PROJECT FOR SUBMISSION. (And have checked-in to the event)
- Your project must be completed entirely during hacking hours and not before
- You cannot work on your project before hacking begins (which is officially 12:00PM PT on Saturday, January 20st, 2018)
- You must submit your project by 12:00PM on Sunday, January 21st. You can continue hacking until noon or until the countdown goes to 0.
- You cannot steal another team's code in any way, shape, or form
- The decision of judges is final for determining prizes and awards
- Max of four team members per team
How to enter
Registration is closed.
Judges
Chris Nitta
Professor
Sam King
Professor
Zhou Yu
Professor
David Doty
Professor
Aditya Thakur
Professor
Liz Tang
Director Student Startup Center
Matt Butner
Lecturer
Xin Liu
Professor
Vladimir Filkov
Professor
Joël Porquet
Lecturer
Brandie Nonnecke
Postdoctoral fellow at CITRIS
Christian Millsop
Engineer at Genentech
Dean Sirovica
Zona Partners
Joanna Quach
Business Analyst at Genentech
Ilvana Mesic
Program Manager at UC Davis Health
Dan Kurtz
Software Engineer at Beyond 12
Laine Himmelmann
Public Relations Officer at Habitat for Humanity
Cass Brown Capel
Save Ourselves Nonprofit
Jeff Rowe
Researcher at UC Davis Information Security Office
Judging Criteria
-
Technical Complexity
How technically impressive is the project? If competing in an API/hardware usage category, was the API/hardware used extensively? -
Polish
How complete is the project? Is it just on the design stage, coding stage, etc.? Ideally the project has 1 or more functionality finished, or close to finishing. -
Originality
Has this project been done before? Does the project make others think this is a really cool idea why didn’t I think of that? -
Usefulness
How beneficial will this project be to its target it audience? How much will it impact their lives? Are people likely to use it often, and will they have a good experience when doing so?