From: Wojtek Kosior via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: guix-devel@gnu.org
Subject: Mixing GPL and non-copyleft code in source files
Date: Fri, 22 Dec 2023 17:53:25 +0100 [thread overview]
Message-ID: <20231222175325.5e611342.koszko@koszko.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]
Hi
I have some changes in my personal Guix fork that I'd like to
contribute. I'd like the lines of code I authored to be dual-licensed
under GPL-3.0-or-later and CC0-1.0. This is purely for personal
reasons (as having a mere few dozens of lines in a project under CC0
causes no practical change to the project).
How can I indicate such licensing? In one patch I sent 5 months ago (a
still unreviewed one, unfortunately) I added a line like
;;; Copyright © 2023 Wojtek Kosior <my-contribution-is-licensed-cc0@koszko.org>
while keeping the rest of the license notice intact. Yup, this happens
to be an existing email address that also conveys a message. However,
I am worried this might be too ambigious.
Are there better ways? How about introducing an SPDX license
identifier + explaining the licensing situation in the commit message?
Btw, is there anything that from technical side should be corrected in
the linked patch? I mean, besides my failure to use `list` with gexps
for the `arguments` field (I already realized that shortcoming myself)
Wojtek
[1] https://issues.guix.gnu.org/64869
-- (sig_start)
website: https://koszko.org/koszko.html
fingerprint: E972 7060 E3C5 637C 8A4F 4B42 4BC5 221C 5A79 FD1A
follow me on Fediverse: https://friendica.me/profile/koszko/profile
♥ R29kIGlzIHRoZXJlIGFuZCBsb3ZlcyBtZQ== | ÷ c2luIHNlcGFyYXRlZCBtZSBmcm9tIEhpbQ==
✝ YnV0IEplc3VzIGRpZWQgdG8gc2F2ZSBtZQ== | ? U2hhbGwgSSBiZWNvbWUgSGlzIGZyaWVuZD8=
-- (sig_end)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2023-12-22 16:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 16:53 Wojtek Kosior via Development of GNU Guix and the GNU System distribution. [this message]
2023-12-22 18:00 ` Mixing GPL and non-copyleft code in source files 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
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=20231222175325.5e611342.koszko@koszko.org \
--to=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).