Re: Pgfoundry and gborg: shut one down - Mailing list pgsql-hackers

From Dave Page
Subject Re: Pgfoundry and gborg: shut one down
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4850868@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Re: Pgfoundry and gborg: shut one down  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Pgfoundry and gborg: shut one down
List pgsql-hackers


-----Original Message-----
From: pgsql-hackers-owner@postgresql.org on behalf of Joshua D. Drake
Sent: Sun 2/19/2006 12:35 AM
To: Bruce Momjian
Cc: Christopher Browne; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Pgfoundry and gborg: shut one down

> This is not "get everything everyone wants before shutting down a site"
> time.  We should move to one site, and if the new site is not to
> someone's liking, there is always sourceforge and other hosting sites.
>
> > I do agree with Bruce here but... we need to make sure that
> > we give everyone their data. If Gborg does CVS like Gforge
> > we may have a problem in that there is only one cvs repository.

Moving CVS is not a problem - each project has their own repo on both systems. The problem is moving all the database
stuffsuch as the bug trackers and todo lists, for which I'm told there are no working scripts. 

The other one that caused me great pain when I moved psqlODBC over was the GBorg genpages. I ended up manually pulling
thecode out of them and into plain HTML files as there is no equivalent area on pgFoundry. 

FWIW, in both the moves I have done (psqlODBC and Npgsql), only the CVS was actually moved.

Regards, Dave


pgsql-hackers by date:

Previous
From: "Satoshi Nagayasu"
Date:
Subject: Prepared Xacts and Vacuum question
Next
From: Florian Weimer
Date:
Subject: Re: possible design bug with PQescapeString()