New VizGrimoireJS library 2.1 with speed boost

We’ve just released a new version (2.1) of the library we use for creating our dashboards. You can see it working it in our new demo site.

There are a lot of improvements and fixes since 2.0. The main ones are:

  • Improved loading logic for boosting speed.
  • Improved support for repository, country and company panels.
  • Style improvements (CSS)
  • Added bars viz to MetricsEvol
  • Use Report config.json file created from Automator
  • New Report.log system
  • Improved people support using all their identities. Improved people panel.
  • New widgets PersonData and MarkovTable.

Download the library to build your dashboards.


Analyzing the software that runs Wikipedia

Starting this July, Bitergia is working with the Wikimedia Foundation (WMF) to analyze their free software projects and related communities. This includes MediaWiki, the software that makes Wikipedia possible. A first (still pre-beta) version of a development dashboard for these projects is already available at Wikimedia Labs. During the next weeks, it will be improved to show detailed information about the most relevant metrics for Wikimedia communities and development processes, and their evolution over time.

Wikimedia development dashboard
Wikimedia development dashboard

The WMF is a nonprofit charitable organization dedicated to encouraging the growth, development and distribution of free, multilingual, educational content, and to providing the full content of these wiki-based projects to the public free of charge. The WMF operates some of the largest collaborative projects worldwide, including Wikipedia.

Continue reading “Analyzing the software that runs Wikipedia”

VizGrimoireJS presentation in Libre Graphics Meeting 2013

On 11st April Bitergia participated in LGM 2013 presenting the status of VizGrimoireJS, our platform for visualizing metrics.


The hot issue was to use HTML5 Canvas or SVG to create the visualizations. And the key to answer this questions is, are the visualizations going to be edited by other tools? Then, use SVG. If not, the two technologies have pros and cons. Right now, VizGrimoireJS is using the cool Flotr2 library and D3 for some specific graphs, like Treemap. Check it in our live preview.

Tomorrow at the LSWC’12

LSWC’12 is the most important business and professional event on Free Software ever held in Spain. And Bitergia will present there our strategy about software metrics and some examples of our basic reports for projects like Zentyal and LibrePlan, that they will also be presented there just after our speech. In the presentation we will also cover the tools and methodologies we used to build the reports, our transparency aim and we hope to join other companies and people around FOSS world as usual to share visions and experiences.

Join us tomorrow at 16:00 in the Business track.

For those interested, the slides of the presentation are available.

Bitergia LSWC12 Slides
Bitergia Development metrics Slides

The Rhythm of GNOME: GNOME Shell

GNOME was one of the first projects adopting time-based release management in 2002. So, in the last ten years GNOME has published a new release each March and September with only one exception: GNOME 3.0 and the introduction of GNOME Shell. Given this history, how has the time-based release plan affected GNOME projects? In our report on GNOME Shell we have analyzed and visualized GNOME Shell activity, and the results clearly show how GNOME projects are orchestrated. Image GNOME Shell Report

[The image above is just a static preview, click on it to see the live interactive chart, and to learn about the meaning of each element in the figure]

The information displayed shows the activity (commits and tickets) of the project since 2009. A clear, large peak can be seen when GNOME 3 was released, but for each major release (labeled in the chart) clear increments of activity can also be shown. In fact, the graph shows how GNOME is working with a rhythm: every six months there is a rush to report, fix and commit, with periods of less activity in between. As expected, commit and ticketing cycles are not perfectly synchronized: commits happen mostly just before release-time (to have new functionality and fixes ready for the release); the increase in closing tickets happens before or around it (to have a release as bug-free as possible, and to fix the most urgent issues raised by the distribution of the release); and the increase in opening tickets comes mostly after it (as new bugs introduced by the release are reported).

Continue reading “The Rhythm of GNOME: GNOME Shell”

Up ↑