public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Thomas Munro <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: Justin Pryzby <[email protected]>
Cc: Peter Geoghegan <[email protected]>
Cc: Greg Stark <[email protected]>
Cc: Gregory Stark (as CFM) <[email protected]>
Cc: Michael Paquier <[email protected]>
Cc: [email protected]
Subject: Re: Commitfest 2023-03 starting tomorrow!
Date: Wed, 22 Mar 2023 02:30:11 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+hUKGK=7mTwheXRfxz=bD47+m7WUa2xWmce0EfoycsfRN98wg@mail.gmail.com>
References: <CA+hUKGKat8ao++a=EeFiPWnoWFe9r979heYpnomgq01=Qzdu4w@mail.gmail.com>
	<[email protected]>
	<CA+hUKGK=7mTwheXRfxz=bD47+m7WUa2xWmce0EfoycsfRN98wg@mail.gmail.com>

Thomas Munro <[email protected]> writes:
> On Tue, Mar 21, 2023 at 10:59 PM Alvaro Herrera <[email protected]> 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

view thread (3+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Commitfest 2023-03 starting tomorrow!
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox