Linked by Thom Holwerda on Sat 21st Apr 2012 19:25 UTC
Permalink for comment 515177
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2006-07-14
If it is alongside GPL, I guess not. But the GPL component must be opensource and provided with the product.
That seems to be the general thinking.
Kind of, but that gets confusing when you start talking about issues like the GPL only flag in the kernel, the class path exemption, or how to do that with scripting languages that are not compiled or linked together.
I do like both GPL and BSD licenses, there are valid use cases for both. GPL for great projects where you want contribution from the community, and BSD for when you do want companies to build off of your code base and deeply integrate it with in their products. The BSD is especially nice when trying to get everyone to use a particular standard for operation ( like say TCP/IP