Re: Pgfoundry and gborg: shut one down

From: "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl>
To: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
Cc: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Thomas Hallgren" <thomas(at)tada(dot)se>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Pgfoundry and gborg: shut one down
Date: 2006-02-20 07:49:30
Message-ID: 21870.125.24.8.84.1140421770.squirrel@webmail.xs4all.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, February 20, 2006 11:00, Marc G. Fournier wrote:

>> Speaking for libpqxx, my only concern with that is the mailing list.
>> Would those have to move to different addresses--or conversely, would a
>> forced migration make it much easier to move *all* GBorg mailing lists
>> to
>> pgFoundry and maintain their old addresses?
>
> All addresses would have to be changed to the pgfoundry.org one ...

Ouch! Moving my project off GBorg wasn't so hard, but forcing all mailing
list subscribers to move to a different address does hurt.

If the same goes for many other projects on there, wouldn't it be possible
to move all mail handling for gborg.postgresql.org over to pgFoundry at
once, but preserve the domain name and list names? It may help people
make the jump if mailing list migration could be decoupled from the other
changes.

Jeroen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paesold 2006-02-20 08:03:29 Re: Domains and supporting functions
Previous Message Martijn van Oosterhout 2006-02-20 07:37:40 Re: AC_REPLACE_FUNCS([getaddrinfo]) in 8.1.3