different ways as she likes to as many different parties as she wishes.

Some companies, such as MySQL AB and TrollTech, use this to their

financial advantage with regard to a GPL'd code base. The standard

version is available from the company under the terms of the GPL\@.

However, parties can purchase separate proprietary software licensing for

a fee.

This business model is problematic because it means that the GPL'd code

base must be developed in a somewhat monolithic way, because volunteer

Free Software developers may be reluctant to assign their copyrights to

the company because it will not promise to always and forever license the

software as Free Software. Indeed, the company will surely use such code

contributions in proprietary versions licensed for fees.

\section{Ongoing Compliance}

GPL compliance is in fact a very simple matter -- much simpler than

typical proprietary software agreements and EULAs. Usually, the most

difficult hurdle is changing from a proprietary software mindset to one

that seeks to foster a community of sharing and mutual support. Certainly

complying with the GPL from a users' perspective gives substantially fewer

headaches than proprietary license compliance.

For those who go into the business of distributing {\em modified\\}

versions of GPL'd software, the burden is a bit higher, but not by

much. The glib answer is that by releasing the whole product as Free

Software, it is always easy to comply with the GPL. However,

admittedly to the dismay of FSF, many modern and complex software

systems are built using both proprietary and GPL'd components that are

not legally derivative works of each other. Sometimes, it is easier simply to

improve existing GPL'd application than to start from scratch. In

exchange for that benefit, the license requires that the modifier give

back to the commons that made the work easier in the first place. It is a

reasonable trade-off and a way to help build a better world while also

making a profit.

Note that FSF does provide services to assist companies who need

assistance in complying with the GPL. You can contact FSF's GPL

Compliance Labs at $<$compliance@fsf.org$>$.

If you are particularly interested in matters of GPL compliance, we

recommend the second course in this series, {\em GPL Compliance Case

  Studies and Legal Ethics in Free Software Licensing\/}, in which we

discuss some real GPL violation cases that FSF has worked to resolve.

Consideration of such cases can help give insight on how to handle GPL

compliance in new situations.

\appendix

\begin{center}

{\parindent 0in

Version 2, June 1991

Copyright \copyright\ 1989, 1991 Free Software Foundation, Inc.

\bigskip

59 Temple Place - Suite 330, Boston, MA  02111-1307, USA

\bigskip

Everyone is permitted to copy and distribute verbatim copies

of this license document, but changing it is not allowed.

}

\end{center}

\begin{center}

{\bf\large Preamble}

\end{center}

The licenses for most software are designed to take away your freedom

to share and change it. By contrast, the GNU General Public License is

intended to guarantee your freedom to share and change Free

Software---to make sure the software is free for all its users. This

General Public License applies to most of the Free Software

Foundation's software and to any other program whose authors commit to

using it. (Some other Free Software Foundation software is covered by

the GNU Library General Public License instead.) You can apply it to

your programs, too.

When we speak of Free Software, we are referring to freedom, not price.

Our General Public Licenses are designed to make sure that you have the

freedom to distribute copies of Free Software (and charge for this service

if you wish), that you receive source code or can get it if you want it,

that you can change the software or use pieces of it in new Free programs;

and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to

deny you these rights or to ask you to surrender the rights. These

restrictions translate to certain responsibilities for you if you

distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or

for a fee, you must give the recipients all the rights that you have. You

but WITHOUT ANY WARRANTY; without even the implied warranty of

MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the

GNU General Public License for more details.

You should have received a copy of the GNU General Public License

along with this program; if not, write to the Free Software

Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA  02111-1307, USA.

\end{quote}

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this

when it starts in an interactive mode:

\begin{quote}

Gnomovision version 69, Copyright (C) yyyy  name of author \\

Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. \\

This is Free Software, and you are welcome to redistribute it

under certain conditions; type `show c' for details.

\end{quote}

The hypothetical commands {\tt show w} and {\tt show c} should show the

appropriate parts of the General Public License. Of course, the commands

you use may be called something other than {\tt show w} and {\tt show c};

they could even be mouse-clicks or menu items---whatever suits your

program.

You should also get your employer (if you work as a programmer) or your

school, if any, to sign a ``copyright disclaimer'' for the program, if

necessary. Here is a sample; alter the names:

\begin{quote}

Yoyodyne, Inc., hereby disclaims all copyright interest in the program \\

`Gnomovision' (which makes passes at compilers) written by James Hacker. \\

signature of Ty Coon, 1 April 1989 \\

Ty Coon, President of Vice

\end{quote}

This General Public License does not permit incorporating your program

into proprietary programs. If your program is a subroutine library, you

may consider it more useful to permit linking proprietary applications

with the library. If this is what you want to do, use the GNU Library

General Public License instead of this License.

\begin{center}

{\parindent 0in

Version 2.1, February 1999

Copyright \copyright\ 1991, 1999 Free Software Foundation, Inc.

\bigskip

59 Temple Place - Suite 330, Boston, MA  02111-1307, USA

\bigskip

Everyone is permitted to copy and distribute verbatim copies

of this license document, but changing it is not allowed.

\bigskip

[This is the first released version of the Lesser GPL. It also counts

 as the successor of the GNU Library Public License version 2, hence

 the version number 2.1.]

}

\end{center}

\begin{center}

{\bf\large Preamble}

\end{center}

The licenses for most software are designed to take away your freedom to

share and change it. By contrast, the GNU General Public Licenses are

intended to guarantee your freedom to share and change Free Software---to

make sure the software is free for all its users.

This license, the Lesser General Public License, applies to some specially

designated software packages---typically libraries---of the Free Software

Foundation and other authors who decide to use it. You can use it too,

but we suggest you first think carefully about whether this license or the

ordinary General Public License is the better strategy to use in any

particular case, based on the explanations below.

When we speak of Free Software, we are referring to freedom of use, not

price. Our General Public Licenses are designed to make sure that you

have the freedom to distribute copies of Free Software (and charge for

this service if you wish); that you receive source code or can get it if

you want it; that you can change the software and use pieces of it in new

Free programs; and that you are informed that you can do these things.

\pagebreak[4]

\section*{How to Apply These Terms to Your New Libraries}

If you develop a new library, and you want it to be of the greatest

possible use to the public, we recommend making it Free Software that

everyone can redistribute and change. You can do so by permitting

redistribution under these terms (or, alternatively, under the terms of

the ordinary General Public License).

To apply these terms, attach the following notices to the library. It is

safest to attach them to the start of each source file to most effectively

convey the exclusion of warranty; and each file should have at least the

``copyright'' line and a pointer to where the full notice is found.

\begin{quote}

one line to give the library's name and a brief idea of what it does. \\

Copyright (C) year  name of author \\

This library is Free Software; you can redistribute it and/or modify it

under the terms of the GNU Lesser General Public License as published by

the Free Software Foundation; either version 2.1 of the License, or (at

your option) any later version.

This library is distributed in the hope that it will be useful, but

WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY

or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public

License for more details.

You should have received a copy of the GNU Lesser General Public License

along with this library; if not, write to the Free Software Foundation,

Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

\end{quote}

Also add information on how to contact you by electronic and paper mail.

You should also get your employer (if you work as a programmer) or your

school, if any, to sign a ``copyright disclaimer'' for the library, if

necessary. Here is a sample; alter the names:

\begin{quote}

Yoyodyne, Inc., hereby disclaims all copyright interest in the program \\

`Gnomovision' (which makes passes at compilers) written by James Hacker. \\

signature of Ty Coon, 1 April 1990 \\

Ty Coon, President of Vice

\end{quote}

\begin{center}

{\parindent 0in

Version 1, March 2002

Copyright \copyright\ 2002 Affero, Inc.

\bigskip

510 Third Street - Suite 225, San Francisco, CA 94107, USA

\bigskip

This license is a modified version of the GNU General Public License

copyright (C) 1989, 1991 Free Software Foundation, Inc. made with

their permission. Section 2(d) has been added to cover use of software

over a computer network.

Everyone is permitted to copy and distribute verbatim copies

of this license document, but changing it is not allowed.

}

\end{center}

\begin{center}

{\bf\large Preamble}

\end{center}

The licenses for most software are designed to take away your freedom

to share and change it. By contrast, the Affero General Public License

is intended to guarantee your freedom to share and change free

software--to make sure the software is free for all its users. This

Public License applies to most of Affero's software and to any other

program whose authors commit to using it. (Some other Affero software

is covered by the GNU Library General Public License instead.) You can

apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. This General Public License is designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.