LEDE (Linux Embedded Development Environment) Project is a Fork of OpenWrt

2016 appears to be the year of splits in open source communities with Kodi losing its main Android developer, LibreELEC being born out of disagreements within OpenELEC community, and now LEDE project, a fork of OpenWrt, has been created because some people are not satisfied with the way the project is managed, and now “includes a significant share of the most active members of the OpenWrt community”.

LEDE_OpenWrt_ForkLEDE, which stands for “Linux Embedded Development Environment” , has three stated goals:

  • Building a great embedded Linux distribution with focus on stability and functionality.
  • Having regular, predictable release cycles coupled with community provided device testing feedback.
  • Establishing transparent decision processes with broad community participation and public meetings.

You can find more on LEDE Project website, and the source code is available on the project’s git server:

Thanks to Zoobab for the tip.

Share this:
FacebookTwitterHacker NewsSlashdotRedditLinkedInPinterestFlipboardMeWeLineEmailShare

Support CNX Software! Donate via cryptocurrencies, become a Patron on Patreon, or purchase goods on Amazon or Aliexpress

ROCK 5 ITX RK3588 mini-ITX motherboard

9 Replies to “LEDE (Linux Embedded Development Environment) Project is a Fork of OpenWrt”

  1. @zoobab
    It looks a bit more than a rebranding. While many core developers moved to LEDE, some were not aware of this at all:

    This announcement comes as a surprise to all the other developers, myself included.

    – mbm (openwrt founder)

  2. Strange fork,

    I don’t understand the need to change name, openwrt is cool – really awsome project – and software is a must have.
    Why just explain community issue and starting an new github account to work together, and leave the openwrt core team apply good patch from this collaborative/openned github?
    It’s an issue of load of work in case of open acces dev?

    It’s seem this is an mistake about “transparency”,,,first where is TOH 🙂

  3. There are always things behind the scene. Some things can be discussed publicly and some are known only to involved people.

  4. So are they going to strip off some confusing OpenWrt core components like uci, nvram, ubus and JSON based config options etc. etc. ?
    And also free up few KB in the final image free space ? Chaos Calmer 15.05.1 on routers with 4MB NOR flash is literally useless!

Leave a Reply

Your email address will not be published. Required fields are marked *

Khadas VIM4 SBC
Khadas VIM4 SBC