• On TechRepublic: Five super-secret features in Windows 7
September 11, 2008 2:07 PM PDT

The difficulty inherent in managing an open-source community

by Matt Asay

I've heard the open-source search engine, Simplexo, come up twice in conversation this week, and so was interested to dig a deeper into what Simplexo offers. My own company, Alfresco, has worked with Lucene, another open-source search engine, for the past few years and has been both pleased and disappointed with its capabilities, but I've been particularly frustrated by how hard it is to contribute code to Lucene.

The Alfresco development team has put Lucene into serious production, and has found a range of areas in which it falls down. To remedy this, our development team has made a wide range of improvements and fixes to the Lucene code. At one time the team tried repeatedly to contribute the code back to the Lucene project, only to have it fall on deaf ears.

Not that our team is necessarily much better. I've seen outside contributions make their way into the core Alfresco code, but I've also seen our developers turn up their noses at outside contributions. It either wasn't up to the level of code quality that the engineers expected or simply wasn't of interest to them.

This isn't to criticize my engineers or on those within the Lucene community. It's just to point out that open-source project leads and participants have their own priorities, priorities that outsiders may struggle to appreciate and embrace. To contribute code to a community effectively, you must become part of that community, which generally involves a great deal of time and effort.

Perhaps this is why more and more companies pay people to contribute to open-source projects of interest to them. The GNOME community offers a poignant example of this: the core developers are paid to be such. It may well be the only way to keep sufficiently abreast of its politics and preferences to become a key member of the community.

In short, it's hard to contribute to open-source projects as a casual contributor. The only - or, at least, the best - way to get code in is to become an insider. Just don't expect it to be easy.

Matt Asay brings a decade of in-the-trenches open-source business and legal experience to The Open Road, with an emphasis on emerging open-source business strategies and opportunities. Matt is vice president of business development at Alfresco, a company that develops open-source software for content management. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure. You can follow Matt on Twitter @mjasay.
Recent posts from The Open Road
Mobile: Still waiting to see what sticks
Google privacy controls: Most people won't care
Amazon's move mocks EU's fear of Oracle
Skype to open-source far too little
The difference a few years makes to open source
Novell cuts 3 percent of its workforce, plus benefits
Data's one-two punch in open-source business models
Open source as an antitrust strategy

FAQ: Buying the right Windows 7 upgrade

Readers still have lots of questions on just which version of the software they need to buy in order to upgrade their PC. CNET News tries to offer some answers.

N.Y. lawsuit details Intel's 'largesse' toward Dell

Attorney General Andrew Cuomo's federal antitrust case filed Wednesday alleges a longstanding symbiotic relationship between Intel and Dell.

advertisement

About The Open Road

Matt Asay brings a decade of in-the-trenches open-source business and legal experience to the Open Road, with an emphasis on emerging open-source business strategies and opportunities. Matt is general manager of the Americas division and vice president of business development at Alfresco, a company that develops open-source software for content management. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure.

Add this feed to your online news reader

The Open Road topics

advertisement
advertisement

Inside CNET News

Scroll Left Scroll Right