We have been working for GitLab for some time, analyzing activity, community and performance in several of their projects like GitLab CE and GitLab EE. And of the questions they have asked has been: how many merge requests do we have open each week?. This workload insight helps to manage the effort spent in code review.
One of the last features we’ve been working on for Bitergia Analytics and GrimoireLab is called Panels Collection: A set of dashboards, aggregated in a unified structure with clear documentation for easy insights analysis and reporting.
One of the main problems community managers face when they want to measure project’s health, is related with the life-cycle of it. If community managers are able to identify whether the project is either in growth, maturity or decline, that can be used when making further decisions regarding the project and its developer community
Software development analytics plays an important role in decision making for many data-driven firms. Being able to provide support for a wide range of different data sources to measure any project (so you can aggregate more than just one type of data) and manage different identities and affiliations among several data sources, is something we believe that can lead to a better understanding of the project as a whole.
SortingHat is an open source tool that simplifies the management of project member identities and their related information such as gender, country and organization enrollments. It is one of the key components of GrimoireLab, daily used in Bitergia to track and visualize project members information.
Bitergia keeps growing as a software development analytics firm and nowadays, we are helping a wide variety of clients (project & community managers, engineering & development teams, HR managers, business analysts, etc.). Obviously, they’re not looking for the same goals in their projects, neither for the same metrics. So, how can Bitergia Analytics dashboards be customized for their specific needs?
Nowadays, more and more companies such as PayPal, Bosch or Autodesk are internally implementing inner source programs. Inner source differs from classic open source development process by remaining within the view and control of a single organization and offers many advantages in terms of efficiency and effectiveness.
In previous posts, we talked about Inner source characteristics and advantages such as InnerSourcing: the development model of the future.
North Bridge and Black Duck published last January their 2016 Future of Open Source Survey Results with a lot of interesting conclusions. Maybe the biggest one it’s that Open Source continue gaining force inside the IT business, but its management is chaotic because the lack of process.
Most common problems related on the survey were:
- Nearly 50% of companies have not formal policy and process for selecting and approving open source code.
- One of the major problems of that is security. 47% don’t have a formal process in place to track the code and only 19% of vulnerabilities are detected and fixed automatically.
- Nearly 1/3 has no process for identifying tracking or solving known open source vulnerabilities.
- Over 1/2 companies has no responsible to identify and tracking remediation.
To celebrate 25 years of Linux kernel development, we at Bitergia have produced the Linux development history dashboard. This dashboard visualizes the current Linux git repository from two points of view: the history of all commits (changes to the source code) up to now, and the history of all lines in the current version. The dashboard visualizes the main parameters about the development (the who, when and what) are visualized, and allows for drilling down in the data, for example finding the specific commits that lead to a specific part of the code.
Do you want to learn about when the lines in the current kernel were authored? Who has participated in specific areas of the kernel? How many files have remain untouched for more than 10 years? Play with the dashboard and find your own interesting details!
The dashboard was produced using only free, open source software tools (among them, GrimoireLab, our tookit for software development analytics). If you want to learn more details, check the slides I intended to use for my presentation at LinuxCon, which unfortunately I couldn’t attend. Those provide some more insight about how it was produced, some examples about how it can be used, and some curiosities found by exploring it.