Linked by Thom Holwerda on Sat 21st Apr 2012 19:25 UTC
Permalink for comment 515236
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:
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.