Hector Martin

If you can't handle, or don't care, or are okay with your software piling up problems, that's *fine*, but you don't get to cheat and make the open issue count go down anyway. That's just insulting your existing users and misleading new ones.

what if... You provide a patch and make the issue go away in that manner? I mean, why do you think you can just push work on other people like that? And that they need to keep that task in their todo forever?

Why is it my job to fix other people's software? The whole point of a bug tracker is to allow users to report problems so you can fix them. I very often *do* provide patches, but when I don't you don't get to pretend the issue doesn't exist at all.

If you don't want to provide support then don't have an open bug tracker at all. Letting people report bugs and then ignoring them is insulting and wastes users' time. If you don't intend to track, nevermind fix bugs, then say so upfront (and then I won't use your software).

I don't know why exactly do you feel entitled to tell people what they can do with bug trackers on their projects and which bugs to prioritize (this includes your triade to ffmpeg developers from some weeks ago).

I'm sorry, but if I'm taking the time to report a bug, yes, they do owe me something: treating my time investment with respect by not throwing it in /dev/null just because they want their bug count to go down without putting any effort into it. Reporting bugs is a contribution.

Very often I spend up to an hour gathering info for a good bug report. Sometimes it takes even longer. This is often more time than it would take to just fix the bug. Now you may take care of it on your own schedule, which might be "never" for all I care...