During the last weeks we have been presenting some of our results in the Liferay Developer conferences in Berlin and Madrid. A daily challenge in our business is to improve the knowledge of the community developers about its project and according to the good feedback we got from the developers this has been achieved.
The Liferay community is driven by a single company and based on the data we got they are doing it well. During the last months the company is hiring one engineer per week, which explains in part the huge growth of code authors during the last four years. Basically the number of developers since 2009 was multiplied by four. During the first half of 2009 the number of people contributing to the source code was 58, four years later during the first half of the current year the number of persons who have contributed to the source code has been 201.
Monthly code authors vs. code committers
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: https://github.com/VizGrimoire/VizGrimoireJS/tree/0.5.1
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.
One of the main activities of Bitergia, our brand new company, is to provide software
development metrics from Free/Libre Open Source Software communities, thus
for us it is critical to have the best metrics tools available. During last years
we have been working in the development of some of them like CVSAnaly, Bicho and Mailing List
stats and now we think that these tools should be part of a bigger
and more neutral project where the LibreSoft research group and third parties
like our company can collaborate in order to create a bigger community. This is the
main target of the project Metrics Grimoire, which is based in some of the
tools that were formerly known as LibreSoft tools.
The project is hosted in Github and so far the tools that have been added are:
- CVSAnalY, a tool that extracts information out of source code repository logs and stores it into a database.
- RepositoryHandler, a python library for handling code repositories through a common interface.
- MailingListStats, a command line based tool used to analyze mboxes.
- Bicho, a command line based tool used to parse bug/issue tracking systems.
- CMetrics, which measures size and complexity for C files.
If you are interested in the tools or if you want to collaborate with us you can reach
the Metrics Grimoire community in this mailing list:
the Bitergia team.
Last week we attended Linux Tag in Berlin to give two talks. First one was about identifying reused code between two FLOSS projects and it was given by me. The second one explained the importance of studying FLOSS software communities and was given by Daniel Izquierdo.
The main aim of my presentation was to show that it is possible (and easy!) to get very interesting results about the shared code between two FLOSS projects using FLOSS tools; the ones we used in this case were: CCFinder, Cloc, Ninka and Grep. The study identified not only the common code but also the possible license issues that were found. These kind of studies can be interesting from different points of view, I’ve summed them up in the following questions:
- how different are two software projects?
- is it feasible to propose a merge of the code?
- how is the derivate project using the original code?
- are the licenses being respected? what about the copyright?
- is the new project using new licenses that could be interested for the team that created the original work? are they improving the code?
- what changes performed the second team on the original code?
- is your source code being adopted by a certain community?
The presentation that was presented is available here.