Community Health Analytics Open Source Software (CHAOSS): An Open Source Community for Advancing Project Transparency - Jesus M. Gonzalez-Barahona, Bitergia;
CHAOSS is a new Linux Foundation project aimed at producing integrated, open source software for analyzing software development, together with defining implementation-agnostic metrics for measuring co …
Talk Title | Community Health Analytics Open Source Software (CHAOSS): An Open Source Community for Advancing Project Transparency - Jesus M. Gonzalez-Barahona, Bitergia; |
Speakers | Matt Germonprez (Professor, University of Nebraska at Omaha), Sean Goggins (Professor, University of Missouri), Jesus M Gonzalez-Barahona (Co-Founder, Bitergia), Harish PIllay (Head, Community Architecture and Leadership, Red Hat) |
Conference | Open Source Summit North America |
Conf Tag | |
Location | Los Angeles, CA, United States |
Date | Sep 10-14, 2017 |
URL | Talk Page |
Slides | Talk Slides |
Video | |
CHAOSS is a new Linux Foundation project aimed at producing integrated, open source software for analyzing software development, together with defining implementation-agnostic metrics for measuring community activity, contributions, and health. The CHAOSS community will help improve transparency of key project metrics, contributing to improve the project itself, as well as helping third parties make informed decisions when engaging with projects.Understanding the community dynamics of open source software projects is of fundamental importance to developers, users, and decision makers, but gaining this needed knowledge is a specialized, time-consuming, and error-prone tasks. The CHAOSS community helps in this task, by highlighting aspects of the projects, tracking relevant patterns, and assisting in the early identification of problems and the detection of trends. In the addition, the CHAOSS community explores what these aspects signal, how they are related to value, and how they might be used in positive or negative ways by people. Collectively, the CHAOSS community work can be used to study the structure of a community and its growth, maturity, and decline, examine project risk and vulnerabilities, understand project diversity, and explore a project’s position within a larger software ecosystem.Publishing these requirements as well as developing working technical systems in the open, so they can be engaged and shaped by everyone, is a step beyond in transparency – enabling better decision making, better awareness of problems, and deeper knowledge about the project dynamics.