Hi, I'm evaluating the project you submitted for approval in Savannah.
On Fri, Jun 27, 2003 at 06:34:06AM -0400, [EMAIL PROTECTED] wrote: > > A package was submitted to savannah.nongnu.org > This mail was sent to [EMAIL PROTECTED], [EMAIL PROTECTED] > > > grégoire HUBERT <[EMAIL PROTECTED]> described the package as follows: > License: gpl > Other License: > Package: Yet Another Firewall For Linux > System name: yaffl > Type: non-GNU > > Description: > YAFFL - Yet Another Firewall For Linux > It is composed of 2 scripts that install anti-syn flood and automatic blacklisting > firewall on a GNU/Linux computer. This prevents usual nmap ports detection, silent > port scannings and syn-floods. It also provides NAT & masquerade for connexion > sharing. > This project is intended to be used on a personnal Linux box that is always > connected to the internet. "Linux" is just a kernel of a more complex system that we like to refer to as GNU/Linux, to emphasize the ideals of the Free Software movement. Would you mind changing references to Linux as an OS to GNU/Linux? For more information, see http://www.gnu.org/gnu/linux-and-gnu.html > > Other Software Required: > > > Other Comments: > You will find the source code at this temporary location : > http://www.coolkeums.org/downloads/yaffl-1.2-1.tar.gz > (this code has not been fully tested yet, working with it....) 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 I didn't see a copying file and the GPL copyright notices in one of the files. 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, -- Rudy Gevaert [EMAIL PROTECTED] Web page http:/www.webworm.org GNU/Linux for schools http://www.nongnu.org/glms Savannah hacker http://savannah.gnu.org _______________________________________________ Savannah-hackers mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/savannah-hackers
