From: Greg Troxel <gdt@lexort.com>
To: <tomas@tuxteam.de>
Cc: guile-user@gnu.org
Subject: Re: Dumb Licensing Questions
Date: Sat, 24 Dec 2016 07:55:41 -0500 [thread overview]
Message-ID: <smueg0xfpv6.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <20161224080340.GB30358@tuxteam.de> (tomas@tuxteam.de's message of "Sat, 24 Dec 2016 09:03:41 +0100")
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
<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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 162 bytes --]
next prev parent reply other threads:[~2016-12-24 12:55 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 [this message]
2016-12-24 15:08 ` Arne Babenhauserheide
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=smueg0xfpv6.fsf@linuxpal.mit.edu \
--to=gdt@lexort.com \
--cc=guile-user@gnu.org \
--cc=tomas@tuxteam.de \
/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).