Re: Commitfest II CLosed

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, David Fetter <david(at)fetter(dot)org>, Boszormenyi Zoltan <zb(at)cybertec(dot)at>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Commitfest II CLosed
Date: 2013-10-22 19:38:20
Message-ID: 5266D42C.7080400@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 10/21/2013 08:11 AM, Robert Haas wrote:

> Supposedly, we have a policy that for each patch you submit, you ought
> to review a patch. That right there ought to provide enough reviewers
> for all the patches, but clearly it didn't. And I'm pretty sure that
> some people (like me) looked at a lot MORE patches than they
> themselves submitted. I think auditing who is not contributing in
> that area and finding tactful ways to encourage them to contribute
> would be a very useful service to the project.

What if as part of the patch submission process you had to pick the
patch you were going to review? If there are no patches to review, then
we obviously don't have a problem. If there are patches to review then
we are all set.

I guess there is the problem of there only being patches that a
submitter is not qualified to review but I find that miniscule as every
person on this list (myself included) can do a cursory review (patch
applies, docs are good, indentation is appropriate, works as advertised).

The commitfest app would have to be modified for this but what do people
think?

Joshua D. Drake

--
Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms
a rose in the deeps of my heart. - W.B. Yeats

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-10-22 19:40:30 Re: Reasons not to like asprintf
Previous Message Heikki Linnakangas 2013-10-22 19:37:33 Re: Failure while inserting parent tuple to B-tree is not fun