Re: [Mailman-Developers] Parsing and Rendering rfc2822

2006-07-06 Thread Brad Knowles
Ethan quoted John Dennis: It's not at all clear to me that mailman should be responsible for archiving. While I am somewhat in agreement, the current situation is that archiving comes bundled with mailman and represents a significant weakness in its current web UI. Not doing anything about

Re: [Mailman-Developers] Parsing and Rendering rfc2822

2006-07-06 Thread John Dennis
On Thu, 2006-07-06 at 13:45 -0400, Brad Knowles wrote: [ snip discussion of fixing pipermail and alternate archivers ] But this is a pretty big undertaking. I'm 100% with Brad on this, this is a huge chunk of work, probably a project in its own regard. Would you really finish this during

Re: [Mailman-Developers] Parsing and Rendering rfc2822

2006-07-06 Thread John Dennis
On Thu, 2006-07-06 at 14:17 -0400, John Dennis wrote: ... don't forget for those folks who dislike pipermail one can with minimal effort use an external archiver. Oh, and I should have added that one of the beefs with using an external archiver is the disjoint UI between mailman and the

Re: [Mailman-Developers] Parsing and Rendering rfc2822

2006-07-05 Thread emf
John Dennis wrote: It's not at all clear to me that mailman should be responsible for archiving. While I am somewhat in agreement, the current situation is that archiving comes bundled with mailman and represents a significant weakness in its current web UI. Not doing anything about the web

Re: [Mailman-Developers] Parsing and Rendering rfc2822

2006-07-05 Thread Barry Warsaw
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jul 5, 2006, at 6:37 PM, emf wrote: I seem to recall this is also Barry's preference who noted the existing pipermail was only a stop-gap solution so there would be some default archiver, but it was never the intention Mailman would have