On 02/11/2013 11:15 PM, Fons Adriaensen wrote:
Something doesn't add up here. Entering a bug in a tracker, if you use one, is the first of*many* actions in the process of fixing it. It's not the most time consuming one. If this tiny part of the process is already overwhelming, what about the rest ?
Writing a good bug report can easily take 10 minutes or more. Plus every developer should know the cost of a context switch.
Chances of a "report" happening via IRC or email already being well structured and complete are lower, as the tracker interface will include certain hints and brings a certain context/perspective to mind.
A developer of a long running, highly complex project will usually have a virtually unlimited amount of work to do. Filing tickets that users could file is a very inefficient use of valuable time.
If a user want a bug fixed, it's in their interest to file it properly and to not waste a developers time. There are of course cases, where talking to a developer first is better, say when it's not clear if it's a bug or a feature, or when hunting a heisenbug. I don't know any developer who would be more approachable, helpful and patient than Paul Davis in such cases (as mad as he made me in design matters, sometimes ;)).
-- Thorsten Wilms thorwil's design for free software: http://thorwil.wordpress.com/ _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
