What They Forgot to Teach You about Open Source

There seems to be a misconception about what’s required to build a vibrant open source community and it’s not “community management”. Community management focuses on providing infrastructure and facilitating communication for a community. This includes setting up events, maintaining TO-DO lists, keeping forums under control, making announcements, etc. And that’s all well and good, in fact it’s vital. However, although this role is important it will likely not lead to any significant growth in your community. Communities need Leadership in order to grow because leaders create a vision of the future that draws people to their communities and motivates them into action.

Multitasking is a Lie

Does instant messaging (IM), email, and social media make us more productive?  Of course they do, right?  …  Well, the real answer is ‘no’ (what would be the point of this post otherwise?:).  As a Community Manager for two open-source projects I reach out and ‘connect’ with people as part of my job.   In doing so I use Twitter, mailing lists, IRC, and discussion forums almost constantly, but what about people who aren’t tasked with making connections and building community?  Is it good for them? 

Flock Theory and Leadership

I have to admit that I’m a bit of a collaboration and community junkie and as such follow some obscure topics. One topic I’ve had on my radar for quite some time is Flock Theory. Flock theory tries to describe the self-organizing and emergent aspects of human behavior. Succinctly put, behavior in some cases is not a property of any individual person (or bird), but rather emerges as a property of a group or social network (flock). This concept can be used to describe aspects of both collaborative teams and open source communities. I’m not going to analyze the merits of the theory but I do want to introduce its concepts which I think have implications for team/community productivity and possibility even individual information relevance.