Re: code contributions for 2024, WIP version - Mailing list pgsql-hackers
From | Alvaro Herrera |
---|---|
Subject | Re: code contributions for 2024, WIP version |
Date | |
Msg-id | 202412051246.74n5he3vdu4m@alvherre.pgsql Whole thread Raw |
In response to | code contributions for 2024, WIP version (Robert Haas <robertmhaas@gmail.com>) |
Responses |
Re: code contributions for 2024, WIP version
Re: code contributions for 2024, WIP version |
List | pgsql-hackers |
Hello Robert, On 2024-Dec-02, Robert Haas wrote: > As many of you are probably aware, I have been doing an annual blog > post on who contributes to PostgreSQL development for some years now. > It includes information on lines of code committed to PostgreSQL, and > also emails sent to the list. This year, I got a jump on analyzing the > commit log, and a draft of the data covering January-November of 2024 > has been uploaded in pg_dump format to here: > > https://sites.google.com/site/robertmhaas/contributions > > I'm sending this message to invite anyone who is interested to review > the data in the commits2024 table and send me corrections. No corrections here -- I noticed nothing wrong with the commits I am involved with, in a quick read. I did notice that for patches with multiple authors, only the first one is listed. For instance, 53c2a97a926's author ("Improve performance of subsystems on top of SLRU") is listed as Andrey Borodin, leaving Dilip Kumar out. I realize that addressing this would complicate the schema and queries, but maybe it's worth thinking about for next time. We have plenty of patches with multiple authors, after all. Hmm, maybe UPDATE commits2024 SET xlines = 0 WHERE commitid in ('43ce181059d', '4632e5cf4bc', '6377e12a5a5', 'ff9f72c68f6', '21ef4d4d897', '592a2283721'); How did you come up with the 'lines' number for each commit anyway? Judging by 592a2283721 it's not just the number of lines added, since that commit added 3 lines and you have lines=2. An unrelated (and possibly useless) thing is that some committers seem firmly in the camp of ending commit titles with a period, others are firmly in the other camp; only two people seem not to have made up their minds about that: committer │ with end period │ without end period │ fraction with end period ────────────────────┼─────────────────┼────────────────────┼────────────────────────── Etsuro Fujita │ 6 │ 0 │ 100.00 Peter Geoghegan │ 39 │ 0 │ 100.00 Tatsuo Ishii │ 8 │ 0 │ 100.00 Amit Kapila │ 87 │ 0 │ 100.00 Fujii Masao │ 35 │ 0 │ 100.00 Tom Lane │ 296 │ 1 │ 99.66 Nathan Bossart │ 131 │ 1 │ 99.24 Jeff Davis │ 88 │ 1 │ 98.88 Noah Misch │ 61 │ 1 │ 98.39 Thomas Munro │ 59 │ 1 │ 98.33 Masahiko Sawada │ 39 │ 1 │ 97.50 Dean Rasheed │ 23 │ 1 │ 95.83 Robert Haas │ 77 │ 10 │ 88.51 Joe Conway │ 1 │ 2 │ 33.33 Alexander Korotkov │ 4 │ 153 │ 2.55 Andrew Dunstan │ 1 │ 40 │ 2.44 Bruce Momjian │ 2 │ 82 │ 2.38 Heikki Linnakangas │ 4 │ 174 │ 2.25 Peter Eisentraut │ 6 │ 309 │ 1.90 Amit Langote │ 1 │ 54 │ 1.82 Álvaro Herrera │ 1 │ 118 │ 0.84 Michael Paquier │ 1 │ 275 │ 0.36 Andres Freund │ 0 │ 26 │ 0.00 Richard Guo │ 0 │ 27 │ 0.00 Daniel Gustafsson │ 0 │ 99 │ 0.00 Magnus Hagander │ 0 │ 4 │ 0.00 John Naylor │ 0 │ 33 │ 0.00 Melanie Plageman │ 0 │ 6 │ 0.00 David Rowley │ 0 │ 106 │ 0.00 Tomas Vondra │ 0 │ 33 │ 0.00 Query was: select committer, count(*) filter (where subject like '%.') as "with end period", count(*) filter (where subject not like '%.') "without end period", ((count(*) filter (where subject like '%.'))::numeric / count(*) * 100)::numeric(5,2) as "fraction with end period" from commits2024 group by committer order by 4 desc, split_part(committer, ' ', 2); Thanks! -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/ "The problem with the facetime model is not just that it's demoralizing, but that the people pretending to work interrupt the ones actually working." -- Paul Graham, http://www.paulgraham.com/opensource.html
pgsql-hackers by date: