[Systers-dev] Mailman thread on MySQL Member Adaptor

[Malveeka Tewari]

Hi all

I am working on extending mailman to provide Single Sign On to other systers
accounts using Systers mailman subscription. I had started working on
patching mailman to have an OpenID enabled version of mailman but through
discussions on mailman and openID mailng lists, and as correctly pointed by
Jennifer that we first need to work on:

Converting our existing membership base that is stored in Mailman to be
stored in an object that is
1) More secure
2) Stored and accessed in a way that will be accessible to multiple
applications (including mailman) (preferably in Postgres), (and has the
potential to support a gui so Systers are able to change their UID/Pasword
options - future project)

This way we would be able to extract user authenication information from the
database in an abstracted manner w/o worrying about details of its
implementation in mailman. This would make our implementation modular,
independant and more scalable.

What we want is basically a membership adaptor (similar to the one Jennifer
has talked about int this mail)  in SQL orPOstgresql.

I believe Kanika and Andy are already working on using the Storm ORM to
handle the Systers Dlist functionality. I must admit that I am not very
experienced with databases and have very little knowledge of Storm ORM. So
the questions that I have may be naive but kindly bear.

I want to know that whether a SQL membership adaptor for handing user
authentication information would be built over the Storm ORM layer or can be
handled independantly - as another module?

What I understand from reading DlistUtils.py is that Mailing Lists form an
important entity based on which Subscribers/Threads and Messages are
defined. Even in the MySQL membership adaptor,  memebership is defined on
the basis of lists. (Users can subscribe to different lists using different
email addresses and have different passwords for different lists in
mailman). But I did not see Kanika talking about lists on
http://systers.org/systers-dev/doku.php/orm_database_abstraction. Are
Mailing lists (mlists) not going to altered with use of Storm?

As I said, I'm no expert of databases, I could be wrong in my understaning
and I apologize in advance for that. Maybe how mailing lists are handled by
Mailman is independant of Subscribers/threads etc.
Strom

As of now, I am planning to start writing a SQL membership adaptor. Since
the memebership adaptor relies heavily on how lists are handled (mlists), I
want to know if you plan to use the Storm ORM for database management of
lists? It'll be great to get feedback from people working on ORM.


Thanks
Malveeka











On Wed, May 27, 2009 at 10:46 PM, Jennifer Redman <jenred at gmail.com> wrote:

> http://www.mail-archive.com/mailman-developers@python.org/msg11122.html
> We actually want a SQL member adaptor not a MySQL member adaptor (we are
> running Postgres) but this may be helpful.
>
> Jen
>