Add deprecation notice

[web.git] / faq.txt

diff --git a/faq.txt b/faq.txt
index 0dbc39fb534765e456fe90a69ca693fc15be70d7..85583f60a0a68ec30b50947338d977c2da15f0e0 100644 (file)
--- a/faq.txt
+++ b/faq.txt
@@ -9,7 +9,8 @@ LEDE mainly targets embedded devices capable of running Linux. In most cases wir
 
 == How do I upgrade from OpenWrt to LEDE?
 
-Use the same mechanisms as used to upgrade from one OpenWrt version to a more recent versions, sysupgrade for example. With sysupgrade even your configuration should be migrated.
+Migrating from OpenWrt to LEDE should work similar to upgrading from one OpenWrt release to another.
+Using the +sysupgrade+ command is the preferred approach as this will also attempt to preserve the system configuration.
 
 == Where is the LEDE Wiki?
 
@@ -17,7 +18,7 @@ This is work in progress.
 
 == Where is the Forum?
 
-Currently we have mailing lists, see /communication.html
+Currently we have mailing lists, see link:communication.html[Communication].
 
 == What happens to the OpenWrt package feed?
 
@@ -27,32 +28,34 @@ LEDE plans to use the normal OpenWrt package feed, till it deviates too much fro
 
 OpenWrt Chaos Calmer will be supported with security and bug fixes by the OpenWrt project.
 
+== 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 LEDE represented by any Company or Industry organization?
 
 No, LEDE is not affiliated with any specific company or any industry organization.
 
 == The company I work for uses LEDE and wants to support the project. What should we do?
 
-The best support is that you allow and encourage your employees to contribute the changes you did internally back to the LEDE project.
-If you are a chip vendor for example adding support for your chips to LEDE would be a nice.
-This way others can also benefit from your changes and you reduce your maintenance cost, because you need less patches when using more recent versions of LEDE.
+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 and
+porting effort decreases over time while the amount of internally required changes can be reduced.
 
 == 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.
 
-== 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.
-
 == 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 holds the copyright.
+The original authors of the code hold the copyright.
 
 == Is the LEDE project a registered legal entity?