zlacker

>>xpe+(OP)
A couple of big projects in the python space use this approach. Pisses me off as a power user. I find what are clearly bugs all the time, and am forced through a funnel that places the burden on me. Stinks of arrogance to think your project is that rock solid you should add friction for reporting bugs. Especially in “forever v0” projects.

But, I am super lazy.

>>lijok+hs
[flagged]

>>Ethery+Fx
There's zero entitlement expressed by the parent, he's just trying to help the project, but is encountering unnecessary friction.

It's not that he has some inner urge to contribute in some way, he just encountered a bug while using the software and wants to report it. The alternative isn't coding — it's no contribution at all.

>>Mawr+eH
I think this is exactly the point most people miss. No contribution is better than bad contribution. Most issues people file are bad. I previously worked at a major OSS company and the vast majority of bug reports are just noise. It takes time to sift through them and they add no value, just waste time. If people did less of that, that would be a good outcome, not a bad one. Sure, there's useful reports there sometimes, but it's more rare than you'd think. On top of that, many of those are dupes of issues we've already found and filed, just haven't had time to fix yet.