[Mailman-Developers] integrating changes into distribution

[Thomas Wouters]

On Fri, Feb 04, 2000 at 01:10:49PM -0500, Barry A. Warsaw wrote:
> 
> >>>>> "BB" == Bill Bumgarner <bbum@codefab.com> writes:

>     BB> For the Mailman-decode-mime-file-via-webdav modifications, I
>     BB> have a relatively significant set of addtions and patches to
>     BB> Mailman.

> I'd like to take a crack at integrating the i18n changes this
> weekend.  If that goes smoothly, your stuff is next on my list.

I'm curious about this... I've browsed through the decoding/webdav patches,
and it seems explicitly webdav. I understand that Bill needed webdav, and
has thus only worked on that, and I appreciate the effort (we might have
customers who want it, eventually ;) but I'm wondering if the patch can't be
split in two different elements; webdav archiving, and attachment-decoding,
and making them seperately configurable.

I do not care about installing and configuring webdav at the moment, our
setup can't handle it yet, but the automatic decoding of whatever
word-document or powerpoint presentation our (sometimes) braindead managers
post to our internal all-employees mailinglists, and placing it simply as a
seperate file in the mailing list archive is a _very_ attractive idea. Not
just to me, the rest of the sysadmin departement went 'ooh' and 'ahhh' when
I told them about this development ;) (Which made me feel quite good, I must
add. I still feel I have to 'prove' python and mailman to them.)

I have no problem with (re)writing that part of the code, of course, but I'd
prefer to wait until Bill's code is in the CVS tree (so that I know the
style/layout and general idea has been approved of ;)

Regards,
-- 
Thomas Wouters <thomas@xs4all.net>

Hi! I'm a .signature virus! copy me into your .signature file to help me spread!