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.
Inner Source (or Inner Sourcing) is a term coined by Tim O’Reilly in 2001 that referenced to the,
“use of open source techniques within the corporation”.
Although more that 25% of the deployee code in the most influential IT companies was Open Source in 2015, IT departments didn’t show much interest in collaboration or innovation process. (Gartner, 2015).
Community managers spend their time in numerous community activities related with his/her main role: to get people to talk and contribute, react to the community managed, keep people engaged, etc. Key Performance Indicators (KPIs) should be set for each community based on its goals. It’s part of the job to elaborate reports with multiple metrics on community health for example. But, measuring should be an effective task.
Keeping this in mind, I’d like to share with you 5 reasons about why community managers or any other professional related with software development should have a dashboard that provides all the data about the community or project that she/he manages:
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!”
As a part of our tests with Kibana and Elasticserch as frontends for our MetricsGrimoire databases, we’ve set up a dashboard for understanding the code review process in OpenStack (be sure of visiting it with a large screen and a reasonable CPU, otherwise your experience may be a bit frustrating).
This dashboard includes information about all review processes (changesets) in OpenStack, using information obtained from their Gerrit instance. For each review, we have information such as the submitter (owner), the time it was first uploaded and accepted or abandoned, the number of patchsets (iterations) needed until it was accepted, and the time until it was merged or abandoned. With all of them we have prepared an active visualization that allows both to understand the big picture and to drill down looking for the details. Follow on reading to learn about some of these details.
[Note: this is our second post about our dashboards based on Kibana. If you’re interested, have a look at the first one, about OpenStack code contributions.]