Re: commitfest.postgresql.org is no longer fit for purpose - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: commitfest.postgresql.org is no longer fit for purpose
Date
Msg-id ZkkweySU1ryKdCbD@momjian.us
Whole thread Raw
In response to Re: commitfest.postgresql.org is no longer fit for purpose  (Melanie Plageman <melanieplageman@gmail.com>)
List pgsql-hackers
On Fri, May 17, 2024 at 11:44:40AM -0400, Melanie Plageman wrote:
> So, anyway, I'd argue that we need a parking lot for patches which we
> all agree are important and have a path forward but need someone to do
> the last 20-80% of the work. To avoid this being a dumping ground,
> patches should _only_ be allowed in the parking lot if they have a
> clear path forward. Patches which haven't gotten any interest don't go
> there. Patches in which the author has clearly not addressed feedback
> that is reasonable for them to address don't go there. These are
> effectively community TODOs which we agree need to be done -- if only
> someone had the time.

When I am looking to commit something, I have to consider:

*  do we want the change
*  are there concerns
*  are the docs good
*  does it need tests
*  is it only a proof-of-concept

When people review commit fest entries, they have to figure out what is
holding the patch back from being complete, so they have to read the
thread from the beginning.  Should there be a clearer way in the commit
fest app to specify what is missing?

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.



pgsql-hackers by date:

Previous
From: Ole Peder Brandtzæg
Date:
Subject: Re: Requiring LLVM 14+ in PostgreSQL 18
Next
From: Thomas Munro
Date:
Subject: Re: speed up a logical replica setup