←back to thread

FFmpeg to Google: Fund us or stop sending bugs

(thenewstack.io)
1125 points CrankyBear | 1 comments | 11 Nov 25 18:32 UTC | HN request time: 0s | source
Show context
ranger_danger ◴[11 Nov 25 19:12 UTC] No.45891460[source]▶
Wouldn't they just fork it, fix their own bugs and stop contributing at all?
replies(6): >>45891483 #>>45891531 #>>45891743 #>>45892105 #>>45892143 #>>45892666 #
inerte ◴[11 Nov 25 20:04 UTC] No.45892105[source]▶
If you're going to fix the bug, why not in the main project?
replies(1): >>45892297 #
ranger_danger ◴[11 Nov 25 20:19 UTC] No.45892297[source]▶
Any time I have tried to fix a bug in an open source project I was immediately struck down with abusive attitudes about how I didn't do something exactly the way they wanted it that isn't really documented.

If that's what I have to expect, I'd rather not even interact with them at all.

replies(4): >>45892519 #>>45892628 #>>45892791 #>>45894498 #
1. shevy-java ◴[11 Nov 25 21:01 UTC] No.45892791{3}[source]▶
I don't think this is what typically happens. Many of my bug reports were handled.

For instance, I reported to the xorg-bug tracker that one app behaved oddly when I did --version on it. I was batch-reporting all xorg-applications via a ruby script.

Alan Coopersmith, the elderly hero that he is, fixed this not long after my report. (It was a real bug; granted, a super-small one, but still.)

I could give many more examples here. (I don't remember the exact date but I think I reported this within the last 3 years or so. Unfortunately reporting bugs in xorg-apps is ... a bit archaic. I also stopped reporting bugs to KDE because I hate bugzilla. Github issues spoiled me, they are so easy and convenient to use.)