On 8/26/20 7:20 PM, Carl Zwanzig wrote:
On 8/26/2020 3:50 PM, Brian Carpenter wrote:
On 8/26/20 6:25 PM, Carl Zwanzig wrote:
So they will not notice a migration to Mailman 3 at all then.
You miss the point- _I'll_ notice, I'm the one who'd be doing the work.
Well, I am sorry to suggest there be some work to be done in a migration.
Also, from
https://docs.mailman3.org/en/latest/pre-installation-guide.html
"The short version is that as of now, upgrading from Mailman 2.1 to
Mailman 3.1 is buggy."
I am pretty sure that documentation is old. Here is a quote from the
above page:
[...]
Old? You've quoted the next paragraph on the same page.
So? I did that to prove that the document was outdated. That's all.
And why would I use linux when I have FreeBSD? :)
That is good as long as no major "DMARC" events come along. Nobody is
complaining that folks are using MM2. But I am seeing some complaints
pointed at the MM developers for no longer willing to develop MM2.
That's a completely separate topic and you'll have noticed that I'm
not one of the complainers.
See, the problem here is, the developers did develop and improve the
Mailman project, its just now called Mailman 3. So embrace and respect
their hard work and move your dang lists to Mailman 3!
When I get to it, maybe in 2022.
Ok. But that then goes against your original premise. MM2 isn't broke so
why move from it. Ever.
The thing is- no matter how much you may want people to "upgrade",
there just aren't sufficient reasons for potentially a lot of small
list operators. Perhaps I'm a luddite- I drive a 15 year old car
because it works, most of my home systems are 5+ years old because
they work and are plenty fast for the load, I use a 18? year old
Brother printer because it works, etc. When one of them stops working
it'll get replaced (if I can't repair it). There is little reason to
replace things that still function as much as one needs.
Ok. Except this isn't about just list operators, or moderators, but also
list members. There are a lot of roles involved here. Mailman 3 is the
future. That REST api is awesome. It allowed me to do things with
Mailman 3 that just wasn't possible with Mailman 2. I think some of the
criticisms is really directed at Postorius/Hyperkitty and not Mailman 3
core. The thing about those interfaces is they too can be improved
continually, and due to the use of Python 3 and modern web development,
have far more potential to make the lives of list owners, moderators,
and members more easier and productive. You are not going to see that
with Mailman 2. You like using antiques? Ok, go for it.
I heartily agree. Developers move on all the time and sometimes others
pick up the codebase and run with it. Embrace that.
Nope. I am going with improving the quality of life for list owners,
moderators, and members by embracing Mailman 3 and its REST api.
--
Please let me know if you need further assistance.
Thank you for your business. We appreciate our clients.
Brian Carpenter
EMWD.com
--
EMWD's Knowledgebase:
https://clientarea.emwd.com/index.php/knowledgebase
EMWD's Community Forums
http://discourse.emwd.com/
------------------------------------------------------
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/
