I'd like to add a +1 for multiple domain support as well. When I selected Mailman almost a year ago I remember this feature being on the 2.2 feature list... Developing software myself I fully understand how it has moved to 3.x.
At the same time, maybe a limit to what goes into 2.2 so that 3.x doesn't keep moving either ? In Service, Michael Kabot President - SOAR Scouting Online Affordable & Reliable [EMAIL PROTECTED] 585-388-0211 www.soarol.com | -----Original Message----- | From: [EMAIL PROTECTED] | [mailto:[EMAIL PROTECTED] On Behalf | Of Barry Warsaw | Sent: Monday, July 09, 2007 7:03 AM | To: David Lee | Cc: mailman-users@python.org | Subject: Re: [Mailman-Users] Mailman roadmap | | -----BEGIN PGP SIGNED MESSAGE----- | Hash: SHA1 | | On Jul 9, 2007, at 4:28 AM, David Lee wrote: | | > I would like to register a "+1" towards at least the beginnings of | > proper, | > multiple-domain support. No need at all for this to be the whole | > thing, | > but at least its basic foundations. Even just a hidden "own-risk" | > installation option of having the listnames (and references to them) | > internally stored and processed as "[EMAIL PROTECTED]" would | help. | | My suggestion would be to investigate some of the unofficial patches | that provide this, or look into using the Site.py hack for this. The | problem with putting something better (even as use-at-your-own-risk) | in 2.2 is that it's a fairly fundamental change to the architecture | of the system so it would require fairly extensive testing. That's | why I really want to defer this to 3.0. | | > What worries me about the "fixed in the Mailman 3 dev branch" is the | > timescale. You mention both that "2.1 is (shockingly) 4.5 years | > old", and | > that there is "no ETA for Mailman 3.0". | | Right. I'm not ready to commit to a schedule yet, but it's basically | all I'm working on right now. | | > So with such a basic, minimal foundation (for true multiple | > domains) in | > place, then those of us who would really like it a.s.a.p. in our | > service | > environments (i.e. not Mailman 3) would be able to contribute to | > building | > it, perhaps as a subproject (analogous to those you mention for | > "SQAlchemy/Elixir", archiver, "web u/i", etc.). | | You can do this now. Start an unofficial branch of Mailman 2.2, | publish it, and contribute some code. If you surprise me about the | scope of the changes necessary, we can consider it for 2.2 proper. | This would be an ideal test of the power of using Bazaar. If you're | interested in this, let's move the discussion over to mailman- | developers. | | > Anyway, thanks for your work over the years,and now on Mailman. It | is | > much appreciated! | | My pleasure! | - -Barry | | -----BEGIN PGP SIGNATURE----- | Version: GnuPG v1.4.7 (Darwin) | | iQCVAwUBRpIV/HEjvBPtnXfVAQLmdAP6A47uRwzcCBZ81Xao1OcoCjIPC+6c0sAd | wUtWPPzdkqp05sNAMQK3r22nH1d7ZRMVODhj01FcM/L+CGyRvH3tJtGT9WJOozIX | EeeehHPkZhS82nXWopPHE1y8J5DrgNrO0zujZZivOVufRN0ToqXSNGV8VYhn+jp6 | EuNq0FxAo+w= | =zdju | -----END PGP SIGNATURE----- | ------------------------------------------------------ | Mailman-Users mailing list | Mailman-Users@python.org | http://mail.python.org/mailman/listinfo/mailman-users | 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- | users/mkabot%40soarol.com | | Security Policy: http://www.python.org/cgi-bin/faqw- | mm.py?req=show&file=faq01.027.htp ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users 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-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp