nanog mailing list archives

Re: We're Back! Outages mailing is now open!


From: Andy Ringsmuth via NANOG <nanog () lists nanog org>
Date: Wed, 14 May 2025 08:58:26 -0500

On May 14, 2025, at 8:32 AM, virendra rode via NANOG <nanog () lists nanog org> wrote:

On Wed, 2025-05-14 at 11:51 +0200, Bill Woodcock via NANOG wrote:


On May 14, 2025, at 08:16, Andrew Latham via NANOG
<nanog () lists nanog org> wrote:
And outages-discussion () outages org is there also!

Yes.  Virendra, correct me if I’m wrong, but I believe that the
intention is for people to post _new_ outage notifications to
outages () outages org, but that _replies to_ and discussion of those go
to outages-discussion () outages org.  So, if you want to follow and
participate in discussion of the outage events, subscribe to both
lists.  If you’re just interested in seeing new events, but not
ongoing discussion of them (or if you’re using automation to track
events) just subscribe to outages () outages org and you should see a
much higher signal-to-noise ratio (addressing the many requests for
this over the years).

                                -Bill
---------
Initially, the intention was for replies to be directed to outages-
discussion@. However, they are currently being directed to outages@. I
have updated the footer to remind everyone that post post discussion
replies should be directed to outages-discussion@

Will monitor to see how this plays out.

/vrode


I personally would STRONGLY advocate for setting the default reply-to: for outages@ to go to -discussion. This has been 
an issue that plagued the old outages list for years and never got better. It actually got worse over time. A brand new 
list seems like a great time to change this behavior, at least to me.

Aside from that, thanks for the work behind the scenes to get things up and running again.



----
Andy Ringsmuth
andy () andyring com

_______________________________________________
NANOG mailing list 
https://lists.nanog.org/archives/list/nanog () lists nanog org/message/27XBWXVURNOUSNW5NB273X4WON2HKFDR/

Current thread: