I think the question really is - is this list designed for *reporting* and confirming outages? Or is it designed for *diagnosing*/discussing/ troubleshooting outages?
I understood the former. It's called outages I want my outages pure and simple and not cut with possible outages "is teh interwebs broken, btw I can't print either" :) There's enough noise and html already I was considering giving up but the move to puck gave me hope it'll evolve into something useful to me. If it doesn't then no problem it's probably useful to someone else. regards brandon
On 24 Jun 2008, at 14:35, Brandon Butterworth wrote:
I think the question really is - is this list designed for *reporting* and confirming outages? Or is it designed for *diagnosing*/ discussing/ troubleshooting outages?
I understood the former. It's called outages I want my outages pure and simple and not cut with possible outages "is teh interwebs broken, btw I can't print either" :)
Whilst I appreciate that it's ironic that I'm adding to the noise I am about to say I would prefer not to see, I found this list most attractive and useful so far when it was nothing more than brief statements of things that were broken, with no analysis. Ideally (in my opinion) any analysis, troubleshooting, drawing of conclusions or other meta-chat would happen somewhere else where I couldn't see it. Joe
PROPOSAL: OUTAGE ALERT to all list members Include link to Wiki of someone wants to dig deeper Aaron D. Osgood Streamline Solutions L.L.C P.O. Box 6115 Falmouth, ME 04105 TEL: 207-781-5561 FAX: 207-781-8067 MOBILE: 207-831-5829 PAGE: 2078315829@vtext.com AOLIM: OzCom1 ICQ: 206889374 AOsgood@Streamline-Solutions.net Blog: http://streamlinesolutionsllc.blogspot.com/ http://www.streamline-solutions.net http://www.WMDaWARe.com Introducing Efficiency to Business since 1986. -----Original Message----- From: outages-bounces@isotf.org [mailto:outages-bounces@isotf.org] On Behalf Of Joe Abley Sent: Tuesday, June 24, 2008 2:40 PM To: Brandon Butterworth Cc: outages@isotf.org Subject: Re: [outages] List comment On 24 Jun 2008, at 14:35, Brandon Butterworth wrote:
I think the question really is - is this list designed for *reporting* and confirming outages? Or is it designed for *diagnosing*/ discussing/ troubleshooting outages?
I understood the former. It's called outages I want my outages pure and simple and not cut with possible outages "is teh interwebs broken, btw I can't print either" :)
Whilst I appreciate that it's ironic that I'm adding to the noise I am about to say I would prefer not to see, I found this list most attractive and useful so far when it was nothing more than brief statements of things that were broken, with no analysis. Ideally (in my opinion) any analysis, troubleshooting, drawing of conclusions or other meta-chat would happen somewhere else where I couldn't see it. Joe _______________________________________________ outages mailing list outages@isotf.org https://puck.nether.net/mailman/listinfo/outages
On Tue, Jun 24, 2008 at 02:40:21PM -0400, Joe Abley wrote:
Whilst I appreciate that it's ironic that I'm adding to the noise I am about to say I would prefer not to see, I found this list most attractive and useful so far when it was nothing more than brief statements of things that were broken, with no analysis. Ideally (in my opinion) any analysis, troubleshooting, drawing of conclusions or other meta-chat would happen somewhere else where I couldn't see it.
I agree. The only time I need this list is when I am out working a live webcast for JP Morgan as part of a contract crew and I don't have time to read email. I typically only check outages during my 12-14 hour shift so that I can tell my boss why some CEO can't see the presentation his CFO just made. I want the facts, naked and pure and above all, short.
On Tue, Jun 24, 2008 at 02:40:21PM -0400, Joe Abley wrote:
Whilst I appreciate that it's ironic that I'm adding to the noise I am about to say I would prefer not to see, I found this list most attractive and useful so far when it was nothing more than brief statements of things that were broken, with no analysis. Ideally (in my opinion) any analysis, troubleshooting, drawing of conclusions or other meta-chat would happen somewhere else where I couldn't see it.
Can we set up -discuss and mung the reply-to header on -notify to point to it? Cheers, -- jra -- Jay R. Ashworth Baylink jra@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com '87 e24 St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274 Those who cast the vote decide nothing. Those who count the vote decide everything. -- (Joseph Stalin)
I think the question really is - is this list designed for *reporting* and confirming outages? Or is it designed for *diagnosing*/discussing/ troubleshooting outages?
I like the discussion of any outage related issue, both reporting, confirming, and troubleshooting. Now the divulging into areas such as "who still uses ICQ/AIM" and why they should/should not/whether or not it's secure is way off base. -- WKH
participants (6)
-
Aaron D. Osgood -
Brandon Butterworth -
Dale Amon -
Jay R. Ashworth -
Joe Abley -
W. Kevin Hunt