From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
---|---|
To: | pgsql-www(at)postgresql(dot)org |
Subject: | Re: pgFoundry Download URLs |
Date: | 2010-01-05 18:32:49 |
Message-ID: | 64ccaa9f9a92336fec247b30b71013c5@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
>> There's also a 2nd advantage to having the PG accessory project mostly
>> hosted elsewhere: it makes us more visible to outside communities.
>
> and makes it harder to aggregate them back into a canonical
> search/aggregator which is what some people want...
We're never going to have that. See below.
...
> so what place would you redirect people too if they ask for a listing of
> stuff related to postgresql? and no I don't think a manually maintained
> "software catalogue" like we have on the website is any/much better.
There is no single *place* we can redirect people to, nor will there ever
be moving forward. It's way too late for that. Look at the number of
Postgres related projects that are *not* on pgf, and ask yourself if
they will ever migrate back to pgf or its successor (hint: no).
> What we need is aggregation of information and it is kind of hard to see
> how we would get that out of any of the existing collab sites (except
> maybe freshmeat but even that would not work too well). For stuff on pgf
> we essentially get most of the important information for "free" as part
> of people running their projects. Just because we failed to utilize that
> information so far does not mean that the whole concept is flawed.
I think it does indicate just that. How many years has gborg and now
pgfoundry limped along? I agree that we can do better with a central
listing. Rather than the hard to navigate and hard to find software
catalogoue (or however Dave spells it :), let's create a page on the
wiki that lists all interesting and active Postgres related projects.
Not a category, not a set of pages, a single page. There are probably
at most 50 such projects. The inclusion rule would be simple: someone
who cares enough about a particular project can get a wiki account
and add it in themselves. Name, link, short description, done.
In case I'm not clear, I'm also +1 for shutting down pgf at some point.
It's a big jumbled mess of unloved and unfinished projects right now,
with a tiny handful of truly active and useful projects. Cut them all
free, and the survivors will find other homes (e.g. github). I know that's
harsh, but it's 2010 and pgf is still embarassingly bad after all these
years.
- --
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 201001051330
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAktDhb8ACgkQvJuQZxSWSsgDcgCbBlXAv8g9DiQPkqf124pbcZyW
N/8AoIdLOkFN7es5Kis1niqoYIC7qAD+
=i0dZ
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Mayer | 2010-01-05 22:35:56 | Re: pgFoundry Download URLs |
Previous Message | Stefan Kaltenbrunner | 2010-01-05 08:26:13 | tribble.postgresql.org - planned maintenance downtime |