From: zimoun <firstname.lastname@example.org>
To: Philip McGrath <email@example.com>,
Guix Devel <firstname.lastname@example.org>,
Liliana Marie Prikler <email@example.com>
Cc: Maxime Devos <firstname.lastname@example.org>, "(" <email@example.com>
Subject: Re: FSDG-compatibility of APSL-2.0
Date: Fri, 17 Jun 2022 11:06:50 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On Thu, 16 Jun 2022 at 18:02, Philip McGrath <email@example.com> wrote:
> I don't want to speak for Maxime, but AIUI the question was whether Guix ought
> to continue to accept all licenses on that list, or instead ought adopt some
> different (more stringent?) license policy.
FWIW, I think that adopting a different (more stringent) license policy
hits two issues:
1. Where do you draw the line? Based on which concrete principles to
decide for this or for that?
Here, each time we discuss license policy, it is some WANL sessions
. Therefore, the line cannot be drawn using legal consideration (as
FSF does and then used by the GNU project).
How to draw the line? Using my personal perception? Using yours? How
do we resolve the disagreements?
I think it is not affordable to adopt a different license policy than
the one listed by the GNU project . It is a pragmatical line
because the Guix project does not have the manpower nor the structure
to do differently.
2. The GNU project is already strict on what is accepted; for good
reasons. The Guix project is a niche and being more stringent would
lead to be an even more niche. And I miss what aim it would serve.
next prev parent reply other threads:[~2022-06-17 9:09 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 [this message]
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
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
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:
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).