File a feature, not a fantasy
Name the user, the failure, and what “done in 24 hours” looks like. Heat from the community is a signal, not a ranking game.
Switzerland · 24-hour marathon
Hackontest
A public 24-hour coding marathon for Free Software. Communities file the features. Teams implement them in Zurich. To win, they work with the project — so the patch can ship after the lights go out.
24hPublic coding session
3Teams on the floor
PrizeAnnounced each edition
10Jury seats
Always open
Tell a project what to build. A team might actually do it.
Hackontest exists so FLOSS gets real work, not slideware. Users and developers send short, scoped requests. The jury picks three teams. Those teams fly in, code in public, and try to land something upstream can review.
Debian, GNOME, Vim, Samba, PostgreSQL, and LibreOffice are already on the board. If your project is missing, say so when you write.
How it works
Users ask. The jury picks. Teams ship in public.
Three teams come to Zurich
Before each marathon the jury invites projects that have both a backlog and people willing to code it.
24 hours on an open floor
Visitors watch Free Software get written in real time. Food, rest, remote community help — the people in the room still own the drop.