In this talk, I explain the single-vendor open source business model (also: multi-licensing, open core) and in particular its intellectual property strategies. This is the slide deck of a previously posted video.
In this talk, I explain the significance of the software industry for a country’s economy and how to strengthen it using open source. It is directed at public policy makers and the general public. This is the slide deck of a previously posted video.
My research and teaching group just celebrated its tenth anniversary, and I wanted to take some time to reflect on our teaching: What worked and what didn’t.
When I started as a university professor ten years ago, I drew on my experience as a student, as a teacher, as a practitioner, and as an entrepreneur, to define the basic principles of how I wanted to teach:
Theory and practice should be joined at the hip; there should only be minimal delay, if any, between hearing some concept and applying it in practice
Learning requires repetition and practice, so the theory and practice of something to learn needs to be drawn out over several iterations to become effective
Learning is a marathon, not a sprint; therefore, learning and using the stick (grading) to direct learning should be continuous and not a fire-and-forget exercise
Feedback needs to be immediate and connected to a student’s actual doing, and not come at the end of a semester or later
Learning is holistic; while some concepts can be isolated, more often than not, concepts interact and require a realistic setting to be learned
In this short video, I explain the significance of the software industry for a country’s economy and how to strengthen it using open source. It is directed at public policy makers and the general public.
In this video, I explain the single-vendor open source business model (also: multi-licensing, open core) and in particular its intellectual property strategies. This talk is partly a reaction to the recent licensing changes by commercial open source firms and the resulting confusion. An upcoming article will go into more detail next year.
IAV GmbH (Berlin) will be hosting this winter semester’s AMOS demo day. Four student teams will present the results of their work, ranging from a logistics dashboard, through an ECU dashboard, a Git module configuration tool, to a next generation HMI app for Android Automotive OS.
10:15am (start) to 11:45 (end)
IAV DigiLab, Hallerstr. 6, (1tes OG), 10587 Berlin
If you would like to attend, please drop me a note.
Abstract: Corporate use of open source in software products is on the rise. While this brings a number of technological and business benefits to companies, it also comes with potential legal and financial risks caused by license non-compliance and ungoverned use of open source components. Companies address these threats with free/libre and open source software (FLOSS) governance – internal guidelines and processes for using open source components in products. An essential aspect of FLOSS governance is component reuse and component repository, which enable efficient governance for the previously used components by the company’s developers. In our study, we aimed to identify the current industry best practices for FLOSS governance and component reuse. We conducted 15 expert interviews in companies with high governance maturity, analyzed these interviews and derived 19 best practices cast in the pattern format of context-problem-solution. The format was inspired by design patterns and enables higher applicability of our research results by practitioners. The 19 best practices form a handbook on FLOSS governance and component reuse that also includes workflows connecting the individual practices into process templates.
Keywords: Open Source Software, FLOSS, FOSS, Open Source Governance, Best Practice, Commercial Use of Open Source, Component Repository, Component Reuse, Industry Best Practice, Introduction of FLOSS in Companies, Pattern, Pattern Language
Reference: Harutyunyan, N., & Riehle D. (2019). Industry Best Practices for FLOSS Governance and Component Reuse. In Proceedings of the 24th European Conference on Pattern Languages of Programs (EuroPLoP 2019). ACM, article no. 21.