public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: stephano <stephano.cetola@linux.intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [edk2-announce] Mailing List Move Day Set: April 4th
Date: Mon, 25 Mar 2019 13:51:15 +0100	[thread overview]
Message-ID: <bd0f757d-1b8d-0602-101b-1242eed53135@redhat.com> (raw)
In-Reply-To: <f1423ef0-4200-0cb9-2a70-1f5eed96dca5@linux.intel.com>

Hi Stephano,

On 03/23/19 01:41, stephano wrote:
> I will be moving our mailing list from 01.org over to Groups.io as of
> April 4th. I will send out another warning 1 week before, and a final
> warning 1 day before the move.
> 
> On April 4th the edk2-devel@lists.01.org will begin to bounce emails and
> I will begin uploading the archive to Groups.io. I do not have an
> estimate from Groups.io on how long that archive upload will take.
> 
> To summarize: after April 4th 2019 you can *no longer send patches to
> edk2-devel@lists.01.org*. Please send all patches to:
> 
> devel@edk2.groups.io

Can you please confirm that the current mailing list archive URLs will
continue working? For example:

https://lists.01.org/pipermail/edk2-devel/2019-March/038114.html

It's fine if the archive will not be extended with new messages in the
future, and also if the old messages get uploaded in the new list
archive. However, the old links should continue working as well,
indefinitely (it will not require additional storage, just a bit of
additional bandwidth, as old messages are looked up).

Personally, when I provide archive links (in discussions, BZs, commit
messages etc), I tend to make sure that I include two links: one into
the master archive, and another (to the same message) into the
mail-archive.com archive. From these, I make sure that the 2nd one is
always a Message-ID-based URL. The benefit is that, even if
mail-archive.com disappears, people can construct new URLs to old
messages, from the old message-IDs that are captured in the old URLs --
assuming a new archive service exposes the old messages by message-ID again.

*However*, that's just me. Most people include just one link, and that's
into the current master archive. Those links make no sense outside of
the specific archive service. And, I suffer *to this day* from the fact
that GMANE had gone down in summer 2016, and a huge amount of old
references (into the GMANE archive) are now completely useless.

In brief, please preseve the archive at
<https://lists.01.org/pipermail/edk2-devel/>, albeit with locked down
content, indefinitely.

Thank you,
Laszlo

> 
> This new list requires 1 email approval before you can post, so please
> be patient as our moderators approve you all.
> 
> After April 4th, all announcements will come from:
> 
> announce@edk2.groups.io
> 
> This list only allows moderators to post, so please contact me if you
> have announcements.
> 
> As always, I welcome your comments and questions. Thank you for your
> patience while we work to improve the quality of our community.
> 
> Cheers,
> Stephano
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel



  reply	other threads:[~2019-03-25 12:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-23  0:41 [edk2-announce] Mailing List Move Day Set: April 4th stephano
2019-03-25 12:51 ` Laszlo Ersek [this message]
2019-03-25 16:21   ` stephano
2019-03-25 22:21     ` Rebecca Cran
2019-03-26 12:07       ` Laszlo Ersek

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-list 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=bd0f757d-1b8d-0602-101b-1242eed53135@redhat.com \
    --to=devel@edk2.groups.io \
    /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