zlacker

>>xpe+(OP)
Personally, I find the distinction between “issues” and “discussions” annoying.

For one, it duplicates the efforts in checking for prior reports. I might try 5–6 sets of keywords, but now I have to do so for 2 separate trackers.

Tickets cannot be moved between trackers, so instead folks resort to duplicating it and moving discussions… which is entirely opaque if you’re following up via email: you won’t get any more notifications and your future replies are silently discarded.

As a maintainer, having two trackers per project never made sense to me, so I’ve disabled discussion everywhere.

This is mostly a criticism of how GitHub implemented this feature, not of the decision taken here.

>>WhyNot+NQ
At the very least I think what matters here is the process. The same exact process could be implemented via, for example, issue labels. It would not be hard for maintainers to search for issues with label "bug", which only maintainers can assign. There are clear UX tradeoffs between the two approaches.