On Thursday 09 April 2009 11:45:32 pm Alberto Passalacqua wrote:
Hi,
Il giorno ven, 03/04/2009 alle 19.39 +0200, jdd ha scritto:
Rajko M. a écrit :
It appear, from many posts on mail lists, as urgent need to organize effort on bug solving, so I propose to create team of people willing to work on that.
isn't that doubling the testing team? jdd
I actually have the same feeling. There is a lot of overlap with the activities of a testing team.
Of course the testing team won't look for bugs in ML and try to convince developers to fix them if not reported on bugzilla in a proper manner, and I don't think this is worth the effort because you need direct feedback by the person affected by the bug in most of the cases.
However, the testing team should also, but of course it depends on the number of people involved, prepare some tutorial to explain how to produce useful bugreports. All this was explained in my slides, when I proposed the testing team creation, so I invite you to re-read them.
Best regards, A.
I didn't mention, but BugBusters should be a shim layer between certain class of users and bugzilla, or better to say developers. For large class of users, words "report a bug", is the same as "fix it". They don't know how to do it. Reasons: 1) Bugzilla is not the friendliest face in computing. UI needs serious work to be brought to that level. Recent improvements are the way to go. 2) Missing clicky pointy tools to collect for debuggers (developers) useful information. Now you have to know how run few utilities that are far beyond average computer user today. 3) Smolt as a hardware information collector can be useful to some extent, but it is not mentioned anywhere. The siga is not mentioned either. 4) As mentioned few times developers have no time to explain everything. Current state of mind is that if I, as a helper, can't reproduce bug, I should not report it, because I can't give any info without going back and fort between ML and bugzilla. In case that I (nor anyone else) can't tell user what to do, and I have no place where to put request for help (ie. escalate case), then user is on his own, unless developers hang on ML. I don't see much duplication of the Testing Team purpose. The comment about splitting the body volunteer users, that is just to some extent correct. Most of the people that help other can do testing, but they do that sporadically, just as those that do testing most of the time sporadically help in forums and ML. They are 2 mind sets that have completely different goals. Fact that they do the other thing from time to time, is just to avoid boredom. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org