Kilo, the new OpenStack release, shows a continuous increase of activity if compared to Juno. From Icehouse to Juno, there was an increase of 6.22% in the number of commits and 17,07% in the number of unique authors. From Juno to Kilo, there’s a higher jump in terms of commits (11,23%) and a lower increase in terms of authors (11,16%). However, with this increase, there is a new peak in the number of unique authors contributing to the OpenStack Foundation projects with close to 1,600 different people participating in its development.
GrimoireLib aims at providing a transparency layer between the database and the user. This helps to avoid the direct access to the databases while providing a list of available metrics.
This is a Python-based library and expects an already generated database coming from some of the Metrics Grimoire tools. CVSAnalY, MailingListStats, Bicho and most of the tools are already supported by this library.
Within a few hours the OpenStack Juno release will be delivered. At the moment of writing this analysis the OpenStack Activity Board shows 91,317 commits spread across 108 repositories. All of this activity was performed by close to 2,600 developers, affiliated to about 230 different organizations. In addition, around 75,000 changesets have gone through code review, submitted by 3,082 developers.
Last week I took part as master of ceremonies on an special event for FLOSS developers at .. Microsoft Spain offices! The idea for the meeting was to explore the different FLOSS technologies already supported by Microsoft Azure with speakers from different companies and communities like MongoDB, PhoneGap/Cordova, etc.
The event is part of the new openness strategy that is driving the company. But, I have thought about how open is really this movement? Of course, they are releasing a lot of code as Open Source, but is the company contributing to other FLOSS projects beyond their own ones? And by suprise, the answer has come from our own dashboards.
An interesting fact: while for previous releases contributing organizations changed a lot, from Havana to Icehouse release top contributors keep stable with no big changes. Even more: no big changes in the top organizations, and no big changes in the number of commits. The only new entry in the top ten is Intel, with the rest contributing in a similar way as they were in Havana.
Turnover is inevitable. Developers leave a project and others join it. And this effect may be more harmful in open source communities than in companies. Depending on the community, it is hard to find new people willing to participate. And even more, there is a knowledge gap left by those that gave up developing. So the issue is double: people leave and those leave a knowledge gap that in some cases is hard to fill.
However, is it possible to analyze that regeneration of developers? How good is my community retaining developers? Is it possible to measure the number of newcomers joining the community? It is clear that having this type of information is basic to define policies to attract new members, retain current ones and check if the current situation is driving the community to good terms.
The demographics of open source communities allows us to understand how the community has evolved, and potentially how this community will evolve through the time. Demographics in open source communities can be seen as the typical analysis of pyramids of population in countries or cities. Typically on the top of the chart the oldest people are found, while the age decreases going to the bottom of the chart. Those are named as pyramids given their typical triangle shape. However during the last decades and in developed countries, this shape is moving to an inverted pyramid, although this is another discussion :).
Thanks to the study of the demographics of developers, it is possible to know a bit more about the community. We already introduced the demographics of the Linux Kernel, and this post is focus on the analysis of the OpenStack community as a case study. The following figure shows the demographics of the OpenStack community (daily updated in the OpenStack activity dashboard). The x-axis indicates the number of developers, while the y-axis shows the timeframe of activity.
Green bars show the number of developers that in each of the periods started contributing with at least one commit. And blue bars show the number of those developers that still contribute to the community. By definition, a developer is still contributing to the community if a commit has been detected during the last six months. If not, this developer is considered as a developer that left the community. There may raise the case when a developer after more than six months, returns and submit another change to the source code. In this specific context, this developer would appear as not leaving the community.
An example was provided and in some cases, and depending on the development policy of the project, commits ignoring merges represented around a 50% of the total activity that we can find.
CVSAnalY is one of the tools that is used as input in our dashboards. It is specialized in versioning systems, and parses the log provided by some of the most used in the open source world. It does this with the priceless help of Repository Handler, in charge of adding a transparency layer.
Its procedure is simple: CVSAnalY reads a log from SVN, CVS or Git and builds and feeds a relational database. For other distributed versioning systems, there are hooks to migrate from those, such as Mercurial or Bazaar to Git.
Havana release is scheduled on the 17th of October. In just a few hours the new version of OpenStack will be ready. As we did for other releases, we at Bitergia have prepared the Havana development dashboard for showing and exploring the main development parameters of the project during this cycle. The first headline that becomes apparent by browsing it is that during these last six months, the OpenStack community has experienced the most active period in their history, and still keeps growing and growing.
The analysis of the OpenStack community is one of the challenging activities on which Bitergia is working. OpenStack enjoys a very lively community, with interest from many companies and a lot of people from around the globe. But, let’s go to the numbers so you can have a better picture:
1,263 developers, with close to 200 of them contributing every week
3,392 participants in the ticketing system
1,472 members in the mailing lists
More than 12,000 people from 130 different countries registered in the OpenStack Foundation.
Some other amazing numbers: annual increase of almost 65% in commits, 55% in Launchpad activity, and an incredible 639% in mailing lists. It is clear that once mailing lists were ready, a huge amount of people started to use them.
Bitergia, the software development analytics company
Bitergia helps companies and organizations by understanding and improving the software development projects that matter to them. Software development is more than writing code: is about engagement and collaboration of the people involved in its design, development, deployment and maintenance. It's about the processes and activities that turn ideas, feature request, and requirements into code.
We provide tools and means to track all these aspects, and to evaluate how policies and decisions are shaping the development processes.