Slashdot Mirror


GPL Lawsuit May Not Settle

A number of readers wrote in to inform us that contrary to earlier indications, it's no sure thing that the lawsuit alleging GPL violation by Monsoon Multimedia will get settled out of court. Linux.com now reports that the SFLC's legal director Daniel Ravicher has stressed that no agreement has been reached: "Simply coming into compliance now is not sufficient to settle the matter, because that would mean anyone can violate the license until caught, because the only punishment would be to come into compliance." (Linux.com and Slashdot are both part of Sourceforge, Inc.)

6 of 285 comments (clear)

  1. Re:Kind of a stupid strategy... by JoelKatz · · Score: 5, Interesting

    No fees are required for any of the rights it grants, yet it puts restrictions on the exercise of those rights (or, if you prefer, the grants are not unlimited). This makes issues that are normally simple to figure out much more difficult.

    For example, if two people negotiate a license agreement that says A can distribute B's book so long as B pays A 15% of the gross receipts, it's clear that the license makes the grant and that the payment is a secondary obligation. If there was non-payment, B would sue A for breach of contract but would have waived the right to sue for copyright infringement.

    The GPL is much more complex because it is non-commercial. The "payment" in the form of reciprocation, yet it's written such that the "payment" is a condition precedent to the grant of rights rather than a secondary obligation. Also, there is no agreement between the two particular parties to the GPL.

    There haven't been enough cases close to the GPL to figure out exactly what the rule is. The general rule is that things outside of copyright (such as payments) are secondary obligations, not conditions precedent but things inside of copyright (such as selling just film rights) are conditions precedent.

    So if I license you to make a movie out my book and you have to pay me $1 million, if you don't pay me, that's a breach of contract. If you sell copies of my book, that's copyright infringement.

    If the GPL is read as a license that waives the right to sue for copyright infringement, that would leave only the ability to sue for breach of contract. If the only penalty the contract allows is loss of license, it's not clear what happens. Do you get back the right you waived? The whole GPL then becomes self-referential. "I waive the right to sue you for copyright infringement so long as you give me the right to sue you for copyright infringement."

  2. Re:Oh yeah by PCM2 · · Score: 3, Interesting

    Stick it to 'em. Make them pay for copyright violations and "loss of revenue".

    IANAL, but the way I understand it, lost revenue is often difficult to prove. In cases where it can be established that the offending party knew that it was violating copyright and willfully did so anyway, however, the court can require payment of statutory damages (which can be much higher than any revenue the plaintiff might have actually lost). The only glitch here is that I was under the impression that you needed to have registered your work with the Copyright Office in advance in order to claim statutory damages.

    --
    Breakfast served all day!
  3. Re:Damages? by QuantumG · · Score: 4, Interesting

    Compensatory damages for open source projects is pretty easy to show. Just look at the prices open source companies charge for "commercial licenses". The claim can be made that by using the work without following the terms of the GPL the infringer is depriving the developers of similar revenues.

    --
    How we know is more important than what we know.
  4. Re:Oh yeah by jhoger · · Score: 3, Interesting

    License != Contract.
    I guess you have consideration. What about the offer and acceptance? Do you really have an exchange of promises?

    A license is not a contract. It is more a one-sided offer of permission to do something that would, without the license grant, be illegal. A license can have restrictions.

    The idea with the GPL is it has restrictions. The logic is that if you don't comply with these restrictions then you never had the right to distribute. And in the case of a copyrighted work, if you redistribute without ownership or a license, and you do it willfully, then you are liable for 3x the statutory damages.

    http://www.informit.com/articles/article.aspx?p=212176&seqNum=3&rl=1

    That's the theory anyway. I guess we'll see.

    -- John.

  5. Re:Excuse me, but this is bunk... by Fruit · · Score: 4, Interesting

    There's no 'intricacies' involved with OSS in the first place- they're simpler licenses to follow.

    Really? Please take the GPL Quiz and tell us what score you got. Hint: it's surprisingly tricky!

  6. So what do they expect to actually get? by harlows_monkeys · · Score: 3, Interesting
    The complaint asks for 5 things:
    1. Injunction to stop infringing copyright
    2. actual damages
    3. profits from the infringement
    4. attorney fees
    5. anything else the court might want to do
    As soon as the defendant complies with GPL, they aren't infringing, so #1 isn't a big deal.

    Actual damages? That's a big fat zero.

    Profits? At this stage in the product's life-cycle, defendant probably isn't profitable yet, so that's likely to be another big fat zero.

    Attorney fees. Finally something that might actually be non-zero!

    I don't see much punishment happening here. They'll settle for attorney fees and some nice (to the developers) but insignificant (to the company) payment.