[kwlug-disc] Service resource management: i.e. Mailman3 vs Mailman2

[Ronald Barnes]

Chris Frey wrote on 2025-01-30 10:43:

> Are there any killer features in MM3 that warrant all this bloat?

Perhaps.

There are some really nice features geared towards large lists like 
Python's, some that are nice for any list.


1) built-in archive search
	Ever search something, land in a list archive and
	try to navigate that? It's terrible.

2) reply to messages in the archive
	If someone joins a list and finds some message
	relevant to them from before they joined, they
	can reply in browser

3) up/down voting messages in browser
	Can help users evaluate messages - if anyone uses this

4) a *much* nicer interface for management of list / users

5) a user can have multiple email addresses
	They can be subscribed to different lists
	I'm not experienced enough to know much about this

6) fewer commands to interact with list via email
	Some would consider this a negative

7) full-text indexing of messages
	Related to #1, making searching pretty effective


Making all these parts work together ... kinda hard. For me, anyway.

I'd forgotten how I set up mailman v2 and so many new parts (Django, 
gunicorn, Hyperkitty, Postorius,...) that it was so confusing.  That 
might be a "me" problem.