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
How is opening a discussion more friction than opening an issue?

>>layer8+e01
In the python projects in question, unlike with the Ghostty project, there isn't an "issue triage" discussion category that maintainers look at. They have just discussions, and everything is treated as such. So when you raise an issue in discussions, it either goes to the void or people come in looking for a discussion of alternative approaches to do what you're trying to do that don't hit the bug, rather than treating the bug as a bug.

At a high level - the audience of discussions is the community at large, the audience of issues is the maintainers.

What Ghostty is doing with a dedicated category for issue triage should work just fine, despite it being an additional hop.