MIME-Version: 1.0
References: 
 <CADkLM=c5p2Tgs=9jB5QyDn16H0KSBbBr-stkjhKMbJ6R8-3amw@mail.gmail.com>
In-Reply-To: 
 <CADkLM=c5p2Tgs=9jB5QyDn16H0KSBbBr-stkjhKMbJ6R8-3amw@mail.gmail.com>
From: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Date: Thu, 6 Aug 2026 10:13:08 -0700
Message-ID: 
 <CALj2ACW0XTqJmnvg6Wi1XqHtttGotd51T+qfymdd92RLs5NcNQ@mail.gmail.com>
Subject: Re: Credits For v19
To: Corey Huinker <corey.huinker@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CALj2ACW0XTqJmnvg6Wi1XqHtttGotd51T%2Bqfymdd92RLs5NcNQ%40mail.gmail.com>
Precedence: bulk

Hi,

On Thu, Aug 6, 2026 at 12:10=E2=80=AFAM Corey Huinker <corey.huinker@gmail.=
com> wrote:
>
> I've been working offline on a system for generating the credits for a gi=
ven postgres release, which derives most of its notion of what a name is ba=
sed on what passed for real names in previous year's release credits and th=
e name/email combinations that people use when sending to the hackers list.=
 When names without emails or emails without names are found, it checks to =
see if that name/email was used with a proper pairing elsewhere. From there=
 I can build up correction lists to cover typos and misspellings.

Thanks, Corey, for working on this. I'm curious to see that system for
sure, and I hope it reduces the time we spend on it in future
releases. It used to take 20-30 hours of one's time per Peter
Eisentraut's message:
https://www.postgresql.org/message-id/flat/a49a9219-844e-489c-8f20-0d424545=
b6d8%40eisentraut.org

Incidentally, I spent some time preparing the ack sections using
Claude Code last week and was about to share it (I can share what I've
got from this exercise along with the artifacts if interested). But
I'm happy to see this.

> The obvious gaps created by that sort of a system is that it doesn't imme=
diately recognize first-time contributors, and it doesn't recognize the fir=
st time a typo happens, etc.
>
> To that end, I've compiles three lists:
>
> 1. names that don't yet have a known "preferred name". 9 times out of 10 =
the name is fine, but I'd like to have the community take a pass at correct=
ing name spellings, proper name order, etc. There are 7 of these.

Maybe I can help with some known names/ordering (especially Indian
names and people I have worked with: first name + last name) from
unverified_names.tsv.

Aditya Gollamudi
Aditya Kamath
Ajay Pal
Akshay Joshi
Baji Shaik
Dharin Shah
Dhruv Chauhan
Gaurav Singh
Gyan Sreejith
Kiran Kaki
Kristian Lejao
Lakshmi G
Lakshmi N
Madhukar Prasad

Mohamed Ali (verified emails match with Mohamed ALi):
Mohamed Ali Mohamed Ali moali.pg@gmail.com reportedby latin1
9d3e094f12c https://github.com/postgres/postgres/commit/9d3e094f12cce57a477=
c3df92f411b2fae816b60
kept
Mohamed ALi Mohamed ALi moali.pg@gmail.com author latin1 0916282a060
https://github.com/postgres/postgres/commit/0916282a0606fb788634738bab5b9f0=
bbde2aa08
kept

Naga Appani
Nikhil Kumar Veldanda
Pradeep Kumar
Rambabu V
Rohit Prasad
Sahitya Chandra
Sarath Kumar
Siddharth Kothari
Soumya S Murali
Srirama Kucherlapati

Vasuki M (verified emails match with VASUKI M):
VASUKI M VASUKI M vasukianand0119@gmail.com suggestedby latin1
b977bd308a0 https://github.com/postgres/postgres/commit/b977bd308a09e8a70db=
1776db80e8abd84ca2b7e
kept
Vasuki M Vasuki M vasukianand0119@gmail.com author latin1 344b572e3ef
https://github.com/postgres/postgres/commit/344b572e3eff620ffc2e3680730103e=
33a502bc6
kept

Vaibhav Dalvi
Vaibhav Jain
Vishal Prasanna

Sunil S
sunil s cased Sunil S https://github.com/postgres/postgres/commit/6ca8506ea=
59

Vaibhave Sekar
vaibhave postgres vaibhave postgres postgresvaibhave@gmail.com author
latin1 273d26b75e7
https://github.com/postgres/postgres/commit/273d26b75e78a4811b0c6039c0ee38c=
de2341ce4
kept

Here's what the initial patch from the commit uses:

From 2d438278debf43215e2185611d2f996d09886268 Mon Sep 17 00:00:00 2001
From: Vaibhave Sekar <vsekar@microsoft.com>
Date: Sun, 25 Jan 2026 10:54:00 +0000
Subject: [PATCH] doc: warn about post-data-only schema dumps with parallel
 restore.

> 2. email addresses with no name associated. The program goes through the =
pg-hackers mbox files from 2024 up through last month - so the email being =
in this list is probably a sign that either the email address was erroneous=
, or the sender does not want their name associated. There are 288 of these=
, but I assume a lot of them are duplicates.
>
> 3. Names in preferred_name+variant_name where evidence exists that the pr=
eferred name is the spelling preferred by that person, with additional rows=
 pairing the preferred names with known variations/typos/etc. There are 320=
 of these, but some may be duplicates.
>
> If you did work on v19, your name or email should be in one of those. Che=
ck it out, post corrections and I'll coalesce them. Also, if you expected t=
o see your name (or somebody else's) but don't, reply with the commit hash(=
es) that you feel are in error.

In the generated artifacts that you shared, it would be nice to have
commit IDs for other hackers to quickly refer to and verify. But
that's okay, reviewers can check it anyway with git logs.

--
Bharath Rupireddy
Amazon Web Services: https://aws.amazon.com