News for hackers. Stuff that matters.
Re:What’s up with these new not-open source licenses? by dragonwriter on Thursday March 18, 2021 @06:36PM (#26508272)
> After all, they are designed only to impact companies attempting to sell a SaaS.

Well, that’s the PR message associated with the new wave of source-available licenses (source-available licensing is not, itself, new; its long been an established form of proprietary licensing.) But it doesn’t hold up: you can’t harm competing services providers without harming end users. There is a reason why the very different ideologies of the Free Software Movement and the Open Source Community nevertheless have stably settled on definitions which are virtually identical in practical applications (and even though those communities have very different preferences for licenses within the scope meeting their similar definitions.) It is because the space is not a continuum, and there is a minimum needed in each of a number of axes of liberty for the whole structure not to collapse into something which either community prefers free/open licensing. Particularly, without robust freedom that protects what other people can do with it (including there ability to sell you services built around the software that the original maker might also want to sell), you are not insulated against future actions of the copyright owner restricting the software or its or others services around it.

And this isn’t opaque to the people issuing these licenses; the overt motive is to enhance monetization by preventing licensees from competing with them to sell services: it is to create a moat enabling monopolization and monopoly rents. That’s the explicit idea: to create lock-in that free/open licenses would not support.

The benefit that the licensors seek directly depends on the harms that extend beyond competitors to end users.

Re:What’s up with these new not-open source licenses? by scottrogowski on Friday March 19, 2021 @06:40AM (#26511851)
> you can’t harm competing services providers without harming end users.

> the overt motive is to enhance monetization by preventing licensees from competing with them to sell services: it is to create a moat enabling monopolization and monopoly rents.

Here's the problem: Amazon, Microsoft, and Google are already able to charge something approaching monopoly rents because they have built a moat that others can't dream to cross. Heck, try to even build two services that talk to each other between the moats and you will get hit with massive data-egress charges. And they do this by monetizing free products with no compensation to the developer. If you are Redis, your hosted product, whose core you developed, is less competitive than that of the cloud providers who didn't contribute anything to the project. At the same time, the parent tech behemoths are engaged in all sorts of other bad behavior that only massive tech companies can get away with.

This state of affairs seriously threatens the open-source ecosystem and the source-available licenses are targeted to righting this imbalance. Again, are they perfect? No. If you are making money selling the software without modification, is it reasonable to ask for royalties to go to the developers? I think, on balance, that is reasonable.

If not source-available licensing, what is the better solution to the problem?

Re:What’s up with these new not-open source licenses? by dragonwriter on Friday March 19, 2021 @10:58AM (#26514074)
> Here's the problem: Amazon, Microsoft, and Google are already able to charge something approaching monopoly rents because they have built a moat that others can't dream to cross.

Even if that was true and they acted like a coordinated oligopoly rather than actively competing, including on price, more monopolies in adjacent markets make things worse, not better, for everyone (customers especially) except the additional monopolists.

> If you are Redis, your hosted product, whose core you developed, is less competitive than that of the cloud providers who didn't contribute anything to the project.

Yes, that F/OSS licensing advantages the firms that have the best infrastructure for monetizing services has been widely observed since it was just Free Software because OSI didn't exist yet, before cloud dominance that was mostly about professional services. And, yes, proprietary (and sometimes source-available) licenses which don't deliver the value of open source to end users have always been the “solution” to that.

What's novel recently is a bunch of firms ignoring well-known facts about the economic incentives around F/OSS, trying to build rapid-growth startups around F/OSS with no plan at all to address the strengths necessary to monetize F/OSS, then whining about the well-known advantages of established firms to pivot to proprietary licensing, then having the unmitigated gall to pretend their proprietary licenses provides the customer benefits of F/OSS licensing (which center on the fact that F/OSS doesn't create a vendor monopoly), despite the fact that not providing those benefits is central to the business reason for which they have adopted the proprietary license.