Abstract: Pattern discovery, the process of discovering previously unrecognized patterns, is often performed as an ad-hoc process with little resulting certainty in the quality of the proposed patterns. Pattern validation, the process of validating the accuracy of proposed patterns, remains dominated by the simple heuristic of “the rule of three”. This article shows how to use established scientific research methods for the purpose of pattern discovery and validation. We present a specific approach, called the handbook method, that uses the qualitative survey, action research, and case study research for pattern discovery and evaluation, and we discuss the underlying principle of using scientific methods in general. We evaluate the handbook method using three exploratory studies and demonstrate its usefulness.Continue reading “Pattern Discovery and Validation Using Scientific Research Methods (TPLoP)”
It is 2021 and there is still a lot of fighting about “freedom” in open source software development. Here is an analytical breakdown of the issues.
Freedom can refer to people or artifacts (source code). When it refers to people, it is typically freedom of choice regarding what to do. There are three main roles in open source: The original programmer, an intermediary (another programmer or a software vendor), and the users or customers of the vendor. I’m simplifying, but this matches the distribution use-case in which license clauses put the most obligations on people.Continue reading “Whose Open Source Freedom is it Anyway?”
I’m happy to report that the 15th article in the Open Source Expanded column of IEEE Computer has been published.
|Title||Open Source Software Engineering the Eclipse Way|
|Authors||Wayne Beaton, The Eclipse Foundation|
|Publication||Computer vol. 54, no. 6 (June 2021), pp. 59-63|
Abstract: This article explains how open source software development works at the Eclipse Foundation. It dives into engineering best practices, providing insights from one of the most successful open source foundations of today.
Also, check out the full list of articles.
Philippe Ombredanne, lead maintainer of ScanCode, will give a talk on open source license compliance, injected into my own lecture series on commercial open source software, both organized by CROSS, the Center for Research on Open Source Software at UC Santa Cruz.Continue reading “Upcoming Talk on Establishing Open Source License Compliance Using Continuous Integration”
When thinking about creating an open source project, starting with the question which license to choose is the wrong approach. Rather, you should ask yourself: Why am I creating this open source project and what do I want to achieve with it? Once you have settled this question, you can use the following simplified cheat sheet:Continue reading “The Wrong First Question: Which Open Source License?”
The short answer: As long as you don’t have product market fit. In more detail:Continue reading “When Does Public Funding Trump Venture Capital?”
Thomas Otter and Dave Kellogg of The SaaS Product Power Breakfast had me join their show and discuss product management, commercial open source, and cloud service strategies. It is out already as a podcast (local copy). Check it out and make sure to subscribe to their show!
There were a couple of references in the show you might like to have the links to.
- The commercial open source course as taught at UC Santa Cruz, starting June 21st, 2021.
- Our Harvard business school type free teaching cases for product management.
If I missed a link, let me know, and I’ll add it.
In 2009, half of open source code was licensed under the GPLv2 license, the canonical copyleft license. Every other license had less than 10% market share. Over the years, the MIT license and other permissive licenses kept climbing at the expense of the GPLv2. As of today, the MIT license is the leading license with more than 32% market share in absolute numbers, with the GPLv2 license having fallen below 20%.Continue reading “The Future Resurgence of Copyleft”
I was interviewed by Lovis Krüger German radio broadcaster WDR on Huawei’s HarmonyOS and the industry strategies around it. Two audio statements made it into the show: (1) HarmonyOS uses a lot of open source software and (2) Huawei can’t use the Android trademark without Google’s permission. So I thought I provide my notes here.Continue reading “HarmonyOS, Android, and a Radio Interview”
In a well-working community open source project, many people contribute. In particular, software developers will submit code contributions. As a consequence, without further measures, the copyright in the project’s code will be widely shared among its contributors.
To ensure that a project can be used without fear of violating someone’s intellectual property rights, all project artifacts, in particular the code, need to have a clear open source license, and ideally only one.Continue reading “Open Source Project Licensing”