Software Research and the Industry
Dirk Riehle's blog about everything computer science, applied and more
Georg Grütter of Bosch recorded my keynote at the Inner Source Commons summit in Renningen, Germany, on May 16th, 2018, and put it on Youtube. Please watch it below (original video, local copy). According to Georg, the video is licensed under CC BY-SA 3.0 (for the Bosch part) and I agree (for my part). Hence …
Continue reading “Ten years of inner source case studies (video)”
Actually, I just notice it is the fourth time within the last two months, but tomorrow is the first time I’ll present our research on inner source in a public venue. If you are interested in ten years of case studies on how to use open source best practices within companies (called inner source), come …
Continue reading “Third time’s the charm: Ten years of inner source case studies”
I got asked the other day why there are only two research groups working on inner source world-wide. Inner source is the use of open source best practices within companies, and it is a hot topic with many companies who want to go beyond agile. There was varied research around the world in the past …
Continue reading “Why are there only two research groups working on inner source?”
During my talk at the inner source summit, I was asked about the following worry with establishing inner source at a company: But if we lay all source code open within the company, don’t we run the risk that a disgruntled employee has it too easy to steal all code and publish it on the …
Continue reading “But what if someone steals my inner source code?”
Today, I gave a keynote at the 2018 spring Inner Source Commons summit at Bosch, in Renningen, Germany. I talked about our experiences with ten years of inner source projects at the companies we have been working with. The slides are available as a PDF. The photo above is from the first keynote of the …
Continue reading “Slides for Keynote at Inner Source Commons Summit at Bosch”
Abstract: Inner source (IS) is the use of open source software development (SD) practices and the establishment of an open source-like culture within an organization. IS enables and requires developers to collaborate more than traditional SD methods such as plan-driven or agile development. To better understand IS, researchers and practitioners need to measure IS collaboration. …
Continue reading “The Patch-Flow Method for Measuring Inner Source Collaboration”
Abstract: Inner Source (IS) is the use of open source software development practices and the establishment of an open source-like culture within organizations. The organization may still develop proprietary software but internally opens up its development. A steady stream of scientific literature and practitioner reports indicates the interest in this research area. However, the research …
Continue reading “Inner Source Definition, Benefits, and Challenges”
I’m giving an invited research talk (“journal-first”) at FSE 2016 in Seattle today, Nov 15, 2016. It is in Session 5, right after lunch. The underlying Transactions on Software Engineering (TSE) paper is available here. More on inner source here.
Abstract: Inner source software development is firm-internal software development that uses the principles of open source software development to collaborate across intra-organizational boundaries that would otherwise hinder any such collaboration. Inner source breaks down the barriers to collaboration across development silos by setting up an internal ecosystem of readily available software components. To get started …
Continue reading “An Example Charter for Inner Source Programs”
Abstract: Inner source is an approach to collaboration across intra-organizational boundaries for the creation of shared reusable assets. Prior project reports on inner source suggest improved code reuse and better knowledge sharing. Using a multiple-case case study research approach, we analyze the problems that three major software development organizations were facing in their product line …
Continue reading “Inner Source in Platform-based Product Engineering”