This is interesting but like that one site that was bought recently (get satisfaction) this is another site that I, as a repository owner, has to track down to find customer feedback. Kinda like Gitter.im, yet another external service I have to be aware of.
It's difficult to be omnipresent so I can track all of the different pieces of feedback my project may be getting; even though it's not ideal I'd rather everyone just funnel through Github issues just so I can interact with them and be aware of any issues or requests. I don't want to miss out on any feedback should it be on an external service I do not know about.
I agree with you, having to keep tabs with thousands of new services is annoying.
In that case though, you shouldn't have to worry about missing some users' feedback. That's why you have to register your project with FeatHub before people can give feedback (we temporarily enabled anonymous import to boostrap the service, but that won't last). This way, as a repo owner, you know you have enabled FeatHub.
Also, it's not implemented now, but we could imagine notifying owners on a regular basis. I suggested the improvement there: http://feathub.com/feathub/feathub/+8
It seems like you build off the comments of issues, parsing for the :+1:, you could functionally provide the same tooling, but in the same additive way that waffle.io does.
And, like Get Satisfaction, it's a pretty dick move to imply to my users that I'm affiliated with you and that their voices can be heard through you. I certainly have sympathy for Mark Otto (https://twitter.com/mdo/status/591707867498946560) asking them to stop doing that.
Gitter.im has an IRC interface so at least I can idle in my projects gitter irc chat in emacs when programming in the best programming language node.js
It could easily use the API to parse comments for +1 / thumbsup emoji / etc too. Also could have a lil viral component, when you +1 on the app, it adds a comment with a link to the app.
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.
I like the idea, but would prefer if GitHub just integrated this functionality. Otherwise, how will the developers know that something was voted on unless they use these third-party tools?
Is it me or this is very similar to the way zenhub.io [1] works?
Anyway, I recently also stumble upon a similar tool that enables voting for PR and even auto merges the code [2], which is not precisely the scope that feathub targets, but it is very useful and similar enough to worth mentioning it :p
It's really hard to add features to someone else's app in such a disconnected way, for everyone in their community. Most people haven't heard of your site, and it's also hard to form habits of checking Github, as well as your page. Usability improvements ... should makes things easier!
Repo owners have control over what gets displayed on their project page (to an extent), and can drive their subset of users to your app.
If owners are having trouble seeing how many people up voted a feature, then make a bot that counts the number of thumbs up in an issue tagged "feature", then update the issue title. This would be really helpful to those people.
Also, if owners want to see the top feature requests, make an embeddable image for the README that clicks to the full list. People love embeddable widgets. :D
Those two things is all I observe your app does, plus you had to reinvent commenting, which is a huge turn off.
There are loads of popular tools out there that integrate into Github, it's worth checking them out to see how they weasel their features into Github.com!
I've been looking for something like this for a while now but honestly if you run a non-technical service requiring your users to sign up for a github account (just to vote on features) is a pretty big ask. Integration with other AUTH services like Facebook/Google would be very beneficial.
We figured out our early adopters would be on GitHub, that's why we started with GitHub login. Fell free to add a feature request on http://feathub.com/feathub/feathub :-)
This raises the question of the gameability of the voting, but this could be mitigated using a mixture of cookies, captchas and browser fingerprinting.
It says "See how they are listening to their users" on the home page. Does this imply that not using this tool or not desiring feature voting is the same as ignoring your users? That's some pretty unpleasant positioning IMO.
This is fantastic. This is perfect for an OpenSource maintainer to get insight into the users priorities on the issues. Thank you for creating this tool.
I'd like to use it for one of my projects (https://github.com/dbcli/pgcli). Even though I've authorized feathub to access my organizations, the repo is not listed in the drop down.
[+] [-] BinaryIdiot|11 years ago|reply
It's difficult to be omnipresent so I can track all of the different pieces of feedback my project may be getting; even though it's not ideal I'd rather everyone just funnel through Github issues just so I can interact with them and be aware of any issues or requests. I don't want to miss out on any feedback should it be on an external service I do not know about.
[+] [-] Ecco|11 years ago|reply
I agree with you, having to keep tabs with thousands of new services is annoying.
In that case though, you shouldn't have to worry about missing some users' feedback. That's why you have to register your project with FeatHub before people can give feedback (we temporarily enabled anonymous import to boostrap the service, but that won't last). This way, as a repo owner, you know you have enabled FeatHub.
Also, it's not implemented now, but we could imagine notifying owners on a regular basis. I suggested the improvement there: http://feathub.com/feathub/feathub/+8
[+] [-] sirwolfgang|11 years ago|reply
[+] [-] ketralnis|11 years ago|reply
You shouldn't have to opt out of stuff like this.
[+] [-] tdaltonc|11 years ago|reply
[+] [-] nodejsisbest|11 years ago|reply
[+] [-] crdoconnor|11 years ago|reply
It would get annoying having two separate lists of features (and, presumably, bugs). One on github and one on this service.
Still, if it just did voting on issues on github, I'd find it pretty useful.
[+] [-] pbnjay|11 years ago|reply
[+] [-] Ecco|11 years ago|reply
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.
[+] [-] lighthawk|11 years ago|reply
[+] [-] Ecco|11 years ago|reply
[+] [-] guiomie|11 years ago|reply
[+] [-] steveklabnik|11 years ago|reply
[+] [-] Ecco|11 years ago|reply
[+] [-] felipesabino|11 years ago|reply
Anyway, I recently also stumble upon a similar tool that enables voting for PR and even auto merges the code [2], which is not precisely the scope that feathub targets, but it is very useful and similar enough to worth mentioning it :p
[1] https://www.zenhub.io/
[2] https://news.ycombinator.com/item?id=9351286
[+] [-] munro|11 years ago|reply
Repo owners have control over what gets displayed on their project page (to an extent), and can drive their subset of users to your app.
If owners are having trouble seeing how many people up voted a feature, then make a bot that counts the number of thumbs up in an issue tagged "feature", then update the issue title. This would be really helpful to those people.
Also, if owners want to see the top feature requests, make an embeddable image for the README that clicks to the full list. People love embeddable widgets. :D
Those two things is all I observe your app does, plus you had to reinvent commenting, which is a huge turn off.
There are loads of popular tools out there that integrate into Github, it's worth checking them out to see how they weasel their features into Github.com!
[+] [-] dvcc|11 years ago|reply
[+] [-] Ecco|11 years ago|reply
[+] [-] krallja|11 years ago|reply
Mark Otto @mdo · 24 minutes ago Hey @feathub, please remove Bootstrap from your site—we've no plans to use it and it's disingenuous to imply we do.
[+] [-] Ecco|11 years ago|reply
[+] [-] telecuda|11 years ago|reply
When I looked again at Get Satisfaction, User Voice, etc they're all so bloated with features and complication.
Looking for a way to direct my signed in users to a simple page to vote up a list of features we're considering.
[+] [-] vohof|11 years ago|reply
[+] [-] kyle_t|11 years ago|reply
[+] [-] Ecco|11 years ago|reply
We figured out our early adopters would be on GitHub, that's why we started with GitHub login. Fell free to add a feature request on http://feathub.com/feathub/feathub :-)
Also, while we're at it, we could even consider anonymous voting (http://feathub.com/feathub/feathub/+15)
This raises the question of the gameability of the voting, but this could be mitigated using a mixture of cookies, captchas and browser fingerprinting.
[+] [-] diiiimaaaa|11 years ago|reply
[+] [-] wkonkel|11 years ago|reply
https://www.bountysource.com/extension
[+] [-] Ecco|11 years ago|reply
Anyway, you're right, it is similar. FeatHub doesn't require an extension though, so you can just point your users to your project's voting page.
[+] [-] thedaniel|11 years ago|reply
[+] [-] 32131532526|11 years ago|reply
[+] [-] amjith|11 years ago|reply
I'd like to use it for one of my projects (https://github.com/dbcli/pgcli). Even though I've authorized feathub to access my organizations, the repo is not listed in the drop down.
[+] [-] Ecco|11 years ago|reply
Meanwhile, I've created the project for you. Here you go: http://feathub.com/dbcli/pgcli
[+] [-] Ecco|11 years ago|reply
[+] [-] fosk|11 years ago|reply
[+] [-] mkolodny|11 years ago|reply