My director has finally agreed to let us open up our listserv to
hosting lists (besides computer-service-owned lists) around campus.
 
BUT, he first wants:
 
   "rules"     for list owners about what kind of lists can be hosted
               and what kind of things are their job and what are my job.
               (I installed the listserv, and serve as techrep and postmast).
 
   "class"     An outline of what sort of training will be required for
               list owners, and an estimate of how much time we will
               need to support and train a list owner.
 
   "resources" An estimate of how much disk space, etc these lists will
               require.
 
Rules aren't a great problem, but if someone has a set drawn up, I'd
love to see them.
 
Training is sort of a problem, because we have some VERY experienced
bitnet users who I would love to have as list owners despite the fact
they have NO training, and I have some highly trained people who are
begging to host lists, and would be absolute nightmares to support
because they just simply don't know what they are doing.  We need a
formal way of classifying who is a bumbling idiot and who would catch on
quick and be a great list owner with a little training.  I can't just
say "no, you can't have a list because you're impossible to train".
 
Resources are a major problem.  The boss wants an estimate, which is
absolutely impossible to do since I don't know yet whether the lists are
going to be STREK-L (150+ messages a day) monsters, or CRYPTO-L (I think
I've got 1 message a month there) crawlers.  And yet I can understand
him wanting to know how much traffic the "average" list has.  Any ideas?
 
 
 /++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\
!  Later        +   Systems Programmer                                 !
!  Gary Warner  +   Samford University Computer Services               !
!               +   II TIMOTHY 2:15                                    !
 \+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++/