Category: 2.5 Inner Source
-
Invited research talk on inner source at FSE 2016
I’ll be 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.
-
An example charter for inner source programs [Technical Report]
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…
-
Inner source in platform-based product engineering [TSE Journal]
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…
-
Inner source in platform-based product engineering [Technical Report]
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 platform-based product…
-
Public upcoming talks on open source and inner source
A bit belated, I’m happy to announce two upcoming talks: Both talks are accessible to the public, see the flyers.
-
Hackathons and 20% time
According to this article, Google’s 20% time never really existed. I’ve always guessed as much, joking with Google friends that their 20% time really could only be taken on Saturday and Sunday. Which is all the same: Engaged employees do what they feel needs to be done no matter what and when. Hackathons, however, exist.…