Why Great Hackathon Projects Never Build Great Open Source Communities

Every hackathon ends with applause, prizes and repositories full of ambitious ideas. But a month later, most of those repositories are silent. The code still exists, yet the contributors are gone, issues remain unanswered and development stops.

The problem usually isn't the idea or the technology. It's that we build projects to impress judges, not to welcome contributors.

I have seen this pattern from multiple perspectives - as a hackathon participant, mentor to winning teams, Smart India Hackathon judge and former Co-Founder & CTO of Social Winter of Code. Time and again, I have watched technically impressive projects struggle because they weren't designed to become open source communities.

In this talk, I'll explore what separates projects that fade away from those that continue to grow. We will discuss how documentation, licensing, contributor onboarding, issue design, governance, release planning and maintainer practices influence whether people choose to contribute - or quietly move on.

This isn't a talk about writing better code. It's about designing projects that people genuinely want to be part of.

Attendees will leave with practical, experience-driven strategies they can apply immediately after their next hackathon to transform a prototype into a sustainable, community-driven open source project.

• Why technically strong hackathon projects often fail to build lasting open source communities.

• A practical roadmap for transforming a prototype into a contributor-friendly project.

• Best practices for documentation, licensing, governance, issue management, and contributor onboarding.

• Common maintainer mistakes that discourage first-time contributors—and how to avoid them.

• Actionable steps to build projects that continue growing long after the hackathon ends.