public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Tom Lane <[email protected]>
Cc: Marc G. Fournier <[email protected]>
Cc: Robert Treat <[email protected]>
Cc: [email protected]
Cc: Joshua D. Drake <[email protected]>
Cc: Stefan Kaltenbrunner <[email protected]>
Subject: Re: archives.postgresql.org not responding
Date: Sun, 22 Jun 2008 21:48:57 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Tom Lane wrote:
> "Marc G. Fournier" <[email protected]> writes:
> > If it involves web infrastructure (ie. archives.postgresql.org), it
> > should go to pgsql-www ... if it involves non-web infrastructure
> > (ie. ftp) it should go to sysadmins ...
> 
> Well, the point to me is that planned outages should be announced
> somewhere where non-admins can see them.  Which service is involved
> shouldn't determine that.

Agreed.  There should be a join-able list that will tell us about such
things.  I can't join sysadmins to find out about outages, and www seems
to fit that role fine.

-- 
  Bruce Momjian  <[email protected]>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

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

view thread (10+ messages)

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], [email protected], [email protected]
  Subject: Re: archives.postgresql.org not responding
  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