all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Philip McGrath <philip@philipmcgrath.com>, 55998@debbugs.gnu.org
Subject: [bug#55998] [PATCH] gnu: Add cctools.
Date: Wed, 15 Jun 2022 21:35:15 +0200	[thread overview]
Message-ID: <401cbe02c58323fd1a52de199e3312b04ca411f0.camel@telenet.be> (raw)
In-Reply-To: <a4a872dd-eeb3-3a88-32c0-e7c75389b81b@philipmcgrath.com>

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

Philip McGrath schreef op wo 15-06-2022 om 15:06 [-0400]:
> I agree that the choice-of-law language is less than friendly to users.
> 
> The FSF has issued an opinion [1] that the APSL 2.0 is a free software 
> license: they say that "Apple's lawyers worked with the FSF to produce a 
> license that would qualify" (after problems with earlier versions of the 
> license)

I am not contesting that FSF considers APSL 2.0 to be a free software
license.  In fact, I looked at that web page to look at why FSF
considers it to be a free software license.  But I didn't find any
answer about the ‘dispute resolution’ clause.  So it seems to me that
FSF overlooked that particular issue, considered it acceptable because
of the US being based in the US, or considered it acceptable due to
some other (unknown) reason.

In case of the FSF overlooking things: mistakes can and should be
corrected (this is a free software distro!).  In case of US-centrism:
err, no.  In case of an unknwon reason: reason is unknown.

The point is being free, not being stamped as free by the FSF.

> IIUC, (guix licenses) only defines FSDG-compatible licenses.

Apparently, it doesn't, given the presence of the APSL 2.0, though
that's a bug.

> Certainly there are broader community governance questions
> implicated, but I don't think this patch needs to resolve them.

I did not ask anything about community governance?

Greetings,
Maxime.


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

  reply	other threads:[~2022-06-15 19:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15 17:15 [bug#55998] [PATCH] gnu: Add cctools Philip McGrath
2022-06-15 18:32 ` Maxime Devos
2022-06-15 18:45 ` Maxime Devos
2022-06-15 19:06   ` Philip McGrath
2022-06-15 19:35     ` Maxime Devos [this message]
2022-06-15 21:00       ` Philip McGrath
2022-06-15 21:11         ` Maxime Devos
2022-06-15 21:20         ` ( via Guix-patches via
2022-06-15 18:53 ` Maxime Devos
2022-06-15 19:19   ` Philip McGrath
2022-06-15 20:07     ` Maxime Devos
2022-06-17 11:28       ` Philip McGrath
2022-06-15 18:55 ` Maxime Devos
2022-06-15 19:34   ` Philip McGrath
2022-06-15 18:56 ` Maxime Devos
2022-06-15 19:21   ` Philip McGrath
2022-06-15 19:23     ` Maxime Devos
2022-06-17 11:19       ` Philip McGrath
2022-06-15 20:04 ` Maxime Devos
2022-06-17 11:09   ` Philip McGrath
2022-06-19 21:01   ` Ludovic Courtès
2022-06-15 20:17 ` Maxime Devos
2022-06-16 22:29   ` Philip McGrath
2022-06-17  6:14     ` Maxime Devos
2022-06-15 20:18 ` Maxime Devos
2022-06-15 20:23 ` Maxime Devos
2022-06-16 23:29   ` Philip McGrath
2022-06-17 11:51 ` [bug#55998] [PATCH v2] " Philip McGrath
2022-06-19 21:02   ` bug#55998: [PATCH] " Ludovic Courtès

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=401cbe02c58323fd1a52de199e3312b04ca411f0.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=55998@debbugs.gnu.org \
    --cc=philip@philipmcgrath.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.