by Zohar Babin
Community managers are used to talk about traffic, social, forums and code analytics... But who is all that relevant to the bottom line? How do you communicate the value of your project and project's community to investors and potential sponsors? How do you measure dollars where participation is the currency?
There is no shortage of algorithms, techniques, and software to produce virtually any metric one may desire. True value is only realized when metrics are chosen that most closely align with your goals.
In this session, learn which goals we chose in the Liferay project (a large, open source portal project), why they were (and continue to be) important, how they are produced, and what we are doing with them.
FLOSSmole, FLOSShub and the Sourceforge Research Data Archive (SRDA) are repositories of papers and data describing how FLOSS is developed. Collectively these community resources store several terabytes of data, which includes both artifacts of the software creation process and metadata about the FLOSS projects and developers. This presentation describes a new collaborative project that will expand, enhance, and integrate these community resources serving the FLOSS research community. The project will capitalize on years of successful collaboration amongst the maintainers of the resources to become a new developmental framework for facilitating access to the massive amounts of data collected by many previously unconnected FLOSS research efforts. Goals also include development of tools to mine that data, an expanded papers repository, and a unified portal to promote collaboration. The presentation will describe the current metadata archives, architectures, and services, followed by planned integration and enhancements.
MetricsGrimoire is a set of tools for retrieving data from git, Subversion, Bugzilla, Jira, GitHub, Mailman and many other data sources about software development, and organizing them in a database. vizGrimoire is intended to analyze and visualize these data. With all of them, Grimoire Dashboards can be produced, providing information about software development communities, their activity and their processes. The talk will present the main aspects of these tools, how they are being used in real cases, and the reasons why it is important that they are free / open source software.
Debian contributors is a new software for gathering, measuring, and crediting the active participants in the Debian Project, for any kind of contribution, technical or otherwise.
It is a web application with a client reporting tool supporting a wide range of data mining options. It offers comprehensive identity management which allows to credit a person's work across multiple emails, logins or gpg keys.
Results for several data sources and proof-of-concepts are visible in https://contributors.debian.org/ currently retrieving 16 types of contributions (only one of them was previously tracked). Source code is AGPL licensed, and quickly evolving in the public Git repository of the Debian project.
Besides being a technical tool, it is a social experiment: the intent is to change the way the Debian community perceives itself, by making a diverse range of contributions visible, and showing them with the same level of importance.
by Dave Neary
Situational awareness is vital in any situation. If you are unaware of an issue, then you are in a poor position to fix it. However, there is a natural human response to the publication of metrics, which is to optimise for what is measured. Here are some cautionary tales of how performance metrics inadvertently created incentives for behaviour that was bad for the system.
by Karsten Wade
The Open Source Way is a book, website, and community around the best practices of using open source methodologies in projects and other endeavors. In this talk, learn how to incorporate your work and practices in to this useful handbook.
I work in the automotive industry. The automotive folks like spreadsheets with hard data, clear metrics, and straight-forward presentations. I'd like to present what I'm sharing with the automotive folks now and get some feedback on whether I've covered all the important metrics -- what am I missing?
LibreOffice forked the OOo code betting on the growth of the first 20 developers. Thanks to a number of strategic moves, the project managed to attract 80 new developers during the first month, and 3 or more new developers each month for 44 months in a row. How we have measured the growth to motivate additional developers to join the project.
by Simon Phipps
Measurement modifies behaviour as well as observing it. My experience of certain metrics used at Sun to measure performance of community programmes shows there can be unwanted consequences if metrics are managed unwisely.
Open Source is People not Corporations. What then is the effect of relentless quantification behaviors engendered by corporate participation in open source projects?
Measures of social activity, blog posts, new code proposals, issue resolution, committer growth, etc., can be useful, and sometimes satisfy corporate interests, but are not clear indicators of one thing or another. So, I want to ask: What does the developer want? What sort of metric, what measures of project activity and identity, would help her work better in the community?
The Eclipse dashboard, and the Eclipse Foundation views about being transparent about corporate contributions.
Assuming being entitled to an opinion is all about having your views treated as serious candidates for the 'truth’, procuring open source software demands some investigations. To use or enhance a given open source project's artifact you need some factual evidence you're doing the right choice.
Dozen of so-called 'open source maturity models' have failed in the past, this talk will briefly describe a pragmatic and efficient method to make your mind in few steps.