Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-advocacy-owner+archive@lists.postgresql.org>)
	id 1knDz7-0005fT-Vz
	for pgsql-advocacy@arkaria.postgresql.org; Thu, 10 Dec 2020 04:55:21 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-advocacy-owner+archive@lists.postgresql.org>)
	id 1knDz6-00069p-5u
	for pgsql-advocacy@arkaria.postgresql.org; Thu, 10 Dec 2020 04:55:20 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <justin@postgresql.org>)
	id 1knDz5-00069i-9n
	for pgsql-advocacy@lists.postgresql.org; Thu, 10 Dec 2020 04:55:20 +0000
Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31])
	by magus.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <justin@postgresql.org>)
	id 1knDyz-0008Oz-4A
	for pgsql-advocacy@lists.postgresql.org; Thu, 10 Dec 2020 04:55:18 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=postgresql.org; s=20171124; h=Message-ID:References:In-Reply-To:Subject:Cc:
	To:From:Date:Content-Transfer-Encoding:Content-Type:MIME-Version:Sender:
	Reply-To:Content-ID:Content-Description;
	bh=lOIo6RKezjG/rCGk/ID8FLFzWEqXrnxcQk7numYIrY0=; b=XnARSbSu/6YWImxM3r236QXIKz
	Km5obsQmtzO3tUZidkZ1Lg3X9hsMzpEV2lhKoiYxZDPx5FXaOf1oPXE0xz94CGRjJsjryOEvbMQsl
	O38XZ4fUR+M1REWS4Mgt+h/Vhg8N6fjRL0coWvSYPzBb+ReoiIV/PLvWCMeIopltMJGU/Qo47KBAQ
	/fg++9XGMUpstxrGUYKdY0MKNbppkvzVRbT4XItJUTN3jruF5SojgecZWCk6/kQK/ZFLPGdafgrPm
	Dd/WafPXuWj3RDnqitScL+LsQb5nbe/tf5MIVhLTmM6LAELkqKgrQ2EsVfQuNlMo+of6EXdVtZOVu
	4wZj+hcA==;
Received: from meldrar.postgresql.org ([87.238.57.231]
 helo=webmail.postgresql.org)
	by meldrar.postgresql.org with esmtpsa
 (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
	(Exim 4.92)
	(envelope-from <justin@postgresql.org>)
	id 1knDyu-0003V8-Da; Thu, 10 Dec 2020 04:55:10 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Thu, 10 Dec 2020 15:55:07 +1100
From: Justin Clift <justin@postgresql.org>
To: Stephen Frost <sfrost@snowman.net>
Cc: "Jonathan S. Katz" <jkatz@postgresql.org>, Valeria Kaplan
 <vk@dataegret.com>, pgsql-advocacy@lists.postgresql.org,
 denish.j.patel@gmail.com
Subject: Re: PostgreSQL on K8 with Operator
In-Reply-To: <20201209163544.GX16415@tamriel.snowman.net>
References: 
 <CAJijpsCy7QSVUAwEQF2QFteUHQeKYysmopS-n75aqtaJ01m31g@mail.gmail.com>
 <d491921372ad788261ed231f824fc3f0@postgresql.org>
 <CAJijpsBg5wkUK7SToPGKUKgiamy2FJ3a6RwUWiU1O3Yhsk1X=Q@mail.gmail.com>
 <CA+OCxowKHiwneJ_PBvX91zcoes14KDwkcrTX9a5kqu-a9ZHwvQ@mail.gmail.com>
 <b257b2f9d757d090293da844914741e7@postgresql.org>
 <CAPcrru5jrqU8g5oXLBvk6c-bB3e7-qps2bV1LcddY_BmoMPmWQ@mail.gmail.com>
 <CAPcrru4YY-=DyU+B+Ae3RoPRrsHDLyMDuk9LS78JdMbpoHC2og@mail.gmail.com>
 <20df13e065750ea1cc0afcb706a0dec2@postgresql.org>
 <CAPcrru4uJi0QP5MAM5D_a-0Df9rGQv9htMGKHb-jUVUugATyeQ@mail.gmail.com>
 <4d53540d-25c1-8f7b-5c98-62c8f08a29ef@postgresql.org>
 <20201209163544.GX16415@tamriel.snowman.net>
Message-ID: <7f985ba8e65202541490300381f65067@postgresql.org>
X-Sender: justin@postgresql.org
User-Agent: Roundcube Webmail/1.3.15
List-Id: <pgsql-advocacy.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-advocacy@lists.postgresql.org>
List-Owner: <mailto:pgsql-advocacy-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-advocacy>
Precedence: bulk

On 2020-12-10 03:35, Stephen Frost wrote:
<snip>
> ... should we really be sending people to such a herokuapp site to sign
> up?  Seems like something we could probably manage to make part of
> pg.org, and really should..

Denish seems to be on the PG Advocacy mailing list now, and is CC-d 
anyway.
So it probably wouldn't be too hard to move to PG infrastructure
hosting. :)


> Not sure if there's a way for the slack admin to change the URL that
> folks on the slack channel see, but if so, that'd be nice to change 
> too,
> so that there isn't this confusion in the future.  Also seems unlikely
> that we need to have that list of domains be associated with the
> community slack...?  Also leads to confusion.

You mean the "postgresteam.slack.com" domain name?  That kind of thing
is pretty standard for Slack, and the "postgresteam" name seem on topic
enough to be ok (to me). :)

The list-of-domains thing sounds like it might be fixable in a month or
two once the new Salesforce ownership of Slack has settled a bit more. 
:)

+ Justin