[hafqa] [hafqa] [Bug 630] Increased Bugzilla transparency - get the developers involved!

[From: bugzilla-daemon at maemo.org]

https://maemo.org/bugzilla/show_bug.cgi?id=630





------- Additional Comments From timeless at gmail.com  2006-11-22 00:04 -------
communities are hard. maybe this one will grow. from my perspective it helps if
people file good bugs that enable developers to query for useful things and
enable reports to quickly get pushed to developers who look at them.

Engineers always hate playing ping pong, and the more need there is for ping
pong, the more likely it is that one side or another (you have at least four:
reporter, qa gateway, qa, engineer) lose the ball.

probably the most important thing is to make the public bugzilla more appealing
than the private one (the less reasons engineers working on open source have to
use a private thing, the more likely they'll use the public thing, but the
current reason would presumably be management and requirements and planning
things). I think that netscape (home of Bugscape) managed the transition because
they were able to have more and better bugs from contributors and had QA they
could use externally to file public bugs and such.

Unfortunately at the moment it seems that the QA available here really is the
two people identified by reference.

If volunteers (1) helped clean up bugs to make them more palatable, (2) checked
bugs that were claimed to be fixed, and perhaps (3) picked up some of the QA
work for whichever pieces are open, that'd be a series of steps in the right
direction. Perhaps it might even draw more developers to this bugzilla.

Certain kinds of people can't be allowed to disclose some information.


-- 
Configure bugmail: https://maemo.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.