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?
-
-
Replying to @jernejv
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.
1 reply 0 retweets 10 likes -
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).
1 reply 0 retweets 6 likes -
Replying to @marcan42
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).
1 reply 0 retweets 1 like -
Not a single OSS developer really owes you anything. You can ASK them to fix a bug, but this arrogant entitled yelling at people who gave you software for free is not worthy of a civilized person. Read e.g. https://caddy.community/t/the-realities-of-being-a-foss-maintainer/2728 … for how shitty this is for maintainers.
1 reply 0 retweets 1 like -
Replying to @jernejv
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.
1 reply 0 retweets 2 likes -
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...
1 reply 0 retweets 1 like -
But the moment when you decide to close the bug due to inactivity, you are telling me "I don't care about your problem, and you've wasted your time reporting it, and this is all a farce and I'm not actually interested in tracking problems with my software". And you're an asshole.
1 reply 0 retweets 0 likes -
It's one thing to manually ping old bugs (over 1 year old) and ask whether they're still relevant (and close them if you don't get a reply within, say, a few weeks). But issue auto-closers are the equivalent of saying "fuck you" to your users.
1 reply 0 retweets 2 likes -
I'm an open source maintainer, and have also maintained free-as-in-beer software with an entitled user base, and you know what? I would *never* ignore bug reports (that are actual bugs and actionable) nor close them just because I don't have the time to deal with them.
1 reply 0 retweets 0 likes
So yeah, if your attitude is that you "don't owe me anything" then say so up front, so I can avoid putting any effort whatsoever into reporting bugs for your software (and most likely just will use something else).
-
-
And by the way, I'm talking about bugs, not feature requests. Feature requests can be legitimately closed if the author doesn't think they'll ever get to them. The space of existing bugs is bounded, but the space of possible features is unbounded. Different story.
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.