Re: [srvx-devel] srvx development directions meeting

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

Minutes for the meeting:

Next stable version tentatively called 1.1
We definitely want modules for 1.1; dependency support needs to be improved
Need to flag possible abuse better (e.g. !voice self, !addop self in god mode -- or disallow and make another staff do it)
#1, #2, #3 in 1.1, using Zoot's rule ACL stuff
DCC/bot support in 1.1
HelpServ is extremely positively received; it goes in, too
Renaming ChanServ access levels is delayed
Fisich notes that having OpServ and ChanServ semi-separate is important; running two instances of srvx is an acceptable solution
Extra channel information (notes, problem histories, etc.): new idea; put just a simple list of notes in 1.1, more stuff can wait
Per-<user,channel> flags for ChanServ: just for plain !togop
Better help files: Not really defined well, but should include things like task-based help entries
Entrope and/or SailorFrag will keep list of help file entries that need to be changed
Database journalling: defer (too hard)
Rule based auth: can also use it with ?trace, etc
Rules:
  being in channel N
  user mode matches +N-M
  opserv level at least N
  channel mode +M-P in channel N
  access level at least N in channel M
  handle flags +N-M
  hostmask M!N@P
  unauthed for duration N
  unvisited channel N for duration M
  handle name matches M
  true
  false

-- Entrope