unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Arne Babenhauserheide <arne_bab@web.de>
To: Greg Troxel <gdt@lexort.com>
Cc: guile-user@gnu.org
Subject: Re: Dumb Licensing Questions
Date: Sat, 24 Dec 2016 16:08:03 +0100	[thread overview]
Message-ID: <87lgv5bc18.fsf@web.de> (raw)
In-Reply-To: <smueg0xfpv6.fsf@linuxpal.mit.edu>

[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]


Greg Troxel writes:

> <tomas@tuxteam.de> writes:
>
>> It's clear that there are different standpoints. The linking thing (dynamic
>> or static) hasn't, AFAIK, tested in court. It's quite possible that different
>> courts reach different conclusions (in the same or different places in the
>> world). It's even possible (gasp!) that the legal interpretations of things
>> change over time.
>  
> Completely agreed.   And, to expand, copyright law doesn't talk about
> linking, it talks about things like "derived works", which leads to "if you
> do X, is it a derived work".
>
>> If I were you, I'd just comply with what the FSF proposes, and that is pretty
>> clear [1]. Any reasons not to comply with that?
>
> A very good point.  Stepping back, there is a question of what's legal
> and where the line is.  But there's another question of what individuals
> and the Free Software community think of as good behavior.  If someone
> writes software and makes it available under a Free License, politenss
> at least demands that those who copy/modify/distribute/use the software
> respect their wishes about what the license means.

Finally there’s the question what’s safe practice. There are three
cases:

1. safe ground: you don’t need to worry about legal issues.
2. murky waters: someone might sue you and you might win or lose.
3. clear breach: if you get sued, you lose.

Case 1 is "just assume you create a derived work and follow the
GPL". Just comply with what the FSF proposes.

Case 2 is madness if you don’t have a well-staffed legal team at your
disposal.

Case 3 is madness if you aren’t already in organized crime. And might be
madness even then (remember that many criminals got caught over tax
fraud. It would be ironic to see branches of the mafia get taken down
for breaching the licenses of the tools they distribute, while getting
away with murder).

Best wishes,
Arne

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]

      reply	other threads:[~2016-12-24 15:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-15  2:41 Dumb Licensing Questions Wes Frazier
2016-12-15  2:46 ` spk121
2016-12-15 19:18 ` Arne Babenhauserheide
2016-12-24  6:15   ` pelzflorian (Florian Pelz)
2016-12-24  8:03     ` tomas
2016-12-24  8:17       ` pelzflorian (Florian Pelz)
2016-12-24 13:10         ` tomas
2016-12-24 12:55       ` Greg Troxel
2016-12-24 15:08         ` Arne Babenhauserheide [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lgv5bc18.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=gdt@lexort.com \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).