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 1undtf-009OFf-Kn for pgsql-www@arkaria.postgresql.org; Sun, 17 Aug 2025 13:58:09 +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 1undtf-00A8R5-2x for pgsql-www@arkaria.postgresql.org; Sun, 17 Aug 2025 13:58:07 +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 1undte-00A8Q3-SQ for pgsql-www@lists.postgresql.org; Sun, 17 Aug 2025 13:58:07 +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 1undtc-000L0E-2k for pgsql-www@lists.postgresql.org; Sun, 17 Aug 2025 13:58:07 +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 57HDvoN8164576; Sun, 17 Aug 2025 09:57:50 -0400 From: Tom Lane To: Peter Eisentraut cc: Christoph Berg , PostgreSQL WWW Subject: Re: PostgreSQL Contributor levels In-reply-to: <4a98007e-2103-42f9-afef-fd75095239a1@eisentraut.org> References: <4a98007e-2103-42f9-afef-fd75095239a1@eisentraut.org> Comments: In-reply-to Peter Eisentraut message dated "Sun, 17 Aug 2025 14:06:22 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <164574.1755439070.1@sss.pgh.pa.us> Date: Sun, 17 Aug 2025 09:57:50 -0400 Message-ID: <164575.1755439070@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Peter Eisentraut writes: > On 15.08.25 19:30, Christoph Berg wrote: >> Clearly, there are more ways to contribute, and the term "Contributor" >> on the curated list should probably be more specific. > The threshold for getting into the release notes is absolutely minimal, > and I think it would devalue the curation work that you are doing by > somehow combining the two data sets or making a third level based on the > release notes or something like that. +1. For example, a single bug report is enough to get you into the commit log and thence the release notes. There's no requirement for continuing effort, but I think even the lowest level of the curated list should imply some amount of that. Perhaps the release notes could be useful as a sanity check though. Say, if a person appears in the last three release-note lists and is not in the curated list, maybe that is a name to take another look at. regards, tom lane