unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Felix Lechner <felix.lechner@gmail.com>, Guix Devel <guix-devel@gnu.org>
Subject: Re: FSDG-compatibility of APSL-2.0
Date: Fri, 17 Jun 2022 23:14:29 +0200	[thread overview]
Message-ID: <138282505b77e7a154a8a0846b60bc89ed3b9967.camel@telenet.be> (raw)
In-Reply-To: <CAFHYt57F8uq8mB6LTZZ19Tbh_sswyMw76JzPa-VDs7wKz+De3w@mail.gmail.com>

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

Felix Lechner schreef op vr 17-06-2022 om 13:11 [-0700]:
> > If you are already in California, [...], but if you don't and
> > simply
> > Apple needs to appeal to international
> > law enforcement or your country in particular, whichever is easier.
> 
> I generally think of license violations as civil matters. With some
> small exceptions, law enforcement focuses on criminal cases.

I thought that copyright violations were a criminal matter in the US,
but after some cursory searching, it appears to be more complicated. 
Apparently there's both a civil part and a criminal part, where
apparently the criminal part is for some cases of willful copyright
infringement.

> As a resident of Northern California, I personally like the local
> legal environment. You would have to talk to a lawyer to see if the
> Ninth Circuit (copyright claims are Federal) would honor the clause
> about ignoring the UN Convention after considering the relative
> strength of the parties, as a matter of sound public policy.

I don't know California but sounds nice.  Also I guess I'd need to do
the same to see if $local_country would do such a thing too.

> Perhaps the weighing of those factors played a role in why Apple's
> attempt to stipulate a venue did not render the license unfree.

Maybe, yes, I dunno.

Greetings,
Maxime.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-06-17 21:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16  6:21 FSDG-compatibility of APSL-2.0 Philip McGrath
2022-06-16  7:43 ` Liliana Marie Prikler
2022-06-16 22:02   ` Philip McGrath
2022-06-17  9:06     ` zimoun
2022-06-17  9:39       ` Maxime Devos
2022-06-17 10:00         ` Liliana Marie Prikler
2022-06-17 17:06           ` Maxime Devos
2022-06-17 20:11             ` Felix Lechner
2022-06-17 21:14               ` Maxime Devos [this message]
2022-06-17 14:37         ` zimoun
2022-06-17 15:52           ` Philip McGrath
2022-06-17  9:40       ` Maxime Devos
2022-06-17 17:11 ` Maxime Devos
2022-06-17 17:13 ` Maxime Devos

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=138282505b77e7a154a8a0846b60bc89ed3b9967.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=felix.lechner@gmail.com \
    --cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).