A handbook for the open source way, written the open source way

No readers like this yet.
A community building a barn

Opensource.com

Remember the Seinfeld episode where Kramer had the idea to make a coffee table book about coffee tables? I always thought that was a pretty elegant idea. Well, a few months ago, some of the smart folks on Red Hat's community architecture team had a similarly elegant idea:

Write a book about building community the open source way... and write it with a community, the open source way. Meaning, open the text up, allow interested users to contribute, and see what happens.

Brilliant.

The book is entitled The Open Source Way: Creating and nurturing communities of contributors and you can access the current text here and the wiki for contributors here.

I caught up with Karsten Wade, who is leading the project, to learn more.

There have been other books written about community-building over the last few years, but I am not aware of any others that have been written by a community. Where did the idea to start this project come from?

Our team, Community Architecture, has a strategic community role in Red Hat, and part of that is learning, distilling, and sharing knowledge.  We bring the knowledge of how to produce software the open source way to different parts of the company.  We're all in a community of practice here, and have much to learn from each other.

Once we had the idea of a cookbook or handbook for internal needs, it was immediately clear that following the open source way with the content would be better, have more impact, and protect important knowledge in case our team gets eaten by raptors.

Raptors, huh? Did you design this project to be a handbook for just open source technology projects? Or could anyone make use of it to create and nurture community?

It is definitely aimed for people beyond technology.  In fact, I consider that a top target audience. We intentionally left blanks in the book under the examples.  Each example illustrates a principle, and if I wrote them, they'd be about Fedora and Linux and yadda yadda yadda.

Two Seinfeld references in one article. Nice.

Thanks. We are inviting participation in picking good examples from outside of technology.  And let the stories compete for a spot on the Great Stories to Tell page.

Like a Wikipedia article, the best version wins out.

What types of people do you think would make the best contributors for the book?

It would be natural to say anyone, and that is in fact true. But still, there is a reason that most people read Wikipedia, and only a portion participate or contribute fully.

Anyone who likes the material enough to tell other people about it is already participating.  Those are the people I'm looking for first,they are the ones on the very periphery of participation, but in making it legitimate, we help grow their expertise 

Which sections do you think offer the best advice as they stand right now? Where do you need more contributor help?

The strongest sections are Communities of practice, How to loosely organize a community, and Stuff everyone knows and forgets anyway.

Yet, within those, there are blank spots that invite participation, and we really need it. Someone new could strengthen even those areas with relative ease.

For someone looking for a bigger challenge, there are three sections that stand out. What your organization does correctly when practicing the open source way and What your organization does wrong when practicing the open source way share a lot of very frank experience from the Red Hat perspective.  

I would like to see people from other organizations—of any size—take the chance to anonymize and record their lessons-learned, which may be underpresented or not present in those chapters.  This is one way to help make sure they do or don't happen again.

The chapter that has me most excited and the one I want to dive into now that I have some breathing room is Business the open source way. There is potential to write some groundbreaking, new content here to identify practices that people haven't thought of in that way before. There is also an even greater chance to make one canonical location for references and learning derived from the best books and the best minds about applying these principles to business.

Thanks, Karsten, the book is off to a fantastic start.

People, go check it out. This is a book that needs to be written. By all of you.

Tags
User profile image.
Chris Grams is the Head of Marketing at Tidelift and author of The Ad-Free Brand: Secrets to Building Successful Brands in a Digital World. Twitter LinkedIn Email: chris(at)tidelift.com

6 Comments

I'm curious to read, but I prefer being able to download and read it or print it?

I think there is probably not a better way to actually write about the Open Source way since out of 100 people there are probably 101 ideas of what it all really means (though most will be pretty similar).

karsten, any plans to regularly export a version of the text for download as an ebook or even for print on demand through Lulu.com?

I've done a few versions myself for the text/download (PDF and HTML), but haven't established a release schedule yet. I think the groundwork is nicely laid for a print-on-demand version, and I'm sure we'll do that in the near future.

Personally, I want to see the parts of the book filled that need more examples and content before I'll recommend chopping down trees and preparing vats of ink. :)

Yes, thanks for the question.

There is a <a href="http://www.theopensourceway.org/book/The_Open_Source_Way.pdf">PDF version</a>, and two HTML versions - a <a href="http://www.theopensourceway.org/book/">multi-page</a> and an <a href="http://www.theopensourceway.org/book/single-page/">all-in-one-page</a>.

You can find this in a neat list on the front page of the wiki:

<a href="http://www.theopensourceway.org/wiki/Main_Page#Pretty_and_handy_book_format">http://www.theopensourceway.org/wiki/Main_Page#Pretty_and_handy_book_format</a>

The content in the wiki is often more current than the PDF and HTML format. We do the content development in the wiki, then do regular version updates of the book.

This sounds like an interesting project. I was about to take a closer look at the web site today, but somehow all the content seems to have disappeared. What's going on?

Thanks for the note. The server fell over, but it's back up again.

Creative Commons LicenseThis work is licensed under a Creative Commons Attribution-Share Alike 3.0 Unported License.