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.
The main changes in this version are:
- Legend for viz could be places now anywhere
- Metrics have now a namespace so you can have the same metric name in different data sources.
- Improved Summary for data sources
- New help system integrated with graphs
- Metrics definition could be modified from a JSON file
- Bug fixes and minor changes.
The code is available at:
Gerrit is becoming more and more popular in open source communities, being an essential part of the Wikimedia or OpenStack foundations among others.
We, at Bitergia, have started the process to include the information provided by Gerrit API in our toolset to finally obtain dashboards with specific information from the review process. So project managers can deal with big amount of data from this repository in an easier way, having aggregated numbers, but also with the possibility to deepen in the numbers and details if required.
There are five functions so far:
- EvolReviews: evolution of reviews per type (merged, new, workinprogress, abandoned,…) and per period of time (month, year, week, …)
- EvolReviewers: evolution of the reviewers per period of time
- EvolEvaluations: type of evaluation per patchset (verified, submitted, …) and period of time
- Waiting4Review: number of patches waiting for a reviewer response (those that got a positive review)
- Waiting4Submitter: number of patches waiting for a submitter response (typically those that had a negative review)
As usual, feedback is welcome!
We’re improving the dashboards created with vizGrimoire, by using Bootstrap to offer a better and more complete look and feel. The data remains the same, the charts are the same, but the overall aspect has changed. Using some data from OpenStack, we have prepared a preview of the new dashboard (still work in progress)
As an update of our analyses on previous releases of OpenStack, today we present our analysis of company contributions to Grizzly, the new release of the project being published today. OpenStack is a well known free / open source software project providing facilities for building private and public clouds. It is also a good example of a development community in which almost all participants are affiliated to some company. Therefore, it is interesting to study how companies contribute to the project by means of their employees. This is exactly what we did in our analysis.
The results are revealing, and more when you put them into context by looking at how companies were behaving in previous release cycles. The data is telling a story of how a project which was clearly dominated by a single company (RackSpace) has led to a real community with many actors. With more than 20 different companies contributing every week and a total of more than 50 companies which contributed at some point, OpenStack is becoming one of the projects with more corporate involvement. The number of people involved is also large, and growing. In September / October, when the release cycle was starting, about 40-50 persons contributed each week. At the end of the cycle, in March, they were about 80-90.
The top corporate contributors are no surprise: Red Hat, Rackspace, IBM, Nebula, HP and others are well known for their support of the project. Maybe it is interesting to see how Rackspace is slowly handing over the leadership of the project to other companies, and how quickly some of them are getting involved.
[Now, go on reading this post, or have a look at the complete analytics dashboard for Grizzly]
[Note (Apr 6th 00:10 CEST): Thanks to those of you who are reporting what seem to be errors or inaccuracies. We're having those reports into account and will produce a new run of the data soon. However, up to now they don't seem to change things significantly except for specific developers or maybe some company going one position up or down in some list. Please, keep those reports coming.]
gvSIG is a is a geographic information system (GIS) software designed for capturing, storing, handling, analyzing and deploying any kind of referenced geographic information (more info in Wikipedia). It was born in 2004 as a project run by a public administration (the Regional Government of Valencia, Spain). 9 year later, gvSIG is a complete, mature platform, with a lively international development (and user) community. Many different products have been built based in, or forked from, it.
As usual, we have run our tools on it, producing our basic dashboard. For source code, we have analyzed the two main branches (roughly corresponding to 1.x and 2.x release lines) from their Subversion repository, for tickets we retrieved all we found, for mailing lists we got everything we could get from their Mailman repository.
Software forges are these kind of collaboration platforms that have been on our radar for years. Alvaro and I have been involved with their integration, deployment and maintenance during the last 5 years and now we are also helping some relevant communities to get the best from these products.
Apart from the work done with Allura integrating our analytics, we are very close to the FusionForge community. FusionForge is a free software application descendant of the forge implemented by the Sourceforge people a decade ago. We used it for a migration we performed for CENATIC (National Benchmark Centre for Open-Source ICT Application) during the last months of 2012. The aim of the migration was to move around 150 projects that were hosted in the infrastructure of the Morfeo’s community to a fresh instance of Fusionforge running on their own data center. The services offered by Morfeo were outdated, it was running a very old version of Gforge (FusionForge’s predecessor) together with a bunch of WordPress and Mediawiki installations. The main task was to design a process to get all the information from the services provided by Morfeo: Gforge, WordPress and Mediawiki, and move them to a fresh instance of FusionForge and WordPress.