| Ok, this specific feature description makes a lot of sense (pulling data from issue trackers to find projects with tasks you can do). From having read the readwriteweb article I was left with this feeling of "but that's exactly what GitHub does". Under the possibly totally incorrect assumption that that article is based on marketing copy from you, I will offer a key suggestion I learned on product differentiation once: you need to say things that your competitors aren't just going to claim applies to their products as well. Example: "our shoes are comfortable" is going to be a really difficult campaign because every single company in that space is going to be claiming that. In this case, saying "social layer for GitHub" is incredibly confusing (even if it is theoretically accurate, as another responder just pointed out), as GitHub bills itself as "a social network for programming projects". To bring it to this case, when I looked at the readwriteweb article, the general idea of "find people to work on your projects" seems to be exactly what people are already using GitHub for, so my response was "wait, wtf" rather than "oh, that's an interesting take". In particular, I got here: "the ability to find and promote repositories, showcase developers' skills and repositories, as well as reward those who contribute", and I thought "this article could have been written a few years ago about the launch of GitHub: what are they actually doing here that GitHub isn't". |
Hopefully we'll get the message across clearer the next time around, thanks for the notes. I'll keep them in mind when we get more attention in future.