[Savannah-hackers] Re: submission of Colibri conference manager - savannah.nongnu.org

[Mathieu Roy]

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
> 
> Alessandro Urpi <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: Colibri conference manager
> System name: colibri
> Type: non-GNU
> 
> Description:
> I\'m writing for the second time a paper submission manager for scientific 
> conferences. The first time I modified a tool called START, which (in version 
> 1) is distributed for free but has not a free license.
> This time I\'m writing it again in PHP, and I want to make a very small 
> program (not as big as cyberChair), absolutely portable and extremely 
> configurable.
> The first release will have an embedded simple (and unscaling) textual 
> database to keep authors/papers/reviews records, then I plan to add mySql 
> support as alternative.
> I\'d like to add a graphical web-based interface to configure a new 
> conference (insertion of name, place, and so on), in order for a conference 
> chair to put online the submission system in a few minutes.
> 
> I have a first unreleased and unlicensed code available at the URL

We cannot accept unlicensed code. Unlicensed code does not provide any
garanties to users about freedom. And it's an issue.

> 
>    http://www.di.unipi.it/~urpi/colibri/colibri.tar.bz2

In order to release your project under the GPL 
(for example) 
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


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