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
