public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: <overseers@sourceware.org>
Cc: Carlos O'Donell <carlos@redhat.com>, Florian Weimer <fweimer@redhat.com>
Subject: Re: Choice of distribution for new sourceware.org server?
Date: Thu, 06 Feb 2020 18:28:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.21.2002061819540.10443@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20200206060547.GA1868@cgf.cx>

On Thu, 6 Feb 2020, Christopher Faylor wrote:

> We talk about that every time we go through a system or OS upgrade.
> I've maintained a postfix/mailman system in the past so maybe those bits
> would swap back in.  I don't really relish the thought of trying to
> convert the ezmlm archives to something else but maybe it isn't a big
> deal.

mailman has its own issues.  mailman2 is written in Python 2 which is EOL 
(though <https://pagure.io/fesco/issue/2312> has someone saying they're 
working on a Python 3 port).  mailman3 is a complete rewrite and its web 
interface (subscription management and archives) has a huge pile of web 
application dependencies that are hard to ensure long term security 
support for on a stable distribution.

(mailman2's default archiver has its own issues - its email address 
munging renders patches to Texinfo documentation pretty unreadable, for 
example - but I don't think it's hard to link mailman, either 2 or 3, up 
to other archive software, such as the existing MHonArc setup.)

-- 
Joseph S. Myers
joseph@codesourcery.com

      parent reply	other threads:[~2020-02-06 18:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06  1:05 Carlos O'Donell
2020-02-06  1:30 ` Christopher Faylor
2020-02-06  1:34   ` Frank Ch. Eigler
2020-02-06  1:51     ` Carlos O'Donell
2020-02-06  2:02       ` Frank Ch. Eigler
2020-02-06  2:16         ` Carlos O'Donell
2020-02-06 14:49           ` Frank Ch. Eigler
2020-02-06 15:10             ` Carlos O'Donell
2020-02-06 15:19               ` Frank Ch. Eigler
2020-02-06 16:36                 ` Carlos O'Donell
2020-02-06 16:46                   ` Christopher Faylor
2020-02-06 16:49                   ` Frank Ch. Eigler
2020-02-06  1:45   ` Carlos O'Donell
2020-02-06  6:05     ` Christopher Faylor
2020-02-06 14:50       ` Carlos O'Donell
2020-02-06 15:11         ` Lukas Berk
2020-02-06 15:22           ` Carlos O'Donell
2020-02-06 15:20         ` Christopher Faylor
2020-02-06 17:05           ` Carlos O'Donell
2020-02-06 18:28       ` Joseph Myers [this message]

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=alpine.DEB.2.21.2002061819540.10443@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --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).