Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| faq:general [2018/08/19 01:42] – [What devices does LEDE target?] Rewrite for post-LEDE/OpenWRT merger context. sampablokuper | faq:general [2018/08/19 02:21] – [Why was the LEDE project forked from OpenWrt, and then merged back into it?] Link to About page sampablokuper | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Frequently Asked Questions: General ====== | ====== Frequently Asked Questions: General ====== | ||
| - | |||
| ===== What devices does OpenWRT target? ===== | ===== What devices does OpenWRT target? ===== | ||
| - | |||
| OpenWRT mainly targets embedded devices capable of running Linux. In most cases wireless routers. | OpenWRT mainly targets embedded devices capable of running Linux. In most cases wireless routers. | ||
| - | ===== Is LEDE compatible with OpenWrt? ===== | ||
| - | The packages distributed along with LEDE are the same you find in OpenWrt, and any instructions you find should work for both. | ||
| - | Sysupgrades from OpenWrt to LEDE or vice versa are supported but it is advised **not** to keep settings to benefit from the updated defaults. | + | ===== Is OpenWRT suitable for me? ===== |
| + | OpenWRT | ||
| - | ===== Is LEDE good for me? ===== | + | OpenWRT' |
| - | LEDE is primarily intended for networking enthusiasts, | ||
| - | While LEDE is a set of building blocks | + | ===== The company I work for uses OpenWRT and wants to support the project. What should we do? ===== |
| + | Companies can best support OpenWRT by upstreaming the required code to support their products. Any platform support code, patch submissions or even just detailed specifications are most appreciated. | ||
| - | ===== How do I upgrade from OpenWrt to LEDE? ===== | + | Upstreaming product support also benefits the company in the long run as ongoing maintenance and porting effort decreases over time while the amount of internally required changes can be reduced. |
| - | Migrating from OpenWrt to LEDE should work similar to upgrading from one OpenWrt release to another. Using the '' | ||
| + | ===== What license does OpenWRT use? ===== | ||
| + | The build system and many OpenWRT components are licensed under the GNU General Public License Version 2. Some parts are licensed under different licenses, this is mostly the case for packages not created in OpenWrt. | ||
| - | ===== What happens to the OpenWrt package feed? ===== | + | ===== Who holds the copyright of OpenWRT code? ===== |
| + | The original authors of the code hold the copyright. | ||
| - | LEDE plans to use the normal OpenWrt package feed, till it deviates too much from OpenWrt and it would be easier to have an own branch or feed. | ||
| + | ===== Is the OpenWrt project a registered legal entity? ===== | ||
| + | No, the OpenWrt project is not a registered legal entity. However, OpenWrt is represented by Software in the Public Interest (SPI). | ||
| - | ===== Were there any technical reasons to split from OpenWrt? ===== | ||
| - | Nothing special, expect that LEDE wants to focus more on stability and not so much on bleeding edge any more. The release process should be better automatized and the release should be better tested. | + | ===== Is OpenWRT a registered trademark? ===== |
| + | Yes, OpenWrt is a registered trademark which is held by the Software in the Public Interest (SPI) in the name of the OpenWrt project. | ||
| - | ===== Is LEDE represented by any Company or Industry organization? | ||
| - | No, LEDE is not affiliated with any specific company or any industry organization. | + | ===== Why was the LEDE project |
| - | + | //Main topic: [[: | |
| - | ===== The company I work for uses LEDE and wants to support the project. What should we do? ===== | + | |
| - | + | ||
| - | Companies can best support LEDE by upstreaming the required code to support their products, any platform support code, patch submissions or even just detailed specifications are most appreciated. | + | |
| - | + | ||
| - | Upstreaming product support also benefits the company in the long run as ongoing maintenance | + | |
| - | + | ||
| - | ===== Are there plans to license LEDE under a different License? ===== | + | |
| - | + | ||
| - | There are no plans to change the license of the LEDE code. It should be easy to copy code from and to OpenWrt. | + | |
| - | + | ||
| - | ===== What license does LEDE use? ===== | + | |
| - | + | ||
| - | The build system and many LEDE components are licensed under the GNU General Public License Version 2. Some parts are licensed under different licenses, this is mostly the case for packages not created in LEDE or OpenWrt. | + | |
| - | + | ||
| - | ===== Who holds the copyright of LEDE code? ===== | + | |
| - | + | ||
| - | The original authors of the code hold the copyright. | + | |
| - | ===== Is the LEDE project | + | The LEDE project |
| - | No, the LEDE project is not a registered legal entity. The OpenWrt project is also not a registered | + | LEDE was not affiliated with any specific company or any industry organization. Nor was a trademark |
| - | ===== Is LEDE a registered trademark? ===== | + | Compatibility between the projects' |
| - | No, LEDE is not a registered trademark, but OpenWrt is a registered trademark which is held by the Software in the Public Interest (SPI) in the name of the OpenWrt project. | + | After some months of working independently, the two groups were able to agree on a way to merge the best aspects of both projects back under the OpenWRT |