Your Web News in One Place

Help Webnuz

Referal links:

Sign up for GreenGeeks web hosting
November 4, 2011 10:05 pm

Ask Slashdot: When and How To Deal With GPL Violations?


jd writes "There are many pieces of software out there, such as seL4 (kindly brought to my attention by another reader), where the vendor has indeed engineered something that they're entitled to Close Source, but where their closed-source license includes the modifications to GPLed software such as the Linux kernel. Then there's a second type of behavior. Code Sourcery produced two versions of their VSIPL++ image processing library — one closed-source, one GPLed. It was extremely decent of them. When Mentor Graphics bought Code Sourcery, they continued developing the closed-course one and discontinued, then deleted, the GPL variant. It's unclear to me if that's kosher, as the closed variant must contain code that had been GPLed at one point. Here's the problem: complaining too much will mean we get code now that maybe four or five people, tops, will actually care about. It will also make corporations leery of any other such work in future, where that work will be of greater value to a greater number of people. So, the question I want to ask is this: When is it a good time to complain? By what rule-of-thumb might you decide that one violation is worth cracking down on, and another should be let go to help encourage work we're never going to do ourselves?"

Read more of this story at Slashdot.


Original Link: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/Ww_2MBRso-w/ask-slashdot-when-and-how-to-deal-with-gpl-violations

Share this article:    Share on Facebook
View Full Article

Slashdot

Slashdot was originally created in September of 1997 by Rob "CmdrTaco" Malda. Today it is owned by Geeknet, Inc..

More About this Source Visit Slashdot