Community Leadership Summit 2011

Community Leadership Summit 2011

Not long now until the [Community Leadership Summit 2011](https://www.communityleadershipsummit.com/); an annual event designed to bring together community leaders and managers to share best practice, ideas, and solutions. The event is entirely **free** and takes place from **23rd – 24th July 2011** in **Portland, Oregon**. The event takes place the weekend immediately before [OSCON](https://www.oscon.com/oscon2011) in the same venue, the **Oregon Convention Center**.

To join us you need to register, and over **180** people have already registered from a [diverse range of organizations](https://www.communityleadershipsummit.com/attendees/) including *Mozilla, O’Reilly Media, Rackspace, Adobe, Partimus, Red Hat, Google, Portland State University, Open Affairs Television, Apache Software Foundation, Xen, Digium, IBM, Microsoft, CloudCamp, OpenSesame, Oregon State University Open Source Lab, Wikia, Eucalytpus, MySQL, MeeGo, Linaro, Oracle, Linux New Media, BitNami, SUSE, setiQuest, Webtrends, Alfresco, Northeast Coalition of Neighborhoods, Open Source Bridge, OpenStack, Joomla!, Peace Markets, Infinity Curve, MoreThanGiving.com, TYPO3 Association*, and many more.


Awesome people having a rocking time and building stonking communities. What’s not to love?

If you are interested in community and building great community for your organization or project, be sure to come and join us. The event is an unconference, and as such the content and topics are driven by the attendees, which has resulted in a rich set of content and great best practice shared across many different disciplines.

I also want to offer my thanks to [O’Reilly](https://oreilly.com/), [Oracle](https://www.oracle.com/), [Ohloh](https://www.ohloh.net/), and [Microsoft](https://www.microsoft.com/) for helping to support the event!

## Interesting In Coming?

Simple. Just go and [register](https://www.communityleadershipsummit.com/register/) (it is **free**) and feel free to [share some session ideas](https://communityleadershipsummit.wikia.com/wiki/2011/SessionIdeas) that you may want to see or run at CLS11.

## If You Are Coming

If you are coming to the *Community Leadership Summit 2011* be sure to do a few things:

* Go to the [CLS11 Wiki](https://communityleadershipsummit.wikia.com/wiki/Community_Leadership_Summit_Wiki) and share [session ideas](https://communityleadershipsummit.wikia.com/wiki/2011/SessionIdeas) and [lightning talks](https://communityleadershipsummit.wikia.com/wiki/2011/Lighting_Talks) for the event. Everyone is welcome to share ideas!
* Tweet about the event and be sure to use the `#cls11` hash tag.
* Join the [Facebook Event](https://www.facebook.com/event.php?eid=196907063655463) for further updates.

I look forward to seeing you all there!

Burnout Prevention Tutorial Session Tomorrow

Burnout Prevention Tutorial Session Tomorrow

Just a quick note that I will be delivering my *Burnout: Detecting it, avoiding it, preventing it* session online tomorrow, **Thu 9th June 2011** at **11am Pacific / 2pm Eastern / 6pm UTC / 7pm / 8pm Europe**. In the session I will discuss about the different stages and how you can prevent being at risk.



Burnout and flip-out are close pals in some cases.

This is going to be a session optimized for [Lernid](https://wiki.ubuntu.com/Lernid) (complete with slides), so be sure to [download the latest version of Lernid from the PPA](https://archivedblog.jonobacon.com/2011/06/05/new-lernid-release-please-test/) and I look forward to seeing you there!

Unity Quality in Ubuntu 11.10: Help Make It Rock

Unity Quality in Ubuntu 11.10: Help Make It Rock

On Thursday 28th April 2011 we released [Ubuntu 11.04](https://www.ubuntu.com/), the *Natty Narwhal*. It was a big release for us. It was the first desktop release that shipped [Unity](https://unity.ubuntu.com/); our new desktop interface designed to bridge the chasm to get Ubuntu and the Free Software it encompasses to the masses.

Unity in this release was very much a first cut. I am hugely proud of the accomplishments of the Desktop Experience Team, Design Team, and Ubuntu Platform Team in delivering Unity in 11.04, but we all acknowledge that there is lots to be done. Quality has to come first and foremost in the Ubuntu experience, and Mark Shuttleworth affirmed that *fit and finish* is going to be a key goal for Ubuntu 11.10, the Oneiric Ocelot.

## In Search Of Quality

As part of this focus on quality, the Canonical Design and Desktop Experience teams are committing their time to fixing some of the design and software bugs that have been reported since the Natty release. As is usual with software teams, bugs have been identified and assigned to respective developers and these bugs will be merged into future Unity releases.

In addition to this, serious bugfixes (such as crashers) are being released as Stable Release Updates for Natty. Currently the [first Unity stable release update release](https://launchpad.net/unity/+milestone/3.8.14) is currently in the `proposed` archive and should be released to 11.04 users over the next few weeks. The team are also focusing on a [second SRU update that will resolve further issues](https://launchpad.net/unity/+milestone/3.8.16). Of course, these bug fixes will also make it into Ubuntu 11.10 too. These stable release updates will ensure that current and future Ubuntu 11.04 users will get an even more stable experience and the Ubuntu 11.10 release will set off on the right foot when it comes to stability.

Of course, there are many software bugs open for Unity (software defects, problems, and oddities), but there are also design bugs open too. Unity was not just a first cut of a software release, but also a first cut of a design delivered in a desktop edition of Ubuntu. As such, since 11.04 there have been lots of design problems and bugs reported too. We are really keen to ensure these issues are also resolved as the Unity design continues to mature and evolve.

*John Lea*, fearless designer on the Design Team, has worked with the team to process these design bug reports, work with the team on proposed solutions, and get these solutions signed-off. As such, we now have [this list of design bugs](https://bugs.launchpad.net/unity/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=OPINION&field.status%3Alist=INVALID&field.status%3Alist=WONTFIX&field.status%3Alist=EXPIRED&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.tag=udo&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search) that are focal points for being resolved in 11.10. Some of these bugs are assigned to Canonical developers, but not all are.

To help with this work, [Jason Smith](https://codearmada.com/) from the Desktop Experience team has been going into these design bugs and providing instructions on what needs to be done to fix them. This is hugely helpful for community volunteers to fix these bugs and help improve Unity.

## How You Can Help

So let’s get to the heart of the matter.


This really has nothing to do with this post, but…well, I just love ducks, and they are clearly the badasses of the waterfowl world.

Quality is something *we can all improve*. Whether you are interested in writing documentation, programming, testing, translating…there is a way in which you can help improve the quality of Unity in 11.10. Canonical is certainly investing in this, but we are an Open Source community and such the wider community we can all help.

If you are a developer and know some C++, *you can make Ubuntu better for millions of people*. A few hours of your time working on some of these bugs could bring great quality of experience to Unity and Ubuntu and help us to take Free Software to even more users as a stable, secure, feature-packed, and well-designed platform.

To get started, take a look at [Jorge’s first post about Unity contributor plans in 11.10](https://ubuntu-news.org/2011/06/07/unity-community-contributor-plans-for-11-10/) – this post explains where to find the bugs, how to get started, where to find help and more. Jorge will be posting every week with new opportunities and bugs to work on and showcasing the great work of our community.

With the Desktop Experience team working on some bugs and also new features, and the community working to help bring an even higher-grade of quality and fix more bugs, together we can deliver a rocking 11.10 release!

I will be talking more in later posts about other ways of helping, such as documentation, translations and testing. I look forward to see the Unity contributor family growing, and don’t forget to come and [join us in `#ayatana` on freenode](https://unity.ubuntu.com/contact-us/).

Better Community With Better Technology

Better Community With Better Technology

One of the primary goals in the Ubuntu community is to encourage and inspire people to get involved in different parts of the project. Getting people involved typically requires a few key steps:

* **Inspire** – Get someone interested in joining the community.
* **Provide Opportunities** – Find something for them to do.
* **Review** – Review their work to help them be successful and have their work included.

For each of these areas we perform different types of work. As an example, to *inspire* people to contribute we perform lots of outreach, run education weeks, and try to showcase great work. For the *opportunities* side of things we run bitesize bugs campaigns and more. We also strive to ensure that contributions are *reviewed* in a timely manner.

We have though found two distinctive challenges in defining *opportunities* and *reviewing work*. First, in terms of opportunities, the bitesize bugs lists, lists of QA tests to complete etc, are often changing and growing and sometimes new contributors don’t see these new additions. Also, in terms of reviews, we have sometimes seen the queues of content that needs to be reviewed (e.g. the Ubuntu Sponsorship Queue and various merge proposals) build up because our reviewers get busy with other work and forget about the reviews.

This is a problem with *visibility of lists*. We want to always ensure that lists of opportunities and reviews are very visible to new contributors for the former and our existing mentors for the latter. Traditionally this has been a challenge as the lists and their visibility has always existed on a website and are not locked into the daily workflow of those respective groups (new contributors and mentors). Fortunately, I think technology could help with this.

## Building Community Into The Desktop

Much of the work we have done in growing our community has happened outside of an installed Ubuntu system. The work happens on websites, in calendars, in social media and elsewhere. I have though always been curious about how we could build community interaction directly into an Ubuntu desktop. I wrote [Lernid](https://wiki.ubuntu.com/Lernid) as an experiment in to this: providing a cohesive application that brought together the different pieces in delivering a solid online learning experience, and the application has proved to be popular.

In thinking about our problem of raising the *visibility of lists*, it struck me that we have this awesome application indicator technology that we ship with every Ubuntu desktop, and this could help significantly. Imagine we had an indicator for different types of participation, and it always provided a set of links that were *tuned to you and your capabilities*. Let’s look at a few examples.

### Bitesize Bugs



You are a new developer and you are interested in contributing to a given project (e.g. Unity). You always want to know which bitesize bugs are going to be great places to start. You install `indicator-bitesize` and you can set which projects you are interested in and it will show the highest priority bitesize bugs for that project. Clicking on each item takes you to the Launchpad bug report with the details.

This indicator would regularly poll Launchpad to update the list when items are tended to and new items appear. The indicator would change color to indicate that there is new content.

### Code Reviews


You are a developer on a project (e.g. Unity), and you want to always provide timely input on merge proposals. The `indicator-codereview` indicator would present code reviews for all the projects you have permissions to review code for in Launchpad. If you click on one of these items it would take you to the merge proposal page for that branch in Launchpad.

This indicator would regularly poll Launchpad to update the list when items are tended to and new items appear. The indicator would change color to indicate that there is new content.

### Tests


You are interested in testing Ubuntu for the current development release. The testing process should be as simple as installing `indicator-testing` which then presents a list of tests that are appropriate to your software and hardware configuration. As an example, if you have an ATI card it would show tests relating to your card and driver. Clicking on each item would load a checkbox type test that would take you through the steps of testing and uploading the results back to the testing team.

This indicator would regularly poll a back-end testing service to update the list with new items when you have completed the tests. The indicator would change color to indicate that there is new content.

### Sponsorship Queue


The Ubuntu Sponsorship Queue is a key piece in how we grow our developer community. The `indicator-ubuntusponsorship` indicator would provide a list of items on the queue potentially that are related to the packages you are interesting in in the queue. Clicking on each item would take you to the item in Launchpad.

This indicator would regularly poll Launchpad to update the list when items are tended to and new items appear. The indicator would change color to indicate that there is new content.

## Next Steps

I think these indicator features could really help raise the visibility for different opportunities and reviews open to our community, and embedding the community experience more deeply into the desktop.

Would anyone be interesting in writing one of these? Some resources:

* [Documentation](https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationIndicators) – some details and code snippets of how to write an indicator.
* [Get Help](https://unity.ubuntu.com/contact-us/) – `#ayatana` on freenode and the [mailing list](https://launchpad.net/~ayatana-dev) are there to help.

I look forward to seeing if anyone is interesting in picking some of these ideas up. 🙂

Burnout Prevention Tutorial Session Tomorrow

New Lernid Release: Please Test

Just a quickie. John. S. Gruber (I assume the S stands for *superstar*), has just kicked out a new [Lernid](https://wiki.ubuntu.com/Lernid) release, version `0.8.1`. John is powering his way through the bug list and getting Lernid ship-shape ready for the [six months of awesome](https://archivedblog.jonobacon.com/2011/06/01/six-months-of-rocking-ubuntu-events/) coming up in the Ubuntu world.



This screenshot doesn’t always drink beer, but when it does, it prefers Dos Equis.

Please go and download the new release from the PPA. It is available for *Maverick*, *Natty*, and *Oneiric*.

To install, just do this:

sudo add-apt-repository ppa:lernid-devs/lernid-releases

Then do this:

sudo apt-get update

And then do this:

sudo apt-get install lernid

Later this week we are going to schedule an event to showcase the features in Lernid and ensure everything is working tip-top. You can file Lernid bugs [right here](https://bugs.launchpad.net/lernid/+filebug).

Cool Projects That Need Your Help

Cool Projects That Need Your Help

I just wanted to highlight a few awesome projects going on that are looking for help and could provide a rocking place to get involved for coders, testers, translators, docs writers and more. Of course there are many other projects that need help, but I just wanted to highlight these few near and dear to me.

## Lernid




The result of Jono writing code, and then someone else re-writing it so it actually works.

[Lernid](https://wiki.ubuntu.com/Lernid) is a tool I wrote a while to provide a simple, integrated interface for joining our many different online events. In it it supports presentation slides, viewing web pages, tuition event schedules and more.

John S. Gruber is now maintaining Lernid, and his focus is on stability and getting the [bug list]() in shape and bugs fixed. Again, this is a Python application, and if you are a Python developer, I am sure John would value the help. See the [Launchpad Project](https://launchpad.net/lernid), grab the code and rock on it. Be sure to join `#lernid` on freenode.

## Ubuntu Tweak




Tweak ’till Hammersmith.

As I have blogged about recently, the author of [Ubuntu Tweak](https://ubuntu-tweak.com/) has been keen to join the recently formed [Ubuntu Power Users]() community and has identified the follow key areas of focus for the new 0.6 series of releases for the app:

* Safety – building in support to backup and undo changes so users can easily roll back config settings if they don’t work for them.
* Pluggability – support installing and loading plug-ins from $HOME/.local/ubuntu-tweak/plugins and separate “Application/Source Center” as a plug-in (Install from PPA, package name: ubuntu-tweak-community-plugins) – this will tend to the current concerns about installing untrusted PPAs inside the app.
* Janitor – the previous “Package Cleaner” will be renamed to “Janitor”, to instead the “Computer Janitor”, it will support plug-in too.

If you are interested in getting involved and writing some code (in Python), see [this guide](https://github.com/tualatrix/ubuntu-tweak/wiki/Get-involved-with-Ubuntu-Tweak-Development), If you want to test and report bugs, see [this guide](https://wiki.ubuntu.com/UbuntuTweak). If you are interested in writing plug-ins for Ubuntu Tweak, see [this guide](https://wiki.ubuntu.com/UbuntuTweak/HowToWritePlugins).

## Ubuntu LoCo Team Portal




Kind of like Second Life, but in the real world.

You know it as [loco.ubuntu.com](https://loco.ubuntu.com), and I have talked recently about some goals for improving it to better serve the growing LoCo Team community. To summarize the goals:

* provide a central point in which you can find out about all the incredible work going on in the community.
* encourage best practice and skills acquisition across different LoCo teams.
* encourage and inspire teams to participate by seeing the great work and ideas from other teams.

To find out how to get involved, first read [this guide](https://wiki.ubuntu.com/LoCoDirectory/Development). It is also recommended that you join [this mailing list](https://lists.ubuntu.com/archives/community-web-projects/) and feel free to ask questions in `#ubuntu-website` on freenode.

There are a number of people actively involved and working on the site, and it is a fun project to be a part of and key piece in helping us to grow and inspire LoCo teams for a growing generation of Ubuntu community members.

Cool Projects That Need Your Help

Six Months Of Rocking Ubuntu Events

Education and learning has always been an important part of the Ubuntu culture. It is important to us because we always want to present an environment in which everyone is welcome to participate, whatever your skills, location, or experience. We want to make it really easy to get involved in Ubuntu and be a part of the revolution. 🙂

Along these lines we always organize online learning events in each cycle that are designed to encourage people to join our community and help get people up to speed with skills and how things work in the interests in growing more and more people who enjoy contributing to Ubuntu and our community.

Today we finalized a stack of dates for the coming cycle and I just wanted share them:

* **Ubuntu Developer Week** – *11th – 15th July 2011* – a week designed to help up-skill those who want to participate in packaging, bug-fixing and other Ubuntu-related development activities. This is a great week to get started as an Ubuntu developer.
* **Ubuntu LoCo Teams Learning Week** – *18th – 22nd July 2011* – in this new event we will be providing a set of sessions that are designed to help get LoCo teams up and running and successful. Topics such as how to get members, build an online presence, organize events and more will be here.
* **Ubuntu Cloud Days** – *25th – 26th July 2011* – Ahmed Kamal will be organizing another set of Ubuntu Cloud tuition sessions that can help get you up and running with an Ubuntu powered Private or Public cloud.
* **Ubuntu Global Jam** – *2nd – 4th September 2011* – an essential part of the Ubuntu calendar in which LoCo teams around the world organize local events to get together to meet and greet and enjoy contributing to Ubuntu together.
* **Ubuntu App Developer Week** – *5th – 9th September* – a week of tuition sessions about writing apps for the Ubuntu platform and how to get your apps into the Ubuntu Software Center.
* **Ubuntu Open Week** – *17th – 21st October 2011* – a week designed to be a good first step for brand-new Ubuntu users, deliberately timed the week after release. This is a great first step if you are a brand new user.

Also, many thanks to the new [Lernid](https://wiki.ubuntu.com/Lernid) maintainer, John S. Gruber, for helping to refine and improve the tool that makes these learning events so simple, fun, and enjoyable to participate in.

More about these events as they happen!

Looking For Awesome LoCo Team Blog Feeds

Looking For Awesome LoCo Team Blog Feeds

As part of the work going in to [make loco.ubuntu.com tab-worthy](https://archivedblog.jonobacon.com/2011/05/26/future-loco-team-portal-plans/), we need to know what the most awesome blog feeds are for LoCo content.

Do you have a blog about your LoCo team? Do you write about, post pictures, and talk about the events your organize? If so, we want to ensure your feed appears on the new [loco.ubuntu.com](https://loco.ubuntu.com).

To do this we are looking for recommendations for feeds. You don’t have to be an official Ubuntu member to have a feed on the site, you just need to blog about the things your team is doing.

If you don’t have a blog, I recommend you set up a free blog at [wordpress.com](https://www.wordpress.com).

Finally, go and [let us know about your feed on this wiki page](https://wiki.ubuntu.com/LoCoPortalFeeds).

Thanks!

Cool Projects That Need Your Help

Be Nice, Free Snacks.

I just wanted to share a fun little story with you all.

On Friday I got up and as I often do, wrote a good morning tweet on my [Twitter feed](https://www.twitter.com/jonobacon):

> Morning peeps, how are we all doing today? Ready for the weekend? It has been a busy week here…

I then got this response from the [Pretzel Crisps twitter account](https://www.twitter.com/PretzelCrisps):

> @jonobacon It’s Friday, we’re feeling good! How about some comp’d bags of Pretzel Crisps to start the weekend! DM work addy and we’ll dlvr!

Being the cynical arse that I am, I suspected this was a scam. I checked their Twitter feed, but I didn’t see reams of other similar tweets (as you often see with scams), so I was stumped and replied:

> @PretzelCrisps you can comp me some free Pretzel Crisps? really? why me?

At this point I was expecting this:


A round-brown, copper-bottomed bucket of nothing, sealed with a kiss..

…but I got this:

> @jonobacon You asked how we were doing…and we can dlvr snacks today before the weekend…best Friday ever! DM work addy!

At this point I was either entirely gullible or there was a world of free pretzels about to come crashing down on top of me. Being the kind of brave and adventurous solider I am, I decided to risk this wave of salty deliciousness.

Well, kind of. I sent them my father-in-law’s business address. I am, as they say, a *master criminal*.

At this point I expected to get a call a few days later from one of the folks at the business to say a box had arrived addressed to me.

*A few hours later* we got a call from the business saying that a woman had walked in and dropped off two bags of pretzels. Not two packets…but two shopping bags filled with packets; approx 15 packets of Pretzel Crisps. When Lynne, who works at the business, brought them to our house we were stunned. Free pretzel crisps, and they are delicious!

I sent them a quick tweet to say thanks:

> @PretzelCrisps wow, you folks are awesome, thanks so much for the crisps! They are delicious. Expect a rather nice blog entry soon. 🙂

..and naturally tweeted my surprise generally:

> Huge kudos to @PretzelCrisps for sending us some free Pretzel Crisps, just because I wrote a good morning tweet. They are delicious. Thanks!

There are multiple morals to this story:

* Pretzel Crisps are delicious.
* The Pretzel Crisps company are awesome.
* Being nice and saying good morning can get you free things.

Bonkers.

The Art of Community: Building Belonging

The Art of Community: Building Belonging

*With many of you folks who read my blog having an active interest in participating or growing a community of some sort, I am going to re-print some portions of my book, [The Art of Community](https://www.artofcommunityonline.org) on my blog. I would feel guilty about doing this if it weren’t for the fact that the book is entirely free and [available for download](https://www.artofcommunityonline.org/get/), although if you can afford to, do [buy a copy so you can to support O’Reilly in publishing Creative Commons books](https://www.artofcommunityonline.org/get/)*.

*This fragment is right at the beginning of chapter one, and starts covering some of the underlying social elements about how community works. The book then delves into the practical elements of growing community later*.

> “Great things are not done by impulse, but by a series of small
things brought together.” — Vincent Van Gogh

As my watch ticked over to 8pm, I knew I was in trouble. First of all, I was late, and not fashionably late, either. In fact, at the time, I was about as unfashionable as you could get for someone staring 18 down the barrel. Long hair, Iron Maiden t-shirt, baggy camouflage trousers, and a thumping-great leather jacket. I left my parents’ house and got into my small van, adorned with oversized speakers and a tree-shaped air freshener. It was time to roll. “Rolling” was optimistic. Instead, I sat bumper-to-bumper in traffic with half of Southern England, all joined in curiosity about whether or not that film with Michael Douglas could become a reality on this cold English day.

This wasn’t helping my nerves. As a fairly outgoing, angsty teen, nerves were not usually my bag, but tonight, I was dining on them.

You see, tonight was different. Tonight I was doing something unusual, something that had seemed like a great idea…when I wasn’t running 30 minutes late, hammering my way down the motorway, with my Number of the Beast cassette ritualistically sacrificed to the gods of hi-fi just for good measure.

Thankfully, the world’s longest mechanical conga line decided to crank it up a notch. Before I knew it, I found myself on a street I had never been to, in a city I had never been to, about to head into a room full of people I had never met before, all united by one simple symbol….

A penguin.

An hour before, that penguin had seemed so inviting and friendly. It was a symbol that encompassed everything about the movement it represented, a movement that came together
in spirit and mind to build a system that drove a new generation of technology and freedom…a movement that celebrated this drive by forming user groups in unknown streets, in unknown cities, and with unknown people.

But as I stood there, doorbell already pressed, none of that was even close to my conscious thoughts. Instead, the brain of one Jonathan E J Bacon was battening down the hatches, preparing for ultimate, unparalleled discomfort as I walked into a place I both did and didn’t want to be at the same time.

Then, the door opened and a rather nice chap called Neil welcomed me into his home.

Community is a funny beast. Most people—the kind who watch talent shows on television and occasionally dip bread in oil in an expensive restaurant—don’t understand people like
Neil. Why on earth would this guy decide to open his home, free of charge, to a collection of strangers who met on the Internet? Why would he want to spend an evening drinking tea and making jokes about something called “Emacs”? And why would he fund online resources like fliers, a mailing list, and a website from his own pocket; start a book-lending service for the group—and even shell out for tea and biscuits?

One person who really didn’t seem to understand was Neil’s wife. Somewhat bemused, and referring to us as his “Internet friends,” Neil’s significant other decided tonight was the night for visiting a long-lost (or possibly ignored) relative, rather than sticking around and faking interest.

## Collaboration-Driven Ethos

What intrigued me when I first walked into Neil’s living room was the concept of a collaboration-driven ethos, although at the time I had no idea what those words meant. What
that experience taught, and what that evening inspired in me, was an excitement about what is possible when you get a group of people together who share a common ethos and a
commitment to furthering it.

In my world, that ethos has thus far been Free Culture, Free Software, digital rights, and breaking down the digital divide, but it can be as critical as creating world peace or as fanciful as sharing photos of kittens playing guitars on the Internet. The importance of community is not in the crusade, but in how you unify people to march forward together, side by side. At its heart, The Art of Community is a distilled set of approaches and thoughts about how to build community. The book is a collection of experiences, observations, and thoughts from my career and elsewhere. My aim is to bring this grab bag of concepts and curiosities together into one consistent text.

However, it is important that we keep the book in perspective in the wider scheme of your growth as a community leader and organizer. You should mentally frame the content here as a foundation for your own ideas, but remember that practical experience is the real magic that we want to create, with theory merely the glittery jacket and spinning bow tie. Community is fundamentally a soft science. Compare it with, for example, programming. If you want to write a computer software application, you write it in a programming language. These synthetic languages are vessels of logic. They live and breathe in a world where the answer to a question is either yes or no ; there is no maybe. In a world where maybe does not exist, you can plan ahead for an answer. With community, the importance and diversity of the question is equally essential.

But Neil is not unusual. At least, not in the Open Source, Free Software, Libre, and Free Culture world. There are many Neils all over the globe, organizing groups, setting up mailing lists, scheduling meetings, and coming together to share an ethos : the combined set of beliefs, customs, and sentiment that flows between like-minded people.
In the last 10 to 15 years, we have seen Free Culture in technology, art, and media explode into our consciousnesses. The entire machine is driven by people like Neil: people who volunteer themselves to the concepts of community and togetherness wrapped around such an ethos.

There are Neils outside the Free Culture world, too. They’re in church groups, helping the poor and unfortunate; in Neighborhood Watch and Meals on Wheels campaigns, reaching out to those around them; and in public art installations, political groups, and craft fairs. They volunteer, perform, and share their opinions and creativity on anything from aerobics to knitting to yoga.

## The Essence of Community

On February 26, 2004, three friends and I released the first episode of a new audio show called [LugRadio](https://www.lugradio.org/). Although LugRadio will be featured extensively in this book as a source of stories, all you really need to know about it right now is that (a) it was a loose and fun audio show (a podcast) about open source and free culture, (b) on that day it was entirely new, and (c) we had absolutely no idea what on earth we were doing. Radio personalities across the world were not exactly shaking in their boots.

Recorded in a very small room that I called a studio, but was actually a bedroom filled with secondhand recording equipment, LugRadio involved my three compadres and me opining into four precariously balanced microphones that fed into a computer. Episode 1 was around half an hour long, composed of bad jokes and a book review, and totally unpolished. At the time, it was just new and different. (Little did we know that four years later we would wrap up the show having achieved over two million downloads.) Anyway, enough of the self-congratulatory back-patting and back to the story….

With the show out, we did what many of us in the open source world do—we set up forums, wikis, and channels, and tried to get people together around our new project. The forums went online first, and people started joining.

The 22nd member was a guy called Ben Thorp, known as mrben on the forums. An Englishman living in Scotland, mrben was an open source enthusiast who stumbled onto the forums,
listened to the show, and liked what he heard. For the four years that LugRadio lasted, mrben was there every single day: in total contributing over 3,000 posts; involving himself in the chat channel, the wiki, and the organization of the live events; running an episode download mirror; and much more. mrben was there every step of the way, loving every second of it.

The first question is—why? Why does a 30-something Engli-Scot decide to immerse himself so deeply in a group of people he has never met before? What is it that makes him want to spend time away from his friends and family to contribute to a radio show performed by four strangers in a different country? Why would he want to contribute to something with seemingly no financial, career, or other conventional benefit to him? A cynic could argue that mrben is some kind of socially challenged nerd who can only communicate with other similarly socially inept nerds. Conventional wisdom sometimes argues that anyone who contributes their time freely to something that could not benefit them financially is weird. This was clearly not the case with Ben. He had a job, a wife, and a child. He went to church regularly. When I had the pleasure of socializing with him, I found him a fun, smart, and entertaining part of the group. In fact, at two of the live events, he was a guest in my home. Social deviation was clearly not the answer, or if it was, he hid it well. The reason why Ben was so involved in LugRadio, why Neil ran the Linux User Group meeting, and why thousands of other community members around the world get together, comes down to one simple word: belonging.

By definition, a community is a collection of people (or animals) who interact together in the same environment. Community exists everywhere in nature. From people to penguins, from monkeys to meerkats, the vast majority of organisms exhibit some form of collective grouping. Grouping, however, is a touch simplistic as a means to describe community. It is not merely the group that generates community, but the interactions within it. These interactions, and the feeling of belonging that they produce, are generated from a distinctive kind of economy: a social economy.

## Building Belonging into the Social Economy

At this point in our journey, it is clear that belonging is our goal. It is that nine-letter word that you should write out in large letters and stick on your office wall. It is that word that should be at the forefront of your inspiration behind building strong community. If there is no belonging, there is no community.

From the outset, though, belonging is an abstract concept. We all seemingly understand it, but many of us struggle to describe it in words. I identify belonging pragmatically: as the positive outcome of a positive social economy. In the same way that we judge a strong financial economy by prosperity, wealth, and a quality standard of living, belonging is the reward of a strong social economy.

An economy is a set of shared concepts and processes that grow and change in an effort to generate a form of capital. In a financial economy, participants put goods and services on the market to generate financial capital. The processes and techniques they use include measuring sales, strategic marketing, enabling ease of access, and so forth. A social economy is the same thing—but we are the product, and the capital is respect and trust. The processes and techniques here are different—open communications mediums, easy access to tools, etc.—but the basic principles are the same.

Social capital is known by us all, but we know it by many different words: kudos, respect, goodwill, trust, celebrity, influence, supremacy, greatness, and leverage, to name a few. The first known use of the term “social capital” (referred to in Robert Putnam’s *Bowling Alone: The Collapse and Revival of American Community* [Simon & Schuster]) was by L. J. Hanifan, a school supervisor in rural Virginia. Hanifan described social capital as “*those tangible substances [that] count for most in the daily lives of people: namely goodwill, fellowship, sympathy, and social intercourse among the individuals and families who make up a social unit….*”.

Social capital is the collective family of positive interactions between two or more people. When you affect someone positively, it builds your social capital. This could include being generous, helping someone, sympathizing over a problem, or something else. Hanifan identifies the opportunity behind social capital:

> The individual is helpless socially, if left to himself…. If he comes into contact with his neighbor, and they with other neighbors, there will be an accumulation of social capital, which may immediately satisfy his social needs and which may bear a social potentiality sufficient to the substantial improvement of living conditions in the whole community. The community as a whole will benefit by the cooperation of all its parts, while the individual will find in his associations the advantages of the help, the sympathy, and the fellowship of his neighbors.

The meat in Hanifan’s description is the opportunity for social capital to “bear a social potentiality sufficient to the substantial improvement of living conditions in the whole community.” In essence, if a member of your community has a positive approach to another member, her social capital grows, which has a positive impact on that person and the community as a whole. It all sounds a lot like karma, and it is.

Of course, capital, whether monetary or social, is not the end game. People don’t make money for the purposes of just having money: they make money because it allows them to do other things.

This is an important aspect of understanding where an economy starts and ends. Most folks riding the financial economy are not purely greedy numbers freaks who just want a big pot of money; most people who work with social capital are not merely air-kissing, hand-wavey, superficial animals who simply want to name-drop and be name-dropped in the interests of social acceptance. Of course, the greedy and the socially obsessed do exist, but it is important not to use them as a basis for judgment. The economy is not flawed; those people are flawed.

A final point: for an economy to work, every participant needs to believe in the economy. Belief is a critical component in how any group of people or animals functions. This can be belief in God, belief in values, or belief in a new future. Whatever the core belief is, the economy and the community can be successful only if everyone has faith in it.

So let’s have a quick recap:

* A sense of belonging is what keeps people in communities. This belonging is the goal of community building. The hallmark of a strong community is when its members feel that
they belong.
* Belonging is the measure of a strong social economy. This economy’s currency is not the money that you find in your wallet or down the back of your couch, but is social capital.
* For an economy and community to be successful, the participants need to believe in it. If no one believes in the community that brings them together, it fails.
* Like any other economy, a social economy is a collection of processes that describe how something works and is shared between those who participate.
* These processes, and the generation of social capital, which in turn generates belonging, needs to be effectively communicated.

So far, we have talked extensively about our goals (belonging), the medium of exchange (social capital), and what is at the heart of an economy (processes). We now need to focus on the final component that binds each of these concepts together: communication.

In many ways, an economy is like a flowing river: it never stops, and the flow is critical to its success. Economies never stand still. Every day they change, adjusting to stimuli in the world that affects them. At the heart of how this movement works is communication.

## The Basis of Communication

Peter Bloch, a consultant on learning, makes an important foundational observation about communication in a social economy: “community is fundamentally an interdependent human system given form by the conversation it holds with itself.” When I first heard that quote, I realized that the mechanism behind communication in a community is stories. Stories are a medium in which we keep the river flowing. They are the vessels in which we not only express ideas (“I was taking the subway to work one day, and I saw this lady on there reading the paper, and it made me think xyz”), but also how we learn from past experiences (“There was one time when I saw David do xyz and I knew I had to adjust how I myself handle those situations in the future”). Furthermore, when the characters in the stories are people in a community, the stories are self-referencing and give the community a sense of reporting.
Communities really feel like communities when there is a news wire, be it formalized or through the grapevine.

Not all stories are cut from the same cloth, though. Communities tend to exchange two very different kinds of story: tales and fables.

Tales are told for entertainment value and to share experiences. They are individual units of experience that are shared between people, and their primary value is in communicating a given person’s experience and adding to the listener’s repertoire of stories and experiences.

Fables are different. Fables are stories designed to illustrate an underlying message. The vast majority of us are exposed to fables as children, and these stories are passed down from generation to generation, each one extolling a moral message to the youth of the day.

Let us now take a step back to our earlier story about mrben joining the LugRadio community. This story was itself a tale that shared an experience that encased many of the concepts we have explored.

When mrben joined the LugRadio community, he identified with the ethos of the show. Then he began to engage with stories: first hearing them on the show itself, then getting them from the community, and finally sharing them himself. As mrben contributed more and more, his social capital started to rise—the community had a lot of respect for him and his opinions. He, in turn, had belief in the community and his own abilities. This objectivity in his storytelling and his general demeanor all contributed to his social capital. As he continued to be a part of the community, his sense of belonging developed. At this point, mrben was living and
breathing LugRadio, its community, and its ethos.

The result of this process is a community member with a strong sense of loyalty. Some of the greatest examples of belonging and commitment to an ethos occur when the community is threatened. An interesting example of this was when we released Season 5, Episode 3 of the show and received a rather angry statement from a listener who was clearly agitated at the level of expertise on the show and the generally positive attitude toward Ubuntu (which all of the presenters expressed):

> Nowadays I mostly stick to Dave Yates at lottalinuxlinks who is a genuine linux obsessive, Chess Griffin at linuxreality who maybe does stuff for noobs but is genuinely knowledgeable about Linux, and the guys at the linuxlinktechshow because they work with Linux and know what the f**k they’re talking about.

mrben, who had spent a few years in the community by then, responded to the criticism using stories to make his point:

> I think you’ll find that all of the presenters on LugRadio work with Linux on a daily basis. Whether or not they know wtf they’re talking about is, of course, a matter of opinion. But the addition of Chris and Adam to the team, both of whom (IIRC) are professional Linux sysadmins, is an influx of knowledge on that side of things. Jono has a long history of working with Open
Source and Linux within the community (bingo!) even if his technical knowledge is not at the same level. Aq is a Free software zealot, but is also experienced in web development and usability. I still think it’s a good mix, personally.

> The Ubuntu thing is an issue, admittedly. But then, LugRadio still reflects my experience of LUGs—the majority of people are talking about Ubuntu. It has become the mainstream desktop distro, and the benchmark that most people mark other distros against. But, IMHO, the recent shows haven’t shown an overly Ubuntu slant. Look at this show—you’ve got an interview with
Quim Gil, which is about Maemo, not Ubuntu, the finger of God, which is plain silliness, the software vendors and security issue, which applies across the board, and packaging, which was fairly Ubuntu specific, but could easily relate across to other Debian-based distros, and, as Chris said, he would’ve talked about RPM if it had been possible.

> The “Ubuntu slant” is more about personal usage and experience, rather than a change in the show’s direction (which was unashamedly Debian slanted before Ubuntu came out….)

In his three-paragraph response, mrben referred to 12 distinctive points and facts, citing many from existing online material. His response not only sought to convince the original poster of his error, but to demonstrate to the community that the poster was wrong, thus providing a sense of security. By using objective facts, he also spoke with the voice of the community, not just his own opinion. mrben’s response was driven by belief in the community, formed by familiarity with stories, and legitimized by a wealth of social capital. Subtle, yet inspiring.

Although the underlying social economy infrastructure in community is compelling, it is important to remember that it is merely a structure designed to deliver a far more exhilarating prospect—opportunity. And with that, let’s spin back in time….

## Unwrapping Opportunity

When I first learned about Linux, I was running a small bookshop in Milton Keynes, in Southern England, and living at home, having taken a year off before starting university. When Simon, the eldest of my two siblings, stayed in our house for a few weeks on his return from the U.S., we frequently spent the evenings talking about computers and stand-up comedy. On one of those evenings, while I was hurling abuse at my computer, Simon expressed surprise that I used a “Mickey Mouse Operating System.” I was surprised myself. As far as I knew, Windows—Windows 98, at that—was all that existed. Simon told me about something called
“Linux,” which I could get for free, from the back of a book.

Armed with my 10% discount, I eagerly snagged a copy of Slackware Linux Unleashed, and Simon set to installing Slackware 96 on my desktop computer. Two weeks later, having used guile, cunning, and a soldering iron (literally), and maintaining the alignment of the planets, I actually got the thing to boot. As I gazed eagerly at the screen, ready to experience the next generation of operating system technology, I was confronted with:

`darkstar login:`

It was not exactly Minority Report.

Simon, being the kind and sharing brother he was, wrote the username and password down on a piece of paper, stuck it to my screen, and promptly sodded off. The following day, he moved out. I was left with a login prompt, some nerves, and absolutely no idea of what to do.

So I cracked open the book, threw on a Testament album, and started reading. It was then that I read about the Free Software community: a worldwide collection of enthusiasts all connected by the Internet, sharing an ethos that software should be free while
building a replacement to the Microsoft behemoth that frustrated so many. Piece by piece, this global army provided software alternatives, many of which improved on their commercial counterparts. Back then, Linux was in the dark ages of computing. It was all command-line-driven, devices rarely worked, and to do anything you needed to compile code. Still, this concept of a worldwide community sharing code absolutely fascinated me. I first smelled the sweet aroma of opportunity.

Although the reality of open source in 1998 was primitive, the potential within the community is what inspired me to stick with it. To be honest, I was pretty perturbed by the sheer complexity of it all. In those days it was insanely complicated to get a system up and running, and the innards of the operating system were on display for all to see. (These days, as [Uncyclopedia](https://uncyclopedia.wikia.com/) so eloquently puts it, “Linux distros are so idiot-proof that you can put their install CDs into the floppy drive upside-down and it will still work” [slightly edited for a family audience].) Back then, we all knew that life with Linux was a lot harder than it needed to be, but the strong sense of underlying opportunity helped spark the imagination to put up with that complexity for the potential of a better future.

There is an important connection here in which imagination and opportunity are close friends. Imagination offers the mind a vision of how things could be. If there is a viable path toward this future, we build a sense of opportunity. If there is no viable path, we enter the world of fantasy.

Linux, and the possibility of it becoming a prominent operating system, was by no means a fantasy. The rails were on the ground. The community just needed freely available tools and communication channels to gather the materials, build the train, and put it on the track. In the case of Linux, this manifested in three primary areas:

* Open communication – With an open community and publicly visible and accessible communication channels, anyone can join the community and meet hundreds of thousands of other community members just like them.
* Licensing of work – Every contribution to the Linux community is licensed in such a way that it benefits the entire community. The fair licensing of all contributions adds a strong sense of confidence to the security of the community.
* Open tools – Anyone with an Internet connection and a computer can contribute. All of the development tools and documentation are entirely free and open to access. This provides a low barrier to entry, and lets new users play with the technology.

Although these elements were essential at the birth of Linux, it is not open communication, licensing, and tools that generate opportunity. These elements merely made it possible to build a world-class Free Software operating system. Opportunity is born in a sense of belief. Belief is a critically important human function. Whether your belief is in an all-creating god, in a family member’s ability to achieve something for herself, in a better future in your neighborhood, or in the reliability of a restaurant guide, belief is what gives us hope for the world around us. Belief can also make human beings surprisingly resilient in intensely difficult
and uncomfortable situations.

One example of this is an incident that occurred a few years back. Every year, as part of LugRadio we host a face-to-face get-together called LugRadio Live (https://www.lugradio.org/ live/ ), which is a very different style of conference. We have worked hard to deliberately make the conference fundamentally a community event. Equality between commercial vendors and
the community is a key attribute, and we deliberately set a low cover charge to keep it accessible. In addition to this, we have worked to produce a very informal and inclusive atmosphere, inspired largely by music events. (Many referred to LugRadio Live as a “rock conference.”)

LugRadio Live has carved out something of a reputation for being different, and each of its participants has been very keen about advocating it and its formula. There was a strong sense of belief in the event—an event that was distinctively community-oriented and -driven, open to participation, and available to all.

With LugRadio Live scheduled for July 22–23, 2006, everything was going to plan. The speakers and exhibitors were sourced, the schedule was in place, the social events were arranged, and the crew and community were ready. Everything was great until the evening of July 18, when I received news of an impending rail strike. The strike was planned for the full weekend of the event, with every rail link going down. The country would be completely inaccessible by train.

I have never experienced such anger and frustration. For about an hour, I transformed into an ultra-conservative right-wing anti-union crazy, and I stomped around the house, venting in the direction of my computer screen. We had spent six months of feverish planning and hard work, and this union decided that their problems were more important than anyone else’s, and it was entirely reasonable to take the country down. I, for one, was not a happy bunny. But, as my fellow organizers and I seethed on the phone, the community was already doing its thing. Forum threads appeared instantly to keep people up-to-date on the strike, blog entries were drafted, a nationwide car-sharing scheme kicked into play, and speakers and exhibitors were notified. While all of this was going on, I was on the phone tearing a strip out of both the union and the rail organization for their decision. Fortunately, the strike was called off a few days later.

What stunned me was just how mobilized the LugRadio community was. The community saw a threat to something they felt invested in, and reacted as a team to cover all the bases and try to limit the damage. Without any prodding from us, they made things happen. In a time of such panic and frustration, that community wrapped around each of the organizers like a comfort blanket. It was one of the most inspiring examples I have ever seen of a community coming together, driven by a belief in something we all shared.

Where belief gets exciting is when it is combined with that friend of ours from a few pages back: opportunity. Belief in a shared crusade—and a sense that the tools and opportunities are available to achieve that goal—is an intensely liberating feeling. People get a sense that they have control over their own destiny.

An example of this was the election of Barack Obama as president of the United States. Building up to his victory, the U.S. was facing difficult times. Led by a president who many lacked faith in and faced with a global economic crisis and a complex set of foreign affairs, the U.S. had a lot to deal with, including a growing sense of cynicism among its people. Many Americans had
lost faith in politics and pride in their country. As Barack Obama stepped up as a candidate for the presidential election, he instilled a sense of belief and opportunity that inspired his followers.

When people feel that they can achieve a dream, it builds an incredible sense of liberation and a willingness to step up to the plate. People become very committed, very quickly. We saw this in droves throughout the presidential election. Thousands of people across the country took to the streets to tell the world about Obama.

Around that time I had kissed chilly England goodbye and relocated to sunny California. The Bay Area was a particularly fascinating place to be—people setting up tables, selling stickers, knocking on doors, and making phone calls. It seemed that one in three people on the street was wearing an Obama t-shirt.

Whether Obama was the right man for the job is the topic of a thousand other books, but he had the ability to define belief, opportunity, and liberation in a language that a nation could understand. His inspiration—and his army of passionate Obamaniacs—sealed his place in the Oval Office. This in itself was an incredible exercise in building, energizing, and inspiring community, and regardless of your political inclination, it was a stunning feat.