Re: Commitfest problems - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: Commitfest problems
Date
Msg-id 548B5C82.6010708@BlueTreble.com
Whole thread Raw
In response to Re: Commitfest problems  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Commitfest problems
List pgsql-hackers
On 12/12/14, 1:44 PM, Joshua D. Drake wrote:
> 1. We don't need a full-time engineer to manage a commitfest. We need a manager or PM.

I don't think that's actually true. The major points on this thread are that 1) we don't have enough capacity for doing
reviewsand 2) the CFM has no authority to enforce anything.
 

I see no way that #2 can be addressed by a mere manager/PM. If three *very* senior community members (David, Josh and
Robert)couldn't get this done there's no way a PM could. (Well, I suppose of Tom was standing behind them with a
flamingsword it might work...)
 

Even so, this still wouldn't address the real problem, which is lack of review capacity.

FWIW, I faced the same problem at Enova: good, solid reviews were very important for maintaining the quality of the
dataand database code, yet were a constant source of pain and friction. And that was with people being paid to do them,
aswell as a very extensive set of unit tests.
 

In other words, this isn't an easy problem to solve.

One thing that I think would help is modifying the CF app to allow for multiple reviewers. IIRC I reviewed 4 or 5
patchesbut I didn't mark myself as reviewer of any of them because I don't feel I have enough knowledge to fulfill that
role.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: PATCH: hashjoin - gracefully increasing NTUP_PER_BUCKET instead of batching
Next
From: Jim Nasby
Date:
Subject: Re: On partitioning