From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: base64: Restore original license header (license compliance issue)
Date: Sat, 27 Aug 2016 08:48:35 -0500 [thread overview]
Message-ID: <87d1ku8gr0.fsf@dustycloud.org> (raw)
In-Reply-To: <87inumodd7.fsf@elephly.net>
Ricardo Wurmus writes:
> Christopher Allan Webber <cwebber@dustycloud.org> writes:
>
>> When incorporating a copyleft licensed program with a lax licensed program,
>> it is correct to preserve the original license notice. See also:
>> https://www.softwarefreedom.org/resources/2007/gpl-non-gpl-collaboration.html
>>
>> base64.scm did not do this. This is important, because it is part of
>> the license that the copyright header be preserved, so we must do this
>> to comply correctly.
>>
>> (This is a common confusion: adding a stronger copyleft does not
>> "relicense" the original work.)
>
> Thank you for this patch. I’m not familiar with these licensing details
> but what you write looks plausible to me.
>
> ~~ Ricardo
Ok cool, pushed!
prev parent reply other threads:[~2016-08-27 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 20:18 base64: Restore original license header (license compliance issue) Christopher Allan Webber
2016-08-27 7:55 ` Ricardo Wurmus
2016-08-27 13:48 ` Christopher Allan Webber [this message]
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=87d1ku8gr0.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).