savannah-hackers
[Top][All Lists]
Advanced

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

[Savannah-hackers] Re: submission of Rizen\'s IRC Bots - savannah.nongn


From: Mathieu Roy
Subject: [Savannah-hackers] Re: submission of Rizen\'s IRC Bots - savannah.nongnu.org
Date: 16 Jan 2003 14:59:33 +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.nongnu.org
> This mail was sent to address@hidden, address@hidden
> 
> Theodore Reed <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: Rizen\'s IRC Bots
> System name: ircbots
> Type: non-GNU
> 
> Description:
> A collection of the IRC bots I\'ve made throughout the past year or so. They 
> are written in Python, and include:
> 
>   - Rapebot: The eldest, a bot which collects and disperses quotations. (The 
> name comes from a joke about \"raping a quote\".)
>   - Logbot: A simple IRC logging bot.
>   - Arcobot: A game, which involves inventing meaning for randomly created 
> acronyms.
>   - Dicebot: Allows the simulation of dice-rolling (ie for RPGs).
> 
> There might later be others, or maybe one superbot that loads modules for 
> features.
> 
> Source code can be had at http://sf.net/projects/ircbots/

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

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]