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.