Stephen John Smoogen wrote:
why is this not communicating? How did we fail to communicate?
Ok the issue for me is trying to say that communication delays/failure
have been a long term problem. Each time a new organization management
comes in and says they will deal with it but seem to focus on the
particular crisis versus the entire problem. Then a new group comes in
and we repeat, lather, rinse. I should have phrased my earlier email
differently, but what I am trying to do is act as a memory unit:
Bugs take a long time to get interaction, people get pissed, community
problems surface, and 'management' reacts. In this case, management
realizes this has occured in the past, and can 'act' in a way to study
and cure the larger problem versus one aimed at specifically at RPM.
Does that clear up what I am trying to say?
We already know that bugzilla feedback is far from ideal. We have a QA
lead now to lead this triaging effort and we need many more from the
community to contribute. The only way to fix that problem is to
participate and help.
Still, having a bugzilla report filed on 2005-11-27 go without a single
response from the package owner till date is not very reasonable and
Fedora Board cannot micro manage at this level.
Rahul
_______________________________________________
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
