Re: Proposal to shutdown pgFoundry - Mailing list pgsql-www

From Tom Lane
Subject Re: Proposal to shutdown pgFoundry
Date
Msg-id 4981.1306333105@sss.pgh.pa.us
Whole thread Raw
In response to Re: Proposal to shutdown pgFoundry  (Cédric Villemain <cedric.villemain.debian@gmail.com>)
Responses Re: Proposal to shutdown pgFoundry  (Magnus Hagander <magnus@hagander.net>)
List pgsql-www
Cédric Villemain <cedric.villemain.debian@gmail.com> writes:
> 2011/5/25 Dave Page <dpage@pgadmin.org>:
>> On Wed, May 25, 2011 at 9:21 AM, Markus Wanner <markus@bluegap.ch> wrote:
>>> The proposal was to put up a static copy. �That hardly has any security
>>> issues, I think.

>> Actually generating a static copy may be a non-trivial amount of work
>> though. It's easy enough to spider the site and store it as a static
>> HTML, but we'd also need to ensure we remove any links or forms to
>> non-static features of course.

> I believe we don't care :)
> We can just add a disclaimer at top of each page : "this site is only
> for archive, do not expect each link to work. Thank you."

Or, just replace the server with something that serves out the same
static page for any pgfoundry URL: "pgfoundry has been retired.  Please
see <list of useful resources> to search for the new location of the
project you are looking for."

The main point in my mind is that we'll never get rid of all the
references to pgfoundry.  Having those URLs go 404 will not look good
nor be helpful to visitors.
        regards, tom lane


pgsql-www by date:

Previous
From: Cédric Villemain
Date:
Subject: Re: Proposal to shutdown pgFoundry
Next
From: Magnus Hagander
Date:
Subject: Re: Proposal to shutdown pgFoundry