Nick Carr: Bebo and Digital Sharecroppers

This was an interesting article by Nick Carr that popped up in Google Reader today - it's about the Bebo acquisition by AOL and how the founders have been rewarded handsomely, to the tune of $800 million, with diddly squat going to the artists who contributed site content. From the article:

As for the millions of members who have happily served as sharecroppers on the Birches' plantation, they'll get the satisfaction of knowing that all the labor they donated to their "community" did indeed create something of tangible value. No doubt they're thrilled that the little Bebo plantation, which they've tended so lovingly, is now part of the giant AOL plantation, itself part of the Time-Warner conglomerate.

The article goes on to reference a great NY Times op-ed by Billy Bragg. It's all must-read stuff.

In the Open Source world, we deal with this all the time. People often ask how we can make money off the backs of free labor, to which I always answer: we don't. But the question lingers, and for good reason. Being a community-centric company is a double-edged sword. After all, if you've successful in convincing a fair number of community members to buy into your vision, what, if anything, is your responsibility to them? Ultimately, my opinion rests on the assumption that Bebo.com is a rather different example from most Open Source community sites, because in those cases, the company gives the community items of great value, whether it's the software, better documentation, or simply the investment into care and feeding of the community.

This is in stark contrast to a community like Bebo's, where the vast majority of content comes from the users. Sure, web sites like my employer's are geared towards providing conduits for community contributions and feedback, but it's always clear in that case that the owner of the web site is the primary source of an overwhelming amount of the content. In Bebo's case, without user-generated content, there wouldn't be anything of value at all.

Well, at least I see a difference. What about you? What do open source companies owe their communities? What are their responsibilities? Put it in the comments below.

The Google Open Source Program Office - A Model to Emulate?

At a recent SDForum event, I was doing my usual schtick about communities, when I happened to mention one of my recent thoughts: that Google's Open Source Program Office kicks major ass. I can think of no other company that has merged marketing, PR, real code, real community events, and real *stuff* that geeks find enthralling as cohesively as Google. It seems to me, as an outsider, to be an almost perfect blend of how you develop community and derive real value from it. And as I always like to point out - in order to do that, you must first give your community real value. Google seems particularly good at both giving and getting value. Better, in fact, than anyone else.

And yet, you would have thought that the audience were a collection of cows staring at a newly-installed gate. Crickets chirped. And then I heard some push-back:

They do it for recruiting!

Well, yes, this is true. But then, I didn't say they were altruistic, but rather that they knew what they were doing with respect to community development. They invest in communities, many of them related to Open Source, and this devotion to community helps them tremendously. It helps them when they launch a new set of services, because the communities they target will no doubt be the early adopters. It helps when Google launches a new platform, such as Android, because their communities will be the source of a great number of hackers who will enjoy bending Android to their will.

As is often the case, whenever I say something that meets with any sort of vehement disagreement, I obsess over why my view differs so greatly from those whose opinions I normally agree with. So, expect to see more posts as I dive more deeply into this issue. It also helps that this happens to coincide with the latest installment of the Google Summer of Code.

Parallel Feedback Loops: Integrating Your Community

I finally wrote something for the Hyperic blog:

The term innovation opportunity has been discussed by Matthew Aslett, who described it as "the potential to lower development costs for business users, while at the same time raising their potential to focus on innovative development." This falls in line with the view that an open model is more efficient, but how exactly is it more efficient, and how does one maximize that efficiency? Does Open Source development lead to the creation of a perfect market? I will attempt to describe how innovation opportunities come about, and how to take advantage of those opportunities. The key would seem to be enhancing the ability to deal with parallel feedback loops that arise as a matter of course from interactions with your user and developer community. Put another way, maximize the surface area of your community and be able to capitalize on these "touches".

Read the rest of Parallel Feedback Loops.