This page should address any licensing concern that anyone may have about using Nelson. We are convinced that Nelson's license allows virtually anyone to use it.
If you still have a concern, don't hesitate to contact us.
The answers below are mutually redundant for the sake of being easier to find.
Nelson is dual-licensed: at your choice,
- either under the
,
- or under the
.
%20v3.0-green.svg?style=flat-square){kind=icon}
%20v3-blue.svg?style=flat-square){kind=icon}
Note that this is an OR, not an AND. You do not need to conform to both licenses, you just pick the one that you prefer.
Typically, almost everybody will regard Nelson as just LGPL-licensed.
The LGPL v3.0 is one of the most popular open source licenses.
It is quite permissive, at least much more permissive than the GPL license. It allows any software to use Nelson. For example, proprietary software may use Nelson without disclosing any of its own source code.
In the following answer, we're assuming that you're using Nelson ''unmodified''. If you are using a ''modified Nelson'', then there's an additional clause.
When you distribute software that ''uses'' Nelson, the LGPL requires you to:
- Say somewhere that that software uses Nelson, and that Nelson is LGPL-licensed.
- Give a link to the text of the LGPL v3.0 license. See Section 3 of the LGPL v3.0.
As long as you're not modifying Nelson's own files, you can safely ignore this. Thus, for almost all of our users, the LGPL is for all practical purposes essentially equivalent to the 2-clause BSD license.
There is an circumstance in which the GPL license may be useful. Some optional advanced functionality can be enabled by letting Nelson use external libraries, which we call back-ends. Some such libraries are GPL-licensed. For example, in our FFT module, there is an option to use the FFTW library as a back-end for higher performance. Since FFTW is GPL-licensed, this is only possible if Nelson is used under GPL license. Meanwhile, Users of Nelson can use the Intel MKL back-end and Nelson under LGPL license.
This is entirely welcome. Of course, you do not have to disclose any of your own source code. Using Nelson does not affect the licensing of your own software in any way. The LGPL v3.0 license of Nelson does not extend in any way to your own software.
LGPL v3.0 is very different from the GPL v3 in this respect. There are countless examples of LGPL-licensed libraries in very wide use by businesses, including in closed-source applications:
- [https://www.qt.io/faq/ Qt], the C++ application framework.
- [http://webkit.org/ WebKit] components such as WebCore and JavaScriptCore, see [http://webkit.org/coding/lgpl-license.html this page].
- [http://ffmpeg.org/legal.html FFmpeg].
I'm distributing a proprietary, closed-source application that uses Nelson. What am I required to do?
The fact that your application is proprietary does not make any difference here.
There is one such circumstance, this is when you are forking Nelson.
As long as you're not modifying Nelson ''itself'', you can safely ignore this. Hence almost all of our users can safely ignore this.
As you may know, Nelson has a module mechanism that can be used to extend it from the outside.
What you have to keep in mind when using the plugins system is that, when you compile your application, typically:
- Nelson is using your plugin
- The code in your plugin is using code from Nelson
- Your application is using the combination (Nelson + your plugin). It is ''your'' responsibility to pick the right license for your own code so that all of this is possible. If you don't know how to license your module, natural choices to consider are to license it like Nelson, or like your own application (check that the specifics of your case allow it), or under a very permissive license such as MIT or BSD licenses.