Why users cannot create Issues directly (github.com)

Article summary

The article discusses why users cannot create issues directly in the Ghostty repository on GitHub. Instead, users are asked to create a discussion first, which can be converted to an issue by a maintainer if it is deemed valid. This approach is based on the experience that many reported issues are not actual bugs, but rather misunderstandings or feature requests. The goal is to make it easier for maintainers to find and work on real issues.

Main themes

• Issue tracking
• GitHub discussions
• Open source maintenance
• Bug reporting
• Feature requests
• Developer workflows

What commenters say

• Using discussions as a filter for issues can help reduce noise and make it easier for maintainers to find real issues to work on.
• The distinction between issues and discussions is not always clear, and some argue that it is not worth the extra effort to separate them.
• Some developers believe that having a large number of open tabs in a browser is necessary for their workflow, while others think it is unnecessary and can be managed with bookmarks or other tools.
• The high memory usage of browsers like Chrome is a problem, but some argue that it is a necessary trade-off for performance and responsiveness.
• There are different opinions on the ideal amount of RAM for a laptop, with some arguing that 8GB is sufficient and others believing that more is needed for demanding workloads.
• Some developers prefer to use local development environments, while others are required to use remote VMs or centralized dev clusters for testing and development.
• The use of discussions and issues can be seen as a way to separate signal from noise, but some argue that it can also lead to important issues being overlooked or ignored.
• The approach to issue tracking and discussion can vary widely depending on the project, team, and industry, and there is no one-size-fits-all solution.