Re: pgFoundry Download URLs

From: Greg Smith <greg(at)2ndquadrant(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Dave Page <dpage(at)pgadmin(dot)org>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-www <pgsql-www(at)postgresql(dot)org>, "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>
Subject: Re: pgFoundry Download URLs
Date: 2009-12-30 23:51:47
Message-ID: 4B3BE793.5050605@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

Joshua D. Drake wrote:
> On Wed, 30 Dec 2009 22:05:41 +0100, Magnus Hagander <magnus(at)hagander(dot)net>
> wrote:
>
>> FWIW, both are AFAIK missing the "simple migration path" that Dave was
>> asking for.
>>
>
> Not really... let the developers move it themselves.
>

I don't have a large data set, just a couple of dozen people I've talked
to about this. Based on some wild-ass extrapolation from those
conversations, I would venture that if one took a survey of every active
pgfoundry maintainer, and told them "we're migrating to a better and
easier to support system, but you'll lose all your active projects and
you'll have to move them yourself to the new host manually", votes would
still be at least 10:1 in favor of that over the status quo. I'd expect
that if you provisioned an officially sanctioned replacement candidate,
the most popular projects would migrate to it in a minute given the
opportunity. The idea that anyone is going to put more time into trying
to maintain it boggles my mind.

The real key as I see it is to never again choose from among anything
but the most popular of such systems
available. Pick one of the widely deployed solutions here, don't
customize *anything*, keep up with updates to it, and let a larger slice
of the rest of the world solve this problem. Seriously--the most
important criteria here is maximizing the odds that somebody else with a
much larger use base is going to maintain and extend the underlying code
of whatever solution is used so this project doesn't have to. A quick
glance at the page Robert suggested:

http://en.wikipedia.org/wiki/Comparison_of_open_source_software_hosting_facilities

And sorting by real or estimated Alexa rank as a popularity estimate,
where lower is more popular:

Sourceforge 198
Google Code 1000 (estimated, but unsuitable anyway so who cares)
GitHub 2342
CodePlex 3334
Tigris.org 10896
Launchpad 12268

Obviously these are not all suitable just based on basic features, but I
would argue that nothing else but the ones on this list are worth doing
any work with.

--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.com

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2009-12-30 23:54:57 Re: pgFoundry Download URLs
Previous Message Robert Treat 2009-12-30 22:12:52 Re: pgFoundry Download URLs