From: Mark H Weaver <mhw@netris.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Import your CK macro into Guile?
Date: Sat, 10 Nov 2012 14:13:04 -0500 [thread overview]
Message-ID: <87r4o19sqn.fsf@tines.lan> (raw)
In-Reply-To: <87ip9d1gn9.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 10 Nov 2012 19:01:30 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> I'd like to import your CK macro into Guile. Would you be willing to
>> contribute it to Guile? If so, please respond to the list to say so.
>> It's small enough (15 lines) that I guess we don't need papers.
>
> For the record, there’s usually no paperwork involved when incorporating
> third-party code like this. It would be inappropriate to ask people who
> wrote code for some unrelated external project to assign copyright to
> the FSF (info "(maintain) External Libraries").
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.
> (It’s also interesting to see how the SLOC metric doesn’t work here,
> given that the explanation of those 15 lines fits in several pages of
> dense non-trivial technical work. :-))
Hmm. While that's true, I took only 15 (non-blank) lines from it.
Is that not the relevant metric?
I confess that I have much to learn on these matters, and am eager to
learn :)
Mark
next prev parent reply other threads:[~2012-11-10 19:13 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 [this message]
2012-11-23 23:15 ` Ludovic Courtès
2012-11-24 1:41 ` Mark H Weaver
2012-11-24 14:26 ` Ludovic Courtès
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=87r4o19sqn.fsf@tines.lan \
--to=mhw@netris.org \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.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).