unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Wojtek Kosior <koszko@koszko.org>
Cc: Felix Lechner <felix.lechner@lease-up.com>, guix-devel@gnu.org
Subject: Re: Mixing GPL and non-copyleft code in source files
Date: Thu, 04 Jan 2024 06:30:46 +0100	[thread overview]
Message-ID: <d3b63511e2030262e225e55bd162877f4562f774.camel@gmail.com> (raw)
In-Reply-To: <20240103222209.1dab71fe.koszko@koszko.org>

Am Mittwoch, dem 03.01.2024 um 22:22 +0100 schrieb Wojtek Kosior:
> > > I don't know whether you are a consequentialist but I surely am
> > > not. 
> > > I am trying to apply the principle of double effect in my
> > > reasoning.  If I am to be criticized for making morally wrong
> > > choices, let the criticism at least concern incorrect application
> > > of that principle.  
> > Even the principle of double effect goes against what you're
> > imagining. The potential threat of litigation is not intended and
> > way outweighed by the benefits of free software.
> 
> I don't see the threat as just an effect of using a non-public-domain
> license.  One that can be disputed to be intended or not.  Rather, I
> consider use of such license itself a threat, although a polite one,
> I admit.
I don't think the distinction between is and has is super meaningful
here.  Particularly, what are you threatening the other party with? 
You say litigation, but as we've already pointed out that's an
unintended consequence for those who don't comply.

If you consider licenses a threat, you should also consider dedications
to public domain a threat: anything you contribute to such a project
can and will be abused by anyone claiming ownership over whichever
small parts they add.  What are, from your perspective, the benefits of
the public domain, and how do they hold up w.r.t. the GPL or w.r.t. a
rollover license?

Cheers


  reply	other threads:[~2024-01-04  5:31 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 [this message]
2024-01-03 20:32                 ` Vagrant Cascadian
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

  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=d3b63511e2030262e225e55bd162877f4562f774.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@gnu.org \
    --cc=koszko@koszko.org \
    /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).