This Github issue has been closed because GitHub issues for new features are not allowed. Is this on the roadmap? How can we tell?
Feature requests in this forum have no associated Github issue, so no link with the actual product development in terms of commits\PRs. Hence there are no real progress updates in this Feature Request. It can be open forever without any status changes and feedback to users.
GitHub issues can get version milestones and visibility on the product roadmap. Feature requests in this forum do not.
Github issues can go stale after inactivity. Feature requests in a forum do not. Too many GitHub issues that go stale look bad reputationally for the project and encourage regular updates. Too many feature requests remain open for years? Meh, who cares? I expect this is an unfair exaggeration of the attitude in this project, but the jist of this point holds.
IMO, should be both. As now, users should request features in this forum using their language (not always precise enough), then devs\admins create one or more associated GitHub issues with the necessary precision and post links to these in the forum Feature Request. Creation of a GitHub issue shows that the devs do actually give a sh!t and intend to do something about it. Other FOSS projects, eg RockStor work well with this setup.
It’s not enough for project leadership to promise they’ll keep an eye on a forum. Meaningful feedback via GitHub issues is also necessary. They serve different purposes and types of people, but both are needed.