From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/31545] New: Replacement for mailman2
Date: Sun, 24 Mar 2024 22:04:42 +0000 [thread overview]
Message-ID: <bug-31545-14326@http.sourceware.org/bugzilla/> (raw)
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.
reply other threads:[~2024-03-24 22:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-31545-14326@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).