Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1perzR-0005kr-Is for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Mar 2023 06:30:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1perzQ-0005KI-0J for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Mar 2023 06:30:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1perzP-0005K8-N4 for pgsql-hackers@lists.postgresql.org; Wed, 22 Mar 2023 06:30:27 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1perzM-0000Nw-7K for pgsql-hackers@postgresql.org; Wed, 22 Mar 2023 06:30:27 +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 32M6UBjB1443466; Wed, 22 Mar 2023 02:30:11 -0400 From: Tom Lane To: Thomas Munro cc: Alvaro Herrera , Justin Pryzby , Peter Geoghegan , Greg Stark , "Gregory Stark (as CFM)" , Michael Paquier , pgsql-hackers@postgresql.org Subject: Re: Commitfest 2023-03 starting tomorrow! In-reply-to: References: <20230321095920.nhf7scs3bqmgvpao@alvherre.pgsql> Comments: In-reply-to Thomas Munro message dated "Wed, 22 Mar 2023 18:45:40 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1443464.1679466611.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 22 Mar 2023 02:30:11 -0400 Message-ID: <1443465.1679466611@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thomas Munro writes: > On Tue, Mar 21, 2023 at 10:59=E2=80=AFPM Alvaro Herrera wrote: >> This led me to suggesting that perhaps we need to be more lenient when >> it comes to new contributors. As I said, for seasoned contributors, >> it's not a problem to keep up with our requirements, however silly they >> are. But people who spend their evenings a whole week or month trying >> to understand how to patch for one thing that they want, to be received >> by six months of silence followed by a constant influx of "please rebas= e >> please rebase please rebase", no useful feedback, and termination with >> "eh, you haven't rebased for the 1001th time, your patch has been WoA >> for X days, we're setting it RwF, feel free to return next year" ... >> they are most certainly off-put and will *not* try again next year. > Right, that is pretty discouraging. It is that. I think that the fundamental problem is that we don't have enough reviewing/committing manpower to deal with all this stuff in a timely fashion. That doesn't seem to have an easy fix :-(. regards, tom lane