unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: "Thien-Thi Nguyen" <ttn@gnuvola.org>, "Ludovic Courtès" <ludo@gnu.org>
Cc: Guile User List <guile-user@gnu.org>
Subject: Re: mod_lisp support for guile-www
Date: Fri, 12 Mar 2010 20:29:07 +0000	[thread overview]
Message-ID: <877hphl1ws.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <876355v4ni.fsf@ambire.localdomain> (Thien-Thi Nguyen's message of "Tue, 09 Mar 2010 17:30:41 +0100")

Thien-Thi Nguyen <ttn@gnuvola.org> writes:

> After a quick skim of the patch, it seems to me the core modlisp support is
> rather straightforward.  I like how you extended `big-dishing-loop'.  Perhaps
> that can be pushed out even further so that the (Guile-WWW) user can define
> other protocols.  We would run the danger of stepping on serveez's toes, but
> maybe that project won't mind so much...

Thanks for your time looking at this.

Would it really be stepping on their toes?  AFAICT they only use Guile
for configuration, whereas Guile-WWW's purpose is to provide function to
Guile applications.

> On the subject of expansions and contractions (as they relate to Guile-WWW),
> i've been thinking of moving the repo to savannah and looking for a co- (or
> perhaps replacement) maintainer, to ensure its longevity and encourage mixing
> w/ other code.  I foresee my interest in it fading, and it deserves better.
>
> Since we are in related communication, i crassly exploit the opportunity to
> ask directly: Would you like to take over Guile-WWW maintenance?

I think my personal preference would be not to maintain it as an
individual package, but to roll it into the Guile distribution.  Would
you be happy with that?

I note that Guile-WWW's license is GPLv3+, whereas the Guile
distribution as a whole is LGPLv3+.  I'm not sure if that's a problem or
not; I think I remember hearing that there are already other pieces of
code that came from guile-library and that have different licenses.

Ludo, do you know the formal position on this?

Thanks,
        Neil




  reply	other threads:[~2010-03-12 20:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-07 23:00 mod_lisp support for guile-www Neil Jerram
2010-03-09 16:30 ` Thien-Thi Nguyen
2010-03-12 20:29   ` Neil Jerram [this message]
2010-03-12 21:45     ` Ludovic Courtès
2010-03-12 23:21       ` Neil Jerram
2010-03-13  4:16     ` Thien-Thi Nguyen
2010-03-16 19:48       ` Neil Jerram
2010-03-16 22:48         ` Ludovic Courtès
2010-06-17 21:42 ` Thien-Thi Nguyen
2010-07-06 23:04   ` Neil Jerram
2010-07-06 23:48     ` Thien-Thi Nguyen

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=877hphl1ws.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-user@gnu.org \
    --cc=ludo@gnu.org \
    --cc=ttn@gnuvola.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).