Linked by Thom Holwerda on Sat 23rd Sep 2006 17:58 UTC, submitted by Ben Jao Ming
Permalink for comment 165443
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 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
Linked by Thom Holwerda on 06/14/13 11:39 UTC
Linked by Thom Holwerda on 06/14/13 11:32 UTC
Linked by Thom Holwerda on 06/13/13 19:39 UTC
Linked by Thom Holwerda on 06/13/13 14:45 UTC
Linked by Thom Holwerda on 06/13/13 11:43 UTC
More News »
Sponsored Links



Member since:
2006-08-31
"Actually, no. In nearly every case, the company involved has opted to do exactly what they were supposed to do in the first place, and that is re-publish the modified code under the GPL."
Sure they released the code, which is now useless on their new WRT54G, because the hardware was redesigned to run on Windriver's OS. Wonder why?
"Actually, no. The products go on to the market just as they were released, and the only thing that needs to be done by the violating company is publish the code."
Sure, except that this exact option of releasing IP is a no no by many companies.
If they only had to release the modified GPL code, then that wouldn't be any problem, and I can understand that perfectly and I also see it as the correct approach.
I modify a public piece of code, I give back the modifications EXCEPT my own additions, unless I want to contribute MY work. That's why the LGPL and BSDs are more corporate friendly than GPL.