Filter
Top Products
How to Apply These Terms to Your
New Programs
If you develop a new program, and you want it to be of
the greatest possible use to the public, the best way to
achieve this is to make it free software which everyone
can redistribute and change under these terms.
To do so, attach the following notices to the program. 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.
one line to give the program’s name and an idea of
what it does.
Copyright (C) yyyy name of author
This program is free software; you can redistribute it
and/or modify it under the terms of the GNU General
Public License as published by the Free Software
Foundation; either version 2 of the License, or (at your
option) any later version.
This program 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 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., 51 Franklin Street,
Fifth Floor, Boston, MA 02110-1301, USA.
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:
Gnomovision version 69, Copyright (C) year 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.
The hypothetical commands ‘show w’ and ‘show c’
should show the appropriate parts of the General Public
License. Of course, the commands you use may be
called something other than ‘show w’ and ‘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:
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 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 Lesser General Public License instead of this
License.
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright © 2007 Free Software Foundation, Inc.
<http://fsf.org/>
Everyone is permitted to copy and distribute verbatim
copies of this license document, but changing it is not
allowed.
Preamble
The GNU General Public License is a free, copyleft
license for software and other kinds of works.
The licenses for most software and other practical
works are designed to take away your freedom to share
and change the works. By contrast, the GNU General
Public License is intended to guarantee your freedom to
share and change all versions of a program--to make
sure it remains free software for all its users. We, the
Free Software Foundation, use the GNU General Public
License for most of our software; it applies also to any
other work released this way by its authors. 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 them 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 prevent others from
denying you these rights or asking you to surrender the
rights. Therefore, you have certain responsibilities if you
distribute copies of the software, or if you modify it:
responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program,
whether gratis or for a fee, you must pass on to the
recipients the same freedoms that you received. 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.
Developers that use the GNU GPL protect your rights
with two steps: (1) assert copyright on the software,
and (2) offer you this License giving you legal permission
to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL
clearly explains that there is no warranty for this free
software. For both users' and authors' sake, the GPL
requires that modified versions be marked as changed,
so that their problems will not be attributed erroneously
to authors of previous versions.