From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>,
zimoun <zimon.toutoune@gmail.com>,
Philip McGrath <philip@philipmcgrath.com>,
Guix Devel <guix-devel@gnu.org>
Cc: "(" <paren@disroot.org>
Subject: Re: FSDG-compatibility of APSL-2.0
Date: Fri, 17 Jun 2022 12:00:52 +0200 [thread overview]
Message-ID: <e1097b46b9adad80205c661fe636bc4335ad98e6.camel@gmail.com> (raw)
In-Reply-To: <7b05425306ead2c333e7671a7c32b4164e4b6a50.camel@telenet.be>
Am Freitag, dem 17.06.2022 um 11:39 +0200 schrieb Maxime Devos:
> The clause is also rather extra-territorial: what if $local_country
> reforms copyright to make all sofware free, if we accepted ‘go to
> this jurisdiction clauses’, then opponents could effectively block
> the legally-enforced freeing of software by adding such a clause.
No, they can't. If $local_country makes all software free, such a
clause would likely be illegal in $local_country and thus unenforcible.
If Apple did try to sue a $local_country citizen, $local_country could
sue Apple for breaking $local_country law.
> ... currently Guix isn't using the APSL2.0 anywhere (according to git
> grep -F aspl), so it seems quite practical and effortless to just
> remove apsl2 from (guix licenses).
It actually does, through the ungoogled-chromium bundle.
Cheers
next prev parent reply other threads:[~2022-06-17 10:01 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 [this message]
2022-06-17 17:06 ` Maxime Devos
2022-06-17 20:11 ` Felix Lechner
2022-06-17 21:14 ` Maxime Devos
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=e1097b46b9adad80205c661fe636bc4335ad98e6.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
--cc=paren@disroot.org \
--cc=philip@philipmcgrath.com \
--cc=zimon.toutoune@gmail.com \
/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).