public inbox for [email protected]  

help / color / mirror / Atom feed

From: Joe Conway <[email protected]>
To: Tom Lane <[email protected]>
To: 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 16:31:01 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CA+TgmobnTcNq1xQE_+jxBEtj+AjKg0r_p5YNFHDE+EDnpcpFxA@mail.gmail.com>
	<[email protected]>
	<[email protected]>

On 5/16/24 15:47, Tom Lane wrote:
> Daniel Gustafsson <[email protected]> writes:
>>> On 16 May 2024, at 20:30, Robert Haas <[email protected]> wrote:
>>> The original intent of CommitFests, and of commitfest.postgresql.org
>>> by extension, was to provide a place where patches could be registered
>>> to indicate that they needed to be reviewed, thus enabling patch
>>> authors and patch reviewers to find each other in a reasonably
>>> efficient way. I don't think it's working any more.
> 
>> But which part is broken though, the app, our commitfest process and workflow
>> and the its intent, or our assumption that we follow said process and workflow
>> which may or may not be backed by evidence?  IMHO, from being CMF many times,
>> there is a fair bit of the latter, which excacerbates the problem.  This is
>> harder to fix with more or better software though. 
> 
> Yeah.  I think that Robert put his finger on a big part of the
> problem, which is that punting a patch to the next CF is a lot
> easier than rejecting it, particularly for less-senior CFMs
> who may not feel they have the authority to say no (or at
> least doubt that the patch author would accept it).

Maybe we should just make it a policy that *nothing* gets moved forward 
from commitfest-to-commitfest and therefore the author needs to care 
enough to register for the next one?

>>> I spent a good deal of time going through the CommitFest this week
> 
>> And you deserve a big Thank You for that.
> 
> + many

+1 agreed

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

view thread (10+ messages)  latest in thread

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]
  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