On Sun, 2006-07-09 at 20:46 -0600, Stephen John Smoogen wrote: > 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 have a problem with this statement. This issue was brought to the board on friday. We've had all of 2 days to discuss and I'd like for there to be a board meeting before we make a final statement. It's hard to communicate an answer to a problem when we didn't really know there was one. Its one package out of what? 3000? And it's one bug out of 150K? How do you think this should have been handled? A problem has been happening in a bug in bugzilla The maintainer didn't know what the best answer was so he brought it to the board We've been discussing it and will come up with something shortly. why is this not communicating? How did we fail to communicate? -sv _______________________________________________ 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
