We are all used to open source projects. Concepts such as community, code review process, continuous integration, geographically distributed contributions, community managers, and a whole myriad of terms and collaborative way of working are usual for all of us. And enterprises are learning from this open process. Those are changing the direction of their development models to a more open one within the organization. Initiatives such as the Inner Source Commons where companies such as PayPal or Bloomberg are publicly exposing their case, help others to deal with the usual problems they face.
In a recent post we’ve seen how to set up Inner Source in your company is a cultural change question. Companies need to increase inner transparency, confidence and collaboration for breaking the functional silos in order to create a proper environment to develop software between motivated peers and enable code/knowledge reuse.
Open Source development communities use several tools for enabling collaboration and transparency. Companies can take advantage of them for their inner software development projects. Let’s see some examples from our experience tracking collaborative software development and helping companies in their Inner Source projects analysis:
In past posts, we talked about Inner Source and the benefits for your organization. Some large organizations, such Paypal or Zalando started their own process to approach Inner Source; we can say without a doubt that each of them has taken their own path, because Inner Source is more related to a philosophy or enterprise culture than to a process or static methodology defining it.
During last LibreCon we have been sharing some insights about it during our
Inner Sourcing and Software Development Analytics talk, and next months we are going to collaborate with some companies in their inner source approach. So it seems the right momentum to start a set of posts about “Inner Source”, doesn’t it?
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.
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?
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…
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:
The EclipseCon starts today in France. And for this special occasion we are landing a new version of the open analytics platform for Eclipse today. This is intended to be used for community purposes, but also for engineering teams and for those curious about how this community performs over time and nowadays. Luis Cañas will talk about this during the Conference, do not miss his talk!
The entry point for the dashboard is the Overview page. There a summary of each of the available data sources is displayed together with some filters that help to understand the evolution and current state of the activity and the community of Eclipse.