RE: [NeoStats-Devel] NeoStats 3 Alpha

> Since Alpha 2 was released in March (3 months ago to the 
> day), and the new
> socket code is in, OPSB updated, and blsb available for the 
> blacklists. is
> there anything else holding up a Alpha 3 release ? I've just 
> about finished
> a Project I've been working on so hopefully will have more 
> time real soon.
> to help out with what's left to do before Alpha 3 where I can.
> 

I just committed some updates to OPSB, BLSB and SecureServ now, but noticed
that the akill etc type code is "work in progress"... I'm not sure what Mark
is doing here, I re-enabled some of it just to test the modules and it seems
to work ok, but Mark might have other work planned for it. 

I need to update some backend code on the secure.irc-chat.net site to
support new message formats from SecureServ (and now OPSB) though, which I
started on today already, but might take me a few days. 

The only other thing that I am aware of is to finish the conversion from the
existing config file to the new confuse library/format, but I doubt that is
something that will hold up a release. 

> Also I'm not sure if an email I sent actually made it to the 
> list, I have
> created a ProfileServ for Registered nicks to be able to add 
> information
> about themselves for others to view. it works completely from 
> the DB so the
> only time it really uses any resources is if user modes 
> change (to check
> registered status for expiring old records), expiring old records, or
> someone issues it a command (apart from normal resources just 
> sitting). 

This sounds cool. Have you ever used the new Magik Services? One thing that
was cool about that was it also allowed you to upload your pic to it. I
thought that was a funky feature that would be cool to implement into
NeoStats and was thinking about tackling some DCC Send code eventually.


if
> its better off being released by itself then it would need a 
> SVN repo set up
> to commit it to. although if the Games modules get released 
> as a Games Pack,
> it might be worth having a Vanity (or other name) Pack, which 
> could include
> SeenServ, ProfileServ, possibly LogServ, and any others that 
> fit into the
> same type of category.
> 


I guess anything goes as far as packages while we are in alpha, so if you
want, I'll just create a new repo, and you can commit to that. At release
time, we might have to look at how the development moves on these new
modules (eg, bugfixes to one module means that the whole pack has to be
released?)