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
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?
I’m happy to report that the fourth article in the new Open Source Expanded column of IEEE Computer has been published.
Getting Started With Open Source Governance
Companies, Licenses, Security, Software, Law
Jeff McAffer, GitHub
Computer vol. 52, no. 6 (October 2019), pp. 92-96
Abstract: Using and managing open source is essential in modern software development. Here we lay out a framework for thinking about open source engagement and highlight the key steps in getting started.
Abstract: Open source has given us many innovations. This article provides an overview of the most important innovations and illustrates the impact that open source is having on the software industry and beyond. The main innovations of open source can be grouped into four categories: Legal innovation, process innovation, tool innovation, and business model innovation. Probably the best known innovations are open source licenses, which also define the concept.
Keywords: Open source, open collaboration, open innovation, software industry, business models
Reference: Riehle, D. (2019, April). The Innovations of Open Source. Computer vol. 52, no. 4, pp. 59-63.
Open Source Expanded is the name of a new column (open-ended article series) that I’m editing for IEEE Computer Magazine. Expect a new article on open source and how it is changing the world every two months!
The first article on the innovations of open source was just published, kicking of the column. I could not negotiate an open license, however, all articles will be free to read and download.
I’m very much interested in the governance of open source projects, in particular if these are user-led projects. With this post, I’m proposing a basic terminology to talk about the formal organizational structure underlying the governance of such open source projects.
It is no secret that software is everywhere. No traditional product has remained untouched, whether the product is being produced using software or whether software is an integral part of it. As part of this wave of digitization, established vendors from outside the software industry need to avoid that someone else will reap all the profits from their products. That someone else would be software companies that supply needed components. In particular software platforms can have such network effects that their providers can reach a monopoly position so that dependent vendors who need the platform will face a diminishing profit margin.
I just finished reading John Carreyrou’s book Bad Blood, which presents the story of the rise and fall of one-time Silicon Valley unicorn Theranos through his eyes as the journalist who broke the story. In case you missed it: Theranos was a healthcare company promising to sell a machine that could perform quickly and reliably a large number of blood tests needed by medical doctors to aid their patient care. The hitch: The technology never worked and Theranos managed to hide this from investors and the public for a long time.