Some metrics of Open Source development in “the Cloud”

Are you still waiting for “The Year of the Desktop”? Not sure when it will happen, but it is clear that the Open Source movement around “Cloud Computing” is growing and growing.

The number of companies releasing Open Source code, contributing to Open Source cloud projects increases each month. A good example to see it is the “under developmentCNCF Grimoire Dashboard:

Table and chart showing CNCF organizations diversity numbers and evolution
CNCF organizations diversity numbers and evolution

And during these days, in events like CloudNativeCon and KubeCon we’ll see more data and insights about how big the open cloud ecosystem is becoming. Do you want a preview?

Continue reading “Some metrics of Open Source development in “the Cloud””

Advertisements

On the Importance of Quarterly Reports : OPNFV and OpenStack as use cases

Public quarterly reports are used for understanding the performance of companies. And so, quarterly reports done by Bitergia fill the gap of understanding the performance of open source communities. This type of analysis focuses on those that are still interested in metrics, but do not have the time to play with the dashboards. This indeed provides a full overview of the current quarter, but adds a comparison with the previous quarters. This allows to have some extra context about where the community is heading.

Continue reading “On the Importance of Quarterly Reports : OPNFV and OpenStack as use cases”

Dashboards for the Eclipse community

We’ve been maintaining a software development dashboard for the Eclipse community for a while. Now that EclipseCon is running, it is a good moment to visit it, to explain some of its peculiarities, and to comment on future directions.

Eclipse software development dashboard
Eclipse software development dashboard

The dashboard shows activity in the four main type of repositories with information about software development (git, Gerrit, Bugzilla and mailing lists) for all the projects in Eclipse. You can browse the specifics of all of them (click on the button right of “Eclipse Foundation” on the top bar), and select between a view of the whole history of the community, or restrict it to the last five years (unfold the option by clicking on “All history”, again in the top bar).

But before commenting some more details, let’s visit the future: a simple PoC of the upcoming GrimoireLab-based dashboards, showing Eclipse data as of two days ago for dashboard for git data and dashboard for Gerrit data.

GrimoireLab-based dashboard for Eclipse git data
GrimoireLab-based dashboard for Eclipse git data

The information in these new dashboards will be much more actionable, with the visitor being able of filtering by just clicking on charts and tables. These dashboards are still early demos, which although show real data, still need a lot of polishing of the user interface. For a more complete (but still proof-of-concept) demo, have a look at the one we presented during FOSDEM.

Continue reading “Dashboards for the Eclipse community”

Kilo: the new OpenStack release

[Updated results based on methodological changes]

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.

After the continuous increase of activity from release to release that we observed in the past, Kilo, the latest release of OpenStack is showing some stabilization. The differences  between Juno (the previous release) and Kilo are the lowest in the history of the analysis we’ve performed for the OpenStack Foundation. Although this release has reached a new peak in contributors, close to 1,500 different persons, the increase from Juno to Kilo was of around 900 commits and 200 authors while from Icehouse to Juno it was of  700 commits and 70 developers.

The list of organizations participating in the development of OpenStack keeps growing as well: close to 170 different organizations have contributed with at least one commit to the development of Kilo.

As the top ten contributors, we find the following organizations:

companies-contributions-updated

Regarding to the community itself, the timezones analysis shows a widespread activity around the world. OpenStack is a truly 24 hours-a-day continuous development community. There are three main groups of activity: America, on the left side of the chart, Europa/Africa in the center and Asia, on the right.

Total commits by timezone as detected in Git repositories
Total commits by timezone as detected in Git repositories

Ignoring the UTC 0 activity, that may be biased by developers using UTC 0 as their timezone with independence of their point of residence, the rest of the activity shows North America East and West coasts as the main contributors in number of commits. Europe/Africa is quite close to this activity (most of it due to Europe), although biased by the UTC peak of activity. India could be represented by the the small peak in UTC+5, and finally the rest of Asia, with China and Japan in first place, which is consistent with the localization of some contributing companies.

Methodological notes:

  • Some of the repositories under the OpenStack project have been removed of the analysis. As an example, specification projects are not counted for this analysis. The full list of repositories is available at the last quarterly report sponsorized by the OpenStack Foundation.
  • Developers are counted as the actual authors of the piece of code merged into upstream.
  • The time of commit takes into account the time when that piece of code is merged into upstream.
  • Each release, new repositories are added to the list of analyzed projects. This partially explains the continuous increasing activity in the OpenStack Foundation projects.

Behind the big numbers on the Wikimedia code review process

Having a dashboard usually opens new paths to understand software development communities. This may be seen as the entry point that helps to understand the basics of a community. And on top of this, there may appear new questions related to those basics or to more advanced issues. This is the case of the new work we are working on with the Wikimedia community metrics analytics team: Core Reviewer and Participants.

  • Core reviewers are defined as those developers that can exercise a +2/-2 review in Gerrit. In addition to this, it is of interest for the community to remove auto merges. Although this is an undesired behaviour, that takes place, and those should be removed.
  • On the other hand, Participants in Gerrit are defined as any member leaving any type of trace in the system. In this set we can find reviews (-2,-1,+1,+2), uploads, comments and others.

It is interesting to notice that depending on the community, requirements are slightly different. In the case of the OpenStack community, there are extra requirements for the Core Reviewer definition. And this is that reviews should be found in master branch. This specific measure can be found in the OpenStack quarterly reports for each of the projects of the Foundation.

Continue reading “Behind the big numbers on the Wikimedia code review process”

Data, data and data about your favourite community: GrimoireLib

[This post is part of the lightning talk presented at FOSDEM 2015. The talk was titled as “Data, data and data about your favourite community” whose slides are available in the Bitergia’s Speakerdeck place. The ipython notebook used for visualization purposes is accesible through nbviewer and can be downloaded in GitHub. This is a basic introduction to GrimoireLib.]

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.

Continue reading “Data, data and data about your favourite community: GrimoireLib”

Create a free website or blog at WordPress.com.

Up ↑