Pasting from initial post on Trello:
Previously the GitHub issue tracker was also used for tracking features. However this proved problematic, e.g.
- The large number of ideas for new features mixed up with bugs made it harder to track the bugs. Even if labels were used to distinguish bugs from features, it made the number of open issues artificially high, which presented a negative image of the community to outsiders.
- Non-technical stakeholders would submit new ideas in a way which didn’t tie up well with development activities.
As a result, it was proposed to move feature tracking to the forums, and feature issues in GitHub were closed. Unfortunately other problems with the forums such as spam attacks surfaced soon after, so the community has effectively been without a place to track features for quite a while.
So the community needs to decide how to address this.
One proposal made on the community technical call on Aug 15 2019 was to use the new Discourse forum for more informal brainstorming around new features, but also to create an issues-only repository e.g. https://github.com/mautic/features which is dedicated to feature tracking. This would have all the standard advantages of using a structured issue tracker, but would keep it cleanly separated from the existing issue tracker. Write-access to this could potentially be limited to technical contributors who can help with the relationship between feature ideas and the corresponding concrete technical work required to implement them. Ideas could then start off being formed in Discourse, and then promoted to GitHub when technical discussions commenced.