Skip to content

Tag Archives: community

Lockheed Goes Open Source. Blankenhorn Hates It.

A Tin Foil Hat

Courtesy CycleDog, Licensed CC-BY-NC

I was really pleased to read the announcement that Lockheed Martin’s social networking platform, EurekaStreams, was released as an open source project today. Lockheed is a very conservative company, and while they’re happy to use open source internally and on projects for their customers, this is their first experiment with actually running a project themselves. I think it’s a big deal, not just for Lockheed Martin, but for large corporations who are considering a more open, more innovative approach to software development. And yet, Dana Blankenhorn hates it:

I don’t see anything in Eureka Streams I can’t do in Drupal, or a number of other high-quality open source projects that have existed for years. Lockheed has reinvented the wheel — why?

So here’s the nice thing about the open source community: competition. If I think I’ve come up with a better way to solve a problem, it can easily compete with the incumbents. Low barrier to entry, we say. Let the best ideas win. Unless, apparently, the best ideas come from a company I don’t like.

Then things start going sideways:

Developers for Glory

Although it may be simple to conflate the Apps for Democracy and Apps for America contests with the exciting new Apps for Army contest, they really couldn’t be more different. Together they represent an exciting experiment in what it takes to pull communities together around a problem. Though they all offer cash prizes to the winners, they each took a slightly different approach, with different results.

Cash incentives are somewhat controversial in open source circles. Most old-school advocates for open source development strongly prefer developers who are personally invested — famously, those that “scratch their own itch.” Developers who are paid a salary to work on software are also invested, but perhaps less zealously than those who are solving a problem they are afflicted with themselves. Developers who are working for glory and cash prizes, the model used by the “Apps for…”  competitions, is yet another class of developer, and despite the excellent submissions to the previous contests, there are valid concerns that the quality and sustainability of the code is not as good as it could be with a different set of incentives. Time will tell, of course.