Linked by Thom Holwerda on Mon 21st Sep 2009 08:44 UTC, submitted by Cytor
Permalink for comment 385226
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2005-10-20
That's not entirely true - I believe that you're perfectly free to release your changes, as *just* your changes (eg, patches) under whatever license you wish. It is only when you give out the intrinsically-linked combination (either binary or source) of your changes and the original code, that the GPL is forced onto your code.
The same thing applies to books - you could write something describing how a book's plot should have been, in your opinion, and do whatever you want with it. If you actually edit that book and change it to be the way you think it should have been, however, you can't publish it without the permission of the copyright holder (within the copyright period, and subject to a few other conditions)