FOSS Hack 2026 - Rules, Guidelines, FAQ

Duration: March 1-31, 2026
Format: Month-long hybrid hackathon
Last Updated: December 2025

FOSS Hack 2026 is a month-long program, not a sprint. You'll have the entire month of March to plan, learn, build thoughtfully, and create something meaningful. The hackathon takes place in hybrid mode. You can choose to hack virtually or in person at our 10 local host venues. FOSS Hack 2026 runs throughout March, but you are not expected to work on your project every single day.

Note: There is no single central venue for FOSS Hack 2026. Evaluation will be based on your active development days, not calendar days. Whether you work intensively for 2 weeks or steadily throughout the month, we'll assess the work you actually put in.

Eligibility
  • The Hackathon is open to any Indian national who has a valid bank account and PAN.

We encourage diverse participants with different skill sets:

  • Developers
  • Designers
  • Legal experts
  • Domain specialists
  • Anyone who can contribute to building complete solutions
How does the format work?
  • The hackathon runs for ~4 weeks
  • Most work is done virtually
  • Local host venues will run key in-person days, keep an eye on communication for dates and other pertinent information, such as:
    • Kickoff/orientation
    • Learning sessions
    • Optional mid-point check-ins
    • Final demo & submission days

You can participate fully without attending in person, as long as you meet submission requirements.

Do I have to attend in person?

No.

In-person attendance is optional and limited to the capacity of the local host venue and/or milestone days.

If your local host venue has space, you’re welcome to attend. Otherwise, virtual participation is completely fine.

Teams

Team size: 1-4 members

When registering for FOSS Hack, you must either create a team or join an existing one. Teams can have 1 to 4 members.

If you are participating solo, you still need to create a team with yourself as the only member.


Team Formation

Where to Find Teammates:

  • Telegram Group
  • Your Friends & Colleagues
  • College Networks
  • Local Host Venues
What kind of projects can I work on?

You have three options:

Option 1: Create Your Own New Project

Build something from scratch that solves a real problem. When submitting, you'll share the link to your new GitHub repository.

Option 2: Contribute to an Existing Open Source Project

Pick any open-source project you're passionate about and make meaningful contributions to it. Share the link to the project repository and your contributions (PRs, issues, etc.).

Option 3: Work on a Partner Project

We've curated a list of partner projects with specific problem statements on our website. These are projects from organisations and communities looking for contributors.

You can work on:

  • A new FOSS app, tool, or library
  • Improving or extending an existing open-source project
  • Design-focused work (UI/UX, redesigns)
  • Documentation, developer tooling, or infra
  • Open hardware projects
  • Partner projects problem statements
  • College-specific challenges

We want projects that solve real problems not just another app built to end up somewhere on your GitHub, but something that addresses a real challenge faced by real people or organisations. You don’t need to build something massive. Scope matters.

Things to keep in mind when choosing a Partner Project

  • Partner Projects are open to contributions, but they won’t have everything mapped out for you. Reading docs, exploring the codebase, and asking thoughtful questions is part of the process.
  • Maintainers may respond asynchronously. Open source work often moves slower than a typical hackathon, patience and clear communication go a long way.
  • Start by checking the project’s issues, contributing guide, and setup instructions before reaching out.
  • If you get stuck, use the project’s preferred communication channel (GitHub issues, discussions, Discord, email, etc.) and be mindful of maintainers’ time.
  • Not all contributions have to be code. Many projects welcome help with documentation, design, testing, localisation, data, or research.
  • The Partner Project list is meant to help you get started, you’re free to contribute to any open-source project that aligns with your interests.
What you should (Probably) not work on
  • An app or project that extensively uses proprietary services or APIs
  • Yet another Keras model on available datasets
  • A simple CRUD application
  • A blockchain/we3 or crypto project (Why?)
How We'll Judge Your Project

We evaluate based on the full development process, not just the final result.

GitHub Activity Throughout the Month:

  • We'll track your commits from Day 1
  • How your project evolved over time
  • Consistency and progression of work

Key Evaluation Factors:

  1. License: Must have a valid Free and Open Source license

  2. Communication:

    • Well-written README explaining what your project does
    • How to install, test, and use it
    • Video demo (max 3 minutes - demo only, no explanations)
    • Concise, meaningful commit messages showing project progression

  3. Problem-Solving Effectiveness:

    • Does it actually address the stated problem?
    • Real-world impact and practical value
    • Usability for the target audience

  4. Completeness:

    • Applications must be complete and working
    • All essential features implemented
    • Properly tested

  5. Code Quality:

    • Clean, maintainable, well-structured code
    • Proper documentation
    • Following best practices

  6. Design and Aesthetics:

    • If you're making a user interface, ensure it's clean, modern, and usable
    • Good UX principles applied

  7. Timeframe:

    • Project must be reasonably built within the month
    • Scope appropriate for a month-long effort
    • The jury's judgment is final

  8. Credits:

    • If using existing code, proper attribution is required
    • Plagiarism is strictly not tolerated
Submission Requirements

Submission Deadline: March 31, 2026 at 6:00 PM IST

What Constitutes a Valid Submission

Your project must include:

  1. GitHub Repository Link
  2. Valid FOSS License
  3. Complete Documentation
  4. Video Demo (Max 3 minutes)
  5. Development Timeline Proof

Only March Development Counts

Only development that happened between March 1-31, 2026 will be considered for evaluation.

  • Pre-built projects with no progress during March do not qualify
  • If you're contributing to an existing project, we'll only evaluate your contributions made in March
  • Your GitHub commit history must show active development within the hackathon period
Prizes

Total Prize Pool: ₹5 lakh

  • Divided among the best projects across different problem statements and categories
  • Specific amounts will be announced once finalised

Payment:

  • Prize money transferred individually via bank transfers within India
  • Winners must furnish a copy of their PAN for TDS and tax documentation
Communication & Updates

  1. FOSS Hack Telegram Group: FOSS Hack Public

  2. Email Updates: All registered participants will receive important announcements and deadline reminders via email.

  3. Local Host Updates: Venue-specific updates will be shared by local host coordinators.

  4. Website & Forum: Check FOSS Hack 2026 regularly for any changes.