About the Editor

Roberto has over 25 years experience in the IT field, and has spent the last 12 years working in the intersection of open source software and business development. Roberto has taken an active interest in different open source projects and organizations, he has served on advisory boards, and helped large IT vendors, open source vendors and customers to design and deploy their open source strategies. After serving as Senior Director of Business Development at SourceForge for over 4 years, in 2016 he started a new company called Business Follows, whose mission is to is to help developers, companies and organizations to make Open Source development a key part of their business strategies. He is the editor of commercial open source blog.

Collection, aggregation and correlation of data fetched by open source public repositories is of great help when you need to assess open source product quality. Let’s see how things are going at QualOSS and what should we expect from them in the next future.

What is QualOSS primary goal?

QualOSS focused mainly on assessing “FlOSS endeavors” from a risk-oriented viewpoint i.e., assess the risk for an enterprise to integrate a particular FlOSS component in one of its software product.

A particular emphasis was put on a situation where the enterprise wants to enter in a full collaboration with the FlOSS endeavor (and not merely fork or exploit the FlOSS component without interacting with the community).

The QualOSS platform has actually become a framework (for lack of a better term). In particular, the measurement part of an assessment is decentralized. It is done by an evaluator using the recommended tools (or measurement procedures) and then entering the measure results in spreadsheets. Risk indicators are computed automatically by these spreadsheets. There is then a repository to centralize the assessment results, which can then be viewed via Specula [a dashboard for project control developed by the QualOSS partner Fraunhofer IESE].

I couldn’t read the Description of Work, and I am looking forward to get it and see at which extent QualOSS is delivering what it was aimed at. Project’s goals are promising, and we have to wait until the second half of August to get the spreadsheets, apparently among the most relevant results of the project. Now they are testing an improving measures and indicators on various FLOSS endeavors, final results are due around the end of September/middle October [The project has been extended until November 2009.]

Tell us something more about the project.

The decision for changing the platform into its current framework comes from the following observations:

The strength of Ohloh is its presentation; however its weakness is the lack of traceability on how they got the results;

The strength of QSOS and OpenBRR is their ease of applicability (via spreadsheet or xul forms).

Furthermore the spreadsheet or xml files provide some traceability from the results to the raw data (from which these results were obtained). However, the weakness is the lack of presentation and in particular, they do not foster sharing assessment results as done by Ohloh.

So we decide to mimic the best of both world. Spreadsheet during evaluation and then upload results to the QualOSS repository + Specula for visualization.

Another important reason for moving to a decentralized assessment via spreadsheets is: Enterprises are likely to prefer dealing with spreadsheets (and recommendation on tools) rather than configuring a platform and many tools.