* [Bug Infrastructure/31545] New: Replacement for mailman2
@ 2024-03-24 22:04 mark at klomp dot org
0 siblings, 0 replies; only message in thread
From: mark at klomp dot org @ 2024-03-24 22:04 UTC (permalink / raw)
To: overseers
https://sourceware.org/bugzilla/show_bug.cgi?id=31545
Bug ID: 31545
Summary: Replacement for mailman2
Product: sourceware
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: Infrastructure
Assignee: overseers at sourceware dot org
Reporter: mark at klomp dot org
Target Milestone: ---
In general we have to think about how we are going to replace
mailman2. It is based on python2. Both aren't maintained anymore. We
are doing fine because lots of others organizations are also still use it.
And we managed to get all the changes we need into the RHEL mailman2
package. So it will still be supported for some time.
There isn't yet a direct replacement with all the same features.
The most likely alternatives are mailman2 and mlmmj.
mailman3 https://list.org/ seems more a user forum (with django account
management) than a mailinglist. The archiver is pluggable.
mlmmj seems under active development, but you have to know where
to look https://codeberg.org/mlmmj/mlmmj/issues/3
We need a prototype setup and a migration path. An idea which
features can and cannot be supported. And confidence that future
email "issues" like dkim, dmarc, single-click unsubscribe, arc,
etc. can and will be supported.
inbox.sourceware.org seems a superior mailinglist archive setup.
But there might be things missing that pipermail offers?
Maybe it needs a pipermail http like "skin"?
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2024-03-24 22:04 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-03-24 22:04 [Bug Infrastructure/31545] New: Replacement for mailman2 mark at klomp dot org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).