[Mailman-Developers] Informal "MEP" process, anyone? [was: PHP Wrappers?]

Joshua Ginsberg jag at fsf.org
Thu Nov 17 20:24:29 CET 2005

The MySQLMemberAdaptor you guys produced is quite good. IMHO, a final
version to be included in 2.2 branch should include:

1) Abstractions of SQL queries on a per list basis, i.e. I don't want to
necessarily have to use your schema. Your schema should be the default,
but I want to be able to override it to best integrate it into existing
user databases.

2) Ability to switch MemberAdaptors through the web interface as well as
configure SQL queries through the web interface.

But yeah, that's my pipe dream. I'd be happy to help hack some of that
out if that would be helpful.


On Thu, 2005-11-17 at 19:38 +0100, Fil wrote:
> > I'll admit I've been on the scene for only a few weeks, and I'd not like
> > to speak for fil or Kev Green, but the MySqlMemberAdaptor they developed
> > works fairly easily with the intended design of MemberAdaptor.  You are
> > spot on that they have a "works for me" flavor, and I look forward to more
> > MemberAdaptors coming out.
> Well, it currently has a "works *not* for me" flavor and I'd appreciate som
> help on the two outstanding bugs I still have (in my version, but I guess
> Kev's version has them too).
> 1) if the DB connection dies or fades away, ping() is never called. I
> suspect this is due to the fact that the function self._prodServerConnection
> is not called with parenthesis. However if I add the parenthesis, I get
> bumped by an error because the function ping() itself does not exist at this
> point.
> 2) There's an issue with the bounce daemon not properly calling the __init__
> sequence (or so it seems), and I get failures when I activate this daemon.
> In both cases, I'd appreciate feedback, a hint to documentation, plain tests
> or even a full patch :)
>                                      ***
> As for the main topic of this thread, I think the issues of building a
> developers' community are very similar in many projects. In brief, you need
> to be familiar with the code to enter the community, and at the same time
> you almost need to belong to the developers' community to (have the
> incentive to) get familiar with the code.
> This kind of loop  has plagued my main pet project for years, and we're
> trying to solve it by opening parts of the development, in two directions:
> 1) modular code (MemberAdaptors are a good idea, in this sense)
> 2) a common and open development platform for modules (imho SourceForge sucks)
>    where people test each other's patches and cooperate a lot.
> -- Fil
> _______________________________________________
> Mailman-Developers mailing list
> Mailman-Developers at python.org
> http://mail.python.org/mailman/listinfo/mailman-developers
> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/jag%40fsf.org
> Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Joshua Ginsberg <jag at fsf.org>
Free Software Foundation - Senior Systems Administrator
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://mail.python.org/pipermail/mailman-developers/attachments/20051117/462b425c/attachment.pgp

More information about the Mailman-Developers mailing list