Re: Pgfoundry and gborg: shut one down - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: Pgfoundry and gborg: shut one down
Date
Msg-id 20060222165525.GC77800@pervasive.com
Whole thread Raw
In response to Re: Pgfoundry and gborg: shut one down  ("Jeroen T. Vermeulen" <jtv@xs4all.nl>)
Responses Re: Pgfoundry and gborg: shut one down
List pgsql-hackers
On Mon, Feb 20, 2006 at 02:49:30PM +0700, Jeroen T. Vermeulen wrote:
> 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.

Actually, it should be entirely possible to setup forwarding for
projects as they migrate, one-by-one. AFAIK mailman will handle
something like project-blah@gbork.org being forwarded to
project-blah@pgfoundry.org.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: windows / initdb oddness
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Memory profiling in postgreSQL