• On TV.com: Beach Bodies photo gallery
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.
Recent posts from The Open Road
What soccer team would your company be?
Open-source licensing: Your mileage may vary
Open source to shape cloud computing, but not dominate it
Off-topic: Why can't I have this job?
Legalized drugs, now open source. Those crazy Dutch!
Will 'good enough' virtualization topple VMware?
Linux community codes around Microsoft's FAT patents
As Mozilla 'upgrades the Web,' Microsoft must upgrade its pace
advertisement

Making sense of Windows 7 upgrades

faq The basics and the fine print on Microsoft's options for those eyeing the next operating system from Redmond.
• Full Windows 7 coverage

Road Trip 2009: Big Sky Country

CNET News reporter Daniel Terdiman takes his car full of gadgets to the Rockies and the Great Plains in search of tech, science, nature, and more.
• America's Fortress: Cheyenne Mountain

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