5 ms·
Not everyone agrees that the freedom to start a SaaS business with GPL software is a "loophole".
by sneak 6y ago
Not everyone agrees that the freedom to start a SaaS business with GPL software is a "loophole".
- hnarn 6y agoI wonder when this idea really started propagating, was it around when AWS came along? Because by a technical definition I don’t understand why this “loophole” wouldn’t also apply to a hypothetical web host back in the late 90s.
- rakoo 6y agoThe GPL has no element saying it can't be used to start any kind of business, and I don't think any of its defenders has ever said the GPL's goal is to suppress that freedom. It seems the FUD is still going strong.
- sneak 6y agoThe same people who made the GPL use the term "ASP loophole" and made the AGPL. Not everyone agrees that the freedom to make a SaaS business with a private GPL fork is a loophole or bug. It seems (from their creation of the AGPL and use of terms like "ASP loophole") that the GPL people do.
- posguy 6y agoNot everyone has trouble with AGPLv3 being the core of their SaaS business. Just because your core business software is AGPLv3 doesn't mean any other business will be able to build a coherent business model atop it, look at Kazoo by 2600Hz or Iris by Lowes. Knowing how to properly configure and maintain said code in production, creating integrations with third party vendors (that your competition likely can't interact with on the same terms) and marketing to build mindshare among potential customers is a common way to offer your core software as AGPLv3 yet have no competitors or few competitors use your core software.
- Dylan16807 6y agoBut the comment you replied to was about the v2->v3 loophole fixing. That has nothing to do with AGPL, it's about bootloader locking.
- kmeisthax 6y agoAGPL isn't pro- or anti-SaaS, though. It just says that you have to provide sources to anyone you grant access to the software over a network. So if you host an AGPL database for someone else, they need access to the source code for that database somehow. But it doesn't prohibit you from hosting the database at all. It's the perfect license for MongoDB and all these other companies trying to keep Amazon from taking their software and proprietarizing it... but instead they make weirdly restrictive one-off licenses nobody are going to contribute to.
- sneak 6y agoAGPL restricts developer freedom simply because they launched a webserver on the same machine. There is a legitimate logical argument that the AGPL is not free software.
- Iolaum 6y agoThe whole idea behind copyleft, hence free software as Stalman envisioned it, is to restrict the developer's freedom in favour of the user freedom.
- Pet_Ant 6y agoCopt-left licenses are about preserving the users’ freedom. If we want to maximize developers’ freedom then the freest license is proprietary code where you own all the rights and then you can do anything you want and nobody can do anything about it.
- kmeisthax 6y agoNo, the license that maximizes developer freedom is a permissive license, like Apache, MIT, BSD 3-clause etc. That lets you mix your code with either a proprietary or a copylefted project. Since a lot of Free Software is written by people who just want to solve a problem for themselves, they often just pick the permissive license. Proprietary code is actually the most restrictive to both users and developers. That's because you can't legally mix proprietary code without a license at every step of the way. Any significantly large proprietary project becomes a mass of third-party dependencies with all sorts of license restrictions that your company is probably ignoring and breaking. Even if you follow all the tenants of those licenses, you don't own your code at the end. A Node-style mess of dependencies becomes ten times worse when each dependency has license restrictions attached to it. In other forms of media, you generally don't see people try to license 30-50 different properties all at once for the same work, because that means nobody owns anything and the work will be really hard to market internationally. Software almost demands this sort of dependency soup, however, which creates all sorts of unique preservation problems. Whenever a large software project (or game engine) is discontinued, a lot of people wonder why the company who wrote it doesn't just release the code as Free for third parties to maintain. The answer is that in most cases, it's not their code to release.
- chimeracoder 6y ago> Not everyone agrees that the freedom to start a SaaS business with GPL software is a "loophole". Neither GPLv3 nor GPLv2 prohibit this. You're thinking of the AGPL, the first version of which was based on the GPLv2 and released in 2002, years before the FSF announced that they were even beginning work on the GPLv3.
- cma 6y agoThe reason people confuse it is because early work on GPLv3 was going to include similar clauses but they were later abandoned.
- kazagistar 6y agoThats wrong too. If you use an unmodified version of AGPL software, or just host any modifications in a public repository like github, then you aren't in violation of AGPL, even if the rest of your stack is proprietary and your service paid. How does it prevent SaaS?
- ckocagil 6y agoAre you thinking of AGPL instead of GPLv3?
- rakoo 6y agoAGPL, like any version of GPL (and most if not all open source licenses) does not prohibit anyone from starting a business. It's weird this FUD is still spreading after all this time, after all the debates the community has had already. AGPL does have restrictions, and it's anyone's preference as to whether they're good or bad, but there has never been an intent to forbid businesses. If anything it's the recent RedisLabs' modules license and the SSPL-style licences that do it: they explicitely contains the wording to indicate that the product can't be used to create a similar product and offer it as a service. Heck, the SSPL says (https://www.mongodb.com/licensing/server-side-public-license https://www.mongodb.com/licensing/server-side-public-license): "If you make the functionality of the Program or a modified version available to third parties as a service, you must make the Service Source Code available via network download to everyone at no charge, under the terms of this License" The AGPL tells you that if a user asks for the source code, you must give it to them and them only. The SSPL says that the source code must be publicly available to all, at no cost. It was created specifically to prevent competitors to run MongoDB as a Service. Surely if they had to change it's because the previous license did authorize competitors to do it. Wanna take a guess what the previous license was ?
- xyzzy_plugh 6y agoI can count the number of remotely successful businesses built on AGPL software on one hand. The AGPL doesn't prohibit starting a business, it makes starting a business prohibitive.
- posguy 6y agoOwnCloud, NextCloud, Linphone (their pricelist starts in the 5 figures for support!), etc all run successful businesses off AGPLv3 code. Amazon is notorious for turning AGPLv3 projects and products into SaaS services! Look at all the SaaS offerings of MongoDB (formerly AGPLv3): https://news.ycombinator.com/item?id=19362919 https://news.ycombinator.com/item?id=19362919 AGPLv3 doesn't make starting a business prohibitive, arguably forks like NextCloud would not exist if AGPLv3 did not compel codebase users to publish the additional code they wrote to extend OwnCloud