Stephen Frost wrote:
I agree with this- one issue is, unfortunately, an overabundance from
KaiGai of "code-writing man-power". This is an odd situation for this
community, in general, so we're having a hard time coming to grasp with
it.
There are plenty of parallels to when Zdenek was writing a ton of
in-place upgrade code faster than anyone else was fully consuming it.
The "do it right or don't do it at all" approach of the PG community
seems particularly hard to reconcile with larger patches from people we
don't get enough face time with. It's easy to get deadlocked and not
have a good way to navigate out when faced with a set of difficult
decisions and only electronic communications between participants.
Shoot, you and Robert have spent time doing technical arguments in
person and we still got a
little rough patch on-list this week out of the debate. I hate to even
use this terminology, but these big patches seem to need a project
manager advocate sometimes: someone who knows everyone well enough to
clear these stalled spots, smooth over any personality conflicts, and is
motivated to intervene because they need the feature. I see it as a
sort of scaling problem that might be a recurring one. It would be nice
if we could all get better at identifying when it does happen, and
perhaps find someone to help with planning before we waste so much time
chasing code that isn't going to be accepted yet again.
--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
