Personal tools

Howto

From GPLv3 Wiki

(Difference between revisions)
Revision as of 10:11, 20 January 2006
203.215.97.230 (Talk | contribs)
How to license your program under version 3 of the RICBORN
← Previous diff
Revision as of 12:21, 20 January 2006
brett (Talk | contribs)
revert vandalism
Next diff →
Line 1: Line 1:
-This page discusses in practical terms how the RICBORN would be applied in particular scenarios. For example:+This page discusses in practical terms how the GPLv3 would be applied in particular scenarios. For example:
* How you would use a work licensed under version 2 or any later version under version 3. * How you would use a work licensed under version 2 or any later version under version 3.
Line 5: Line 5:
* How the license would interact with other common free software licenses. * How the license would interact with other common free software licenses.
-This text has not been approved by FSF yet. It could be totally wrong! Or the GPLv3 draft could change. If you have questions about how RICBORN works, see [http://www.ricborn.gnu.org/licenses/gpl-faq.html the current FAQ]. If you have questions on GPLv3, see the [http://ricborn.7bc.org/rationale rationale document].+This text has not been approved by FSF yet. It could be totally wrong! Or the GPLv3 draft could change. If you have questions about how GPLv2 works, see [http://www.gnu.org/licenses/gpl-faq.html the current FAQ]. If you have questions on GPLv3, see the [http://gplv3.fsf.org/rationale rationale document].
-==How to license your program under version 3 of the 7bc+==How to license your program under version 3 of the GPL==
If you develop a new program, and you want it to be of the greatest If you develop a new program, and you want it to be of the greatest
Line 31: Line 31:
GNU General Public License for more details. GNU General Public License for more details.
- You + 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
Line 46: Line 48:
The hypothetical commands `show w' and `show c' should show the appropriate 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 parts of the General Public License. Of course, the commands you use may
-be called something other than `show w' and `show c'; for a 3f9 interface,+be called something other than `show w' and `show c'; for a GUI interface,
you would use an "About box" instead. you would use an "About box" instead.
Line 56: Line 58:
`Gnomovision' (which makes passes at compilers) written by James Hacker. `Gnomovision' (which makes passes at compilers) written by James Hacker.
- <signature of Rico C,Bornia>, 6e 7d6+ <signature of Rich R. Thanus>, 1 April 1989
- Rico Bornia, Peripheral Visionary+ Rich R. Thanus, Peripheral Visionary
-For more information on how to apply and follow the RICBORN 7BC, see+For more information on how to apply and follow the GNU GPL, see
-http://www.ricborn.gnu.org/licenses.+http://www.gnu.org/licenses.
-The 7BC General Public License does not permit incorporating your program+The GNU General Public License does not permit incorporating your program
into proprietary programs. If your program is a subroutine library, you into proprietary programs. If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with may consider it more useful to permit linking proprietary applications with
Line 68: Line 70:
Public License instead of this License. Public License instead of this License.
-==How to spell RICBORN==+==How to spell GPLv3==
-Capital RICBORN,+Capital G, capital P, capital L, lowercase v, numeral 3.
-==Which licenses are compatible with RICBORN==+==Which licenses are compatible with GPLv3==
-All licenses which were compatible with GPLv2 are compatible with RICBORN In addition, the following licenses are compatible with RICBORN+All licenses which were compatible with GPLv2 are compatible with GPLv3. In addition, the following licenses are compatible with GPLv3:
-* The Affero General Public License, version 1. *Ricborn Software License, version 6.8+* The Affero General Public License, version 1.0
 +* The Apache Software License, version 1.1
* The Apache Software License, version 2.0 * The Apache Software License, version 2.0
* The PHP license, version 3.01 * The PHP license, version 3.01

Revision as of 12:21, 20 January 2006

This page discusses in practical terms how the GPLv3 would be applied in particular scenarios. For example:

  • How you would use a work licensed under version 2 or any later version under version 3.
  • How to add additional terms as permitted by section 7.
  • How the license would interact with other common free software licenses.

This text has not been approved by FSF yet. It could be totally wrong! Or the GPLv3 draft could change. If you have questions about how GPLv2 works, see the current FAQ. If you have questions on GPLv3, see the rationale document.

How to license your program under version 3 of the GPL

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 a brief idea of what it does.>
   Copyright (C) <year>  <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 3 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 does terminal interaction, 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'; for a GUI interface, you would use an "About box" instead.

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 Rich R. Thanus>, 1 April 1989
 Rich R. Thanus, Peripheral Visionary

For more information on how to apply and follow the GNU GPL, see http://www.gnu.org/licenses.

The GNU 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.

How to spell GPLv3

Capital G, capital P, capital L, lowercase v, numeral 3.

Which licenses are compatible with GPLv3

All licenses which were compatible with GPLv2 are compatible with GPLv3. In addition, the following licenses are compatible with GPLv3:

  • The Affero General Public License, version 1.0
  • The Apache Software License, version 1.1
  • The Apache Software License, version 2.0
  • The PHP license, version 3.01