All code must be written during the event. You cannot use existing code that
you have written and finish it during the event.
Participants cannot use any external APIs as a part of their core
functionality. (Using Google Maps API for an app that tracks a delivery is
fine, but using Google Maps API to build a navigation app is not allowed)
You can apply as an individual or a team. Teams can consist of up to a maximum of 5 members.
The organizers reserve the right to make changes to the event program.
- The prize pool will be split among the winners.
- Download all the necessary files (IDE, SDK, etc) before the event.
Internet connection will be provided, but it is best to have your 4G
dongle or mobile hotspot.
- All participants must bring their own laptops.
- Be present at the venue on 9th April at 9 AM.
- Submit your idea at the registration desk.
There will be two sessions for coding:
- 9 AM - 6 PM on 9th April
- 9 AM - 12 PM on 10th April
- You CAN code between the two sessions when you're not at the venue.
During the event, the Hackathon judges will visit every team, ask some questions and make evaluations.
There will be three kinds of evaluations:
- 2 PM on 9th April for project concept and usability
- 10 AM on 10th April for core readiness
- 2 PM on 10th April for final presentation
Your project is eligible for submission only if it's in working condition
and has minimum quality standards
Maximum 10 teams will qualify for presenting their final work in round 3.
- You are supposed to push your code on GitHub by 12 PM on 10th April.
Include a brief description of your project in the README and mention the
installation steps along with screenshots. Projects submitted without a
proper README will not be considered.
Once your project is submitted, DO NOT make any changes. We will keep an eye
on the commits made on GitHub.
All code, design, art, music, SFX, and assets must be created during the
duration of the Hackathon. You are however permitted to use any publicly
available open-source resources (images, datasets, etc.) in your project.
Participants are free to make plans, create wireframes, and brainstorm prior
to the event.
All projects submitted for consideration for a prize will be subject to a
full code and asset review in order to determine whether the work originated
during the hackathon or not.
The project must be developed in public repositories on GitHub and should
have a valid Open Source License.
You can read about open source licenses here.
- All projects must be uploaded to GitHub before 12PM on 10th April.
If you’re new to Github,
read this guide.
All teams retain full ownership of what they have created during the
A FOSS United Initiative