Feedback-ID: ie0a040ee:Fastmail
Message-ID: <4c3ed20a-e2db-463f-829f-deef59e4e739@eisentraut.org>
Date: Fri, 21 Mar 2025 17:41:03 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Next commitfest app release is planned for March 18th
To: Jelte Fennema-Nio <me@jeltef.nl>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
 Peter Geoghegan <pg@bowt.ie>, Maciek Sakrejda <m.sakrejda@gmail.com>
References: 
 <CAGECzQR8oAaA2dFbE76-0s3f-Dgb4BJ4h1piux99QkHcmYqdTQ@mail.gmail.com>
 <CAGECzQR4F_3bp4ofxseZCtzkiSOKbGzb+unsNsYkq2tEQK5KPA@mail.gmail.com>
Content-Language: en-US
From: Peter Eisentraut <peter@eisentraut.org>
In-Reply-To: 
 <CAGECzQR4F_3bp4ofxseZCtzkiSOKbGzb+unsNsYkq2tEQK5KPA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/4c3ed20a-e2db-463f-829f-deef59e4e739%40eisentraut.org>
Precedence: bulk

On 17.03.25 23:11, Jelte Fennema-Nio wrote:
> 1. Major change: There's a new /me page which shows a dashboard of
> open patches where you are author/reviewer/committer. These patches
> are ordered & grouped in a hopefully useful way. Peter Geoghegan
> suggested adding a "dashboard" of this kind. It's the first attempt
> and can probably use some fine tuning based on feedback.

Thanks, this is very promising.

I have a few pieces of feedback that could be addressed by additional 
rules for how things are listed in the dashboard:

- If I'm the committer for a patch but not a reviewer, and the patch is 
in "needs review" status, then the patch is formally speaking not 
actionable by me and should not be under "Patches that are ready for 
your review".  Perhaps it should be under "Blocked on others" [namely 
the reviewers], or in a different category.

- Conversely, if I'm the reviewer for a patch but not the committer, and 
the patch is in "ready for committer" status, then it's also not 
"Patches that are ready for your review".  This might similarly be 
"Blocked on others" [namely the committer].

- Also, my dashboard shows patches from past and future commitfests.  I 
don't know what I'm supposed to do with that.  The purpose of having a 
"current" commitfest is that you work on that one when it's current. 
The patches in past and future commitfests were presumably put there for 
reasons that mean that they are not currently to be worked on as a priority.

(I'm probably not representative, but my current dashboard has a 
somewhat low hit ratio because of the above points.)