On 7/9/06, Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxxx> wrote:
On Sun, 2006-07-09 at 19:12 -0400, Jesse Keating wrote: > > Really there are two issues.
And that brings up 3. 3) Communication on such things with the community. The above is a perfectly valid statement as to why RPM has not been upgraded in Core. Why couldn't someone simply add a comment to the bug saying so? Instead, it was left completely unanswered until it turned into the flamefest it is now.
I can tell from longer history, that this has come up in 'lessons learned' since at least 1998.. and keeps coming up. It has always been "next time we will communicate better" but something always comes up and there is always a good list of reasons why communication broke down again (lack of people, extra demands on engineers, etc.). At this point, I would have to say the problem needs serious management power aimed at it with it being put as a priority. A developer can only deal with so many issues (features, bugs, packages, upstream communication, downstream communication) and the company has to manage that number or it will end up with burnt out developers, poor community relations, and tanking sales. I think this is from the Navy SeaBees: The engineers will forget that they are draining a swamp.. it is up to management to prioritize which alligators get shot. -- Stephen J Smoogen. CSIRT/Linux System Administrator _______________________________________________ fedora-advisory-board mailing list fedora-advisory-board@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-advisory-board _______________________________________________ fedora-advisory-board-readonly mailing list fedora-advisory-board-readonly@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-advisory-board-readonly
