From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Joe Conway <mail(at)joeconway(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Commitfest problems |
Date: | 2014-12-12 22:16:51 |
Message-ID: | 548B6953.5030705@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/12/2014 01:22 PM, Jim Nasby wrote:
>
> 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 reviews and 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 flaming sword it might work...)
#2 is solved by my previous comments about giving the CFM/C the
authority. -Core could do that, they are in charge of release.
#1 is a more difficult problem for sure.
JD
--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, @cmdpromptinc
"If we send our children to Caesar for their education, we should
not be surprised when they come back as Romans."
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2014-12-12 22:17:49 | Re: Commitfest problems |
Previous Message | Claudio Freire | 2014-12-12 22:14:29 | Re: On partitioning |