Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gi1TM-0001Do-HQ for pgsql-www@arkaria.postgresql.org; Fri, 11 Jan 2019 18:24:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gi1TL-00019g-6h for pgsql-www@arkaria.postgresql.org; Fri, 11 Jan 2019 18:23:59 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gi1TK-000198-TV for pgsql-www@lists.postgresql.org; Fri, 11 Jan 2019 18:23:59 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gi1TI-00058Y-Dx for pgsql-www@lists.postgresql.org; Fri, 11 Jan 2019 18:23:57 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id BE14820C8C; Fri, 11 Jan 2019 13:23:55 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Fri, 11 Jan 2019 13:23:55 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=VgMk8P1t6pTcDM3WP4OUnO63cKF khzsPn40XlRF3QRc=; b=qN8xEHCsoD4Vv+sRLm23W4FPk44bXeTemu0nJnlt9Xb qRw6oUcGsCQv11Ux1GrUV1jBvnnEwKtOHLMPliJ+LUOzVH/rqHgWLLt9RSJp8qZ8 KIxR28yFIH13twY1fnEo8wR2MHBxg3RQly7fUet5qz5eHyzPEu0hZBekFqphC/jY 1FNf264LdtwrmIJ9JcD49+BV5FPk5ag/vK8dz4nk1pAddxF3Nxz47UUow3KcHQtr DsfJ9r5am+NmqsqAbU7UsquDKZFXgAmbMG8OwfWhI6CEiZxeGaM4iIeJ+hE569pB OLckOE4fwUivOl9NR0I82I0IgHNeOn28t+Z6bibxphg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=VgMk8P 1t6pTcDM3WP4OUnO63cKFkhzsPn40XlRF3QRc=; b=cgg3mhBC25vVeAJyRwug57 aG97W3syjyAB5mMss8h4I3Ckp1zccv+liFNrRi7v/o7V6AZbXcwrp1rbs94J3Igm nEBC1sjR+Mb0mHdZgtVSdbrsTT4khr7/C/k7V4SqSaP/50YEiFyv5IIXUM//d2Ui Y9Ksj3VIYF5Gr4Zd9jOcVpbxJPj6sKb7pTHjDqLgi1vzpBWmLNu9Ri/lvZR/G8q4 q0VI3wingAJNkxcbWgiYhl2I7IYw0s4A97jEs33dgLKi2fQYln0UAfRWY4AnO4Py u200LErbi8VAb2FUHUJNyAT3fjj+w3Vy9h4AQ6tYa/OewUsRIGIfdpfu3GrbrCig == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrfeehgdduudefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpeffhffvuffkfh ggtggujgesthdtredttddtvdenucfhrhhomheptehnughrvghsucfhrhgvuhhnugcuoegr nhgurhgvshesrghnrghrrgiivghlrdguvgeqnecukfhppeelkedrvddutddrudegtddrud ejudenucfrrghrrghmpehmrghilhhfrhhomheprghnughrvghssegrnhgrrhgriigvlhdr uggvnecuvehluhhsthgvrhfuihiivgepud X-ME-Proxy: Received: from intern.anarazel.de (c-98-210-140-171.hsd1.ca.comcast.net [98.210.140.171]) by mail.messagingengine.com (Postfix) with ESMTPA id BC54CE4394; Fri, 11 Jan 2019 13:23:54 -0500 (EST) Date: Fri, 11 Jan 2019 10:23:53 -0800 From: Andres Freund To: Stephen Frost Cc: Tatsuo Ishii , dpage@pgadmin.org, tgl@sss.pgh.pa.us, dean.a.rasheed@gmail.com, pgsql-www@lists.postgresql.org, Magnus Hagander Subject: Re: Policy on cross-posting to multiple lists Message-ID: <20190111182353.flfkfrxybredgmyc@alap3.anarazel.de> References: <20190110171835.GP2528@tamriel.snowman.net> <3281.1547142423@sss.pgh.pa.us> <20190111.100804.2220477848676088079.t-ishii@sraoss.co.jp> <20190111163805.GT2528@tamriel.snowman.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190111163805.GT2528@tamriel.snowman.net> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, On 2019-01-11 11:38:05 -0500, Stephen Frost wrote: > After stealing some time from Magnus to chat quickly about this (he > seems to be mostly unavailable at present), what we're trying to figure > out is what the group, overall, wants, and in particular if the change > to allow cross-posting with -hackers solves the valid use-cases while > preventing the invalid use-cases (like cross-posting between -general, > -performance, and -sql). Those don't really seem to be common and painful enough to really need a technical solution. -performance still seems like a useful subset of people, and sometimes threads migrate to/from there. I'd personally just merge -sql with -general, it doesn't seem to have a use-case left anymore. But that can be done later. > Of course, it isn't perfect, but then it's unlikely that anything will > be. Changes which require us to write additional code into pglister > will, of course, take longer, but we can work towards it if there's > agreement about what such a change would look like. In the interim, we > could see how things go with the current configuration, or we could add > other lists to the 'exclude', beyond just -hackers and the private > lists, or we could add them all (effectively going back to where things > were before the changes were made). > > Thoughts? Specific votes in one of those directions would help me, at > least, figure out what should be done today. I think you should just revert to the prior state, and then we can discuss potential solutions and the problems they're intended to address. I find it baffling that after being called out for unilateral/not publicly discussed decisions you attempt to address that criticism by continuing to make unilateral decisions. Greetings, Andres Freund