09:00-09:30
Keynote
Opening address and contribution culture
Open source maintainers and community leads set the tone with a talk on why contribution quality, documentation, and release discipline matter in production projects.
Free and open source software hackathon
FOSS HACK 25
Build, extend, contribute.
Date
July 27-28, 2025
Venue
T Hub, Hyderabad
Attendees
90+
Format
48-hour open source hackathon
Overview
Build Open. Build Together.
FOSS Hack 25 was a two-day open source hackathon that brought together student teams, platform engineers, and community maintainers to build or meaningfully extend real FOSS projects.
Hosted at T Hub Hyderabad, the event mixed short technical talks with mentor-led build sprints, so teams could ship useful work while learning how open source projects are planned, reviewed, and released in practice.
90+
Students and engineers attending
48h
Non-stop build window
T Hub
Hyderabad innovation campus
FOSS
Open source focus
Agenda
How It Unfolded
July 27-28, 2025 · T Hub, Hyderabad
Day 1 - Launch
10:00-11:00
Onboarding
Problem statements and repo selection
Teams reviewed starter repositories, selected tracks, and aligned on realistic goals with mentors from engineering and developer relations backgrounds.
Day 1 - Build Sprint
12:00-13:00
48 Hrs
Sprint begins
Participants started building features, fixes, or integrations, with an emphasis on clean commits, test coverage, and steady progress through the first build block.
15:00-16:30
Mentor Hours
Architecture and licensing review
Mentors circulated through the room to review architecture decisions, open source licenses, and release readiness before the teams moved into the evening session.
Day 2 - Polish
09:30-11:00
Final Push
Integration, testing, and documentation
The final build window focused on finishing features, tightening documentation, and making sure each project could be understood by outside contributors.
11:30-12:30
Community Clinic
Merge requests and release preparation
Teams prepared pull requests, release notes, and demo scripts while mentors helped them prioritise the work most likely to land cleanly upstream.
Day 2 - Demos
14:00-15:30
Judging Panel
Project review and technical evaluation
The panel reviewed each submission for code quality, utility, contribution value, and how well the project could live beyond the event itself.
16:00-16:45
Ceremony
Recognition and closing remarks
Top teams were recognised for shipping useful work and for showing the kind of collaboration that keeps the open source ecosystem healthy.
Winners
Winning Teams
Congratulations to our standout teams who impressed the panel with their innovation, execution, and technical excellence.
…who impressed the panel and took home some exciting goodies.
Closing note