ZMailman classes

Before we get much further into coding, I'd like to take a second and go 
over the current class hierarchy (ignoring the ZMMuserFolder for now):

ConfigManager:
  - Handles access to Mailman mm_cfg class
ListManager:
  - Abstract class for handling list management (creation, deleting, etc)
FormManager:
  - Handles access to management forms

MailmanFolder (inherits from Folder, ConfigManager, Listmanager):
  - Zope object providing a Folderish interface to ListManager.
ZMailList (inherits from Folder, FormManager):
  - Zope object representing a mailing list
Member (inherits from SimpleItem)
  - Zope object representing a mailing list member

Stephan, does this seem accurate?  It would nice to start adding doc 
strings to these.

Some comments:
- ConfigManager and even more so ListManager strike me as generally 
useful.  If we cleaned these up and removed the Zope-specific stuff 
perhaps these could be added to Mailman?  Barry?

- We need a consistent naming scheme.  The reason for calling it 
"ZMailList" is probably because there is already a "MailList" class. 
But then I think we should stick with that convention and have 
"ZMailmanFolder" and "ZMember".

- Hmm, thought I had another one, but it's gone now :)

-- Brent

-------------------------------------------------------------------------

"The programmer, like the poet, works only slightly removed from pure
  thought-stuff.  He builds his castles in the air, from air, creating
  by exertion of the imagination.  Few media of creation are so
  flexible, so easy to polish and rework, so readily capable of
  realizing grand conceptual structures."
                         -- Frederick Brooks, Jr., The Mythical Man Month