Rules
The marathon is public. The patch has to survive contact with maintainers.
Selection
- Anyone may propose a feature for a registered Free Software project.
- Community marks are a signal, not a binding vote.
- Before each marathon the jury invites three teams, looking at request quality, support, and who signed up to implement.
- The assigned feature is announced late on purpose. Do not pre-implement the secret task.
During the 24 hours
- Work happens in public in Zurich, Switzerland.
- Remote community help is expected. The people in the room still own the drop.
- Licenses stay with the upstream project. Hackontest does not relicense your tree.
- Sleep is allowed. Performance theatre is not a scoring category.
Judging
- Does the code address the selected request?
- Could upstream merge it without a rewrite?
- Did the team work with the project instead of forking in the dark?
Prize money is announced with each edition.