Guest post: Paul Anderson interviews Jono Bacon

This post is by Paul Anderson, EPSRC Computer Science Writer of the Year 2007.

Jono Bacon is the community manager for Ubuntu, a popular distribution of GNU-Linux. Based on his experience Jono has just written a book, published by O’Reilly but available under a Creative Commons Licence, about community and open source. Originally from England, these days he is based near Berkeley, California. Paul Anderson from Intelligent Content caught up with him on a recent visit to London.

Q: You’ve just published a new book, The Art of Community, what’s the key message you are hoping to get across?

The Art of Community essentially teaches the reader how to build a productive and enjoyable open source community. It starts with a bird’s eye view of the social science behind the concept of ‘community’ and then gets into how to build a strategy for a particular community. The book then delves into each of the elements that go into the delivery of that strategy such as processes, governance, tools, running events, dealing with conflict, and how to hire a community manager.

Q: So why is the idea of community so important for open source?

I think that there are ethical benefits and there are pragmatic benefits. The ethical benefits of working through a community seem fairly obvious to me. They are things like it helps to reduce elitism, providing an opportunity for everyone to get involved, and it provides opportunities for people to gain experience. On the pragmatic side, a community that has been harnessed effectively can deliver some really interesting things. For example, on one of the projects I worked on we decided to open it up for translations [of the documentation] and within two weeks we had 17 languages.

Q: In the book you argue that a ‘sense of belonging’ is important.

Yes. The way we build community is to create a sense of belonging. When people feel that sense of belonging in the community then they feel like they are part of something, they feel it is their ‘place’, their home. And when they have that they feel like contributing back to the community.

Meritocracy is very important part of this. This is where people build up reputations based on the merit of what they actually do. It is the only way that a distributed community can really work. When anyone is in a meritocratic environment they fundamentally feel a sense of principles and they really treasure the premise of equality.

Q: Ubuntu operates a code of conduct. This seems to be an important thing to get right.

When you build a community the first thing you need to do is build a set of principles. You need to say this is the culture that I want to instil and for open source software that means a culture of openness and transparency with freedom to contribute. You want people to be respectful and polite but not too restricted in their communications with each other.

The Code of Conduct we have in the Ubuntu community is essentially to provide a charter of reasonable interactions. So what it does is say: ‘every contributor to Ubuntu should follow this conduct’. It is a very basic set of ‘don’t be an idiot’ instructions. I believe that documents like this can hold tremendous value and it is held in very high regard in the Ubuntu world. This kind of thing helps build a sense of belonging.

Q: This raises the issue of managing the community, or as you describe it in the book, ‘Governance’.

Governance is having some kind of official structure that takes decisions on behalf of the community, like a Management Board or a Council. One of the mistakes that a lot of communities make is to believe that they need an explicit and very expansive governance structure in place, otherwise they are not real community. And this is not true.

Ubuntu has quite an expansive governance structure in place. We have a community Council and a tech Board at the top, and then various team councils that report to them. But this is because the Ubuntu community is huge and we need this to deal with the scale of what we’re doing. If you’re a smaller project you just don’t need that.

Q: You also talk at length about process workflows and tools.

Yes, I think it’s really important to get this right. On the workflow side of things the focus is on identifying ways in which people can work together on common problems, for example bug tracking. How do you handle bugs? How does the team triage them when they come in? Who fixes them? All these are part of the community workflow, they are really important and the book has a lot of ‘hands on’ stuff about these issues.

I think that tools need to be applicable to do the job. One of the problems for a lot of communities is that they want to have something like a public website, so what they’ll do is agree that they need a website, but then have a long and drawn out debate about which content management system they should use. What happens is that they spend more time bickering about tools than actually doing something good like having a basic project website and actually getting people to visit it.

What I recommend in the book is that they just pick something, it doesn’t matter too much what that is. In a year’s time they will want something different. The first six months of a community is the most critical time and a team needs to be built – a sense of excitement, a sense of belonging needs to be built up. You don’t get that by spending the time bickering about tools like a CMS.

Q. Widening things out a little, where do you see the general situation with open source today?

I think we are in good shape. What we are doing is building a new IT industry with open source, building a new approach to software and I think we have made tremendous progress. Just look at Linux. I first got involved in 1998 and we have made so much progress in the intervening years. I look back to those days when I actually needed a soldering iron and a steady hand to get Linux working on my PC! We have made huge progress in terms of writing software, making it useful and integrating it with systems.

This week is Ubuntu Open week which includes a series of tuition sessions and the whole ubuntu community is joining in. If you’re interested in getting a taste of what’s involved, now is the time to see for yourself. 

3 thoughts on “Guest post: Paul Anderson interviews Jono Bacon

  1. Pingback: Jono Bacon (jonobacon) 's status on Tuesday, 03-Nov-09 18:04:28 UTC -

  2. Pingback: Bacon for lunch « Tech Lunch

  3. Andrew Back

    I’d love to know what computer that was and why it required soldering in order to run Linux! The last PC I attacked with a soldering iron was in the early 90s, just around the time they turned to all surface mount components on the motherboard and were non-serviceable.

Comments are closed.