Which Open-Source License Fits Your Needs Best?

  • Thread starter Thread starter lpetrich
  • Start date Start date
Click For Summary
The discussion highlights the complexity and variety of open-source software licenses, referencing a Wikipedia article on license proliferation. It identifies three main classes of open-source licenses based on their features regarding linking with code under different licenses and releasing changes under different licenses. GPL-like licenses prohibit both linking and releasing changes under different licenses, while LGPL-like licenses allow linking but not the release of changes under different licenses. BSD-like licenses permit both linking and the release of modifications under different licenses, including proprietary ones. The GNU General Public License (GPL) is noted for its "contaminating" effect on included code, while the Lesser GPL aims to allow compatibility with proprietary code. The discussion suggests that despite the classification, there remains significant variation within LGPL-like and BSD-like licenses, with the MIT license being favored for its simplicity.
lpetrich
Science Advisor
Messages
998
Reaction score
180
Comparison of free and open-source software licenses - Wikipedia
Open Source Licenses | Open Source Initiative

There are oodles of open-source licenses that various people and organizations have composed, and I find it rather bewildering. In fact, someone composed an article on license proliferation for Wikipedia.

The main features compared in Wikipedia's comparison are
  1. Link with code using a different license
  2. Release changes under a different license

There are thus three main classes of open-source licenses:
  • GPL-like: (1) no, (2) no
  • LGPL-like: (1) yes, (2) no
  • BSD-like: (1) yes, (2) yes
There are none with (1) no, (2) yes.

The GNU General Public License (GPL) is intended to simulate absence of copyright in the present of copyright. GPLed code also "contaminates" whatever code it is included in, a rather controversial feature.

The Lesser GPL is intended to permit linking of code released on GPL-like terms with code under other licenses, like proprietary code.

BSD-like licenses permit releasing modifications under different licenses, like making them proprietary. The original still remains open.

Even with this classification, there's still a rather sizable field of possibilities in the LGPL-like and BSD-like categories. Any comments or recommendations?
 
Technology news on Phys.org
I don't want to make things any more complicated than they need to be so I use the MIT license.
 
Learn If you want to write code for Python Machine learning, AI Statistics/data analysis Scientific research Web application servers Some microcontrollers JavaScript/Node JS/TypeScript Web sites Web application servers C# Games (Unity) Consumer applications (Windows) Business applications C++ Games (Unreal Engine) Operating systems, device drivers Microcontrollers/embedded systems Consumer applications (Linux) Some more tips: Do not learn C++ (or any other dialect of C) as a...

Similar threads

  • · Replies 2 ·
Replies
2
Views
3K
  • · Replies 12 ·
Replies
12
Views
2K
  • · Replies 13 ·
Replies
13
Views
4K
  • · Replies 17 ·
Replies
17
Views
46K
  • · Replies 19 ·
Replies
19
Views
8K
  • · Replies 13 ·
Replies
13
Views
4K
  • Sticky
  • · Replies 2 ·
Replies
2
Views
503K
  • · Replies 89 ·
3
Replies
89
Views
37K