On Dec 06, 2011, at 12:36 PM, Terri Oda wrote: >As a developer, this sounds the makings of one of those life-sucking projects >you shouldn't touch with a 10-foot pole unless you're getting paid to define >and defend a standard. There's no guarantee that anything we choose to do >will ever be considered correct, and it could wind up being a lot of arguing >and wasted effort at a time when I think we're better off just getting >mailman 3 out the door.
I agree completely. (he says, still struggling with REST authentication/authorization :). >Which is a pity, because this seems like a great opportunity for us to >trailblaze and help correct a mistaken assumption in DKIM. Maybe the other >developers are a lot more excited about that than I am and willing to take >the risk of implementation, but maybe we should just keep an eye on the >expansion of DKIM and revisit this issue after Mailman 3 is released? What Mailman 3, and to some lesser extent MM2 can do today, is to provide a framework for experimentation, for those folks who are motivated to improve the current situation. Fortunately, I think MM3 has everything you'd need to do that. A team working on improving things should be able to distribute a plug-in that implemented their experiment for sites that wanted to participate. -Barry _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org 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
