Date: Tue, 28 Apr 2020 17:33:02 +0200 From: Matthias Andree <matthias.andree@gmx.de> To: Dan Langille <dan@langille.org>, Kurt Jaeger <pi@FreeBSD.org> Cc: freebsd-ports <freebsd-ports@freebsd.org> Subject: Re: mail/mailman v3? Message-ID: <1650e99c-8095-c4c0-07c1-988b40f33f76@gmx.de> In-Reply-To: <a7d09766-dacc-4a7f-bf08-ae6ddd34d794@www.fastmail.com> References: <FD5DA99A-4B99-4730-BD8E-7079416A56BB@langille.org> <20200424130424.GJ39563@home.opsec.eu> <E0A0D488-3FEC-48D8-9425-08432321719C@langille.org> <a7d09766-dacc-4a7f-bf08-ae6ddd34d794@www.fastmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 28.04.20 um 16:34 schrieb Dan Langille: > On Fri, Apr 24, 2020, at 9:32 AM, Dan Langille wrote: >>> On Apr 24, 2020, at 9:04 AM, Kurt Jaeger <pi@FreeBSD.org> wrote: >>> >>> Hi! >>> >>>> With mail/mailman being Python 2.7 (which is end-of-life), and mailma= n 3 being Python 3 compatible: >>>> >>>> Do you know of any plans to port Mailman 3? >>> >>> There's already a PR about that: >>> >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225543 >> >> Now 2 years old I see. Good start. >> >>> The patch itself is fine, but we need run-tests. >>> >>> This means: If you want to help, >>> - use that patch, >>> - build mailman3, >>> - and install it somewhere and >>> - test all the use-cases that you can think of >>> - then write some docs on how to move an existing mailman2 site >>> to mailman3 >> >> I'm guessing that's over and above what I found at: >> >> https://docs.mailman3.org/en/latest/migration.html >> >> >>> - and give ideas how to handle list archives >>> *especially* keeping the URLs identical (!) >> >> I think the existing archives are static HTML. I have some archives da= ting >> back to 1999: https://www.unixathome.org/adsl/ >> >> There might be some server-side rewrites or aliases to ensure that this >> URL always works, before and after mailman3: >> >> https://lists.freebsd.org/pipermail/freebsd-ports/2020-April/118352.htm= l <https://lists.freebsd.org/pipermail/freebsd-ports/2020-April/118352.htm= l> >> >> Let's compare 2 and 3 lists: >> >> https://mail.python.org/pipermail/mailman-users/ >> <https://mail.python.org/pipermail/mailman-users/>; >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ >> <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/>; >> >> They are distinct (ignoring the hostname differences) so keeping the >> old alongside the new should be safe. >> >>> And, speaking as one of the postmaster@ team: >>> As lists.freebsd.org uses mailman2, we need this! >>> >>> postmaster@ has not yet decided if we really want to move to mailman3, >>> so we are open to other options. The mail archive is the biggest hurdl= e 8-( >> >> Yes, we can't lose those. I have my own archives to support. > > I see the mailman lists themselves are now on Mailman 3: > > https://mail.python.org/archives/list/mailman-announce@python.org/thread= /HHQN7V6NY7G5CTOSC3WBU7VXW5KEBGVO/ > Just figured my earlier message did not make it to the public freebsd-ports list, I was using the wrong sender address. I will resend it= . However, I find that bears no relevance for the code itself whatsoever. It is good that they have finally started dogfooding their produce, but evidently it's limited to lists that can bear higher risk because there is less user interaction, and if so, from more technically versed audience (devel/announce).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1650e99c-8095-c4c0-07c1-988b40f33f76>