Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Sunday September 10 2017, @06:28PM   Printer-friendly
from the GNU-ruling dept.

Arthur T Knackerbracket has found the following story:

A recent federal district court decision denied a motion to dismiss a complaint brought by Artifex Software Inc. ("Artifex") for breach of contract and copyright infringement claims against Defendant Hancom, Inc. based on breach of an open source software license. The software, referred to as Ghostscript, was dual-licensed under the GPL license and a commercial license. According to the Plaintiff, those seeking to commercially distribute Ghostscript could obtain a commercial license to use, modify, copy, and/or distribute Ghostscript for a fee. Otherwise, the software was available without a fee under the GNU GPL, which required users to comply with certain open-source licensing requirements. The requirements included an obligation to "convey the machine-readable Corresponding Source under the terms of this License" of any covered code. In other words, under the open source license option, certain combinations of proprietary software with Ghostscript are governed by the terms of the GNU GPL.

Plaintiff alleged that because Defendant did not have a commercial license for Ghostscript, its use and distribution of Ghostscript constituted consent to the terms of the GNU GPL, Section 9 of which states:

You are not required to accept this License in order to receive or run a copy of the Program...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.

Plaintiff further alleged that Hancom failed to comply with key provisions of the GNU GPL, including the requirement to distribute the source code for Hancom's software.

Hancom responded to these allegations with three arguments. First, it alleged Plaintiff failed to state a claim for breach of contract and that any such claim is preempted by copyright law. Second, it alleged Plaintiff's copyright claim must be dismissed in part because Plaintiff has failed to allege that Defendant committed a predicate act in the United States. Finally, Defendant moved to strike portions of the relief sought in the complaint.

The Court rejected all three arguments. On the first issue, the court stated: "Defendant contends that Plaintiff's reliance on the unsigned GNU GPL fails to plausibly demonstrate mutual assent, that is, the existence of a contract. Not so. The GNU GPL, which is attached to the complaint, provides that the Ghostscript user agrees to its terms if the user does not obtain a commercial license." The Court added: "Plaintiff's allegations of harm are also adequately pled. Plaintiff plausibly alleges that Defendant's use of Ghostscript without obtaining a commercial license or complying with GNU GPL deprived Plaintiff of the licensing fee, or alternatively, the ability to advance and develop Ghostscript through open-source sharing. Indeed, as the Federal Circuit has recognized, there is harm which flows from a party's failure to comply with open source licensing: "[t]he lack of money changing hands in open source licensing should not be presumed to mean that there is no economic consideration" because "[t]here 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 case highlights the need to understand and comply with the terms of open source licenses. Many companies use open source without having adequate open source usage policies or understanding of the legal risks of using open source. As this case highlights one of the key risks with using open source is that in certain circumstances, a company may be required to release the source code for its proprietary software based on usage of open source code in the software. It also highlights the validity of certain dual-licensing open source models and the need to understand when which of the options apply to your usage. If your company does not have an open source policy or has questions on these issues, it should seek advice.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1, Insightful) by Anonymous Coward on Monday September 11 2017, @07:46AM (4 children)

    by Anonymous Coward on Monday September 11 2017, @07:46AM (#566156)

    The GPL is not a contract, it's a license. You don't have to agree to it. It only allows you to do a couple of things that copyright law would otherwise deny you. It gives you these permissions as long under a few conditions - that you give anyone who receives your software the same permissions. If you don't do that, you simply don't get any extra permissions on top of copyright law.

    Without reading Hancoms arguments, as far as not having agreed to the GPL, I'd say they are correct. However, the result is that the case simply falls back to copyright law - Hancom is not allowed to distribute their software, and must therefore do a full recall, refunding every customer the full purchase price.

    And this is why the FSF has been so successful in convincing violators to follow the GPL. It's not that the GPL gives some contractual obligation to release source, the alternative is just that much more expensive.

    Starting Score:    0  points
    Moderation   +1  
       Insightful=1, Total=1
    Extra 'Insightful' Modifier   0  

    Total Score:   1  
  • (Score: 2) by TheRaven on Monday September 11 2017, @10:54AM (1 child)

    by TheRaven (270) on Monday September 11 2017, @10:54AM (#566184) Journal
    It's amusing that a lot of the FSF's income comes from selling proprietary software. The reason that they require copyright assignment is not so that they can take infringers to court, it's so that no one else can. The latter means that they can settle with a company caught infringing the GPL by giving them a retroactive proprietary license for the software in exchange for money and a commitment to respect the terms of the GPL in future. If they didn't have copyright assignment then this license would be worth a lot less because any other contributor to the project could also sue the infringer.
    --
    sudo mod me up
    • (Score: 2) by maxwell demon on Monday September 11 2017, @08:58PM

      by maxwell demon (1608) on Monday September 11 2017, @08:58PM (#566385) Journal

      Do you have any source for that claim?

      --
      The Tao of math: The numbers you can count are not the real numbers.
  • (Score: 0) by Anonymous Coward on Monday September 11 2017, @06:55PM (1 child)

    by Anonymous Coward on Monday September 11 2017, @06:55PM (#566324)

    Yeah, which is also why the AGPL is bullshit -- or, more precisely, is only as legally valid/enforceable as a EULA -- it tries to impose conditions more restrictive than copyright's default of "all rights reserved". The validity of that, then, depends on the ability to compel users to agree to a license after you've aleady handed them the software. If users are allowed to decline (as they are with GPL), the AGPL becomes toothless, because the whole point of AGPL is to address cases the GPL can't touch because there is no distribution happening.

    • (Score: 2) by TheRaven on Tuesday September 12 2017, @07:22AM

      by TheRaven (270) on Tuesday September 12 2017, @07:22AM (#566581) Journal
      As I understand it, the AGPL simply requires (beyond the GPL) that, if there is a download source button that you do not remove it. It is not restricting how you can use the software, it is restricting how you can modify the software, which is entirely within the bounds of copyright law. If you do not accept the AGPL then you can still use the software, but you cannot distribute it and you cannot create derived works.
      --
      sudo mod me up