| |||||||||||
SCO's new offensive and the GPLSCO's new offensive and the GPLPosted Jul 22, 2003 16:32 UTC (Tue) by iabervon (subscriber, #722)In reply to: SCO's new offensive and the GPL by jdthood Parent article: SCO's new offensive The same things all apply to, for example, MicroSoft; there are a huge number of MicroSoft developers of varying degrees of technical proficiency. What are the chances that none of them has ever taken code from somewhere else (without a suitable license) instead of writing it like they were supposed to? This is a fundamental problem with copyrights on works which are not intended for distribution (like proprietary source); it's impossible to determine whether something you have belongs to someone else when nobody who knows will tell you. I'm not entirely clear on how the legal system intends this to be resolved (e.g., an author puts someone else's private letter in a book, gives it to a publisher as a work of fiction, and disappears; the original writer recognizes this when the book is published; the publisher couldn't have known beforehand, the plagarist is gone, and the original writer may not want the letter in print, and hasn't been compensated for it, either; what happens?) If anything, the risk with Open Source is that if you are violating a copyright, the copyright holder has a chance of finding out. But there's no more risk there than there is in buying books. And it's certainly possible that hidden offences will be discovered at some point, and a copyright dispute is certain to be much more acrimonious when and accidental offender has been profitting substantially from the offense for a while in secret.
(Log in to post comments)
SCO's new offensive and the GPL Posted Jul 23, 2003 18:48 UTC (Wed) by MathFox (subscriber, #6104) [Link] Improper copying takes place in propriatary software development too. The chances of discovery are small, only a few cases per year become public.Between software vendors the case is usually settled with the infringer taking a licence (paying damages) for the infringed software. The FSF prefers to settle cases like this by demanding the infringing company to change procedures to prevent further infringement. I have heard stories about distributers (Dell) that ask their suppliers to comply with the license (GPL). Awareness of licensing issues is certainly rising. Copyright limits the act of copying to the author and his/her licensees. So, in your example the author is (criminally) wrong in sending a copy of the letter to the publisher. The publisher is wrong (in civil law) by printing the letter in the book. Most publishers will recall the offending book; they are allowed to distribute a reprint with the offending pages removed. The amount of compensation for the original writer of the letter will depend on the damage that he sustained in the incident; the publisher could be sentenced to pay the damages if the author can't be found. [I am not a lawyer, and english is not my native tongue so bear with my choice of words here.]
|
|||||||||||