On Wed, Apr 4, 2012 at 2:58 AM, Toshio Kuratomi wrote: > I don't think you're going to find the will to make this sort of decision > right at this instant because what we want the archiver ecosystem to look > like for mailman3 is somewhat in the air. Do we really want an obviously > less capable archiver to be the bundled archiver? Do we want to have > a single blessed archiver (probably in a separate tarball as postorius, the > admin web ui, is separate) as an eventual goal? Do we want (at least for > a year or two) to let people go to town with their new ideas for archivers > and then see if a best-of-breed archiver is raising its head? I don't > believe any of this is decided inside of our minds yet, so, for now, people > are defaulting to wait and see.
I think it would be a mistake to bundle any archiver with mailman3. Listing the available archiver options and their features and shortcomings would be a better way to go. -- bye, pabs http://wiki.debian.org/PaulWise _______________________________________________ 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
