public inbox for [email protected]  

help / color / mirror / Atom feed

From: Stefan Kaltenbrunner <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: Marc G. Fournier <[email protected]>
Cc: Joshua D. Drake <[email protected]>
Cc: PostgreSQL www <[email protected]>
Subject: Re: New email list for emergency communications
Date: Mon, 24 Mar 2008 17:53:22 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Bruce Momjian wrote:
> Marc G. Fournier wrote:
>>> I would like the requirements defined by the -www and sysadmins teams.
>>> I don't want us to go off and create yet more infrastructure without
>>> full documentation and understanding of the purpose and whether it is
>>> redundant.
>>>
>>> This list is currently redundant as we have the resources and
>>> technology already in place to deal with this. I think you are
>>> attacking the wrong problem Bruce.
>> 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.

the sysadmin team already maintains a list of emergency contacts 
including external email, phone numbers, alternative contacts in 
addition to the what we are usually using to communicate (IM,personal 
email, the lists) - not sure if we need to duplicate that ...




Stefan

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], [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