Re: Development Plan

Hi!

I see my main goals reached if we have a Zope-based user repository that can
be used by both Zope and Mailman. Something like the ultimate membership
module. With MM2.1., this seems to be a reachable goal.

I deliberately don't say ZODB, because I think a really sane architecture
will separate the storage issues for members and lists (which seem to be the
main objects to be concerned of) form the actual API. So we can use LDAP,
RDBMS, or even plain text files as data sources, like the Zope acl_user
folders do.

The member objects (holding member data, member credentials (password etc.),
member preferences) should work like extenden user folders from Zope. The
remaining question is:

Are we going to store the list memberships with the members or with the
lists? (What are plans for Mailman 2/3?) Or will there be a linking table
(which would be the SQL way of doing it)? Or will we have an API that
exposes methods like list.getAllMembers() to MailMan and leave the
implementation issues to the list and member storage modules?


----- Original Message -----
From: "Barry A. Warsaw" <[email protected]>
To: "Joachim Werner" <[email protected]>
Cc: "ZMailman Mailing List" <[email protected]>; "Stephan Richter"
<[email protected]>
Sent: Tuesday, December 04, 2001 10:33 PM
Subject: Re: [ZMailman] Development Plan


>
> >>>>> "JW" == Joachim Werner <[email protected]> writes:
>
>     JW> - I want to use ZMailman to handle sending mails to groups
>     JW> that are defined in Zope. E.g. we have a Zope-based extranet
>     JW> for a students organization, and they want to maintain mailing
>     JW> list that are automatically in synch with their user
>     JW> database. These mailing lists/groups are rather stable, but it
>     JW> is important that they don't have to maintain two lists.
>
> Doable in MM2.1.
>
>     JW> - It should be possible to create new objects in Zope (e.g. a
>     JW> project like in SourceForge) and automatically get a mailing
>     JW> list for it
>
> Doable in MM2.1
>
>     JW> - One very cool thing would be if ZMailman also could handle
>     JW> sending mails to lists that are temporary, e.g. results of a
>     JW> database query.
>
> Doable in MM2.1 (sort of).  The list must exist, but it can be a
> "virtual" list where you specify exactly the recipient list that you
> want to use, instead of the list's normal recipients.
>
> -Barry
>
>