Message-ID: <43CC027A.4070105@commandprompt.com>
Date: Mon, 16 Jan 2006 12:30:50 -0800
From: "Joshua D. Drake" <jd@commandprompt.com>
User-Agent: Thunderbird 1.5 (X11/20051201)
MIME-Version: 1.0
To: "Marc G. Fournier" <scrappy@postgresql.org>
CC: gforge-admins@pgfoundry.org, pgsql-www@postgresql.org
Subject: Re: [Gforge-admins] Re: PgFoundry Move
References: <43CBE53E.5090106@commandprompt.com>
	<20060116145602.C28752@ganymede.hub.org>
	<1137441491.3769.15.camel@swithin>
	<20060116160513.Q28752@ganymede.hub.org>
In-Reply-To: <20060116160513.Q28752@ganymede.hub.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


>> - unsupported (and in fact unknown) mailman version
>
> Wasn't Joshua planning on fixing that?
For the migration yes. I haven't touched the current machine as it is 
production.

>
>> - missing features like SVN support
>
> SVN support is there, and last I heard on that, Joshua was reading 
> through the docs on how to setup that ...
I did setup and install SVN but I did not getting it working "with" 
gforge and as I stated in an email I would leave
that to someone more knowledgeable about gforge itself.


> That it has ... and the solution to that constantly seems to be "lets 
> bring someone else new onto the admin team since they apparently have 
> spare time" ... if JoshuaD has the spare time to set this up on one of 
> his Linux boxes
Well first a good portion of this isn't "spare time". It is that I have 
resources in the management and infrastructure area regardless of 
myself. It is the same reason we
are about to host the search.

> (which isn't acceptable, the reason I agreed to move pgfoundry in the 
> first place was that the box it moved to was running FreeBSD to match 
> the rest of our *core* servers, including wwwmaster)
There is no reason except technical bias to keep it on FreeBSD and a lot 
of reasons (including a larger support pool) to put it on Linux.

> , then how come, in almost 12 months, he hasn't had the time to do the 
> same getting it up and running on a server that was bought 
> specifically for that purpose? It isn't lack of access, since everyone 
> involved with that side project has root access to do what is required 
> ...
We are also talking about physical access.

>
> The problem isn't moving the vServer ... the problem is that JoshB 
> wants to move the vServer *and* upgrade pgfoundry at the same time ... 
> if it was a matter of just moving the vServer, that could have been 
> done simply enough 12 months ago with a simple rsync, same as we did 
> when we moved wwwmaster to another server ...
We aren't really talking about JoshB's efforts as much as trying to get 
PgFoundry moved in general.

Sincerely,

Joshua D. Drake

-- 
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: PLphp, PLperl - http://www.commandprompt.com/