"
What's changed is that once open source started getting serious VC's, people believe they've created tons of value, and should be able to extract some of it (in reality, the model created most of the value, not them).
In the past, people were just relatively happy to be doing okay for themselves while created cool software.
Once you try to move to "value extraction", things become a lot thornier because you discover you aren't as important as you thought you were - your attempts to extract value fail. Usually, because it was not you who created the value, but the model.
I would much rather an honest transactional relationship for commercial software. That also includes consumer commercial software, like phone apps and websites. If we had honest expectations about the cost of software we wouldn't see so much aggressive advertising and tracking.
There are fantastic use cases for the generosity of open source. Education software is something I whole heartedly agree should be driven by open source. But I feel open source has been taken advantage of in commercial settings.
That is often true, but i guess i try to be pragmatic. I did not create the corporation or do all of that work to make that happen. Maybe people think this is easy, but it's not. it is a lot of work in most cases.
I also get paid plenty. Why should i care that someone else is getting paid more? None of this was ever about making significant amounts of money, and open source is almost certainly a bad model to achieve that for real. It tends to create lots of value and attempts to distribute that value usually destroy it.
I may be weird about this though. I have plenty of friends who have made hundreds of millions or billions building those corporations. I chose not to do that, and instead be happy with what i've got (and i've got plenty) and value different things.
This is true of everything. This isn't a problem with open source, it is a problem with society generally.
But the value those corporations are creating is embodied in much more than just the software. It's the whole infrastructure they build, which integrates the software into a complete solution that meets users' needs.
> Why would I want to build a tool for corporate infrastructure if they take it and make millions while I run support for free?
If someone is using a corporation's cloud infrastructure that happens to rely on open source tools you made, they're not going to call you for support when something goes wrong; they're going to call the corporation. If the corporation comes asking you about it, you are perfectly free to set the price of your services to them.
Back to the desire to work on OSS. I used to work on an OSS eCommerce platform for a living, and as an agency we would contribute back. The platform gives us work because it exists, we contribute back. But it's still all commercial software made for monetary gain. Its just tiring, and deters me from working on it after hours. I don't want my whole life to be about making other people money.
Amazon on the other hand...
It made more sense when you could release a product openly and then start a business around supporting it, consulting and training and selling "enterprise" versions for serious customers. But now that's even hard to do when everyone just wants to use AWS, etc to use this software.
It's a double edged sword and we take for granted. These projects have grown and become so feature rich because of the investment in them and the ability to hire hundreds of developers to contribute full time. But then this is harvested by someone who isn't paying for it and not just a little bit - a whole lot. What will eventually happen is we won't have feature rich products that are open source in the future without a change in how we think about licensing. The Apache License is not compatible with running a business around an open source project any longer.
Whether Commons Clause is the right solution or not (and I have my opinion on that), at least the Redis people are trying something to fix the problem of unstustainable one-way resource extraction by mega-corporations. Of the hundreds of people criticizing them here, often in ways that question their motivation and integrity, how many are offering alternative solutions? As far as I can tell, it's a depressingly small number.
After everything Antirez has contributed to us, he deserves better than this avalanche of unconstructive negativity. If you think Commons Clause is not the correct solution to the problem of unsustainable exploitation of open-source projects, what do you propose?
The only thing they're doing "differently" is the deceptive messaging. For this, I blame the Commons Clause initiative.
Redis Labs could take these same actions under a non-deceptive name and the response of the Open Source community would be vastly different.
Lots of companies have an "open core" model (where the core is OSS and some modules are proprietary). Many organizations have mechanisms where you can review source code of their proprietary code, subject to certain requirements. When things are made clear, there's no deception.
But naming a license rider "Commons" seems designed to cause confusion. It'll be easily confused with OSS licenses (since a "commons" is the discussed reason for having them) and with the well-known Creative Commons licenses. Saying it's a rider "with" the Apache License 2.0 also makes it appear that that this is the Apache License and endorsed by the Apache Foundation, which it is not. Saying that something is only OSS if you use the standard definition of OSS makes it sound like there's a minor legal nit, but it's a fundamental precept that OSS allows any use (including use by business).
> Redis Labs could take these same actions under a non-deceptive name and the response of the Open Source community would be vastly different.
I think that's right. I'm sure some would be unhappy, but the real problem here is the naming that seems designed to mislead. I'm not sure the information here was actually designed to mislead, but if that wasn't the intent, I think Redis Labs needs to change the names to quell the confusion.
If Redis Labs continues to use these confusing names, I suspect that the Creative Commons Corporation and Apache Foundation will consider going to court to protect their trademarks, since otherwise there's a significant risk of confusion in the marketplace (the reason that trademarks exist). Hopefully Redis Labs will just change to less-confusing names and then the problem will disappear.
I get that Commons Clause does not meet the official definition of Open Source (which I believe they admit upfront), but it’s definitely different from “open core” and from whatever Red Hat calls their model. Since it’s something new, it seems reasonable to give it a new name. I don’t have any strong opinions about the name “Commons Clause, maybe there’s a better name for it, but I wouldn’t call this one deceptive.
In the 90s and 2000s, OSS project were more grass roots efforts. In the past decade, there have been a series of primarily commercial OSS projects like Redis and ElasticSearch that have gained a fair bit of traction. They really aren't grass roots efforts, don't have a lot of volunteers, and have seen their business model gutted by AWS.
I think that's very unfair. Both Redis and ElasticSearch are definitely grassroots projects - both Salvatore (Antirez) and Shai worked on their projects for years, with minimal support from the outside world, grew their community organically, and managed to build something useful for thousands of grateful developers. Later, they looked for ways to make a good living while continuing to invest in the success of their projects. In the process they built (or joined, in the case of Salvatore) businesses dedicated to supporting the development of their project. There is no perfect solution, but in both cases I would say that they succeeded - they are making a good living, and their projects have continued to grow and make many users happy, in great part thanks to them and the business they work with.
To use that success as an argument against them - to present their business efforts as opposite to their community efforts is just not true, and I think it’s harmful. It punishes them, the creators and maintainers of a great and useful project, for wanting fair compensation for their efforts, and making the effort to give back in the process - when so many others profit from their work, and give back nothing, or the bare minimum to make themselves look good.
In other words, making a good living from the product was an afterthought. So they shouldn't be surprised that they're not getting as much value for themselves out of the product as they would have if making a good living from it was a fundamental part of the project from the beginning.
That's not to say that there aren't ways to monetize open source products, just that doing it as an afterthought isn't one of them. If it's a business, it's a business, and you have to treat it that way from day one. Otherwise you will be out-competed, as a business, by others who do.
Says who? You are entitled to your opinion on the matter, but this is a very contested issue and your opinion is just one of many. If you’re going to argue that Redis and Elastic are “doing open-source monetization wrong”, maybe you should back up your claim with arguments.
> If it's a business, it's a business, and you have to treat it that way from day one. Otherwise you will be out-competed, as a business, by others who do.
You seem very knowledgeable about what is and is not a good monetization strategy for open-source. What do you propose as an alternative to what Elastic and Redis are doing?
I did. Did you read my post?
> What do you propose as an alternative to what Elastic and Redis are doing?
As an alternative now? I'm not sure there is one. Their products are already out there being monetized by others.
As an alternative back when they started? They could have let everyone know that they were aiming to monetize their products as a business from the beginning. Then they would have been taking on for themselves the business risks that cloud providers, for example, took on by building infrastructure using their products and trying to sell it to users.
That said, I never made the argument that their business efforts were a bad thing nor opposed to community efforts, though certainly others have in this context.
Personally, I believe that both commercial entities are entitled to compensation. One of the points that I was attempting to make is that AWS nearly killed their respective businesses by reselling the product of their efforts while making no contribution back to either project.
One is the following observation. Customers are usually willing to spend $X on a solution to their problem, but are relatively agnostic on how $X is divided up. So if customers are willing to pay about the same for Oracle on Sun, and for Oracle on Linux, but Linux is cheaper than Sun, then Oracle can (and did!) successfully charge more to run on Linux. The result is that it is in Oracle's interest to make the Linux solution available and preferred by any means necessary..including improving Linux.
The same logic applied to IBM contributing to Apache so that they could charge for Websphere. Or any other case where there is a required component of an overall solution.
The widespread recognition of this back in the late 1990s was why the open source movement so quickly got a lot of corporate sponsorship from big companies.
But open source didn't depend on these funding models in the 90s/2000s did it? I did a whole post on the philosophy of open source a while back:
https://penguindreams.org/blog/the-philosophy-of-open-source...
..but one of the things I didn't find enough sources on where a lot of funding came from (And percentage of volunteer contributors).
This recent Redis things reminds me of the Caddy controversy, and maybe even more recently, how Win/Mac Docker binaries are behind a login wall.
What changed? Do developers no longer have the time to volunteer to work on this stuff? The desire? Is the demand for tech in The Valley/West Cost changing the dynamics of how much time people have to contribute. Were the earlier efforts way less commercial and new efforts moving much faster and requirement more maintenance/resources?