From: "Philip McGrath" <philip@philipmcgrath.com>
To: "Vagrant Cascadian" <vagrant@debian.org>,
"Wojtek Kosior" <koszko@koszko.org>,
"Liliana Marie Prikler" <liliana.prikler@gmail.com>
Cc: "Felix Lechner" <felix.lechner@lease-up.com>,
"Brian Cully" <guix-devel@gnu.org>
Subject: Re: Mixing GPL and non-copyleft code in source files
Date: Wed, 03 Jan 2024 20:24:10 -0500 [thread overview]
Message-ID: <d69f803a-1749-4b47-9690-3cc28574656f@app.fastmail.com> (raw)
In-Reply-To: <87il4ab1kd.fsf@contorta>
On Wed, Jan 3, 2024, at 3:32 PM, Vagrant Cascadian wrote:
> 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.
>
In the spirit of sticking to the concrete issue, there is precedent for GNU software accepting changes that the contributor has placed in the public domain: see in particular <https://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html>. In fact, since Guix leaves copyright ownership with individual contributors, it seems like there's no way to stop contributors from also licensing their contributions under additional licenses.
I think it could make sense to include in the commit message something like, "I, Alyssa P. Hacker, dedicate my contribution in this commit to the public domain under CC0-1.0.". That would make it clear exactly what changes are covered.
Philip
next prev parent reply other threads:[~2024-01-04 1:25 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
2024-01-04 1:24 ` Philip McGrath [this message]
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=d69f803a-1749-4b47-9690-3cc28574656f@app.fastmail.com \
--to=philip@philipmcgrath.com \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
--cc=koszko@koszko.org \
--cc=liliana.prikler@gmail.com \
--cc=vagrant@debian.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).