| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-www(at)postgresql(dot)org, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
| Subject: | Re: archives.postgresql.org not responding |
| Date: | 2008-06-23 01:48:57 |
| Message-ID: | 200806230148.m5N1mve23872@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
Tom Lane wrote:
> "Marc G. Fournier" <scrappy(at)hub(dot)org> 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 <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2008-06-23 10:43:52 | Revised downloads section on the website |
| Previous Message | Marc G. Fournier | 2008-06-23 01:36:16 | Mail VPS |