While we’re developing and testing our new toolchain for producing Kibana-based software development dashboards, we’re producing a good collection of them, with real data from real projects.
Continue reading “Check our Kibana-based development dashboards!”
Mid Liberty Release Cycle: OpenStack Quarterly Report
Finally we released a new version of the OpenStack Quarterly report. This is intended to provide insights about the software development process of the OpenStack projects. This covers information from several data sources such as Git, Launchpad, Gerrit, Mailing lists, ask.openstack.org and IRC channels. And it aims at providing quantitative and qualitative information about the activity, community and software process.
Continue reading “Mid Liberty Release Cycle: OpenStack Quarterly Report”
The OpenStack Juno release: activity and organizations
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.
Continue reading “The OpenStack Juno release: activity and organizations”
Free / Libre Open Source Software Community Metrics meeting recap
After the Community Leadership Summit, our next big event in Portland has been the FLOSS Community Metrics meeting, organized by us together with Puppet Labs, that hosted the meeting in their offices. Special thanks to Dawn Foster and Kara Sowles for all their help and support.
The room was crowded, with people from organizations like Eclipse Foundation, Red Hat, Google, Twitter, PayPal, Open Source Initiative, LibreOffice, Kaltura, Cloudera, etc. There has been a lot of interesting topics and talks, and almost everything is already available in the 2014’s edition website
Let’s try to brief how it was…
Continue reading “Free / Libre Open Source Software Community Metrics meeting recap”
Companies contributing to Icehouse: preliminary results
Less than two weeks for a new release of the OpenStack software. As usual, we at Bitergia keep contributing to this project through the Comunity Activity Board project as part of the openstack-infra project. A beta version of our companies analysis of the Icehouse release is already available at the OpenStack releases dashboard, where previous releases are accessible as well: Havana, Grizzly, Folsom and Essex.
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.
Continue reading “Companies contributing to Icehouse: preliminary results”
Measuring demographics: OpenStack as case study
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.
This post is an example of the type of things that in Bitergia we are building on top of the CVSAnalY tool. In previous posts we introduced the concept of commit, its peculiarities as a metric, and several ways to calculate this, adding filters such as bots, merges or branches.
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.
Continue reading “Measuring demographics: OpenStack as case study”
How to measure commits: merges, branches, repositories and bots
In a previous post (Commits: that metric), we were talking about all of the flavors we should take into account when measuring commits.
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.
In order to illustrate this post, the publicly available database for the OpenStack project is used. This database is the basement of the dashboard that can be visualized at the Openstack Activity Dashboard page. Bitergia provides and daily updates this database. So, this analysis is done with dataset up to today.
Continue reading “How to measure commits: merges, branches, repositories and bots”
Reviewers and companies in the WebKit project
As promised, here you have the second part of our series on WebKit, which we started with the analysis of companies focused on who is authoring reviewed commits.
Continue reading “Reviewers and companies in the WebKit project”
Do you want to measure your project?
On February 3rd, I was delivering a lightning talk at FOSDEM, presenting MetricsGrimoire and vizGrimoire as free software tools to get some analytics from the software repositories of your preferred project. The talk was titled “Do you want to measure your project?”, as it was focused on explaining the capabilities of these tools for analyzing a project, and on how they can be easily used for that.
![Do you want to measure your project? [slides]](https://i0.wp.com/blog.bitergia.com/wp-content/uploads/2013/02/screenshot-from-2013-02-11-192421.png?resize=300%2C210)
Report on the activity of companies in the WebKit project
[Update (2013.03.01): New post in the series: Reviewers and companies in the WebKit project]
Today Bitergia presents the first of a series on analytics for the WebKit project. After the preview we published some weeks ago, we finally have more detailed and accurate numbers about the evolution of the project. In this case, we’re presenting a report on the activity of the companies contributing to WebKit based on the analysis of reviewed commits.
Some interesting results are the share of contributions by the two main companies behind the project (Apple and Google), and how it has evolved from a project clearly driven by Apple, before 2009, to the current situation, with Google leading the top contributors table, and both Apple and Google being almost equal in contribution share over the whole history of the project. During the last years, it is also noteworthy how the diversity of the project is increasing, with new players starting to show a significant activity.
Continue reading “Report on the activity of companies in the WebKit project”