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 <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1sAccN-00BAmb-P2
	for pgsql-hackers@arkaria.postgresql.org; Fri, 24 May 2024 21:38:29 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1sAccK-009ha9-Tf
	for pgsql-hackers@arkaria.postgresql.org; Fri, 24 May 2024 21:38:24 +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 <tgl@sss.pgh.pa.us>)
	id 1sAccK-009ha1-Lb
	for pgsql-hackers@lists.postgresql.org; Fri, 24 May 2024 21:38:24 +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 <tgl@sss.pgh.pa.us>)
	id 1sAccH-000bMF-Fi
	for pgsql-hackers@postgresql.org; Fri, 24 May 2024 21:38:23 +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 44OLcGHH710217;
	Fri, 24 May 2024 17:38:16 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
cc: Joe Conway <mail@joeconway.com>, Robert Haas <robertmhaas@gmail.com>,
        Dmitry Dolgov <9erthalion6@gmail.com>,
        "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Subject: Re: commitfest.postgresql.org is no longer fit for purpose
In-reply-to: <9fc48474-b5df-4446-a6e9-9ec2641e4d30@enterprisedb.com>
References: <CA+TgmobnTcNq1xQE_+jxBEtj+AjKg0r_p5YNFHDE+EDnpcpFxA@mail.gmail.com> <20240519093719.sutsn2afqjs7vpft@ddolgov.remote.csb> <3238799.1716146291@sss.pgh.pa.us> <CA+TgmoYBOWpNc-1YB7v4ev5p3xprNGyfq4pcAdYo6dHcT0_dPw@mail.gmail.com> <17f80bc0-81da-4e2b-8704-8a9aca4562d1@enterprisedb.com> <672072.1716570569@sss.pgh.pa.us> <e256b693-89d3-4026-a6b0-23ca8f3857e3@enterprisedb.com> <696756.1716579914@sss.pgh.pa.us> <a1614299-2150-4db3-9cdb-9f374bf177d3@joeconway.com> <703841.1716583459@sss.pgh.pa.us> <9fc48474-b5df-4446-a6e9-9ec2641e4d30@enterprisedb.com>
Comments: In-reply-to Tomas Vondra <tomas.vondra@enterprisedb.com>
	message dated "Fri, 24 May 2024 23:23:24 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <710215.1716586696.1@sss.pgh.pa.us>
Date: Fri, 24 May 2024 17:38:16 -0400
Message-ID: <710216.1716586696@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: <https://www.postgresql.org/message-id/710216.1716586696%40sss.pgh.pa.us>
Precedence: bulk

Tomas Vondra <tomas.vondra@enterprisedb.com> writes:
> I personally don't think the FOSDEM triage is a very productive use of
> our time - we go through patches top to bottom, often with little idea
> what the current state of the patch is. We always ran out of time after
> looking at maybe 1/10 of the list.

> Having an in-person discussion about patches would be good, but I think
> we should split the meeting into much smaller groups for that, each
> looking at a different subset. And maybe it should be determined in
> advance, so that people can look at those patches in advance ...

Yeah, subgroups of 3 or 4 people sounds about right.  And definitely
some advance looking to see which patches need discussion.

			regards, tom lane