On Mon, 24 Mar 2003, Mantas [ISO-8859-13] Kriaučiūnas wrote: > Maybe I should report bugs and suggestions to http://tux4kids.net/bugs/ (mailing > list isn't a good place to trace bugs for pretty big program like tuxpaint) ? > I still think that bugzilla is better solution, because it contains more features > and is easier to use than CVSTrac and my friend can setup bugzilla for tux4kids if > tux4kids developers don't have time.
the reason we picked cvstraq over bugzilla is because bugzilla is so massive and too featureful. for smaller projects like the ones we have in tux4kids, bugzilla becomes a nightmare to maintain. cvstraq is simple and integrated into cvs, so developers can close or reference open bugs within their cvs changelogs. as to the argument that bugzilla is easier to use, i would contend that. tux typing used bugzilla for years, and few people ever used it. the end users never submitted bugs there in spite of the fact that it was clearly linked from the website (it no longer is, but it was for years) anything that went into bugzilla would typically disappear forever. bugzilla is such a high-ceremony bug tracking suite that it's just too unwieldy for such small individual projects. cvstraq is so low-ceremony that it requires little more than knowing a bug's ID to close it in your cvs checkin. the original idea behind the bug tracking group in tux4kids was that there would be a mailing list where people would post new bugs for tux4kids apps to. the subscribers on that list would then enter the bugs into cvstraq and notify the project administrators. the project administrators could choose to ignore the bug and close it (the bug was not-applicable or something similar), work on it, etc. ----------- Jacob Greig [EMAIL PROTECTED] http://tux4kids.net/~bombastic/ _______________________________________________ Tuxpaint-dev mailing list [EMAIL PROTECTED] http://tux4kids.net/mailman/listinfo/tuxpaint-dev
