From: Neil Jerram <neil@ossau.uklinux.net>
To: "Julian Graham" <joolean@gmail.com>
Cc: Guile Development <guile-devel@gnu.org>,
Karl Berry <karl@freefriends.org>
Subject: Re: guile licensing niglets
Date: Sun, 20 Jan 2008 22:08:45 +0000 [thread overview]
Message-ID: <87bq7gkv4i.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <2bc5f8210801201318v10825f24k3c3246123450d52b@mail.gmail.com> (Julian Graham's message of "Sun, 20 Jan 2008 16:18:52 -0500")
"Julian Graham" <joolean@gmail.com> writes:
> Off-topic, but has there been any discussion of moving Guile to LGPLv3?
Unless I get pressure to do this, I'd prefer to postpone this for now.
There are other aspects of the Guile plan/roadmap/whatever that I'd
like to get a grip on first.
Philosophically/politically, I'm happy that LGPLv3 is the right move
for Guile. Are there any practical considerations that would
encourage us to do this sooner rather than later?
Regards,
Neil
next prev parent reply other threads:[~2008-01-20 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 21:13 guile licensing niglets Neil Jerram
2008-01-20 21:18 ` Julian Graham
2008-01-20 21:40 ` Karl Berry
2008-01-20 22:08 ` Neil Jerram [this message]
2008-01-21 23:13 ` Ludovic Courtès
2008-01-21 23:14 ` Ludovic Courtès
2008-01-22 21:50 ` Neil Jerram
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=87bq7gkv4i.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=joolean@gmail.com \
--cc=karl@freefriends.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).