savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Savannah-hackers] savannah.gnu.org: submission of PHP Web Proxy


From: Loic Dachary
Subject: Re: [Savannah-hackers] savannah.gnu.org: submission of PHP Web Proxy
Date: Mon, 31 Dec 2001 13:16:22 +0100

alex writes:
 > On Mon, 2001-12-31 at 11:58, Loic Dachary wrote:
 > > 
 > >    Ok then. Could you re-submit your project please ? When uploading
 > > to Savannah, please change the GPL and all that with a proper copyright
 > > notice.
 > 
 > Sure. I assume the "proper" text can be found on Savanah, I wasn't
 > planning on putting the whole license in the script but I can create
 > some embryonic README, INSTALL and LICENSE files for the minimal
 > distribution.

        It really depends if the script is likely to grow or not. If it's
only a few lines length and will stay this way, you might as well use an
all permissive license (modified BSD for instance).

 > As the Snoopy class is GPL and I have yet to hear from the authors I
 > shall put a properly referenced copy of it in the CVS to reduce external
 > package dependancies for now. If development restarts on Snoopy I can
 > always remove it or keep it in sync.

        If you're not the original author then the only option is to 
add a proper copyright notice + a copy of the GPL. A bit overkill but does
not require the approval of the original author. For more information see
at the end of 

http://www.gnu.org/licenses/gpl.txt 

 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 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 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., 59 Temple Place, Suite 330, Boston, MA  02111-1307  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 Library General
Public License instead of this License



        Cheers,

-- 
Loic   Dachary         http://www.dachary.org/  address@hidden
12 bd  Magenta         http://www.senga.org/      address@hidden
75010    Paris         T: 33 1 42 45 07 97          address@hidden
        GPG Public Key: http://www.dachary.org/loic/gpg.txt



reply via email to

[Prev in Thread] Current Thread [Next in Thread]