Past editions of FOSSHack ran for 36 hours. Teams would rush to build something before the deadline, often pushing all their code in one final commit. We are changing the format, FOSSHack 2026 will be a month-long program and run from 1- 31 March 2026. We’re giving you time to plan, learn, build thoughtfully, and create something meaningful.
FOSShack 2026 is a hybrid hackathon, with participants joining online or in person at one of our 10 local host venues hosted by FOSS clubs across colleges. Each venue will accommodate participants from both the host college and outside institutions. We encourage showing up in person for the first day and the last two days. For the rest of the month, working virtually is the default. If the host college has space, participants can also work from the venue or in small self-organised groups.
The total prize pool is ₹5 lakh, split across different problem statements and categories. We’ll share specific amounts once we finalise everything.
What we are looking for:
We want projects that solve actual problems. Not just another app built because you could, but something that addresses a real challenge faced by real people or organisations. Some problem statements will come from partner organisations, others can come from what you’ve noticed in your community or college. Please share your ideas with us before planning. We’re also encouraging participation from people with diverse skill sets, including design, documentation, and legal or policy backgrounds. Problem statements will be available across different projects. More will be shared in the upcoming days.
Support:
Each local host may receive a grant of up to ₹50,000 to run the programme. This can be used for food, improving internet connectivity if needed, basic workspace setup, printed materials, small goodies, and other essentials to ensure the event runs smoothly.
You’ll need to submit a detailed budget plan with proper planning and bills. Check this document for templates, guidelines, and requirements.
Organisers and community members might drop by venues during the month if they’re available to see how things are going, join scrum calls, or just chat.
Schedule:
Important: Local hosts have the flexibility to set their own schedules within the month of March. The dates mentioned below are suggested reference points. “Week 1” means your first week, not necessarily March 1-7. You can start earlier or later, and adjust your milestone days based on your venue’s availability and participant needs.
Week 1(March 1-7): planning and team formation
The first week is about getting organised. Day 1 starts with an orientation, this can be any date in early March that works for your venue, we recommend being there in person if you can. After that, spend the week finding teammates, picking a problem you want to solve, and planning how you’ll build it.
Weeks 2-4: development
You have three weeks to construct your project. Attend check-ins, try new things, make mistakes, correct them, and ask mentors for assistance when you need it. If necessary, regular scrum meetings with the local hosts are advised. We will have planned calls to assist you with partner problem statements.
Final Milestone Days(March 30-31): wrapping up
The final two days are your venue’s milestone days - these don’t have to be March 30-31. Local hosts can schedule these based on their calendar and when teams are ready to wrap up. You can start early and end early if it works better for your venue. These milestone days can be conducted in person at your venue or online. They’re meant for finalising work, polishing the project, improving documentation, adding a clear README, choosing an appropriate licence, preparing any required submissions, recording a short demo or walkthrough video, and getting the final presentation ready.
Note for Local Hosts: You control your timeline. Set your orientation day, development period, and final milestone days based on what works best for your participants and venue. Just ensure everything wraps up by the end of March.
How we evaluate
We’ll look at your GitHub activity throughout the month, your commits, how your project evolved, and the work you put in. This helps us see the real effort, not just what got rushed together at the end.
People we need
-
Co-chairs to help run the event and make key decisions about problem statements, evaluation, and overall direction.
-
Judges and evaluators from different backgrounds who can look at projects from various angles, code quality, documentation, and whether it actually solves the problem.
-
Mentors with FOSS Community or specific technical knowledge who can guide teams when they need help.
Please share your comments, suggestions, and feedback on this proposal.