On Thu, 2020-09-17 at 07:13 -0700, Mark Sapiro wrote:
On 9/17/20 6:54 AM, Matthew Pounsett wrote:
If someone was going to undertake a rewrite of Postorius, using a different web development framework (e.g. Flask, but pretty much anything that isn't Django) would at least remove one major moving part from the install process.
I have said multiple times that Postorius and HyperKitty are just examples and are part of Mailman 3 because we need something and that's what we've got, and also that efforts to port Mailman 2.1 to Python 3 or add new features to Mailman 2.1 would be better spent building a lightweight (e.g. Flask based) web UI to manage Mailman 3 via its REST API.
Would it though? Is that conjecture or based on available data that can be analyzed? Here's my POV, if mm2 can (and it appears to me that it can somewhat easily) be fixed to use py3 then all the installed bases of mm2 don't have to learn/deal/secure/test/manage/deal with a REST API and/or Flask, etc. All those current mm2 admins get to continue life as they normally do. They save a weekend (or a month in some cases) and some even save some $$, by not having to significantly change their Mailman installation or server size, etc. What I'm trying to do is provide a painless (or, at least a less painful) path forward for all those existing Mailman sites that don't want to deal with all the same issues that are appearing over on the MM3-users list and in #mailman.
-Jim P.