Message-ID: <466E5BB6.9040907@postgresql.org>
Date: Tue, 12 Jun 2007 09:39:18 +0100
From: Dave Page <dpage@postgresql.org>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: Magnus Hagander <magnus@hagander.net>
CC: pgsql-www@postgresql.org
Subject: Re: Moving the website project from GBorg
References: <466E5422.9070102@postgresql.org>
	<20070612083630.GC2819@svr2.hagander.net>
In-Reply-To: <20070612083630.GC2819@svr2.hagander.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Magnus Hagander wrote:
> On Tue, Jun 12, 2007 at 09:06:58AM +0100, Dave Page wrote:
>> I've created a pgweb project on pgFoundry to migrate from GBorg to. The 
>> original idea was to migrate the CVS and just lose the bugs etc. as 
>> they're largely out of date at the moment anyway. We can make an effort 
>> to be more organised with the more usable pgFoundry trackers in the future.
> 
> They're only slightly more usable, but still ;-)
> Agreed (again) on the fact that we just drop whatever's tehre now. It's all
> insanely out of date.
> 
>> Magnus has since come up with an idea though, that instead of using CVS 
>> on pgFoundry, we move the website CVS to an SVN repository actually on 
>> wwwmaster to remove the dependency on pgFoundry for the operation of the 
>> website. This seems like a fine idea to me - any other thoughts or ideas?
> 
> Can we set up some way to replicate that repository *back* into pgfoundry?
> Might be nice for "outsiders" to be able to use the cvs viewer... Or we
> just add a simplistic cvs viewer on wwwmaster for them?

We could probably rsync it back in, *when* we have a SVN-supporting 
GForge, assuming that it remains 1 repo per project.

/D