Core OpenWrt developers forked the project as LEDE over governance failures and declining contributor count. After 18 months apart, the projects reunited — under LEDE's rules but OpenWrt's name.
OpenWrt is a Linux-based operating system targeting embedded devices, primarily wireless routers. It provides a fully writable filesystem with package management, allowing customization through thousands of available packages. The system uses the UCI configuration system and supports a wide range of router hardware.
OpenWrt had been the premier open-source router firmware since 2004, turning cheap consumer routers into powerful network devices. But by 2016, the project was in trouble. Core developer count was declining, there was no process for onboarding new contributors, the infrastructure was unreliable, and decision-making was opaque. Personality conflicts festered because there was no formal governance structure to resolve them — individuals could block changes indefinitely.
In May 2016, a group of prominent OpenWrt contributors — including Jo-Philipp Wich, John Crispin, Daniel Golle, Felix Fietkau, and several others — announced the LEDE project (Linux Embedded Development Environment). The fork wasn't about technical direction; it was purely about governance. LEDE specified a flat hierarchy with one class of committer, simple majority votes for decisions, and a requirement that all infrastructure have at least three administrators.
The split was ugly in the way that family disputes usually are — these were people who had worked together for years. OpenWrt was left with fewer developers and diminished momentum, while LEDE attracted most of the active contributors. The two projects developed in parallel for about 18 months, with LEDE releasing faster and more frequently.
By late 2016, reconciliation talks began. In June 2017, LEDE developers voted to approve a merger, and the reunion was formally announced in January 2018. The result was a compromise that satisfied both camps: the merged project kept the OpenWrt brand name (which had vastly more recognition) but adopted LEDE's governance rules, development processes, and approach to releases.
The LEDE fork is one of the most successful fork-and-remerge stories in open source. The fork wasn't permanent — it was a pressure valve that forced governance reform. Sometimes you have to leave to make your point, and then come back once the point is made.
OpenWrt project founded as custom firmware for Linksys WRT54G routers
Core contributors fork OpenWrt as LEDE, citing governance failures
Merger discussions begin between OpenWrt and LEDE teams
LEDE developers vote to approve merger terms
Merger announced: OpenWrt name retained with LEDE governance rules
The LEDE fork fundamentally reformed OpenWrt's governance structure without permanently splitting the project. The merged OpenWrt adopted LEDE's focus on smaller, more frequent releases, transparent decision-making, and a flat contributor hierarchy — exactly the changes the LEDE founders had wanted all along.
The episode showed that forks can serve as a negotiating tactic rather than a permanent divergence. By proving they could run a successful project independently, LEDE's founders earned the leverage to dictate the terms of the reunion.