-
Notifications
You must be signed in to change notification settings - Fork 0
Should we replace Mailman2 with an alternative? #3
Copy link
Copy link
Open
Labels
ask lugmastersBefore investing effort into developing this "issue" further, the lugmasters need to show interest.Before investing effort into developing this "issue" further, the lugmasters need to show interest.discussionThis is an option for the future, and needs weight from one or more of the lug adminsThis is an option for the future, and needs weight from one or more of the lug admins
Milestone
Description
Metadata
Metadata
Assignees
Labels
ask lugmastersBefore investing effort into developing this "issue" further, the lugmasters need to show interest.Before investing effort into developing this "issue" further, the lugmasters need to show interest.discussionThis is an option for the future, and needs weight from one or more of the lug adminsThis is an option for the future, and needs weight from one or more of the lug admins
Mailman3 has, I seem to recall, significant issues, and is far from "feature complete" compared to what we want.
An alternative I'm looking into is replacing Mailman2 with Discourse. I know that HacMan moved from Mailman2 to Discourse, and it's entirely possible to do this, including importing the full mbox files from the existing mailman instances. (Reason for looking at this)
Now, one criticism I've seen about even editing the mailman2 indexes is that quite often the indexes are referred to in external indexes. It's possible (although, to be fair, I don't know how much work it would entail) to set up redirect links to the discourse site for those links which would be "lost".
Perhaps one other alternative would be to offer the option to the lugs - migrate to Discourse, or stick with Mailman... but that then means maintaining two systems.