All,
My $0.02:
With the presensce today of Launchpad, Codehaus, SourceForge, Tigris,
Java.net, CPAN, GEM, Developerworks, Github, Code.Google.com, and
others, it seems silly for our project to be putting our scarce admin
resources into maintaining/improving an outdated collab site. Let
others do the work.
There's also a 2nd advantage to having the PG accessory project mostly
hosted elsewhere: it makes us more visible to outside communities.
What we need out of pgfoundry is five things, none of which require a
full collab framework, and some of which are really unrelated to the others:
1) a place for less offical mailing lists (e.g. non-permanent
non-@postgresql.org mailing lists) which can be created without the
whole process required for a new "official" list. Note that many of
these lists are not related to any code development project.
2) a place for web pages/documentation for some projects (which could be
a wiki, or something else)
3) a search and download service for postgresql accessories (something
pgfoundry currently does a poor job of)
4) a news feed for postgresql accessories (something pgfoundry currently
does a bad job of)
5) A place to store files for download for internal project use which is
easier to manage than mediawiki's "images", and includes the ability to
restrict files to a specific access list. Like (1), these files are
largely not related to specific development projects.
It seems to me that *all* of the above could be better done than how
pgfoundry does it, and done in a simpler and more maintainable way.
--Josh Berkus
