InnerSourcing: the development model of the future?

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_graphic

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

Continue reading

Getting your project backlog with GrimoireLab. CoreOS use case

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.

backlog_panel_coreos

CoreOS Pull Requests / Issues Backlog panel

This panel aims at providing information at three main levels:

Continue reading