[Savannah-register-public] [task #6453] Submission of FIGS

[Stephan Peijnik]

Update of task #6453 (project administration):

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

    _______________________________________________________

Follow-up Comment #1:

Hi,
  
I'm evaluating the project you submitted for approval in Savannah. While
doing so I have noticed a few problems which are described below.

First of all I would like to let you know that I am sorry for the huge delay
you have been facing. If you do not want your project to be hosted at
Savannah anymore, please let me know.


Secondly, you must determine whether your project can run on a Free Software
Java suite (see http://www.gnu.org/software/java/ for more information).

We recommend you to test your project using GCJ and GNU Classpath, and ensure
that your Java code runs on this Free Software Java suite.

GCJ is the GNU Compiler for Java, part of the GCC (GNU Compiler Collection). 
The Classpath project aims to develop a free and portable implementation of
the Java API (the classes in the 'java' package).

More information is available at http://gcc.gnu.org/ and
http://www.gnu.org/software/classpath/ .

Also, some additional information, especially regarding the fact that neither
Java 1.4, 1.5 nor 1.6 have been released under the GNU GPL, is available at
http://savannah.gnu.org/maintenance/JavaIssues.

Please provide us with more information about this point.


Additionally, 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,

Stephan

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/task/?6453>

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