Slashdot Mirror


Strong Court Ruling Upholds the Artistic License

dilute writes "The US Court of Appeals for the Federal Circuit (an authoritative court that normally deals with patent law), has issued a strong ruling (PDF) upholding the Artistic License in a copyright dispute between the developers of the Java Model Railroad Interface (JMRI), and Kamind, a company that used portions of DecoderPro to develop a competing product. The product at issue was DecoderPro, an open source project released on SourceForge under the Artistic License, for interfacing with model railroad control chips. Kamind used a number of DecoderPro files in developing its product, Decoder Commander. However, Kamind did not comply with the Artistic License in a number of respects, including attribution, copyright notices, tracked changes or availability of the underlying standard version." Read on for more, below. Dilute continues: "The lower court denied relief, saying that the Artistic License merely imposed 'contractual' promises, and that a violation did not constitute copyright infringement (any contract-based relief would probably have been meaningless). In a strong ruling, the Federal Circuit found that the Artistic License is legally enforceable, that its terms constituted 'conditions' for reliance on the license, and consequently that a violation of those conditions would put the violating product outside the license and thus make the violator a copyright infringer, potentially liable for an injunction. The case lays out a clear and compelling description of the rationale for open source, and reflects a complete willingness by the court to lend the force of law to these licenses." Reader ruphus13 point to Lawrence Lessig's commentary on the ruling; Lessig calls it "huge and important news," and notes that the reasoning is generalizable to the GPL and other Free software licenses, as well.

149 comments

  1. Good for GPL but... by Anonymous Coward · · Score: 4, Interesting

    ; Lessig calls it "huge and important news," and notes that the reasoning is generalizable to the GPL and other Free software licenses, as well.

    As well as most EULAs I suppose... or is a legal distinction made between license for personal use vs. license for redistribution?

    1. Re:Good for GPL but... by Anonymous Coward · · Score: 2, Informative

      Yes.

    2. Re:Good for GPL but... by Anonymous Coward · · Score: 2, Informative

      is a legal distinction

      IIRC, the original ruling that the lower court made in order to claim that the artistic license was powerless, was that no money changed hands therefore there were wookies on endor or something equally inane.

    3. Re:Good for GPL but... by fishbowl · · Score: 5, Informative

      >or is a legal distinction made between license for personal use vs. license for redistribution?

      Yes, there is such a distinction from the start -- copyright protects distribution, not use.
      You need a specific contract if you want your license to speak to use. For distribution, you
      reserve all rights under copyright law, license or no license.

      --
      -fb Everything not expressly forbidden is now mandatory.
    4. Re:Good for GPL but... by stoolpigeon · · Score: 1

      IANAL-- It's stronger copyright law - but for 'our' side I guess. Interesting.

      I would think with a eula the issues aren't just whether or not it is a license or contract but all the issues with how that agreement is entered by the user. so there is more to it than this, it seems to me.

      With the vast number of Free and Open Source licenses out there, I think it will take a few more cases like this before things really start to get ironed out. Yeah- stuff may bleed over, but it doesn't have to, even if it would make sense.

      --
      It's hard to believe that's how Micronians are made. Why don't we see it right now by having you both kiss one another?
    5. Re:Good for GPL but... by Anonymous Coward · · Score: 0

      That just does not make sense.

      You keep talking trash like that and my head will explode.

    6. Re:Good for GPL but... by HappySmileMan · · Score: 1

      is a legal distinction

      IIRC, the original ruling that the lower court made in order to claim that the artistic license was powerless, was that no money changed hands therefore there were wookies on endor or something equally inane.

      I'd prefer if this was upheld, bad news for FOSS but everyone who gets sued by the RIAA for file-sharing could just state that no money was transferred therefore the copyright license was meaningless

    7. Re:Good for GPL but... by Ruzty · · Score: 1

      Use of a copy of the original work is not at issue. When the license comes into play is in making and distributing copies without abiding by the terms of the license you received the work under.

      If the license says you are authorized to modify the original and distribute said modification as long as you abide by the license's terms and you do not that is copyright infringement. That differs from most EULAs which do not grant a right to duplicate or distribute the work.

      --
      The Master (Angelo Rossitto) in Mad Max Beyond Thunderdome, "Not shit, energy!"
    8. Re:Good for GPL but... by apathy+maybe · · Score: 2, Informative

      EULAs tend to restrict your rights, to less then what is available under copyright law. (E.g. many of them would say that you aren't allowed to make back-up copies, or to reverse engineer the software, both of which are allowed (at least) under Australian copyright law (I believe).)

      However, free software licences enhance what you are allowed to do. Enabling, for example, you to re-use software in your own work.

      However, these licences tend to say that you have to follow certain conditions if you wish to have this extra freedom. The most common being attribution.

      In the case mentioned, one actor (company or person, whichever), took code from another actor's project and used it without permission in a manner which wasn't permitted by the licence for that code.

      If there was no licence for the code, then that would be a strict copyright violation. There was a licence, and reuse was allowed, under certain conditions. However, because these weren't followed, bang copyright violation (as if there wasn't a licence at all).

      Insert standard disclaimer here.

      --
      I wank in the shower.
    9. Re:Good for GPL but... by mrchaotica · · Score: 0

      is a legal distinction made between license for personal use vs. license for redistribution?

      A distinction should be made, since personal use doesn't require a license to begin with. Think about it: when's the last time you had to agree to an EULA to read a book you bought, or wear a shirt you bought, or listen to a CD you bought, or watch a movie you bought, or even played a (console-based) video game you bought? These things are no different than using software you bought.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    10. Re:Good for GPL but... by HappySmileMan · · Score: 2, Informative

      IANAL-- It's stronger copyright law - but for 'our' side I guess.

      It's not stronger copyright law, the way copyright works has not changed at all, it's just an already existing copyright being honoured by the federal court, after for some reason a lesser court refused to honour it. I could probably explain better if I RTFA but we all know that's not going to happen

    11. Re:Good for GPL but... by stoolpigeon · · Score: 1

      I don't know what would be the best words for it - but some people thought the wording was ambiguous enough that the license wouldn't be afforded certain protections and this court has said the language was acceptable. Maybe stronger isn't right - how about broader? Or a change in how copyright law is applied? Something definitely has changed here in my opinion.

      --
      It's hard to believe that's how Micronians are made. Why don't we see it right now by having you both kiss one another?
    12. Re:Good for GPL but... by 2nd+Post! · · Score: 2, Funny

      Does this mean you don't believe in copyright?

    13. Re:Good for GPL but... by mrchaotica · · Score: 4, Informative

      IANAL-- It's stronger copyright law - but for 'our' side I guess.

      On the contrary, the issue being decided here is copyright law. To say that the Artistic License is "stronger than copyright law" makes no sense, as it relies on copyright law for its enforcement. In essence, the court ruled that the Artistic License works the same way as the GPL (even though the GPL makes it explicit and the Artistic License doesn't):

      You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.

      (GPL version 3, section 9; emphasis mine)

      The argument made by the emphasized text is the same argument that the JMRI people made here (and that the judge agreed with).

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    14. Re:Good for GPL but... by HappySmileMan · · Score: 1

      I was joking.

    15. Re:Good for GPL but... by Svartalf · · Score: 1

      Ahh... The wookie defense... >:-)

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    16. Re:Good for GPL but... by stoolpigeon · · Score: 2, Informative

      I'm not trying to say the license is stronger than copyright law. I was trying to say that by making the license more than a contract they've made copyright law stronger, broader - however it would be best put. In fact, if I understand you correctly, I was trying to say what you just said.

      --
      It's hard to believe that's how Micronians are made. Why don't we see it right now by having you both kiss one another?
    17. Re:Good for GPL but... by Anonymous Coward · · Score: 0

      I never understood why the GPL was a eula?

      As an end user I could care less. I don't even need to agree to the gpl to use it.

      The GPL is basically irrelevant for usage of a program, but for some reason many OSS apps insist on making you click "i agree" when installing the binaries..

    18. Re:Good for GPL but... by mrchaotica · · Score: 4, Informative

      I never understood why the GPL was a eula?

      Exactly: it isn't one!

      for some reason many OSS apps insist on making you click "i agree" when installing the binaries..

      Yep, this is a fairly serious bug in those software's installers. I keep meaning to file it on OO.o's tracker...

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    19. Re:Good for GPL but... by Anonymous Coward · · Score: 0

      That's doublethink, free software licenses also restrict what you are allowed to do, just not to the extent of the licenses applied to proprietary software.

    20. Re:Good for GPL but... by hedwards · · Score: 2, Informative

      This wouldn't be an EULA situation, it's a license issue on the code itself. Had the party being sued been an end user it would have been a very different situation. But they took the code, incorporated it into a product and sold that product.

      Along the way they apparently violated the licensing on the code on multiple fronts and are now likely to be taken to task for doing so.

      It's a much easier case to make, once you've managed to subpoena the code than enforcing a EULA would be. For instance you don't have to spend time and effort trying to figure out who agreed to it.

    21. Re:Good for GPL but... by fishbowl · · Score: 5, Insightful

      Rights that are asserted under copyright, are not surrendered based on any money changing hands.

      You have two concepts confused: Rights are reserved, not granted, but contracts require consideration.
      I think you have the ideas of a "License" and a "Contract" conflated. A contract is not valid without
      consideration (e.g., "money changing hands"), but rights are reserved by default.

      --
      -fb Everything not expressly forbidden is now mandatory.
    22. Re:Good for GPL but... by fishbowl · · Score: 2, Insightful

      >I never understood why the GPL was a eula?

      It is not. It is a license that makes a limited grant of distribution rights, rights that would otherwise be fully reserved by default under copyright law.

      It has nothing whatsoever to do with "end users", and even goes as far as to explicitly point this out (even though it is not necessary to do so).

      A EULA would be valid if it were a contract (with a meeting of minds, agreement on the subject matter, and consideration), but most EULAs are not contracts, and therefore serve little purpose aside from "notice" (and "notice" does have some value in a legal sense).

      --
      -fb Everything not expressly forbidden is now mandatory.
    23. Re:Good for GPL but... by vux984 · · Score: 4, Insightful

      Yes, there is such a distinction from the start -- copyright protects distribution, not use.

      copyright protects *copy rights* including: copying, redistribution, performance, and broadcast.

      You need a specific contract if you want your license to speak to use. For distribution, you
      reserve all rights under copyright law, license or no license.

      What difference does it make when "using" the software entails making a copy to your hard drive, and then another copy into ram, and then another copy into cache? Using it entails copying it.

      If I have no license to use it, I can't make those copies.

      So you can't use it without a license.

      And the courts have ALREADY made rulings that apply copyright infringement to occurring in an unauthorized 'disk to RAM' copy made by that WoW cheat program. (glider?)

    24. Re:Good for GPL but... by Sloppy · · Score: 4, Interesting

      the reasoning is generalizable to the GPL and other Free software licenses

      As well as most EULAs I suppose...

      Let's all hope. This could totally trash EULAs that some people have been attempting to enforce despite the other parties never taking the offer.

      JMRI: we offer you the terms of this license, if you are not satisfied with the rights and prohibitions of copyright law.
      Kamind: Fuck you.
      Court: Very well, forget the license, since you're obviously not electing to take the deal that JMRI offered. The terms of copyright law are now in force.
      Kamind: May I create and sell derived works?
      Court: Copyright law says you may not.
      Kamind: oh, crap.

      Apple: We offer you the terms of this license, if you are not satisfied with the rights and prohibitions of copyright law.
      User: Fuck you.
      Court: Very well, forget the license, since you're obviously not electing to take the deal that Apple offered. The terms of copyright law are now in force.
      User: May I install the software I bought on my computer even if Apple didn't make the computer?
      Court: Copyright law says you may.
      Apple: oh, crap. we should have required signing a sales contract, as a condition for obtaining the software.
      Blizzard: oh, crap.

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    25. Re:Good for GPL but... by fishbowl · · Score: 1

      >copyright protects *copy rights* including: copying, redistribution, performance, and broadcast.

      Yes, I know. I've studied and practiced entertainment law.

      I'm not willing to go down the "copy to your hard drive in order to use it" road with you right now,
      although I understand the argument, including the Blizzard case.

      --
      -fb Everything not expressly forbidden is now mandatory.
    26. Re:Good for GPL but... by stinerman · · Score: 4, Insightful

      They should put the GPL in the license agreement spot, but allow the "next" button to be clicked even if the agreement is not read or agreed to.

      A small blurb saying acceptance is not required to use the software, but is required to distribute copies (modified or otherwise) would be an extra perk.

    27. Re:Good for GPL but... by russotto · · Score: 1

      What difference does it make when "using" the software entails making a copy to your hard drive, and then another copy into ram, and then another copy into cache? Using it entails copying it. If I have no license to use it, I can't make those copies. So you can't use it without a license.

      In the United States, you can. 17 USC 117(a). Which is why EULAs are unnecessary, and why this ruling does not necessarily mean that violating an EULA is violation of copyright.

    28. Re:Good for GPL but... by Todd+Knarr · · Score: 3, Informative

      USC Title 17 Chapter 1 section 117 paragraph (a) grants permission to make certain copies, eg. those neccesary for running a computer program. To be technically picky about it, it says that it is not an infringement of copyright to make those copies or to authorize having them made.

    29. Re:Good for GPL but... by orclevegam · · Score: 1

      Something has been resolved, not changed. It's one of the flaws with out legal system (a great many legal systems actually), that until a law has been brought to court (often many times), and all the edges cases get ironed out, there's a lot of wiggle room in exactly what the law "means" and whether it applies in this or that case. All this ruling has done is nailed down one of those edge cases, in copyright law.

      --
      Curiosity was framed, Ignorance killed the cat.
    30. Re:Good for GPL but... by mrchaotica · · Score: 4, Insightful

      What difference does it make when "using" the software entails making a copy to your hard drive, and then another copy into ram, and then another copy into cache? Using it entails copying it.

      Although I admit that some judges have been stupid enough to buy it, that argument is bullshit because those copies are incidental to the physical workings of the medium, and express no intent on the part of a human.

      By the same argument, DVDs would require an EULA because they're decrypted and stored in the DVD player's RAM, the Internet couldn't exist as we know it because routers would violate copyright if they were set to store-and-forward (and I'm not even going to mention proxy and mail servers!), books would require an EULA because their information is copied into photons by the light reflecting off them and into the reader's eyes, etc. It's absurd.

      And this isn't even a Fair Use argument: the installation of software onto hard drives and duplication into RAM shouldn't even count, legally, as copies to begin with! (As long as there's a one-to-one correspondence between the installed program and its installation media, of course.)

      And the courts have ALREADY made rulings that apply copyright infringement to occurring in an unauthorized 'disk to RAM' copy made by that WoW cheat program. (glider?)

      And those courts were wrong.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    31. Re:Good for GPL but... by Svartalf · · Score: 3, Informative

      It's NOT a EULA.

      The GPL doesn't cover USAGE (In fact, it explicitly prohibits the placing of any restrictions on usage by downstream recipients...)- it covers a little different thing.

      It covers publication and derivative works.

      If you give a copy to someone else, you're publishing a copy.

      If you make a modification to the protected work and then give that to someone else, you're making a derivative work.

      Neither is usage in the eyes of Copyright Law.

      If you fail to abide by the terms under which you are given permission to do so by the various rights holders, you don't have their permission and thereby are guilty of straight Copyright Infringement.

      Willful acts thereof are viewed in a very dim light by the Courts and the Law.

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    32. Re:Good for GPL but... by Anonymous Coward · · Score: 5, Insightful

      It's not stronger copyright law, it's just common-sense upholding of contracts.

      JMRI offered a license which overrides copyright law and Kamind violated the terms of that license. The court is saying that when Kamind broke the terms of the license, the copyright-defying activities that the license allowed, were no longer allowed.

      If I offer to trade you a moon rock for a pint of ice cream, and you don't give me a pint of ice cream, then you don't get my moon rock. Kamind wanted to take the moon rock anyway, and then say, "Don't like it? Then sue me for the value of a pint of ice cream! Nyah nyah!" JMRI says, "No, I'm suing you for the value of my moon rock."

    33. Re:Good for GPL but... by stoolpigeon · · Score: 1

      I'd consider bringing clarity where there was confusion to be a change. We could play these games all day. I'm glad I'm not a lawyer - it would drive me nuts picking apart every little word.
       
      But back on topic - there are people that have made decisions based on the lack of clarity in this very situation as well as others. Now that it is less foggy, they make different decisions now. Once again, in my book, change.
       
      I'm just glad it fell this way. I think it could have turned out differently - because to be honest I don't think the artistic license was worded all that well. But we learn as we go I guess.

      --
      It's hard to believe that's how Micronians are made. Why don't we see it right now by having you both kiss one another?
    34. Re:Good for GPL but... by Anonymous Coward · · Score: 4, Insightful

      There is always the merchantability argument to counter that. If you sell me a product which requires specific technical steps to use and then don't allow me (by whatever mechanism) to take those steps, the product is useless.

      To use a DVD as intended and marketed, my DVD player has to be able to read the disc, store and decrypt the data stream, copy it to a buffer, stream the video to a TV, and so on. If you prevent me from doing so, that would be a form of fraud because you marketed and sold it as a way to watch a movie.

    35. Re:Good for GPL but... by vux984 · · Score: 1

      Although I admit that some judges have been stupid enough to buy it, that argument is bullshit

      For what its worth, I agree it SHOULD be bullshit. The trouble is that the courts ARE buying it.

    36. Re:Good for GPL but... by cfulmer · · Score: 2, Informative

      Eeehhh....

      In-memory copies count as copies. But, if you are the owner of a copy of computer software, then you can (under 17 U.S.C. 117(a)) copy it into computer memory for the purpose of running it without infringing.

      The reason that EULAs are important is because software publisher asserts that you are not an owner of a copy. And, if you're not an owner of a copy, then Section 117(a) doesn't apply. There have been court decisions on both sides of this one.

      As for your arguing about temporary buffer copies, those aren't "fixed" under the copyright act and thus are not infringing copies. (See the recent Cablevision case for a longer discussion). Your other cases (such as store-and-forward email) are cases either of an implied license or where there was no volitional act. (You're not liable if somebody else causes your computer to make a copy and you don't even know that copy exists.)

      Copyright Infringement actions are decided under strict liability -- the "intent" of the person doing the copying doesn't matter.

    37. Re:Good for GPL but... by mr_mischief · · Score: 1

      No, it's the copyright law that limits what you can do. Free software licenses loosen some of those restrictions somewhat. They just don't loosen them as much as certain other OSS license or placing the work in the public domain.

    38. Re:Good for GPL but... by cfulmer · · Score: 1

      For the most part, the GPL only covers distribution. But, there are some terms that cover the end user -- see, for example, sections 15 and 16 of GPL v3. These are VERY much the sort of thing that EULAs are intended to cover.

    39. Re:Good for GPL but... by cfulmer · · Score: 1

      When you buy software knowing that it is covered by a license agreement the seller intends to apply to you, the sale itself is conditioned upon your acceptance of the license. See http://en.wikipedia.org/wiki/ProCD_v._Zeidenberg .

    40. Re:Good for GPL but... by swillden · · Score: 3, Informative

      What difference does it make when "using" the software entails making a copy to your hard drive, and then another copy into ram, and then another copy into cache? Using it entails copying it.

      It makes a HUGE difference, since US copyright law specifically exempts copies that are necessarily made in the normal course of use. Those copies cannot legally be considered copyright infringement.

      Specifically, the law says:

      Making of Additional Copy or Adaptation by Owner of Copy. â" Notwithstanding the provisions of section 106, it is not an infringement for the owner of a copy of a computer program to make or authorize the making of another copy or adaptation of that computer program provided:

      (1) that such a new copy or adaptation is created as an essential step in the utilization of the computer program in conjunction with a machine and that it is used in no other manner, or

      (2) that such new copy or adaptation is for archival purposes only and that all archival copies are destroyed in the event that continued possession of the computer program should cease to be rightful.

      Emphasis mine, of course.

      So, the GP is absolutely correct: EULA's that try to impose additional restrictions BEYOND what copyright law imposes must be interpreted as contracts, and there must be some consideration paid to the seller that justifies the buyer giving up those rights that he or she would otherwise have.

      Copyleft licenses of various sorts, on the other hand, impose no restrictions that aren't already imposed by the law. Instead, they just grant permission to make copies and derived works, subject to some requirements.

      In both cases, mere normal use of the program, even if that involves making copies on a hard drive, in RAM, etc., are not copyright infringement.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    41. Re:Good for GPL but... by mr_matticus · · Score: 1

      It is not. It is a license that makes a limited grant of distribution rights, rights that would otherwise be fully reserved by default under copyright law.

      You cannot impose terms and restrictions or require action through the use of a license; a license is a grant. If you are imposing terms, it's a license agreement, period. Whether you want to consider the affected party an end user or not is really immaterial.

      The GPL is indeed a EULA in the broad sense that it is a distribution agreement from a content owner and its licensees. The term is based on a notion that everyone who is not the developer/owner or a merchant is an end user. The basic term is perhaps inadequate, but the idea of derivative developers vs. "end users" is an unimportant distinction. It is really at this point simply a straw man for false pedanticism, particular since the industry term is SLA, not EULA.

      most EULAs are not contracts

      An assertion without backing. A software license agreement is per se valid, and always has been. This case simply confirms it. Whether it's the Artistic License, the GPL, or a proprietary license, they are enforceable, less any unlawful provisions. No case has ever held otherwise.

    42. Re:Good for GPL but... by gnasher719 · · Score: 5, Insightful

      It's not stronger copyright law, the way copyright works has not changed at all, it's just an already existing copyright being honoured by the federal court, after for some reason a lesser court refused to honour it. I could probably explain better if I RTFA but we all know that's not going to happen.

      The judge in this case corrected a blatant error by the District Court.

      Like the GPL, the Artistic License basically says "You can copy this software provided you do X, Y and Z". The correct interpretation of this license is: If I do X, Y and Z then I have the right to copy the software. If I don't do X, Y and Z, then I have no right to copy the software, and copying is copyright infringement, and courts will stop me from doing it if the copyright holder asks them. The wrong interpretation, used by the District Court, was: I have the right to copy the software. I am also obliged to X, Y and Z, and if I don't do them, then the copyright holder can sue me to do X, Y and Z or pay damages. However, the copyright holder cannot stop me from copying. As I said, this has now been declared the wrong interpretation.

    43. Re:Good for GPL but... by mr_matticus · · Score: 4, Informative

      I have no idea how this got modded insightful. It doesn't even make sense.

      You have two concepts confused: Rights are reserved, not granted, but contracts require consideration.

      Contracts have nothing to do with it. Copyright does indeed deal with reserved rights--the creator's rights. Any right not granted by copyright or by independent agreement is reserved by the owner. Copyright does not supersede contractual rights; indeed, the entire point of contract law is to create relationships outside of or contrary to statutory law.

      A contract is not valid without
      consideration (e.g., "money changing hands"), but rights are reserved by default.

      What does this even mean? Consideration is one way of validating a contract (but not the only way), and this has exactly nothing to do with reserved rights.

      A license is a grant of rights. It is a promise not to sue. That's it. The GPL is not a license, because it says, "I promise not to sue IF you do x, y, and z"--that is a license agreement. It contains a license, but it too requires assent. Failure to provide that assent results in failure to attain the needed license, thus placing a person in a position of copyright inflation. The attempt to characterize it here as mere breach of contract is an attempt to limit potential judgments, as contractual damages are far less than statutory copyright damages.

      It is not a binary situation. Finding copyright infringement does not preclude breach of contract, and in fact the two usually go hand in hand in licensing disputes. It is possible to infringe the copyright without breaching the contract, and it is also possible to breach the contract without committing copyright infringement.

    44. Re:Good for GPL but... by ksd1337 · · Score: 1

      The Mozilla Foundation knows this, as they have an EULA for their binary releases.

    45. Re:Good for GPL but... by Dachannien · · Score: 1

      Blizzard: oh, crap.

      Wrong. You have to agree to the EULA/ToS before subscribing to their service, and they offer a full refund to anyone who, before subscribing, decides they don't want to accede to the EULA/ToS.

      In general, that pretty much takes care of the big problem that the courts have had with shrinkwrap licenses (that you must buy the software and complete the transaction before you can read the EULA). While the refund provision, AFAIK, hasn't been tested in court directly, it stands to reason that the court's concerns would be ameliorated by such a provision. In the absence of a shrinkwrap concern, EULAs have generally been found valid, barring other standard contract law issues like unconscionable terms, etc.

    46. Re:Good for GPL but... by bcrowell · · Score: 1

      for some reason many OSS apps insist on making you click "i agree" when installing the binaries..

      Yep, this is a fairly serious bug in those software's installers. I keep meaning to file it on OO.o's tracker...

      The really annoying thing about it is that on a shared Windows box, it demands that every user click through the license.

    47. Re:Good for GPL but... by crossconnects · · Score: 2, Informative

      Contracts require consideration, and that means that a contract must have benefits going to each party. This may involve money, but a contract that grants benefits to one party, but not the other is considered to have been forced, and is therefore not enforceable.

      I did not read the article, but it appears the court decided that this is not a contract issue as the lower court said, but rather a copyright issue, and that Kamind apparently violated it.

      --
      no big sig
    48. Re:Good for GPL but... by mr_matticus · · Score: 2, Informative

      Contracts require consideration, and that means that a contract must have benefits going to each party.

      No. Consideration is not benefit.

      a contract that grants benefits to one party, but not the other is considered to have been forced

      No. A contract involving acts on one party may be unilateral or gratuitous, but being "forced" has nothing to do with whether the contract is a good deal for both parties. Voluntary entry into an agreement not requiring unlawful activity is not "forced".

      I did not read the article, but it appears the court decided that this is not a contract issue as the lower court said

      Then perhaps it would be best to refrain from speculation, since that is not what the opinion says at all. The operative language is "only for breach of contract", which is not the issue. The issue is the availability of copyright infringement as a cause of action, wherein the lower court erred in rejecting the theory.

      Once again, it is not either/or.

    49. Re:Good for GPL but... by fishbowl · · Score: 1

      >>most EULAs are not contracts

      >An assertion without backing.

      EULAs are not contracts. That assertion has plenty of "backing".

      Where's the consideration? Where's the meeting of the minds? Even if it's a contract of adhesion, where are the parties' rights in terms of "reasonable expectations?"

      Quickly now, list the four criteria required to make an agreement "a contract" under US law.

      --
      -fb Everything not expressly forbidden is now mandatory.
    50. Re:Good for GPL but... by mrchaotica · · Score: 1

      Okay, but Section 9 contradicts that. Considering that it explicitly says that you don't have to accept the GPL to run the program, does that mean that the warranty and liability are not actually disclaimed until one conveys the program (and thus agrees to the GPL)?

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    51. Re:Good for GPL but... by cfulmer · · Score: 1

      So that's one of the reasons I think the GPL could have used a little more editing by a good lawyer. Those sections are clearly intended to apply to all uses, but because of Section 9, there's a decent argument that they don't.

    52. Re:Good for GPL but... by mr_matticus · · Score: 1

      EULAs are not contracts. That assertion has plenty of "backing".

      Citation please.

      Where's the consideration? Where's the meeting of the minds? Even if it's a contract of adhesion, where are the parties' rights in terms of "reasonable expectations?"

      Agreement with consideration is just one of at least five judicially-recognized theories of contractual obligation, but since that's the wheelhouse you want to stay in, so be it. The consideration is a promise backed by money (or an exchange promise) versus delivery of a valuable product. There is no issue of a meeting of the minds, because the terms are laid out and assented to. It's not a case of mistake or misrepresentation, and even mentioning it is nothing more than a red herring.

      As to "rights" with "reasonable expectations", your use of the terminology smacks of amateurism. The reasonable expectation in a software licensing arrangement are the nonexclusive use of the product, subject to the terms of the license chosen. In 2008 it is well past the point where the existence of license terms is a surprise. As long as consumer software has been available, they have included various terms designed to protect the interests of both parties.

      The tool is wrongly maligned based on inappropriate uses. It's no better to make your attack than to question contracts in general because they are abused by some.

      Quickly now, list the four criteria required to make an agreement "a contract" under US law.

      "A contract" has two parts. Offer and acceptance. Anyone who attempts to break the elements of a contract down into a specific number of parts (beyond offer and acceptance) is acting on Cliff's notes at best. What constitutes an offer and acceptance varies based on the type of contract being considered and the specifics of the bargain.

      I would imagine, however, that you are referring to agreement, consideration, intent, and some combination of capacity or memorialization, depending on where you live. The purpose of this exercise, though, is unknown.

    53. Re:Good for GPL but... by kjots · · Score: 1

      Although I admit that some judges have been stupid enough to buy it, that argument is bullshit

      For what its worth, I agree it SHOULD be bullshit. The trouble is that the courts ARE buying it.

      Now is the time to decide if we want to be complacent about such a situation, or outraged.

      I've made my decision, how about the rest of you?

    54. Re:Good for GPL but... by mdmkolbe · · Score: 1

      17 USC 117 explicitly allows you to make as many copies as necessarily to utilize a computer program. So it sound to me like if you own a legal copy(*) you are allowed to install it.

      (*) "Copy" is defined by 17 USC 101 to be the material object "in which a work is fixed" so legally owning a CD with the program on it is owning a legal copy.

      (IANAL but I want to understand, so corrections from more informed readers are welcome. Glider is a bit of a puzzle to me so I'm not sure how it jives with this section of the law.)

    55. Re:Good for GPL but... by mdmkolbe · · Score: 1

      The reason that EULAs are important is because software publisher asserts that you are not an owner of a copy. And, if you're not an owner of a copy, then Section 117(a) doesn't apply. There have been court decisions on both sides of this one.

      Since Section 101 says that copies are "material objects ... in which a work is fixed" and I don't think anyone could reasonably claim you don't own the physical media of a game bought from the store, it really puzzles me how those rulings came about.

    56. Re:Good for GPL but... by omfgnosis · · Score: 1

      Fuck it what's on tv

    57. Re:Good for GPL but... by JoelKatz · · Score: 2, Interesting

      No, the District Court had it right. If your license says "you can copy this software provided you do X, Y, and Z", then you have a license to copy the software. No doing X, Y, and Z violates the license, but does not violate copyright law.

      I can't make a license that says, "you can copy this software provided you don't pick your nose" and then sue you for copyright infringement for picking your nose.

      Because lawsuits for copyright infringement have special powers (like statutory damages and a presumption of irreparable harm), we can't let people decide what's copyright infringement just by writing it in a license. Congress has to do that.

      This ruling is very wrong and very troubling.

    58. Re:Good for GPL but... by Anonymous Coward · · Score: 2, Informative

      Idiot. The license says "if you do not pick your nose, you are allowed to do what you like with the software - copyright law does not apply". If you then pick your nose, the license is invalidated and copyright law, as decided by Congress, applies. The license is not deciding what copyright infringement is, you moron, the license is granting exemption from copyright law provided you follow its terms.

    59. Re:Good for GPL but... by Just+Some+Guy · · Score: 2, Informative

      I can't make a license that says, "you can copy this software provided you don't pick your nose" and then sue you for copyright infringement for picking your nose.

      You absolutely can. Absent a license, I have no right to distribute your work. If you grant me a license to copy if I agree to certain conditions, and I fail to meet those conditions, then the license is void. At that point, the baseline default of "no copies allowed" as set forth in copyright law is in force.

      The court was absolutely correct. When Kamind failed to meet the conditions of their license, it was revoked. From that moment on, they were distributing JMRI illegally.

      --
      Dewey, what part of this looks like authorities should be involved?
    60. Re:Good for GPL but... by Just+Some+Guy · · Score: 1

      Exactly: it isn't one!

      Note that its officially sanctioned cousin, the AGPL, is a EULA in that it specifically restricts end users from making certain modifications (namely removing any built in redistribution mechanism).

      --
      Dewey, what part of this looks like authorities should be involved?
    61. Re:Good for GPL but... by JoelKatz · · Score: 1

      The license is deciding what copyright infringement is, and that's precisely what pretty much every court to consider the issue has found.

      Copyright violation is when you act *without* a license and do something that copyright law prohibits. Violating the terms of a license is a mere contract violation.

      Copyright violation is very special. It permits you to presume irreparable harm. It permits you to seek statutory damages. Mere violations of contract do not give you these extra powers.

      If you have a citation, I'd love to see. But given that you posted anonymously, odds are you are as misinformed as your are cowardly.

      You must exceed the scope of a license *under* *copyright* *law* to violate copyright law. For example, if you have a license to publish the book, and you publish it but don't pay me the amount agreed in the license, that's a contract violation. If you create a sequel to the book, that's a copyright violation (since the license never gave you the right to create derivative works).

      Every other court has held that a license cannot transform any act other than those prohibited by copyright law into copyright violations. They become mere violations of the license agreement.

    62. Re:Good for GPL but... by JoelKatz · · Score: 1

      "If you grant me a license to copy if I agree to certain conditions, and I fail to meet those conditions, then the license is void."

      No, that's precisely not true. If you fail to meet those conditions, then you have violated the contract that required you to meet them.

      "The court was absolutely correct. When Kamind failed to meet the conditions of their license, it was revoked. From that moment on, they were distributing JMRI illegally."

      This is precisely what every other court has held that you cannot do. You cannot use a license to create new violations of copyright law. If the license grants you permission to do something, then doing that something is not a violation of copyright law.

      This is so for a very precise reason. Copyright violations are special. You can seek statutory damages. You can presume irreparable harm. None of these things make sense when the action is a mere violation of a contract.

      Can you cite *any* other court that has held that a contract can turn failure to comply with license terms into a violation of copyright law?

      The only cases I could find were cases where, for example, the license allowed publication but the licensee created derivative works. That make sense -- copyright law makes creating derivative works a distinct right from copying, so you can license one but not the other.

      Put up or shut up.

    63. Re:Good for GPL but... by Aladrin · · Score: 1

      Yes, but how can I agree to something I've never read? If EULAs were all identical, or able to be read before the sale, I could agree with you. But they aren't, and you can't. And getting your money back is not possible in some case without going to court over it.

      I don't care if a court case DID decide that it's legal, it's obviously stupid and I don't think it would stand up if tried properly.

      --
      "If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
    64. Re:Good for GPL but... by Just+Some+Guy · · Score: 2, Insightful

      Put up or shut up.

      I don't have to. A federal appellate court says that my interpretation is right and your's is wrong. At this moment in time, my take on it is legally verified for a very large chunk of the American population.

      --
      Dewey, what part of this looks like authorities should be involved?
    65. Re:Good for GPL but... by cfulmer · · Score: 1

      Well, you've just given the argument for the rulings that say that you do have that right. Basically, those say that if you get a copy and you don't have to give it back, then you own it.

      The other side says that if you get a copy and agree that you don't own it, then you don't own it. And, that agreement comes in the license "agreement" which is binding because you bought the software knowing that it was covered by a license agreement.

    66. Re:Good for GPL but... by mdwh2 · · Score: 2, Informative

      And the courts have ALREADY made rulings that apply copyright infringement to occurring in an unauthorized 'disk to RAM' copy made by that WoW cheat program. (glider?)

      Nope, Glider was only a problem because the copying to RAM wasn't part of the software's normal operation. Copying to RAM when you use the software is allowed, as the other commenters have pointed out.

      The title of this article should be "Strong Court Ruling Upholds Copyright Law", which isn't really surprising. There's nothing in here that means that any arbitrary one-sided set of claims (e.g., an EULA) suddenly becomes legally enforceable.

    67. Re:Good for GPL but... by cfulmer · · Score: 1

      You have the right to return it if you don't accept the license agreement. Whether the store wants to make it easy is another matter. This is a case whether common practice differs from the legal requirement.

      I've read the case, and it was absolutely "tried properly." The Court's view (in response to your original point) was that it would be silly to require the EULA to be printed on the outside of the box when there's potentially a lot more useful things that can be put there.

      An interesting situation comes up when companies don't put any indication of an EULA on the packaging at all -- if my recollection of the case is correct, it was premised on the box saying something like "subject to the terms contained in the EULA." If you don't have at least that sort of minimum statement on the box, then it's harder to claim that you should be bound by the EULA. (Of course, just about all software is accompanied by a license agreement, so that's not a particularly strong case.)

      Note that one of the problems is tiered licensing , which is especially common in enterprise software. Basically, a company sends out one disk and says "If you're going to run this on a desktop, the price is $XXX. If you're going to run this on a typical server, the price is $XXX and if you're going to run this on a huge multi-core enormous server, the price is $XXX." If you actually buy a copy of the software (instead of just licensing it), then you could pay the desktop price and install it on the ginormous server.

    68. Re:Good for GPL but... by Sloppy · · Score: 4, Interesting

      An interesting situation comes up when companies don't put any indication of an EULA on the packaging at all

      Like this this? You and I are unusual people; yes, we read slashdot, follow trends in the software industry, and know that many, probably most, proprietary software packages come with some sort of statement about a license. But if Joe Sixpack looks at that page the above link points to, he would have no idea that a transaction between him and Amazon causes him to be bound by a contract with a third party. He would have no reason to even suspect it. By the time he receives the box, whether there's something printed on the outside or the inside, he has already paid Amazon.

      And god help him if, when the box shows up on his doorstep, someone else (e.g. his kid) opens the box and installs it on his computer. With every other contract in every part of my life, there was never even a chance that someone else who doesn't have power-of-attorney (or good forgery skills), could perform an act that gets me into a contract unknowingly. And that's not surprising; it's fundamental to the concept of responsibility.

      It gets even weirder to think that when the box arrives, Joe Sixpack owns the box and its contents, but as soon as he (or someone else!? see above paragraph) looks at it or opens it and becomes aware of the existence of some license, his ownership ceases and is replaced by licensing. I guess we should call that the Heisenberg uncertainty principle of software ownership.

      If the courts assert the license is binding anyway (and the courts have to, since none of the legislatures have done so), they are making a very special case, where purchases of this one type of product (software), works unlike anything else in the realm commerce.

      You have the right to return it if you don't accept the license agreement.

      That right is asserted inside the license. Taking advantage of that, presumes that the unwitting buyer has already read and accepted the license. What if that's not the case?

      Whether the store wants to make it easy is another matter. This is a case whether common practice differs from the legal requirement.

      That just points out Yet Another paradoxical consequence of the ProCD court's misunderstanding. If users are bound by Apple's license when they buy software from a third party like Amazon, how did Amazon avoid being bound by the license when they bought the software from Apple? Professional resellers are even more informed about this subject than users; there's no way they can credibly assert ignorance of the contract, if users can't. The fact that "common practices" contradict a supposedly-binding requirement on the reseller, makes one question whether or not it's really a requirement.

      Unconsenting/uninformed licensing raises too many paradoxes and weird situations that defy common sense and common law. It will eventually be overturned.

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    69. Re:Good for GPL but... by 42forty-two42 · · Score: 1

      Often there is such a blurb, but the dev just uses some off-the-shelf installer and throws the GPL into the 'EULA GOES HERE' box.

    70. Re:Good for GPL but... by vux984 · · Score: 1

      Nope, Glider was only a problem because the copying to RAM wasn't part of the software's normal operation. Copying to RAM when you use the software is allowed, as the other commenters have pointed out.

      Two responses:

      1) "normal operation"? Why should that matter? Why is it up to blizzard "how" I USE it? I thought this whole debate was that there was a fundamental difference between copying for "distribution" and copying for "use". This is clearly USE, and yet I am still exposed to copyright infringment for USE simply because I'm not using it the way blizzard wants?

      2) Further to that, making a backup of software to another hard drive as part of a regular backup routine isn't part of the software's normal operations. Moving a running VM from one physical host to another by cloning the running process isn't part of the software's normal operations. Do I need vender permission to make these copies of my software which isn't strictly required to operate it, but yet which result from the way I choose to use it.

    71. Re:Good for GPL but... by cfulmer · · Score: 1

      You've pointed out a great example of what I was talking about -- nowhere on that page does it say "You can only use this on Macintosh computers" or make any reference to a license agreement.

      That right is asserted inside the license. Taking advantage of that, presumes that the unwitting buyer has already read and accepted the license. What if that's not the case?

      Actually, no. As contemplated by the ProCD court, your right to return the software comes from the UCC, contract law and the rules around offer and acceptance, not from the agreement itself. The License could say "You cannot return this software to the store" and you still would be able to, because doing so negates the entire license.

      In answer to your last question about why Amazon isn't bound, the answer is because Amazon and Apple have a separate agreement. If both Apple and Amazon agree that the EULA doesn't apply to Amazon's resale, then it doesn't apply. Also, the Apple EULA, by its terms, probably only applies only to end users.

      I agree that the whole mess is unsatisfactory. There was a move in the 1990's to standardize the law around this sort of thing through a uniform law that the states were all going to adopt, known as UTICA. I seem to recall that it was only adopted in Virginia and maybe one other state.

    72. Re:Good for GPL but... by Deathanatos · · Score: 1

      The GPL is not a license ... that is a license ... It contains a license

      (emphasis mine) Huh? The GPL is not a license? I wonder, whatever could the L stand for then?

    73. Re:Good for GPL but... by mr_matticus · · Score: 1

      It's called a license because that is the norm, as the license is the element of value that is being conveyed. The document and its terms, however, are a license agreement.

      You can call it strawberry ice cream if you like. That doesn't change what it is. The document contains warranty terms, liability terms, a license grant (there's your license), and, tellingly, terms and conditions. It is a license agreement. It even talks about acceptance and use. A license is granted, not accepted. If you have to accept anything, it's not just a license.

    74. Re:Good for GPL but... by JoelKatz · · Score: 1

      I think you're missing the point. We agree on what this ruling held. I'm saying that this ruling is inconsistent with prior ruling and what the majority of the legal community believed that the law was. I've even explained why.

      You can't point to the ruling to show that the ruling is consistent with prior rulings and prior understanding.

      The prior understanding was that if you gave someone a license to do something normally prohibited under copyright law, you gave up the ability to charge them with copyright infringement and gained the ability to charge them with infringing the license.

      And there's a very specific reason why things have to be that way -- charging someone with copyright infringement has a different set of legal rules than charging someone with violating a contract. The whole logic behind copyright law is that there is no agreement between the parties.

    75. Re:Good for GPL but... by againjj · · Score: 1

      I can't make a license that says, "you can copy this software provided you don't pick your nose" and then sue you for copyright infringement for picking your nose.

      Correct. BUT, if I pick my nose and then COPY THE SOFTWARE, then you CAN sue me, since I only have permission to copy if I don't pick my nose, and without permission, copyright law says I can't copy.

    76. Re:Good for GPL but... by Anonymous Coward · · Score: 0

      The GPL doesn't cover USAGE

      So true, it drive me nuts when some developer has me "agree" to GPL before I can run a binary. It's stupid, pointless and confuses the issue when explaining to people the GPL isn't a EULA and isn't a contract.

    77. Re:Good for GPL but... by JoelKatz · · Score: 1

      Except you did have permission. You violated the terms of that permission, but you had permission.

      Copyright law is for cases where there is no agreement between the parties. Contract law is for cases where there is.

      As I already explained, copyright infringement cases follow different rules from contract violation, and this is precisely because there is no agreement between the parties. (This includes a presumption of irreparable harm and statutory damages.)

      If the gravamen of the argument is that the contract's terms were violated, and the action would not have been a violation of copyright law had the contract's terms not been violated, then you are suing because the contract's terms were violated.

      The exception would be if the action you are suing over exceeded the scope of the license *under* *copyright* *law*. For example, if the license allowed only publication and you created a derivative work.

    78. Re:Good for GPL but... by JoelKatz · · Score: 1

      Let me try an example. Suppose I say you can borrow my car but you can't use it to leave the State. If you do leave the State, can I charge you with the same thing I would charge you with if there was no agreement at all and you took my car without permission?

      There is a huge difference between taking a car without permission and taking a car with permission but exceeding the scope of that permission.

      Same thing here. There is a huge difference between copyright without any permission at all (infringing copyright) and copying with permission but violating the terms of that permission (infringing the license).

    79. Re:Good for GPL but... by xsmasher · · Score: 1

      No, the GPL serves a very different function than an EULA. The EULA takes rights away from you (like warranty protections and, sometime, ability tu publish benchmarks) - the GPL gives you rights you wouldn't otherwise have.

      You need to agree to the EULA in order to install or use a program - not true for the GPL. You need to agree to the GPL in order to *copy and distribute* the GPL program - or, if you don't agree, you're a copyright infringer, because the GPL is the only thing giving you permission to make copies and distribute them.

      It's nice to see the courts agree here (albeit pertaining to a different license) - "a violation of those conditions would put the violating product outside the license and thus make the violator a copyright infringer, potentially liable for an injunction. "

    80. Re:Good for GPL but... by Anonymous Coward · · Score: 0

      It is a license agreement. It even talks about acceptance and use. A license is granted, not accepted. If you have to accept anything, it's not just a license.

      Wrong. It is indeed a license, because it tells you what you MAY do - it does not actually require you to do anything.

    81. Re:Good for GPL but... by mr_matticus · · Score: 1

      Yes, it absolutely does. It requires you to accept the condition that redistribution requires your act of contributing source code.

      It requires you to accept those restrictions in order to exercise the full scope of the license.

    82. Re:Good for GPL but... by squiggleslash · · Score: 1

      That's not a condition though. That's a set of circumstances in which redistribution is valid. A condition would imply that you would normally have a right to redistribute but the GPL is somehow adding something. What the GPL is saying though is that the act of distributing with source code (or distributing with an offer to make source code available, etc) is allowed. The act of distributing without source code was never allowed to begin with. Hence this is a license, not a contract. You're not accepting conditions, you have nothing to agree to (accept the license or not, you still have no right to distribute without source) you're doing the only form of allowed distribution.

      If I made a license that allowed you to redistribute main.c, but offered you no permissions to distribute library.c or functionality.c, it wouldn't be a "license agreement" because it somehow imposed the condition that you cannot distribute the latter .c files. You redistributing main.c does not require that you "agree" to not distribute the other two. You don't have a choice in the matter, you're not allowed to distribute them anyway, license or no license.

      --
      You are not alone. This is not normal. None of this is normal.
    83. Re:Good for GPL but... by torstenvl · · Score: 1

      "It requires you to accept the condition that redistribution requires your act of contributing source code."

      Wrong.

    84. Re:Good for GPL but... by mr_matticus · · Score: 1

      That's not a condition though. That's a set of circumstances in which redistribution is valid.

      No, an affirmative act is not a "circumstance". A set of circumstances establishing scope would be something like "for non-commercial purposes". Anything that requires you to do something in order to achieve a right is not a grant, but an agreement.

      A condition would imply that you would normally have a right to redistribute but the GPL is somehow adding something.

      The GPL is adding something. The right to distribute is being granted in exchange for your contribution of resulting source code. A license grant cannot be predicated on an exchange or an act. That is a license agreement.

      Hence this is a license, not a contract.

      False dichotomy.

      You're not accepting conditions, you have nothing to agree to

      You must agree to the restriction that any right to distribute requires further action on your part. The entire GPL must be accepted by the receiving party at the onset, or it carries no weight at all. If the intent were to require acceptance of terms only for those wishing to distribute, those terms should be in a separate agreement. The GPL contains notices and disclaimers, along with a license grant and restrictions. It is a complete memorialization of a license agreement.

      If I made a license that allowed you to redistribute main.c, but offered you no permissions to distribute library.c or functionality.c, it wouldn't be a "license agreement" because it somehow imposed the condition that you cannot distribute the latter .c files.

      No, but if you including language that did grant distribution rights, but only if you agree to do something, then you have a license agreement.

      You cannot then say that that term is "inactive" until used. If you are putting someone on notice and requiring them to act within those terms, you are introducing a license agreement. You must agree, from the onset, that if you prepare a derivative work and then choose to distribute it, that you will contribute the source code to the community. If you do not accept those terms, you simply cannot use the software.

      Using the software and not distributing your derivative works is accepting the terms, contrary to how the GPL attempts to frame the issue. If you are acting consistent with the rights granted to you, without violating the restrictions, that is assent by performance, pure and simple.

    85. Re:Good for GPL but... by Anonymous Coward · · Score: 0

      Great. So then since the license grants rights to use, modify, and distribute (with conditions I don't have to accept), I can just go ahead and distribute without the source code.

      Thanks for eviscerating the GPL. I'm sure thousands of developers of soon-to-be closed source applications thank you.

  2. Sounds like very good news for the FOSS community. by sherpajohn · · Score: 2, Informative

    In the US at least. Has there been any similar cases in Canada or other countries outside the US?

    --

    Going on means going far
    Going far means returning
  3. Oh Hell Yes by cromar · · Score: 4, Funny

    Sadly, I will sleep better at night knowing that there is some favorable precedent regarding open licenses.

  4. Re:Sounds like very good news for the FOSS communi by msaver · · Score: 1

    It's actually a really easy case to win. I wouldn't worry about it holding up in any nation's court. All you need to ask is two questions...

    1. Do you have a license to use this copyrighted code?
    If no, they lose the case. If yes...
    2. Did you abide by the terms of your license?

    That's it.

  5. Finally, a court for the 21st century! by langelgjm · · Score: 5, Insightful
    It was refreshing to read certain portions of the ruling. I suggest everyone take a look at it. Here's what stuck out at me:

    Traditionally, copyright owners sold their copyrighted material in exchange for money. The lack of money changing hands in open source licensing should not be presumed to mean that there is no economic consideration, however. There are substantial benefits, including economic benefits, to the creation and distribution of copyrighted works under public licenses that range far beyond traditional license royalties.

    This too:

    The copyright holder here expressly stated the terms upon which the right to modify and distribute the material depended and invited direct contact if a downloader wished to negotiate other terms. These restrictions were both clear and necessary to accomplish the objectives of the open source licensing collaboration, including economic benefit... Copyright holders who engage in open source licensing have the right to control the modification and distribution of copyrighted material.

    Good to know the court system can still work!

    --
    "Anyone who [rips a CD] is probably engaging in copyright infringement." - David O. Carson
    1. Re:Finally, a court for the 21st century! by Anonymous Coward · · Score: 0

      groklaw has it all as text.

    2. Re:Finally, a court for the 21st century! by shallot · · Score: 2, Interesting

      I agree, it was surprisingly detailed and coherent when talking about open source.

      And it was also fairly amusing, the very verbose explanation of what the words "provided that" and "condition" mean, it sounded like a really fancy *plonk* to the district court :)

      I was, however, surprised to see this in the footnote on page 7:

      For example, the GNU General Public License, which is used for the Linux operating system, prohibits downstream users from charging for a license to the software. See Wallace v. IBM Corp., 467 F.3d 1104, 1105-06 (7th Cir. 2006).

      I'm not sure what the court's exact definition of 'charging for a license' is there (and I don't have that Wallace v. IBM reference handy), but the GPL isn't actually supposed to prohibit distributors from charging, it just makes charging impractical because they have to provide the whole code as well.

    3. Re:Finally, a court for the 21st century! by gnasher719 · · Score: 2, Insightful

      I'm not sure what the court's exact definition of 'charging for a license' is there (and I don't have that Wallace v. IBM reference handy), but the GPL isn't actually supposed to prohibit distributors from charging, it just makes charging impractical because they have to provide the whole code as well.

      Let's say I have the source code and executable code for the gcc compilers on my hard drive at home. I can sell you the executable code for a million dollars if you are stupid enough to pay that amount; that is perfectly legal under the GPL. You can then ask me for the source code; I can charge you my cost for providing the source code (lets be generous, 20 dollars for burning a CD and mailing it to you). You decide that you want to give copies to your friends, so you need a license to do this. I have to give you the license to make copies under the terms of the GPL, and I am not allowed to charge a penny for it.

    4. Re:Finally, a court for the 21st century! by shallot · · Score: 1

      OK, so the footnote is just too generally phrased for my mental parser. A simple reference to GPL v2.0 section 2b would have sufficed. But I guess they like to reference other court documents only.

  6. Re:Sounds like very good news for the FOSS communi by chromatic · · Score: 3, Informative

    Do you have a license to use this copyrighted code?

    I believe you mean "distribute", not "use".

  7. Smack down by tjstork · · Score: 4, Informative

    Katzer and company really need to be smacked down.

    On their web site, they try to create the impression that they had their own solution and didn't copy any code from the open source guys, but, then, in court, they fully admit that they in fact, did that.

    So, they stole a bunch of code, made some money on it, then, they admitted it in court, but continue to lie to the public about what they did.

    I mean, how sickening is that?

    --
    This is my sig.
    1. Re:Smack down by mrchaotica · · Score: 5, Informative

      It's not even just that: Katzer also went and got patents over the concepts expressed in JMRI, which were only granted because he failed to disclose JMRI's prior art to the patent office, and then sued the JMRI people for infringement of their own code!

      The open source guys didn't even start this; Katzer did. He brought it upon himself!

      JMRI has a long and detailed page describing what happened. I highly recommend everyone reading it; it's amazing how brazenly this prick Katzer (and his lawyer) tried to rip everybody off.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    2. Re:Smack down by jasper · · Score: 3, Insightful

      How bad is our legal system when Kratzer can lie cheat and steal, then require others to spend large amounts of time and money to defend their creation?

      Thankfully justice is achieved in the end... but it's not even over, theres still motions in the court system. Put this guy in jail already.

    3. Re:Smack down by the_humeister · · Score: 0, Flamebait

      Man, this Katzer person seems to be the biggest A-hole ever. The only thing worse would be if he'd murdered his wife...

    4. Re:Smack down by smellsofbikes · · Score: 4, Informative

      What justice?
      Bob Jacobsen has paid Katzer $30,000 in judgments against Jacobsen, as well as his own legal fees. Katzer's made money off his product and gotten his legal costs paid for, and as I read the judgments, has yet to actually lose anything other than three of his 12 patents.
      Katzer isn't winning, but JMRI is suffering a lot more than Katzer is.

      I'm glad the court ruled the way it did but a lot of JMRI people have gotten pretty badly ground up along the way. This is only justice insofar as the rest of FOSS has dodged a bullet.

      --
      Nostalgia's not what it used to be.
    5. Re:Smack down by swillden · · Score: 1

      It's almost like Katzer set out with the intention of establishing precedents that would protect open source software licenses.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    6. Re:Smack down by Anonymous Coward · · Score: 1

      Why don't you tell him what you think: webmaster@kamind.com

    7. Re:Smack down by mrchaotica · · Score: 1

      Not really; if that were the case then he would have skipped straight to the litigation instead of harassing Bob Jacobsen (the primary JMRI guy) through his employer by filing a FOIA request claiming that he worked on JMRI at work (Lawrence Berkeley National Laboratory). Instead, Katzer is a genuine greedy asshole.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  8. Re:Sounds like very good news for the FOSS communi by Svartalf · · Score: 4, Informative

    Yeah, the GPL was upheld in Germany as valid.

    The truth be known, if the FOSS licenses were held to be unenforceable, then most of the publication, etc. licenses that the record labels, book publishers, etc. live by would also be so- and NOBODY in that space wants that.

    These licenses are NOT EULAs. They're all largely publication and derivative works licenses- with the royalties being whatever the terms of the license requires for being able to publish the stuff to downstream recipients.

    No license?

    No publication. No derivative works.

    You publish or make a derivative work without the license to do so, you're guilty of willful infringement of the rights holders. That carries a much, much nastier penalty than accidental ones and it's something Verizon and Actiontec did NOT want to face the music on in court- so they settled out of it once it got filed.

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
  9. Re:Sounds like very good news for the FOSS communi by mrchaotica · · Score: 2, Informative

    It's actually a really easy case to win.

    You think that, but you should note that this is an appellate decision: JMRI actually lost the first time!

    Granted, if you read the original court's decision it's obvious that the judge didn't understand the issue at all -- which is not necessarily the judge's fault, as JMRI's case wasn't argued very competently in my opinion -- but it still happened.

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  10. Which version? by FilterMapReduce · · Score: 5, Interesting
    It is interesting that the Artistic License has passed a legal test of sorts, considering that it has been criticized as one of the more shoddily-written licenses out there—at least, version 1.0. I mean, look at this (from the "Definitions" section of 1.0):

    "You" is you, if you're thinking about copying or distributing this Package.

    That reads like someone tried to satirize the "legalese" present in most licenses rather than create a working license for themselves. Also, the license is automatically binding for anyone who is thinking about using the license? Compare to a Creative Commons license, where

    "You" means an individual or entity exercising rights under this License...

    You'd think programmers would know better than to let ambiguities like that by. (And incidentally, some people have similar concerns about the language in the GPL: it has a conspicuous lack of "legalese", which might make it easy to read, but also risks ambiguity popping up in a court case down the road.)

    1. Re:Which version? by mrchaotica · · Score: 2, Insightful

      That reads like someone tried to satirize the "legalese" present in most licenses rather than create a working license for themselves.

      What did you expect? The name of the thing is a pun!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    2. Re:Which version? by TheRaven64 · · Score: 1

      And incidentally, some people have similar concerns about the language in the GPL: it has a conspicuous lack of "legalese", which might make it easy to read, but also risks ambiguity popping up in a court case down the road

      Have you read the same GPL as me? The GNU one? The one that is several pages of convoluted legalese (not quite as bad as the MPL, but close), written by a lawyer (who then went on to write the CC licenses you seem to think so highly of)?

      --
      I am TheRaven on Soylent News
    3. Re:Which version? by FilterMapReduce · · Score: 1

      The one that is several pages of convoluted legalese...

      Convoluted language != convoluted legalese.

      ...written by a lawyer (who then went on to write the CC licenses you seem to think so highly of)?

      Which lawyer is this? The GPL and the CC licenses are both written collaboratively. The authorship of the GPL is overseen by Richard Stallman (and if Wikipedia is correct, he was the sole author of version 1), who is not a lawyer and wants nothing to do with Creative Commons.

    4. Re:Which version? by DNS-and-BIND · · Score: 1

      Yeah, it's really irritating how geeks will take something serious and try to crack jokes about it. Come on, it's a binding legal contract, can we leave the funny-making aside for just five minutes? Oh hell no, because that would be impinging on our glorious freedoms...

      --
      Shutting down free speech with violence isn't fighting fascism. It IS fascism!
    5. Re:Which version? by TheRaven64 · · Score: 2, Interesting

      Lawrence Lessig wrote versions 2 and 3 of the GPL, under advisement from RMS. Version 1, which had no input from Lessig, was a legal mess, and I don't know of any projects that have used it in the last decade.

      --
      I am TheRaven on Soylent News
  11. Now we're on Track by dmomo · · Score: 4, Funny

    This is rail nice. I do believe open licenses are at a critical junction. Kamind certainly bit off more than they can choo.

    1. Re:Now we're on Track by dmomo · · Score: 3, Funny

      I should have posted this anonymously. I'm a freight of getting modded down.

    2. Re:Now we're on Track by mrchaotica · · Score: 1

      Wow, that was a trainwreck of a post!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    3. Re:Now we're on Track by Anonymous Coward · · Score: 0

      Thomas the tank engine http://en.wikipedia.org/wiki/Thomas_the_Tank_Engine was unavailable for comment.

  12. Re:_OSS by TaoPhoenix · · Score: 2, Insightful

    "Free" might aquire yet another meaning, something like "Free as in a Dollar".

    It might have to do with the "Consideration Exchanged" part of contract law. I'd forego a dollar's worth of benefit for software to slide by that rule on the software side. "A Dollar's benefit" could be interpreted like "A Dollar's worth of NYCL's time"... which would be a reply to a comment here.

    --
    My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
  13. Game console EULA by tepples · · Score: 1

    when's the last time you had to agree to an EULA to [...] even played a (console-based) video game you bought?

    I had to click through a license screen to get some features of my Wii console to work. I don't remember the exact words, but it appeared to prohibit me from modifying the console to accept software developed by entities too small to be eligible for a license from Nintendo.

    1. Re:Game console EULA by mrchaotica · · Score: 1

      The mere fact that that text was there doesn't mean it had any actual legal force. What gives Nintendo the right to dictate what you can do with your own property? Nothing!

      It's as absurd as Ford trying to tell you that you can't add a supercharger to your Mustang. Ford can't do that (the most it can do is deny your warranty claim, and even then it has to prove that your modification caused the problem), and Nintendo can't either!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  14. Well, duh. by afabbro · · Score: 0, Offtopic

    The U.S. Court of Appeals for the Federal Circuit (an authoritative court

    Well thanks, dilute - I always thought the U.S. Court of Appeals for the Circuit Court was just a joke that everyone laughed off. Now I see it's an authoritative court.

    --
    Advice: on VPS providers
  15. Wrong! (Re:Good for GPL but...) by bwcbwc · · Score: 1

    The GPL is a EULA. It's also a DLA (distributor's license agreement). It grants you the right to make unlimited copies of the software either for your own use (EULA) or for distribution under the terms of the license. That's what the L stands for. Without the GPL, you would not be allowed to copy/install/compile the work on a single computer, let alone many, without violating the copyright.

    The distinguishing feature of the GPL that makes it seem like it isn't a EULA is that it grants much, much broader permissions for redistribution and modification to the licensees than any commercial EULA. But these are still licensed permissions with binding conditions on the licensee, and not public domain relinquishment of the rights attached to copyright.

    --
    We are the 198 proof..
    1. Re:Wrong! (Re:Good for GPL but...) by mrchaotica · · Score: 2, Informative

      Without the GPL, you would not be allowed to copy/install/compile the work on a single computer, let alone many, without violating the copyright.

      Whoa there, champ. Read Section 9:

      9. Acceptance Not Required for Having Copies.

      You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.

      So either the lawyers who wrote the GPL were wrong, or you are. (Guess who I'm siding with.) Also, see my other post about the "copy/install/compile is copyright infringement" argument.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  16. Re:Sounds like very good news for the FOSS communi by ksd1337 · · Score: 1

    The truth be known, if the FOSS licenses were held to be unenforceable, then most of the publication, etc. licenses that the record labels, book publishers, etc. live by would also be so- and NOBODY in that space wants that.

    If they were unenforceable, the whole concept of copyright would suddenly appear to be a pile of nonsense to all the "intellectual property" zealots like the RIAA, MPAA, etc.

  17. Proof: Patents are ruining innovation in America by MacDork · · Score: 1

    It's not even just that: Katzer also went and got patents over the concepts expressed in JMRI, which were only granted because he failed to disclose JMRI's prior art to the patent office, and then sued the JMRI people for infringement of their own code!

    It would be nice if the OSS community chould foot the bill for a few high profile ads publicizing this case, and specifically Katzer's actions. It would go a long way toward creating awareness about the software patent process and how badly it is failing.

  18. Anyone know how precedent works for this? by harlows_monkeys · · Score: 1

    Note that this is a copyright decision, by the CAFC, which normally does not handle copyright cases. They had subject jurisdiction here because it was also a patent case, and that is something they have jurisdiction over.

    So how does this fit in as precedent? In future copyright cases, that do NOT have that patent component that gives CAFC jurisdiction for the appeal, does the district court follow the precedent of the appeals court for the circuit it is in, or this CAFC decision?

    1. Re:Anyone know how precedent works for this? by Todd+Knarr · · Score: 2, Informative

      This holding wouldn't be controlling outside the Federal Circuit, but it'd be considered very persuasive. Basically having two Appeals Courts make contradictory rulings is one of the fastest ways to get the Supreme Court to take the appeal and resolve the conflict, and the only constant there is that if that happens at least one of the Appeals Courts will be told they were wrong. So Appeals Courts try not to make contradictory rulings. And District Court judges try not to make rulings that their controlling Appeals Court will have to overturn. Seeing as how the Federal Circuit appeals court isn't the 9th Circuit one, I'd expect most district courts to take their cue from this ruling. Especially given how clear the CAFC ruling is. Few judges would like to explain in a ruling why they're disregarding the plain language used in a license despite an Appeals Court ruling saying that that language means exactly what it says.

  19. A rip-off artist gets his just reward by davide+marney · · Score: 1

    Reading the tortured history of this case was a real eye-opener. I hadn't really thought about the lengths that some people will apparently go to steal from the community, lie to regulators, and engage in what must have been a very expensive legal fight.

    All that for model railroad software?

    I am so thankful we have the legal support to fight and win these kinds of battles. Thanks to all involved for sticking up for all our rights.

    --
    "We receive as friendly that which agrees with, we resist with dislike that which opposes us" - Faraday
    1. Re:A rip-off artist gets his just reward by _Sprocket_ · · Score: 2, Interesting

      Reading the tortured history of this case was a real eye-opener. I hadn't really thought about the lengths that some people will apparently go to steal from the community, lie to regulators, and engage in what must have been a very expensive legal fight.

      You've got to wonder what the motivation is. Is there really that much money in model train software? Or is this someone who has money to throw at whatever they want?

      Dig around a bit... and you find some interesting things.

      It seems Katzer and his parnter have made a sizable donation to the University of Oregon in the tune of "$1.25 million for computer labs, software and a technology endowment fund." That's a nice chunk of change to throw around. Where does it come from?

      It's interesting to note that Katzer shows up in a number of roles from software development to a model train store. I suspect ongoing concerns are something along the lines of his LinkedIn profile:

      Matt Katzerâ(TM)s Summary

      KAMIND Associates delivers Microsoft solutions for small business customers since 1998. We solve your IT problems with the following solutions â" eCommerce sites for samll business using Microsoft Commerce Servers, Microsoft Small Business Server and Microsoft Retail Management System (POS) Solutions for specialty retailers. As part of our service model, we work with customers to develop an integrated IT services plan that solves the customers need and results in long term bottom line savings.

      That seems pretty straight forward. But there's some other oddities out there. Take this blog entry of a Microsoft manager for example:

      Matt Katzer runs an ISV called KAM Industries. They build software for the REALLY big railroads - railroad yard automation, engine automation, that kind of thing. Software that makes really big, heavy stuff move when and where itâ(TM)s supposed to. Matt told me that they also do similar stuff for model railroads â" HO, N, and O-scale stuff. They can completely automate, and simulate very complex setups.

      If that werenâ(TM)t cool enough, Matt has built all this on top of Microsoft technologies - .NET Framework, the Compact Framework, WMI (okay, not REALLY MS tech, but it counts), XML, Windows Server 2003, etc.

      Eh, what? Is this more than model trains or was Katzer simply exaggerating to impress?

      Side note is a comment on the blog:

      Matt Katzer was my first manager at Intel and the reason that I moved out to Oregon to work for Intel.

  20. What about the $30,000? by loshwomp · · Score: 4, Insightful

    I want to know if Bob Jacobsen got his $30,000 (legal fees paid to the scum suckers) back.

    1. Re:What about the $30,000? by rahvin112 · · Score: 3, Informative

      Don't worry, with this ruling he will. He's now eligible for disgorgement of profits, statutory damages, punitive awards, legal fees and expenses. I imagine the legal expenses alone is going to be rather massive but tack in a few statutory damages at $150K per violation (for every single file they stripped the copyright notice from which exceeds 300 files by my reading of the JMRI site and possibly each of these violations applies for each distribution of Katzer's product so if he sold 10 copies he's on the hook for 3000 violations of copyright). Jacobsen's not going to end up with millions but my guess is Jacobsen is going to get back every dime he spent probably three times over and he won't be paying any legal bills. My hope is they can destroy Katzer financially, his behavior is reprehensible and he should be punished for it.

      Keep following the Saga though, this Katzer guy is as slimy as SCO. He'll probably try to fend off any judgement with Bankruptcy just like SCO.

    2. Re:What about the $30,000? by 42forty-two42 · · Score: 1

      IANAL, but don't you only get statutory damages if you register your copyright?

  21. Rail? by Anonymous Coward · · Score: 0

    Well, at least you didn't mention Ruby.

  22. Good job, Federal Court of Appeals! Some comments: by KWTm · · Score: 2, Interesting

    It was refreshing to read certain portions of the ruling. ... Good to know the court system can still work!

    Agreed! I did read through the entire judgement --I figured I'd take my turn as the 0.1% of Slashdot to read the article so that the rest of Slashdot didn't-- and here are some comments.

    This judge. Jeffrey S. White, was surprisingly familiar with free and open source licenses, mentioning the GNU GPL and the MIT OpenCourseware licenses. I wonder if he already had some familiarity, or whether it was the amici curiae from the Creative Commons Corporation and from the Wikimedia Foundation? Anyway, good job on all of them!

    This judgement reminded me of why it was important to get advice from lawyers. Something that seemed plain-as-day to me turned out to be a focal point of debate. I've always assumed that, with a license like the GPL or other open source licenses, if you don't abide by the GPL, then the GPL doesn't apply --it's as if the GPL didn't exist-- and now you've violated copyright law. In this case (which is not GPL but the Artistic License, it wasn't so obvious: the defendants argued that the license itself freed the defendants from copyright law, and if the defendants then violated the license, then it was just a license violation (contract law) rather than copyright violation. This was how the defendants successfully argued at the Northern California District Court. Fortunately, the Appeals court overrode this, taking into account the spirit of the Artistic License and keeping in mind the other open source licenses. But it was a point I never thought would be questioned.

    As the judgement points, the difference between license violation and copyright violation is especially important because, with license (contract) violation, you only get economic damages in return. If you write F/LOSS, then usually you can't really say that you've lost a million bucks because they stole your software. But this judge recognized the non-economic benefit of licensing under F/LOSS, and specifically said,

    The choice to exact consideration in the form of compliance with the open source requirements of disclosure and explanation of changes, rather than as a dollar-denominated fee, is entitled to no less legal recognition. Indeed, because a calculation of damages is inherently speculative, these types of license restrictions might well be rendered meaningless absent the ability to enforce through
    injunctive relief.

    In other words, "money isn't everything".

    If the law decided that the problem was license violation, then Microsoft could violate F/LOSS, and then toss it a few coins and say, "Sorry --here's some spare change for your troubles." With the law deciding that it's a matter of copyright and not contract violation, the judge can tell Microsoft, "I don't give a rat's ass how much money you have --stop what you're doing or you will be caned."

    I'm sure the GNU GPL, having been thoroughly vetted by Eben Moglen, has clearer language than the Artistic License, which prevents such loopholes, but it's still good to see a judge that understands the issues. Judge White has remanded the case --I think this means that he's sent the case back to the District Court saying, "Go try this case again --you didn't do your homework properly the first time."

    (Incidentally, was this the same judge that Slashdot covered a year or so ago where he lambasted the lawyers on both sides for not doing their homework? Name sounds familiar somehow, but I can't place it.)

    --
    404555974007725459910684486621289147856453481154 in hex is "You sank my Battleship?"
    [GPG key in journal]
  23. Here's the full text (after some tidying) by Anonymous Coward · · Score: 0

    Haha, if I post this, then my karma will be modded up all the way!
    Hey, wait, who are all these other people who have posted under the same nickname as me?

    United States Court of Appeals for the Federal Circuit 2008-1001
    ROBERT JACOBSEN, Plaintiff-Appellant,
    v.
    MATTHEW KATZER and KAMIND ASSOCIATES, INC. (doing business as KAM Industries), Defendants-Appellees.
    Victoria K. Hall, Law Office of Victoria K. Hall, of Bethesda, Maryland, argued for
    plaintiff-appellant.
    R. Scott Jerger, Field Jerger LLP, of Portland, Oregon, argued for defendants-
    appellees.
    Anthony T. Falzone, Stanford Law School, Center for Internet and Society, of
    Stanford, California, for amici curiae Creative Commons Corporation, et al. With him on
    the brief was Christopher K. Ridder.
    Appealed from: United States District Court for the Northern District of California
    Judge Jeffrey S. White
    United States Court of Appeals for the Federal Circuit

    Appeal from the United States District Court for the Northern District of California in
    case no. 06-CV-1905, Judge Jeffrey S. White.
    __________________________DECIDED: August 13, 2008__________________________
    Before MICHEL, Chief Judge, PROST, Circuit Judge, and HOCHBERG, * District Judge.
    HOCHBERG, District Judge.
    The Honorable Faith S. Hochberg, District Judge, United States District Court
    for the District of New Jersey, sitting by designation.
    We consider here the ability of a copyright holder to dedicate certain work to free
    public use and yet enforce an Aopen source@ copyright license to control the future
    distribution and modification of that work. Appellant Robert Jacobsen (AJacobsen@) appeals
    from an order denying a motion for preliminary injunction. Jacobsen v. Katzer, No. 06-CV-
    01905 JSW, 2007 WL 2358628 (N.D. Cal. Aug. 17, 2007). Jacobsen holds a copyright to
    computer programming code. He makes that code available for public download from a
    website without a financial fee pursuant to the Artistic License, an Aopen source@ or public
    license. Appellees Matthew Katzer and Kamind Associates, Inc. (collectively
    AKatzer/Kamind@) develop commercial software products for the model train industry and
    hobbyists. Jacobsen accused Katzer/Kamind of copying certain materials from Jacobsen=s
    website and incorporating them into one of Katzer/Kamind=s software packages without
    following the terms of the Artistic License. Jacobsen brought an action for copyright
    infringement and moved for a preliminary injunction.
    The District Court held that the open source Artistic License created an Aintentionally
    broad@ nonexclusive license which was unlimited in scope and thus did not create liability
    for copyright infringement. The District Court reasoned:
    The plaintiff claimed that by modifying the software the defendant had
    exceeded the scope of the license and therefore infringed the copyright.
    Here, however, the JMRI Project license provides that a user may copy the
    files verbatim or may otherwise modify the material in any way, including as
    part of a larger, possibly commercial software distribution. The license
    explicitly gives the users of the material, any member of the public, Athe right

  24. A quick shout out to RMS by Broofa · · Score: 2, Insightful

    While discussing (and rejoicing) in this decision, I'd suggest we all say thank you to Richard Stallman for his work on "copyleft" licensing. It is possibly the single greatest innovation in modern software development and, without it, our world would be a darker, more depressing place.

    RMS, you rock dude!

  25. Winning free software business model by Anonymous Coward · · Score: 0

    Finally we have figured out how to make money with free software:

        1. Develop an attractive free software product.

        2. Wait for greedy capitalists to exploit the product.

        3. Shake the greedy capitalists in copyright litigation.

  26. Neither are the copies in HDD or RAM while playing by Anonymous Coward · · Score: 0

    Since they are not fixed in the medium. They are malleable and last only as long as your have the game installed or are playing it.

    Playing the game is MOST DEFINITELY an ephemeral copy.

  27. No that's wrong by Anonymous Coward · · Score: 0

    So wrong in fact that it is hard to point out where it is wrong.

    Rather like trying to point to the atmosphere while standing in it.

    If the license to use the copyrights says you must do X, Y and Z then if you don't do X, Y or Z then you cannot use the copyrights. So you cannot produce a copy to distribute and you cannot create a derivative work.

    If the EULA says to use the program (which doesn't require using the copyrights) you must to A, B and C, then not doing A, B or C means you can't use the copyrights. But you aren't using the copyrights, so copyright is not broken. Now you've broken the agreement but that is a contractual thing.

  28. Re:Neither are the copies in HDD or RAM while play by cfulmer · · Score: 1

    If you can touch ram (and, I can -- I installed some in my computer a few weeks ago) or a hard drive, then it's sufficiently tangible. The fixation requirement just means that it has to be accessible for more than transitory duration.

  29. Cornell Law School has cites to contradict you by Anonymous Coward · · Score: 1, Informative

    http://topics.law.cornell.edu/wex/Contracts/

    Not contradicting you on the "forced" discussion, but (at least in the U.S.) contracts most definitely require consideration and the core definition of a consideration is that it is a "benefit" to the grantee.

    1. Re:Cornell Law School has cites to contradict you by xsmasher · · Score: 1

      That's the best part of the GPL - if the court did decide that the GPL constitutes a "contract without consideration," and therefore was null and void... then the person making the copies is a copyright infringer. They've just argued away the only protection they had from a copyright lawsuit; they need to go back and negotiate with the copyright holder, because they have no permission to make copies.

      The GPL is Judo for copyright law, using the aggressor's own weight against him.

    2. Re:Cornell Law School has cites to contradict you by mr_matticus · · Score: 1

      but (at least in the U.S.) contracts most definitely require consideration and the core definition of a consideration is that it is a "benefit" to the grantee.

      No. You are relying on a boiled-down simplification of the law.

      Consideration and benefit are two distinct concepts. Consideration is not benefit. The benefit of the bargain (the receipt of something valuable) is not consideration. Consideration may be payment, a return promise, forbearance from an act. Benefit is what the party receives from the contract.

      Further consideration is not universally required. It is generally required, and there are a number of varying forms of contracts that do not require consideration, but rather any number of judicially-accepted substitutes for consideration, or particular contractual scenarios where consideration is not an element of the agreement.

    3. Re:Cornell Law School has cites to contradict you by torstenvl · · Score: 1

      I've never heard "benefit" used as a term of art. As a vernacular term, it suffices as a pretty accurate definition of "consideration." You do need to receive something of value in return to satisfy consideration, and any distinction between "something of value" and "benefit" is pedantic at best.

      In terms of consideration not being universally required... that's not exactly true. In law, consideration is always required. It's just that in equity, that requirement can be waived in certain circumstances (e.g., when enforcing a consideration-less promise is the "only" way to prevent "injustice," a doctrine known as "promissory estoppel"). Promissory estoppel is an equitable doctrine, not a legal one per se.

    4. Re:Cornell Law School has cites to contradict you by mr_matticus · · Score: 1

      I've never heard "benefit" used as a term of art.

      Then you've not looked very hard.

      You do need to receive something of value in return to satisfy consideration

      The benefit of the bargain is what you hope to achieve as a result. Consideration is what you use to support your promise. They're on opposite sides of the agreement. The benefit of the Offeror may be the consideration from the Offeree, but in the case of software licenses this is rarely complete, and in the case of free software licenses is totally inadequate, as there is no consideration but a return promise.

      The benefit of the bargain is not always, and in fact relatively rarely is the same as the consideration supporting the promise, even within a bilateral AwC. It is therefore an overly simplistic and inaccurate statement, and it is worthless in the vernacular as well, by which I expect you mean 'colloquial'--as there is no such thing as vernacular contract discussion using bastardized terms of art.

      In law, consideration is always required.

      No, it's not--there is rarely any such thing as "always" or "never" in law, contracts doubly so. It is "required" in AwC, which is but one form of contract. There are also judicially-recognized substitutes for consideration, even in AwC. Promissory estoppel is just one such example. Further, all consideration-based arguments and disputes fundamentally hinge on matters of equity, as courts of law are not empowered to rule on the adequacy of consideration, so the mention of a law/equity distinction (particularly no such bright line exists in most jurisdictions today) is nothing more than a poor red herring.

    5. Re:Cornell Law School has cites to contradict you by torstenvl · · Score: 1

      Your post is nonsense, not to mention self-contradictory.

      You can't honestly expect us to overlook the fact that you assert both that all exceptions to consideration are based in equity ("all consideration based arguments... hinge on matters of equity") and that some exceptions to consideration are NOT based in equity ("in law, consideration is always required. no, it's not.")

      You can't have it both ways dude.

    6. Re:Cornell Law School has cites to contradict you by mr_matticus · · Score: 1

      Your post is nonsense, not to mention self-contradictory.

      Only to the uninformed.

      you assert both that all exceptions to consideration are based in equity

      No such assertion. Please read more carefully.

      You can't have it both ways dude.

      There aren't two ways about it, so there's no problem. Thanks for playing.

  30. you overlooked a key difference by Anonymous Coward · · Score: 0

    In your book publishing example, a contract existed whereas in the case at hand no contract could have existed (because there was no acceptance of one by the infringing company).

    In the book publisher example, acceptance would have been explicit. The case at hand would have been more interesting if the defendant had previously complied with the APL terms and only subsequently broken them since then they might have argued a contract was previously established through implicit acceptance. *THEN* your book publisher analogy would have been apt.

    To match this case's actual circumstances, an accurate book publisher analogy would have had the book publisher purchase one copy at retail and then proceed to produce and sell copies of that one. That's why CD and DVD 'pirates' are prosecuted under copyright law rather than contract law.

    1. Re:you overlooked a key difference by JoelKatz · · Score: 1

      It's a tricky question whether there was an acceptance of the license or not. Neither the GPL nor the Artistic License require explicit acceptance. So you can't argue there was no acceptance because acceptance was not explicit.

      Certainly some copies were made of the code before other things were done with it. If these copies were made without violating the license, that could indicate acceptance of the license.

      Pirates are prosecuted under copyright law because they do not have any license to copy or distribute the works. Copyright law prohibits copying or distributing without a license.

      Suppose I leave a bicycle unlocked at the front of my house. A sign says "you may borrow my bicycle but have it back within an hour". My neighbor's bicycle is also unlocked but has no such sign. A person who takes my bicycle with the intent of having it back in two hours is doing something very different from a person who takes my neighbor's bicycle with the intent of having it back in two hours.

      Copyright infringement and license violation are two very different beasts. The former exists only when there is no agreement that license an operation prohibited under copyright law. The latter exists when the terms of the permission are violated.

      This case is about the latter, but the court treated it as the former. This is as absurd as treating someone who fails to return a car in the time period agreed the same as someone who borrows a car from a rental lot with no permission at all.