savannah-register-public
[Top][All Lists]
Advanced

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

[Savannah-register-public] [task #5574] Submission of wisp scripts for o


From: Steven Robson
Subject: [Savannah-register-public] [task #5574] Submission of wisp scripts for open source data mining
Date: Tue, 23 May 2006 23:06:03 +0000
User-agent: Mozilla/5.0 (compatible; Konqueror/3.5) KHTML/3.5.2 (like Gecko)

Update of task #5574 (project administration):

                  Status:                    None => Need Info              
             Assigned to:                    None => stevenr                

    _______________________________________________________

Follow-up Comment #1:

Hi,

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


Savannah's mission is to host free software projects, and we want the public
to think of them as free software projects.  A project name that says "open"
will tend to lead people to think of the project as "open source" instead of
"free software".

We would be glad if you accept to use "free" instead of "open" in your
project name.


Also, we need a detailed technical description that specifies such
requirements as programming languages and external libraries.  It should be
at least one-half a page.


Finally, 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 copyrightable file, usually any file more than 10
lines long.
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.


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.

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.

Regards.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/task/?func=detailitem&item_id=5574>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/





reply via email to

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