BYBLACK DUCK

Social Networking is NotWorking

As a coder by profession, I think I’m not alone when I say that I don’t see the appeal in using most social networks.

They require lots of input (who are you? what do you do? where do you work? what do you like? who are your friends? don’t you have more friends – please – add more friends!).

Then, in return for all this input, you get very little – mostly you spend more time wondering if you should accept someone else as a friend.

Here at Ohloh we often get asked: “why doesn’t Ohloh focus on being the ‘myspace/facebook/linkedin’ of open source developers’?

The answer is is two-fold:

Yes – we are heading there. We do want to be the place open source developers connect. However,

No – we’re not going to just jam random (often annoying) social networking features.

Our strategy is simple: we’re going to attempt to reverse the value equation: you will tell Ohloh relatively little about yourself (basic bio and what software you create and use) – and, in return, we’ll give you more and more relevant info out of it.

So far we’ve covered:

  • we provide automated metrics on software projects
  • we give you stats on your own development
  • we provide relevant suggestions on what other software you should consider using

As usual, our problem is what to focus on first. This is where you come in. Let’s start discussing where you’d like Ohloh to grow in this space – and, if you must, where you’d like us to not go. Fire away…

  • doogie (doogie)

    Social networks could be a good idea, but it’s hard to be really enthusiastic about them given what we’ve seen on facebook, MySpace, Spoke and Xing.

    I think we can all tell you what we don’t like:
    * invitation mails jamming my inbox
    * building up huge lists of “friends” most of whom I really don’t care about
    * entering a lot of information about myself and my friends
    * not getting much back from the service relative to the effort I put into it.

    Instead I would like to know is what people I am interested in:
    * do in the open source community (code, docs, project management)
    * visit on the web
    * music they listen to
    * books they read
    * technologies they use
    * blogs or articles they write

    I would also like to have a sense of who my friends are and what they are up to.

    Thanks

  • http://naesten.googlepages.com SamB (Samuel Bronson)

    It might be nice to have an ohloh facebook application (so I could show off my pitiful contributions to SVN-using projects on facebook).

  • http://nitens.org dartar (dartar)

    I couldn’t agree more on the fact that Ohloh doesn’t need fancy social software features to do its job. Ohloh’s core business is to extract metrics and map the OS development landscape, right? So I don’t see how adding blog, music-I-listen, books-I-read could make my ohloh experience more enjoyable/useful. I have my photo sharing, blog, bookmarking, music-sharing websites, why should I expect Ohloh to monkey these services?

    On the other hand I’d love to see more user-related information extracted from the data you collect.
    * are people in the UK using PHP more than the French?
    * where does OS development happen in the world?
    * how many people near me are working on similar projects?
    etc.

    Now, instead of allowing users to share information on the music they like or photos of their kids, I’d love to see features allowing to share more developer-oriented user information, e.g. which OS, platform, browser, code editor, revision control system, bug tracker one uses (stacks are just too generic for this). Cross-referencing these data with development metrics could lead to really interesting discoveries, e.g. the most popular code editor among Mac users, the most common platform from which PHP developers work etc. Some demographics might be interesting too but maybe users prefer not to disclose their age, sex etc.

    My 2 cents.

  • jason (Jason Allen)

    Excellent points, dartar.

    I agree that Ohloh needs to carefully think this through so as to add relevant features. We will move carefully.

    When you mention the “standard social feature set” (e.g. picture/music/book sharing…), there is one basic feature we are missing: communication.

    It’s happened to me a few times where I run across someone on Ohloh that I find interesting and would like to leave a remark or a question.

    What do you think of a “facebook wall”-type feature?

  • http://nitens.org dartar (dartar)

    from ohloh’s perspective some internal messaging/contacts system makes sense (it would definitely encourage people to ‘stick around’ more than they do at the moment). I’m just not sure how useful I’ll find this, considering that I already spend too much time on messaging systems on different websites.

    Or maybe an (optional) contact form?

  • http://www.rooftopsolutions.nl evert (Evert)

    If you are going this route, please try to not make ohloh yet another user silo.. open things up with foaf and openid.

  • jason (Jason Allen)

    Evert,

    We’re putting a lot of thought into providing an open api to access ohloh data. I’ll post something up later today.

  • http://petal-and-paws.co.uk Nazca (Daniel / Nazca)

    Sadly social networking is largely a disaster… I refuse on principle to have a myspace account … I pretty much ignore any social networking invites that drop in to my inbox.

    I do have an Orkut account … that’s occasionally worth it for killing time looking at groups, but I think you hit the problem squarely in the face when you said that most social network sites are high input, high maintenance, and low return. Why bother?

    @ doogie:

    music they listen to

    I’d love to see a “music you code to” sort of thing … could be really mad to collect a “This project was written while listening to:” type thing?

    @ dartar:

    So I don’t see how adding blog, music-I-listen, books-I-read could make my ohloh experience more enjoyable/useful.

    RSS feed from blog could be useful … I don’t know if it’s within Ohloh’s planned goalposts to do rss feed aggregation (Planet style) for project developers and friends/kudos’d people (could maybe have a flag on kudos links for rss aggregation?)

    Music I listen … could be interesting

    Books I read … has value if said books are books about code, or books that assisted in the development of a project. Could be interesting to know what reference books the lead developers of apache or subversion have sat on their desks.

    @ jason:

    What sort of ohloh data … the same stuff we see on here now but via a convenient api?

  • jason (Jason Allen)

    Daniel: yes – a REST (xml or json) service API that exposes most of Ohloh’s data. I’ll hopefully still post about it sometime tonight – although the hour is getting late!

  • rah003 (rah003)

    What about this: let those who wants to have it add links to their social network accounts to their profile.
    As for other things, I’d like to see blog aggregation mentioned already few times, and also maybe list of conferences/meetings/presentations/trainings attended by different people and their rating of those events.
    Would be also nice to be able to drop a note to someone. This can stay on site and be shown just when you login, not necessarily redirected to anyones mailbox straight away.

  • http://6v8.gamboni.org mortimer (mortimer)

    I think the ohloh site is great to get stats about project and asses developers and project progress. A cool addition (as mentioned before) would be to be able to tell which OS we are using or other non open source things (for example, for some open source project, on OS X, I need to use XCode, etc…) to gather the data proposed by data.

    Another cool thing would be to put people in contact with each other. Let say a developer is planning to do a project that does A and another project already exists that does B which is close to A… then instead of doing two separate projects, they could merge and become a better project.

    So people that have a project would say if they need help, more idea, etc… or if it’s a mature project. Then from ohloh data, you could notify other developers that would have the right knowledge to help the unmature projects…

    not sure it makes sense ;)