Re: Commitfest 2023-03 starting tomorrow! - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Commitfest 2023-03 starting tomorrow!
Date
Msg-id 1443465.1679466611@sss.pgh.pa.us
Whole thread Raw
In response to Re: Commitfest 2023-03 starting tomorrow!  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
Thomas Munro <thomas.munro@gmail.com> writes:
> On Tue, Mar 21, 2023 at 10:59 PM Alvaro Herrera <alvherre@alvh.no-ip.org> 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 rebase
>> 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



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Add pg_walinspect function with block info columns
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Data is copied twice when specifying both child and parent table in publication