Re: Pgfoundry and gborg: shut one down

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "Christopher Browne" <cbbrowne(at)acm(dot)org>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Pgfoundry and gborg: shut one down
Date: 2006-02-19 10:02:53
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4850868@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

-----Original Message-----
From: pgsql-hackers-owner(at)postgresql(dot)org on behalf of Joshua D. Drake
Sent: Sun 2/19/2006 12:35 AM
To: Bruce Momjian
Cc: Christopher Browne; pgsql-hackers(at)postgresql(dot)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 stuff such 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 the code 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Florian Weimer 2006-02-19 10:08:01 Re: possible design bug with PQescapeString()
Previous Message Satoshi Nagayasu 2006-02-19 09:59:14 Prepared Xacts and Vacuum question