:Licensing 101 for Open Source Projects: Choosing an Open Source License
Licensing 101 for Open Source Projects: Choosing an Open Source License Jul 9, 2009, 22 :03 UTC (0 Talkback[s]) (2244 reads) (Other stories by Ossi Niiranen)
"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."
