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
I've been annoyed at this distinction myself when trying to troubleshoot problems with other Github-hosted software. I actually think the distinction Ghostty is making here where the Discussion section is open for anyone to bring up an issue with a project, and the Issues section is locked down to official maintainers and is only used for tracking well-scoped planned changes to the software (which might arise from a user-initiated discussion about a problem) makes a great deal of sense. I haven't seen any other Github-hosted project which organizes itself in exactly this way but I have zero problem with it as a user of Ghostty myself.