Linked by Thom Holwerda on Sat 21st Apr 2012 19:25 UTC
GNU, GPL, Open Source "A new analysis of licensing data shows that not only is use of the GPL and other copyleft licenses continuing to decline, but the rate of disuse is actually accelerating." This shouldn't be surprising. The GPL is complex, and I honestly don't blame both individuals and companies opting for simpler, more straightforward licenses like BSD or MIT-like licenses.
Thread beginning with comment 515236
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Practical considerations
by jessesmith on Sun 22nd Apr 2012 17:30 UTC in reply to "RE[2]: Practical considerations"
jessesmith
Member since:
2010-03-11

To answer the above post, not only did I say "license", but I believe I indicated least restrictive license _possible_.

When I'm working on a new project from scratch I will try to license it under a BSD style of license. Basically let anyone do whatever they want with the code. However, sometimes I work on projects which pull pieces from (or are linked to) software already licensed. For example, my most recent project uses code from a GPLed project, so (obviously) my project will have to be licensed under the GPL as well. However, the project I started previous to this one was done from scratch and doesn't incorporate third-party code/libraries and I was able to license it under the BSD license. (Which turned out to be an advantage as it was picked up for inclusion by one of the BSD projects and they probably wouldn't have touched it had I gone with a GPL license.)

I have released a few pieces of code under public domain, but they weren't so much functioning projects as example code which I thought would be helpful for people learning to program, such as college students.

Reply Parent Score: 1