PuppetLabs and Opscode Reveal How They Built Their Open Source Communities

| by Matthias Marschall Follow 0 Followers on Mar 19, 2013. Estimated reading time: 1 minute |

A note to our readers: You asked so we have developed a set of features that allow you to reduce the noise: you can get email and web notifications for topics you are interested in. Learn more about our new features.

Being nice to people and being explicit and transparent about how things are done are key ingredients for growing communities say both, Luke Kanies, CEO and founder of PuppetLabs, and Adam Jacob, co-founder of Opscode and creator of Chef. They both claim that you need to be genuine in the way you interact with your communities. PuppetLabs and Opscode both succeeded in building thriving Open Source communities alongside growing businesses.

“A lot of companies think you can force the creation of a community,” but you can’t, says Kanies during his keynote at ApacheConf. He adds that you need to be honest in answering questions, but transparency is not the same as openness. He isn't going to answer questions about funding or other topics that aren’t something he can disclose to the entire community. For Kanies it's essential to engage the community instead of simply announcing changes. The example he mentioned was the license switch from GPL to Apache. The process took months but eventually only two out of 3,000 community members complained.

Jacob told InfoQ that the foundation of a community is respect. Only if you take the community seriously do you have a chance to succeed. Being transparent in how you operate is essential. One example he mentioned was their Contributor License Agreement (CLA). People don't like the hassle of filling it out but it makes it absolutely transparent that every contributor has the exact same rights as Opscode.

Jacob emphasized that every company has a choice about which role it plays in the Open Source community around their products. A company can either consider their software as a gift to the community while keeping the rights to exploit contributions for themselves or a company can decide that every contributor should be equal. Opscode, he says, took the latter approach.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you