Re: Experimental tool to explore commitfest patches

From: Akshat Jaimini <akshatjpostgresql(at)gmail(dot)com>
To: Jacob Brazeal <jacob(dot)brazeal(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, robertmhaas(at)gmail(dot)com, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
Subject: Re: Experimental tool to explore commitfest patches
Date: 2025-02-24 05:03:08
Message-ID: CAO8Bkb6-Rx+eqZyTLwOOQpos43CMJiem0E_NU1xYgc6Nid8aSw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Jacob,

Thanks a lot for this! We have been trying to come up with a similar
feature for the new commitfest app [0].

> If we like this, I'm happy to help port a version of it over to the
commitfest app.

I would love to help you out in porting this to the commitfest app.

Regards,
Akshat Jaimini

[0] https://github.com/postgres/pgcommitfest/issues/18

On Mon, Feb 24, 2025 at 9:01 AM Jacob Brazeal <jacob(dot)brazeal(at)gmail(dot)com>
wrote:

> Hi all,
>
> I have created an experimental tool [0] to help explore the vast depths of
> the upcoming commitfest, and it's designed to help each contributor find
> actually useful and relevant patches to review. Please have a look!
>
> Under the hood, it does two things:
>
> 1. Use a good LLM [1] to analyze all the mailing threads tied to the
> commitfest. This gives us a summary of the thread, a summary of the main
> blocker, if any, and a gut-check on whether we actually need a new reviewer
> in the thread. It also gives a first-principles read on the actual status:
> are we waiting for the author to make changes, for a reviewer to respond,
> etc.
> 2. Cross-reference the files in the patches to the personal commit history
> of everyone in the postgres project. In this way, using a variant of the
> classic TF-IDF algorithm [2], we can score how close the patch lies to each
> contributor's usual territory. It's only a heuristic, but seemed well worth
> trying.
>
> The data pipeline for this is run on my personal laptop at the moment.
> I've just refreshed everything but, of course, the various statuses and
> analyses need to be re-run reasonably often to remain useful. It only costs
> a dollar or two to run everything through the LLM, and I can probably
> optimize what really needs to be processed, but this is worth considering
> if there is broader interest. If we like this, I'm happy to help port a
> version of it over to the commitfest app.
>
> Here is the source code for the whole app [3].
>
> Regards,
> Jacob Brazeal
>
> [0] https://patchwork-three.vercel.app/
> [1] https://deepmind.google/technologies/gemini/flash/
> [2] https://en.wikipedia.org/wiki/Tf%E2%80%93idf
> [3] https://github.com/polkerty/patchwork
>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-02-24 05:16:04 Re: psql \dh: List High-Level (Root) Tables and Indexes
Previous Message John Naylor 2025-02-24 04:51:22 Re: Parallel heap vacuum