This will be your first opportunity to collaborate with the other fellows in your Pod on a software project and put some of what you’ve been learning into practice! 

You’ll use Git & GitHub best practices to build an Open Source project.

Explorer Fellows:

  • You will build a pod portfolio platform to showcase work your pod achieves. Your Pod Leader can help you brainstorm ideas of what it could do, and how your pod can manage it.

Open Source Fellows:

  • Your project will utilize at least one of the technologies that your Pod will be contributing to during the program. Ask your Pod Leader for help if you’re unsure.

Externship Fellows:

  • Your project will utilize some of the technologies you might encounter during the program while working on your partner projects. Ask your GPM for help if you’re unsure. 

By the end of this session, you should accomplish the following:

  1. Familiarized yourself with at least one of the technologies you might use during the program

  2. Practiced collaborating on a project on GitHub using best practices

  3. Expanded your network by collaborating with fellows from your Pod

 

Timeline

The Orientation Hackathon takes place during your first week of the fellowship. The kickoff will take place at the end of your first Pod meeting and demos will take place at the beginning of your first meeting during your second week.

  • Orientation Hackathon Kickoff – During this event, we’ll reveal the “secret ingredient” (your Pod’s assigned projects) and help you form teams of 2-3 fellows. Explorer Fellows will work with their Pod Leader to decide what their portfolio platform will do.

  • Hacking – Between the end of your orientation hackathon kickoff and the beginning of the demos on Monday, you should be collaborating with your team on your hackathon project. Explorer Fellows, you will begin the project in the middle of the week.

  • Hackathon Pod Demos – All of your Pod Leader's Pods will come together to show off their projects during a series of live demos on Zoom. Judging will take place independently.

Hackathon Sponsors

Prizes

Top Open Source Team (4)

Amazon Echo Dot
Ellie Mask

Top Externship Team (2)

Amazon Echo Dot
Ellie Mask

Top Explorer Pod Portfolios (3)

Amazon Echo Dot
Ellie Mask

Devpost Achievements

Submitting to this hackathon could earn you:

Eligibility

You must be a Fellow of the MLH Fellowship (Batch 2) in order to be eligible to participate.

Requirements

As you know, you have until the beginning of your hackathon demos to work on your project. As part of your submission, you’ll need to complete the following:

  1. Publish your project on GitHub with an appropriate Open Source license

  2. Record a 3-5 minute video overview and demo of your project.

Publishing Your Project on GitHub

Before demos the repository should be set to public and should have an appropriate README and LICENSE included. One of the criteria that you will be evaluated on is your use of Git and GitHub best practices, so also try to make sure your commit history is visible on the repository.

Recording Your Video Demo

A day or so before the Demos you should plan to record a video demo of your project. While you’ll do a live demo with your Pod, the videos will be shared with the full fellowship, and the judges for the global competition will see the videos from the top team from each Pod.

During this video demo (and probably your live demo too) you should aim to cover the following key pieces of information. 

  • Project Name & Tagline - The name of your project and a 1-2 sentence tagline describing it.

  • Project Overview – A more detailed written description of the project. Aim for 3-5 paragraphs about the problem you were trying to solve, how you approached it, and what you built.

  • Techonologies Used  – A list of any technologies you used when building the project, including any not officially being supported by your Pod.

  • Pod Number and Team Member Names – Your Pod’s number and a list of your team members.

Full page can be found here.

Judges

Wei He

Wei He
Batch 1 Fellow

Shreya Gupta

Shreya Gupta
Batch 1 Fellow

Saurabh Kumar Suryan

Saurabh Kumar Suryan
Batch 1 Fellow

Garima Singh

Garima Singh
Batch 1 Fellow

Nyior Clement

Nyior Clement
Batch 1 Fellow

Ruby Werman

Ruby Werman
Batch 0 Fellow

Vividha

Vividha
Batch 1 Fellow

Nitish Gadangi

Nitish Gadangi
Batch 1 Fellow

Boyu Jiang

Boyu Jiang
Batch 1 Fellow

Shivay Lamba

Shivay Lamba
Batch 1 Fellow

Shubhank Saxena

Shubhank Saxena
Batch 1 Fellow

Yash Khare

Yash Khare
Batch 1 Fellow

Rishiraj Singh Chhabra

Rishiraj Singh Chhabra
Batch 1 Fellow

Chirag Singhal

Chirag Singhal
Batch 0 Fellow

Sebastian Crossa

Sebastian Crossa
Batch 0 Fellow

Ridham Bhat

Ridham Bhat
Batch 1 Fellow

AB Satyaprakash

AB Satyaprakash
Batch 1 Fellow

Kenneth Aladi

Kenneth Aladi
Batch 0 Fellow

Temitope Akinsoto

Temitope Akinsoto
Batch 0 Fellow

Muhammad Saad

Muhammad Saad
Batch 1 Fellow

Ankit Maity

Ankit Maity
Batch 1 Fellow

Samuel Obe

Samuel Obe
Batch 0 Fellow

Anshul Goyal

Anshul Goyal
Batch 0 Fellow

Aksh Gupta

Aksh Gupta
Batch 1 Fellow

Harsh Bardhan Mishra

Harsh Bardhan Mishra
Batch 1 Fellow

Aditya Raman

Aditya Raman
Batch 1 Fellow

Pablo Domínguez Durán

Pablo Domínguez Durán
Batch 1 Fellow

Abhishek Chaurasia

Abhishek Chaurasia
Batch 1 Fellow

Aayush Joglekar

Aayush Joglekar
Batch 1 Fellow

Siddharth S

Siddharth S
Batch 0 Fellow

Rahul Tarak

Rahul Tarak
Batch 1 Fellow

Gagan Deep

Gagan Deep
Batch 1 Fellow

Yoseph Ahmed

Yoseph Ahmed
Batch 0 and Batch 1 Fellow

Utkarsh Goel

Utkarsh Goel
Batch 1 Fellow

Nenad Pantelić

Nenad Pantelić
Batch 1 Fellow

Laveesh Gupta

Laveesh Gupta
Batch 0 Fellow

Judging Criteria

  • Technology
    How technically impressive was the hack? Was the technical problem the team tackled difficult? Did it use a particularly clever technique or did it use many different components? Did the technology involved make you go "Wow"?
  • Design
    Did the team put thought into the user experience? How well designed is the interface? For a website, this might be about how beautiful the CSS or graphics are. For a hardware project, it might be more about how good the human-computer interaction is?
  • Completion
    Does the hack work? Did the team achieve everything they wanted?
  • Learning
    Did the team stretch themselves? Did they try to learn something new? If a team which always does virtual reality projects decides to switch up and try doing a mobile app instead, that exploration should be rewarded.
  • Best Practices
    Did the team apply the best practices including, but not limited to, use of branches, pull requests, reviewing each other’s code, writing a comprehensive README, and using issues to track tasks.

Questions? Email the hackathon manager

Tell your friends

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