Data Gathering Protocol for Open Source Projects

From Maisqual Private Wiki

Jump to: navigation, search

This document was a draft and has been superseded by Data Retrieval Process.

This article describes the protocol used for the day-to-day analysis of open source projects. This is quite different than with so-called legacy projects, which have a dedicated protocol: Data Gathering Protocol for Legacy Open Source Projects.

We intend to gather the following data for open-source projects.

This relies on data defined in other parts of this wiki:

Check also the Jenkins page for more information on the tools and scripts used to achieve our retrieval.


[edit] Trunk analysis

[edit] Process execution

This process is to be executed weekly through the Jenkins continuous integration engine.

We intend to monitor:

  • HEAD of trunk.
  • HEAD of active branches (i.e. branches that had some activity in the last 6 months).

[edit] Metrics

For each project analysis, we run SQuORE with models ISO9126_Maintainability_OO or ISO9126_Maintainability_C, depending on the language.

[edit] Change Management

We get the following data from the Change Management project tools:

  • A report that gives the number of bugs in the different project versions and their statuses.

What we want to compute from these is:

  • Number of open/analysis/working/closed bugs each days.

[edit] Results

After the process execution, results are:

  • Bugs: a csv file with the distribution of bugs for the day located at /media/stock/maisqual/projects/<project>/bugs/.
  • SQuORE Metrics: 2 csv files, one for the application-level metrics and the second for file-level metrics. Both files are located at /media/stock/maisqual/projects/<project>/metrics/.
Personal tools