all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Wojtek Kosior <koszko@koszko.org>,
	Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: Felix Lechner <felix.lechner@lease-up.com>, guix-devel@gnu.org
Subject: Re: Mixing GPL and non-copyleft code in source files
Date: Wed, 03 Jan 2024 12:32:18 -0800	[thread overview]
Message-ID: <87il4ab1kd.fsf@contorta> (raw)
In-Reply-To: <20240103184608.5d05b5c6.koszko@koszko.org>

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

On 2024-01-03, Wojtek Kosior via wrote:
> Before getting back to the discussion, please let me ask 1 question.
> Assume I submit a patch series that adds some useful and needed code and
> includes a copyright notice with a promise, like this
>
> ;;; Copyright © 2023 Wojtek Kosior <koszko@koszko.org>
> ;;; Wojtek Kosior promises not to sue for violations of this file's license.
>
> Will this weirdness be considered minor enough to tolerate?  I made
> sure the promise line takes below 78 chars.

I am not at all a lawyer, but this seems like an entirely different
license, and at the very least a pragmatic headache.

"I promise not to sue" might even hold up in one court, but not another;
anyone with a modicum of legal caution would reasonably avoid using
software with such terms, and people who are naive enough to use
something with such a baited risk attached are just setting themselves
up for getting legally attacked.

You claim you do not want to threaten anyone with force, but this sort
of licensing clause opens the door wide to all sorts of legal abuses and
threats.

It honestly feels like a sabotage clause to me, even if that is not the
intention.

I would be very concerned about guix accepting such licensing terms.

live well,
  vagrant

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

  parent reply	other threads:[~2024-01-03 20:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22 16:53 Mixing GPL and non-copyleft code in source files Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-12-22 18:00 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-12-22 21:06   ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-12-22 22:41     ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-12-23 18:19       ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-12-24  2:41         ` Liliana Marie Prikler
2023-12-24  4:15           ` Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution.
2023-12-27  9:25             ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-12-27  9:22           ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-12-27 18:31             ` Liliana Marie Prikler
2024-01-03 17:46               ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2024-01-03 20:19                 ` Liliana Marie Prikler
2024-01-03 21:22                   ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2024-01-04  5:30                     ` Liliana Marie Prikler
2024-01-03 20:32                 ` Vagrant Cascadian [this message]
2024-01-04  1:24                   ` Philip McGrath
2024-01-03 18:17             ` Alexandre Oliva
2024-01-03 21:17               ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2024-01-04 11:49           ` Alexandre Oliva

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=87il4ab1kd.fsf@contorta \
    --to=vagrant@debian.org \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@gnu.org \
    --cc=koszko@koszko.org \
    --cc=liliana.prikler@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 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.