public inbox for [email protected]  

help / color / mirror / Atom feed

From: Marc G. Fournier <[email protected]>
To: David Fetter <[email protected]>
Cc: Marc G. Fournier <[email protected]>
Cc: Joshua D. Drake <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: PgFoundry Move
Date: Mon, 16 Jan 2006 16:33:17 -0400 (AST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

On Mon, 16 Jan 2006, David Fetter wrote:

> On Mon, Jan 16, 2006 at 02:59:29PM -0400, Marc G. Fournier wrote:
>>
>> Not sure where this email came from, but JoshB has gone to the
>> trouble of setting up a new server for pgFoundry, and when that is
>> ready, it will be moved there ...
>>
>> Is there a problem that I haven't been informed of with the server
>> it is currently running on?
>
> There are several problems, but I'll stick to the systemic one that
> such a move can address.  Right now, there is exactly one very
> hard-working person, Sean Chittenden, who can put his hands on the
> hardware when needed.  This is a fragile situation, and it's already
> cost months of effort because Sean can't put the pgFoundry machine's
> welfare ahead of everything else in his life.
>
> Command Prompt has people on call 24/7, and Josh Drake has mentioned
> to me that their absolute worst situation so far resulted in four
> hours of downtime.

If its a matter of time on Sean's part, can we ship the server up to 
Joshua to put onto their network?

My one criteria in all of this, from day one, was that it had to be 
FreeBSD based, it has to be redundant with our current *core* 
infrastructure ... as JoshB has stated in the past, he's sunk personal 
money into the server *for* pgFoundry, so just 'ditching' that server, 
IMHO, seems to be a no-op ...

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: [email protected]           Yahoo!: yscrappy              ICQ: 7615664

view thread (57+ 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: PgFoundry Move
  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