-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sep 25, 2008, at 5:28 PM, Morgan Reed wrote:

     I'm currently looking at creating a fork of mailman to add
support for GPG encrypted mailing lists, however given that mailman is
a rather complex beast I'm having trouble figuring out where to start.

Can somebody direct me to a good structural overview of how all the
bits and pieces of mailman fit together?

There isn't a good architecture document, but there should be, probably captured in the code or on the wiki. Your best bet is to dig in and ask lots of questions here.

Mailman 3 is being developed pretty religiously using test-driven development and doctests, which are testable documentation -- but documentation first. It doesn't provide a good overview, but it does provide good documentation on the specific components. However, Mailman 3's architecture is different than Mailman 2.x in some significant ways. In some ways (e.g. the queue runners) it's very similar though.

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAkjdT5UACgkQ2YZpQepbvXFL6QCdHy0pMvbgY36uXZLchPZhLsJ7
sYkAn07sKK/QVLhQuw8h00nYedv0Pb0v
=etrq
-----END PGP SIGNATURE-----
_______________________________________________
Mailman-Developers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: 
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Reply via email to