[Savannah-hackers] Re: submission of java Content Creation System - savannah.gnu.org

[Mathieu Roy]

Hi,

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


address@hidden said:

> A package was submitted to savannah.gnu.org
> This mail was sent to address@hidden, address@hidden
> 
> Krystian Lewandowski <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: java Content Creation System
> System name: jccs
> Type: GNU
> 
> Description:
> This project called (jCCS) java Content Construction System - is 
> implementation of module based content creation depends on servlet api 2.3 
> (this is only one dependency). Working code depends on Context/Session 
> Listeners and HttpServletRequest to make appropriate actions - initialize 
> context/session for module or request a content from it.
> jCCS provides only a few classes Context/Session Listener, GenericServlet and 
> excpect developer to implement interfaces - User, Server Policy 
> (authorization, information about https server available), Module interface 
> of course, document layout interface. Also defines self request and response 
> classes (works as decorators for HttpServletRequest/Response) - implements 3 
> levels of acces to request/session/context parameters - local: for this class 
> only, package and global.
> 
> jCCS is compiling on servlet.jar and gnujaxp.jar (from paperclips gnu 
> project) - Debian Woody with \"free\" only packages set.
> 
> jCCS source code (alpha version) is available at 
> http://jccs.citan.net/cgi-bin/viewcvs.cgi/jccs (no Makefile version available 
> yet).

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