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 Koha Library Auto


From: Jaime E . Villate
Subject: Re: [Savannah-hackers] savannah.gnu.org: submission of Koha Library Automation Package
Date: Fri, 31 May 2002 12:17:14 +0100
User-agent: Mutt/1.2.5i

Hi,
In order to release your project under the GPL you must write copyright
notices and copying permission statements at the beginning of every source
code file, and include a copy of the plain text version of the GNU GPL
(http://www.gnu.org/licenses/gpl.txt; copy it, for instance, into a file named
COPYING). In its current state, I can see that the perl programs in Koha
were written by people from Katipo, but I cannot tell if you are allowed
to modify them and import them to Savannah.

Please write copyright notices and copying permission statements following the
advice of http://www.gnu.org/licenses/gpl-howto.html and when your are done
register your project again. I also suggest that you write a README file
describing your package.

Regards,
Jaime

JaimeOn Thu, May 30, 2002 at 12:40:28AM -0400, address@hidden wrote:
> 
> A package was submitted to savannah.gnu.org.
> This mail was sent to address@hidden, address@hidden
> 
> 
> Steve Tonnesen <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: Koha Library Automation Package
> System name: koha
> This package does NOT want to apply for inclusion in the GNU project
> 
> Description:
> Koha is an open source library automation package.
> 
> Koha is currently hosted at sourceforge and can be found at:
> 
> http://sourceforge.net/projects/koha/
> 
> Other Software Required:
> perl  (DBI DBD-mysql)
> apache
> mysql
> 
> 
> Other Comments:
> Koha was initially developed by Katipo Communications of New Zealand for a 
> group of libraries in New Zealand.  The software was released under the GPL 
> at the suggestion of Katipo in the hopes that it would be widely adopted and 
> extended.
> 




reply via email to

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