Re: code contributions for 2024, WIP version

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: code contributions for 2024, WIP version
Date: 2024-12-05 16:43:49
Message-ID: CA+TgmoYnJooP6r3XH3BXzP-Az4Tn_aqUDyLfrCT5zi_0apfaTQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 5, 2024 at 11:19 AM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> Just give credit to all lines for all authors, would be my approach. Is
> that unfair? Perhaps, but I'd rather err on the side of giving too much
> credit, than on not giving enough.

I'm not against somebody putting that together, but I don't think it
would be useful for me. I think it would inflate the numbers for
committers by quite a lot more than what is fair, because if I commit
a 1000 line patch and I add 50 lines of code, I'm going to get an
awful lot more credit than I deserve. It would probably also inflate
or distort the numbers for some other people as well. But what I would
say is -- if you think it's a useful thing, try doing it.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message James Hunter 2024-12-05 16:46:45 Re: Possible integer overflow in bringetbitmap()
Previous Message Bruce Momjian 2024-12-05 16:42:36 Re: code contributions for 2024, WIP version