public inbox for [email protected]  

help / color / mirror / Atom feed

From: Joe Conway <[email protected]>
To: Jacob Champion <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Daniel Gustafsson <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: commitfest.postgresql.org is no longer fit for purpose
Date: Thu, 16 May 2024 17:29:23 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAOYmi+kahznR7NKONCPs-ESz8ZzgMuFUNen8taFtpXs9uj-5dw@mail.gmail.com>
References: <CA+TgmobnTcNq1xQE_+jxBEtj+AjKg0r_p5YNFHDE+EDnpcpFxA@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<CAOYmi+=FSh3_bhO_PAFMy5+NeHm59Re9vgNGrcdUbOO=bZDmbA@mail.gmail.com>
	<[email protected]>
	<CAOYmi+kahznR7NKONCPs-ESz8ZzgMuFUNen8taFtpXs9uj-5dw@mail.gmail.com>

On 5/16/24 17:24, Jacob Champion wrote:
> On Thu, May 16, 2024 at 2:06 PM Joe Conway <[email protected]> wrote:
>> Maybe the word "care" was a poor choice, but forcing authors to think
>> about and decide if they have the "time to shepherd a patch" for the
>> *next CF* is exactly the point. If they don't, why clutter the CF with it.
> 
> Because the community regularly encourages new patch contributors to
> park their stuff in it, without first asking them to sign on the
> dotted line and commit to the next X months of their free time. If
> that's not appropriate, then I think we should decide what those
> contributors need to do instead, rather than making a new bar for them
> to clear.

If no one, including the author (new or otherwise) is interested in 
shepherding a particular patch, what chance does it have of ever getting 
committed?

IMHO the probability is indistinguishable from zero anyway.

Perhaps we should be more explicit to new contributors that they need to 
either own their patch through the process, or convince someone to do it 
for them.

-- 
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

view thread (10+ 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]
  Subject: Re: commitfest.postgresql.org is no longer fit for purpose
  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