Open Source Community Metrics and State of the Puppet Community

Many of you probably know that I’ve spent the past week in Belgium for Puppet Camp Ghent and FOSDEM. I’ll be writing a blog post on the Puppet Labs blog later this week to talk about Puppet Camp Ghent, but I wanted to at least get my presentations out here while I finished writing the longer post.

Puppet Camp Ghent was amazing. I saw a few old friends and connected in person with quite a few community members that I had not yet met in person. Overall, I was very happy with the event, and the people at HoGent were great hosts. There were so many amazing presentations, and we’re getting them uploaded to the Puppet Camp page as soon as we get the slides from the speakers. Here is the presentation that I delivered on the State of the Puppet Community.

state-of-puppet-community

I had an amazing time at FOSDEM, too. I helped facilitate the Configuration / Systems Management DevRoom on Saturday along with a DevRoom dinner that evening. I love working in such a collaborative industry. The DevRoom and the dinner were organized collaboratively with our primary competitors, but we all worked together to pull it off in a way that benefited the industry. Aside from the DevRoom, I got to see a lot of old friends and had a great time!

At FOSDEM, I also gave a short version of my Open Source Community Metrics talk. If you are interested in open source metrics, you might rather look at the longer version that I presented at LinuxCon Barcelona in November. I also had a great conversation from Jesus at Bitgeria, and they are doing some awesome stuff with open source community metrics that you should look at if you are interested in metrics.

Next on my agenda are trips to Stockholm, Sweden and Oslo, Norway for two more Puppet Camps in the next two weeks before heading back home to Portland.

Lurking and Learning as a New Community Manager

LurkingI started working at Puppet Labs during the last week of September. During the interview process and in the first few weeks, I made sure people knew that I would spend my first month or two lurking in the community while I learned about how people participate in this community. I’ve been working with open source and communities for more than a decade, but this is still an essential step when you are new to a community as a community manager*.

I’ve seen too many over-eager new community managers jump into the community early and make mistakes by violating community norms, talking about things that aren’t relevant, making people unnecessarily upset, and just generally making a mess of things. Every community manager makes mistakes at some point, but here I’m talking about the issues that could have been avoided by knowing more about the community before jumping in with both feet.

Don’t be afraid to let other people do most of the responding while you learn from them. By taking the time to observe and lurk for a bit, you can learn about how people behave and get a feel for how people typically respond.

This doesn’t mean that I spent my first month sitting on my butt. As part of the learning process, I spent a lot of time talking to other employees about what works well in the community and about what isn’t working. As a part of talking about the things that weren’t working, I focused on what was causing the most pain for our engineers and started thinking about how we could make things better. I came up with a big list of things to tackle and started talking to people about plans for improving some of the community processes that were the most painful. I’ve started working on a few of these already, and others are in my 2013 plans.

I also worked on a lot of documentation and improvements to website content during this first month. We really didn’t have community guidelines or other standard documentation. Since community guidelines are relatively similar for many open source projects, I got a good start on those in the first month. I also focused on getting monthly community metrics published. I actually got a ton of work done during my first months. It just wasn’t publicly visible work.

Don’t be afraid to work behind the scenes for your first month or two while you learn about the community. If you make sure that your manager and colleagues know why you aren’t publicly visible while making sure that your work behind the scenes benefits the company, people are more likely to see it as an important and necessary part of the process of starting this new job.

Additional Reading:

*If you were hired out of a community where you have already been participating or are hired to work on a newly launched community, this advice probably doesn’t apply to you.

Photo by Stephen Jones used under a Creative Commons license.

 

2012 Year in Review

Family Margaritas and ScrabbleEvery year, I like to write some kind of year in review blog post. I started writing these in 2007 as  a way for people that I don’t talk to very often to keep up with what I’ve been doing, but I’ve found that it helps me see what I’ve accomplished (or not accomplished) that I can use to reflect on what I want to do in the next year. You can find the 2007200820092010, and 2011 editions if you want to see how this year compares with previous years.

2012 in Review

This year, I spent more time doing things that I enjoyed: reading, running, working in a job that makes me happier and much more!

  • The single biggest change I made in 2012 was leaving Intel and taking some time off before joining Puppet Labs. I had been at Intel for 2.5 years (along with an earlier stint from 2000 – 2006). While I loved the people I worked with (and miss them), the job left me drained of energy, and I just wasn’t passionate about it anymore. I left without a real plan other than to take a month (or a few) off before starting anything new. I used this little sabbatical (aka funemployment) to read, run and hang out with friends. I started at Puppet Labs 7 weeks later feeling relaxed and recharged. I’m loving the work and enjoying being back in a startup!
  • I read over 70 books last year! Most of them were science fiction / fantasy, and I keep a list of everything that I read here on my blog.
  • I also ran … a lot. In 2012, I ran over 470 miles, and just over 100 of those miles were in August during my funemployment. My longest run of the year, also the longest run of my entire life, was 11.3 miles (just 1.7 miles short of a half-marathon distance). I also did some weight lifting and other workouts. Aside from falling off the wagon over the past month due to a couple of back-to-back colds, I’m feeling pretty good on the fitness side.
  • Like last year, I did a fair bit of travel. For work, I went to Brussels, Belgium; Seoul, South Korea; Berlin and Nuremberg, Germany; and Barcelona, Spain. For fun, I took trips to Hawaii, Seattle, Las Vegas, and Ohio to visit family. I even have pictures from many of the trips posted on Flickr.
  • As part of this travel, I presented at a few conferences. I did a few Tizen presentations earlier in the year, but recently, I’ve been speaking about open source metrics at LinuxCon in Barcelona and the LibreOffice Conference in Berlin.
  • I’ve also been dabbling with programming again, mostly in Ruby, since that’s what everyone at Puppet Labs uses. I’m pretty terrible at it, since I haven’t done any real programming since the mid-90’s, but it’s enough to accomplish a few simple things and be more self-sufficient. And, I enjoy doing it 🙂
  • I am still selling my vegan cookbookWhat Dawn Eats: Vegan Food That Isn’t Weird. It was published last year and is available in paperback, Kindle edition and PDF format.

If I look back to what I wanted to accomplish in 2012 from last year’s year in review, I did pretty well!

  • I continued to travel and visit new places (South Korea, Spain and maybe Belgium were new last year).
  • I wanted to do runs in the 8-13 mile range and more regularly hit the gym to lift weights. I made it just over 11 miles, which is pretty good, and I did quite a bit of weightlifting, so I feel good about this one, too.
  • For several years, I’ve been wanting to do some light programming, and this is the year that I finally started real work on that one!
  • I also said that I wanted to get to a point where I can actually carry on a conversation in French that goes beyond basic greetings and travel phrases in 2012. With one lesson a week, it’s taking a while, but I’m finally getting to the point where I can carry on very simple conversations … as long as you speak very slowly, repeat yourself a few times and use mostly words that I already know 🙂
  • I failed miserably at my goal to keep my blog updated.

What I Want to Accomplish in 2013

  • Yet again, I’m going to make an effort to blog here more often.
  • I want to travel to even more new places. I’m off to a good start on this one, since I’ve already scheduled a work trip for February in Belgium, Norway and Sweden along with a fun trip with mom to Aruba in May!
  • I plan to continue meeting my fitness goals from last year with regular running, weight lifting and other activities. This will be a little more challenging because I expect to be doing quite a bit of travel this year, and working out is a lot harder when you are jet-lagged and busy working in another time zone. While I was happy with my general fitness in 2012, I still tend to eat too much, so I’ll work on that a bit.
  • I also want to continue to work on my French. I’d love to be more conversational next year and ideally, be able to read simple books and watch movies in French without relying entirely on the subtitles.
  • I hope to spend more time writing code. In addition to being more self-sufficient, I would also like to learn how to not suck at it by spending the time to learn how to do things properly rather than just doing whatever gets the job done the fastest.
  • While I want to continue to read, I actually need to pull back on that a bit. I love reading, but it’s taking too much time away from other activities, so I’m going to try to read a bit less to free up more time to actually do the things mentioned above!

Blogging Elsewhere

I’ve been neglecting my blog, but it isn’t because I haven’t been blogging. I just haven’t been blogging here 🙂

Here are a few posts that I’ve written over the past couple of months for work as part of my Community Manager gig at Puppet Labs:

I also wrote a few posts on my cookbook site, What Dawn Eats. Don’t forget that you can buy the cookbook (available in paperback, kindle edition or PDF)!

Open Source Community Metrics: LinuxCon Barcelona

I wanted to share the presentation that I will be giving today at LinuxCon Barcelona at 1:20pm, Open Source Community Metrics: Tips and Techniques for Measuring Participation. This is similar to the presentation that I gave a few weeks ago at the LibreOffice Conference in Berlin, but I have added some new data and included different examples. You might also be interested in seeing the Puppet Community Metrics that I recently started posting on the Puppet Labs website.

You can download the presentation from SlideShare.

Talk Abstract:

Do you know what people are really doing in your open source project? Having good community data and metrics for your open source project is a great way to understand what works and what needs improvement over time, and metrics can also be a nice way to highlight contributions from key project members. This session will focus on tips and techniques for collecting and analyzing metrics from tools commonly used by open source projects. It’s like people watching, but with data.

The best thing about open source projects is that you have all of your community data in the public at your fingertips. You just need to know how to gather the data about your open source community so that you can hack it all together to get something interesting that you can really use. This session will be useful for anyone wanting to learn more about the communities they manage or participate in.

LibreOffice Conference: Open Source Metrics

Today at the LibreOffice Conference in Berlin, I will be presenting a session titled, “Open Source Community Metrics: Tips and Techniques for Measuring Participation.” It has tools, techniques and examples of metrics from the LibreOffice project, Puppet and MeeGo to illustrate several ways to gather and interpret the metrics for your open source project.

If you are interested in watching the presentation, it will be on the LibreOffice Conference live stream starting at 18:00 CEST in Berlin or 9am Pacific time.

You can also download a copy of the presentation from SlideShare.

Talk Abstract

Do you know what people are really doing in your open source project? Having good community data and metrics for your open source project is a great way to understand what works and what needs improvement over time, and metrics can also be a nice way to highlight contributions from key project members. This session will focus on tips and techniques for collecting and analyzing metrics from tools commonly used by open source projects. It’s like people watching, but with data.

The best thing about open source projects is that you have all of your community data in the public at your fingertips. You just need to know how to gather the data about your open source community so that you can hack it all together to get something interesting that you can really use. We’ll start with some general guidance for coming up with a set of metrics that makes sense for your project and talk about the LibreOffice community metrics. The focus of the session will be on tips and techniques for collecting metrics from tools commonly used by open source projects: Bugzilla, MediaWiki, Mailman, IRC and more. It will include both general approaches and technical details about using various data collection tools, like mlstats. The final section of the presentation will talk about techniques for sharing this data with your community and highlighting contributions from key community members. For anyone who loves playing with data as much as I do, metrics can be a fun way to see what your community members are really doing in your open source project.

Community Manager at Puppet Labs

After being lazy and taking a nice little month and a half off of work after leaving Intel, I’m happy to announce that I have just accepted the Community Manager job at Puppet Labs. I will be spending most of my time during the first month just lurking and learning more about the community while working on things like community metrics before diving too far into the job.

I am super excited to be working at Puppet Labs. It’s a great team of people, and I’m looking forward to working at a startup in downtown Portland again!

I’ll be starting at Puppet Labs on Thursday during PuppetConf in San Francisco. James will have a session on the State of the Community at Friday at 10:45 (you can watch the live stream) if you want to learn more about the Puppet community.

If you’ll be at PuppetConf on Thursday or Friday, find me and say hello!

Leaving Intel and Moving On

After over two years of leading the community efforts for the Open Source Technology Center, I have decided to leave Intel. This was a really tough decision for me, but the reality is that the job isn’t the right fit for me right now for a variety of reasons. I want to thank the management of the Open Source Technology Center for working with me during the process of trying to make the job work better for me. It’s a great team of people who continue to do really interesting work in open source.

But, it was more than just the job. I’ve worked in large companies and startups, and I’ve realized that I really want to get back into a startup again. I miss the energy of working in a startup where everything moves faster than in a large corporation.

I’ll be taking the rest of August mostly off to relax and work on a few geeky personal projects. Starting in September, I’ll either take a full-time job or do some consulting while I continue to look for the right opportunity. I’ve already starting talking to a few people, and I would like to eventually land at a startup in a Director / VP level community, evangelist or open source position. I’m willing to take my time to find the right fit, and that includes finding a job where I can live in Portland, but travel to other places as needed.

I feel very fortunate to have some flexibility and other options that allow me to make this move now. As a result, my last day at Intel will be August 7. While I will miss many of the friends and smart people I’ve worked with at Intel, I feel like this is the right decision for me at this time.

Photo by Patrick McGarvey used under a Creative Commons license. A side note: this is one of my favorite roller coasters, The Maverick, at Cedar Point in Sandusky, Ohio, and I plan to ride it on vacation next week! 🙂

Community Manager Tip: Take a Fresh Look

Keep It FreshMost of us get into the swing of our day to day routine and work habits, which can be good most of the time. However, occasionally, you need to take a fresh look at your community to get a new perspective on what you have. We sometimes remember to do this when we notice issues, but the best time to do this is when the community is healthy.

When was the last time you really looked at your primary landing page for your community? Take the time to really look at everything on that page, and remember that your landing pages are primarily for new and prospective community members, since active community members will just dive right into the heart of the community. Is everything still relevant? Does it focus on the right things for your community to help new community members easily find what they need?

When was the last time you looked at every page on your website or your wiki to see what information was out of date or irrelevant? This may not be practical for a very large community, but you can use your analytics programs to help you at least find the most frequently used pages to review.

Are the discussions in your community productive and appropriate? Take a hard look at what people are discussing and the tone of those discussions. If it doesn’t feel right for your community (and this varies for each community), then spend some time thinking about what you can do to make it better.

Additional Reading

Photo by Mars Infomage used under a Creative Commons license.

Community Manager Tip: Don't Copy

This is the first post in an attempt to resurrect my Community Manager Tips series, a collection of short posts to share quick tips for community managers, to get me back into the blogging habit.

People often ask me for a list of the “best” communities that they can use as a model when building their own community, but this is fundamentally the wrong question. Each community has a different audience, different goals, and a different purpose. Building your community based on what works for another successful community can fail very quickly if that community doesn’t have the same needs as your community.

A better question is, “what type of communities are my competitors building and what does or doesn’t work for them?” Your top competitors are likely to be more similar to you than other companies, and this gives you a place to start. Spend some time lurking in your competitors communities to see how they work and try to get a feel for what works and doesn’t work for them. Look for common complaints, and come up with interesting ways to solve them in your community. Pay attention to what people enjoy or get excited about, and think about how you might get people excited about your community. You shouldn’t model your community on a competitor’s community, but this analysis along with some basic best practices will probably give you a start for how you want to build your community or improve an existing one.

Don’t copy other companies. Build something unique that will work well for your audience while also meeting your goals.

Additional Reading

Part of a series of community manager tips blog posts.

Photo by Juliancolton2 used under a Creative Commons license.

Open source, Linux kernel research, online communities and other stuff I'm interested in posting.