savannah-hackers
[Top][All Lists]
Advanced

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

[Savannah-hackers] Re: submission of Asynuxconges - savannah.gnu.org


From: Mathieu Roy
Subject: [Savannah-hackers] Re: submission of Asynuxconges - savannah.gnu.org
Date: 14 Feb 2003 19:30:45 +0100
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.gnu.org
> This mail was sent to address@hidden, address@hidden
> 
> Couillard Pascal <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: Asynuxconges
> System name: asynuxconges
> Type: GNU
> 
> Description:
> Hi,
> 
> Asynuxconges is based upon :
> - php scripts
> - MySQL dabase
> 
> Source code is available here : http://www.asynux.fr/Asynux/f0014/s0001
> - Asynuxconges-V.0.9.0.tgz, Asynuxconges-V.0.9.0.zip

Note that links are broken: 
   http://tokyo.asyres.fr:8080/Asynux/f0014/s0001/Asynuxconges-V.0.9.0.tgz
 is shown instead of 
   http://www.asynux.fr/Asynux/f0014/s0001/Asynuxconges-V.0.9.0.tgz
 which actually work.



In order to release your project under the GPL you
should write 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). Copy it for instance
into a file named COPYING.

Please follow the advice of http://www.gnu.org/licenses/gpl-howto.html

The GPL FAQ can also help you understand the reason behind
thoses 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

> same contents : sources, README, INSTALL, COPYING, database
> structure SQL file.
> 
> - Asynuxconges-V.0.9.0.pdf 
> User Manual
> 
> Briefly, this web application is used in our society by employees. They ask 
> for days off (holidays, authorized abscences ...) via web browser. Then their 
> requests  enter a tiny validation workflow. (Mail can be associated with the 
> request).
> 
> It is very tied to french uses (\"famous\" 35 hours : RTT) and unfortunately, 
> at the beginning of the developpement process we didn\'t anticipate english 
> translation issue.    


I noticed. At least, you should maybe split the name Asynuxconges in two
words as Asynux Conges. I didn't catch at first the name meaning,
despite that I'm french :)


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
 
 << Profile  << http://savannah.gnu.org/users/yeupou <<
 >> Homepage >> http://yeupou.coleumes.org           >>
 << GPG Key  << http://stock.coleumes.org/gpg        <<




reply via email to

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