Looks like hacker news filters out emojis. My thumbs up pun has been ruined.
In all seriousness - thank god. Hopefully it won't take Google Code issue tracker like levels of effort to get people to "please star the issue if it is important to you rather than commenting with +1".
I like the idea of adding more expressiveness, pictorially capturing sometimes fleeting moments of emotion or accurately representing an emotional state that can occur.
Do they capture the necessary expressiveness for the context? Facebook's reactions cover more emotions, but FB is trying to support reaction to anything that can be posted.
Considering that it's Github, how about things relevant to software engineering, like: agree, disagree, support, insightful, obsolete, misleading. I can't imagine it being helpful to know that someone felt "heart" about an issue comment.
I recently wrote a post about Facebook Reactions and if it would be effective at helping quantify sentiment. (http://minimaxir.com/2016/02/facebook-reactions/) The tl;dr is that I believe that Reactions are redundant outside of positive/negative classification.
GitHub actually has both +1 and -1, which satisfies me. But there's not much productive purpose with a smile/heart/tada other than to be quirky. (The thinking_face is neutral and adds nothing in this aspect)
Yeah, as I asked below: Will this be a meaningful form of communication and is the language (subset of images) sufficient? Can small changes like this perhaps change how PRs, Comments, etc are treated? Will it be productive, a distraction, or a NOOP?
I think the point is: Will this be a meaningful form of communication and is the language (subset of images) sufficient? Can small changes like this perhaps change how PRs, Comments, etc are treated? Will it be productive, a distraction, or a NOOP? Would you use this feature or have you used a feature like this?
I think GitHub wanted an option to express "I don't understand this," and decided :confused: was a better fit. Which makes sense, because :thinking_face: could mean "I'm considering this" or "Interesting point," which is not, I think, what that option is meant to convey.
I think it is definitely the end of +1 era, folks! Thanks Github to listen to the community feature requests. You should allow more icons like Slack is doing currently.
I think people will still write +1 comments because they won't notice this new feature, at least initially. It'd be nice if Github just converted "+1" comments into reactions.
Perhaps it follows the Hollywood model. There are lots of features in development, staff-shipped, in discussion, in the backlog, or whatever. Then there is some external stimulus (Facebook launched reactions!) and the feature gets quickly tailored and green-lighted.
So there is a quick reaction, but work on the idea may have been hidden from the public for a long time.
That's a bit suspicious, really. A feature like "Reactions to a comment" doesn't take two years to implement, even with all the scaling considerations. And people have been complaining about that for at least two years.
Version 3.4.0 of Octicons [0] came out on January 22, 2016. It added "smiley" icon, which was used in this feature today. That's 8 days after the dear github letter. 7 weeks before today.
This is a welcome addition. I've run into bugs in projects before and wanted to "+1" a thread, but it always felt like spamming the maintainers.
It'd be cool if they added a way to search through your list of reactions. This would allow you to effectively comment on an issue in an OS project, while simultaneously bookmarking it, so that you can go back and commit a fix when you have a free moment.
In that scenario, I just subscribe to the issue, so at least I get notified if something changes. But of course there is no way to list the issues you're subscribing to.
A missing feature here is sorting issues by public support. An example is FontAwesome, which explicitly asks users to leave a +1 comment on issues they support. You can then get a pretty good idea of the most desired features by sorting the issues by most commented.
Agreed -- this is the first thing I looked for. My guess is that this feature is probably next on their TODO list. There's not much point in sorting by +1s before there are many +1s accumulated, anyways.
Awesome move by GitHub. ZenHub[1] will be phasing out our +1 button now that it's no longer needed – feels good to focus. We're excited to use this reactions data as part of our reporting suite, please keep the improvements coming!
Is there a way to sort by "reactions"?
Otherwise I think this feature is useless..
I would have preferred having more detailed issues rather than ugly Emojis.
I don't think these necessarily cover all of the responses that can be made, but I think it is a great start to getting simple feedback like this. Like other users mentioned, it would be awesome to be able to sort or perform some kind of action based on the quantify of the reactions.
I wonder if they will allow for repository owners to select which reactions they will allow? I think that would help with the limited selection but still allow owners to select what they consider useful to them.
237 comments
[ 2.8 ms ] story [ 250 ms ] threadIn all seriousness - thank god. Hopefully it won't take Google Code issue tracker like levels of effort to get people to "please star the issue if it is important to you rather than commenting with +1".
These are the following reactions:
Do they capture the necessary expressiveness for the context? Facebook's reactions cover more emotions, but FB is trying to support reaction to anything that can be posted....which I just did to my team's Slack.
[edit: at least that's who I presume the GP meant]
GitHub actually has both +1 and -1, which satisfies me. But there's not much productive purpose with a smile/heart/tada other than to be quirky. (The thinking_face is neutral and adds nothing in this aspect)
Where is the sadface to go with smile? The warface to go with heart? Or the facepalm to go with party?
It definitely solves the horrible problem of too many +1s everywhere, but there are times when getting those emails are helpful.
(Not that I do :+1: comments, but the above is a scenario where automatically converting wouldn't work.)
Or just wait for people to learn the feature over time.
[1] https://github.com/dear-github/dear-github
[2] https://github.com/blog/2111-issue-and-pull-request-template...
So there is a quick reaction, but work on the idea may have been hidden from the public for a long time.
[0] https://github.com/github/octicons/releases/tag/v3.4.0
It'd be cool if they added a way to search through your list of reactions. This would allow you to effectively comment on an issue in an OS project, while simultaneously bookmarking it, so that you can go back and commit a fix when you have a free moment.
https://github.com/FortAwesome/Font-Awesome/blob/master/CONT...
https://github.com/FortAwesome/Font-Awesome/issues?q=is%3Ais...
Would also be nice to see these reactions on the issue list so you can get a feel for the issues at a glance without digging deep into each one.
[1] https://www.zenhub.io/
But seriously, it likely means the person up voting the issue has also had the same problem and wants it fixed as quickly as possible.
I wonder if they will allow for repository owners to select which reactions they will allow? I think that would help with the limited selection but still allow owners to select what they consider useful to them.