unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel@gnu.org
Subject: Re: Import your CK macro into Guile?
Date: Sat, 24 Nov 2012 15:26:40 +0100	[thread overview]
Message-ID: <87haofcc0v.fsf@gnu.org> (raw)
In-Reply-To: <87pq333hgd.fsf@tines.lan> (Mark H. Weaver's message of "Fri, 23 Nov 2012 20:41:54 -0500")

Hi,

Mark H Weaver <mhw@netris.org> skribis:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Mark H Weaver <mhw@netris.org> skribis:
>>
>>> Apologies if I mishandled this, but the problem here is that the code
>>> had no explicit license or copying permission notice.  If it had been
>>> explicitly published as free software, I certainly would not have
>>> bothered him about it.
>>
>> There are still two errors in the file:
>>
>>   1. There’s a line “copyright FSF”;
>>
>>   2. The file says to be GPLv3+.
>>
>> Could you fix that by removing the line and stating its actual license?
>>
>> My guess is that Oleg Kiselyov did not bother adding a license
>> boilerplate that would be longer than the actual code, but that’s still
>> a bit embarrassing.  Is there an official statement somewhere about its
>> status?
>
> As I wrote above, Oleg's code had no explicit license or copying
> permission notice.  I took 15 lines of his code, which is not "legally
> significant" according to my reading of the GNU maintainers guile.  I
> then reworked the code to use an auxillary macro instead of the
> string-literal hack.  For that reason I added the FSF copyright.

OK, makes sense, since you modified it anyway (I had forgotten that.)

It just stroke me when looking at the file to see “copyright FSF” and no
copyright line for Oleg; but as you say the copyright line doesn’t mean
much here.

> I then sent Oleg a copy of the file that I proposed for inclusion
> (with the FSF copyright and the GPLv3+ notice) and asked him if he'd
> be willing to contribute it to Guile, calling his attention to the
> attached file.  He agreed in a message sent to the guile-devel mailing
> list.

I know, but “would you like to contribute it to Guile” doesn’t mean
anything in legal terms.

Thanks,
Ludo’.



  reply	other threads:[~2012-11-24 14:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-09 18:35 Import your CK macro into Guile? Mark H Weaver
2012-11-10 10:37 ` oleg
2012-11-10 18:01 ` Ludovic Courtès
2012-11-10 19:13   ` Mark H Weaver
2012-11-23 23:15     ` Ludovic Courtès
2012-11-24  1:41       ` Mark H Weaver
2012-11-24 14:26         ` Ludovic Courtès [this message]
2012-11-24 18:53           ` Mark H Weaver
2012-11-24 23:20             ` Ludovic Courtès

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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87haofcc0v.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=mhw@netris.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.
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).