We’ve just uploaded to pypi a new collection of GrimoireLab Python packages suitable for direct installation with pip. Please, upgrade your virtual environments!!!
These packages allow for a very easy use of most GrimoireLab tools. For example, assuming you have ElasticSearch and Kibana installed locally (or available as cloud services), producing a fairly complete software development dashboard from scratch for a git project is just a matter of running a few commands.
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.
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:
We are so excited about starting the new year with our contribution and participation at FOSDEM 2017.
FOSDEM is the strongest reference event for developers and geeks to meet and know the hottest incoming tech topics since 17 years ago.
In 2000, Raphael Bauduin, a Linux fan from Belgium, decided to organize a small event for Open Source developers. He named it ‘Open Source Developers European Meeting’ (OSDEM). From the second edition OSDEM became FOSDEM and every year host more than 5000 developers and Open Source geeks.
FOSDEM is our natural environment. We have joined it in a lots of editions and we are very proud to come again this year as speakers. We are also going to set up a stand for chatting with all our friends with special gifts for our community.