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]

>>gertop+Dt
> to know "what is clearly a bug" 100% of the time in projects you don't own

Owning a project is counter-productive for QA. If it’s your project, you know where to click and where to not click.

OTOH, you don’t need to know anything about a project to conclude that a crash with access violation, or hang with 100% CPU usage, are clearly bugs.