Isn’t that why FOSS survives as a model and is encouraged so much, though, so there is something to enclose and charge bullshit fees for once you fork it?
Not all licenses allow charging for forks. You can charge for your services always. And you can charge for code that is all your own. But, only certain licenses allow you to actually fork and charge for it without sharing those contributions. And many might not even really consider those licenses to really be FOSS.
It’s particularly popular for startups to use to bootstrap their tech company and build cred shortly before they reach the “we have to actually turn a profit” phase, at which point the bean counters try to squeeze every bit for a nickel. Once they have marketshare, they say, “we are helping the competition by releasing this!” and abandon the things they actively maintain.
There is also a direct benefit for open sourcing: you can get other people to debug and improve your software for free. They go the enclosure direction once they want to squeeze their customers for more money, e.g. closing the source code and charging $x per use of the software to their service clients.
Once they’re a monopoly, companies can swing back to the open source direction because they have no competitors to worry about and can just get free dev work and good will out of it.
My best guess about their purchase is that they wanted to do a bunch of copyright infringement of code hosted on GitHub to train their language models. Are you thinking there’s also a motivation to get free dev work another way, too?
So, don’t mistake this as me telling you you’re totally wrong, because you definitely do have a point and it gets under my skin too (that’s why I believe licenses like AGPL and, dare I say, SSPL should be used), but many of these companies actively contribute back to the open source software they’re using.
[the SSPL] primarily replaces [the AGPL v3’s] section 13 “Remote Network Interaction; Use with the GNU General Public License.” with a new section that requires that anyone who offers the functionality of SSPL-licensed software to third-parties as a service must release the entirety of their source code, including all software, APIs, and other software that would be required for a user to run an instance of the service themselves, under the SSPL. In contrast, the AGPL v3’s section 13 covers only the program itself (the copyrightable work licensed under AGPL v3).
I get what they’re going for and I sympathize with the goal, but I’m not sure there’s any software in the world that could comply with that license because it would have to release an entire container or disc image with nothing but SSPL software from the kernel on up. Does a SSPL-licensed kernel or httpd even exist?
Even if they want to do it, can they? The Wikipedia article claims that every piece of software necessary to run the service would have to be licensed as SSPL. Not just to have its source code released in compliance with whatever other copyleft or permissive license it was under, but relicensed as SSPL. That means (assuming the Wikipedia article is accurate, anyway) you can’t even run it on top of Linux and be in compliance with the license! You’d have to write your SSPL service for the bare metal hardware, or write an entire new SSPL-licensed OS for it.
So, without getting too into the specifics about SSPL because you and many of the critics of it I agree with in that it seems poorly thought out or too aggressive, I do think AGPL fails in some ways. Mongo and (I think) Elastic were both licensed under AGPL but made/changed to SSPL because of a perceived abuse by cloud services like Amazon. As for what exactly the cloud providers were doing that they perceived as wrong and what the best solution is I’m not too sure. It could be that Elastic’s own managed version of its product wasn’t getting any use because Amazon’s was benefiting from economy of scale and vendor lock in (“hey, we already have everything on AWS, let’s use AWS’s Elastic offering”) and if that’s the case then it’s not really a failing of software licenses and just a shitty and unfortunate situation.
One of the things libre software is trying to accomplish is letting anyone use it for anything and allowing competitors to monetize it is a valid use. It seems like Elastic and Mongo may have been trying to have a primary revenue stream be money from offering their own managed service and cloud providers were out competing with them. It’s hard to not see this as them being a parasite that will take over the host and eventually kill them both because the devs of the product will stop getting compensation.
Some products (I think QT is another example) offer a GPL/AGPL version but for a fee will give you a more traditional license (non copy left) and this allows users to have a way to keep their own code closed source while providing revenue for the creators. Win win. AGPL was made to fix a loophole of putting a GPLed product behind a web interface and then saying “hey I’m not technically distributing anything so I don’t have to release my source code.” You’d think that most enterprise folks would pay but it seems like the cloud providers didn’t need to because they found ways around AGPL or just didn’t modify anything.
Like I said in another comment, no matter how you look at the situation, open source devs are getting taken advantage of. Enterprise customers should set the example and monetarily support the devs of open source software they use. While they do sometimes it’s not the norm. Even within the same company you see mixed behaviors. Microsoft has been contributing code back to git and adding new features but also “stole” AppGet. They even interviewed the dev and asked specific questions about it. It’s just scummy. It’s a reminder that something being legal isn’t automatically ethical or moral.
and are hardly the only companies using FOSS; everyone from non profits to miliary systems use it. this meme doesn’t really work when you take the whole picture into account.
I have two diverging responses to this - one, if they’re credited for their commits, in the purview of FOSS projects, they’re compensated as much as they expect; two - that said, I would love to see FOSS projects get more love and financial support from the community - which is why watching the GODOT project has been exciting. I’m not much of a dev, and not in a position to contribute to what they’re doing in code, but sending them some coffee money has been worthwhile.
Even in Stallman’s visions open source was not hostile to making money at all, as long as the tenets are followed. Also, you might wanna read economics.
Because last I checked, Microsoft, Apple, Oracle and Google still are the biggest companies and their wealth rests primarily on closed source software.
I would think for the “largest” transfer of wealth, we would be able to pinpoint some poor exploited geeks coding software juxtaposed against some rich fat cats making money off of it.
But Linus Torvalds doesn’t seem poor and IBM/Red Hat, while rich, is much smaller than Microsoft.
Apple I think relies heavily on the BSD project (I think they might be even using the same kernel?) and Google on Linux. There’s also probably a lot of open-source software they use behind the scenes or which aren’t as big.
In Linus’ defense, I would probably pay the person that wrote and maintains the software that literally runs the world pretty well too. Can’t afford not to.
You should be aware that much of the effort of some big players like oracle and even microsoft goes into Linux. I am not aware of how this is for other FOSS projects but I would assume many companies have embraced open source. This may not be out of the goodness of their hearts but they definitely pour a lot of effort into these ojects and I think that is the beauty of FOSS, but also the beauty of the free market.
On the other hand, I’d wager that any given person who uses Linux daily at work is far more likely to own a stake in their company than the average worker.
My Linux laptop is also literally my means of production, which I own. Karl Marx never predicted this.
He also didn’t predict a class of people born with no labor to sell because so much of it has been automated away. How are they supposed to use their labor as a bargaining chip if they can’t find labor to do to begin with?
Marx wasn’t a technological determinist though. He believed that a workers revolution would bring the end of capitalism. He even thought it would happen druing his lifetime.
Marx did talk about individuals owning the means of production. For example farmers or craftsmen owning their tools before capitalism. Marx talked about the means of production being shared under communism and not owned by one specific person or capitalist. If anything Marx predicted FOSS lol.
Except this is really reductionist and ignores there is very little “open hardware” out there, and few people producing it. So while you might have access to the “means of production” through software, you absolutely do not in hardware.
Great that software tools are in the hands of the worker, but the means to fabricate the machines that code runs are definitively not owned by workers. (To say nothing of issues with getting drivers for a DIY motherboard working with Linux long-term.)
Also, not everyone is born to code, so it’s a bit elitist.
You can use FOSS without knowing how to code though. I wasn’t completely serious I know Marx didn’t predict FOSS but I do think it’s an example of how the means of production being shared could look like. It would be great if that also included open hardware as well.
Edit: I realize it means the workers doesn’t actually own the means of production but it’s a step in that direction and I don’t think it contradicts what Marx said is my point.
lemmy.ml
Hot