Slashdot Mirror


Michigan Diagnostic Software Case Big Win for GPL

Pig Hogger writes "Many people claim that the validity of the GNU Public License has not been tested in court in the US. Well, it just had been, in Michigan, in a case that validated open-source car diagnostic software against the pretension of automakers who want to keep it secret. But don't take my word for it; read the story on GROKLAW." It's actually the Society of Automotive Engineers involved here; DrewTech (the developers in this case) nicely donated half of their settlement money to the SAE.

5 of 307 comments (clear)

  1. Suing for damages? Inappropriate, IMHO by goldspider · · Score: 3, Interesting

    Wouldn't simply compelling the defendant to release the code with the appropriate acknowledgements be more in line with the community spirit of the GPL? A monetary settlement seems unnecessarily punitive.

    --
    "Ask not what your country can do for you." --John F. Kennedy
  2. I don't see anything for the GPL in here by Qzukk · · Score: 5, Interesting

    Yes, the code was written under the GPL, yes the SAE did then take that code and start selling it as if they had written it and without the GPL, but it seems that the entire process was over whether the SAE owns their own regulations after the government steps in and turns them into Law.

    The answer, as it was in the prior case cited, was "no".

    It seems that the license of the software involved wasn't related to the case at all, other than as a "starting point" for the case to begin. If the code had been BSD-licensed, they wouldn't have been suing the SAE first. If nothing else, it simply indicates that you can issue a DMCA takedown notice for GPL'd code someone else is using without obeying the GPL license.

    --
    If I have been able to see further than others, it is because I bought a pair of binoculars.
  3. Re:Not a win, but a settlement by man_of_mr_e · · Score: 3, Interesting

    Not necessarily. Simply being a widely accepted contract doesn't mean the contract is legal. I'm not saying the GPL isn't, just that your argument is faulty.

    As an example, Microsoft's OEM contracts were widely accepted. That didn't mean they were legal.

  4. GPL also wasn't the issue - but proved a good tool by Ungrounded+Lightning · · Score: 3, Interesting

    But remember, the GPL itself is not specifically "tested", per se, because GPL software developers assert them rights granted to them via copyright on an individual basis.

    Also: As I read it GPL wasn't strictly at issue here. The core issue was whether a standards organization can claim IP rights over the standard itself when that standard is embodied as code. Once that issue was clearly articulated both parties seemed to take the enforcability of the terms of the GPL as a given.

    What is important here is that it was the terms of the GPL that allwed Drew Technologies to haul the SAE into court, claim damages from them, and get them to settle WITH a payment of damages.

    The SAE had posted Drew Tech's code, claiming they owned the copyright because it was derivitive of the standard and demanding a "subscription fee" from both Drew Tech and from all other users of Drew Tech's GPLed code.

    The GPL violation was the hook Drew Tech chose to file a takedown demand, drag the SAE into court, and demand damages for violation of THEIR copyrights - like any other GPL software provider. B-)

    Even in the absense of an actual decision, this case shows that licensing your code under the GPL doesn't jepoardize your ability to haul offenders into court and claim (and get settlements for) damages for violating your license terms.

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  5. Re:GPL Derivative Works by Almost-Retired · · Score: 3, Interesting

    I see you still don't 'get' it regarding the GPL. So let one of those freaks you refer to attempt to enlighten you.

    When those GPL'd libraries are linked in, staticly or dynamicly at runtime, you are still making use of code that bears a GPL license. If your code that wants to use that GPL licensed code as part of its functionality isn't GPL also, then the linking is, and properly so, a violation of the GPL and illegal by copyright law.

    There is no 'slightly pregnant' here. If you want to use GPL'd code, then your code must be likewise GPL'd or under an approved similar license. End of discussion.

    Gawd I wish some dummy would actually let this get to where the judge renders his/her opinion for public record and let the precedent actually be set instead of saveing a few on attorneys fees with a settlement when they realise that tweaking the GPL tigers tail is going to get them eaten.

    You're right about one thing, these decisions really are quite obvious. Oh, and go learn how to spell license too. There are in fact several ways, but yours is not among them in my dictionary.

    --
    Cheers, gene
    "There are four boxes to be used in defense of liberty:
    soap, ballot, jury, and ammo. Please use in that order."
    -Ed Howdershelt (Author)
    99.34% setiathome rank, not too shabby for a WV hillbilly