Re: [9.4 CF 1] The Commitfest Slacker List

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-Dev <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [9.4 CF 1] The Commitfest Slacker List
Date: 2013-06-24 17:48:32
Message-ID: CAGTBQpZ6mHye6fxD9qMWJA1oJ3VGp4wf+ZBP4FJhyTtk2n5eXw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 24, 2013 at 2:41 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>> I don't like idea of sending gifts. I do like the idea of public thanks. We
>> should put full recognition in the release notes for someone who reviews a
>> patch. If they didn't review the patch, the person that wrote the patch
>> would not have gotten the patch committed anyway. Writing the patch is only
>> have the battle.
>>
>> Heck, think about the FKLocks patch, Alvaro wrote that patch but I know that
>> Noah (as well as others) put a herculean effort into helping get it
>> committed.
>>
>> Reviewer recognition should be on the same level as the submitter.
>
> The problem with that is that that HUGELY depends on the patch and the
> review. There are patches where reviewers do a good percentage of the
> work and others where they mostly tell that "compiles & runs".

Well, you can't so arbitrarily pick who you're recognizing as
contributor and who you aren't. So why not mention them all? They did
work for it, some more than others, but they all worked. And since
whoever submitted a patch (and got it committed) must have reviewed
something as well, they'd be recognized for both reviewing and
submitting.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2013-06-24 17:50:42 Re: [9.4 CF 1] The Commitfest Slacker List
Previous Message Josh Berkus 2013-06-24 17:46:52 Re: [9.4 CF 1] The Commitfest Slacker List