Re: PostgreSQL passes MySQL for Freshmeat Downloads - Mailing list pgsql-advocacy

From Jonathan Fuerth
Subject Re: PostgreSQL passes MySQL for Freshmeat Downloads
Date
Msg-id d359a6a50806130817h154aee8ewe107a867c9a129d1@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL passes MySQL for Freshmeat Downloads  (Chander Ganesan <chander@otg-nc.com>)
Responses Re: PostgreSQL passes MySQL for Freshmeat Downloads
List pgsql-advocacy
On Fri, Jun 13, 2008 at 8:59 AM, Chander Ganesan <chander@otg-nc.com> wrote:
> Alvaro Herrera wrote:
>>
>> _Please_ by all means let's remove it.  It is always out of date.  If we
>> absolutely must keep a Freshmeat entry, then it should not list any
>> "current release" at all -- let's make it just point to our own web site
>> that's (almost) always up to date.
>>
>
> But then we would drop behind MySQL in terms of downloads, since noone would
> be able to download from freshmeat. ;-)  It's quite the conundrum..  Perhaps
> we can let them download a downloader, which downloads from the PostgreSQL
> site (j/k)...
>

Although I agree it's better to present nothing at all than to present
something consistently incorrect and out-of-date, I think that entry
on freshmeat is too important to the project's public image to let it
go.

I think a solution as simple as a script that scrapes the PostgreSQL
download site for the newest version (currently 8.3.3) and ensures
it's mentioned in the freshmeat entry (currently, it's not) and then
nags the people with access to edit the entry would be sufficient to
solve this problem.

I have no clout in this community, so I won't ask for access to edit
the freshmeat entry. But I would be happy to write and maintain the
script!

-Jonathan

pgsql-advocacy by date:

Previous
From: Simon Riggs
Date:
Subject: Re: PostgreSQL derivatives
Next
From: "Gavin M. Roy"
Date:
Subject: Re: PostgreSQL passes MySQL for Freshmeat Downloads