From: Kevin Ryde <user42@zip.com.au>
Subject: doc license section
Date: Thu, 15 Jan 2004 10:30:06 +1000 [thread overview]
Message-ID: <873cai3vg1.fsf@zip.com.au> (raw)
I wonder if the guile license section in the manual could say a little
more about the terms guile is published on. For a start I think it
ought to mention the readline module is gpl rather than lgpl.
I'm thinking of something like below. Perhaps with a few more words
about what free software means, and/or about source code availablity.
The one-liners about what the terms mean in practice to applications
might want to be run past an expert, perhaps even rms.
Might be worth thinking about GFDL for the manuals, while on the
subject of licenses.
The Guile License
*****************
Guile is Free Software. Guile is copyrighted, not public domain, and
there are restrictions on its distribution or redistribution, but these
restrictions are designed to permit everything a cooperating person
would want to do.
* The Guile library (libguile) and supporting files are published
under the terms of the GNU Lesser General Public License version
2.1. See the file `COPYING.LIB'.
* The Guile readline module is published under the terms of the GNU
General Public License version 2. See the file `COPYING'.
* The manual you're now reading is published under terms described at
the start of the document (*note Top::).
Basically you can give or sell copies of Guile to anyone, with or
without modifications, but you may not deprive others of these same
rights, and must clearly identify any modifications.
C code linking to the Guile library is subject to terms of that
library. Basically such code may be published on any terms, provided
users can re-link against a new or modified version of Guile.
C code linking to the Guile readline module is subject to the terms
of that module. Basically such code must be published on Free terms.
Scheme level code written to be run by Guile (but not derived from
the Guile sources) is not resticted in any way, and may be published on
any terms. We encourage authors to publish on Free terms.
You must be aware there is no warranty whatsoever for Guile. This is
described in full in the license terms.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2004-01-15 0:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 0:30 Kevin Ryde [this message]
2004-01-15 2:12 ` doc license section Stephen Compall
2004-01-20 0:46 ` Kevin Ryde
2004-01-15 21:37 ` Neil Jerram
2004-01-21 21:56 ` Marius Vollmer
2004-01-21 22:04 ` Carl Witty
2004-01-21 22:58 ` Kevin Ryde
2004-01-21 23:07 ` Marius Vollmer
2004-01-21 23:22 ` Marius Vollmer
2004-01-22 18:08 ` Pierre Bernatchez
2004-01-22 18:22 ` Paul Jarc
2004-01-22 23:18 ` Marius Vollmer
2004-01-21 22:13 ` Kevin Ryde
2004-01-21 22:40 ` Neil Jerram
2004-02-18 20:34 ` Marius Vollmer
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=873cai3vg1.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).