head     1.1;
branch   1.1.1;
access   ;
symbols  INITIAL:1.1.1.1 TOLKIEN:1.1.1;
locks    ; strict;
comment  @# @;


1.1
date     2002.09.03.09.14.56;  author tolkien;  state Exp;
branches 1.1.1.1;
next     ;

1.1.1.1
date     2002.09.03.09.14.56;  author tolkien;  state Exp;
branches ;
next     ;


desc
@@



1.1
log
@Initial revision
@
text
@TODO:
- write help files for all the plugins that are included in the base
  distribution.
- the bot's own words are not logged.  they should be.  right now the
  only bot action that shows up in a bot's own logs is when it joins
  a channel.  public and action, and I guess part should get logged too.
- sprinkle more debugging output stuff around, particularly in the
  class modules (User.pm, Chan.pm, etc.) since there's not much
  there right now.  if a user uncovers a problem in there, the
  debugging output won't pinpoint it.
- implement user-defined formats for things like logfile names and
  logfile entries.  could use % codes, like %y.%m.%d for
  year.mon.day .
- Allow configuration of which events justify notifying the owners.
  Also, possibly allow owners to specify which types of notifications
  they do and don't want to get.
- make the User package more robust...
  - users should have more info that other users with the
    appropriate flags should be able to access, ie:
    real name, last seen, last unidle, email addy, daytime phone,
    home phone, real address, etc... anything one can think of that
    would be useful
    -- these have been added, but we really need an entirely new
       user config file and format...
  - this info should be able to be set by each individual user with
    as much or as little info as desired... this means we need to
    both parse and save out a seperate user config file


THOUGHTS:

- currently, users need to say '#help core ...' for help on the core stuff
  like part/join/note etc. (i.e. the stuff in PerlbotCore)  is this OK?

- we should make several classes that represent redirections.  one for
  channels, one for users, etc.  each channel would have a list of these
  objects, and to redir something it would just pass a user and a string
  to redir_obj->redir .
@


1.1.1.1
log
@initial from kang.sarang.net
@
text
@@
