The reason I favour a GBorg is that VA Linux (who own sourceforge) have yet
to turn in a profit and so maylook to trim some of it's assets in order to
improve profitability at some point in the future.
I think it would be a bad move to shift everything to sourceforge, only to
find that a year or more down the line the site dissappears/degrades to a
level where it causes problems for the project, and loose the time we could
have spent building up the reputation of GBorg.
----- Original Message -----
From: "Neil Conway" <neilc(at)samurai(dot)com>
To: "Greg Copeland" <greg(at)CopelandConsulting(dot)Net>
Cc: "Alvaro Herrera" <alvherre(at)dcc(dot)uchile(dot)cl>; "Marc G. Fournier"
<scrappy(at)hub(dot)org>; "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp>; <raanders(at)acm(dot)org>;
"PostgresSQL Hackers Mailing List" <pgsql-hackers(at)postgresql(dot)org>
Sent: Wednesday, December 18, 2002 2:55 AM
Subject: [mail] Re: [HACKERS] Update on replication
> On Tue, 2002-12-17 at 21:33, Greg Copeland wrote:
> > I do agree, GBorg needs MUCH higher visibility!
> I'm just curious: why do we need GBorg at all? Does it offer anything
> that SourceForge, or a similar service does not offer?
> Especially given that (a) most other OSS projects don't have a site for
> "related projects" (unless you count something like CPAN, which is
> totally different) (b) GBorg is completely unknown to anyone outside the
> PostgreSQL community and even to many people within it...
> Neil Conway <neilc(at)samurai(dot)com> || PGP Key ID: DB3C29FC
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
In response to
pgsql-hackers by date
|Next:||From: Janardhan||Date: 2002-12-18 08:23:15|
|Subject: Re: Reusing Dead Tuples:|
|Previous:||From: Christopher Kings-Lynne||Date: 2002-12-18 07:19:21|
|Subject: Re: MySQL 4.1 Features|