Efficiency analysis in the OpenStack community Liberty release

Liberty is the new release of OpenStack. This shows an increase in activity and people participating in the development of OpenStack.

  • There are 25,268 commits in total merged into master thanks to the work of 1,873 different developers.
  • In order to have that code into master, it was necessary the effort of 2,239 people that submitted at least one patchset to Gerrit. That means that 83% of them are actual contributors of Liberty release.
  • In terms of community, Launchpad activity shows that 9,919 people helped participating in the bug tracking process, opening, commenting and closing tickets.
  • The mailing lists are a busy channel of communication with 1,742 participants, but IRC seems to be the preferred channel with more than 6,000 detected nicknames.
  • Ask.openstack.org is also an interesting communication channel where there have been 1,386 people participating and around 2,200 different questions.

As a disclaimer, this post will not focus on organizations participating in the OpenStack development, but in the software development process. Organizations information can be easily retrieved in the Activity Board. We believe that process in the OpenStack community is important and even more when we are talking about a team of more than 2,000 different contributors.

Efficiency of the community closing changesets

As mentioned, there have been more than 2,200 people in Liberty release that aimed at contributing with a patchset in the OpenStack community. And only a subset of those pieces of code were eligible to be part of the project and merged into master. However, not all of the people that were part of the that set were even reviewed. Each quarter, the community leaves around a 20% of the changesets population open. This can be observed in the following chart. The y-axis represents the percentage of changesets that were closed (abandoned or merged) per quarter (x-axis).

OpenStack_efficiencyclosingchangesets Continue reading