@musicman It can take years for that to become effective. Red Hat typically supports software versions that is years behind the external versioning, and Debian is not known for being in a hurry about anything.
@musicman If I recall correctly, it is designed to prevent companies using SSPL licensed software to generate (substantial) profit, instead driving them to purchase a proprietary commercial license instead.
Think about how this would affect Amazon, Microsoft, Google, CenturyLink, and other large cloud hosting providers. This isn’t targeted at people like me, who spin up a server at home and run #MongoDB, #Redis, and similar services in a non-profit manner.
(I sympathize with companies who sponsor #FLOSS projects and find that the largest corporations in the world reap the benefit, but contribute little or nothing to the ongoing development and maintenance of the software. But going fake-open [“fauxpen”] is a case of the cure being worse than the disease.)
The additional clause that requires release of source code for a SaaS host’s entire service. That is, if you are Amazon, and you offer a cloud database based on #MongoDB as part of your AWS service, the license forces you to open the source repos for the entire AWS service ... including the “secret sauce” that serves as the reason people go with Amazon instead of “Uncle Fred’s Discount Cloud Hosting and Breakfast Cafe.
The #SSPL license is intended to make it unprofitable to host the service as a cloud-based offering, so that companies whose business is based around cloud-based service hosting will be forced to buy a proprietary commercial license, and therefore is not “free”.
OTOH, the #AGPLv3 forces release of the source (as used in operating the service) of the specific software (as modified and in use) and its derivatives, but not of other software used in operating your service.