unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: jgart <jgart@dismail.de>
Cc: 59844@debbugs.gnu.org
Subject: [bug#59844] [PATCH 1/2] gnu: Add bugroff license.
Date: Mon, 05 Dec 2022 22:18:23 +0100	[thread overview]
Message-ID: <874ju9cyhl.fsf@nckx> (raw)
In-Reply-To: <20221205143551.GB4964@dismail.de>

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

[Apologies for the previous half-mail sent in unforgivable error.]

Hi,

The author mentions a 'no-restrictions BSD' licence in addition to 
[0].  Could they mean 0BSD?  We could just use that.  It's in 
Guix.

jgart via Guix-patches via 写道:
> Should we add it?

Bizarrely, Debian did[1][2].  Debian is not our touchstone, but 
it's an excellent smoke test.

What they were smoking when they added that is not clear to me.

A quick search turned up only packages ‘dual’-licenced under 
another, actual licence that explicitly grants the required 
rights.

In such cases, presumably the joke licence is moot: the real one 
does all the work of not getting people sued.

Kind regards,

T G-R

[0]: http://tunes.org/legalese/bugroff.html
[1]: https://www.debian.org/legal/licenses/

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

  reply	other threads:[~2022-12-05 21:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-05 20:35 [bug#59844] [PATCH 1/2] gnu: Add bugroff license jgart via Guix-patches via
2022-12-05 21:18 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2022-12-06 14:33 ` [bug#59844] [PATCH v2] gnu: Add fare-csv jgart via Guix-patches via
2022-12-06 18:58 ` [bug#59844] [PATCH v3] " jgart via Guix-patches via
2022-12-12 10:56   ` bug#59844: " Guillaume Le Vaillant

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=874ju9cyhl.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=59844@debbugs.gnu.org \
    --cc=jgart@dismail.de \
    --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 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).