[srvx-devel] srvx-1.1 and srvx-2.0

[Entrope <en...@us...>]

(I have no idea if AfterNET is still interested in srvx or not.  If
not, somebody tell me, and I'll stop sending to the sr...@af...
list. :)

The current CVS HEAD for srvx (what we call -unstable) has been a
testing ground for a lot of next-generation features that would go
into srvx-2.0.  However, a lot of what we want is very awkward to do
in C, so we're probably going to end up rewriting it in C++ or C#.
And that will take time.

In the mean time, we plan on making a new fork from the current
srvx-1.0 tree (the srvx-1_0 tag) to work on a srvx-1.1, and release it
soonish.  Here's a list of what will be in 1.1 and what will only be
in 2.0 (we'll of course aim for 2.0 to have a strict superset of 1.1's
capabilities); the rough criteria were how much code it changes, and
whether it would be helped a lot by virtual functions:

IN SRVX-1.1
-----------
More restrictions on when/how "god mode" can be used
HelpServ (an automatic question queueing service)
Per-user flags in ChanServ
Additional notes for ChanServ (e.g. web page, staff notes on history;
  probably some will only be visible to staff)
Most of the stuff on the SourceForge feature request tracker
A few additional ChanServ commands (such as !giveownership)
Expanded proxy testing support (in particular, being able to match
  arbitrary length strings, so HTTP CONNECT proxies can be tested
  interactively)

SRVX-2.0 ONLY
-------------
Multiple protocol support
Multiple connection core (for DCC, IPC, etc.)
Dynamically loaded modules
"Pluggable" services (can assign commands to arbitrary service bots)
I18N (or at least translation of various strings)
Freeform aliasing
.. and most other wide-ranging changes

-- Entrope