From: "Eric S. Raymond" <esr@thyrsus.com>
To: freedomfromruin@aaathats3as.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Licenses and revocability, in a paragraph or less.
Date: Thu, 27 Sep 2018 23:56:48 -0400 [thread overview]
Message-ID: <20180928035648.GA27803@thyrsus.com> (raw)
In-Reply-To: <6ed65e31150937cad0733374eb8a9ef4@aaathats3as.com>
freedomfromruin@aaathats3as.com <freedomfromruin@aaathats3as.com>:
> As has been stated in easily accessible terms elsewhere:
> "Most courts hold that simple, non-exclusive licenses with unspecified
> durations that are silent on revocability are revocable at will. This means
> that the licensor may terminate the license at any time, with or without
> cause." +
Furthermore, license revocation is not the only option. In Jacobsen
vs. Katzer (535 F.3d 1373 (Fed. Cir. 2008) it was found that
open-source developers have an actionable right not to have their
software misappropriated even though the resulting damages are only
reputational rather than monetary.
Under that theory, developers can seek an injunction against a
misappropriating party without globally revoking their license.
The application of that case law to this situation is left as
an easy exercise for the reader. Any competent paralegal could
write the brief in an evening. Hell, I could almost do it myself.
I do not personally want to see this happen. But that it is possible
is a fact all parties must deal with.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.
next prev parent reply other threads:[~2018-09-28 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 3:30 freedomfromruin
2018-09-28 3:56 ` Eric S. Raymond [this message]
2018-09-29 1:00 ` freedomfromruin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180928035648.GA27803@thyrsus.com \
--to=esr@thyrsus.com \
--cc=freedomfromruin@aaathats3as.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome