Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id E4BC22E003D for ; Sat, 22 Mar 2008 12:31:56 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 74004-06 for ; Sat, 22 Mar 2008 12:31:53 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id CDD272E003A for ; Sat, 22 Mar 2008 12:31:53 -0300 (ADT) Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and authenticated) by svr2.hagander.net (Postfix) with ESMTP id 9C401DCC99A; Sat, 22 Mar 2008 16:31:51 +0100 (CET) Message-ID: <47E5270E.9030303@hagander.net> Date: Sat, 22 Mar 2008 16:34:38 +0100 From: Magnus Hagander User-Agent: Thunderbird 2.0.0.12 (X11/20080213) MIME-Version: 1.0 To: Bruce Momjian CC: Dave Page , "Joshua D. Drake" , Robert Treat , pgsql-www@postgresql.org Subject: Re: Time to get infrastructure team-based References: <200803221448.m2MEm9G05256@momjian.us> In-Reply-To: <200803221448.m2MEm9G05256@momjian.us> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/473 X-Sequence-Number: 14592 Bruce Momjian wrote: > Dave Page wrote: >> On Sat, Mar 22, 2008 at 2:37 PM, Bruce Momjian wrote: >>> > I can, but it can be changed so that I cannot in seconds. We *need* >>> > agreement otherwise this could get extremely messy. Has anyone from >>> > -core other than me actually asked yet? >>> >>> No, but it seems like a waste of time to even try. >>> >>> One idea is to set up the duplicate infrastructure with a domain in >>> place, and if the domain change gets blocked, we just switch to the new >>> domain name. >> I don't even want to think about the ramifications of doing that. > > Well, then we will forever be hostage to the will of the domain name > holder. Yes, but that would be equally true of the holder of the new domain. It would, however, make sense to have the domain reassigned to postgresql.org - it's currently owned by pgsql,inc. But you still need a contacts on the domain that are individuals, who will always have at least a theoretical ability to "hold hostage". But this is really a different question from the other one. I'm not saying both shouldn't be fixed, I'm just saying it's different things. //Magnus