savannah-hackers
[Top][All Lists]
Advanced

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

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


From: Mathieu Roy
Subject: [Savannah-hackers] Re: submission of mini3d - savannah.nongnu.org
Date: 16 Oct 2003 15:37:57 +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
> 
> Philippe COVAL <address@hidden> described the package as follows:
> License: lgpl
> Other License: 
> Package: mini3d
> System name: mini3d
> Type: non-GNU
> 
> Description:
> Mini3d is a set of basic tools for exporting/importing 3d mesh
> 
> This lib provide read/write 3d mesh in 3ds ascii format (.asc)
> 
> Also packaged sample utilities (basic viewers)
> 
> Other formats aim to be supported in the future.
> 
> Is is writen in C (no dependencies to other lib)
> 
> and can be compiled standalone as a library (libmini3d.a/.so)
> 
> or included inline. Java, C++, etc bindings are possible
> 
> Currently it is used in other GPL software :
> 
> http://pinball.sf.net
> 
> If you include in your own project,
> 
> I suggest you to copy and include files  :
> 
> extras/mimi3d/mini3d/mini3d.h
> 
> Project Home (temp) at :
> 
> http://www.philippe.coval.free.fr/tmp/mini3d/

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


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]