On Tue, 2005-05-03 at 06:47, Lars Magne Ingebrigtsen wrote: > I wonder if adding a layer of indirection here would help with these > considerations. > > That is -- Mailman could have a box saying "archive using external > archivers" (without saying which external archivers) that list admins > could tick/untick that resulted in a message being sent to a > meta-archival site. This meta-archival site would then have a list of > external archivers that be notified about the mailing list. > > This meta-archive would be run by a third party, and would de-list > any archivers that are naughty.
My idea of having a framework in Mailman wouldn't preclude this, and it would give list owners the option of picking a specific archiver (because of compliance with whatever policies they care about), or just let the meta-archiver choose. -Barry
signature.asc
Description: This is a digitally signed message part
_______________________________________________ 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-users%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
