Re: Proposal to shutdown pgFoundry

Dave,

As you know, I'm in favor of this in general. Shutting down pgfoundry will be a significant amount of effort though.

So, some things:

Mailing Lists:
I think you're underestimating the number of mailing lists in pgFoundry. I know I use pgFoundry for "disposable" mailing lists for special purposes (Google SOC 2011, for example). While there are plenty of places I can externally host code, free mailing list hosting on third parties in general is inadequate for the community purposes I need lists for (yahoo and google groups are problematic for multiple reasons).
I really need to have a mailserver which is not considered critical by the sysadmin team, and where I can freely create new lists and drop old ones.

Links:
The pgfoundry page is often the top google link for a lot of projects. If those links stop working a lot of PG-related projects will effectively vanish from Google. So we're going to need to create redirects for all of the projects.postgresql.org pages at a minimum to new locations supplied by the project owner.

Directory:
We're going to need something better than the current software directory app, which is dominated by commercial advertisting. Ideas?

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
San Francisco