X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP id 9FBB4D1B7F0
	for <pgsql-www-postgresql.org@localhost.postgresql.org>;
	Fri, 12 Mar 2004 18:37:05 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024)
	with ESMTP id 10262-07
	for <pgsql-www-postgresql.org@localhost.postgresql.org>;
	Fri, 12 Mar 2004 14:36:54 -0400 (AST)
Received: from sss.pgh.pa.us (unknown [192.204.191.242])
	by svr1.postgresql.org (Postfix) with ESMTP id 5092DD1B979
	for <pgsql-www@postgresql.org>; Fri, 12 Mar 2004 14:36:51 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i2CIamFW011655;
	Fri, 12 Mar 2004 13:36:48 -0500 (EST)
To: "Marc G. Fournier" <scrappy@postgresql.org>
Cc: Rod Taylor <pg@rbt.ca>, "Jeroen T. Vermeulen" <jtv@xs4all.nl>,
	Thomas Swan <tswan@idigx.com>, Robert Treat <xzilla@users.sourceforge.net>,
	PostgreSQL Development <pgsql-hackers@postgresql.org>,
	pgsql-www@postgresql.org
Subject: Re: [HACKERS] The Name Game: postgresql.net vs. 
In-reply-to: <20040312142952.V64550@ganymede.hub.org> 
References: <03AF4E498C591348A42FC93DEA9661B889F5DD@mail.vale-housing.co.uk>
	<200403111808.09687.xzilla@users.sourceforge.net>
	<200403111519.55064.josh@agliodbs.com>
	<200403120811.24506.xzilla@users.sourceforge.net>
	<9272.1079104465@sss.pgh.pa.us>
	<14858.199.222.14.2.1079109814.squirrel@www.idigx.com>
	<20040312165255.GY39391@xs4all.nl> <1079112222.736.5.camel@jester>
	<20040312142952.V64550@ganymede.hub.org>
Comments: In-reply-to "Marc G. Fournier" <scrappy@postgresql.org>
	message dated "Fri, 12 Mar 2004 14:30:45 -0400"
Date: Fri, 12 Mar 2004 13:36:47 -0500
Message-ID: <11654.1079116607@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Archive-Number: 200403/179
X-Sequence-Number: 3995

"Marc G. Fournier" <scrappy@postgresql.org> writes:
> the projects site will not be under postgresql.org ... postgresql.net is
> available for it, but not postgresql.org ... we are keeping that domain
> "clean" for any future stuff we want to do with the core project ...

I agree we don't want <project>.postgresql.org, as that is likely to
risk name conflicts.  However, that objection doesn't apply to
<project>.projects.postgresql.org, or variants of that.  So far the only
objection I've heard to that sort of setup is "the domain name is too
long", and as others have pointed out, it's a weak objection.

Since we do already own pgfoundry.org, could we satisfy everybody by
dual-naming the project sites?  That is, have both
	<project>.pgfoundry.org
	<project>.pgfoundry.postgresql.org
point to the same place?

			regards, tom lane