3 ms·

That's something we made on purpose. We believe feature requests and issues should be treated differently. In our vision, an issue refers to a bug in the softw

by Ecco 11y ago

That's something we made on purpose. We believe feature requests and issues should be treated differently. In our vision, an issue refers to a bug in the software. It doesn't need voting: it's up to the developers to figure out the gravity of the situation (or to an analytics tool that gather how many times a given issue arises). On the other hand, a feature request refers to a new capability of said software. It then makes sense for users to vote, because, as a developer, it's hard to know which feature is the most expected.

crdoconnor 11y ago
>We believe feature requests and issues should be treated differently. Github doesn't. Issues can be tagged as 'bug' or 'enhancement' and they're both treated essentially the same way. >it's up to the developers to figure out the gravity of the situation Sure would be nice if there were some sort of tool that could help with figuring that out.
- deleted 11y ago
  [deleted]
- Karunamon 11y ago
  Those are just default tags to a (very limited) issue tracking system. "Enhancement" could very well be (and is) used by developers for planned features, not necessarily requests from end users. Heck, the title of the page you access that system on is called "issues".
munro 11y ago
> We believe feature requests and issues should be treated differently. If you want other people to use what you made, you may have to do what they want. :) > In our vision, an issue refers to a bug in the software. Overloading causes miscommunication, and can affect how we think! Github issues aren't about issues, as in bugs. It's a moldable concept to keep track important things. Lots of repos already use Github issues to track features, as well as many other things, why not help their lives?
- itistoday2 11y ago
  > If you want other people to use what you made, you may have to do what they want. :) Exactly. First thing I did when visiting the comments here was see if someone had brought up this issue. Just some more feedback (to indicate a consensus): I won't consider using this tool unless it provides easy access back to GitHub. An example of a successful project that does bi-directional linking is BountySource.

by Ecco 11y ago

crdoconnor 11y ago

>We believe feature requests and issues should be treated differently. Github doesn't. Issues can be tagged as 'bug' or 'enhancement' and they're both treated essentially the same way. >it's up to the developers to figure out the gravity of the situation Sure would be nice if there were some sort of tool that could help with figuring that out.

deleted 11y ago
[deleted]
Karunamon 11y ago
Those are just default tags to a (very limited) issue tracking system. "Enhancement" could very well be (and is) used by developers for planned features, not necessarily requests from end users. Heck, the title of the page you access that system on is called "issues".

munro 11y ago

> We believe feature requests and issues should be treated differently. If you want other people to use what you made, you may have to do what they want. :) > In our vision, an issue refers to a bug in the software. Overloading causes miscommunication, and can affect how we think! Github issues aren't about issues, as in bugs. It's a moldable concept to keep track important things. Lots of repos already use Github issues to track features, as well as many other things, why not help their lives?

itistoday2 11y ago
> If you want other people to use what you made, you may have to do what they want. :) Exactly. First thing I did when visiting the comments here was see if someone had brought up this issue. Just some more feedback (to indicate a consensus): I won't consider using this tool unless it provides easy access back to GitHub. An example of a successful project that does bi-directional linking is BountySource.