public inbox for [email protected]  

help / color / mirror / Atom feed

From: Joshua D. Drake <[email protected]>
To: Marc G. Fournier <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: Robert Treat <[email protected]>
Cc: [email protected]
Cc: Andreas 'ads' Scherbaum <[email protected]>
Subject: Re: New email list for emergency communications
Date: Tue, 25 Mar 2008 22:45:43 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

Marc G. Fournier wrote:

>> I have IRC ops too.  But I am really looking for something that notifies
>> me that there is a problem, rather than having me go looking for
>> information.  If email is down, people should be able to subscribe to
>> alerts and status reports.
> 
> 'k, I can guarantee you that if/when there is a problem, my focus is going to 
> be on *fixing* the problem, not sending out status messages to the effect of 
> "its still down" ...

Any reliable network infrastructure will have the ability for the users 
of that infrastructure to get a status update on a particular problem. I 
am able to do this even with my uber cheap DSL line. I call the status 
line when there is a problem and a nice little attendant says, "Yo... we 
know there is a problem in hood river, ETA to fix, 2 hours".

Do I think it is reasonable that Marc or anyone else start sending out 
status messages? No.

Do I think it is reasonable that when there is a problem that a ticket 
be created on pmt.postgresql.org that describes the problem, and when 
the problem is fixed (or if the problem is going to be longer term), 
that ticket be updated and closed? Yes.

We are either a network of professionals supporting an infrastructure, 
or were not.

Whether we like it or not, the moment we agreed to be on sysadmins@, 
postgresql.org became our customer. We should act like they are our 
customer and provide the relevant and appropriate customer 
communications. That means, tickets, updates, communication, and 
documentation.

Sincerely,

Joshua D. Drake

view thread (76+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: New email list for emergency communications
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox