First off, Happy 5th Birthday Ubuntu! I first installed Ubuntu on a machine on March 12, 2005. Impressively precise date, huh? That’s because I signed up on ubuntuforums.org the same day.

In an interesting coincidence, this morning I had the pleasure of attending my first Ubuntu Community Council Meeting as a Council Member. And we don’t start small with our new council! The major topic was ratifying revisions to the Ubuntu Code of Conduct, version 1.1. The rationale behind the changes can be found here and the full text of the revised Code of Conduct is here.

So here’s one of your birthday gifts, Ubuntu, a shiny new Code of Conduct!

Ubuntu Code of Conduct v1.1

This Code of Conduct covers our behaviour as members of the Ubuntu Community, in any forum, mailing list, wiki, web site, IRC channel, install-fest, public meeting or private correspondence. Ubuntu governance bodies are ultimately accountable to the Ubuntu Community Council and will arbitrate in any dispute over the conduct of a member of the community.

”Be considerate.” Our work will be used by other people, and we in turn will depend on the work of others. Any decision we take will affect users and colleagues, and we should take those consequences into account when making decisions. Ubuntu has millions of users and thousands of contributors. Even if it’s not obvious at the time, our contributions to Ubuntu will impact the work of others. For example, changes to code, infrastructure, policy, documentation, and translations during a release may negatively impact others’ work.

”Be respectful.” The Ubuntu community and its members treat one another with respect. Everyone can make a valuable contribution to Ubuntu. We may not always agree, but disagreement is no excuse for poor behaviour and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important to remember that a community where people feel uncomfortable or threatened is not a productive one. We expect members of the Ubuntu community to be respectful when dealing with other contributors as well as with people outside the Ubuntu project and with users of Ubuntu.

”Be collaborative.” Collaboration is central to Ubuntu and to the larger free software community. This collaboration involves individuals working with others in teams within Ubuntu, teams working with each other within Ubuntu, and individuals and teams within Ubuntu working with other projects outside. This collaboration reduces redundancy, and improves the quality of our work. Internally and externally, we should always be open to collaboration. Wherever possible, we should work closely with upstream projects and others in the free software community to coordinate our technical, advocacy, documentation, and other work. Our work should be done transparently and we should involve as many interested parties as early as possible. If we decide to take a different approach than others, we will let them know early, document our work and inform others regularly of our progress.

”When we disagree, we consult others.” Disagreements, both social and technical, happen all the time and the Ubuntu community is no exception. It is important that we resolve disagreements and differing views constructively and with the help of the community and community processes. We have the Technical Board, the Community Council, and a series of other governance bodies which help to decide the right course for Ubuntu. There are also several Project Teams and Team Leaders, who may be able to help us figure out the best direction for Ubuntu. When our goals differ dramatically, we encourage the creation of alternative sets of packages, or derivative distributions, using the Ubuntu Package Management framework, so that the community can test new ideas and contribute to the discussion.

”When we are unsure, we ask for help.” Nobody knows everything, and nobody is expected to be perfect in the Ubuntu community. Asking questions avoids many problems down the road, and so questions are encouraged. Those who are asked questions should be responsive and helpful. However, when asking a question, care must be taken to do so in an appropriate forum.

”Step down considerately.” Members of every project come and go and Ubuntu is no different. When somebody leaves or disengages from the project, in whole or in part, we ask that they do so in a way that minimises disruption to the project. This means they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off.

We pride ourselves on building a productive, happy and agile community that can welcome new ideas in a complex field, and foster collaboration between groups with very different needs, interests and goals. We hold our leaders to an even higher standard, in the Leadership Code of Conduct, and arrange the governance of the community to ensure that issues can be raised with leaders who are engaged, interested and competent to help resolve them.

In the coming days the old CoC will be updated with version 1.1 in all the relevant places on Ubuntu sites.

I gave my Expanding Involvement in F/OSS talk at PLUG West this past Monday. One of the great things about PLUG is how our different venues give us different audiences. When I gave this talk down at our Central chapter held at USP the majority of the audience was college kids, hobbiests and consultants, while talks at a business park in Malvern yield a wider audience of IT professionals in large companies. Since I encourage audience participation during my talks, the direction the talks took was very different in each area, at Central we ended up with the lead dev of OpenHatch.org giving a demo, at West we ended up discussing how F/OSS is marketed.

Now my talk focused on getting more people to contribute to F/OSS, in part, by attracting contributions from people who traditionally may not have been involved, more stay at home moms, professional usability experts, Joe the Plumber testing your point of sale project running on Linux. The point that brought us in the general Marketing direction was when I said “F/OSS needs to change their Marketing strategy to get these people interested” and immediately I received a comment from the audience “F/OSS has a marketing strategy?” Everyone laughed, but I quickly wrapped up the rest of my slides (this was toward the end anyway) and our Q&A focused on the Marketing of F/OSS. A lot of great points came up in the discussion that I hadn’t thought much about.

Some of the topics that were discussed:

How do I convince my neighbor to switch?

Within the F/OSS community we frequently want to tout the virus-free nature of Ubuntu and how it’s free. In some ways I believe we’ve already converted most of the adventurous folks we can convert by using these arguments and randomly giving out LiveCDs

For the rest of our audience? Unfortunately we’re up against a couple of common misconceptions:

1. Computers are supposed to crash and have viruses, when the computer gets slow you reboot, reinstall or take it to the computer shop down the street
2. Windows is free, it came with the computer!
3. Software is a black box on the shelf, there no way to impact development, feature requests or bugs, you just have to buy something else if there is a problem or deal with it and hope the next version fixes it

It’s time to redefine our message and get more personal.

1. Offer support personally, through your LoCo team and introduce them to the Ubuntu support community
2. Do demos where you show off Synaptic, not only is Ubuntu free (afterall, “Windows is too”) but all these thousands of amazing software packages are also free!
3. Don’t oversell it – I love Ubuntu and have been using Linux full time for almost 8 years, it’s tempting to just tell stories about marathon uptime and flawless upgrades, but people will run into problems. The key is to carefully impress upon the potential user that every OS has problems, but the ones in Ubuntu are ones you can fix, complain about, maybe even help resolve!

Related to this question but perhaps drifting away from the neighbor example. I also believe in selling a solution, not necessarily F/OSS itself. When you approach a non-profit to help them create a classroom where they can teach job-hunting on the internet, bring in a small Ubuntu Linux Terminal Server Project deployment (can be three old laptops, one acting as a server and the others as thin clients) as a demonstration of what can be done with a handful of discarded Pentium 3s. Use this for free, on old hardware, and there is no need to maintain OS installs on a whole room full of PCs! Another example is an Open Source Personal Video Recorder, by far the most successful events for “regular people” that Ubuntu Pennsylvania has hosted have been our Mythbuntu presentations and installfests. It’s not Ubuntu we’re getting people to switch to, it’s a Tivo alternative with many benefits that include lower cost and more flexibility.

How do I explain that F/OSS is Free (as in beer)?

At the Trenton computer festival earlier this year we had an encounter with a fellow who decided to argue with us about whether Ubuntu could be anywhere near the quality of Windows since Microsoft pours hundreds of millions of dollars into development and Ubuntu doesn’t have near that much and it’s given away for free. This surprised me, and was difficult to convincingly respond to on the spot.

And perhaps more important than responding to a single person at a computer festival? Business-wise, there are companies pouring a significant amount of money into marketing their products and portraying F/OSS as “insecure, unreliable, unsupported and developed by random people on the internet.” This misconception is one that the F/OSS community needs to work against.

Much of what we came up with during the discussion at the meeting is that it’s not strictly volunteers working on F/OSS. Companies all over the world are built using F/OSS and are constantly contribute back, LinuxForce (if I do say myself!), Google, Linode and Unisys are the first examples that come to mind, but there are thousands and thousands of others that contribute in large and small ways by employees who are paid for development. You also have companies like Red Hat and Canonical who have full time developers contributing to the operating systems and run with a business model of support contracts rather than software sales. Contrary to popular belief, today’s F/OSS demographic is not all white college nerds in basements.

I’d also be interested in seeing articles about the finances of F/OSS (something more concrete, practical and current than The Cathedral and the Bazaar, please) so I could better explain with real examples.

How do I get non-standard contributors to contribute?

My talk centered around things you can do to make your project attract more contributors of all kinds, but I didn’t explore deeply into how this is done because my talk was too general. I think this probably deserves a whole talk itself.

Our meeting discussion primarily came up with the need to target individual strengths, show how they can be useful within the F/OSS community. It’s very frustrating when I hear people with their “I tried to get my girlfriend to use Ubuntu, but she didn’t care” lines. If that’s the response you’re getting you’re Doing It Wrong. A perfect example of Doing It Right is from Duda Nogueira yesterday, in his post My mother on Ubuntu Artwork Karmic Release Shortlist!!:

Since she knows about the whole Open Source thing, and uses Ubuntu since 2006, I told her about this contest. She start sending her photos right away! She was excited to help the Ubuntu Project with what she can, and have her photos used all over the world!

Last week, she was VERY HAPPY to to have 5 photos selected to the Ubuntu Artwork Karmic Release Shortlist!

Bravo! Thank you! He shared knowledge about the Open Source community with someone, and knowing her strengths he let her know of opportunities within the community where her skills could be used. There needs to be much, much more of this. F/OSS has opportunities for all kinds of people with all kinds of skills, moreover F/OSS involvement is extremely rewarding on both personal and professional levels. Many people don’t even realize such a community exists, and if they do the assumption is often that it’s “just a bunch of coders, I can’t help.”

There was also a very good article published over at ITWorld.com by Esther Schindler titled Mentoring in Open Source Communities: What Works? What Doesn’t? As we reach out to a broader range of folks to contribute to F/OSS, I feel mentoring programs that work with individuals to pinpoint their skills and interests are important. Huge thanks to Fred Stluka for posting this to the PLUG list following my talk and generally being very engaging during the talk and follow-up discussion. Oh and I do quite like his tradition of buying the speaker dinner when we all go out for food and drinks afterwards, yum, thanks again!

I’ve only scratched the surface of this discussion by summarizing what we were able to discuss at a single LUG meeting, but it’s a fascinating and important topic and one I hope more folks will take time to embrace and discuss.

Last minute addition: Fred just posted this to the list, a second article by Esther, the same subject as my talk: How to Attract More People to Your Open Source Project Excellent!