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.
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 diesem kurzen Video erkläre ich die Bedeutung der Softwareindustrie für die Wirtschaft eines Landes und wie Open-Source-Software diese stärken kann. Es richtet sich an Public-Policy-Maker und alle interessierten Personen.
Die englische Version dieses Videos folgt; die Folien wurden vom FAU Sprachdienst aus dem Englischen ins Deutsche übersetzt (und von mir nachkorrigiert).
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.
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.
I’m happy to report that the fifth article in the new Open Source Expanded column of IEEE Computer has been published.
How to select open source components
Open Source Software, Licenses, Documentation, Computer Bugs, Software Project Management
Diomidis Spinellis, Athens University of Economy and Business
Computer vol. 52, no. 12 (December 2019), pp. 103-106
Abstract: With millions of open source projects available on forges such as GitHub, it may be difficult to select those that best match your requirements. Examining each project’s product and development process can help you confidently select the open source projects required for your work.
It is common to see members of the open source community at large bash companies that use an open core model to make money. I have always found that curious, because the open source community is not against making money, but many are against making money using this particular approach. Just why?