When to LGPL?
I am a member!
Is there a standard methodology for when code could be licensed under the LGPL?
I understand that it "depends on the circumstances" but I'm at least partially unclear just what those are. For example, are there certain categories of circumstances that drive the differences? (I have heard that even the FSF is now recommending licensing even libraries under the standard GPL.)
Thanks.
Try this
https://www.gnu.org/licenses/license-recommendations.html
--
Gpg Fingerprint: AB3F DF36 512E 1EE1 9055 A8C9 62C6 5508 B625 C793
What's the above? see https://emailselfdefense.fsf.org/en/
I am a member!
I should add that I'm aware of the money issue. Proprietary companies have money to spend developing the LGPL libraries and therefore it may benefit everyone to use their resources to promote the free program/library. I'm just not sure of all of the other factors to consider in choosing the LGPL over the GPL.
LGPL is for when preventing proprietary software from using your library is less important than making your library popular. The classic example is the GNU C Library: there are other C library implementations, so preventing proprietary software from using the GNU C Library would just make them use another (possibly proprietary) implementation.
Here's something on the subject