Date: Thu, 14 Feb 2013 18:10:39 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
Cc: "Joshua D. Drake" <jd@commandprompt.com>,
	Josh Berkus <josh@agliodbs.com>, pgsql-www@postgresql.org
Subject: Re: azpug@postgresql.org
Message-ID: <20130214211039.GI4747@alvh.no-ip.org>
References: <511AA399.90107@commandprompt.com>
	<20130212203238.GF5901@alvh.no-ip.org>
	<511AA7E2.1080509@commandprompt.com>
	<511ABC83.4090006@agliodbs.com>
	<511ABFD5.5000800@commandprompt.com>
	<511D5070.60202@kaltenbrunner.cc>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <511D5070.60202@kaltenbrunner.cc>
User-Agent: Mutt/1.5.21 (2010-09-15)
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-www-owner@postgresql.org

Stefan Kaltenbrunner wrote:
> On 02/12/2013 11:19 PM, Joshua D. Drake wrote:

> >> Mind you, if the list needs modification *anyway*, is there something
> >> wrong with using ArizonaPUG@postgresql.org?
> >=20
> > That seems a reasonable compromise.
>=20
> yeah - I don't think we should use azpug@ for arizona and shadow an
> entire country so I would thing that arizonapug@ seems like a sensible
> alternative

And how about US-Ariz-pug?  The ISO code for Arizona is US-AZ; we could
do that too.

I want something that has gotten at least *some* discussion, thought,
and agreement, not the first thing that crosses our minds.  It's a name
that we're going to be stuck with for a long time, because it's damn
hard to change list names.  I note none of the guys from AZ have
actually said anything.

--=20
=C1lvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services


--=20
Sent via pgsql-www mailing list (pgsql-www@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www