On Mon, 13 Jan 2003, Kamil Toman wrote: >Bugzilla may help a bit (if it was activelly maintained). I >don't expect bugreports regarding x-protocol.
Indeed, such type of bug report is extremely rare. >I'm quite sure that most of reports would concern drivers. I can back that up with my own experience. Almost all bug reports that come into our database are either: 1) Driver related 2) Configuration related 3) App related There are other bug categories too of course, and it would be interesting to divide up X into different categories, then go through and get statistics on those categories. >The plus is that such bugreports can be easily categorized (per >driver) and seen only by interested people (driver maintainer, >contributors and maybe some power-users), another that (at least >some) people will stop asking about the same all over again >(there are even volunteers outside projects who often help >marking duplicates and nonsential bugreports). More general >reports could be forwarded elsewhere. Yep. That is basically what I see on a day to day basis. >Another point of view: Bugzilla can be thus seen (and used!) as >an email filter + advanced search. Thus (if set properly!) can >substantively reduce the amount of mail a >developer/maintainer/contributor of a smaller part has to skim >through. Of course, you could subscribe into many smaller lists >than devel but who does it (especially if the chance of any >response is smaller?) There are also people who do care about a >particular bug only... Indeed. Some developers just read the bugzilla emails, and prefer to work with stuff in that context, only using the web interface when they need to. I use both myself. I sometimes use my email folder for quick searches, and to flag bug reports in pine with a * for looking at later today. There are many ways of using the tool though as there are developers that use it. ;o) -- Mike A. Harris _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
