From: Christopher Dimech <dimech@gmx.com>
To: moasenwood@zoho.eu
Cc: help-gnu-emacs@gnu.org, emacs-devel@gnu.org
Subject: law question
Date: Sat, 22 May 2021 01:56:51 +0200 [thread overview]
Message-ID: <trinity-db880f65-1011-4168-867f-fc37386046ab-1621641411465@3c-app-mailcom-bs04> (raw)
In-Reply-To: <87fsyfbrva.fsf@zoho.eu>
The GPL was found to be an enforceable set of copyright terms (a license) in
Jacobsen v. Katzer. What has changed now is that for the purposes of the court,
the GPL is both a license, which can be enforced through a claim of copyright
infringement, and a contract, which can be enforced through a claim of breach
of contract (Artifex v. Hancom). You can allege both in your court claim in a
single case, and fall back on one if you can’t prove the other. Thus, the potential
to enforce the GPL in court is very strong.
> Sent: Saturday, May 22, 2021 at 11:15 AM
> From: "Emanuel Berg via Users list for the GNU Emacs text editor" <help-gnu-emacs@gnu.org>
> To: help-gnu-emacs@gnu.org
> Cc: emacs-devel@gnu.org
> Subject: Re: law question
>
> Christopher Dimech wrote:
>
> >> Should we assume the worst-case scenario?
> >
> > Only if we cannot get all the required information to decide
> > if we can use the code.
>
> Right, do you also happen to know what precedents there are?
>
> --
> underground experts united
> https://dataswamp.org/~incal
>
>
>
next prev parent reply other threads:[~2021-05-21 23:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 20:59 law question Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-21 21:09 ` Jean Louis
2021-05-21 21:17 ` Christopher Dimech
2021-05-21 21:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-21 21:30 ` Jean Louis
2021-05-21 21:37 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-21 21:46 ` Christopher Dimech
2021-05-21 23:15 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-21 23:31 ` Christopher Dimech
2021-05-21 23:56 ` Christopher Dimech [this message]
2021-05-22 0:12 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-21 22:34 ` Christopher Dimech
2021-05-22 6:14 ` Eli Zaretskii
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-db880f65-1011-4168-867f-fc37386046ab-1621641411465@3c-app-mailcom-bs04 \
--to=dimech@gmx.com \
--cc=emacs-devel@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).