Re: Member/Usermanagement

Hi!

I just want to suppor that use case:

We also have many scenarios where we want to have ONE user source (that can
come from LDAP, SQL, etc.) and want to make membership in a mailing list an
option for the members.

Actually the issue here is that we need a general Membership framework for
Zope, with MailMan mail lists just as one service, at least in the long run.

In such a framework, you'd actually separate the list management from the
e-mail address storage:

- There would be a centralized user source with "rich users" that have full
names and passwords attached to them. And maybe general options like "I want
to get notified by mail!" or "I want to only get notifications on my portal
homepage!"

- Every project has a recipients list. Depending on the project members and
the individual preference settings of the users, the actual mailing list is
generated

Stephan, do you remember our initial Proiektor plans? This is exactly what I
am talking about.

If I find the time, I will post some design stuff after christmas.

Joachim