From: | Joshua Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Alexey Klyukin <alexk(at)commandprompt(dot)com> |
Cc: | Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org>, Dave Page <dpage(at)pgadmin(dot)org> |
Subject: | Re: Proposal to shutdown pgFoundry |
Date: | 2011-05-21 15:07:15 |
Message-ID: | 854272521.60318.1305990435037.JavaMail.root@mail-1.01.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2011-05-23 03:21:20 | Re: planet in more languages |
Previous Message | Joshua D. Drake | 2011-05-21 03:42:57 | Re: Proposal to shutdown pgFoundry |