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 ) id 1knOoj-0001nO-VY for pgsql-advocacy@arkaria.postgresql.org; Thu, 10 Dec 2020 16:29:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1knOoi-00006y-HA for pgsql-advocacy@arkaria.postgresql.org; Thu, 10 Dec 2020 16:29: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 ) id 1knOoi-00006m-BC for pgsql-advocacy@lists.postgresql.org; Thu, 10 Dec 2020 16:29:20 +0000 Received: from tamriel.snowman.net ([2001:470:e38f::11]) by magus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1knOoe-0005a2-29 for pgsql-advocacy@lists.postgresql.org; Thu, 10 Dec 2020 16:29:19 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id A213B5F799; Thu, 10 Dec 2020 11:29:14 -0500 (EST) Date: Thu, 10 Dec 2020 11:29:14 -0500 From: Stephen Frost To: Justin Clift Cc: "Jonathan S. Katz" , Valeria Kaplan , pgsql-advocacy@lists.postgresql.org, denish.j.patel@gmail.com Subject: Re: PostgreSQL on K8 with Operator Message-ID: <20201210162914.GL16415@tamriel.snowman.net> References: <20df13e065750ea1cc0afcb706a0dec2@postgresql.org> <4d53540d-25c1-8f7b-5c98-62c8f08a29ef@postgresql.org> <20201209163544.GX16415@tamriel.snowman.net> <7f985ba8e65202541490300381f65067@postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="763rk6KrQGL1h0tu" Content-Disposition: inline In-Reply-To: <7f985ba8e65202541490300381f65067@postgresql.org> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --763rk6KrQGL1h0tu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * Justin Clift (justin@postgresql.org) wrote: > On 2020-12-10 03:35, Stephen Frost wrote: > >... 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.. >=20 > Denish seems to be on the PG Advocacy mailing list now, and is CC-d anywa= y. > So it probably wouldn't be too hard to move to PG infrastructure > hosting. :) I suppose it'd probably be clearer to say that we'd be re-implementing the functionality of what that app does on pginfra as part of pgweb. Looks like it'd be pretty trivial to do, as the main part of the app is: https://github.com/rauchg/slackin/blob/master/lib/slack-invite.js In pgweb, for users who have registered an account, we've already got their email address (and vetted it) and therefore we could actually make the link from .Org go to a logged-in page that then sends the appropriate call to postgresteam.slack.com to have them send the email invite. > >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. >=20 > 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). :) I wasn't referring to that as being an issue, but rather wondering if there was a way on the admin side of the slack team to modify the URL that shows when you click on the top-left drop-down menu, to make it point to the .Org Community page, or something along those lines, so that folks don't send people to the postgresteam.slack.com URL by mistake, as happened here. > 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. :) With the above, I wouldn't think we'd need to have the list of domains at all, which seems like it'd be a general improvement and would hopefully reduce the confusion. Thanks, Stephen --763rk6KrQGL1h0tu Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJf0kzaAAoJEO1sijiDR2RVZTQP/AnFpkvNRxIrFRIz0JvfYTjc /n6c46MwBw55P2uV26xYzqmoovDTSR0vIw1RAjPRZmH3Zf6i9iOW6S7yejAIlJU6 AYwDys58D5LS+Uul2LNxyZTExZJoJJdtd5/Z/Ha7RYsSZ0uBBO7E64oJQ3bSmegR dBuOg3JIF9gYP/7yrXMW5gzobHMdXDqxGQrWhh6ewta477Ymv6t+4G9WddCmLtbM OFUTFcPxeohxyCOzslihw37yiClJW2NOHIeudqoAF6xvTveAENTjen/ekMxQxYFn 8HlRw0WF/tJbReiv6ho10H95PEISuPw6u3E3qnO07xfWnMRnEFseKi/s7oO7It28 Gr9oqgyZNKqRH+3hD45RwgJVlag5sctkGZ9wOt6zdBtQi8iJcHfs6A3SKozoz/A6 qnMjEPGIu9/WOLAlxM4z5e3MHd+x9o6HzGVZ8c//KfuHGs27j9JN86j0i1SDwpxR EJuEMak90AUvlJwNLIudUuiV2qOUlJRcXhNvxMrhHY5gIdbZknGaD+bP5Xs08Nhz 73sK/koGChkZHXfdAGIJy0alRjL3a8u/hwkAe3qc95eNp2FbAZp2CO1yNlgw2rba DtqFoIPw7WqgSW/8iL7L8uPNCYraSIsexRasUSMvy+Oi4QicpoTgp5/km78QdgbJ kSbzv0rZRMXPNgQENStp =6OLD -----END PGP SIGNATURE----- --763rk6KrQGL1h0tu--