That is my suggestion as well. We have ~1000 issues now, but that is likely to grow very quickly as it gets more and more users. A lot of them might be related and would be solved by a single ‘feature’/‘improvement’. So it is very useful to create new ‘roadmap issues’, that gives a better perspective of the high level requirements.
If we get an agreement on that, we could update the app that I have mentioned in ERPNext Roadmap Document [Long Term Goal] - #13 by spoojary to capture all the requirements specific to our roadmap management. We will continue to use the github for detailed feature discussions, but use the app for capturing data needed for managing the roadmap. My previous company had a custom ‘backlog tool’ of prioritised roadmap items. One of the fields was input from account team telling how much valuable that feature is. That would be much more meaningful than a upvote button.
Btw, really great summary of the meetings minutes!