Re: new commitfest transition guidance

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Aleksander Alekseev <aleksander(at)timescale(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Jacob Brazeal <jacob(dot)brazeal(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Tomas Vondra <tomas(at)vondra(dot)me>, Jeff Davis <pgsql(at)j-davis(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>
Subject: Re: new commitfest transition guidance
Date: 2025-02-19 15:19:44
Message-ID: 2012753.1739978384@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Aleksander Alekseev <aleksander(at)timescale(dot)com> writes:
>> On Feb 19, 2025, at 10:02 AM, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>>> The opposite, which was discussed at length at FOSDEM, was to ask authors to
>>> click a single button once a month at most. If that level of engagement is too
>>> much to ask then maybe said authors should question why they in return ask
>>> others to spend hours reviewing?

>> Exactly this.

> True, but didn't we just discover that it doesn't work?

I think what we discovered is that the amount of effort that was put
into *notifying authors of this new requirement* was woefully
inadequate. One email thread within the firehose that is
pgsql-hackers doesn't cut it.

How about having the cfbot send out some nagmail to patch authors,
saying "please move your patch forward, or close it if no longer
interested"? If nothing happens after a few rounds of that,
an auto-close could be justified.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksander Alekseev 2025-02-19 15:24:19 Re: new commitfest transition guidance
Previous Message Aleksander Alekseev 2025-02-19 15:13:51 Re: new commitfest transition guidance