Managing Open Source Projects

Spacemonkey — Wed, 21 Nov 2007 14:41:00 +0000

While browsing the Open Source Community blog I found a post by Amy Stephen about managing open source projects. Or more succinctly, what it takes to manage one, and who is/isn’t a good fit to manage such an effort, written by Matt Asay for c|net.

The original post is based on research published in the Academy of Management Journal on the topic. Ultimately open source projects need specific skills in growing and nurturing the project and the project community and that need gets more and more prevalent over time as the project evolves.

I’d like to add my personal view that these skills are most definitely not technical skills, and despite the popular notion that open source projects should be managed by elite alphageeks, they scream for an exact opposite personality to manage.

I’ve seen several projects run into the ground due to a few developers who, despite making major contributions to the code, had a complete lack of skills needed to manage a project. For the alphageeks out there:

"eleet skillz" != "competent management"

Looking around the open source world, there are actually many famous personalities that although being technically gifted with brilliance, they are also notorious for being, er, less than approachable.

I’ll end this post with the moneyquote from Matt:

“in other words, a jerk is a jerk, even if he/she writes great code. You may want them on the project, but you don’t want them running it (into the ground).”

Open Source Hypocrisy: Tag management

Managing Open Source Projects