From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Greg Stark <stark(at)mit(dot)edu>, "Gregory Stark (as CFM)" <stark(dot)cfm(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Commitfest 2023-03 starting tomorrow! |
Date: | 2023-03-22 06:30:11 |
Message-ID: | 1443465.1679466611@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> On Tue, Mar 21, 2023 at 10:59 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Hayato Kuroda (Fujitsu) | 2023-03-22 06:31:50 | RE: Data is copied twice when specifying both child and parent table in publication |
Previous Message | Michael Paquier | 2023-03-22 06:22:14 | Re: Add pg_walinspect function with block info columns |