From: Robert Treat <xzilla@users.sourceforge.net>
To: pgsql-www@postgresql.org
Subject: Re: PgFoundry Move
Date: Mon, 16 Jan 2006 16:37:28 -0500
User-Agent: KMail/1.6.2
Cc: "Marc G. Fournier" <scrappy@postgresql.org>,
	David Fetter <david@fetter.org>, "Joshua D. Drake" <jd@commandprompt.com>,
	gforge-admins@pgfoundry.org
References: <43CBE53E.5090106@commandprompt.com>
	<20060116202147.GC14577@fetter.org>
	<20060116162903.R28752@ganymede.hub.org>
In-Reply-To: <20060116162903.R28752@ganymede.hub.org>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200601161637.28716.xzilla@users.sourceforge.net>

On Monday 16 January 2006 15:33, Marc G. Fournier wrote:
> 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 ...
>

based on my interaction with the foundry admins, afaict the single thing 
stopping us from getting pgfoundry onto a new server is that we're trying to 
do it on bsd (reread fetters' email for a good synopisis of this).  At what 
point do we decide moving forward is more important than the os we are 
putting it on?

-- 
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL