savannah-hackers
[Top][All Lists]
Advanced

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

[Savannah-hackers] Re: submission of nanoFTPd - savannah.nongnu.org


From: Mathieu Roy
Subject: [Savannah-hackers] Re: submission of nanoFTPd - savannah.nongnu.org
Date: 15 Jul 2003 12:51:40 +0200
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2

Hi,

I'm evaluating the project you submitted for approval in Savannah.


address@hidden said:

> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
> 
> Szilveszter Farkas <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: nanoFTPd
> System name: nanoftpd
> Type: non-GNU
> 
> Description:
> The project, called nanoFTPd, is aimed to develop a fully functional FTP 
> server in PHP language.
> 
> There are already an amount of features included in the latest version, such 
> as:
>  - user authentication against a database/flat file
>  - mysql and postgresql support
>  - passive mode
>  - dynamic ip support
>  - basic ftp commands
>  - logging
>  - resuming downloads
>  - connection limitations (overall/per ip)
> 
> And we plan to add some other features, like ratio management, group-based 
> permission management, etc.
> 
> The homepage of nanoFTPd can be found at: http://nanoftpd.sourceforge.net/

To release your project under the GPL, you should put
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 GPL
(http://www.gnu.org/licenses/gpl.txt).
Put it in a file named COPYING.

Please follow the advice of http://www.gnu.org/licenses/gpl-howto.html.

The GPL FAQ explain the reason behind these recommendations.  For
example, there is an entry explaining why the GPL requires including a
copy of the GPL with every copy of the program:
 http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude


Also , licensing under the "GNU GPL v2 only" is problematic.
Would you please agree to license under the "GNU GPL v2 or later"?

The reason for this is that when we publish GPL v3, it will
be important for all GPL-covered programs to advance to GPL v3.
If you don't put this in the files now, the only way to port
your program to GPL v3 would be to ask each and every copyright holder,
and that may be very difficult.
We can explain the issue in more detail if you wish.
If you have concerns about "GNU GPL v2 or later", We'd be
happy to address them too.


Please register your project once more with the changes mentioned
above.  The way we handle pending projects makes it difficult to keep
track of projects that have been answered but have not been approved
yet, so we erase them and we ask you to register the project again every
time some change has to be done to the registration, and users might
have to register their projects several times.  Thank you for your
understanding.

Some users find it useful to use the big re-registration URL provided in
the acknowledgment e-mail you received after registration.

Regards,


-- 
Mathieu Roy
 
  Homepage:
    http://yeupou.coleumes.org
  Not a native english speaker: 
    http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english




reply via email to

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