On Thu, 2020-09-17 at 07:54 -0700, Mark Sapiro wrote: > On 9/17/20 7:36 AM, Jim Popovitch via Mailman-Users wrote: > > 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. > > Or they can just continue to use Mailman 2.1 with Python 2.7, and no one > needs to do anything. > > > > 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. > > Forward to where?
Oh the irony of you asking that question. :) If we go back a year, there were STARK warnings about the EOL of mm2. Blatant EOL warnings. To me, a "path forward" is a way past that, a continued L(ife) with something that people know, and something that meets their needs. Flipping the coin around, make the actual written case, an "elevator pitch" if you will, for some entity like NANOG or MAILOP to migrate to mm3 this weekend. Let's see what that looks like. -Jim P. ------------------------------------------------------ Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
