On the 8th of October we joined LinuxCon to share our Gender Diversity Analysis of technical contributions to the Linux Kernel.
We are aware of the diversity gap in the tech industry and the efforts of some institutions, like Linux Foundation, are doing to solve it. So, we decided to add our five cents, working over the weeks to bring some stats about women’s contribution to Linux Kernel.
Before diving deep into our results, let’s take a look at some data we already have from the tech sector. Women represent:
Software development is eating up the labor market
More than 20 years after the crash of the 1990’s dot-com bubble, IT has transformed business. Today, the majority of businesses are software companies. Netflix is not a film company, Amazon is not an online ebook company, Spotify is not a music company, Pixar is far from being an animation studio, and Groupon is not just a marketplace. There are more than 330K active organizations in GitHub. We are living in the Digital Transformation buzzword era.
OPNFV Organizations diversity
A lot of these companies are using Open Source technologies and they demand experts in many application fields (Cloud, Web Development, etc.). Open source’s talent has a strong pro demand. Managers are always looking for experienced developers. According to the 2016 Open Source Jobs Report:
- 87% of hiring managers say it is difficult to find open source talent and 79% have even increased incentives to retain their current open source professionals.
- 58% of hiring managers are looking for DevOps talent, making DevOps the most in-demand role in open source today.
- For jobs seekers, even though 86% of tech professionals say open source has advanced their careers, only 2% say money and perks are the best part of their job.
Having a solid strategy in attracting and retaining IT talent is crucial for the future of companies. How could Software Development Analytics help them?
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).
But recently there are so many mainstream IT firms that are allocating resources to Open Source contributions, not only for the benefits of the code, but the benefits of the methodology brought to the organization such as collaborations, innovation and quality control.
Inner Source takes the lessons learned from developing Open Source software and applies them to the processes that companies follow to develop software internally.
Innersourcing’s benefits for the company
One of the first tasks done by a developer during the day is to choose where to go and what to fix. Backlogs are quite useful for this purpose, either using Kanban and directly having a look at the open issues waiting lists project by project as in the case of GitHub, or using any other manual or automated method.
For this engineering focus we have started to produce some panels whose main purpose is to help developers to make decisions. As this is still in its first stages there is room for improvement, but this hopefully shows how powerful this could be. The displayed panel is part of the open analytics panel produced for the CoreOS community.
CoreOS Pull Requests / Issues Backlog panel
This panel aims at providing information at three main levels:
On Monday, June 20th, our colleague Jesús will be in Berlin for OPNFV Design Summit to present The Quantitative State of OPNFV.[Update]: slides available, Jun, 20th, 2016.
OPNFV is one of the open source projects hosted by Linux Foundation and we have been working for them for almost a year, deploying and maintaining a Metrics Grimoire based Bitergia Dashbobard and detailed quarterly reports. But, meanwhile, we have been developing the new GrimoireLab toolkit, so we have some new things to show in Berlin for our OPNFV friends…
OPNFV MetricsGrimoire and GrimoireLab based dashboards
We have built a GrimoireLab based dashboard for OPNFV, but with some extra goodies!
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: