All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <christian.brauner@ubuntu.com>
To: containers@lists.linux.dev,
	containers@lists.linux-foundation.org,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Containers Development List Migration
Date: Fri, 16 Apr 2021 13:00:30 +0200	[thread overview]
Message-ID: <20210416110030.2jwljvcpcuq2xao5@wittgenstein> (raw)

Hello everyone,

The good people running kernel.org have put a lot of effort into better
tooling for the kernel community. This covers handling patches for
maintainers and developers via the new b4 tool, archiving all our
mailing lists in the new public-inbox format, better spam filtering,
non-delayed delivery of patches. Part of these efforts is to ultimately
run all our kernel development mailing lists under the kernel.org
umbrella 
People interested in details can re-read the threads on [1] and
subscribe to the workflows mailing list at [2] or peruse the articles
published about this initiative on LWN.

In the coming time mailing lists will slowly start migrating to the new
lists.linux.dev domain run by the kernel community under the kernel.org
umbrella. Some details about the new lists can be found in the great
blogpost at [6].
The migration has already happened for a few lists (ksummit-discuss,
linux-staging, tools) others are in the process of doing so right now
and it will ultimately take on all the duties that vger (and others)
once fulfilled including lkml itself.

Last year I already asked Konstantin to start archiving the containers
development list through lore.kernel.org at [3] and sent out a
corresponding announcement to this list [4].

We will now initiate the move of the mailing list to

        containers@lists.linux.dev

Given the low-volume of this list the move is scheduled to happen on

        01 May 2021

Note, there is no need for you to do anything now.

The migration is coordinated with Konstantin Ryabitsev who leads this
effort (I'm sure most of you know him from his excellent blogposts on
tooling at [5].). Disruptions will be kept to a minimum.

# Steps on May 1:

  - We will switch the archives for lore.kernel.org/containers to be
    from the new list.
  - All existing subscribers of the old list will be subscribed to the
    new list.
  - Archiving will be enabled for the new list.
  - The list will show up at lists.linux.dev with details about
    subscription, unsubscription etc.
  - An autoresponder will be setup on the old list notifying anyone
    still posting there that the list has moved. The old list will
    likely stick around for a few months.

Konstantin will announce when the move has finished on May 1 with a mail
to the new list. Until May 1 I will send a few reminders about the
upcoming move with people Cced (as done in this mail) that have sent
patches in the last couple of weeks.

Thanks!
Christian

[1]: https://lore.kernel.org/workflows/
[2]: workflows@vger.kernel.org
[3]: https://lore.kernel.org/containers/
[4]: https://lists.linuxfoundation.org/pipermail/containers/2020-August/042030.html
[5]: https://people.kernel.org/monsieuricon/
[6]: https://people.kernel.org/monsieuricon/subspace-mailing-list-server
_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/containers

             reply	other threads:[~2021-04-16 11:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 11:00 Christian Brauner [this message]
2021-04-28 14:56 ` Containers Development List Migration Christian Brauner

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=20210416110030.2jwljvcpcuq2xao5@wittgenstein \
    --to=christian.brauner@ubuntu.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=containers@lists.linux.dev \
    --cc=konstantin@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.