Re: Proposal to shutdown pgFoundry

2011/5/21 Joshua Berkus <josh(at)agliodbs(dot)com>:
>
> 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.

Josh and I discussed this in person. It's still not entirely clear
that there is a genuine requirement for this much flexibility, though
clearly Josh does need to be able use both public and private mailing
lists. I don't see any reason at the moment why those lists couldn't
be on the existing list server.

> 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.

Links will be available from the software catalog, which we can
redirect to from pgfoundry.org. I don't think we have any
responsibility to provide search rankings for projects beyond that.

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

Option to filter out non-OSS projects?

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company