Jo Rhett writes: > I'm here out of good will,
I believe you, but your posting style provides zero evidence for it. > trying to avoid the banning of Mailman from dozens of large ISPs. > This kind of response just makes me think I'm wasting my time. Well, yes, that's what we've been saying. The resources to do what you say is necessary are not currently available. As you've remarked yourself, 2.2 is dead in the water and 3.0 is a long time away. 2.1 gets a new release every so often with a few bug fixes, and this is only really possible because it's in pure maintenance mode -- feature changes are mostly rejected out of hand. Those aren't symptoms of a project flush with resources. The technical problem of backscatter has been acknowledged. From the posts to this thread, I conclude the Mailman community *at large* is at present unaware of the threat of banning. I gather that includes Mark but perhaps not Barry. On the other side, there are very few resources available, and for this kind of change there is special pressure on the translators; no one of us can do it alone. The question is where to get the resources. While it's not your responsibility to do it, it isn't anybody else's, either. Regards, _______________________________________________ Mailman-Developers mailing list Mailman-Developers@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-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
