>I still consider SSPL to be "free software" very much within the ideals that movement, regardless of what the OSI says.
Yeah, I think the issue is that these days there's a lot of open source developers, who zealously believe in open source, but are working for corporations. They have a natural incentive to maximize the usefulness of open source for corporations, whether they explicitly acknowledge that or not. On a social level, I think that's having many effects, one of which is the backlash against SSPL, which is obviously hard for mostly-proprietary corporations to comply with.
Many open source programmers have built a mental model around the notion that the scripts that operate and deploy an application (service) aren't part of the application (service), and therefore don't need to be open source. But that doesn't make any sense from a software-freedom perspective! The fundamental tenets of open source are that users should be able to use, modify, and redistribute the application. If the users don't have access to the scripts that are required to actually deploy a modified version of the service, then it's not meaningfully open source. That's a new perspective, it's true, but I think the old perspective (the scripts to deploy a service don't need to be open sourced) was just wrong, it came from a long period of biased, commercial-centric thinking.
Yeah, I think the issue is that these days there's a lot of open source developers, who zealously believe in open source, but are working for corporations. They have a natural incentive to maximize the usefulness of open source for corporations, whether they explicitly acknowledge that or not. On a social level, I think that's having many effects, one of which is the backlash against SSPL, which is obviously hard for mostly-proprietary corporations to comply with.
Many open source programmers have built a mental model around the notion that the scripts that operate and deploy an application (service) aren't part of the application (service), and therefore don't need to be open source. But that doesn't make any sense from a software-freedom perspective! The fundamental tenets of open source are that users should be able to use, modify, and redistribute the application. If the users don't have access to the scripts that are required to actually deploy a modified version of the service, then it's not meaningfully open source. That's a new perspective, it's true, but I think the old perspective (the scripts to deploy a service don't need to be open sourced) was just wrong, it came from a long period of biased, commercial-centric thinking.