Tracking new and non-committed issues as Discussions #1559
Locked
lodicolo
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have finished triaging all of our open issues (it regularly was over 170) and have closed (we had some open things despite them being fixed) or converted most of them to Discussions if they were better as one.
There's very little organization and it's difficult to track community interest in different features using the issue tracker, and so it's better left to committed features/enhancements (ones we plan to do or are working on already), and true bugs (not functionality that doesn't behave as someone wants).
In order to better serve the community's interests and better prioritize features that do not get picked up by someone (be it a developer or external contributor), all feature requests should be submitted as a Discussion, which have a special voting feature that displays in the list itself. Super easy to see what is desired from a high level instead of digging into each individual issue!
This also separates features from bugs, and gives a place for everyone to collaborate on what we would like to see in different feature implementations before we ever get started. This will help us determine in advance what is highly desired, and also the ability to properly vet how large a given request is.
Bugs should continue to be filed as issues, but please make sure it is really a bug and not just a feature not implemented the way you would like, that should be a Discussion first!
Beta Was this translation helpful? Give feedback.
All reactions