Re: Proposal to shutdown pgFoundry

2011/5/20 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> If you drive people to sourceforge for distribution, what value is there
> in git.postgresql.org?

A number of us in the sysadmin team see git.postgresql.org as a
resource for "family" projects that want to use it, like pgadmin,
psqlODBC, JDBC, translation team, press etc. For more general project
use, and for personal development trees, the feeling is that GitHub or
SourceForge are the appropriate places.

> I need to figure out what to do with pg_filedump.  All I need for it
> is an SCM and someplace to put release tarballs.  I'd prefer to use
> git.postgresql.org, but if there's nowhere for tarballs, that's not
> going to work.

Hmm, that's a good example. It would certainly qualify to live on
git.postgresql.org using the criteria I have in mind, but I can see
the tarballs would be an issue. If we do keep git.postgresql.org for
trusted projects, then perhaps it wouldn't be such an issue to give
certain users from each one access to a server to upload tarballs into
the mirror network.

I certainly wouldn't want to offer that to every project on pgFoundry though.

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

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