X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id 39DE09DC847;
	Mon, 16 Jan 2006 20:49:48 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 80452-09; Mon, 16 Jan 2006 20:49:50 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from eastrmmtao05.cox.net (eastrmmtao05.cox.net [68.230.240.34])
	by postgresql.org (Postfix) with ESMTP id 802779DC81C;
	Mon, 16 Jan 2006 20:49:44 -0400 (AST)
Received: from [192.168.0.17] (really [24.136.39.213]) by eastrmmtao05.cox.net
	(InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP
	id <20060117004950.HOJP14098.eastrmmtao05.cox.net@[192.168.0.17]>;
	Mon, 16 Jan 2006 19:49:50 -0500
From: Robert Treat <xzilla@users.sourceforge.net>
To: "Marc G. Fournier" <scrappy@postgresql.org>
Subject: Re: PgFoundry Move
Date: Mon, 16 Jan 2006 19:49:41 -0500
User-Agent: KMail/1.6.2
Cc: pgsql-www@postgresql.org,
 gforge-admins@pgfoundry.org
References: <43CBE53E.5090106@commandprompt.com>
	<200601161836.37704.xzilla@users.sourceforge.net>
	<20060116194415.S28752@ganymede.hub.org>
In-Reply-To: <20060116194415.S28752@ganymede.hub.org>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200601161949.41925.xzilla@users.sourceforge.net>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.109 required=5 tests=[AWL=0.109]
X-Spam-Score: 0.109
X-Spam-Level: 
X-Archive-Number: 200601/192
X-Sequence-Number: 9380

On Monday 16 January 2006 18:59, Marc G. Fournier wrote:
> On Mon, 16 Jan 2006, Robert Treat wrote:
> > So if we procrastinate^h^h^hcan just hold out for another 2 months we
> > can be completely up and running with gforge on a quality dedicated bsd
> > machine? Cause I think we can be up and running in month on a linux
> > box...  now i dont have anything against bsd so if you only need one
> > extra month I'm happy with that, but if you come back in three and say
> > you need two more...
>
> to be totally honest, since it appears that there are no reasons why it
> can't be moved over to the existing server that was bought up for it,
> pgFoundry *could* be moved over to that tomorrow *shrug*
>
> The question has never been about moving it ... the problem, as far as I
> know, is that there seems to be a desire/requirement to do two steps in
> one: move pgfoundry to the new server *at the same time* as upgrading
> gForge to the latest version ... its not something I necessarily subscribe
> to, but JoshB was pushing for that one ...
>

*sigh* you ask the software guys what the problem is and they say hardware/os. 
you ask the hardware/os guy what the problem is and he says software. You ask 
joshua and he says first week of february. sounds like we should go cmd/linux 
to me

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