Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s7j2g-0073gj-2o for pgsql-hackers@arkaria.postgresql.org; Thu, 16 May 2024 21:53:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s7j2f-00GsmQ-Me for pgsql-hackers@arkaria.postgresql.org; Thu, 16 May 2024 21:53:37 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s7j2f-00GsmH-Cq for pgsql-hackers@lists.postgresql.org; Thu, 16 May 2024 21:53:37 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s7j2c-000Ysd-K6 for pgsql-hackers@postgresql.org; Thu, 16 May 2024 21:53:36 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 0BCCC3019570 for ; Thu, 16 May 2024 23:53:32 +0200 (CEST) Received: from s981.loopia.se (unknown [172.22.191.5]) by s807.loopia.se (Postfix) with ESMTP id EFB3C2E2B1F1; Thu, 16 May 2024 23:53:31 +0200 (CEST) Received: from s474.loopia.se (unknown [172.22.191.5]) by s981.loopia.se (Postfix) with ESMTP id E670C22B179C; Thu, 16 May 2024 23:53:31 +0200 (CEST) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.2 X-Spam-Level: X-Spam-Status: No, score=-1.2 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1] autolearn=disabled Authentication-Results: s474.loopia.se (amavisd-new); dkim=pass (2048-bit key) header.d=yesql.se Received: from s981.loopia.se ([172.22.191.5]) by s474.loopia.se (s474.loopia.se [172.22.190.14]) (amavisd-new, port 10024) with LMTP id bCmtXnPNwNrG; Thu, 16 May 2024 23:53:31 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 185.224.57.161 Received: from smtpclient.apple (unknown [185.224.57.161]) (Authenticated sender: daniel@yesql.se) by s981.loopia.se (Postfix) with ESMTPSA id C056822B17BC; Thu, 16 May 2024 23:53:30 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yesql.se; s=loopiadkim1707475645; t=1715896411; bh=/cD3iTZF154DUWB2Dfks3AkoVNJlfgTy0Hw0WqOh7jk=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=amYaY7W0BX0Sp8DL+7Mi/+zlZlOBQZas/UT3g8/7Hz78z1pVjSPTZUFMXLzhCsvhU h/9P8AfJC3440GwKChzefzBo4OOBvq80xNSNEviBwS42IUGjjltbkvP9EnPTIpWoC4 zSHuRT0cjydt2pdKPHvzSlV0eHkKc6Gnrux0OFJzBPlbA3oQYSvklCzJQ47hPHJCfy 4j5793RiXWPK35Pns1CG2olEftvvz2UJiJvIb9Sbzq4iTi8yUo25CQJdhHgvIhCbnk 86oTf1at0d9DPaMQ4N8hwaUCaUdNNa6dlyPe8rp77DUFsNRa2NQV+c7XnGurA5OPgA 8keQ/7aBZQLgw== Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\)) Subject: Re: commitfest.postgresql.org is no longer fit for purpose From: Daniel Gustafsson In-Reply-To: <2186208.1715895987@sss.pgh.pa.us> Date: Thu, 16 May 2024 23:53:17 +0200 Cc: Peter Eisentraut , Melanie Plageman , Robert Haas , PostgreSQL Hackers Content-Transfer-Encoding: quoted-printable Message-Id: <0DA6D676-D2DA-434C-94AA-F38DD6DC23AF@yesql.se> References: <45faf826-42b7-4ce9-a081-0903d033f411@eisentraut.org> <2186208.1715895987@sss.pgh.pa.us> To: Tom Lane X-Mailer: Apple Mail (2.3774.500.171.1.1) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 16 May 2024, at 23:46, Tom Lane wrote: > At this point it seems like there's consensus to have a "parking" > section of the CF app, separate from the time-boxed CFs, and I hope > somebody will go make that happen. But I don't think that's our only > issue, so we need to keep thinking about what should be improved. Pulling in the information from the CFBot regarding test failures and = whether the patch applies at all, and automatically altering the state to WOA = for at least the latter category would be nice. There's likely to be more = analysis we can do on the thread to measure "activity/hotness", but starting with = the simple boolean data we already have could be a good start. -- Daniel Gustafsson