Licensing 101 for Open Source Projects: Choosing an Open Source License

"How the License Type Affects Your Project

"1. Strong copyleft
Choosing a strong copyleft licensee (e.g., GPL) ensures that the source code of all modifications, additions, or derivatives of your work will be disclosed (eventually). In case of the GPL, derivatives are likely to include also other components licensees link your program to and distribute your program with.

"If your project uses a strong copyleft license, most enterprises relying on licensing revenue for their business are unlikely to use your software as their own software linking to your code could be subject to GPL obligations. In fact, many companies have prohibited the use of GPL interally for this very reason. Your code is more likely to be used by companies requiring the software for internal use, or companies that do not rely on license fees for their business but instead make their money out for example the provision of IT services."

Complete Story

Related Stories:

• New CAOS report on open source licenses, uses(Jul 07, 2009)
• Amazon code release irrelevant, Kindle is still closed(Jun 19, 2009)
• Special Episode: Amicus Brief in Jacobsen v. Katzer(Jun 18, 2009)
• FOSS and the Labyrinthine Land of Licensing(May 31, 2009)
• Finding the right open-source savvy lawyer(May 23, 2009)
• How To Turn Customers Into Pirates(Mar 03, 2009)
• Joe 'Zonker" Brockmeier Fights FOSS LIcense FUD(Mar 02, 2009)
• Bruce Perens: How Many Open Source Licenses Do You Need?(Feb 17, 2009)