Re: Proposal to shutdown pgFoundry - Mailing list pgsql-www

From Tom Lane
Subject Re: Proposal to shutdown pgFoundry
Date
Msg-id 11761.1305906217@sss.pgh.pa.us
Whole thread Raw
In response to Re: Proposal to shutdown pgFoundry  (Dave Page <dpage@pgadmin.org>)
Responses Re: Proposal to shutdown pgFoundry  (Dave Page <dpage@pgadmin.org>)
Re: Proposal to shutdown pgFoundry  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
List pgsql-www
Dave Page <dpage@pgadmin.org> writes:
> 2011/5/20 Devrim G�ND�Z <devrim@gunduz.org>:
>> When we shut it down, all projects will all go somewhere else, and that
>> somewhere else might sound reliable to the people outside the community.
>> That is the only concern of me. Getting rid of CVS is fine, and they can
>> move their projects to git.postgresql.org, which would be excellent.
>> Still, is there a simple way that PostgreSQL infrastructure team can
>> provide hosting are for tarballs for ex-pgfoundry projects?

> I think we'd want to try to avoid doing that as it would require
> policing to ensure inappropriate content wasn't uploaded.

... yeah, that's a problem.

> Plus, people can always use SourceForge for distribution.

If you drive people to sourceforge for distribution, what value is there
in git.postgresql.org?

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.
        regards, tom lane


pgsql-www by date:

Previous
From: Dave Page
Date:
Subject: Re: Proposal to shutdown pgFoundry
Next
From: Dave Page
Date:
Subject: Re: Proposal to shutdown pgFoundry