1 How to Apply These Terms to Your New Programs 2 3 If you develop a new program, and you want it to be of the greatest 4possible use to the public, the best way to achieve this is to make it 5free software which everyone can redistribute and change under these terms. 6 7 To do so, attach the following notices to the program. It is safest 8to attach them to the start of each source file to most effectively 9state the exclusion of warranty; and each file should have at least 10the "copyright" line and a pointer to where the full notice is found. 11 12 <one line to give the program's name and a brief idea of what it does.> 13 Copyright (C) <year> <name of author> 14 15 This program is free software: you can redistribute it and/or modify 16 it under the terms of the GNU General Public License as published by 17 the Free Software Foundation, either version 3 of the License, or 18 (at your option) any later version. 19 20 This program is distributed in the hope that it will be useful, 21 but WITHOUT ANY WARRANTY; without even the implied warranty of 22 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 23 GNU General Public License for more details. 24 25 You should have received a copy of the GNU General Public License 26 along with this program. If not, see <http://www.gnu.org/licenses/>. 27 28Also add information on how to contact you by electronic and paper mail. 29 30 If the program does terminal interaction, make it output a short 31notice like this when it starts in an interactive mode: 32 33 <program> Copyright (C) <year> <name of author> 34 This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 35 This is free software, and you are welcome to redistribute it 36 under certain conditions; type `show c' for details. 37 38The hypothetical commands `show w' and `show c' should show the appropriate 39parts of the General Public License. Of course, your program's commands 40might be different; for a GUI interface, you would use an "about box". 41 42 You should also get your employer (if you work as a programmer) or school, 43if any, to sign a "copyright disclaimer" for the program, if necessary. 44For more information on this, and how to apply and follow the GNU GPL, see 45<http://www.gnu.org/licenses/>. 46 47 The GNU General Public License does not permit incorporating your program 48into proprietary programs. If your program is a subroutine library, you 49may consider it more useful to permit linking proprietary applications with 50the library. If this is what you want to do, use the GNU Lesser General 51Public License instead of this License. But first, please read 52<http://www.gnu.org/philosophy/why-not-lgpl.html>. 53