From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Devrim GÜNDÜZ <devrim(at)gunduz(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: Proposal to shutdown pgFoundry |
Date: | 2011-05-20 17:35:54 |
Message-ID: | BANLkTinM3k=HeaXywKuacOfKgP-LidXtRQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
2011/5/20 Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>:
> On Fri, 2011-05-20 at 15:48 +0000, Dave Page wrote:
>> > 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.
>
> We already allow *everyone* to distribute their tarballs through our FTP
> mirror network.
Yes, but that wasn't the point of my comment - more that there's a
barrier of entry to pass at present before you can do that, which
makes it harder for people to use the distribution facilities
inappropriately.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2011-05-20 17:38:20 | Re: Proposal to shutdown pgFoundry |
Previous Message | Dave Page | 2011-05-20 17:34:14 | Re: Proposal to shutdown pgFoundry |