Re: Commitfest Update - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Commitfest Update
Date
Msg-id 0a042e06-057c-2e56-b00c-fb690240df64@timescale.com
Whole thread Raw
In response to Re: Commitfest Update  (Jacob Champion <jchampion@timescale.com>)
List pgsql-hackers
On 7/18/22 06:13, Justin Pryzby wrote:
> On Mon, Jul 18, 2022 at 03:05:51PM +0200, Alvaro Herrera wrote:
>> Maybe we should have two reviewers columns -- one for history-tracking
>> purposes (and commit msg credit) and another for current ones.
> 
> Maybe.  Or, the list of reviewers shouldn't be shown prominently in the list of
> patches.  But changing that would currently break cfbot's web scraping.

I think separating use cases of "what you can currently do for this
patch" and "what others have historically done for this patch" is
important. Whether that's best done with more columns or with some other
workflow, I'm not sure.

It seems like being able to mark items on a personal level, in a way
that doesn't interfere with recordkeeping being done centrally, could
help as well.

--Jacob




pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: Commitfest Update
Next
From: Martin Kalcher
Date:
Subject: [PATCH] Introduce array_shuffle() and array_sample()