Repository navigation
Feedback wanted: Roadmap structure #115
Nystik-gh
announced in
Feedback Wanted
Replies: 4 comments
|
Engagement with the issue is usually the best indicator. The more emojis, comments, and pull requests you see related to something the more important it is. |
0 replies
|
I think using something like this is a good roadmap view + votes to see what people wants. Apologies for posting other people's roadmap, but i think a roadmap with real data will be helpful here. |
0 replies
|
I agree. Ideas can be created in discussions section, and users can upvote those same ideas, and you can convert an idea to a feature enhancement in Issues (instead of users making new features by opening an Issue). |
0 replies
|
Thanks for the feedback so far. I am still thinking through how to handle this. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I want some feedback on how I should handle the updating of the roadmap for the project. It's getting a bit difficult to respond quickly to compatibility issues and bugs without postponing features too much.
So, I would like to know how people prefer me to handle the roadmap. Should I set up polls for voting on what feature and/or issues people want prioritized? Or maybe a pinned discussion thread where I outline the order I am planning for coming changes, where people can ask questions and I can update the roadmap as I go when I re-prioritize items?
I am not sure what the best solution here is so please let me know how you would prefer this to work.
All reactions