How not to handle a licensing violation

Posted Apr 13, 2007 6:05 UTC (Fri) by k8to (guest, #15413)
In reply to: How not to handle a licensing violation by lysse
Parent article: How not to handle a licensing violation

It seems the essential issue that the code was being actively considered for use in another project remains, and the rough description is not entirely inaccurate.

Let us all make *some* room in order to allow discussion to occur.

to post comments

How not to handle a licensing violation

Posted Apr 13, 2007 13:00 UTC (Fri) by lysse (guest, #3190) [Link] (1 responses)

But then we have to return to the "hearsay" point. What has been presented isn't evidence of anything except what the original mail writer believed to be the case; he may be mistaken, he may not be aware of the most current facts, etc.

We can make some room, sure; but for one thing, it's manifestly unfair to start slinging concrete accusations around on the back of unsupported hypotheses; and for another, the GPL is clear that it applies to distribution rather than receipt, so the point (of whether the code was about to be reused by Sun, Microsoft, or some random guy who wanted to make his machine work) has no relevance at all.

Which makes it curious that it was raised in the first place, let alone overstated as wildly as it was.

How not to handle a licensing violation

Posted Apr 14, 2007 13:35 UTC (Sat) by Los__D (guest, #15263) [Link]

...the GPL is clear that it applies to distribution rather than receipt, so the point (of whether the code was about to be reused by Sun, Microsoft, or some random guy who wanted to make his machine work) has no relevance at all.

What? Distributions about to reuse a driver, has no affect on the distribution clause? What do you think they would like to reuse it for?