This year’s hackathon is about contributing to open source projects. Over the course of 24 hours, teams will find an open-source project that interests them and ideate, implement, and present a contribution to the project. If you are new to open source, don’t worry! We’ll be hosting workshops and sessions to help get new hackers introduced to open source and the process of making a contribution.

This hackathon is limited to undergraduate students at UC Berkeley.

Sign up for the hackathon here: https://ieee.berkeley.edu/hackathon-signup.

Join the discord here: http://ieee.berkeley.edu/hackathon-discord.

Eligibility

In order to participate in the hackathon, you must be an undergraduate student at UC Berkeley.

Teams can be a maximum of 5 people, and everyone must be present at the hackathon's opening ceremony to participate. 

Requirements

Submissions must include a Github link to the repository, a short ~30-second walkthrough video/screen recording of the contribution, and responses to the various questions regarding the inspiration and technologies behind the project. 

Teams will have allotted time to present to judges and answer questions during the judging sessions.

Hackathon Sponsors

Prizes

$300 in prizes
First Place Overall
1 winner

Second Place Overall
1 winner

Third Place Overall
1 winner

Devpost Achievements

Submitting to this hackathon could earn you:

Judges

Weikeng Chen

Tiffany Cappellari

Tiffany Cappellari

Kevin Zheng

Kevin Zheng

Judging Criteria

  • Technology
    How technically impressive was the hack? Did the team tackle a difficult technical problem or use a clever or complex technique to address the issue? Were you impressed by their contribution?
  • Design
    Did the team put thought and effort into the user experience? How well designed is the contribution’s interface? For example, websites will be judged based on consistency in styling or how easy they are to navigate.
  • Completion
    Is the contribution functional? Does the contribution do what it is intended to do? Does the contribution improve the overall project?
  • Learning
    Has the team shown growth? Did they learn something from the process? Did they experiment with technologies they haven’t used before?
  • Open Source Best Practices
    How effectively did the team apply open source best practices? Including, but not limited to: use of pull requests, branches, reviewing each other’s code, writing a comprehensive README or modifying the existing one, and using issues to track tasks.
  • Presentation
    Did they clearly communicate the motivation behind the project? How well did they respond to the Devpost prompts?

Questions? Email the hackathon manager

Tell your friends

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.