I want to use an open-source modular SaaS platform, but it seems that it doesn't let change them, what can I do?
For copyright information, please see the COPYRIGHT file.
X is published under the GNU LESSER GENERAL PUBLIC LICENSE, Version 3 (LGPLv3), as included below. Since the LGPL is a set of additional permissions on top of the GPL, the text of the GPL is included at the bottom as well.
Some external libraries and contributions bundled with X may be published under other GPL-compatible licenses. For these, please refer to the relevant source files and/or license files, in the source code tree.
**************************************************************************
GNU LESSER GENERAL PUBLIC LICENSE Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
You are not allowed to change the license for that module.
So long as your application only uses the library and does not statically link to it, your application can have whatever license it wants (closed, proprietary, whatever), but you must still notify users that a portion of the software has the LGPL-3.0 license.
The idea behind LGPL license (i'm no lawyer either) is basically that you are allowed to use it either "as is", dynamically loaded, allowing users to use the official one instead if they wish, or modify it, in which case you must also provide your changes under the same lgpl license (basically you must publish the source code). the rest of your application, however, can be closed source. In both cases, you must inform the users of the lgpl lib that you are using.
This is as opposed to pure GPL license, that does not allow using it in closed-source apps.
Comments
I want to use an open-source modular SaaS platform, but it seems that it doesn't let change them, what can I do?
For copyright information, please see the COPYRIGHT file. X is published under the GNU LESSER GENERAL PUBLIC LICENSE, Version 3 (LGPLv3), as included below. Since the LGPL is a set of additional permissions on top of the GPL, the text of the GPL is included at the bottom as well. Some external libraries and contributions bundled with X may be published under other GPL-compatible licenses. For these, please refer to the relevant source files and/or license files, in the source code tree. ************************************************************************** GNU LESSER GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.You are allowed to modify it.
Hi Dion, yes based on LGPL3 I'm allowed, but when they add extra info and close this permission, still can change it?
They added:
The text says:
Therefore you are not allowed to distribute a changed copy of the license document.
I am not a lawyer.
It seems that I can't change licence and copyright docs? But I'm allowed change the whole modules?
The TLDRLegal site explains:
I am not a lawyer.
The idea behind LGPL license (i'm no lawyer either) is basically that you are allowed to use it either "as is", dynamically loaded, allowing users to use the official one instead if they wish, or modify it, in which case you must also provide your changes under the same lgpl license (basically you must publish the source code). the rest of your application, however, can be closed source. In both cases, you must inform the users of the lgpl lib that you are using.
This is as opposed to pure GPL license, that does not allow using it in closed-source apps.
For those curious, here is a list of the 264 open-source packages that Autodesk has used, and is legally obliged to publish.