[Mailman-Developers] Getting code in? (was: Storm based MemberAdaptor for Mailman)
andy.grover at gmail.com
Sun Aug 9 21:35:17 CEST 2009
On Sat, Aug 8, 2009 at 1:25 AM, Malveeka Tewari<malveeka at gmail.com> wrote:
> I am working on writing a storm based member adaptor for mailman so that the
> mailman membership data can be stored in a database instead of .pck files.
> The reason for choosing storm is that it provides an abstraction to use any
> underlying db language- either mysql, postgresql or sqllite.
Hi, I'm one of the GSOC mentors for Systers, all of whose students are
working on Mailman enhancements. Some of these (Like Malveeka's) would
be suitable for merging upstream, but the review and acceptance
process is not clear.
* Do people on this list regularly provide review of proposed
* Is there a set of people who explicitly ACK or NAK all proposed patches?
* Once reviewed, merging is via LP merge requests, right? Or does one
do the merge request and *then* get reviewed?
* More fundamentally, is Mailman currently accepting patches from
We have code to contribute. It's not perfect yet but we will make it
better. We need some Official Mailman participation or our
improvements will never make it out of our branch. Even a response of
"we're not interested in X, thanks" would be much superior to no
response at all.
Thanks -- Regards -- Andy
More information about the Mailman-Developers