John Du Hart <compwhizii(a)gmail.com> writes:
Fair enough. I think what I'm looking for is a bug
tracker that is more
easier to use for both developers and users. I would also like tools that
allow us to better visualize progress on bugs and what's fixed or needed
for a released. Finally an API that doesn't suck would be nice
I'm not about to argue for the user-friendliness of Bugzilla or
visualization that it offers. However, I have used the API extensively
and, while I do agree that there are areas it could be improved, I've
found it useful for most things.
Hack-ability is a big benefit here. Lots of other people use Bugzilla
and adapt it to their needs. Some of those changes get incorporated
into the core.
Mozilla, for instance, created MediaWiki integration that might help
with visualization:
http://lawrencemandel.com/2012/02/23/embed-bugzilla-data-in-wikimo-pages/
(This was later disabled because of the load on Bugzilla, but I think it
is a start. See <https://bugzilla.mozilla.org/731672>.)
And the Mozilla has certainly shown that Bugzilla's UI (at least for
entering bugs, which is the biggest pain point for for new users) can be
made better.
I don't think Bugzilla is the best it could possibly be.
But, I do think there is the problem of known pain (Bugzilla) versus
the unknown pain that will come with learning a new system and then
adapting to its quirks and inadequacies.
I would rather use the energy to adapt Bugzilla to our needs.
Proprietary
software as well.
Like I replied earlier, this is not a major concern.
I think you'll find quite a lot of resistance from me on this point.
--
Mark A. Hershberger
Bugmeister
Wikimedia Foundation
mah(a)wikimedia.org