On Friday, September 30, 2011 09:10:22 PM Andras Mantia wrote: > I agree. There is a common complaint by developers, that they waste > their time on bug report reading/asnwering instead of coding. While this > seems reasonable, you have to understand that developing a software > product involves interaction with your users and dealing with bugs. True > in companies and in open source as well.
This is only true to the extent dealing with the bug reports helps you figure out what to work on. It is not a rare thing for me to get bug reports about issues I'm aware of, but haven't dealt with yet. While taking the time to explain this to the user so they don't feel ignored is a good thing from a community development perspective, it's not helpful for development. This gets back to the good bug reports issue. Sometimes they are worth investing time in, sometimes they aren't. I can understand both perspectives. I get annoyed by useless/pointless bug reports as a developer, but I'm also frustrated as a user where I'm using poorly performing software and either the bug reports don't get much response or I know I don't understand the system well enough to file a useful report, so I'm sort of stuck waiting (kdepim - I'm thinking of you when I write this). Scott K >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
