doc: Set document encoding to UTF-8; typeset my surname correctly.
[bpt/guile.git] / doc / ref / preface.texi
... / ...
CommitLineData
1@c -*-texinfo-*-
2@c This is part of the GNU Guile Reference Manual.
3@c Copyright (C) 1996, 1997, 2000, 2001, 2002, 2003, 2004, 2010, 2011
4@c Free Software Foundation, Inc.
5@c See the file guile.texi for copying conditions.
6
7@node Preface
8@unnumbered Preface
9
10This manual describes how to use Guile, GNU's Ubiquitous Intelligent
11Language for Extensions. It relates particularly to Guile version
12@value{VERSION}.
13
14@menu
15* Contributors::
16* Guile License::
17@end menu
18
19@node Contributors
20@unnumberedsec Contributors to this Manual
21
22Like Guile itself, the Guile reference manual is a living entity, cared
23for by many people over a long period of time. As such, it is hard to
24identify individuals of whom to say ``yes, this person, she wrote the
25manual.''
26
27Still, among the many contributions, some caretakers stand out. First
28among them is Neil Jerram, who has been working on this document for ten
29years now. Neil's attention both to detail and to the big picture have
30made a real difference in the understanding of a generation of Guile
31hackers.
32
33Next we should note Marius Vollmer's effect on this document. Marius
34maintained Guile during a period in which Guile's API was
35clarified---put to the fire, so to speak---and he had the good sense to
36effect the same change on the manual.
37
38Martin Grabmueller made substantial contributions throughout the manual
39in preparation for the Guile 1.6 release, including filling out a lot of
40the documentation of Scheme data types, control mechanisms and
41procedures. In addition, he wrote the documentation for Guile's SRFI
42modules and modules associated with the Guile REPL.
43
44Ludovic Court@`es and Andy Wingo, the Guile maintainers at the time of
45this writing (late 2010), have also made their dent in the manual,
46writing documentation for new modules and subsystems in Guile 2.0. They
47are also responsible for ensuring that the existing text retains its
48relevance as Guile evolves. @xref{Reporting Bugs}, for more information
49on reporting problems in this manual.
50
51The content for the first versions of this manual incorporated and was
52inspired by documents from Aubrey Jaffer, author of the SCM system on
53which Guile was based, and from Tom Lord, Guile's first maintainer.
54Although most of this text has been rewritten, all of it was important,
55and some of the structure remains.
56
57The manual for the first versions of Guile were largely written, edited,
58and compiled by Mark Galassi and Jim Blandy. In particular, Jim wrote
59the original tutorial on Guile's data representation and the C API for
60accessing Guile objects.
61
62Significant portions were also contributed by Thien-Thi Nguyen, Kevin
63Ryde, Mikael Djurfeldt, Christian Lynbech, Julian Graham, Gary Houston,
64Tim Pierce, and a few dozen more. You, reader, are most welcome to join
65their esteemed ranks. Visit Guile's web site at
66@uref{http://www.gnu.org/software/guile/} to find out how to get
67involved.
68
69
70@node Guile License
71@unnumberedsec The Guile License
72@cindex copying
73@cindex GPL
74@cindex LGPL
75@cindex license
76
77Guile is Free Software. Guile is copyrighted, not public domain, and
78there are restrictions on its distribution or redistribution, but
79these restrictions are designed to permit everything a cooperating
80person would want to do.
81
82@itemize @bullet
83@item
84The Guile library (libguile) and supporting files are published under
85the terms of the GNU Lesser General Public License version 3 or later.
86See the files @file{COPYING.LESSER} and @file{COPYING}.
87
88@item
89The Guile readline module is published under the terms of the GNU
90General Public License version 3 or later. See the file @file{COPYING}.
91
92@item
93The manual you're now reading is published under the terms of the GNU
94Free Documentation License (@pxref{GNU Free Documentation License}).
95@end itemize
96
97C code linking to the Guile library is subject to terms of that
98library. Basically such code may be published on any terms, provided
99users can re-link against a new or modified version of Guile.
100
101C code linking to the Guile readline module is subject to the terms of
102that module. Basically such code must be published on Free terms.
103
104Scheme level code written to be run by Guile (but not derived from
105Guile itself) is not restricted in any way, and may be published on any
106terms. We encourage authors to publish on Free terms.
107
108You must be aware there is no warranty whatsoever for Guile. This is
109described in full in the licenses.
110
111
112@c Local Variables:
113@c TeX-master: "guile.texi"
114@c End: