public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: "Frank Ch. Eigler" <fche@redhat.com>,
	Sourceware Overseers <overseers@sourceware.org>
Subject: Re: sourceware hardware transition plan, part 1/N
Date: Wed, 12 Sep 2012 17:09:00 -0000	[thread overview]
Message-ID: <20120912170900.GA26605@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20120912160935.GE22100@redhat.com>

On Wed, Sep 12, 2012 at 12:09:35PM -0400, Frank Ch. Eigler wrote:
>> Should we rsync stuff over and then start working on a ezmlm->mailman
>> translation?  We'll also likely need to do a lot of work to keep URLs
>> correct.
>
>(My original thought was that the existing mhonarc archives would be
>preserved, so existing URLs would stay valid; just new archives would
>go to a new http url hierarchy.)

Ah, that would be easier.  So we just have an "old" archive which
preserves the old ml and a "new" one.

So, would it make sense to populate the new archive with old content too
just for consistency?  We'd have duplicate content but it seems like it
would be less confusing to end users.

>> Do we REALLY want to move from ezmlm?  Isn't there an rpm-based package
>> out there somewhere that we could use?
>
>Well, dunno.  ezmlm is not the worst thing about old sourceware; if
>others are content, we could keep it awhile longer.  The mediawiki
>transition could also be done later, on-line.

I chatted with Ian about this on irc.  The problem with ezmlm and qmail
is that they are not maintained and, so, are unaware of new standards
like DKIM.

If we think we will have to at some point then I think we should pull
the band-aid off now.  Or, alternatively, commit to supporting both
packages ourselves.

cgf

  reply	other threads:[~2012-09-12 17:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07 21:47 Frank Ch. Eigler
2012-09-07 22:47 ` Joseph S. Myers
2012-09-08 12:23   ` Frank Ch. Eigler
2012-09-08 13:19     ` Joseph S. Myers
2012-10-28 22:44     ` Gerald Pfeifer
2012-11-03 17:31       ` Daniel Berlin
2012-09-07 23:55 ` Jonathan Larmour
2012-09-10 17:32   ` Angela Marie Thomas
2012-09-10 17:57     ` Frank Ch. Eigler
2012-09-10 19:01       ` Christopher Faylor
2012-09-10 20:18         ` Angela Marie Thomas
2012-09-12 15:29           ` Frank Ch. Eigler
2012-09-12 15:37             ` Christopher Faylor
2012-09-12 15:51               ` Christopher Faylor
2012-09-12 15:59               ` Joseph S. Myers
2012-09-12 16:20                 ` Jeff Law
2012-09-12 16:29                   ` Joseph S. Myers
2012-09-12 16:09               ` Frank Ch. Eigler
2012-09-12 17:09                 ` Christopher Faylor [this message]
2012-09-12 20:48                   ` Joseph S. Myers
2012-09-13  3:18                     ` Christopher Faylor
2012-09-13  3:59                       ` Ian Lance Taylor
2012-09-07 23:59 ` Christopher Faylor

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=20120912170900.GA26605@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=fche@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).