Page 1

Automated Measurement and Analysis of Open Source Software

Project Overview 24 November 2012

OSSMETER Project Overview

1


Open Source Software (OSS)

Quality/Maturity

Quick replies to questions Frequent source code updates Bugs fixed quickly Frequent releases Large number of downloads Many external references

? Late/no replies to questions Infrequent source code updates Bugs not fixed Infrequent releases Small number of downloads Few external references

24 November 2012

OSSMETER Project Overview

2


Adopters  Need support with  Selecting OSS software  Monitoring OSS software they have previously selected

24 November 2012

OSSMETER Project Overview

3


Selecting OSS  Is a challenging task  Time, cost of error, stress

 Approaches     

Use over-simplified selection criteria Try to avoid making a decision altogether Choose arbitrary default options Overestimate their expertise Become highly risk averse

24 November 2012

OSSMETER Project Overview

4


Selecting OSS  Many OSS projects with similar/overlapping functionality  Adopters are looking for OSS that is …  of high quality (fast, secure, extensible etc.)  supported by a substantial team of developers • questions answered • bugs fixed • new requirements implemented  backed by a company  used by other people  going to be around for a while

24 November 2012

OSSMETER Project Overview

5


Monitoring OSS  The health of OSS needs to be monitored after initial selection has taken place  The company behind an OSS project may fold/switch focus  OSS developers may change jobs (or simply lose interest)  A newer/better OSS may make the project obsolete

 Adopters need to be warned early enough to set up a transition plan 24 November 2012

OSSMETER Project Overview

6


OSSMETER Vision

24 November 2012

Quick replies to questions Frequent source code updates Bugs fixed quickly Frequent releases Large number of downloads Many external references

Quality/Maturity

 Develop a platform that will support decision makers in the process of discovering, comparing, assessing and monitoring the health, quality, impact and activity of open-source software

OSSMETER Project Overview

? Late/no replies to questions Infrequent source code updates Bugs not fixed Infrequent releases Small number of downloads Few external references

7


Sources of Information  OSS forge metadata  Source code repositories  Issue/bug tracking systems

 User communication channels  Newsgroups, forums

24 November 2012

OSSMETER Project Overview

8


Expected Results ď Ž Metamodels for capturing metainformation relevant to OSS projects (e.g. types and details of source code repositories, communication channels and bug tracking systems, types of licences, number of downloads etc.)

24 November 2012

Communication channel (Newsgroup/forum/ mailing list)

Source Code Repository

OSS Project

Bug Tracking System OSS Forge Metadata

OSSMETER Project Overview

9


Complex OSS project landscape

Google Code

GitHub

SourceForge

24 November 2012

OSSMETER Project Overview

10


Expected Results ď Ž OSS analysis based on advances in language-agnostic and languagespecific methods for code analysis, state-of-the-art Natural Language Processing (NLP) and text mining techniques 24 November 2012

Communication channel (Newsgroup/forum/ mailing list)

Source Code Repository

OSS Project

Bug Tracking System OSS Forge Metadata

OSSMETER Project Overview

11


Source Code Analysis  Current state of practice: LanguageAgnostic Analysis  #LoC vs. comments  File extensions

 OSSMETER contribution: LanguageAware Analysis  Integrate current state-of-the-art in source code analysis  Tailored metrics for source code written in OO languages, procedural languages, markup-languages etc. 24 November 2012

OSSMETER Project Overview

12


Bug Tracking and Communication Channel Analysis

 Current state of practice  # of bugs  # of messages

 OSSMETER contributions

 Thread analysis • How many people ask/answer questions? • How do users feel about the support they receive? • How does this evolve over time?

 Bug lifecycle analysis • Are bugs fixed? How long does it take on  …

24 November 2012

average?

OSSMETER Project Overview

13


Expected Results ď Ž Extensible cloudbased platform enabling users to discover and compare OSS projects, which can also support quality analysis and monitoring of inhouse software development projects 24 November 2012

Communication channel (Newsgroup/forum/ mailing list)

Source Code Repository

OSS Project

Bug Tracking System OSS Forge Metadata

OSSMETER Project Overview

14


OSSMETER Platform  Platform  Storage, analysis

 API  Interoperability

 Web application  Presentation

 Available both as a service and as open source software for local deployment  Can also be used to measure proprietary/internal software development projects 24 November 2012

OSSMETER Project Overview

15


24 November 2012

OSSMETER Project Overview

16


Reuse, Reuse, Reuse  We should aim to reuse as much as possible  Ohloh  Sonar  Connectors for SVN, Git, Bugzilla, Mantis, Trac, NNTP  Components from previous EU projects • Alitheia-Core • Flossmetrics

24 November 2012

OSSMETER Project Overview

17


Beneficiaries 

Developers and Project Managers who are responsible for deciding on the adoption of OSS, will be able to make decisions on hard facts and uniform quality indicators

Developers of OSS will be able to monitor the quality of the OSS projects they contribute to and promote the projects using independently calculated and trustworthy quality indicators, and identify related projects for establishing synergies

Funding Bodies supporting projects which produce OSS will be able to monitor the quality and assess the impact of the produced software even after the end of the projects

24 November 2012

OSSMETER Project Overview

18


Case Studies  Assessing internal software development projects  Multi-sector IT projects (Softeam)  Construction industry (Uninova & Unparallel Innovation)

 Assessing Eclipse.org projects (Tecnalia)  External industrial evaluations (The Open Group)

24 November 2012

OSSMETER Project Overview

21


Related Projects  MARKOS: Extraction and analysis of information related to OSS functionality, structure and licensing  PROSE: Co-ordination platform for software projects  RISCOSS: OSS adoption risk management  ALERT: Automated support for bug resolution

 BIGFOOT: Big data management  LEADS: Storage and analysis of publicly available data

24 November 2012

OSSMETER Project Overview

22


Inter-Project Collaboration  https://groups.google.com/forum/#!for um/eu-oss-projects  Participants from  MARKOS, PROSE, SUCRE, innoPOLE

24 November 2012

OSSMETER Project Overview

23


Contact Details  www.ossmeter.eu  Project Coordinator  The Open Group  Contact: Scott Hansen s.hansen@opengroup.org

 Technical Coordinator  University of York  Contact: Dimitris Kolovos dkolovos@cs.york.ac.uk

24 November 2012

OSSMETER Project Overview

24

OSSMETER Project Presentation  

Overview of the European Commission funded OSSMETER project addressing new technologies for measuring open source software quality.