What happened
Mixed outcomes. Debian reached a binding decision, and dissenters began a separate project. A procedure allowed the existing project to proceed without reconciling its participants’ competing priorities; open licensing gave those leaving a starting point for their own work.
- “General Resolution is not required” defeated every other option in the 2014 preference vote. General Resolution: init system coupling
- The rejected proposals concerned package dependencies and support obligations, a different question from the earlier choice of a default initialization system. General Resolution: init system coupling
- Devuan’s founders described their fork as a response to disagreements about governance and mission as well as technical design. Announcement of the Debian Fork
What might explain it
Supported in case
A formal vote may preserve a project’s ability to proceed without making minority participants accept its priorities. General Resolution: init system coupling Announcement of the Debian Fork
Alternative explanation: The departure might have happened even without this vote because technical commitments had already diverged.
Plausible
Forkability may convert an otherwise blocked internal dispute into parallel experimentation. Announcement of the Debian Fork
Alternative explanation: Parallel projects may instead duplicate scarce maintenance work and retain dependencies on the upstream community they leave.
Questions to take into practice
- Ask whether a decision procedure promises a binding decision or genuine convergence; those are different outcomes.
- Before proposing a fork, identify the maintainers, infrastructure, and continuing upstream dependencies it would need.
What remains uncertain
- Devuan’s founders presented their own account of the dispute, which does not establish how representative their grievances were across Debian. The fork’s longer-term value also depends on adoption, quality and the extra maintenance required.