BTW, you should probably change https://redislabs.com/community/oss-projects/ to match the the non-Open-Source-licenses most things have there. (yes, they are listed, but the page pretends everything on it is Open Source)
Here is the Free Redistribution section: "The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources."
Yiftech commented that the reason for making the switch was that "AGPL does not prevent cloud providers (such as AWS) from building managed services from these modules". The entire reason for making the switch to licensing the modules under the new license is that the Free Redistribution aspect of AGPL and other open source licenses allows cloud providers to use the software in a way that Redis labs doesn't like.
Cloud providers are not "giving away or selling" the software, they are running it, which isn't covered under that section.
You're probably looking for #6:
> 6. No Discrimination Against Fields of Endeavor
The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research. ... or in this case, "offering Redis with extension X as a Service"
> You're mixing up Open Source and Free Software, those two are not the same.
There is an ideological difference between the movements, but very little practical definitions between the OSI Open Source definition and the FSF Free Software definition. Yes, they are worded differently, but in practice they are virtually identical (I don't think a single license has been reviewed by both entities with a different conclusion.)
They have different ideologies behind them, but they refer to almost exactly the same class of software. A license that doesn't allow commercial use is proprietary and closed source.
Not closed source since the source is public and freely given [1].
Not open source because the license [2] forbids use based on field of endeavor which is required in the OSD [3].
As for the other direction, you can't have software be Open Source and closed source simultaneously since being Open Source requires the source to be available. Or in symbols.
According to most of people who invented the term "open source", the OSI and their open source definition, propritary software, even if you can see the source, is not "open source".
Nearly everyone uses the term "open source" this way, and to use it otherwise is grossly misleading.
Of course, if you follow the osi definition you are absolutely correct. [1]
"the obvious meaning for the expression “open source software”—and the one most people seem to think it means—is “You can look at the source code.”" [2]
The main problem imho lies in the fact that afaik we still don't know how to call proprietary software with released source code, although this is mighty common (again, see github). If that problem is solved, the osi definition is much better applicable.
(On a side note: A word that might describe such software is public. Public Software vs. Open Software Software. This however is again problematic because of "public-domain" software.)
> the obvious meaning for the expression “open source software”—and the one most people seem to think it means
I disagree. I think if you ask nearly people who know what the term "source code" means, if you ask them what "open source" means, they'll give the OSI definition (which is in practice the same as the FSF's 'free software' definition). They'll say it's more than "I can look at the source", but includes the rights to share and build on it.
Microsoft tried the term "Shared Source", which might be what you mean.
