Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: bloat@lists.bufferbloat.net, cake@lists.bufferbloat.net,
	cerowrt-devel@lists.bufferbloat.net, codel@lists.bufferbloat.net,
	ecn-sane@lists.bufferbloat.net, libreqos@lists.bufferbloat.net,
	make-wifi-fast@lists.bufferbloat.net,
	nnagain@lists.bufferbloat.net, rpm@lists.bufferbloat.net,
	starlink@lists.bufferbloat.net
Subject: [NNagain] Migrating the Bufferbloat mailing lists
Date: Sun, 13 Jul 2025 18:47:49 +0200	[thread overview]
Message-ID: <87ms9811hm.fsf@toke.dk> (raw)

Hi folks

I am about to initiate a migration of the Bufferbloat mailing lists off
of Dave's old Linode server an onto my own mail server. In the process,
the list backend will be switched from the old Mailman2 instance to an
up to date Mailman3 installation, and the archive backend will be
switched to a public-inbox based archive.

The mailing lists in the To field of this email are the active lists
which will be migrated, and no action is necessary for you to continue
to be subscribed. All other lists currently hosted at
lists.bufferbloat.net will have their archives migrated for posterity,
but won't be setup to receive new email.

I am sending this email before initiating the migration. Once the mail
has been flushed from the mailing list queue, I will shut down the mail
server daemon on the old server, and initiate the archive and DNS
migration.

After the migration is complete, I will send another notification email
to let you all know the migration has been completed. Meaning that if
you receive this email, but not the follow-up notification, that could
indicate a delivery issue. In which case, please do let me know
(off-list!), but please allow a day or so for everything to flush out.

See you on the other side!

-Toke

                 reply	other threads:[~2025-07-13 16:47 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

  List information: https://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ms9811hm.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=libreqos@lists.bufferbloat.net \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=nnagain@lists.bufferbloat.net \
    --cc=rpm@lists.bufferbloat.net \
    --cc=starlink@lists.bufferbloat.net \
    /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