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 1s7iKn-006zkc-1D for pgsql-hackers@arkaria.postgresql.org; Thu, 16 May 2024 21:08:18 +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 1s7iKm-00Flan-O5 for pgsql-hackers@arkaria.postgresql.org; Thu, 16 May 2024 21:08:16 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s7iKm-00Flaa-EE for pgsql-hackers@lists.postgresql.org; Thu, 16 May 2024 21:08:16 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s7iKj-000bIS-8i for pgsql-hackers@postgresql.org; Thu, 16 May 2024 21:08:15 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 44GL89Y02171751; Thu, 16 May 2024 17:08:09 -0400 From: Tom Lane To: Jacob Champion cc: Joe Conway , Daniel Gustafsson , Robert Haas , PostgreSQL Hackers Subject: Re: commitfest.postgresql.org is no longer fit for purpose In-reply-to: References: <50435844-54E0-4100-AE23-C72FF4134F92@yesql.se> <2145897.1715888840@sss.pgh.pa.us> Comments: In-reply-to Jacob Champion message dated "Thu, 16 May 2024 13:57:05 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <2171749.1715893689.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Thu, 16 May 2024 17:08:09 -0400 Message-ID: <2171750.1715893689@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Jacob Champion writes: > On Thu, May 16, 2024 at 1:31 PM Joe Conway wrote: >> Maybe we should just make it a policy that *nothing* gets moved forward >> from commitfest-to-commitfest and therefore the author needs to care >> enough to register for the next one? > I think that's going to severely disadvantage anyone who doesn't do > this as their day job. Maybe I'm bristling a bit too much at the > wording, but not having time to shepherd a patch is not the same as > not caring. Also, I doubt that there are all that many patches that have simply been abandoned by their authors. Our problem is the same as it's been for many years: not enough review person-power, rather than not enough patches. So I think authors would just jump through that hoop, or enough of them would that it wouldn't improve matters. regards, tom lane