Hi, I have read the LGPL licence but it left me with more questions than answers.
In a nutshell I plan to host, but not distribute, a commercial application where multiple licensee will get access to an admin interface. That admin interface will
contain, among other elements, the FCK editor.
Thing is, I had to change some of the FCK editor code to fit my needs, such as coldfusion connector files and part of the JS code.
So... to recap.. I'm not going to redistribute the code, but I will have people paying to get access to a UI containing a modified version of your product.
Please let me know if this is acceptable and what notices I should include on my site.
PS, before somebody replies 'read the lgpl', I did, and I think gems such as: <-start-quote> "However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. ... <-endquote>is confusing more than one user who may end up violate some copyright!!!
In a nutshell I plan to host, but not distribute, a commercial application where multiple licensee will get access to an admin interface. That admin interface will
contain, among other elements, the FCK editor.
Thing is, I had to change some of the FCK editor code to fit my needs, such as coldfusion connector files and part of the JS code.
So... to recap.. I'm not going to redistribute the code, but I will have people paying to get access to a UI containing a modified version of your product.
Please let me know if this is acceptable and what notices I should include on my site.
PS, before somebody replies 'read the lgpl', I did, and I think gems such as: <-start-quote> "However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. ... <-endquote>is confusing more than one user who may end up violate some copyright!!!
RE: LGPL Licence: need answers
Yes you can include FCKEditor in a proprietary product without opening *your* source code.
However, you must make available to your clients if requested the source code to FCKEditor, _*including*_ any changes you made to it.
As an example: if you edited fckeditor.cfc you must make your changes available to your clients.
A common misconception is that you must make the source code available to everybody that requests it, not true, you need only release it to those people you "distribute" it to, i.e. your clients (distributing includes over the internet).
You also need to display the LGPL license and warranty of disclaimer, perhaps on an about page.
Also, as an aside (may be relevant to you), if you include any software under a BSD license you don't need to make your source code available but must attribute that the copyright for certain portions of your product belongs to the original author - this must be included in all advertisments (i.e. web pages, press ads) and in the product itself.
|
RE: LGPL Licence: need answers
Thank you very much for your answer, it's clearer now