unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Guile parsing html and htmlprag.
Date: Sat, 17 Aug 2013 14:28:17 +0200	[thread overview]
Message-ID: <87fvu81oym.fsf@gnu.org> (raw)
In-Reply-To: 87vc3x817x.fsf@tines.lan

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

> taylanbayirli@gmail.com (Taylan Ulrich B.) writes:
>
>> If I'm not mistaken, having a nontrivial amount of code (e.g. whole
>> module) become part of the official Guile distribution requires the
>> copyright of the code (and subsequent contributions) to be assigned to
>> the FSF.  So both you and all original authors of htmlprag would need to
>> officially assign their copyright.
>
> That can't be right, because Guile has already imported several modules
> of similar size without copyright assignment. e.g. SSAX, match, and
> several SRFI implementations.  Htmlprag is distributed under the LGPL
> 2.1 or later, which should be fine for us.

Indeed.  When importing third-party code, it is usually unreasonable to
ask the author(s) to assign copyright for code that was not initially
written for Guile (info "(maintain) Copying from Other Packages").

For Htmlprag to be considered for inclusion in Guile, it would need to
have good documentation, a reasonable test suite, and an API that looks
good (I don’t know whether this is the case, just giving the check list
in case ;-)).

Ludo’.




      parent reply	other threads:[~2013-08-17 12:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24 13:04 Guile parsing html and htmlprag Dmitry Bogatov
2013-07-24 13:52 ` Taylan Ulrich B.
2013-07-24 14:09   ` [guile] " Dmitry Bogatov
2013-07-26 21:23   ` Mark H Weaver
2013-07-27 13:31     ` [guile] " Dmitry Bogatov
2013-08-17 12:28     ` Ludovic Courtès [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://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=87fvu81oym.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@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).