Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id C0FCC2E0049 for ; Wed, 26 Mar 2008 02:45:57 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 76316-04 for ; Wed, 26 Mar 2008 02:45:54 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id CED5D2E007C for ; Wed, 26 Mar 2008 02:45:56 -0300 (ADT) Received: from [192.168.1.226] (or-69-34-217-90.sta.embarqhsd.net [69.34.217.90]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m2Q5kJRV005104 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Mar 2008 22:46:20 -0700 Message-ID: <47E9E307.7030504@commandprompt.com> Date: Tue, 25 Mar 2008 22:45:43 -0700 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: "Marc G. Fournier" CC: Bruce Momjian , Robert Treat , pgsql-www@postgresql.org, "Andreas 'ads' Scherbaum" Subject: Re: New email list for emergency communications References: <200803260159.m2Q1xta08068@momjian.us> <5CBE18B06DC0D9B5500FE767@ganymede.hub.org> In-Reply-To: <5CBE18B06DC0D9B5500FE767@ganymede.hub.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Tue, 25 Mar 2008 22:46:21 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/590 X-Sequence-Number: 14709 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