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

[Sylvain Beucler]

Hi,

We did not get a response from you, so we deleted your project from
the pending queue.

If you would still like to have your project hosted at Savannah,
please register it again.

The re-registration URL found in our acknowledgment of your earlier
registration will direct you to the proper location where you can
re-register your project.

Regards,

-- 
Sylvain


On Thu, Aug 26, 2004 at 01:39:58PM +0200, Sylvain Beucler wrote:
> Hi,
> 
> I'm evaluating the project you submitted for approval in Savannah.
> 
> > Robert Butler <address@hidden> described the package as follows:
> > License: lgpl
> > Other License: 
> > Package: abyssx
> > System name: abyssx
> > Type: GNU
> > 
> > Description:
> > AbyssX is a lightweight ircd intended for use with specialized irc
> > networks that is robust, reliable, maintainable, stable, and secure
> > internet relay chat(irc) daemon for running on such networks..it
> > provides enough framework and structure to allow for modifications
> > to the server code without straining too heavily on ugly(or often
> > unneccessary) hacks of the main codebase.. abyssx provides many
> > useful, yet functional modesets, and customizations, and some tiny
> > hacks to the IRC protocol itself, when introducing Underworld v2.0,
> > a superset of u:line controls allow irc services to have a better
> > control over network activities than just standard u:lines by
> > implementing advanced channel formation, topic, channel ban, and
> > mode moderation abilities.
> > 
> > Other Software Required:
> > 
> > 
> > Other Comments:
> 
> Please reply and include an (temporary) URL pointing to the source
> code.  The description you gave when registering will not be read by
> the general public. If you are still concerned with privacy, however,
> you can forward the code to me by email.
> 
> We wish to review your source code, even if it is not functional, to
> catch potential legal issues early.  
> 
> For example, to release your program properly under the LGPL you must
> include a copyright notice and permission-to-copy statements at the
> beginning of every file of source code.  This is explained in
> http://www.gnu.org/licenses/gpl-howto.html.  Our review would help
> catch potential omissions such as these.