public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Joshua D. Drake <[email protected]>
Cc: Marc G. Fournier <[email protected]>
Cc: PostgreSQL www <[email protected]>
Subject: Re: New email list for emergency communications
Date: Mon, 24 Mar 2008 11:54:38 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Joshua D. Drake wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Mon, 24 Mar 2008 11:47:20 -0400 (EDT)
> Bruce Momjian <[email protected]> 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  <[email protected]>        http://momjian.us
  EnterpriseDB                             http://postgres.enterprisedb.com

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

view thread (78+ 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]
  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