From: Bruce Momjian <bruce@momjian.us>
Message-Id: <200803241554.m2OFscI17468@momjian.us>
Subject: Re: New email list for emergency communications
In-Reply-To: <20080324085326.62056486@commandprompt.com>
To: "Joshua D. Drake" <jd@commandprompt.com>
Date: Mon, 24 Mar 2008 11:54:38 -0400 (EDT)
CC: "Marc G. Fournier" <scrappy@hub.org>,
	PostgreSQL www <pgsql-www@postgresql.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"

Joshua D. Drake wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Mon, 24 Mar 2008 11:47:20 -0400 (EDT)
> Bruce Momjian <bruce@momjian.us> wrote:
> 
> > > For how often it happens, its worth nothing: I agree 100% with
> > > Joshua here, but, if Bruce wants to create a list on his personal
> > > domain (which, in itself is a failure point as it requires that
> > > *his* domain is not 100% perfect), it doesn't mean that anyone
> > > actually has to *use* it ... I know I never will, since there
> > > already exist faster, more reliable, contact methods ...
> > 
> > I think we need a more centralized contact system than we have now. 
> > Personally when I don't get email I am unsure who to contact (because
> > community email is down).  The email list was a method to centralize
> > that.  The list of possible contact methods listed confirms my point.
> 
> This comes back to defining teams which is already being discussed in
> another thread. The people that need to be contacted are the sysadmins
> team but we need to know how. Right now, the only people that know how
> to get a hold of the sysadmins team, is the sysadmins team :P. 

My big point is if the sysadmins team is hosted by the postgresql.org
domain, how do we communicate with them when postgresql.org email is
down?

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +