[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-register-public] [task #4862] Submission of Gnu Forensic Zip
From: |
Davidlohr Bueso Arnett |
Subject: |
[Savannah-register-public] [task #4862] Submission of Gnu Forensic Zip |
Date: |
Mon, 24 Oct 2005 12:26:46 -0300 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Firefox/1.0.7 (Debian package 1.0.7-1) |
Update of task #4862 (project administration):
Status: None => Wait reply
Assigned to: None => unixoz
_______________________________________________________
Follow-up Comment #1:
Hi,
I'm evaluating the project you submitted for approval in Savannah.
Your project is not yet part of the GNU project, so we cannot accept its
current name. So please change the projects full name, mainly eliminating the
GNU part.
While there are non-GNU programs with names that include 'gnu', such as
gnuplot and gnuboy, they are not hosted on Savannah.
We want to maintain the distinction between GNU and non-GNU projects.
When your project is accepted into the GNU project you may change its name.
You can do this by asking us.
It's not valid to link code released under the GNU GPL and
code under the license used by OpenSSL. Please read
http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs
I recommend you change to GNUTLS.
In order to release your project properly and unambiguously under the GNU
GPL, please place copyright notices and permission-to-copy statements at the
beginning of every file of source code.
In addition, if you haven't already, please include a copy of the plain text
version of the GPL, available from http://www.gnu.org/licenses/gpl.txt, into
a file named "COPYING".
For more information, see http://www.gnu.org/licenses/gpl-howto.html.
If some of your files cannot carry such notices (e.g. binary files), then you
can add a README file in the same directory containing the copyright and
license notices. Check
http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html for further
information.
The GPL FAQ explains why these procedures must be followed. To learn why a
copy of the GPL must be included with every copy of the code, for example,
see http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude.
To help us better keep track of your registration, please use the tracker's
web interface following the link below.
Do not reply directly, the registration process is not driven by e-mail, and
we will not receive such replies.
If you are willing to make the changes mentioned above, please provide us
with an URL to an updated tarball of your project.
Upon review, we will reconsider your project for inclusion in Savannah.
Regards.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/task/?func=detailitem&item_id=4862>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/