all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 46784@debbugs.gnu.org, lle-bout@zaclys.net
Subject: [bug#46784] [PATCH 1/2] guix: Add Zero-Clause BSD License.
Date: Sat, 27 Feb 2021 18:05:54 +0100	[thread overview]
Message-ID: <874khx5tl9.fsf@nckx> (raw)
In-Reply-To: <87r1l1203h.fsf@nicolasgoaziou.fr>

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

Nicolas Goaziou 写道:
> OTOH, bsd-0 is not totally accurate either, because zero-clause 
> BSD is
> not a BSD derivative. So, here come my nitpick: what about 
> zero-bsd?

I disagree (disclaimer: I'm the one who suggested ‘bsd-0’ to Alex 
:-) that accuracy is implied or valuable.  Guix maps 
‘n-clause-BSD’ to ‘bsd-n’, we get (marginally) fewer requests to 
add ‘missing’ licences, all is well with the world.

It's true that the 0-clause BSD licence was based on the ISC text; 
that doesn't make it any less of a BSD licence.  That requires 
claiming that OpenBSD is not under a BSD licence either, which is 
a... certain kind of correct.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2021-02-27 17:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 23:41 [bug#46784] [PATCH 1/2] guix: Add Zero-Clause BSD License Alexandros Theodotou
2021-02-25 23:41 ` [bug#46785] [PATCH 2/2] gnu: Add mamba Alexandros Theodotou
2021-02-25 23:59   ` [bug#46785] [PATCH] " Alexandros Theodotou
2021-03-06 10:41     ` bug#46785: [PATCH 2/2] " Ludovic Courtès
2021-02-25 23:57 ` [bug#46784] [PATCH 1/2] guix: Add Zero-Clause BSD License Alexandros Theodotou
2021-02-26 10:07 ` Léo Le Bouter via Guix-patches via
2021-02-27 11:58   ` Nicolas Goaziou
2021-02-27 17:05     ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2021-03-06 10:40       ` bug#46784: " 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=874khx5tl9.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=46784@debbugs.gnu.org \
    --cc=lle-bout@zaclys.net \
    --cc=mail@nicolasgoaziou.fr \
    --cc=me@tobias.gr \
    /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.