As some of you know, Bitergia became an active member of InnerSource Commons with the aim to help companies to implement open source practices within organizations and how to use the right InnerSource metrics for their projects.
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.
Once again, Bitergia will be at OSCON, held this time in Portland, at Oregon convention center. OSCON, one of the biggest open source conventions in USA, has been ground zero of the open source movement and nowadays continues to be the catalyst for innovation among companies.
Open source projects issues deal with community health and activity: how to get people to contribute or how to keep people engaged are common activities for community managers. Thus, key Performance Indicators (KPIs) should be set for each community based on those goals.
The InnerSource Spain community had its first meeting, and we are already planning next steps. Let’s start by briefing first meeting outcomes.
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.
Not everything in inner source is about community building [but a big portion!] and the infrastructure is basic to foster collaboration, transparency and community building.
We are pleased to announce that we are writing a book about inner source.
We have been collaborating for some months with companies that are developing this methodology to produce the software they need. They were pioneers who early on realized that inner source has lots of benefits for talent management, software development, and business improvement. And now others are asking us for advice about implementing inner source.
Continue reading “How, What and When Measure Inner Source”