Bruce Perens, one of the founders of the Open Source movement, is ready for what comes next: the Post-Open Source movement.
First of all, our licenses aren’t working anymore," he said. "We’ve had enough time that businesses have found all of the loopholes and thus we need to do something new. The GPL is not acting the way the GPL should have done when one-third of all paid-for Linux systems are sold with a GPL circumvention. That’s RHEL.
Starting a project as just source-available or with noncommercial clause is just fine. But the definition of free software and open source are pretty unambiguous - software with noncommercial clause can’t be either. The problem really happens when certain companies/projects want the advantages of the FOSS label, but don’t want to make the compromises associated. Any FOSS project has certain advantages that comes with the label - promotion by individuals and industries, widespread training and external contributions. Some companies/projects start off as FOSS (almost always with CLA) and take advantage of all those. Then when they’re popular, they switch to non-commercial, citing competition. Hashicorp and Redis are examples of these. When they cite unfair competition, they’re outright denying the contributions of external players like contributors and industry that popularized it. It’s basically a rug pull.
Another form of this is a recent trend of people claiming that non-commercial clauses count as FOSS. I’ve heard weird claims like the FSF and OSI don’t a monopoly on the definition of what’s FS or OSS. Yet others simply ignore these definitions. Any project that wants to be source-available should compete on their own merit, rather than riding and exploiting the world’s preference for FOSS.
Just want to reiterate - it’s ok as long as it starts as such, instead of doing a bait and switch. But another method is to use AGPL or similar license for all your code. The corporations that exploit FOSS code hate this license. And that’s why they widely promote the idea that copyleft licenses are less-free compared to permissive licenses (less free for them to exploit, perhaps). Unfortunately, many FOSS developers have bought this BS.
Corporations convert a lot of FOSS code into part of their closed source products. Using copyleft instead of permissive license is a good way to prevent that. But that aside, there is one class of software whose exploitation can’t be solved with copyleft licenses - cloud software. Many companies that switched licenses were offering cloud services. And then AWS of GCP comes and offers their cloud version, forcing the smaller companies to go source-available. The main problem I see is, why are they cloud software? The main goal of free software is freedom - especially the freedom to privacy, to own the data and to decide on the computation. That’s much better served on local machines than on the ‘cloud’. That’s much easier today with machines that are magnitudes of order more advanced than a decade old ones in terms of computational power and storage. Yet, we see companies wanting to turn all that computing power and storage into mere thin clients with everything from note-taking tool to entire operating systems offered as SaaS. This entire problem happened because the ‘freedom’ part of ‘FOSS’ got de-emphasized in-lieu of profiteering.
I’m part of that group. If OSI and FSF want to control the definition of something, they should make new and unique terms, not just attempt to take over a concept that predates both of them. (Interestingly, OSI’s website claims no one used “open source” to talk about software before 1998, and that’s patently not true; I remember seeing people use that in IRC channels back in the early 90s). If I came along tomorrow and said, “my org now controls the definition of ‘downloadable software’,” people would tell me to sod off. Even worse “Open Source” and “Free” are both terms with plain-English meanings (which most people naturally assume to be what people are calling “source available”, in OSS’s case). Trying to impose centralized control over a simple phrase isn’t really in line with the collaborative, community-led spirit of the FOSS community, imho
Call it OSI-Approved Zero-Restriction Licensing or something.
Funny, that’s how I feel about OSI stepping in to claim control of that term.
I agree with this for existing projects, absolutely.
Whether that term existed before it or not, that’s what people understand now. When talking about FOSS software, those definitions are what people expect - by a humongous wide margin. Calling those terms ‘generic’ is the weakest argument I have heard to dismiss the rigorous meaning people attach to it. Standards are centralized for a reason - so that everyone is on the same page. There’s nothing wrong with it. Claiming otherwise isn’t anarchy - it’s an intent to cause unnecessary confusion.
Trying to subvert those definitions and trying to pass of non-commercial as either Free software or Open source software are in my opinion, rather malevolent distortion of an existing paradigm meant to help only the companies that I mentioned before - those that want to exploit the FOSS ecosystem, but without making the necessary compromises. It’s an attempt to exploit a widely-held belief based on a rather vague and frankly misguided technicality.
Non-commercial sources already have an appropriate term - ‘source available’. It’s another generic term with a well-defined meaning. Hijacking the meaning of ‘open source’ and 'free software, instead of using this one is the perfect indication of the misleading nature of the hijack. And looking at the prevalence of this, I’m starting to suspect a widespread astroturfing/misinformation campaign.
Funny, they just used a generic term to mean something, while the exploiters use the term that means something to hide their true intentions and profiteer.