On Thu, 2020-09-17 at 09:07 -0700, Mark Sapiro wrote: > On 9/17/20 8:04 AM, Jim Popovitch via Mailman-Users wrote: > > On Thu, 2020-09-17 at 07:54 -0700, Mark Sapiro wrote: > > > 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. > > The EOL notices were clarified to mean "no new features" I committed to > continue to fix critical bugs and security issues going forward.
I can't say this enough, Thank you for clarifying that issue because it does mean a lot to a lot of people when it comes from you. > If Mailman 2.1 meets their needs now, why won't it continue to do so as > it is? (Aside: I still sometimes use Adobe Reader 9 for Linux on my > desktop even though it has been unsupported and unavailable from Adobe > for years.) That's kind of my point. mm2 works for me and my use, I'd much rather prefer to keep it working than to rip it out and replace it, including installed and maintaining a database, a framework, a new setup of custom admin scripts unique to my setup, etc. No one has sold me on mm3 yet. > > > 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. > > I'm not sure what the point of this is. According to > <https://www.mailop.org/about/>;, MAILOP is already on Mailman 3. They are not, (i'd guess most likely due to overly optimistic views on how easy a migration to mm3 would be, perhaps they needed a bigger server or had to hire a database guy, who really knows). What i do know is that, from a post yesterday, they are still using an old Mailman version: Date: Wed, 16 Sep 2020 08:37:43 -0500 Subject: Re: [mailop] Spam using bit.ly link shorteners, this time via Outlook X-BeenThere: mai...@mailop.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: For mail operators <mailop.mailop.org> I'd email Simon to ask why the discrepancy, but he's already alluded to it a few times on their list. Note: he originally planned to started moving mailop.org to mm3 last December, so he's had plenty of time. > It appears NANOG has only 3 public Mailman 2.1 lists and only one has > archives pre-dating MM 2.1 which could require attention before > importing to HyperKitty. So list migration via `mailman import21` and > `django-admin hyperkitty_import` should be straightforward. > > I guess you are saying that step 1, "First install Mailman 3" would be > the sticking point, but this is the same whether you are NANOG or > mail.python.org or tiny site with one list, and it has been accomplished > multiple times by multiple people. I've documented my experience at > <https://wiki.list.org/x/17891998>;. Brian's take is at > <https://wiki.list.org/x/17892066>;. > I've read both of those links in the past, and honestly that is good detail to have. What I was looking for in an "elevator pitch" is a 30 second statement on what benefit someone would have by moving to mm3. Given the time and effort (big or small) why should anyone move to mm3 if their mm2 installation still works and functions fine? There are people here saying "move to mm3 now!!, etc.", but what's the selling point? -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/
