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 1tw0A1-009oPY-B1 for pgsql-hackers@arkaria.postgresql.org; Sat, 22 Mar 2025 14:49:17 +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 1tw09z-00EV9x-DQ for pgsql-hackers@arkaria.postgresql.org; Sat, 22 Mar 2025 14:49:15 +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 1tw09z-00EV9o-3z for pgsql-hackers@lists.postgresql.org; Sat, 22 Mar 2025 14:49:15 +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.96) (envelope-from ) id 1tw09w-000W1u-1Q for pgsql-hackers@lists.postgresql.org; Sat, 22 Mar 2025 14:49:14 +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 52MEn4ID1828576; Sat, 22 Mar 2025 10:49:04 -0400 From: Tom Lane To: Peter Geoghegan cc: Jelte Fennema-Nio , Peter Eisentraut , PostgreSQL Hackers , Maciek Sakrejda Subject: Re: Next commitfest app release is planned for March 18th In-reply-to: References: <4c3ed20a-e2db-463f-829f-deef59e4e739@eisentraut.org> <1579213.1742579607@sss.pgh.pa.us> Comments: In-reply-to Peter Geoghegan message dated "Sat, 22 Mar 2025 10:31:17 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1828574.1742654944.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Sat, 22 Mar 2025 10:49:04 -0400 Message-ID: <1828575.1742654944@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Peter Geoghegan writes: > On Sat, Mar 22, 2025 at 7:15 AM Jelte Fennema-Nio wrote: >> Yeah I think we need a way to "star" a patch (not just for committers, >> but for anyone). > Right. In my view "starring" something should definitely not appear in > the "History Log" of the patch; it should be private. +1 > Personally, I think it'd be most useful for the dashboard to show all > open patches. Surely not "all"? We have that display already. Should be more like "patches that I have expressed an interest in or have reason to take current or future action on". In the case of stale patches that haven't been moved forward from a closed commitfest, perhaps we could compromise on Jelte's suggestion of putting those in a separate section at the bottom of the page. However, I still think such patches should be treated differently for the author than other people. The author does have current action to take on the patch, namely moving it forward or withdrawing it. regards, tom lane